FAQFAQ SearchSearch MemberlistMemberlist UsergroupsUsergroups RegisterRegister
ProfileProfile Log in to check your private messagesLog in to check your private messages Log inLog in

 
Internal Format of XDL files

 
Post new topic   Reply to topic    TunerPro User Forum Forum Index -> TunerPro Discussion
 
razorx



Joined: 24 Mar 2014
Posts: 5

PostPosted: Mon Mar 24, 2014 10:24 am    Post subject: Internal Format of XDL files Reply with quote

Hi,

I am working on a micro-controller board to write logs to a SD/MMC card.
More Easy than taking your laptop with you. Wink

It has already built into my car and captures the ECM/ECU data. I only need to have the internal format of the XDL files, so I could make the micro-controller write down the file in XDL format.

Any information on this would be highly appreciated.
Back to top
View user's profile Send private message
 

 
ReadyXB



Joined: 29 May 2014
Posts: 8

PostPosted: Wed Jun 18, 2014 6:29 pm    Post subject: Reply with quote

Did you figure out the format? I have decoded most.
Back to top
View user's profile Send private message
 

 
razorx



Joined: 24 Mar 2014
Posts: 5

PostPosted: Thu Jun 19, 2014 11:28 am    Post subject: Reply with quote

ReadyXB wrote:
Did you figure out the format? I have decoded most.


Wow!

Would you like to share this? This is very handy for anyone setting up a microcontroller based logging system.


.I haven't come any further with this, I am very busy with a semi automatic VE map calculator sheet based on TunerPro's history tables. I am convinced that I can make the same handy sheet for the TCV duty cyle pilot control maps. Saves a lot of time.

Driving a Volvo V70R. Motronic 4.4. Wink
Back to top
View user's profile Send private message
 

 
ReadyXB



Joined: 29 May 2014
Posts: 8

PostPosted: Thu Jun 19, 2014 1:32 pm    Post subject: Reply with quote

razorx wrote:

Wow!

Would you like to share this? This is very handy for anyone setting up a microcontroller based logging system.


I agree. I have a PM out to Mangus, but he has not yet replied, even though he seems to be replying to forum posts. I want to a) confirm a few unknowns, and b) be sure he is ok with the details being posted. I imagine the only concern would if the .XDL format changes in future Tunerpro revisions, it might breaking outside software.
Back to top
View user's profile Send private message
 

 
Mangus
TunerPro Author


Joined: 19 Mar 2003
Posts: 1789

PostPosted: Fri Jun 20, 2014 11:59 am    Post subject: Reply with quote

ReadyXB wrote:
I imagine the only concern would if the .XDL format changes in future Tunerpro revisions, it might breaking outside software.


Exactly correct. I can share the details with you, but I'm about 90% of the way done with replacing the entire logging system with a new, custom database-like implementation. Due to my own time constraints (I'm sure everyone has noticed that releases are further between and less feature-rich), I can't tell you exactly when the replacement will roll out, but it will happen.
_________________
***************************************
TunerPro Author
1989 Trans Am
Back to top
View user's profile Send private message
 

 
razorx



Joined: 24 Mar 2014
Posts: 5

PostPosted: Fri Jun 20, 2014 12:50 pm    Post subject: Reply with quote

Mangus wrote:
ReadyXB wrote:
I imagine the only concern would if the .XDL format changes in future Tunerpro revisions, it might breaking outside software.


Exactly correct. I can share the details with you, but I'm about 90% of the way done with replacing the entire logging system with a new, custom database-like implementation. Due to my own time constraints (I'm sure everyone has noticed that releases are further between and less feature-rich), I can't tell you exactly when the replacement will roll out, but it will happen.

OK thanks,

In the meantime I use an Asus Transformer book. To do the logging.
Controlled via an RDP session by an double din Parrot Asteroid Smart. Works fine, buy I want to make daily drive logging more simple. What car and engine manangement do you have?
Back to top
View user's profile Send private message
 

 
festy



Joined: 17 May 2012
Posts: 24
Location: Oz

PostPosted: Fri Jun 20, 2014 10:22 pm    Post subject: Reply with quote

Mangus wrote:
ReadyXB wrote:
I imagine the only concern would if the .XDL format changes in future Tunerpro revisions, it might breaking outside software.


Exactly correct. I can share the details with you, but I'm about 90% of the way done with replacing the entire logging system with a new, custom database-like implementation. Due to my own time constraints (I'm sure everyone has noticed that releases are further between and less feature-rich), I can't tell you exactly when the replacement will roll out, but it will happen.


Are you planning on publishing the new format, or at least still support reading XDL format files as well?
My raspberry pi based ALDL dash uses your ADX/XDL formats for logging, it's very handy to be able to pop a USB stick out of the dash and open straight up in Tuner Pro...
Back to top
View user's profile Send private message
 

 
razorx



Joined: 24 Mar 2014
Posts: 5

PostPosted: Fri Jun 27, 2014 10:37 am    Post subject: Reply with quote

Mangus wrote:
ReadyXB wrote:
I imagine the only concern would if the .XDL format changes in future Tunerpro revisions, it might breaking outside software.


Exactly correct. I can share the details with you, but I'm about 90% of the way done with replacing the entire logging system with a new, custom database-like implementation. Due to my own time constraints (I'm sure everyone has noticed that releases are further between and less feature-rich), I can't tell you exactly when the replacement will roll out, but it will happen.

Take your time Wink

Offtopic: The history tables are perfect for semi automatic map corrections in Excel. Works very nice.

A database based logging would be perfect. Giving the user the opportunity to collect useful data and do the calculations on it even more easily.
Back to top
View user's profile Send private message
 

 
dfddfd2



Joined: 27 Feb 2008
Posts: 112
Location: Burgaw, NC

PostPosted: Sun Jun 29, 2014 5:11 am    Post subject: Reply with quote

Rather than have the micro-controller board store data in XDL format, You might try storing the raw data on the SD card, then emulate the ECU side of data logging back to TunerPro. This way, it doesn't matter what the XDL format is. Your micro-controller board is already emulating the TunerPro side of the logging protocol to read the data. The only issue you may have is the per-packet relative time stamp, which means you may have to pace the communications back to TunerPro so it time stamps as if it was actually talking to the ECU.
_________________
NismotronicSA Tuning Package/Powered by TunerCodeSA
Speed-Density Tuning for Nissans
Back to top
View user's profile Send private message AIM Address
 

 
razorx



Joined: 24 Mar 2014
Posts: 5

PostPosted: Sun Jun 29, 2014 7:01 am    Post subject: Reply with quote

dfddfd2 wrote:
Rather than have the micro-controller board store data in XDL format, You might try storing the raw data on the SD card, then emulate the ECU side of data logging back to TunerPro. This way, it doesn't matter what the XDL format is. Your micro-controller board is already emulating the TunerPro side of the logging protocol to read the data. The only issue you may have is the per-packet relative time stamp, which means you may have to pace the communications back to TunerPro so it time stamps as if it was actually talking to the ECU.

Good suggestion!
Back to top
View user's profile Send private message
 

 
festy



Joined: 17 May 2012
Posts: 24
Location: Oz

PostPosted: Sun Jun 29, 2014 11:50 pm    Post subject: Reply with quote

The problem with doing it that way is that an hour long log would then take an hour to transfer to TP Crying or Very sad
The XDL format is pretty much just a timestamp plus the data returned by the ECU anyway - if you compare a hex dump of an xdl file with it's csv export, you should be able to spot the record structure.
If you use a short log with the engine off (so pretty static data values) it's even easier.
Back to top
View user's profile Send private message
 

 
ReadyXB



Joined: 29 May 2014
Posts: 8

PostPosted: Mon Jun 30, 2014 5:23 am    Post subject: Reply with quote

dfddfd2 wrote:
Rather than have the micro-controller board store data in XDL format, You might try storing the raw data on the SD card, then emulate the ECU side of data logging back to TunerPro. This way, it doesn't matter what the XDL format is. Your micro-controller board is already emulating the TunerPro side of the logging protocol to read the data. The only issue you may have is the per-packet relative time stamp, which means you may have to pace the communications back to TunerPro so it time stamps as if it was actually talking to the ECU.

I had implemented this method already and it does work. The time factor is currently unavoidable (although there are options that diags software could implement to eliminate this), but still, it gives me flexibility to continue logging if new diags software and/or log formats are released and I'm trying to play catchup.
Back to top
View user's profile Send private message
 

 
Mafketel



Joined: 18 Apr 2015
Posts: 4

PostPosted: Fri Apr 01, 2016 8:46 am    Post subject: Its 2016 now xdl is still used ;) Reply with quote

I know this is an old tread but the question is exactly right but sadly no answer.

So can I conclude that the format of the logfile is not going to be available?

It is about 2 years later and the logfile seems not to have changed.
From what i have gathered
the first 1 line info from tunerpro in my case 146 bytes long lotsa FF's on the end, does this change between different sessions?
next lines
first 12 bytes tunerpro info consisting of:
a timestamp(first 8 bytes) I am not entirely sure what is what within.
first 4 bytes are not clear yet
last 4 bytes LSB in ms
9 byte always 1? as a delimiter?
10 11 12 byte I don not know

the raw info from the ECU(in my case 135 bytes)

next entry in the logfile starting with the timestamp.

At least this is what i can gather from the file i have from the ecu log with 135 bytes of data from the ecu. And repetition at 147 bytes line length.


Last edited by Mafketel on Wed Sep 13, 2017 5:08 am; edited 1 time in total
Back to top
View user's profile Send private message
 

 
Mafketel



Joined: 18 Apr 2015
Posts: 4

PostPosted: Wed Apr 06, 2016 5:08 pm    Post subject: It was not an aprils fool question Reply with quote

A small bump Wink
Back to top
View user's profile Send private message
 

 
festy



Joined: 17 May 2012
Posts: 24
Location: Oz

PostPosted: Wed Apr 06, 2016 5:54 pm    Post subject: Reply with quote

I don't believe there are any plans to publish the XDL format, but regardless of whether or not it remains the primary log format used by Tuner Pro I think it's safe to assume it will continue to be supported in it's current form for the foreseeable future.
Back to top
View user's profile Send private message
 

 
Mafketel



Joined: 18 Apr 2015
Posts: 4

PostPosted: Mon Apr 18, 2016 7:05 am    Post subject: Reply with quote

Is there any good reason not to publish the format?

eventually somebody will share most details and it is open. Untill then ppl wanting to know just have to separately invest the time to decode.

I really would like not to spend more time figuring something out i do not have to.

I prefer just write some code on the microcontroller that also takes into account the crc in the datastream and not have to take my laptop to log data.

just read a different ecm and the header is still 146 bytes long even though the data line repetition is 115 bytes
Back to top
View user's profile Send private message
 

 
Mafketel



Joined: 18 Apr 2015
Posts: 4

PostPosted: Wed Sep 13, 2017 4:15 am    Post subject: Reply with quote

a small bump ....

maybe someone would like to shine a light on the format?
Back to top
View user's profile Send private message
 

Display posts from previous:   
View previous topic :: View next topic  
Post new topic   Reply to topic    TunerPro User Forum Forum Index -> TunerPro Discussion All times are GMT - 9 Hours
 
Page 1 of 1
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
 


Powered by phpBB © 2001, 2002 phpBB Group
RedSquare theme 1.0.3 © DoubleJ(Jan Jaap)