Thankyou! Its getting there slowly.Cincinnatus wrote:Impressive work Tazzi!
I need to fix up the 'extended addressing' since Im doing a bit of a hack work around.
Extended address is when we get things like this:
101 FE 01 3E
Where the first byte FE, is our extended addressing byte. Basically used as a global "Everyone look!".
The length byte is then next 01, and finally data byte of 3E.
The way OBDX is currently designed, when I send the data... what gets sent to the CAN line is the following:
101 02 FE 3E
The OBDX tool does not know that its an extended address, so it treats it as a data byte.
The way I kinda beat this was temporarily disabling formatting on the tool.. sending the frame, then re-enabling the formatting. It really shouldn't be done like that, hence a smarter solution needs to be created.
The best way I can see currently, is to have a setting in the tool which when enabled, checks the first byte of the data, and if it is 0xFE (or whatever assigned byte), it then uses that as the extended address.
Technically, there should never be an instantance where FE is the first byte, and we want it in our data frames.. since there is no 'FE' mode... so it should not hurting implementing that method
