Automatic and event based savings of logs

[Ben-Acn33]

Hi Devs,

hope this is not beyond the scope but we are looking for an easy solution to store DLT data automatically while having a live (TCP) connection running. Example scenario would be: 1. Connect Laptop with chipmunk to DLT port of component. 2. Start Test loop of component (testdrive, loop testing etc.) 3. After testing is complete, have set of DLT logs saved on Laptop. To do this it would be nice to have:

1. Auto reconnect to port (it seems this is already in the making?)

2. Auto save of traces based on time interval, e.g. store all DLT lines every 30 minutes. (Bonus: save logs based on an event within the logs)

Is this even possible in principle?
Thanks a lot.
benedikt.krimphoff@accenture.com

[DmitryAstafyev]

Hi @Ben-Acn33,

Thanks for your issue. You can already cover your needs with using not GUI application, but CLI:

chipmunk-cli -o ~/Desktop/chip_output/logs.dlt -a -f binary dlt -f ~/Fibex/file1.xml -f ~/Fibex/file1.xml tcp 127.0.0.1:7777 -m 1000

That will:

• connect to tcp 127.0.0.1:7777
• parse dlt with 2 given fibex schemes ~/Fibex/file1.xml -f ~/Fibex/file1.xml
• save data into file ~/Desktop/chip_output/logs.dlt
• if the connection is lost, will try to reconnect as well and will continue storing

We started publishing cli tool for a while, you can find the latest release here (check the assets of the release for chipmunk-cli) and docs here.

[DmitryAstafyev]

@Ben-Acn33 in GUI auto-reconnection will also be present pretty soon. We are working on a general solution to make it possible for all data-sources. Please keep tracking for updates ;)

[Ben-Acn33]

Oh did not see that. Thanks for the info! Will try!

[AmmarAbouZor]

Hi @Ben-Acn33,
as mentioned by Dmitry, the reconnect configurations are currently available via the CLI tool only. To see all reconnect options please run

chipmunk-cli dlt tcp --help

Also to explore more commands you can try

chipmunk-cli --help
chipmunk-cli dlt --help

Also, we have gathered further points to implement for the CLI tool in #2202 . Please let us know if you need some of those features so we can prioritize it. Also, feel free to suggest new features there as well

The reconnecting in GUI part has a separate issue as well #2315