As title says. Should or could it be in the xml?
Printable View
As title says. Should or could it be in the xml?
The VN/VP PCM's data stream is very, very basic (and slow at 160 baud). It only contains the PIDs that are defined for it - as far as I can tell.Quote:
Originally Posted by limited cv8r
Regards
Paul
Here is a screenshot from tunerpro supposedly showing a spark pid. Can the pid data/offsets etc be entered into V4 to see if it works and what would need to be entered into the software?
The offset for the spark advance defined by that app is byte 32. The size of each frame returned by the VN/VP controller is only 20 bytes long. So no PIDs can be defined after byte number 20.
That is unless I got it wrong and the frame is longer than 20 bytes. To check that, turn on display serial I/O (View->Serial I/O) and then click the "Display ALDL Chatter (Ctrl+L)" toolbar icon. However, I'm not 100% sure if that works for 160 baud controllers or not and I don't have a spare VN/VP controller lying around to test it on.
Anyway if that does show the raw data frames, can you post up that text data and I'll see if it really doe shave more than 20 bytes per frame.
If it does you'd need to change the "Frame Length" setting in the "Dummy Request" entry in the vehicle definition to match the actual frame length. Then you can add in the spark PID at offset 32 - assuming the actual frame length is at least 32 bytes long
Regards
Paul