Just get a vag com cable, that should work. The cable works fine its just that the software isnt really designed full with the vstrom. I have not played around with it in a while but interested in getting it to work with the Suzuki's sds software. There are advanced functions that allow for adjustments of throttle bodies. If you are reading this post then its most likely why you are here.
can anyone expand on the meanings of the bits in the statusOfDTC byte?
this byte follows each DTC in response to the ReadDiagnosticTroubleCodesByStatus service, and the notes in ECUeditor indicate:
' 0x01 bit0 = pending fault present
' bit1 = pending fault state
' bit2 = test running
' bit3 = test inhibit
' bit4 = test readiness
' 0x20 bit5 = DTC validated and stored in non volatile memory
' 0x40 bit6 = validated fault preset at time of request
' 0x80 bit7 = validated fault has been present during this driving cycle
But I'd like to know the meanings of these descriptions in more detail. For example, what is the difference between bit0 and bit1 (the descriptions look almost the same to me)?
And what do bits 2,3,4 mean? (i.e. what does test mean?)
If a particular DTC appears more than once in the response, what does that mean? (each time with a different status value) ... for example, in one response I got three successive IAPS codes:
01 05 A2
01 05 E1
01 05 A0
Unfortunately the ISO14230/KWP2000 standards are of no help here, as they simply state that "Format and length of this parameter are vehicle manufacturer specific."
any help muchly appreciated,
cheers,
Mark
-- Edited by bozo on Saturday 28th of January 2012 04:16:35 AM
Kashima, Can you tell us the exact commands you use with the ELM to estabilish a connection ? This would help people develop more sds tools, maybe on Android phones too.
-- Edited by Manzo on Thursday 14th of June 2012 06:47:33 PM
Some of you may find also this interesting - not tested yet so may not work as its only based on reading the disassembled code. 80 12 F1 02 21 08 monitor sensor data 80 12 F1 03 14 00 00 clear dtc 80 12 F1 04 18 00 00 00 dtc monitoring 80 12 F1 01 3e keep alive not all below mentioned are tested... 80 12 F1 06 a5 01 80 00 00 00 set pair on 80 12 F1 06 a5 01 00 00 00 00 set pair off 80 12 F1 06 a5 02 not applicable 80 12 F1 06 a5 03 80 00 00 CKS set excva on 80 12 F1 06 a5 03 00 00 00 CKS set excva off 80 12 F1 06 a5 02 not applicable 80 12 F1 06 a5 05 28 RPM 00 CKS set ics rpm value, value needs to be between 54 and A0, rpm is =(HEX2DEC(RPM)*2^5)/2.56 80 12 F1 06 a5 06 80 00 00 CKS set fan on 80 12 F1 06 a5 06 00 00 00 CKS set fan off 80 12 F1 06 a5 07 80 00 00 CKS set evap on 80 12 F1 06 a5 07 00 00 00 CKS set evap off
Hi,
I´m about to program some kind of SDS-tool in VB. Monitoring of sensor data works fine. Logging as well.
I establish communication starting with wake up pattern (WuP) followed by
byte
1
2
3
4
5
wert
81
12
F1
81
5
Then I loop request to ECU by a timer of 150 ms
ptr
0
1
2
3
4
5
6
Len
1
2
Value
80
12
F1
2
21
8
CS
And read response with sensor values. That works fine. I can read the desired idle speed (seams to be that value) and the ISC-valve position.
Now I want to implement more SDS functionality. For example test of ISC-Valve by setting desired idle speed to different values temporarily.
I tried to start with the WuP followed again by
byte
1
2
3
4
5
wert
81
12
F1
81
5
Then I looped according to PetriKs discovery
byte
1
2
3
4
5
6
7
8
9
wert
80
12
F1
6
A5
5
28
RPM_Set
0
CS
CS is greater than &HFF!
With &H68 for RPM_Set (should be 1300 rpm), but idle stand at 1150 rpm. Dont have a clue....
In ECU-Editor data are sent by "txbyte" declared as Byte. But what if checksum is greater than &HFF? That´s the case with PAIR ON funtionality as well: cks is &H2AF. I suppose cks is not sent copletely due to declaration as byte...?
could somebody give me a hint please?
with kind regards, Torsten.
-- Edited by torsten on Thursday 16th of August 2012 08:00:06 PM
-- Edited by torsten on Friday 17th of August 2012 08:29:50 AM
I can't tell if this is old news or not so I'll throw it out on the off chance that it is of interest.
I've been studying the pds file saved by the SDS software. It seems like there's a good chance that the saved values are the same as in the K-line data stream. The relationship between those values and engineering units is as follows:
RPM = Value*100/255 Throttle position (°) = Value*125/255 Manifold pressure = (Value*5 - 153)*133/4/255 Temperature (C) = Value*160/255 - 30 Temperature (F) = Value*288/255 - 22 Voltage = Value*20/255 Secondary throttle position (%) = Value*100/255 EXCVA sensor = Value*100/255
Edit : I found the problem : an option in the bios ( serial ) must be active to make the software working on windows 7 and windows XP.
-- Edited by songotag on Wednesday 1st of August 2012 08:51:32 PM
What isthis option?
The option is " use serial " on my laptop. It's a HP 6710B, an there's no physical serial port on it. But if i whant he kashima's software working, i must anable this option.
I' interesting of programming a pic to check the sensors values ( via the ODB connector ) of the strom to display on a small LCD screen.. but i don't know how to do...
I am actually playing with an ELM327 usb dongle to communicate with the ECU through the SDS connector.
I wrote a sw in C-language to interface with the ELM327.
When the engine is not started, I can have an updated response frame from the ECU of about 5Hz.
When the engine is on, the update rate is between 4~5Hz with the engine idle.
When I turn the throttle, I have some kind of lag before receiving the datas.
I am wondering if this is due to the ECU priorizing the engine task or a problem with the voltage level of Vbat and K-line which are higher.
can anyone expand on the meanings of the bits in the statusOfDTC byte?
this byte follows each DTC in response to the ReadDiagnosticTroubleCodesByStatus service, and the notes in ECUeditor indicate:
' 0x01 bit0 = pending fault present
' bit1 = pending fault state
' bit2 = test running
' bit3 = test inhibit
' bit4 = test readiness
' 0x20 bit5 = DTC validated and stored in non volatile memory
' 0x40 bit6 = validated fault preset at time of request
' 0x80 bit7 = validated fault has been present during this driving cycle
But I'd like to know the meanings of these descriptions in more detail. For example, what is the difference between bit0 and bit1 (the descriptions look almost the same to me)?
And what do bits 2,3,4 mean? (i.e. what does test mean?)
If a particular DTC appears more than once in the response, what does that mean? (each time with a different status value) ... for example, in one response I got three successive IAPS codes:
01 05 A2
01 05 E1
01 05 A0
Unfortunately the ISO14230/KWP2000 standards are of no help here, as they simply state that "Format and length of this parameter are vehicle manufacturer specific."
any help muchly appreciated,
cheers,
Mark
HelloBozo
I planto makean OBDonthe dashboardof myVSTROM650.I sawon another forumthatyou madean OBDthat reads informationdirectly from theOBDconnector.Iswhat you cangive meinformation onyourprojects?
I would like tomake anOBDplayback to display thegear engaged,consumption,defectsetc ...
It's not difficult to add temperature sensor... the problem is to synchronise the data between arduino nano and ECU when you add some stuff int the program.
the electronique interface is in this thread, it's the shematic with two transistor and some resistances...
-- Edited by songotag on Saturday 13th of June 2015 03:25:00 PM
-- Edited by songotag on Saturday 13th of June 2015 03:25:31 PM
Is anybody has the formulas for SPEED, RPM etc for VSTROM 650 k8, I tested all the formulas in this forum and there is that good engine temperature, ECT; TPS and BAT formulas for my bike.
Formulas OK :
ECT = k_inByte * 160 / 255; // BillV,
TPS = (k_inByte * 125 / 255); // petrik
BAT = k_inByte * 20.0 / 255;
Probably Kashima or Petrik ????
thank-you
-- Edited by songotag on Monday 6th of June 2016 10:17:28 AM
Thanks. I am using PuTTY (similar to Hyperterminal) and using your commands on OBD Link SX (STN chip). It works like a charm. But I have an iCar VGate device also (ELM 327 device). It doesn't work. On hitting command for show DTC (18 00 FF 00) it shows NO DATA. How is it possible? There is an app called SZ Viewer which I used with the iCar VGate device and it works. But your commands don't. Are there any more commands to be hit to configure the device? Are there any AT commands like AT SW or AT ST (timeout) etc that needs to be put before your commands?
>ATWM8012F1013E (set a special keep alive message)
OK
>ATSH8112F1 (set a header for first negotiaton)
OK
>ATFI (initialize bus)
BUS INIT: OK
>ATSH8012F1 (set a header for data transaction)
OK
>1A9A (Read ECU ID)
5A 9A 33 32 39 32 30 2D 30 .....
>2108 (Read Data by Local ID)
61 08 0F 02 01 A0 02 02 A0 .....
>82 (Close a connection)
C2
>ATPC (ELM Protocl Close)
OK
-- Edited by kashima on Friday 15th of June 2012 07:50:02 AM
Thanks. I am using PuTTY (similar to Hyperterminal) and using your commands on OBD Link SX (STN chip). It works like a charm. But I have an iCar VGate device also (ELM 327 device). It doesn't work. On hitting command for show DTC (18 00 FF 00) it shows NO DATA. How is it possible? There is an app called SZ Viewer which I used with the iCar VGate device and it works. But your commands don't. Are there any more commands to be hit to configure the device? Are there any AT commands like AT SW or AT ST (timeout) etc that needs to be put before your commands?
Hi, is it possible to see all sensors for certain bike, or we need to fuzzy them?
Im trying to resolve issue with my bike, at 2000-4000rpm there is fuluctistion in revs.
So i need to find out what sensor does that!
There is new iridium spark inside, checked, all sensors by the book. Revs goes up&down even on just front or rear cilinder.
Gas thank is OK and the fuel pump also.