Zum Inhalt springen

DDA+ File gesucht, da ich einen DDA+ zu CSV converter schreibe


konastab

Empfohlene Beiträge

Hallo Jungs,

könnte mir jemand bitte ein dda+ log file senden? (von der PANI mit GPS) Es soltlen alle Daten befüllt sein - also speed, gear, GPS,.... (NICHT IM STILLSTAND)

Ich schreibe gerade ein kleines Programm, das dda+ files in CSV umwandeln kann. Somit kann man die log Daten auch in anderer Sofware ansehen!

bitte PM an mich, sende dann meine Mail.

DANKE!!

Ciao

Patrick

PS.: KLAR! Das Programm kann dann jeder haben!!(ok)

Link zu diesem Kommentar

Der erste Schritt ist getan!

DANKE @bk98 und @bassman!! Eure Files haben mir super geholfen. Das DECODING in HEX Files ist echt nervenaufreibend:(. Irgend wann mal sieht man nur noch Zahlen und Buchstaben...

So sieht das aus......

 

photo_2018-07-06_19-50-41.jpg

BUT FINALLY - I DID IT (ok)

Im Anhang das Excel File des decodierten Datenstreams. Aus diesem File werde ich nun ein kleines Programm schreiben, und hier dann posten!

EIN FELD fehlt mir noch. Ich könnte mir vorstellen, dass hier die Rundenzahl steht. Daher die Bitte - Falls jemand ein File hat, bei dem auch der Rundentrigger funktioniert hat, bitte mir senden!!

1199_DDA+_DECODING.xlsx

Link zu diesem Kommentar

Moin Patrick,

in dem file, was ich Dir geschickt habe ist leider der ganze Turn als eine Runde gespeichert, der Fahrer hat vergessen aufs Knöpf chen zu drücken :D

Wenn Du möchtest frag ich nochmal. Eventuell finde ich auch noch eines von einer 1198. Allerdings ist da das Format sicherlich anders, weil für DDA Version 2, hilft wohl nicht viel.

Link zu diesem Kommentar
  • 4 Monate später...

JUNGS ES IST SOWEIT!!!!

Ich habe den converter fertig. Ab jetzt kann jeder seine dda files in csv umwandel, und dann z.B in Dashware benutzten um Data Overlay videos zu machen!!

wie dieses von mir erstellt: https://www.youtube.com/watch?v=DjnkZ9t-FS0&t=316s

 

Und ich gebe gleich noch mein Dashware Template zum einlesen der Ducati Daten UND mein gezeichnetes Display mit.

Momentan habe ich es für 1199s mit GPS getestet. Möglicherweise funktioniert es auch mit anderen Modellen. Bitte versuchen!

Habe auch noch eine Anleitung geschrieben. Die ist aber auch im zip mit dabei.

 

This package contains 2 separate parts:
1.) DDA2CSV.exe
Convert tool to transform *.dda files ( 1199s Panigale with GPS receiver) into a *.csv file.

2.) DashWare Folder
Dashware is a software to create data overlay to an existing video based on csv files. Dashware could be downloaded free of charge from http://www.dashware.net/.
This folder with the subfolders will contain a special created DUACTI Dashboard, and the DataProfile to load the *.csv File created with DDA2CSV.exe into Dashware
To use it, just copy the contend of the folders into the corresponding DashWare folders on your hard drive.
Usually the folder is located in ..\Documents\Dashware

Ad1.)
1.)    Copy DDA2CSV.exe to the folder where your *.dda files are stored
2.)    Start DDA2CSV.exe -->a command window will pop up
3.)    Type the name of the dda file, that should be converted include .dda (Example: RedBullRing.dda)
4.)    Your *.dda file is converted into a *.csv in the same folder with the same name
5.)    Do what you want with this csv file :-)
Ad2.)
1.)    Start DashWare
2.)    File-->New Project
3.)    Enter Project Name; Project Template choose <None>; klick ok
4.)    On the right side you could see the tab “Project” In there you could see “Input Settings”
5.)    Beside Video klick the plus symbol, and choose a video from your Hard drive
6.)    Beside Data Files klick the plus symbol. A window will pop up
7.)    In “Data logger file” choose the just converted csv file
8.)    In “Choose a data profile” choose 1199. Klick ok. Now the data is loaded correctly
9.)    In tab “Gauge Toolbox” search for “Ducati Corse..” Display and drag and drop it into the video
10.)    in tab “Synchronization” you could sync the data to the video
11.)    READY!


VIEL SPASS!!

 

DDA2CSV_and_DASHWARE.zip

Link zu diesem Kommentar
  • 2 Jahre später...
Am 17.11.2018 um 17:40 schrieb konastab:

JUNGS ES IST SOWEIT!!!!

Ich habe den converter fertig. Ab jetzt kann jeder seine dda files in csv umwandel, und dann z.B in Dashware benutzten um Data Overlay videos zu machen!!

wie dieses von mir erstellt: https://www.youtube.com/watch?v=DjnkZ9t-FS0&t=316s

 

Und ich gebe gleich noch mein Dashware Template zum einlesen der Ducati Daten UND mein gezeichnetes Display mit.

Momentan habe ich es für 1199s mit GPS getestet. Möglicherweise funktioniert es auch mit anderen Modellen. Bitte versuchen!

Habe auch noch eine Anleitung geschrieben. Die ist aber auch im zip mit dabei.

 

This package contains 2 separate parts:
1.) DDA2CSV.exe
Convert tool to transform *.dda files ( 1199s Panigale with GPS receiver) into a *.csv file.

2.) DashWare Folder
Dashware is a software to create data overlay to an existing video based on csv files. Dashware could be downloaded free of charge from http://www.dashware.net/.
This folder with the subfolders will contain a special created DUACTI Dashboard, and the DataProfile to load the *.csv File created with DDA2CSV.exe into Dashware
To use it, just copy the contend of the folders into the corresponding DashWare folders on your hard drive.
Usually the folder is located in ..\Documents\Dashware

Ad1.)
1.)    Copy DDA2CSV.exe to the folder where your *.dda files are stored
2.)    Start DDA2CSV.exe -->a command window will pop up
3.)    Type the name of the dda file, that should be converted include .dda (Example: RedBullRing.dda)
4.)    Your *.dda file is converted into a *.csv in the same folder with the same name
5.)    Do what you want with this csv file 🙂
Ad2.)
1.)    Start DashWare
2.)    File-->New Project
3.)    Enter Project Name; Project Template choose <None>; klick ok
4.)    On the right side you could see the tab “Project” In there you could see “Input Settings”
5.)    Beside Video klick the plus symbol, and choose a video from your Hard drive
6.)    Beside Data Files klick the plus symbol. A window will pop up
7.)    In “Data logger file” choose the just converted csv file
8.)    In “Choose a data profile” choose 1199. Klick ok. Now the data is loaded correctly
9.)    In tab “Gauge Toolbox” search for “Ducati Corse..” Display and drag and drop it into the video
10.)    in tab “Synchronization” you could sync the data to the video
11.)    READY!


VIEL SPASS!!

 

DDA2CSV_and_DASHWARE.zip

sag mal, konastab - könnte man diesen Converter auch für Mac OS X kompilieren?

Ich verwende eine GoPro Max und die App "Telemetry Overlay" von Juan Irache auf meinem Mac (https://goprotelemetryextractor.com/telemetry-overlay-gps-video-sensors).
Da würde ich natürlich gerne zusätzliche Daten von einem DDA einpflegen.

Danke, Christof

Link zu diesem Kommentar
  • 3 Monate später...
Am 23.1.2021 um 22:18 schrieb konastab:

@doctorb

Ja klar!

Hast PN..

CIao

Patrick

Hi @konastab,

Vielen dank für diesem DDA2csv converter!

Converting DDA data coming from my V4s seems to work and your V4 dash setup templates for DashWare are looking great. Nice looking stuff! 😎

I have an issue with importing DDA conversions from your DDA2csv tool into DashWare though.

Please refer to picture: V4_DDA2DashWare

In short, I am unable to have DashWare recognise my DDA data properly, as converted by your tool from this V4 dda file:

https://www.dropbox.com/s/837iud5doweikj1/Run005-088535-00.00_1pit.dda?dl=0

In this example 7 practice laps.

New to adding DDA telemetry and using the DashWare tool for my GoPro movies, I could be doing something wrong or does the data-structure between 1199 DDA and V4 DDA differ somewhat?

For example, could it be that the order of a/o amount of DDA data-fields from a 1199 DDA(+) differ somewhat from a V4 DDA+ (Mod1409 (Evo))?

Thanks again for your help.

Regards, Robert.

Link zu diesem Kommentar
Am 17.5.2021 um 21:10 schrieb konastab:

@RdashP yes, the data is different from 1199 to V4. The converter will not work. Sorry...

Hi, dein converter funktioniert prima aber input ist ja anders! Wie kann ich zum Beispiel das dda Input Struktur vom mein V4 oder die converted csv Ordnung ändern so das RaceRender oder Dashware sie normalerweise erkannt und importieren kann wie beim dein eigene 1199 dda Data? freundliche Grüße

Link zu diesem Kommentar
  • 1 Monat später...
Am 21.5.2021 um 09:00 schrieb konastab:

@RdashP As you can see here:

 

It was a lot of work to decode the HEX file. Of course the HEX file is different from the V4. My converter is hardcoded to the HEX file from the 1199. It must be re-written for the V4. Since I don't have a V4 I'm not able to support here.

Bye

Patrick

 

@konastab Hi Patrick, this is how far I get with the V4.dda in comparison to your own HEX analysis of a 1199.dda, as you posted a snapshot of: 

LlaAbwb.jpg

Line4line in the same part of our Offset(h), indeed the V4.dda compared to your 1199.dda datasheet picture looks very different!

Then again I'm not even sure if I should compare your 'FF' indicators of the 1199.dda from Offset(h) 00016160 and further on 1:1 to the ones I find in different positions of the same section within my V4.dda file!?: Run005-088535-00.00_1pit.dda (dropbox.com)

SOS I'm trying to learn here. 🙂

May be you can give me a few clues on how to advance from here e.g. how to set the relevant color coding's as per HEX value for my V4.dda as you used yourselves to figure out the file-structure of the 1199.dda?

Vielen dank für Die Muhe!

Robert

 

Link zu diesem Kommentar
Am 8.7.2018 um 10:18 schrieb konastab:

Der erste Schritt ist getan!

DANKE @bk98 und @bassman!! Eure Files haben mir super geholfen. Das DECODING in HEX Files ist echt nervenaufreibend:(. Irgend wann mal sieht man nur noch Zahlen und Buchstaben...

So sieht das aus......

 

photo_2018-07-06_19-50-41.jpg

BUT FINALLY - I DID IT (ok)

Im Anhang das Excel File des decodierten Datenstreams. Aus diesem File werde ich nun ein kleines Programm schreiben, und hier dann posten!

EIN FELD fehlt mir noch. Ich könnte mir vorstellen, dass hier die Rundenzahl steht. Daher die Bitte - Falls jemand ein File hat, bei dem auch der Rundentrigger funktioniert hat, bitte mir senden!!

1199_DDA+_DECODING.xlsx

Patrick,

Die Anfang dieses V4.dda liest ziemlich normal als decodierte Text fur welche Kanäle (Data PIDs?) erforderlich sind?:

ArbYwt6.jpg

Sollte ich diese Informationen brachen um weiter ins dda bestimmte HEX zu decodieren?

Danke, Robert

 

Link zu diesem Kommentar

@RdashP Nein den Wert brauchst du nicht unbedingt. Er gibt nur an wie viele Byte in einer Zeile dargestellt werden. Wenn du einmal eine ganze Nachricht gefunden hast, könntest du die Länge der Nachricht über die Byte einstellen. Dann hast du in jeder Zeile eine Nachricht und das decodieren ist einfacher. Bei der 1199 war das Ende einer Nachricht mit FF.

Ciao

Patrick

Link zu diesem Kommentar
Am 26.6.2021 um 08:38 schrieb konastab:

@RdashP Nein den Wert brauchst du nicht unbedingt. Er gibt nur an wie viele Byte in einer Zeile dargestellt werden. Wenn du einmal eine ganze Nachricht gefunden hast, könntest du die Länge der Nachricht über die Byte einstellen. Dann hast du in jeder Zeile eine Nachricht und das decodieren ist einfacher. Bei der 1199 war das Ende einer Nachricht mit FF.

Ciao

Patrick

Hi Patrick,
I've checked available DDA channels between 1199 and V4 and indeed they are quite different.

So message length and order of PID data channels per timestamp will be different too:

gZAw6nC.png

Next I will try to find the message separator per time-stamp. Hopefully the same as the DDA file-format for 1199 uses 'FF' at the end of each string per timestamp.

To be continued... 

 

Link zu diesem Kommentar
Am 8.7.2018 um 10:18 schrieb konastab:

Der erste Schritt ist getan!

DANKE @bk98 und @bassman!! Eure Files haben mir super geholfen. Das DECODING in HEX Files ist echt nervenaufreibend:(. Irgend wann mal sieht man nur noch Zahlen und Buchstaben...

So sieht das aus......

 

photo_2018-07-06_19-50-41.jpg

BUT FINALLY - I DID IT (ok)

Im Anhang das Excel File des decodierten Datenstreams. Aus diesem File werde ich nun ein kleines Programm schreiben, und hier dann posten!

EIN FELD fehlt mir noch. Ich könnte mir vorstellen, dass hier die Rundenzahl steht. Daher die Bitte - Falls jemand ein File hat, bei dem auch der Rundentrigger funktioniert hat, bitte mir senden!!

1199_DDA+_DECODING.xlsx

Hi Patrick,

I'm confused when counting your bytes for the 1199 message length:

- in your picture you count only 165 bytes between each message ending 'FF' separator.

- in your attached xlsx you seem to count as much as 275 bytes between each message ending 'FF' separator?!

Which byte count per DDA message is the correct one for 1199: 275 of 165?

 

FYI the V4.dda files seem to contain even more bytes (14E/334) between each message ending 'FF' separator, if indeed 'FF' is also used to signal the byte string endpoint. Is expected given at least 3 more data channels (PIDs).

Leider ist mein Deutsch nicht gut genug um meine Erfahrungen hierhin zu schreiben. ;)

Cheers, Robert

oyZbgws.png

Link zu diesem Kommentar

Guys,

Just like the 'woman in the red dress' within the Matrix, it looks as though I found logic within the seemingly endless 334 bytes message-length string for V4.dda?! Instead of chaos, I suddenly see structure when setting the HEX reader to an odd column-width of 33! With these 334 bytes and reader set to 33 columns, I finally see a similar byte-structure as @konastab had when setting his 165 bytes of the 1199  message-length string to 16 columns.

Hopefully this is not a coincidence, but a sensible repeating pattern of actual related bytes per V4 PID-channel, repeating itself visibly when set to 33 columns:

EKyBdEh.png

I now need to map available 9+ channels to their repeating positions within the message-string like Patrick did.

Hmmm, where to start/ which itself repeating bytes look like e.g. Speed or RPM?

Help and smart iDs are appreciated and will for sure speed up my mapping quest for V4.dda? ;)

To be continued...

Link zu diesem Kommentar

Hi konastab and RdashP!

It makes me happy to see that 2 smart people are working on this front! So there is hope :-)

My skills in this field are pretty much "0" and I doubt whether I am able to truly help here.

But with my ODBLink MX+ connected to my iPhone via BT, I can read some basic data such as rpm and throttle position straight into the ODB app.
And I have yet to try to get some of these channels read into RaceChrono, but both apps appear to support some CanBus data straight out of the box.
And this being the case, maybe you guys can use the log of these apps to get to the structure of the packages?

Just an idea!

Chris

Link zu diesem Kommentar
Am 4.7.2021 um 23:26 schrieb doctorb:

This is a session from my recent session at Rijeka. RaceChrono says that it contains ODB II data.

Export is for RaceRender / DashWare format

The display in RC mentions speed, rpm and throttle

Let me know if you want different formats

session_rijeka_lap7_20210613_1014_v2.csv 11 MB · 3 downloads

Hi Chris,

Interesting csv indeed!

In your csv, are these PID channels recorded in real-time (i.e. while racing?) coming from your from V4 via the OBDLinkMX dongle/plug connected to the 4pin DDS connecter under your seat?

If so, can you also find #Gear, #DTC (TorqueFast) and #DWC (TorqueSlow) in Settings of OBDLink app under ‘User-Defined PIDs’ (or RC app?) while connected to V4 with ignition on/ running engine?

Besides DDA and continue to work on dda2csv mapping, I also have an OBDLink MX WiFi dongle with an OBD<>DDS conversation cable. I will try to replicate your csv export with these #3 missing V4 PIDs included.

If this works via OBDLink dongles , we finally unlock specific V4 PIDs as data attributes for universal application (e.g. for GoPro telemetry overlays).

Since I understand only the red DDA-stick connected to the 4pin DDS connector is able to also tap into the 10Hz GNSS receiver (i.e. add-on accessory to DDA) installed in V4 tail, you need to fall back to another GNSS source for satellite 🛰 position data, e.g. from the 10x slower embedded 1Hz GNSS receiver of GoPro or Smartphones. 5Hz or slower GNSS update rates are useless for racing line analysis.

Hmmm this would mean that if you don’t also add a fast 3rd party GNSS receiver like VBox Sport, that would mean a typical case of ‘you win some, you loose some’? 🤔😆 

Bearbeitet von RdashP
redo non-typo OBD 2 ODB
Link zu diesem Kommentar

Hi RdashP!
Let me try to be more specific:

1. at the moment, the ODBLink can only (off-the-shelf) read and transmit some very basic data. Basically what it would get from a car. But it gets recorded real-time into RC. And once some relevant PIDs are decoded from the V4 CanBus, these can be set as custom channels within RC. Since I am not a technical person, I haven't been able to achieve this, but it shouldn't be too hard. After all, AIM has also done this for their wired solution. The Dongle + adapter fits under the seat and is auto-on / auto-off.

2. the QStarz works perfectly in my "trunk" and like the ODBLink, it is connected via BLE. The data gets recorded at 10 Hz in real time as well and RC also calculates a "theoretical lean-angle" from the GPS data.

Hope this is more clear!

Christof

Link zu diesem Kommentar
Am 5.7.2021 um 23:20 schrieb RdashP:

If so, can you also find #Gear, #DTC (TorqueFast) and #DWC (TorqueSlow) in Settings of OBDLink app under ‘User-Defined PIDs’ (or RC app?) while connected to V4 with ignition on/ running engine?

Besides DDA and continue to work on dda2csv mapping, I also have an OBDLink MX WiFi dongle with an OBD<>DDS conversation cable. I will try to replicate your csv export with these #3 missing V4 PIDs included.

forgot to answer: from what I learned, it only works via BLE and with the MX+. And no, I could not easily find these channels, but I haven't delved very deep into the expert settings of RC yet. Will play some more once I am back with my bike (Brno in 2 weeks)

Link zu diesem Kommentar

In addition to the previous posts:

I asked Antti Lammi, whether RaceChrono has "listening tools" for CanBus PIDs, and here is his reply:

"RaceChrono does not have tools or features to find OBD-II or CAN-Bus PIDs. It could have them, but of course it's more work, and this is not a feature that a lot of people would use... 
 
If you're working on the raw CAN-Bus messages (instead of OBD-II), you could use a terminal connection to your OBD-II reader. You can then send some commands to it:
 
ATZ (+ enter) 
Will reset your reader
 
ATM
Will listen to the CAN-Bus. It will display all the packets (and PIDs) it's seeing in the bus. 
 
You could also use some more elaborate tools to monitor and reverse engineer the bus. But this is how I did it on my bike" 

Maybe this info is of use to you guys.

But at the end of the day, we probably need to find someone, who has the electronic tools / interface and knowledge to RE the V4 CanBus ...

 

Link zu diesem Kommentar
Am 8.7.2021 um 19:04 schrieb doctorb:

forgot to answer: from what I learned, it only works via BLE and with the MX+. And no, I could not easily find these channels, but I haven't delved very deep into the expert settings of RC yet. Will play some more once I am back with my bike (Brno in 2 weeks)

I understand. will focus my mapping quest for V4 similar to @Konastab for 1199 then. May be with have some SME help closer then I thought 💭… 

Great summer to ya all :)

Link zu diesem Kommentar
Am 30.6.2021 um 20:04 schrieb RdashP:

Hi Patrick,
I've checked available DDA channels between 1199 and V4 and indeed they are quite different.

So message length and order of PID data channels per timestamp will be different too:

gZAw6nC.png

Next I will try to find the message separator per time-stamp. Hopefully the same as the DDA file-format for 1199 uses 'FF' at the end of each string per timestamp.

To be continued... 

 

 

I believe I’m close to solving the V4.dda puzzle 🧩:

1) IF order for 9+4 DDA channels of V4 is like the order in its header:

image.thumb.jpeg.9dea295447d70328c4bd959732e7f3f9.jpeg

2) AND string is 334 bytes of length (FF2FF) per 1 second devided by 10Hz which is the 10 times/sec sampling-rate of the build-in GNSS receiver also attached to CanBus of the bike for DDA- and Lap2Lap-recording:

520F6B85-D9E0-4ADB-A18D-646561A9F368.jpeg.3268d453d698a0de649e07226a718363.jpeg

3) THEN after every ~33 bytes bytes in the string (i.e. 334/10 also equals set HxD column width!) the DDA channel recording repeats itself 10 times for most PiD channels/attributes (TBD not all!) in same order as channel/attribute order stated in header of each v4.dda file, before moving to next 1 second ‘FF2FF’ string recording!!!

image.thumb.png.6c4867a3ef20ca807b72df138d17de28.png

 

If this turns out to be a correct assumption then the ‘only’ remaining task to solve the V4.dda file format puzzle 🧩, is to determine how many bytes each of the 9+4 repeating PiD channels require before moving to the next channel byte-set and the next etc. for all 9(+4?), before the next identical repetition of 33 bytes starts.

May be we can find a certain separator character (e.g. ‘$’) which is used to indicate/isolate/signal the start/end of each PiD channel.

Like @konastab e.g. found out for 1199.dda that ‘RPM’ byte-sets are always repeating 4-4-2, ‘DTC’ is always 1, ‘Speed’ is 2 and LAT/LON are always 4, etc. etc.

So, let’s take @konastab 1199.dda 27 column repetition and byte-set ordering as a starting point and see where v4.dda differs for 33 columns.

To be continued…

Link zu diesem Kommentar
Am 8.7.2021 um 19:04 schrieb doctorb:

forgot to answer: from what I learned, it only works via BLE and with the MX+. And no, I could not easily find these channels, but I haven't delved very deep into the expert settings of RC yet. Will play some more once I am back with my bike (Brno in 2 weeks)

Looked in RC settings > [+] ‘Add Other Device’ as explained by RC’s FAQ you quoted. As snapshot shows both our OBDlink dongles BLE ánd WiFi seem to be supported by RC. Which is great. 👍 

4E981FAE-2057-4C25-A9C6-81BA622639A6.jpeg

 

Since DDA only records the 9(+4) DMH approved PiDs for V4, the RCapp + OBDlink combo indeed seem to have the potential to read TBD ‘all’ PiDs on the live Canbus it is connected to via the 4-pin DDS connector! This way we are able to reverse engineer all ‘packets and PiDs’ transferred through the V4 Canbus. Instead of ‘just’ connecting OBDlink to your bike and setting up the RC app in iOS correctly with ‘just a few clicks’, you probably need a ‘pro’ monitoring tool 🥸 and ‘NDA’ bound 😝knowhow to achieve this…

Nevertheless it would be great to also be able to select and record in this RC app the by DMH-Prosa omitted/ restricted 🚫 PiDs for live recording (e.g. engine oil-/water temp sensors, ABS sensors, DSC, EBS, etc.).

 

For now, to keep things ‘easy’ and achievable, I will concentrate on deciphering and mapping the very limited amount of 9(+4) PiDs their positions/order per 33 bytes, as recorded in each v4.dda file. Which is already a challenge in itself. LOL😝 

 

Bearbeitet von RdashP
Link zu diesem Kommentar
  • 1 Monat später...
  • 2 Wochen später...
Am 1.9.2021 um 07:47 schrieb RdashP:

Guys, I will seize my dda2csv efforts for V4, since someone I got in contact with already pulled it off. As agreed, I will not undisclose nor share this knowhow. I’m sorry.

I can share the rewarding result:

 

Sorry guys. Really I can’t share my dda2csv converter. Once online no control. 

Please do ask contact_us@ducati.com to finally provide a similar dda2csv function through their official DDA software.

If enough of their DDA ‘enabled’ riders request this, may be Bologna finally understands that this actually could improve DDA+ sales (i.e. no need to buy similar 3rd party solution instead for any V4) ánd make their already existing data-savvy customers happier? #win-win

take care grtz

Link zu diesem Kommentar
  • 5 Wochen später...
Am 30.6.2021 um 20:04 schrieb RdashP:

Hi Patrick,
I've checked available DDA channels between 1199 and V4 and indeed they are quite different.

So message length and order of PID data channels per timestamp will be different too:

gZAw6nC.png

Next I will try to find the message separator per time-stamp. Hopefully the same as the DDA file-format for 1199 uses 'FF' at the end of each string per timestamp.

To be continued... 

 

This is how ill-conversion of dda2csv looks (if it works at all) when using any of the existing 1199.dda converters for a V4.dda file:

STrfiqF.jpg

Link zu diesem Kommentar
Am 17.11.2018 um 17:40 schrieb konastab:

JUNGS ES IST SOWEIT!!!!

Ich habe den converter fertig. Ab jetzt kann jeder seine dda files in csv umwandel, und dann z.B in Dashware benutzten um Data Overlay videos zu machen!!

wie dieses von mir erstellt: https://www.youtube.com/watch?v=DjnkZ9t-FS0&t=316s

 

Und ich gebe gleich noch mein Dashware Template zum einlesen der Ducati Daten UND mein gezeichnetes Display mit.

Momentan habe ich es für 1199s mit GPS getestet. Möglicherweise funktioniert es auch mit anderen Modellen. Bitte versuchen!

Habe auch noch eine Anleitung geschrieben. Die ist aber auch im zip mit dabei.

 

This package contains 2 separate parts:
1.) DDA2CSV.exe
Convert tool to transform *.dda files ( 1199s Panigale with GPS receiver) into a *.csv file.

2.) DashWare Folder
Dashware is a software to create data overlay to an existing video based on csv files. Dashware could be downloaded free of charge from http://www.dashware.net/.
This folder with the subfolders will contain a special created DUACTI Dashboard, and the DataProfile to load the *.csv File created with DDA2CSV.exe into Dashware
To use it, just copy the contend of the folders into the corresponding DashWare folders on your hard drive.
Usually the folder is located in ..\Documents\Dashware

Ad1.)
1.)    Copy DDA2CSV.exe to the folder where your *.dda files are stored
2.)    Start DDA2CSV.exe -->a command window will pop up
3.)    Type the name of the dda file, that should be converted include .dda (Example: RedBullRing.dda)
4.)    Your *.dda file is converted into a *.csv in the same folder with the same name
5.)    Do what you want with this csv file :-)
Ad2.)
1.)    Start DashWare
2.)    File-->New Project
3.)    Enter Project Name; Project Template choose <None>; klick ok
4.)    On the right side you could see the tab “Project” In there you could see “Input Settings”
5.)    Beside Video klick the plus symbol, and choose a video from your Hard drive
6.)    Beside Data Files klick the plus symbol. A window will pop up
7.)    In “Data logger file” choose the just converted csv file
8.)    In “Choose a data profile” choose 1199. Klick ok. Now the data is loaded correctly
9.)    In tab “Gauge Toolbox” search for “Ducati Corse..” Display and drag and drop it into the video
10.)    in tab “Synchronization” you could sync the data to the video
11.)    READY!


VIEL SPASS!!

 

DDA2CSV_and_DASHWARE.zip

Hallo konastab,

funktioniert dein Converter auch für DDA-Files der 1299 mit GPS ??

Habe versucht gemäß deiner Anleitung ein Video zur erstellen.

Das Ergebnis sieht aber so aus wie im Bild des letzten Beitrages zu sehen ist

oder hat das eine andere Ursache ?

Gruss

A.

Link zu diesem Kommentar
×
×
  • Neu erstellen...

Wichtige Information

Wenn du dich hier anmeldest hast du die Datenschutzerklärung und die Foren Regeln gelesen! Du versicherst damit dich auch an diese zu halten!