Hi Jacek, I hoped someone from Viewer side replies to your message. So please see this message more as "resend" than answer to your question because I am not familiar with the viewer code enough. Best regards Christoph Lipka Engineering System & Architecture (ADITG/ESA) Tel. +49 5121 49 6945 > -----Original Message----- > From: genivi-diagnostic-log-and-trace <genivi-diagnostic-log-and-trace- > bounces@lists.genivi.org> On Behalf Of Wywrót Jacek via genivi-diagnostic- > log-and-trace > Sent: Mittwoch, 9. Januar 2019 13:44 > To: genivi-diagnostic-log-and-trace@lists.genivi.org > Subject: [genivi-dlt] Question regarding modifying time / timestamp of Log > message > > Hello guys, > > I have a question regarding possibility of modifying time/timestamp of Log > messages. > What I try to do is create some plugin for adjusting time of messages. > I import dlt stream, and then only timestamps of messages are valid (I > assume that time of messages in file is created basing on time they has been > imported). > But the idea is to parse all the logs against logs with Time syncronization (and > setup correct time of frames basing on real time). > The time sync logs are sent with constant interval, so using the date and time > from logs I could update the time of logs. > > I generally try to be able to modify the time of frames basing on sync points, > real time of sync points and timestamp of frames. > Then I would want to load log from another MCU containing real time, and > sort messages by time to have correct relations of logs for both MCUs. > > I tried with creating control plugin to be able to read all messages in the > imported file. > I used initFileFinish function to process all messages and obtain all sync points > for time. > At this point I can construct hashmap containing real time for each frame, but > I'm unable to update the messages to the correct time. > > So I tried to implement also decoder plugin interface, to be able to modify > messages passed in decodeMsg (mofify the time). > Unfortunately in decodeMsg function I have no information about the > message index, to be able to update message time repectively to real time > information. > > So maybe someone could advice some solution for that kind of approach. > > > -- > > Pozdrawiam / Kind Regards > > Jacek Wywrot > M.Sc. Eng. > Senior Software Engineer > Development Centre > Car Infotainment > > Bury Sp. z o.o. > ul. Wspolna 2A > 35-205 Rzeszow > > Intern.:3467 > Tel: +48 (0) 17 773 87 67 > Fax: +48 (0) 17 773 88 01 > Mobile: +48 (0) 663 85 01 45 > > E-Mail: Jacek.Wywrot@bury.com<mailto:Jacek.Wywrot@bury.com> > wywrot@bury.com<mailto:wywrot@bury.com> > Internet: http://www.bury.com > > > W związku z wejściem w życie przepisów Ogólnego Rozporządzenia o > Ochronie Danych Osobowych (tzw. RODO), BURY Sp. z o.o. z siedzibą w > Mielcu, spełniając swój ustawowy obowiązek, umożliwia Państwu > zapoznanie się z informacjami dotyczącymi przetwarzania Państwa danych > osobowych przez BURY Sp. z o.o. > Podstawowe informacje: > 1. Administratorem danych osobowych jest BURY Sp. z o. o. z siedzibą w > Mielcu, będąca stroną łączącej nas z Państwem (podmiotem, w którym > Państwo są zatrudnieni, z którym współpracujecie, którego jesteście > wspólnikami lub reprezentantami etc.) umowy lub podmiotem, z którym > nawiązany został kontakt. > 2. W każdym czasie mogą Państwo poprosić o dostęp do swoich danych, ich > poprawienie, usunięcie lub ograniczenie przetwarzania. Wszystkie > przysługujące Państwu prawa znajdują się na tej stronie > https://www.bury.com/pl/dzialalnosc/info/rodo/. W celu realizacji > powyższych uprawnień prosimy o kontakt na adres rodo@bury.com. > 3. Państwa dane osobowe przetwarzane są głównie w celu nawiązania lub > zachowania współpracy, wykonania umowy. > 4. Więcej na ten temat mogą Państwo przeczytać > tutaj<https://www.bury.com/pl/dzialalnosc/info/rodo/> > > Following the entry into force of the General Data Protection Regulation (so- > called GDPR), BURY Sp. z o.o. based in Mielec, fulfilling its statutory duty, > enables you to become familiar with the information concerning the > processing of your personal data by BURY Sp. z o.o. > Basic information: > 1. BURY Sp. z o. o. based in Mielec is the administrator of personal data and a > party (entity, you are employed in, you cooperate with, you are a partner or > a representative of, etc.) to the agreement concluded with you, or the entity > with which the contact has been established. > 2. At any time, you can ask for access to your data, their rectification, deletion > or limitation of their processing. All the rights you are entitled to can be > found on this website https://www.bury.com/en/business/info/gdpr/. In > order to exercise the above rights, please contact us at rodo@bury.com. > 3. Your personal data are processed mainly in order to establish or maintain > cooperation, perform an agreement. > 4. More details on this topic can be found > here<https://www.bury.com/en/business/info/gdpr/>. > _______________________________________________ > genivi-diagnostic-log-and-trace mailing list genivi-diagnostic-log-and- > trace@lists.genivi.org > http://lists.genivi.org/mailman/listinfo/genivi-diagnostic-log-and- > trace_lists.genivi.org

Hello all, I have yet another though related question. I would like to create plugin which would help me to see missing log messages. Currently we face some issue, and some logs being sent over UART, are dropped either in the device, DLT viewer or in FTDI serial-to-usb adapter. This is probably because lots of messages are sent at 500kbit/s. So the plugin is supposed to check message "count" value (messageCounter field in qdltmsg), and compare with the previous message in the file. I would like to see some feedback on log when I[n] - I[n-1] != 1 (of course considering the counter/ overturns with 255 to zero). So if following logs are visible: 7677 2019/01/21 09:51:02.762564 0.0320 9 NFCB FBAP N/A 0 log info verbose 1 13 ******************************************************** 7679 2019/01/21 09:51:02.763540 0.0360 11 NFCB FBAP N/A 0 log info verbose 1 15 RESFR: |0x200|POWUP| With index 9, an the following has index 11 I would like to see the log coloured red (so maybe the plugin could switch subtype to DltLogWarn or DltLogError) So I imagine I could implement QDLTPluginDecoderInterface and ::isMsg/ ::decodeMsg functions. In function I would like to, at certain condition, change log subtype, but basing on the previous message. Is that possible to access the n-1 message somehow, maybe combining with some other plugin types, and modify QDltMsg parameters? Kind Regards Jacek Wywrót W dniu 16.01.2019 o 08:59, Lipka, Christoph (ADITG/ESA) pisze: Hi Jacek, I hoped someone from Viewer side replies to your message. So please see this message more as "resend" than answer to your question because I am not familiar with the viewer code enough. Best regards Christoph Lipka Engineering System & Architecture (ADITG/ESA) Tel. +49 5121 49 6945 -----Original Message----- From: genivi-diagnostic-log-and-trace <genivi-diagnostic-log-and-trace- bounces@lists.genivi.org<mailto:bounces@lists.genivi.org>> On Behalf Of Wywrót Jacek via genivi-diagnostic- log-and-trace Sent: Mittwoch, 9. Januar 2019 13:44 To: genivi-diagnostic-log-and-trace@lists.genivi.org<mailto:genivi-diagnostic-log-and-trace@lists.genivi.org> Subject: [genivi-dlt] Question regarding modifying time / timestamp of Log message Hello guys, I have a question regarding possibility of modifying time/timestamp of Log messages. What I try to do is create some plugin for adjusting time of messages. I import dlt stream, and then only timestamps of messages are valid (I assume that time of messages in file is created basing on time they has been imported). But the idea is to parse all the logs against logs with Time syncronization (and setup correct time of frames basing on real time). The time sync logs are sent with constant interval, so using the date and time from logs I could update the time of logs. I generally try to be able to modify the time of frames basing on sync points, real time of sync points and timestamp of frames. Then I would want to load log from another MCU containing real time, and sort messages by time to have correct relations of logs for both MCUs. I tried with creating control plugin to be able to read all messages in the imported file. I used initFileFinish function to process all messages and obtain all sync points for time. At this point I can construct hashmap containing real time for each frame, but I'm unable to update the messages to the correct time. So I tried to implement also decoder plugin interface, to be able to modify messages passed in decodeMsg (mofify the time). Unfortunately in decodeMsg function I have no information about the message index, to be able to update message time repectively to real time information. So maybe someone could advice some solution for that kind of approach. -- Pozdrawiam / Kind Regards Jacek Wywrot M.Sc. Eng. Senior Software Engineer Development Centre Car Infotainment Bury Sp. z o.o. ul. Wspolna 2A 35-205 Rzeszow Intern.:3467 Tel: +48 (0) 17 773 87 67 Fax: +48 (0) 17 773 88 01 Mobile: +48 (0) 663 85 01 45 E-Mail: Jacek.Wywrot@bury.com<mailto:Jacek.Wywrot@bury.com><mailto:Jacek.Wywrot@bury.com><mailto:Jacek.Wywrot@bury.com> wywrot@bury.com<mailto:wywrot@bury.com><mailto:wywrot@bury.com><mailto:wywrot@bury.com> Internet: http://www.bury.com W związku z wejściem w życie przepisów Ogólnego Rozporządzenia o Ochronie Danych Osobowych (tzw. RODO), BURY Sp. z o.o. z siedzibą w Mielcu, spełniając swój ustawowy obowiązek, umożliwia Państwu zapoznanie się z informacjami dotyczącymi przetwarzania Państwa danych osobowych przez BURY Sp. z o.o. Podstawowe informacje: 1. Administratorem danych osobowych jest BURY Sp. z o. o. z siedzibą w Mielcu, będąca stroną łączącej nas z Państwem (podmiotem, w którym Państwo są zatrudnieni, z którym współpracujecie, którego jesteście wspólnikami lub reprezentantami etc.) umowy lub podmiotem, z którym nawiązany został kontakt. 2. W każdym czasie mogą Państwo poprosić o dostęp do swoich danych, ich poprawienie, usunięcie lub ograniczenie przetwarzania. Wszystkie przysługujące Państwu prawa znajdują się na tej stronie https://www.bury.com/pl/dzialalnosc/info/rodo/. W celu realizacji powyższych uprawnień prosimy o kontakt na adres rodo@bury.com<mailto:rodo@bury.com>. 3. Państwa dane osobowe przetwarzane są głównie w celu nawiązania lub zachowania współpracy, wykonania umowy. 4. Więcej na ten temat mogą Państwo przeczytać tutaj<https://www.bury.com/pl/dzialalnosc/info/rodo/><https://www.bury.com/pl/dzialalnosc/info/rodo/> Following the entry into force of the General Data Protection Regulation (so- called GDPR), BURY Sp. z o.o. based in Mielec, fulfilling its statutory duty, enables you to become familiar with the information concerning the processing of your personal data by BURY Sp. z o.o. Basic information: 1. BURY Sp. z o. o. based in Mielec is the administrator of personal data and a party (entity, you are employed in, you cooperate with, you are a partner or a representative of, etc.) to the agreement concluded with you, or the entity with which the contact has been established. 2. At any time, you can ask for access to your data, their rectification, deletion or limitation of their processing. All the rights you are entitled to can be found on this website https://www.bury.com/en/business/info/gdpr/. In order to exercise the above rights, please contact us at rodo@bury.com<mailto:rodo@bury.com>. 3. Your personal data are processed mainly in order to establish or maintain cooperation, perform an agreement. 4. More details on this topic can be found here<https://www.bury.com/en/business/info/gdpr/><https://www.bury.com/en/business/info/gdpr/>. _______________________________________________ genivi-diagnostic-log-and-trace mailing list genivi-diagnostic-log-and- trace@lists.genivi.org<mailto:trace@lists.genivi.org> http://lists.genivi.org/mailman/listinfo/genivi-diagnostic-log-and- trace_lists.genivi.org W związku z wejściem w życie przepisów Ogólnego Rozporządzenia o Ochronie Danych Osobowych (tzw. RODO), BURY Sp. z o.o. z siedzibą w Mielcu, spełniając swój ustawowy obowiązek, umożliwia Państwu zapoznanie się z informacjami dotyczącymi przetwarzania Państwa danych osobowych przez BURY Sp. z o.o. Podstawowe informacje: 1. Administratorem danych osobowych jest BURY Sp. z o. o. z siedzibą w Mielcu, będąca stroną łączącej nas z Państwem (podmiotem, w którym Państwo są zatrudnieni, z którym współpracujecie, którego jesteście wspólnikami lub reprezentantami etc.) umowy lub podmiotem, z którym nawiązany został kontakt. 2. W każdym czasie mogą Państwo poprosić o dostęp do swoich danych, ich poprawienie, usunięcie lub ograniczenie przetwarzania. Wszystkie przysługujące Państwu prawa znajdują się na tej stronie https://www.bury.com/pl/dzialalnosc/info/rodo/. W celu realizacji powyższych uprawnień prosimy o kontakt na adres rodo@bury.com. 3. Państwa dane osobowe przetwarzane są głównie w celu nawiązania lub zachowania współpracy, wykonania umowy. 4. Więcej na ten temat mogą Państwo przeczytać tutaj<https://www.bury.com/pl/dzialalnosc/info/rodo/> Following the entry into force of the General Data Protection Regulation (so-called GDPR), BURY Sp. z o.o. based in Mielec, fulfilling its statutory duty, enables you to become familiar with the information concerning the processing of your personal data by BURY Sp. z o.o. Basic information: 1. BURY Sp. z o. o. based in Mielec is the administrator of personal data and a party (entity, you are employed in, you cooperate with, you are a partner or a representative of, etc.) to the agreement concluded with you, or the entity with which the contact has been established. 2. At any time, you can ask for access to your data, their rectification, deletion or limitation of their processing. All the rights you are entitled to can be found on this website https://www.bury.com/en/business/info/gdpr/. In order to exercise the above rights, please contact us at rodo@bury.com. 3. Your personal data are processed mainly in order to establish or maintain cooperation, perform an agreement. 4. More details on this topic can be found here<https://www.bury.com/en/business/info/gdpr/>.