The "Align to header" thing was indeed not implemented at all. I added support for that for the next version. As for the listen packet, I've looked at the code and you're absolutely right. This will require a bit more work but I guess I could eventually get it done as well.
As for the most important part, the crash, I fixed one thing but I feel like there is more going on. It crashes in the XDL stuff. I will have to investigate / test some more.
Just pushed version 0.61 to Play (should show up in a few hours).
Crash while starting to data log was in XDL code when the ADX file had at least one listen packet that "process data" wasn't checked. This should be fixed and you should be able to datalog now Jayme. Let me know if you still have any issue. There was a few other random crashes reported by other users that should be fixed as well in this version.
I haven't got the "align to header" thing in this release as I had a few issues with it, still need more work.
On another note, the NVRAM ECU from antus should be here sometime next week
installed 0.61.... tried it again, still crashed. I sent a crash report. I assume that goes to you ?
it does create the csv and XDL, it just crashes before it puts any data into them.
could it have anyhting to do with having the checksum validaiton disabled? there is no checksum on my data packets
Yeah, that's some sort of progress. It was crashing in the writing headers function, now it's crashing while trying to write the first row of data
I'm a bit confused by the multiple listen packets now. I guess the app should read data for all listen packets and once it got response for all, write a row of data in the XDL file. I will have to rethink some of the code... geez
yeah its pretty messy adx..... it has to send and receive some data to set up the cable im using, then send some more to set up the dynamic packets in the PCM, then send and receive 3 different packets to get the actual data. you have done a great job to get the app as good as it is
0.62 is on Play with the data logging happening only at the end of the monitor macro. I'm thinking this might fix the crash as well. Again, it will brings us closer but there might be more to it. I wish I had the hardware to test, it would makes things easier but oh well
sorry to report 0.62 still crashes. sent a crash report. it would be good to have the hardware but an avt is like $200 cable I might look into replicating the problem without the AVT by making a simple program to send the correct responses to the ADX requests and do a basic emulation of the cable and pcm responses. then you can have the next best thing to real hardware to test on
Crap, same exact stacktrace for the crash too... That's annoying Have you taken a look inside the CSV file, does it log a bit of something or it crashes right away ?
I have a couple idea of what could be going on but I'm thinking I should have added some debugging in this version
yeah I opened the CSV. I get column headings and no data. the XDL file is a few KB, I assume its the header stuff but ill open it and have a squiz at that too.
not sure if im dreaming, but i think it took a bit longer before dropping out to the crash report this time.
ok so I narrowed the problem down. the crash happens when there is more than one data frame in the main logging macro.
right now I have 3 different data packets:
DPID FE TX, DPID FE RX
DPID FD TX, DPID FD RX
DPID FC TX, DPID FC RX
if I remove any 2 of them and leave only one packet in my main log macro, I can datalog with no crash.
I might look into replicating the problem without the AVT by making a simple program to send the correct responses to the ADX requests and do a basic emulation of the cable and pcm responses. then you can have the next best thing to real hardware to test on