Coming Soon: new obd-ii datastream tool

[Stokes1114]

0D is 8192.
I'm in for testing for ya Steveo! I've got some 0411 vehicles and various interfaces.

[ras"86]

I wish I could be helpful,sounds like a great project.

[steveo]

right now im a bit stuck on how the user interface is going to be as i'm trying to envision that part before i jump in and start writing it. 'really easy to use' is something that other software already does, so honestly it might be more for advanced users..

[ralmo94]

right now im a bit stuck on how the user interface is going to be as i'm trying to envision that part before i jump in and start writing it. 'really easy to use' is something that other software already does, so honestly it might be more for advanced users..

Would be really cool if it has a dark ui. Bright white screens suck at night.

[steveo]

i've done dark UIs with some of my other software. QT makes it really easy to theme stuff, actually you can write style sheets with it just like a website.

[steveo]

still putting a few hours a day into it but no UI yet

i do have it working so you can build complex structures based on the programs. each program runs in its own thread and has an input and output, so they just need to be chained together. multiple programs operating on the same datastream works too, all the incoming data is replicated, so they can react independently if they were written for it

still need to figure out how a program will generate its controls and stuff like that. i have some good ideas for that but im trying not to make it a 9999 hour project

[steveo]

still working on it, here's a more complex example of the language, this implements obdxpro dvi protocol send/recv from an arbitrary stream:

#--------------------------------------------

#SET $COMMAND AND THIS SUBROUTINE SENDS/GETS REPLY AS $DVI_REPLY - WITH DATA
#ONLY.).  OMIT THE CHECKSUM IN THE $COMMAND INPUT. THE SECOND BYTE(LENGTH) CAN
#BE ANYTHING (00?) AS THIS ROUTINE CORRECTS IT.

*SEND_DVI
SIZE %PKTSIZE $COMMAND
DEC %PKTSIZE
DEC %PKTSIZE
SET $COMMAND[1-1] $PKTSIZE
CHECKSUM_GENERATE %COMMAND "DVI"
TX $COMMAND # .. send
CALL *RECV_DVI
IF FALSE FAIL
ADD %COMMAND[0-0] 10 # reply will have command+10
COMPARE $DVI_REPLY[0-0] | $COMMAND[0-0]
IF = TRUE
IF = RETURN
COMPARE $DVI_REPLY[0-0] | 7F
IF = GOTO *REPLY_ERROR
PRINT "UNKNOWN DVI REPLY: " /HEX $DVI_REPLY
FAIL

*RECV_DVI
RX %DVI_REPLY[2] # GET TWO BYTE HEADER
IF FALSE FALSE
IF FALSE RETURN
SET %_LENGTH_IN $DVI_REPLY[1-1] # SECOND BYTE IS REPLY.
INC %_LENGTH_IN  # +1
RX %_DATA_IN[$_LENGTH_IN]
APPEND %DVI_REPLY $_DATA_IN
CHECKSUM_TEST "DVI" | $DVI_REPLY
IF FALSE FAIL "CHECKSUM ERROR IN REPLY FROM INTERFACE"
PRINT "DVI RX PKT: " /HEX $DVI_REPLY
TRUE
RETURN

*REPLY_ERROR
PRINT "DVI ERROR OCCURRED FOR COMMAND " /HEX $DVI_REPLY[2-2] /TEXT " ERR_CODE " /HEX $DVI_REPLY[3-3]
FAIL "FATAL DVI PROTOCOL ERROR"