OBDX Development - Developer Tools and Suggestions

[Gampy]

J2534 client initializing...
Initializing J2534 Device
J2534 client: Device initialization fail.
Battery Voltage is: 11.997
Failed to set filter, J2534 error: Error ERR_INVALID_FILTER_ID
Failed to set parameters

Is what I get when trying on the MasterTech II
. . ISO15765
. . ISO15765_500000
. . NONE

Am I missing something ??

I did place the ecm_ISO16765.xml in the xml folder as well.

UP 22.02

-Enjoy

[acln99]

kur4o - I don't know IDA and probably toooo old to learn.

Can you send me the disassembled NGC3 - I'm curious what it looks like - never saw a complete one - just snippets.

This is NGC3 log request VIN , read 9e-b0 ?? , seed/key , write 9e-b0 ?? , read 9e-b0 again

ngc3.txt

(675 Bytes) Downloaded 51 times

[kur4o]

Gampy, put the config file in Logger/j2534Profiles folder.
Before connecting click Load button, [above connect/disconnect button], And select the xml file, Than connect.

This error happens when you try to connect without setting flow control filters.

acln99,
I will dig out the ngc3 diss, but will need some time to find it.

[Gampy]

Loading J2534 settings from file: UniversalPatcher\UniversalPatcher\Logger\J2534Profiles\ecm_ISO16765.xml
[OK]
J2534 client initializing...
Initializing J2534 Device
J2534 client: Device initialization complete.
Battery Voltage is: 11.929
Adding filters:
Type:FLOW_CONTROL_FILTER,Name:23-02-04-10-13-46
Mask:FFFFFFFF,RxStatus:NONE,TxFlags:NONE
Pattern:000007E8,RxStatus:NONE,TxFlags:NONE
FlowControl:000007E0,RxStatus:NONE,TxFlags:NONE

Type:FLOW_CONTROL_FILTER,Name:23-02-04-10-13-46
Mask:FFFFFFFF,RxStatus:NONE,TxFlags:NONE
Pattern:000007E0,RxStatus:NONE,TxFlags:NONE
FlowControl:000007E8,RxStatus:NONE,TxFlags:NONE


Device initialization complete.

Ok, it connects, I get nothing in the log ...

Shouldn't it be logging idle chatter at this point ??

-Enjoy

[Tazzi]

Loading J2534 settings from file: UniversalPatcher\UniversalPatcher\Logger\J2534Profiles\ecm_ISO16765.xml
[OK]
J2534 client initializing...
Initializing J2534 Device
J2534 client: Device initialization complete.
Battery Voltage is: 11.929
Adding filters:
Type:FLOW_CONTROL_FILTER,Name:23-02-04-10-13-46
Mask:FFFFFFFF,RxStatus:NONE,TxFlags:NONE
Pattern:000007E8,RxStatus:NONE,TxFlags:NONE
FlowControl:000007E0,RxStatus:NONE,TxFlags:NONE

Type:FLOW_CONTROL_FILTER,Name:23-02-04-10-13-46
Mask:FFFFFFFF,RxStatus:NONE,TxFlags:NONE
Pattern:000007E0,RxStatus:NONE,TxFlags:NONE
FlowControl:000007E8,RxStatus:NONE,TxFlags:NONE


Device initialization complete.

Ok, it connects, I get nothing in the log ...

Shouldn't it be logging idle chatter at this point ??

-Enjoy

Set the "Mask" to 00000000, this should allow all frames through.

[Gampy]

Loading J2534 settings from file: UniversalPatcher\UniversalPatcher\Logger\J2534Profiles\ecm_ISO16765.xml
[OK]
J2534 client initializing...
Initializing J2534 Device
J2534 client: Device initialization complete.
Battery Voltage is: 11.967
Adding filters:
Type:FLOW_CONTROL_FILTER,Name:23-02-04-10-13-46
Mask:00000000,RxStatus:NONE,TxFlags:NONE
Pattern:000007E8,RxStatus:NONE,TxFlags:NONE
FlowControl:000007E0,RxStatus:NONE,TxFlags:NONE

Type:FLOW_CONTROL_FILTER,Name:23-02-04-10-13-46
Mask:00000000,RxStatus:NONE,TxFlags:NONE
Pattern:000007E0,RxStatus:NONE,TxFlags:NONE
FlowControl:000007E8,RxStatus:NONE,TxFlags:NONE


Device initialization complete.

Thank you, done, still nothing ...

-Enjoy

[Tazzi]

FDCAN is going to be a shitstorm.. at least.. possibly in the future.

I was reading in the official SAE document for J2534 with FD CAN that larger blocks then 4095 is now possible. In my head, I figured it would be maybe.. 8192 bytes... nope... absolutely not... its 32000+ bytes more!!!

As seen in the blurb below, technically its a 4byte value used for the length, so.. theoretically.. the max amount of bytes that could be sent is 0xFFFFFFFF. Thats an integer value of 4,294,967,295bytes. If an ECU had a large enough RAM buffer, technically an entire flash could be uploaded in one chunk

The SAE standard has limited it to a value they deem acceptable, but 32000+ is still MUCH larger then what the OBDX GT/FT can store. Id be surprised if even 1 quarter of scantools have implemented that requirement to be honest. To be 'technically' SAE compliant, we will have to be using a processor with larger ram to fit an entire 32k+ frame. At this time, Im pretty certain none of the current FD CAN GM ECUs are using larger then the standard 4k blocks.

With that all said, it doesnt stop manufactures from using bigger blocks in the future so we will have to be prepared for that.

J2534fdcan.PNG (112.97 KiB) Viewed 612 times

[Tazzi]

Loading J2534 settings from file: UniversalPatcher\UniversalPatcher\Logger\J2534Profiles\ecm_ISO16765.xml
[OK]
J2534 client initializing...
Initializing J2534 Device
J2534 client: Device initialization complete.
Battery Voltage is: 11.967
Adding filters:
Type:FLOW_CONTROL_FILTER,Name:23-02-04-10-13-46
Mask:00000000,RxStatus:NONE,TxFlags:NONE
Pattern:000007E8,RxStatus:NONE,TxFlags:NONE
FlowControl:000007E0,RxStatus:NONE,TxFlags:NONE

Type:FLOW_CONTROL_FILTER,Name:23-02-04-10-13-46
Mask:00000000,RxStatus:NONE,TxFlags:NONE
Pattern:000007E0,RxStatus:NONE,TxFlags:NONE
FlowControl:000007E8,RxStatus:NONE,TxFlags:NONE


Device initialization complete.

Thank you, done, still nothing ...

-Enjoy

What J2534 tool are you using?

[Gampy]

Genuine Bosch Mastertech II

4,294,967,295 - Now that's a packet (frame).

-Enjoy

[antus]

@tazzi I dont read that the same as you describe. I think the length is the size of the total payload across multiple frames, and it is sent in smaller packets, segmented. So rather than the application layer knowing what each segement is and reassembling it in the application part of the code, it can be done by the can layer, but you still don't need to handle packets 32kb in size (and that piece of doc doesn't specify the maximum segment size, which may still be different between different interfaces similar to what we see on some current gen interfaces and J2534). So it'd be something like first frame says 128Kb payload. Second frame has a 4k payload, third frame has a 4k payload, and so on and so on, until the whole 128Kb is transmitted. Then the can layer in the pcm could reassemble it and provide the payload to the app as a single piece of data.