Vs commodore wont connect to tunerpro

160 And 8192 Baud Aldl
User avatar
Tazzi
Posts: 3422
Joined: Thu May 17, 2012 8:53 pm
cars: VE SS Ute
Location: WA
Contact:

Re: Vs commodore wont connect to tunerpro

Post by Tazzi »

VL400 wrote:Where did you get the interface from? We need to know the hardware type before being able to give much info other than general advice.

Can you connect with the flashtool? http://pcmhacking.net/forums/viewtopic.php?f=3&t=82
bmak wrote:The interface is from a member here TAZZI

I tried the flashtool and I select the car, click connect and it gets no response.
Just to clarify the unit was 100% working as tested by myself on a VT,VX,VY ecus. Also in VY car using both tunerpro and efilive.
Uses a genuine FTDI chip, direct from the source and was no issues installing on a XP,vista, W7 and W8 devices here.

We are currently troubleshooting the issue :thumbup:
Your Local Aussie Reverse Engineer
Contact for Software/Hardware development and Reverse Engineering
Site:https://www.envyouscustoms.com
Mob:+61406 140 726
Image
User avatar
Tazzi
Posts: 3422
Joined: Thu May 17, 2012 8:53 pm
cars: VE SS Ute
Location: WA
Contact:

Re: Vs commodore wont connect to tunerpro

Post by Tazzi »

VS ecu on bench testing. Im able to pull frames no trouble. :thumbup:
I am however having alot of difficulty getting the tunerpro definiton files to sync up properly.
VSFramesonBench.PNG
VSFramesonBench.PNG (26.42 KiB) Viewed 6716 times

*Edit: Ohh.. found where its going wrong!
Using Jayme's VS V6 v1.07 file, the "wait for silence" was a bit too high, the ecu was responding way early causing tunerpro to miss some of the data.

Attached is the version Im using which seems to work fine on a VS V6 ecu. Lowered the silence time to 40ms.

*Edit 2 -reuploaded new VS V6 file with 50ms silence
50ms seems to be optimum
At 60 I get plenty of missed frames and errors.
At 40 I get a couple
And ad 50 seems to be a solid read!
Attachments
Vs V6 engine and trans 1.08-tp5 - Credit to Jayme.adx
(101.99 KiB) Downloaded 318 times
Your Local Aussie Reverse Engineer
Contact for Software/Hardware development and Reverse Engineering
Site:https://www.envyouscustoms.com
Mob:+61406 140 726
Image
User avatar
Tazzi
Posts: 3422
Joined: Thu May 17, 2012 8:53 pm
cars: VE SS Ute
Location: WA
Contact:

Re: Vs commodore wont connect to tunerpro

Post by Tazzi »

Yep, same goes for all the other VS files. the Silence delay at 60ms is too long. Its error galore!
Pushing it down to 45-50 makes a MASSIVE improvement on connecting first time reliably.
Your Local Aussie Reverse Engineer
Contact for Software/Hardware development and Reverse Engineering
Site:https://www.envyouscustoms.com
Mob:+61406 140 726
Image
User avatar
antus
Site Admin
Posts: 8237
Joined: Sat Feb 28, 2009 8:34 pm
cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B
Contact:

Re: Vs commodore wont connect to tunerpro

Post by antus »

Awesome, well spotted!
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
bmak
Posts: 20
Joined: Mon Feb 09, 2015 7:36 pm
cars: commodore

Re: Vs commodore wont connect to tunerpro

Post by bmak »

Still no luck here.

Just to rule out the fact I'm trying to connect to a Toyota i went with a fresh install on a netbook and hooked it up to a VS V6 Ecotec.

Any suggestions for testing would be appreciated
User avatar
VL400
Posts: 4991
Joined: Sun Mar 01, 2009 2:54 pm
cars: VL Calais and Toyota Landcruiser. Plus some toys :)
Location: Perth, WA
Contact:

Re: Vs commodore wont connect to tunerpro

Post by VL400 »

Tazzi wrote:Yep, same goes for all the other VS files. the Silence delay at 60ms is too long. Its error galore!
Pushing it down to 45-50 makes a MASSIVE improvement on connecting first time reliably.
Looking at the ADX the reason is its a 60ms silence length with a 50ms timeout ..... pretty hard to find 60ms when only waiting 50ms :lol:

The usual default/recommended is 15ms silence length with a 400ms timeout. This works for everything including chatter happy VT and later.
User avatar
Jayme
Posts: 2585
Joined: Sun Mar 01, 2009 8:59 am
Location: North Coast, NSW

Re: Vs commodore wont connect to tunerpro

Post by Jayme »

Haha oops my bad
User avatar
Tazzi
Posts: 3422
Joined: Thu May 17, 2012 8:53 pm
cars: VE SS Ute
Location: WA
Contact:

Re: Vs commodore wont connect to tunerpro

Post by Tazzi »

VL400 wrote:
Tazzi wrote:Yep, same goes for all the other VS files. the Silence delay at 60ms is too long. Its error galore!
Pushing it down to 45-50 makes a MASSIVE improvement on connecting first time reliably.
Looking at the ADX the reason is its a 60ms silence length with a 50ms timeout ..... pretty hard to find 60ms when only waiting 50ms :lol:

The usual default/recommended is 15ms silence length with a 400ms timeout. This works for everything including chatter happy VT and later.
Ahhhh.. that could be it then! :thumbup:
Your Local Aussie Reverse Engineer
Contact for Software/Hardware development and Reverse Engineering
Site:https://www.envyouscustoms.com
Mob:+61406 140 726
Image
bmak
Posts: 20
Joined: Mon Feb 09, 2015 7:36 pm
cars: commodore

Re: Vs commodore wont connect to tunerpro

Post by bmak »

A replacement cable has solved my issue.
User avatar
j_ds_au
Posts: 384
Joined: Sun Jan 25, 2015 4:21 pm
Location: Sydney

Re: Vs commodore wont connect to tunerpro

Post by j_ds_au »

VL400 wrote: Looking at the ADX the reason is its a 60ms silence length with a 50ms timeout ..... pretty hard to find 60ms when only waiting 50ms :lol:

The usual default/recommended is 15ms silence length with a 400ms timeout. This works for everything including chatter happy VT and later.
Wow! Good catch! I can see this now in the Listen For Silence command definition of the ADX.

Funny thing is, I only get the occasional data error on my VS with these ADX files, it takes about 7 minutes to clock up 20 errors. No problems syncing at start up, either. I'll have to try an increased timeout to see if all the data errors go away, that would be sweet!

Joe.
Post Reply