Allpro development

They go by many names, P01, P59, VPW, '0411 etc . Circa 1999 to 2006. All VPW OBD2 PCMs.
Site Admin
User avatar
Posts: 5629
Joined: Sat Feb 28, 2009 8:34 pm

Re: obdpro

Postby antus » Tue Jun 07, 2016 10:28 am

Obddiag has taken my patch and updated the official source to not send the test packet when J1850 is explicitly set. That solves one problem.

"update explicitly set protocol handling"
https://github.com/ObdDiag-Net/allpro/t ... dapter/obd
Have you read the FAQ? For lots of information and links to significant threads see here: viewtopic.php?f=7&t=1396

User avatar
Posts: 9622
Joined: Sat Feb 28, 2009 9:05 pm
Location: Tenambit, NSW

Re: obdpro

Postby Holden202T » Tue Jun 07, 2016 12:21 pm

good to see your getting some love back :)

Site Admin
User avatar
Posts: 5629
Joined: Sat Feb 28, 2009 8:34 pm

Re: obdpro

Postby antus » Fri Jun 24, 2016 12:01 am

Its been a while since I looked at this, but tonight I tried various different ways of making the concept of variable speed vpw fit in to the object orientated code base of the obdpro. After several false starts and hours trying to figure out why I could not set my vpw speed flag to 1 (because I had appended the definition of the setting to the end of the list, not the end of the booleans at the top!) things came together.

I have extended the protocol adapter class to support setSpeed (which does nothing for the other adapters). But then the VPW adapter calls a function which tests if 4x is turned on or not and sets all the timings appropriately.

Heres the test.. This shows the code in the protocol function which calls setSpeed, the terminal window I was testing from (and some bool setting debugging). Essentially ive set VPW, displayed the protocol name, set V1 for vpw high speed, displayed the protocol again which now includes '4X' on the end, then sent a packet which is logged at the protocol analyser showing that it was indeed valid VPW 4x that came out of it. Win!
Attachments
vpw4x test.png
Have you read the FAQ? For lots of information and links to significant threads see here: viewtopic.php?f=7&t=1396

Site Admin
User avatar
Posts: 5629
Joined: Sat Feb 28, 2009 8:34 pm

Re: obdpro

Postby antus » Fri Jun 24, 2016 2:21 pm

New command ATV for toggling VPW high speed, and ATR for toggling raw payload support. And buffer size changes which gets me up to 128 byte packets. Not ideal, but good enough to get started.

NO DATA means no response from the pcm. Thats fine, there is nothing on the data bus, Im just passively reading the output with the logic analyser.

Code: Select all
ATZ
OK
ELM327 v1.4
>AT#1
Copyright (c) 2009-2016 ObdDiag.Net, 2016 PCMHacking.net
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>ATSP2
OK
>ATDP
SAE J1850 VPW
>6C10F100112233445566778899AABBCCDDEEFF (this outputs at 1x, and with an incorrect 3 bytes header inserted at the front by the hardware)
NO DATA
>ATR1 (sets raw payload, hardware no longer adds the 3 byte header)
OK
>6C10F100112233445566778899AABBCCDDEEFF (this outputs as is, at 1X)
NO DATA
>ATV1 (this sets VPW 4X)
OK
>6C10F100112233445566778899AABBCCDDEEFF (this outputs as is, at 4X)
NO DATA
Have you read the FAQ? For lots of information and links to significant threads see here: viewtopic.php?f=7&t=1396

Site Admin
User avatar
Posts: 5629
Joined: Sat Feb 28, 2009 8:34 pm

Re: obdpro

Postby antus » Wed Jan 02, 2019 10:54 pm

Just to close this off, this work was successful, and this and large packet support ended up in the allpro, which can now flash with pcmhammer :)
Have you read the FAQ? For lots of information and links to significant threads see here: viewtopic.php?f=7&t=1396

Previous

Return to GM LS1 512Kbyte and 1Mbyte

Who is online

Users browsing this forum: brandonwh64 and 1 guest