FORScan and As-Built Data
#107
12-17-2016, 11:53 PM
#109
12-18-2016, 09:33 AM
I am actively working on "Bambi" mode. Fogs and High Beams.
Haven't noticed 911 assist. I will check that today.
Keith
#110
12-18-2016, 10:09 AM
Mike,
I'm sitting at 85% and have a shiny new OBDLinkMX sitting under the Christmas tree begging to be unwrapped. It will be tomorrow before I go anywhere though.
I will have to double check the 911 assist with the NAV override but I did lose vehicle health report (not that I or probably anyone following this thread ever use it).
I enabled my own version of Bambi mode via an upfitter and a couple of relays. Works great (as do the HIDs I put in the stock fogs) but getting my switch back would be nice. I plan to look at that as well as a allowing the doors to be locked with the key in the ignition. Currently if I have the truck started and lock it with the door button while the door is open, it auto unlocks. I'd like to be able to lock the truck when I get out without having to use the other key. I have the door keypad so unlocking without a key isn't an issue.
I'm sitting at 85% and have a shiny new OBDLinkMX sitting under the Christmas tree begging to be unwrapped. It will be tomorrow before I go anywhere though.
I will have to double check the 911 assist with the NAV override but I did lose vehicle health report (not that I or probably anyone following this thread ever use it).
I enabled my own version of Bambi mode via an upfitter and a couple of relays. Works great (as do the HIDs I put in the stock fogs) but getting my switch back would be nice. I plan to look at that as well as a allowing the doors to be locked with the key in the ignition. Currently if I have the truck started and lock it with the door button while the door is open, it auto unlocks. I'd like to be able to lock the truck when I get out without having to use the other key. I have the door keypad so unlocking without a key isn't an issue.
#111
12-18-2016, 10:39 AM
PM sent. Keep us posted. I feel like we are getting close to turning on OCR.
Mike
#112
12-18-2016, 03:16 PM
Dakster,
Are you getting the same message that I was when it doesn't write? I had the same message with a OBDlinkMX trying to write to the IPC module. I tried a different laptop and both my cheap ELM with MS switch and the expensive adapter would write to the IPC. So in my case, the issue was the laptop and not the adapter. Odd that it would write to the BdyCM but not the IPC.
Bob
Are you getting the same message that I was when it doesn't write? I had the same message with a OBDlinkMX trying to write to the IPC module. I tried a different laptop and both my cheap ELM with MS switch and the expensive adapter would write to the IPC. So in my case, the issue was the laptop and not the adapter. Odd that it would write to the BdyCM but not the IPC.
Bob
#113
12-18-2016, 03:27 PM
#114
12-18-2016, 04:18 PM
Keith,
For your spreadsheet
Dark Car
726-08-01 0200 38 is off
726-08-01 0201 39 is on
I did not discover this, it is already in Forscan BdyCM.
Dark car mode disables the interior and exterior lights from turning on when the door is open. It is typically used on police vehicles.
Bob
For your spreadsheet
Dark Car
726-08-01 0200 38 is off
726-08-01 0201 39 is on
I did not discover this, it is already in Forscan BdyCM.
Dark car mode disables the interior and exterior lights from turning on when the door is open. It is typically used on police vehicles.
Bob
Thanks I will update today
Side note, I had no issues writing to IPC today.
Keith
#116
12-18-2016, 11:44 PM
Dakster,
Are you getting the same message that I was when it doesn't write? I had the same message with a OBDlinkMX trying to write to the IPC module. I tried a different laptop and both my cheap ELM with MS switch and the expensive adapter would write to the IPC. So in my case, the issue was the laptop and not the adapter. Odd that it would write to the BdyCM but not the IPC.
Bob
Are you getting the same message that I was when it doesn't write? I had the same message with a OBDlinkMX trying to write to the IPC module. I tried a different laptop and both my cheap ELM with MS switch and the expensive adapter would write to the IPC. So in my case, the issue was the laptop and not the adapter. Odd that it would write to the BdyCM but not the IPC.
Bob
Interesting as I was just getting ready to get an OBDlinkMX... It's possible both my laptop are screwy... Was the other laptop a Win10 Box as well?
Ohh and I found out the dark car setting was for police vehicles by trial and error...
#117
12-19-2016, 11:30 AM
Dakster,
Neither computer was windoze 10. I am a Linux guy but occasionally I am forced to step to the dark side. The first computer I tried was an old XP SP3 box and the one it worked was a Vista box. Don't know if my issue was operating system (XP) or just the age of the Bluetooth adapter in that computer.
If you have access to a non-windows 10 machine, it may be worth trying before buying a new adapter. If not, you could try running Forscan in compatibility mode. Worth a shot at least. See the link for instructions.
https://support.microsoft.com/en-us/...ams-compatible
Got a local auto parts store with a USB OBDII reader that you could borrow?
Keith, Mike, are either of you running Windows 10?
Bob
Neither computer was windoze 10. I am a Linux guy but occasionally I am forced to step to the dark side. The first computer I tried was an old XP SP3 box and the one it worked was a Vista box. Don't know if my issue was operating system (XP) or just the age of the Bluetooth adapter in that computer.
If you have access to a non-windows 10 machine, it may be worth trying before buying a new adapter. If not, you could try running Forscan in compatibility mode. Worth a shot at least. See the link for instructions.
https://support.microsoft.com/en-us/...ams-compatible
Got a local auto parts store with a USB OBDII reader that you could borrow?
Keith, Mike, are either of you running Windows 10?
Bob
#118
12-19-2016, 12:00 PM
#119
12-19-2016, 12:17 PM
Thanks,
Mike
Last edited by blkout50; 12-19-2016 at 12:20 PM. Reason: Fix typo.
#120
12-19-2016, 01:08 PM
Cargo Master
Dakster,
Neither computer was windoze 10. I am a Linux guy but occasionally I am forced to step to the dark side. The first computer I tried was an old XP SP3 box and the one it worked was a Vista box. Don't know if my issue was operating system (XP) or just the age of the Bluetooth adapter in that computer.
If you have access to a non-windows 10 machine, it may be worth trying before buying a new adapter. If not, you could try running Forscan in compatibility mode. Worth a shot at least. See the link for instructions.
https://support.microsoft.com/en-us/...ams-compatible
Got a local auto parts store with a USB OBDII reader that you could borrow?
Keith, Mike, are either of you running Windows 10?
Bob
Neither computer was windoze 10. I am a Linux guy but occasionally I am forced to step to the dark side. The first computer I tried was an old XP SP3 box and the one it worked was a Vista box. Don't know if my issue was operating system (XP) or just the age of the Bluetooth adapter in that computer.
If you have access to a non-windows 10 machine, it may be worth trying before buying a new adapter. If not, you could try running Forscan in compatibility mode. Worth a shot at least. See the link for instructions.
https://support.microsoft.com/en-us/...ams-compatible
Got a local auto parts store with a USB OBDII reader that you could borrow?
Keith, Mike, are either of you running Windows 10?
Bob
Bob, with regards to a viable workstation to run Forscan, I'm a MAC guy. I downloaded VirtualBox from Oracle(free), and installed a clean copy of Win10 inside it. there is a Linux version of VB as well. Win 10 .iso can be downloaded from Microsoft, installed for Free and used. You just have to have a purchased license to activate it, but I've been running an unactivated copy for a few months now, and the only thing you cant do is customized the UI on Win10 without activating.