Closed anthonyhbest closed 1 year ago
%TEMP%\j1939840.log (or any j1939*.log file that was modified at about the time you made this run that crashed) will have the important information for us to understand what crashed. Can you zip those and send them to j1939-84@soliddesign.net ?
The ASC file would let us try to reproduce it, but for this type of error, it likely will not help.
It may be that your truck produces more traffic than the other test trucks. I have increased the amount of memory allocated for this (from 128 MB to 256 MB) for the next release.
Files sent as requested.
Bob Has seen similar errors including the pop-up … cycling the key … hit the App with a hammer.
We expect this to be related to the memory configuration. We changed the setting from 128MB to 256 MB for the 3.1.8 release.
Still having the issue with v3.1.8 and confirmed across multiple vehicles.
Addressd with release 3.1.9.
Have not seen the issue return in v3.1.9
Reported as resolved in 3.1.9
Tool proceeds until 1.26.2.c then after "reading bus for x seconds" gets to 0, tool hangs and will not proceed.
Starting the engine will trigger the tool to move on, but then issues the following error message:
Tool then hangs again at "reading bus for 0 seconds" in part 2.17.1.c
Keying off triggers the tool to move on but issues numerous failures.
Log file:
j1939-84-gc.txt