|
Weston@PPE
|
 |
« Reply #15 on: August 15, 2012, 02:27:19 pm » |
|
We have found what was going on here, and we're currently working on a software fix for this. I was hoping that we would be able to get this working for you by having you change a setting, but the problem is deeper than that...
|
|
|
|
« Last Edit: August 15, 2012, 02:29:01 pm by Weston@PPE »
|
Logged
|
|
|
|
|
mterveen
|
|
« Reply #16 on: August 15, 2012, 05:32:31 pm » |
|
ok - great (i think  ) eagerly waiting for the fix. thx for your attention to this issue. |
|
|
|
|
Logged
|
|
|
|
|
mterveen
|
|
« Reply #17 on: August 16, 2012, 01:35:14 pm » |
|
p.s. please keep me in the loop on what kind of time frame i may be looking at for resolution of this. i really need to get this resolved and if it is going to be a couple weeks or more i need to come up with an alternative.
|
|
|
|
|
Logged
|
|
|
|
|
Weston@PPE
|
|
« Reply #18 on: August 20, 2012, 10:42:11 am » |
|
We're still working on the software fix for this, it will probably be in the next update of ScanXL.
Whats going on is that ScanXL is requesting PID data from the ABS module faster than the module can provide it. Instead of making us wait, and then giving us the PID information, the ABS module sends back a message that basically means "I'm busy right now, try again later". We weren't expecting that response, and the software currently isn't written to handle it correctly and marks the PID as not supported.
I was able to get more PIDs to work, and drove around the block watching all 4 wheel speed sensors. Before you connect, go to the Settings tab > OBD-II Settings, and change the Minimum Bus Idle Time to 50. What this does is forces the software to slow down, allowing the ABS module some extra time to process things in between our PID requests. You do need to do a PID validation after changing this setting.
Try that out and let us know how it goes. At 50, I was able to get 57 ABS PIDs shown as supported, compared to 27 PIDs previously -- more than double.
|
|
|
|
« Last Edit: August 20, 2012, 10:46:30 am by Weston@PPE »
|
Logged
|
|
|
|
|
mterveen
|
|
« Reply #19 on: August 20, 2012, 12:36:29 pm » |
|
will do
|
|
|
|
|
Logged
|
|
|
|
|
Weston@PPE
|
|
« Reply #20 on: August 21, 2012, 12:18:07 pm » |
|
We have finished a software fix for this, it will be in the next release.
|
|
|
|
|
Logged
|
|
|
|
|
mterveen
|
|
« Reply #21 on: August 21, 2012, 12:35:44 pm » |
|
great news weston:
1) glad to see the fix will be in the next version. any idea of the release date?
2)greater news! setting the bus speed to 50 mSecs WORKED. i just took the car out this noon and did an aggressive scan with the new setting and all the abs pids showed up green. yahoo. there were a few doubles but who cares at this point.
you the man! i will make sure i sing PPE's praises on the other forums i frequent. a couple bug fixes and you guys will be sitting at the top of the heap.
if you want to do a knockout punch on the other competitors, 1) get the bidirectional stuff going and 2) figure out a way to read the pcm and rewrite the pcm (similar to hptuners/efilive)
thx again.
|
|
|
|
|
Logged
|
|
|
|
|
mterveen
|
|
« Reply #22 on: August 31, 2012, 08:01:24 am » |
|
weston - are you able to provide a time frame on the next update?
|
|
|
|
|
Logged
|
|
|
|
|
Weston@PPE
|
|
« Reply #23 on: August 31, 2012, 11:49:02 am » |
|
Unfortunately I'm not able to give you an exact time frame, since I'm not the one with the final say on when we release updates.
|
|
|
|
|
Logged
|
|
|
|
|
bobbing
|
|
« Reply #24 on: August 31, 2012, 09:29:47 pm » |
|
Unfortunately I'm not able to give you an exact time frame, since I'm not the one with the final say on when we release updates.
Are there build dates and release notes with the program downloads? |
|
|
|
|
Logged
|
|
|
|
|
Weston@PPE
|
|
« Reply #25 on: September 01, 2012, 01:20:21 pm » |
|
There are release notes and dates with the downloads, but those are added the day of the release. We usually don't pre-determine an exact release date.
|
|
|
|
|
Logged
|
|
|
|
|
