Conti Fahrrad Akku Technik Faden.

Der chaotische Hauptfaden

Moderatoren: Finger, Sven, TDI, Heaterman, duese, Marsupilami72

Benutzeravatar
Hightech
Beiträge: 9093
Registriert: So 11. Aug 2013, 18:37

Re: Conti Fahrrad Akku Technik Faden.

Beitrag von Hightech » Sa 9. Jul 2022, 23:48

Dann ist der Akku leer, bzw. ein Zellenblock ist unter 3V.

tom
Beiträge: 1077
Registriert: Sa 19. Okt 2013, 23:17

Re: Conti Fahrrad Akku Technik Faden.

Beitrag von tom » Sa 9. Jul 2022, 23:51

Hightech hat geschrieben:
Sa 9. Jul 2022, 23:48
Dann ist der Akku leer, bzw. ein Zellenblock ist unter 3V.
Alle Zellen bei 8,4V
Ich habe auch noch mal den BMS-Stecker und die Akku-Anschlüsse getrennt, wie letztes mal. -Keine änderung.

Benutzeravatar
Hightech
Beiträge: 9093
Registriert: So 11. Aug 2013, 18:37

Re: Conti Fahrrad Akku Technik Faden.

Beitrag von Hightech » Sa 9. Jul 2022, 23:53

Dann kann es sein, das die Zellen-Block Spannung zu hoch ist.
Über 4,20V je Block ist der Ausgang nicht aktiv.

tom
Beiträge: 1077
Registriert: Sa 19. Okt 2013, 23:17

Re: Conti Fahrrad Akku Technik Faden.

Beitrag von tom » Sa 9. Jul 2022, 23:56

Hightech hat geschrieben:
Sa 9. Jul 2022, 23:53
Dann kann es sein, das die Zellen-Block Spannung zu hoch ist.
Über 4,20V je Block ist der Ausgang nicht aktiv.

Das heißt ja, das das BMS keinen Ladeschluß macht. Beim Laden ist bei 42,3 V der strom auf bis zu 250mA zurückgegangen, und dann ist der Ladestrom auf 0 zurückgegangen.
Ladestrom war auf 1,5A begrenzt.

soll ich mal den Akku über die Internen Akkuanschlüsse entladen ?

Benutzeravatar
Hightech
Beiträge: 9093
Registriert: So 11. Aug 2013, 18:37

Re: Conti Fahrrad Akku Technik Faden.

Beitrag von Hightech » So 10. Jul 2022, 03:09

Hast du über das BMS geladen?
Dann sollte alles ok sein.

Benutzeravatar
Hightech
Beiträge: 9093
Registriert: So 11. Aug 2013, 18:37

Re: Conti Fahrrad Akku Technik Faden.

Beitrag von Hightech » So 10. Jul 2022, 07:09

Kann mir jemand erklären wie ich bei dem bq34z100 den Strom auslese?
Die einfachen Werte kann ich ja lesen mit read 0x11 usw.
Aber bei den Sub und extended Commands blicke ich nicht durch.

Benutzeravatar
Fritzler
Beiträge: 11736
Registriert: So 11. Aug 2013, 19:42
Wohnort: D:/Berlin/Adlershof/Technologiepark
Kontaktdaten:

Re: Conti Fahrrad Akku Technik Faden.

Beitrag von Fritzler » So 10. Jul 2022, 07:50

Den Befehl für den durschnittlichen Strom auslesen haste ja schon drinne (0x0A/0x0B).
Der Momentanstrom ist doch genauso auslesbar laut DB.
Nur eben mit COMMAND CODE 0x10/0x11.

An die Extended musste da noch nicht ran.

tom
Beiträge: 1077
Registriert: Sa 19. Okt 2013, 23:17

Re: Conti Fahrrad Akku Technik Faden.

Beitrag von tom » So 10. Jul 2022, 08:19

Hightech hat geschrieben:
So 10. Jul 2022, 03:09
Hast du über das BMS geladen?
Dann sollte alles ok sein.
Ja, ich habe über das BMS geladen.

MatthiasBastel
Beiträge: 36
Registriert: Sa 25. Jun 2022, 06:20

Re: Conti Fahrrad Akku Technik Faden.

Beitrag von MatthiasBastel » So 10. Jul 2022, 19:37

Hightech hat geschrieben:
Sa 9. Jul 2022, 23:02
Gelb ist Data+
Violett ist Bat+
Das Oszillogramm ist das Einstecken des Ladegerät in den Akku.


SDS00001.pngSDS00002.pngSDS00003.pngSDS00004.pngSDS00005.png
Hmm, das sieht wirklich nicht besonders hilfreich aus :-( Danke trotzdem!

Mein auf 4,2V umprogrammierter bq "ohne Hysterese" schaltet jetzt bei etwa 4,08-4,14V ab (so war die Spannungsverteilung nach nem Leerlauf) und hat in diesem Fall nicht gebalanced. Ich balance jetzt manuell noch etwas, dann kommt das Pack zu. Ich gebe der Stecker-Firma noch 2 Tage zum Antworten, danach reiß ich den Stecker raus und führ mir ein Kabel mit XT60-Stecker mit Sika-Flex eingedichtet nach draußen.

MatthiasBastel
Beiträge: 36
Registriert: Sa 25. Jun 2022, 06:20

Re: Conti Fahrrad Akku Technik Faden.

Beitrag von MatthiasBastel » Mo 11. Jul 2022, 00:24

Okay, ich hab noch mehr Umbaumöglichkeiten.

a) Ich hatte nen Denk/Messfehler: Der PACK Pin vom bq77PL900 hängt über ne Diode am PACK Anschluss, deswegen reicht das zum einschalten -> Muss nicht umgelötet werden.
b) Scheinbar hat der PIC im Reset wirklich einfach ne zu hohe Stromaufnahme und daher hat bei mir was gequalmt. Es reicht, NUR den PIC auszulöten. Dann läuft die FuelGauge. Standby-Verbrauch liegt irgendwo zwischen 300µA und 2mA - 2-15 Ah pro Jahr. Ich kanns nicht genau messen ohne mein BMS + Kabel durchzutrennen, vielleicht mach ich das mal... Wäre jedenfalls verkraftbar, sofern der Akku 2x im Jahr nachgeladen wird. Da die Packs eh schon alt sind, werden sie ja eher "benutzt" als "gelagert".
c) Anstatt die Dioden am bq77pl900 zu überbrücken um die Fets einzuschalten, können die entsprechenden pins vom abgelöteten PIC auf 3,3V gelegt werden.

Sprich: Mit Heißluft PIC auslöten, mit Fädeldraht 2 Pins gemeinsam (sind nebeneinander) an 3,3V legen (alternativ 2 kleine 0805 Dioden auslöten/brücken) und eine 4-Pin 2,54mm Buchsen/Stiftleiste zum programmieren anbringen -> Fertig ist das funktionierende BMS. Wahlweise mit FuelGauge auf Kosten von 2-15 Ah pro Jahr oder ohne (dann noch einen weiteren Widerstand auslöten).

Bebilderte Anleitung folgt nach Kontrolle, dass das BMS so auch gut tut.

... N minikleines Programm für den PIC würde also eigentlich alles tun: bq EEPROM checken, ggf. umprogrammieren; Fets einschalten, schlafen legen.

Benutzeravatar
Hightech
Beiträge: 9093
Registriert: So 11. Aug 2013, 18:37

Re: Conti Fahrrad Akku Technik Faden.

Beitrag von Hightech » Mo 11. Jul 2022, 01:51

Nur muss man noch das ganze Einschalten, wie macht man das?
Data+ nach GND?
Ich muss zumindest am Ladeanschluss Spannung haben, um die Platine zu starten, und ohne externe 3,3V für den BQ77 geht es bei mir nicht.
Die Stromversorgung 3,3V kommt aus dem BQ77 so wie ich das gesehen hatte, wenn PACK und BAT >8V sind.

Wie bekomme ich raus, wie stark man den Akku belasten kann bevor der in Overload geht?
Eepromwert auslesen und durch den Rsense Wert Teilen?

RSense ist 2mOhm
Ich komme da bei
OC&UVDELAY REGISTER (0x08)
auf 0x09 ( OCD3 OCD1) =55mV.
Das sind 27,5A?
Zuletzt geändert von Hightech am Mo 11. Jul 2022, 02:50, insgesamt 6-mal geändert.

Benutzeravatar
Hightech
Beiträge: 9093
Registriert: So 11. Aug 2013, 18:37

Re: Conti Fahrrad Akku Technik Faden.

Beitrag von Hightech » Mo 11. Jul 2022, 01:56

Fritzler hat geschrieben:
So 10. Jul 2022, 07:50
Den Befehl für den durschnittlichen Strom auslesen haste ja schon drinne (0x0A/0x0B).
Der Momentanstrom ist doch genauso auslesbar laut DB.
Nur eben mit COMMAND CODE 0x10/0x11.

An die Extended musste da noch nicht ran.
Das verstehe ich nicht:
Ist das doppelt?

Code: Alles auswählen

7.2.2.1 AtRate(): 0X10/0x11
The AtRate() read-/write-word function is the first half of a two-function call-set used to set the AtRate value used
in calculations made by the AtRateTimeToEmpty() function. The AtRate() units are in mA.
The AtRate() value is a signed integer and both positive and negative values will be interpreted as a discharge
current value. The AtRateTimeToEmpty() function returns the predicted operating time at the AtRate value of
discharge. The default value for AtRate() is zero and will force AtRate() to return 65535.

7.2.2.3 Current(): 0x10/0x11
This read-only command pair returns a signed integer value that is the current flow through the sense resistor.
It is updated every 1 second. Units are 1 mA per bit except if X10 mode is selected. In X10 mode, units are 10
mA per bit.with units of 1mA. However, if PackConfiguration [SCALED] is set then the units have been scaled
through the calibration process. The actual scale is not set in the device and SCALED is just an indicator flag.

Benutzeravatar
Hightech
Beiträge: 9093
Registriert: So 11. Aug 2013, 18:37

Re: Conti Fahrrad Akku Technik Faden.

Beitrag von Hightech » Mo 11. Jul 2022, 03:06

Am Eingang der Schaltung, dort wo Can L/H und Data+/- angeschlossen sind ist der
TPS54260
Das ist ein Weitbereich Spannungswandler.
Ich vermute, das der die Spannung für den PIC und den BQ34 zur Verfügung stellt. Der BQ34 wird vom BAT+ gespeist.
Den müsste man noch aktivieren, am Besten so, das der mit Data+ aktiv ist.
Dann hätte man einen prima Start/Stop.
Leider verschwindet die Ansteuerung in einem Dioden/Transistordickicht.

Benutzeravatar
Hightech
Beiträge: 9093
Registriert: So 11. Aug 2013, 18:37

Re: Conti Fahrrad Akku Technik Faden.

Beitrag von Hightech » Mo 11. Jul 2022, 07:01

Verwegene Idee:
Den Discharge Fet nutzen zur Strombegrenzung über eine PWM?

MatthiasBastel
Beiträge: 36
Registriert: Sa 25. Jun 2022, 06:20

Re: Conti Fahrrad Akku Technik Faden.

Beitrag von MatthiasBastel » Mo 11. Jul 2022, 10:04

Nein, der PIC und die FuelGauge werden von dem kleinen LDO auf der Rückseite in der Nähe des Balancer-Anschlusses produziert (der kleine QFN-8).
Ich habe jetzt auch funktionierendes Balancing - eventuell hab ich den ersten Chip einfach gegrillt, andererseits hab ich die OVP auf 4,25V gestellt, weil die bq's da scheinbar eh alle nen Drift nach unten haben. Hab gerade Fotos gemacht und schreibe heut im Laufe des Tages nen Post dazu.

Zum "Starten" nach Anschluss einfach 30+V auf den PACK-Anschluss (also Ausgang des Akkus) legen, geht von draußen, dann macht der BQ die Fets auf (Das geht natürlich nur, wenn die Dioden überbrückt sind oder die Gate-Fets vom PIC aufgesteuert werden)

MatthiasBastel
Beiträge: 36
Registriert: Sa 25. Jun 2022, 06:20

Re: Conti Fahrrad Akku Technik Faden.

Beitrag von MatthiasBastel » Mo 11. Jul 2022, 13:31


Benutzeravatar
Hightech
Beiträge: 9093
Registriert: So 11. Aug 2013, 18:37

Re: Conti Fahrrad Akku Technik Faden.

Beitrag von Hightech » Mo 11. Jul 2022, 15:44

Super!!! Danke!!!!!
MatthiasBastel hat geschrieben:
Mo 11. Jul 2022, 13:31
Sooo, meine Umbauanleitung:

https://matthias-larisch.de/2022/07/11/ ... ttery.html

Benutzeravatar
Fritzler
Beiträge: 11736
Registriert: So 11. Aug 2013, 19:42
Wohnort: D:/Berlin/Adlershof/Technologiepark
Kontaktdaten:

Re: Conti Fahrrad Akku Technik Faden.

Beitrag von Fritzler » Mo 11. Jul 2022, 16:25

Hightech hat geschrieben:
Mo 11. Jul 2022, 01:56
Fritzler hat geschrieben:
So 10. Jul 2022, 07:50
Den Befehl für den durschnittlichen Strom auslesen haste ja schon drinne (0x0A/0x0B).
Der Momentanstrom ist doch genauso auslesbar laut DB.
Nur eben mit COMMAND CODE 0x10/0x11.

An die Extended musste da noch nicht ran.
Das verstehe ich nicht:
Ist das doppelt?

Code: Alles auswählen

7.2.2.1 AtRate(): 0X10/0x11

7.2.2.3 Current(): 0x10/0x11
Klingt durchaus unverständlich, aber ich interpretiert das so:
Lesend: AtRate = Current, also der Strom durch den Shunt.
Sobald du aber einmal AtRate schreibst berechnet der IC die Entladedauer in min damit (AtRateTimeToEmpty).

Abers gibt wohl nochn Weg an den Momentanstrom zu kommen:
Über die Commands, da gibts nen CURRENT Befehl (Tabelle 7-2)
Über I2C senden: <Start><BqAddr+W><0x00><0x18><0x00><Stop>
Über I2C senden:<Start><BqAddr+W><0x00><Stop><Start><BqAddr+R><Read><Read><Stop>
Dann haste nen int16 in mA

Benutzeravatar
Hightech
Beiträge: 9093
Registriert: So 11. Aug 2013, 18:37

Re: Conti Fahrrad Akku Technik Faden.

Beitrag von Hightech » Mi 13. Jul 2022, 00:48

E4F3B854-C6E8-484B-A7DB-C28F071DB830.jpeg
B994E2E9-CE02-461A-9C02-CA59D225071B.jpeg
19904BC2-514D-4821-9DF8-67D7372A9002.jpeg
F16DD164-FE7E-4FC3-8AFD-865A5AC3DCC7.jpeg
PL5.png
Dateianhänge
PL4-2.png
128635C3-5DBF-4D76-A83F-8424217B9092.jpeg

MatthiasBastel
Beiträge: 36
Registriert: Sa 25. Jun 2022, 06:20

Re: Conti Fahrrad Akku Technik Faden.

Beitrag von MatthiasBastel » Mi 13. Jul 2022, 10:34

Hui, hast du das noch in besserer Qualität und Auflösung? Ein Scanner geht richtig gut :-) Aber yay, das wäre ganz toll, da nochmal ein paar Details abzuzeichnen. Andererseits bin ich mit meinem beschriebenen Umbau sehr zufrieden: Tut alles wie es soll.

Anschluss mach ich über 6,3mm Flachstecker, die passen gut rein. Den "I2C"-Stecker hab ich einfach nach dem Einstecken mit Heißkleber zusammengepappt, so kann ich die 3 Pins auf einmal ein/ausstecken und jederzeit eine Akkudiagnose durchführen :-)

Benutzeravatar
Hightech
Beiträge: 9093
Registriert: So 11. Aug 2013, 18:37

Re: Conti Fahrrad Akku Technik Faden.

Beitrag von Hightech » Mi 13. Jul 2022, 14:34

Ich mach es normal in schön :lol:
PL1000.png
PL2000.png
PL4-1-1.png
PL4-2-2.png

MatthiasBastel
Beiträge: 36
Registriert: Sa 25. Jun 2022, 06:20

Re: Conti Fahrrad Akku Technik Faden.

Beitrag von MatthiasBastel » Mi 13. Jul 2022, 21:51

Sorry, Hightech, aber die Bilder sind alle unterschiedlich groß und perspektivisch verzerrt und nicht hochauflösend genug. Hast du einen Scanner, auf den du sie auflegen kannst? Das erspart unglaublich viel Entzerr-Arbeit... Wenn du das nicht hast, kannst du sie mir gerne schicken oder nen Nachbarn fragen ?

Benutzeravatar
Hightech
Beiträge: 9093
Registriert: So 11. Aug 2013, 18:37

Re: Conti Fahrrad Akku Technik Faden.

Beitrag von Hightech » Do 14. Jul 2022, 06:41

Die letzten Bilder sind vom Scanner, nur will der ums Verrecken nicht über 300dpi
Den 2.Layer färbe ich nochmal ein für optimalen Kontrast.

MatthiasBastel
Beiträge: 36
Registriert: Sa 25. Jun 2022, 06:20

Re: Conti Fahrrad Akku Technik Faden.

Beitrag von MatthiasBastel » Do 14. Jul 2022, 07:25

Wie gesagt, schick sie mir an die Wurzener Adresse wo schon 4 Akkus hingingen in nem kleinen Luftpolsterumschlag als Großbrief zu 1,60€... Kann dir die auch gern überweisen :D

Benutzeravatar
Hightech
Beiträge: 9093
Registriert: So 11. Aug 2013, 18:37

Re: Conti Fahrrad Akku Technik Faden.

Beitrag von Hightech » Sa 16. Jul 2022, 16:25

Ich schnüffel gerade am CAN Bus, aber am 48V-System.
Vielleicht kommt man damit weiter.

Das UDS Discovery hat das gefunden:

Code: Alles auswählen

Identified diagnostics:

+------------+------------+
| CLIENT ID  | SERVER ID  |
+------------+------------+
| 0x00000311 | 0x00000102 |
| 0x00000337 | 0x00000102 |
| 0x00000487 | 0x00000102 |
| 0x000004ac | 0x00000102 |
| 0x00000550 | 0x00000551 |
| 0x000007d1 | 0x000007e1 |
| 0x000007d0 | 0x000007e0 |
| 0x000007d1 | 0x000007e1 |
| 0x000007ff | 0x000007e1 |
+------------+------------+

Code: Alles auswählen

pi@can-pi:~/caringcaribou/tool $ ./cc.py -i can0 uds services 0x7d1 0x7e1

-------------------
CARING CARIBOU v0.3
-------------------

Loaded module 'uds'

Probing service 0xff (255/255): found 16
Done!

Supported service 0x-2e: Unknown service
Supported service 0x-3e: Unknown service
Supported service 0x10: DIAGNOSTIC_SESSION_CONTROL
Supported service 0x11: ECU_RESET
Supported service 0x14: CLEAR_DIAGNOSTIC_INFORMATION
Supported service 0x19: READ_DTC_INFORMATION
Supported service 0x22: READ_DATA_BY_IDENTIFIER
Supported service 0x27: SECURITY_ACCESS
Supported service 0x28: COMMUNICATION_CONTROL
Supported service 0x2a: READ_DATA_BY_PERIODIC_IDENTIFIER
Supported service 0x2e: WRITE_DATA_BY_IDENTIFIER
Supported service 0x2f: INPUT_OUTPUT_CONTROL_BY_IDENTIFIER
Supported service 0x31: ROUTINE_CONTROL
Supported service 0x3e: TESTER_PRESENT
Supported service 0x85: CONTROL_DTC_SETTING
Supported service 0x86: RESPONSE_ON_EVENT

Code: Alles auswählen

pi@can-pi:~/caringcaribou/tool $ ./cc.py -i can0 uds services 0x7ff 0x7e1

-------------------
CARING CARIBOU v0.3
-------------------

Loaded module 'uds'

Probing service 0xff (255/255): found 14
Done!

Supported service 0x10: DIAGNOSTIC_SESSION_CONTROL
Supported service 0x11: ECU_RESET
Supported service 0x14: CLEAR_DIAGNOSTIC_INFORMATION
Supported service 0x19: READ_DTC_INFORMATION
Supported service 0x22: READ_DATA_BY_IDENTIFIER
Supported service 0x27: SECURITY_ACCESS
Supported service 0x28: COMMUNICATION_CONTROL
Supported service 0x2a: READ_DATA_BY_PERIODIC_IDENTIFIER
Supported service 0x2e: WRITE_DATA_BY_IDENTIFIER
Supported service 0x2f: INPUT_OUTPUT_CONTROL_BY_IDENTIFIER
Supported service 0x31: ROUTINE_CONTROL
Supported service 0x3e: TESTER_PRESENT
Supported service 0x85: CONTROL_DTC_SETTING
Supported service 0x86: RESPONSE_ON_EVENT

Code: Alles auswählen

pi@can-pi:~/caringcaribou/tool $ ./cc.py -i can0 uds services 0x7d0 0x7e0

-------------------
CARING CARIBOU v0.3
-------------------

Loaded module 'uds'

Probing service 0xff (255/255): found 11
Done!

Supported service 0x10: DIAGNOSTIC_SESSION_CONTROL
Supported service 0x11: ECU_RESET
Supported service 0x14: CLEAR_DIAGNOSTIC_INFORMATION
Supported service 0x19: READ_DTC_INFORMATION
Supported service 0x22: READ_DATA_BY_IDENTIFIER
Supported service 0x27: SECURITY_ACCESS
Supported service 0x28: COMMUNICATION_CONTROL
Supported service 0x2e: WRITE_DATA_BY_IDENTIFIER
Supported service 0x31: ROUTINE_CONTROL
Supported service 0x3e: TESTER_PRESENT
Supported service 0x85: CONTROL_DTC_SETTING


Code: Alles auswählen

pi@can-pi:~/caringcaribou/tool $ ./cc.py -i can0 uds services 0x7d1 0x7e1

-------------------
CARING CARIBOU v0.3
-------------------

Loaded module 'uds'

Probing service 0xff (255/255): found 15
Done!

Supported service 0x-1e: Unknown service
Supported service 0x10: DIAGNOSTIC_SESSION_CONTROL
Supported service 0x11: ECU_RESET
Supported service 0x14: CLEAR_DIAGNOSTIC_INFORMATION
Supported service 0x19: READ_DTC_INFORMATION
Supported service 0x22: READ_DATA_BY_IDENTIFIER
Supported service 0x27: SECURITY_ACCESS
Supported service 0x28: COMMUNICATION_CONTROL
Supported service 0x2a: READ_DATA_BY_PERIODIC_IDENTIFIER
Supported service 0x2e: WRITE_DATA_BY_IDENTIFIER
Supported service 0x2f: INPUT_OUTPUT_CONTROL_BY_IDENTIFIER
Supported service 0x31: ROUTINE_CONTROL
Supported service 0x3e: TESTER_PRESENT
Supported service 0x85: CONTROL_DTC_SETTING
Supported service 0x86: RESPONSE_ON_EVENT

Code: Alles auswählen

pi@can-pi:~/caringcaribou/tool $ ./cc.py -i can0 uds services 0x550 0x551

-------------------
CARING CARIBOU v0.3
-------------------

Loaded module 'uds'

Probing service 0xff (255/255): found 14
Done!

Supported service 0x-3e: Unknown service
Supported service 0x-1e: Unknown service
Supported service 0x10: DIAGNOSTIC_SESSION_CONTROL
Supported service 0x11: ECU_RESET
Supported service 0x14: CLEAR_DIAGNOSTIC_INFORMATION
Supported service 0x19: READ_DTC_INFORMATION
Supported service 0x22: READ_DATA_BY_IDENTIFIER
Supported service 0x27: SECURITY_ACCESS
Supported service 0x28: COMMUNICATION_CONTROL
Supported service 0x2e: WRITE_DATA_BY_IDENTIFIER
Supported service 0x2f: INPUT_OUTPUT_CONTROL_BY_IDENTIFIER
Supported service 0x31: ROUTINE_CONTROL
Supported service 0x3e: TESTER_PRESENT
Supported service 0x85: CONTROL_DTC_SETTING

pi@can-pi:~/caringcaribou/tool $ 

Hier passiert sogar was, der Motor beginnt zu zucken und dann geht das Steuergerät nach kurzer Zeit aus:

Code: Alles auswählen


-------------------
CARING CARIBOU v0.3
-------------------

Loaded module 'xcp'

Starting XCP discovery
Sending XCP connect to 0x01a7
Found XCP (with a bad reply) at arbitration ID 0x1a7, reply at 0x1507
Received error message:
Timestamp: 1657981275.876678    ID: 00001507    X                DLC:  8    fe 01 dc 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error
Sending XCP connect to 0x01b1
Found XCP (with a bad reply) at arbitration ID 0x1b1, reply at 0x1507
Received error message:
Timestamp: 1657981276.926007    ID: 00001507    X                DLC:  8    fe 01 d2 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error
Sending XCP connect to 0x01b3
Found XCP (with a bad reply) at arbitration ID 0x1b3, reply at 0x1507
Received error message:
Timestamp: 1657981277.046040    ID: 00001507    X                DLC:  8    fe 01 ee 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error
Sending XCP connect to 0x01be
Found XCP (with a bad reply) at arbitration ID 0x1be, reply at 0x1507
Received error message:
Timestamp: 1657981278.176572    ID: 00001507    X                DLC:  8    fe 01 d0 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error

Found XCP (with a bad reply) at arbitration ID 0x1be, reply at 0x1507
Received error message:
Timestamp: 1657981278.186043    ID: 00001507    X                DLC:  8    fe 01 d2 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error
> DECODE CONNECT RESPONSE
Timestamp: 1657981278.196555    ID: 00001507    X                DLC:  8    ff 01 d5 00 00 00 00 00     Channel: can0
--------------------
Resource protection status

CAL/PAG     True
X (bit 1)   False
DAQ         False
STIM        False
PGM         False
X (bit 5)   False
X (bit 6)   False
X (bit 7)   False
--------------------
COMM_MODE_BASIC

BYTE_ORDER              1
ADDRESS_GRANULARITY_0   0
ADDRESS_GRANULARITY_1   1
X (bit 3)               0
X (bit 4)               1
X (bit 5)               0
SLAVE_BLOCK_MODE        1
OPTIONAL                1

Address granularity: 1 byte(s) per address
--------------------
Max CTO message length: 0 bytes
Max DTO message length: 0 bytes
Protocol layer version: 0
Transport layer version: 0
Found XCP at arb ID 0x01be, reply at 0x1507
####################


> DECODE CONNECT RESPONSE
Timestamp: 1657981278.225978    ID: 00001507    X                DLC:  8    ff 01 d7 00 00 00 00 00     Channel: can0
--------------------
Resource protection status

CAL/PAG     True
X (bit 1)   False
DAQ         False
STIM        False
PGM         False
X (bit 5)   False
X (bit 6)   False
X (bit 7)   False
--------------------
COMM_MODE_BASIC

BYTE_ORDER              1
ADDRESS_GRANULARITY_0   1
ADDRESS_GRANULARITY_1   1
X (bit 3)               0
X (bit 4)               1
X (bit 5)               0
SLAVE_BLOCK_MODE        1
OPTIONAL                1

Address granularity: 4 byte(s) per address
--------------------
Max CTO message length: 0 bytes
Max DTO message length: 0 bytes
Protocol layer version: 0
Transport layer version: 0
Found XCP at arb ID 0x01be, reply at 0x1507
####################



Found XCP (with a bad reply) at arbitration ID 0x1be, reply at 0x1507
Received error message:
Timestamp: 1657981278.236648    ID: 00001507    X                DLC:  8    fe 01 d2 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error
Sending XCP connect to 0x01c0
Found XCP (with a bad reply) at arbitration ID 0x1c0, reply at 0x1507
Received error message:
Timestamp: 1657981278.446036    ID: 00001507    X                DLC:  8    fe 01 dc 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error
Sending XCP connect to 0x01c2> DECODE CONNECT RESPONSE
Timestamp: 1657981278.636564    ID: 00001507    X                DLC:  8    ff 01 ad 00 00 00 00 00     Channel: can0
--------------------
Resource protection status

CAL/PAG     True
X (bit 1)   False
DAQ         False
STIM        False
PGM         False
X (bit 5)   False
X (bit 6)   False
X (bit 7)   False
--------------------
COMM_MODE_BASIC

BYTE_ORDER              1
ADDRESS_GRANULARITY_0   0
ADDRESS_GRANULARITY_1   1
X (bit 3)               1
X (bit 4)               0
X (bit 5)               1
SLAVE_BLOCK_MODE        0
OPTIONAL                1

Address granularity: 1 byte(s) per address
--------------------
Max CTO message length: 0 bytes
Max DTO message length: 0 bytes
Protocol layer version: 0
Transport layer version: 0
Found XCP at arb ID 0x01c2, reply at 0x1507
####################


Sending XCP connect to 0x01cf> DECODE CONNECT RESPONSE
Timestamp: 1657981279.966017    ID: 00001507    X                DLC:  8    ff 01 d5 00 00 00 00 00     Channel: can0
--------------------
Resource protection status

CAL/PAG     True
X (bit 1)   False
DAQ         False
STIM        False
PGM         False
X (bit 5)   False
X (bit 6)   False
X (bit 7)   False
--------------------
COMM_MODE_BASIC

BYTE_ORDER              1
ADDRESS_GRANULARITY_0   0
ADDRESS_GRANULARITY_1   1
X (bit 3)               0
X (bit 4)               1
X (bit 5)               0
SLAVE_BLOCK_MODE        1
OPTIONAL                1

Address granularity: 1 byte(s) per address
--------------------
Max CTO message length: 0 bytes
Max DTO message length: 0 bytes
Protocol layer version: 0
Transport layer version: 0
Found XCP at arb ID 0x01cf, reply at 0x1507
####################


> DECODE CONNECT RESPONSE
Timestamp: 1657981279.976231    ID: 00001507    X                DLC:  8    ff 01 d2 00 00 00 00 00     Channel: can0
--------------------
Resource protection status

CAL/PAG     True
X (bit 1)   False
DAQ         False
STIM        False
PGM         False
X (bit 5)   False
X (bit 6)   False
X (bit 7)   False
--------------------
COMM_MODE_BASIC

BYTE_ORDER              0
ADDRESS_GRANULARITY_0   1
ADDRESS_GRANULARITY_1   0
X (bit 3)               0
X (bit 4)               1
X (bit 5)               0
SLAVE_BLOCK_MODE        1
OPTIONAL                1

Address granularity: 4 byte(s) per address
--------------------
Max CTO message length: 0 bytes
Max DTO message length: 0 bytes
Protocol layer version: 0
Transport layer version: 0
Found XCP at arb ID 0x01cf, reply at 0x1507
####################


Sending XCP connect to 0x01d4> DECODE CONNECT RESPONSE
Timestamp: 1657981280.525948    ID: 00001507    X                DLC:  8    ff 01 d2 00 00 00 00 00     Channel: can0
--------------------
Resource protection status

CAL/PAG     True
X (bit 1)   False
DAQ         False
STIM        False
PGM         False
X (bit 5)   False
X (bit 6)   False
X (bit 7)   False
--------------------
COMM_MODE_BASIC

BYTE_ORDER              0
ADDRESS_GRANULARITY_0   1
ADDRESS_GRANULARITY_1   0
X (bit 3)               0
X (bit 4)               1
X (bit 5)               0
SLAVE_BLOCK_MODE        1
OPTIONAL                1

Address granularity: 4 byte(s) per address
--------------------
Max CTO message length: 0 bytes
Max DTO message length: 0 bytes
Protocol layer version: 0
Transport layer version: 0
Found XCP at arb ID 0x01d4, reply at 0x1507
####################


Sending XCP connect to 0x01da
Found XCP (with a bad reply) at arbitration ID 0x1da, reply at 0x1507
Received error message:
Timestamp: 1657981281.136598    ID: 00001507    X                DLC:  8    fe 01 d2 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error
Sending XCP connect to 0x01dd
Found XCP (with a bad reply) at arbitration ID 0x1dd, reply at 0x1507
Received error message:
Timestamp: 1657981281.436592    ID: 00001507    X                DLC:  8    fe 01 f0 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error
Sending XCP connect to 0x01e7> DECODE CONNECT RESPONSE
Timestamp: 1657981282.445905    ID: 00001507    X                DLC:  8    ff 01 b7 00 00 00 00 00     Channel: can0
--------------------
Resource protection status

CAL/PAG     True
X (bit 1)   False
DAQ         False
STIM        False
PGM         False
X (bit 5)   False
X (bit 6)   False
X (bit 7)   False
--------------------
COMM_MODE_BASIC

BYTE_ORDER              1
ADDRESS_GRANULARITY_0   1
ADDRESS_GRANULARITY_1   1
X (bit 3)               0
X (bit 4)               1
X (bit 5)               1
SLAVE_BLOCK_MODE        0
OPTIONAL                1

Address granularity: 4 byte(s) per address
--------------------
Max CTO message length: 0 bytes
Max DTO message length: 0 bytes
Protocol layer version: 0
Transport layer version: 0
Found XCP at arb ID 0x01e7, reply at 0x1507
####################


Sending XCP connect to 0x01f1
Found XCP (with a bad reply) at arbitration ID 0x1f1, reply at 0x1507
Received error message:
Timestamp: 1657981283.436549    ID: 00001507    X                DLC:  8    fe 01 a0 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error
Sending XCP connect to 0x01f3
Found XCP (with a bad reply) at arbitration ID 0x1f3, reply at 0x1507
Received error message:
Timestamp: 1657981283.656512    ID: 00001507    X                DLC:  8    fe 01 c8 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error

Found XCP (with a bad reply) at arbitration ID 0x1f3, reply at 0x1507
Received error message:
Timestamp: 1657981283.665966    ID: 00001507    X                DLC:  8    fe 01 d2 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error
Sending XCP connect to 0x01f5> DECODE CONNECT RESPONSE
Timestamp: 1657981283.856461    ID: 00001507    X                DLC:  8    ff 01 d5 00 00 00 00 00     Channel: can0
--------------------
Resource protection status

CAL/PAG     True
X (bit 1)   False
DAQ         False
STIM        False
PGM         False
X (bit 5)   False
X (bit 6)   False
X (bit 7)   False
--------------------
COMM_MODE_BASIC

BYTE_ORDER              1
ADDRESS_GRANULARITY_0   0
ADDRESS_GRANULARITY_1   1
X (bit 3)               0
X (bit 4)               1
X (bit 5)               0
SLAVE_BLOCK_MODE        1
OPTIONAL                1

Address granularity: 1 byte(s) per address
--------------------
Max CTO message length: 0 bytes
Max DTO message length: 0 bytes
Protocol layer version: 0
Transport layer version: 0
Found XCP at arb ID 0x01f5, reply at 0x1507
####################


Sending XCP connect to 0x01f8
Found XCP (with a bad reply) at arbitration ID 0x1f8, reply at 0x1507
Received error message:
Timestamp: 1657981284.146238    ID: 00001507    X                DLC:  8    fe 01 cb 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error
> DECODE CONNECT RESPONSE
Timestamp: 1657981284.156471    ID: 00001507    X                DLC:  8    ff 01 d7 00 00 00 00 00     Channel: can0
--------------------
Resource protection status

CAL/PAG     True
X (bit 1)   False
DAQ         False
STIM        False
PGM         False
X (bit 5)   False
X (bit 6)   False
X (bit 7)   False
--------------------
COMM_MODE_BASIC

BYTE_ORDER              1
ADDRESS_GRANULARITY_0   1
ADDRESS_GRANULARITY_1   1
X (bit 3)               0
X (bit 4)               1
X (bit 5)               0
SLAVE_BLOCK_MODE        1
OPTIONAL                1

Address granularity: 4 byte(s) per address
--------------------
Max CTO message length: 0 bytes
Max DTO message length: 0 bytes
Protocol layer version: 0
Transport layer version: 0
Found XCP at arb ID 0x01f8, reply at 0x1507
####################


Sending XCP connect to 0x01f9> DECODE CONNECT RESPONSE
Timestamp: 1657981284.236639    ID: 00001507    X                DLC:  8    ff 01 d7 00 00 00 00 00     Channel: can0
--------------------
Resource protection status

CAL/PAG     True
X (bit 1)   False
DAQ         False
STIM        False
PGM         False
X (bit 5)   False
X (bit 6)   False
X (bit 7)   False
--------------------
COMM_MODE_BASIC

BYTE_ORDER              1
ADDRESS_GRANULARITY_0   1
ADDRESS_GRANULARITY_1   1
X (bit 3)               0
X (bit 4)               1
X (bit 5)               0
SLAVE_BLOCK_MODE        1
OPTIONAL                1

Address granularity: 4 byte(s) per address
--------------------
Max CTO message length: 0 bytes
Max DTO message length: 0 bytes
Protocol layer version: 0
Transport layer version: 0
Found XCP at arb ID 0x01f9, reply at 0x1507
####################


Sending XCP connect to 0x01fd> DECODE CONNECT RESPONSE
Timestamp: 1657981284.716543    ID: 00001507    X                DLC:  8    ff 01 df 00 00 00 00 00     Channel: can0
--------------------
Resource protection status

CAL/PAG     True
X (bit 1)   False
DAQ         False
STIM        False
PGM         False
X (bit 5)   False
X (bit 6)   False
X (bit 7)   False
--------------------
COMM_MODE_BASIC

BYTE_ORDER              1
ADDRESS_GRANULARITY_0   1
ADDRESS_GRANULARITY_1   1
X (bit 3)               1
X (bit 4)               1
X (bit 5)               0
SLAVE_BLOCK_MODE        1
OPTIONAL                1

Address granularity: 4 byte(s) per address
--------------------
Max CTO message length: 0 bytes
Max DTO message length: 0 bytes
Protocol layer version: 0
Transport layer version: 0
Found XCP at arb ID 0x01fd, reply at 0x1507
####################


Sending XCP connect to 0x01ff
Found XCP (with a bad reply) at arbitration ID 0x1ff, reply at 0x1507
Received error message:
Timestamp: 1657981284.845936    ID: 00001507    X                DLC:  8    fe 01 c3 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error
Sending XCP connect to 0x0208> DECODE CONNECT RESPONSE
Timestamp: 1657981285.796503    ID: 00001507    X                DLC:  8    ff 01 d2 00 00 00 00 00     Channel: can0
--------------------
Resource protection status

CAL/PAG     True
X (bit 1)   False
DAQ         False
STIM        False
PGM         False
X (bit 5)   False
X (bit 6)   False
X (bit 7)   False
--------------------
COMM_MODE_BASIC

BYTE_ORDER              0
ADDRESS_GRANULARITY_0   1
ADDRESS_GRANULARITY_1   0
X (bit 3)               0
X (bit 4)               1
X (bit 5)               0
SLAVE_BLOCK_MODE        1
OPTIONAL                1

Address granularity: 4 byte(s) per address
--------------------
Max CTO message length: 0 bytes
Max DTO message length: 0 bytes
Protocol layer version: 0
Transport layer version: 0
Found XCP at arb ID 0x0208, reply at 0x1507
####################



Found XCP (with a bad reply) at arbitration ID 0x208, reply at 0x1507
Received error message:
Timestamp: 1657981285.817601    ID: 00001507    X                DLC:  8    fe 01 d2 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error

Found XCP (with a bad reply) at arbitration ID 0x208, reply at 0x1507
Received error message:
Timestamp: 1657981285.825862    ID: 00001507    X                DLC:  8    fe 01 d5 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error
Sending XCP connect to 0x0209> DECODE CONNECT RESPONSE
Timestamp: 1657981285.885941    ID: 00001507    X                DLC:  8    ff 01 d7 00 00 00 00 00     Channel: can0
--------------------
Resource protection status

CAL/PAG     True
X (bit 1)   False
DAQ         False
STIM        False
PGM         False
X (bit 5)   False
X (bit 6)   False
X (bit 7)   False
--------------------
COMM_MODE_BASIC

BYTE_ORDER              1
ADDRESS_GRANULARITY_0   1
ADDRESS_GRANULARITY_1   1
X (bit 3)               0
X (bit 4)               1
X (bit 5)               0
SLAVE_BLOCK_MODE        1
OPTIONAL                1

Address granularity: 4 byte(s) per address
--------------------
Max CTO message length: 0 bytes
Max DTO message length: 0 bytes
Protocol layer version: 0
Transport layer version: 0
Found XCP at arb ID 0x0209, reply at 0x1507
####################


Sending XCP connect to 0x0210> DECODE CONNECT RESPONSE
Timestamp: 1657981286.636509    ID: 00001507    X                DLC:  8    ff 01 f0 00 00 00 00 00     Channel: can0
--------------------
Resource protection status

CAL/PAG     True
X (bit 1)   False
DAQ         False
STIM        False
PGM         False
X (bit 5)   False
X (bit 6)   False
X (bit 7)   False
--------------------
COMM_MODE_BASIC

BYTE_ORDER              0
ADDRESS_GRANULARITY_0   0
ADDRESS_GRANULARITY_1   0
X (bit 3)               0
X (bit 4)               1
X (bit 5)               1
SLAVE_BLOCK_MODE        1
OPTIONAL                1

Address granularity: 1 byte(s) per address
--------------------
Max CTO message length: 0 bytes
Max DTO message length: 0 bytes
Protocol layer version: 0
Transport layer version: 0
Found XCP at arb ID 0x0210, reply at 0x1507
####################


Sending XCP connect to 0x0211
Found XCP (with a bad reply) at arbitration ID 0x211, reply at 0x1507
Received error message:
Timestamp: 1657981286.707021    ID: 00001507    X                DLC:  8    fe 01 cb 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error
Sending XCP connect to 0x0212
Found XCP (with a bad reply) at arbitration ID 0x212, reply at 0x1507
Received error message:
Timestamp: 1657981286.876471    ID: 00001507    X                DLC:  8    fe 01 d5 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error
Sending XCP connect to 0x0213
Found XCP (with a bad reply) at arbitration ID 0x213, reply at 0x1507
Received error message:
Timestamp: 1657981286.956414    ID: 00001507    X                DLC:  8    fe 01 d5 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error
> DECODE CONNECT RESPONSE
Timestamp: 1657981286.965930    ID: 00001507    X                DLC:  8    ff 01 d7 00 00 00 00 00     Channel: can0
--------------------
Resource protection status

CAL/PAG     True
X (bit 1)   False
DAQ         False
STIM        False
PGM         False
X (bit 5)   False
X (bit 6)   False
X (bit 7)   False
--------------------
COMM_MODE_BASIC

BYTE_ORDER              1
ADDRESS_GRANULARITY_0   1
ADDRESS_GRANULARITY_1   1
X (bit 3)               0
X (bit 4)               1
X (bit 5)               0
SLAVE_BLOCK_MODE        1
OPTIONAL                1

Address granularity: 4 byte(s) per address
--------------------
Max CTO message length: 0 bytes
Max DTO message length: 0 bytes
Protocol layer version: 0
Transport layer version: 0
Found XCP at arb ID 0x0213, reply at 0x1507
####################


Sending XCP connect to 0x0214> DECODE CONNECT RESPONSE
Timestamp: 1657981287.065836    ID: 00001507    X                DLC:  8    ff 01 d0 00 00 00 00 00     Channel: can0
--------------------
Resource protection status

CAL/PAG     True
X (bit 1)   False
DAQ         False
STIM        False
PGM         False
X (bit 5)   False
X (bit 6)   False
X (bit 7)   False
--------------------
COMM_MODE_BASIC

BYTE_ORDER              0
ADDRESS_GRANULARITY_0   0
ADDRESS_GRANULARITY_1   0
X (bit 3)               0
X (bit 4)               1
X (bit 5)               0
SLAVE_BLOCK_MODE        1
OPTIONAL                1

Address granularity: 1 byte(s) per address
--------------------
Max CTO message length: 0 bytes
Max DTO message length: 0 bytes
Protocol layer version: 0
Transport layer version: 0
Found XCP at arb ID 0x0214, reply at 0x1507
####################


Sending XCP connect to 0x0216> DECODE CONNECT RESPONSE
Timestamp: 1657981287.236432    ID: 00001507    X                DLC:  8    ff 01 aa 00 00 00 00 00     Channel: can0
--------------------
Resource protection status

CAL/PAG     True
X (bit 1)   False
DAQ         False
STIM        False
PGM         False
X (bit 5)   False
X (bit 6)   False
X (bit 7)   False
--------------------
COMM_MODE_BASIC

BYTE_ORDER              0
ADDRESS_GRANULARITY_0   1
ADDRESS_GRANULARITY_1   0
X (bit 3)               1
X (bit 4)               0
X (bit 5)               1
SLAVE_BLOCK_MODE        0
OPTIONAL                1

Address granularity: 4 byte(s) per address
--------------------
Max CTO message length: 0 bytes
Max DTO message length: 0 bytes
Protocol layer version: 0
Transport layer version: 0
Found XCP at arb ID 0x0216, reply at 0x1507
####################


Sending XCP connect to 0x0226
Found XCP (with a bad reply) at arbitration ID 0x226, reply at 0x1507
Received error message:
Timestamp: 1657981288.906987    ID: 00001507    X                DLC:  8    fe 01 d0 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error
Sending XCP connect to 0x0227
Found XCP (with a bad reply) at arbitration ID 0x227, reply at 0x1507
Received error message:
Timestamp: 1657981288.956370    ID: 00001507    X                DLC:  8    fe 01 d2 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error
Sending XCP connect to 0x0228> DECODE CONNECT RESPONSE
Timestamp: 1657981289.136454    ID: 00001507    X                DLC:  8    ff 01 d0 00 00 00 00 00     Channel: can0
--------------------
Resource protection status

CAL/PAG     True
X (bit 1)   False
DAQ         False
STIM        False
PGM         False
X (bit 5)   False
X (bit 6)   False
X (bit 7)   False
--------------------
COMM_MODE_BASIC

BYTE_ORDER              0
ADDRESS_GRANULARITY_0   0
ADDRESS_GRANULARITY_1   0
X (bit 3)               0
X (bit 4)               1
X (bit 5)               0
SLAVE_BLOCK_MODE        1
OPTIONAL                1

Address granularity: 1 byte(s) per address
--------------------
Max CTO message length: 0 bytes
Max DTO message length: 0 bytes
Protocol layer version: 0
Transport layer version: 0
Found XCP at arb ID 0x0228, reply at 0x1507
####################


Sending XCP connect to 0x023a> DECODE CONNECT RESPONSE
Timestamp: 1657981290.925778    ID: 00001507    X                DLC:  8    ff 01 df 00 00 00 00 00     Channel: can0
--------------------
Resource protection status

CAL/PAG     True
X (bit 1)   False
DAQ         False
STIM        False
PGM         False
X (bit 5)   False
X (bit 6)   False
X (bit 7)   False
--------------------
COMM_MODE_BASIC

BYTE_ORDER              1
ADDRESS_GRANULARITY_0   1
ADDRESS_GRANULARITY_1   1
X (bit 3)               1
X (bit 4)               1
X (bit 5)               0
SLAVE_BLOCK_MODE        1
OPTIONAL                1

Address granularity: 4 byte(s) per address
--------------------
Max CTO message length: 0 bytes
Max DTO message length: 0 bytes
Protocol layer version: 0
Transport layer version: 0
Found XCP at arb ID 0x023a, reply at 0x1507
####################


Sending XCP connect to 0x0257
Found XCP (with a bad reply) at arbitration ID 0x257, reply at 0x1507
Received error message:
Timestamp: 1657981293.925788    ID: 00001507    X                DLC:  8    fe 01 d0 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error
Sending XCP connect to 0x025b> DECODE CONNECT RESPONSE
Timestamp: 1657981294.325703    ID: 00001507    X                DLC:  8    ff 01 d2 00 00 00 00 00     Channel: can0
--------------------
Resource protection status

CAL/PAG     True
X (bit 1)   False
DAQ         False
STIM        False
PGM         False
X (bit 5)   False
X (bit 6)   False
X (bit 7)   False
--------------------
COMM_MODE_BASIC

BYTE_ORDER              0
ADDRESS_GRANULARITY_0   1
ADDRESS_GRANULARITY_1   0
X (bit 3)               0
X (bit 4)               1
X (bit 5)               0
SLAVE_BLOCK_MODE        1
OPTIONAL                1

Address granularity: 4 byte(s) per address
--------------------
Max CTO message length: 0 bytes
Max DTO message length: 0 bytes
Protocol layer version: 0
Transport layer version: 0
Found XCP at arb ID 0x025b, reply at 0x1507
####################


Sending XCP connect to 0x0264> DECODE CONNECT RESPONSE
Timestamp: 1657981295.265667    ID: 00001507    X                DLC:  8    ff 01 d5 00 00 00 00 00     Channel: can0
--------------------
Resource protection status

CAL/PAG     True
X (bit 1)   False
DAQ         False
STIM        False
PGM         False
X (bit 5)   False
X (bit 6)   False
X (bit 7)   False
--------------------
COMM_MODE_BASIC

BYTE_ORDER              1
ADDRESS_GRANULARITY_0   0
ADDRESS_GRANULARITY_1   1
X (bit 3)               0
X (bit 4)               1
X (bit 5)               0
SLAVE_BLOCK_MODE        1
OPTIONAL                1

Address granularity: 1 byte(s) per address
--------------------
Max CTO message length: 0 bytes
Max DTO message length: 0 bytes
Protocol layer version: 0
Transport layer version: 0
Found XCP at arb ID 0x0264, reply at 0x1507
####################


Sending XCP connect to 0x0266> DECODE CONNECT RESPONSE
Timestamp: 1657981295.485766    ID: 00001507    X                DLC:  8    ff 01 cb 00 00 00 00 00     Channel: can0
--------------------
Resource protection status

CAL/PAG     True
X (bit 1)   False
DAQ         False
STIM        False
PGM         False
X (bit 5)   False
X (bit 6)   False
X (bit 7)   False
--------------------
COMM_MODE_BASIC

BYTE_ORDER              1
ADDRESS_GRANULARITY_0   1
ADDRESS_GRANULARITY_1   0
X (bit 3)               1
X (bit 4)               0
X (bit 5)               0
SLAVE_BLOCK_MODE        1
OPTIONAL                1

Address granularity: 4 byte(s) per address
--------------------
Max CTO message length: 0 bytes
Max DTO message length: 0 bytes
Protocol layer version: 0
Transport layer version: 0
Found XCP at arb ID 0x0266, reply at 0x1507
####################


Sending XCP connect to 0x026b> DECODE CONNECT RESPONSE
Timestamp: 1657981295.906853    ID: 00001507    X                DLC:  8    ff 01 d5 00 00 00 00 00     Channel: can0
--------------------
Resource protection status

CAL/PAG     True
X (bit 1)   False
DAQ         False
STIM        False
PGM         False
X (bit 5)   False
X (bit 6)   False
X (bit 7)   False
--------------------
COMM_MODE_BASIC

BYTE_ORDER              1
ADDRESS_GRANULARITY_0   0
ADDRESS_GRANULARITY_1   1
X (bit 3)               0
X (bit 4)               1
X (bit 5)               0
SLAVE_BLOCK_MODE        1
OPTIONAL                1

Address granularity: 1 byte(s) per address
--------------------
Max CTO message length: 0 bytes
Max DTO message length: 0 bytes
Protocol layer version: 0
Transport layer version: 0
Found XCP at arb ID 0x026b, reply at 0x1507
####################



Found XCP (with a bad reply) at arbitration ID 0x26b, reply at 0x1507
Received error message:
Timestamp: 1657981295.916282    ID: 00001507    X                DLC:  8    fe 01 d0 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error
> DECODE CONNECT RESPONSE
Timestamp: 1657981295.935939    ID: 00001507    X                DLC:  8    ff 01 d2 00 00 00 00 00     Channel: can0
--------------------
Resource protection status

CAL/PAG     True
X (bit 1)   False
DAQ         False
STIM        False
PGM         False
X (bit 5)   False
X (bit 6)   False
X (bit 7)   False
--------------------
COMM_MODE_BASIC

BYTE_ORDER              0
ADDRESS_GRANULARITY_0   1
ADDRESS_GRANULARITY_1   0
X (bit 3)               0
X (bit 4)               1
X (bit 5)               0
SLAVE_BLOCK_MODE        1
OPTIONAL                1

Address granularity: 4 byte(s) per address
--------------------
Max CTO message length: 0 bytes
Max DTO message length: 0 bytes
Protocol layer version: 0
Transport layer version: 0
Found XCP at arb ID 0x026b, reply at 0x1507
####################


Sending XCP connect to 0x026f> DECODE CONNECT RESPONSE
Timestamp: 1657981296.336309    ID: 00001507    X                DLC:  8    ff 01 d7 00 00 00 00 00     Channel: can0
--------------------
Resource protection status

CAL/PAG     True
X (bit 1)   False
DAQ         False
STIM        False
PGM         False
X (bit 5)   False
X (bit 6)   False
X (bit 7)   False
--------------------
COMM_MODE_BASIC

BYTE_ORDER              1
ADDRESS_GRANULARITY_0   1
ADDRESS_GRANULARITY_1   1
X (bit 3)               0
X (bit 4)               1
X (bit 5)               0
SLAVE_BLOCK_MODE        1
OPTIONAL                1

Address granularity: 4 byte(s) per address
--------------------
Max CTO message length: 0 bytes
Max DTO message length: 0 bytes
Protocol layer version: 0
Transport layer version: 0
Found XCP at arb ID 0x026f, reply at 0x1507
####################



Found XCP (with a bad reply) at arbitration ID 0x26f, reply at 0x1507
Received error message:
Timestamp: 1657981296.345667    ID: 00001507    X                DLC:  8    fe 01 cb 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error
Sending XCP connect to 0x0278
Found XCP (with a bad reply) at arbitration ID 0x278, reply at 0x1507
Received error message:
Timestamp: 1657981297.316225    ID: 00001507    X                DLC:  8    fe 01 dc 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error
Sending XCP connect to 0x027a> DECODE CONNECT RESPONSE
Timestamp: 1657981297.456235    ID: 00001507    X                DLC:  8    ff 01 d0 00 00 00 00 00     Channel: can0
--------------------
Resource protection status

CAL/PAG     True
X (bit 1)   False
DAQ         False
STIM        False
PGM         False
X (bit 5)   False
X (bit 6)   False
X (bit 7)   False
--------------------
COMM_MODE_BASIC

BYTE_ORDER              0
ADDRESS_GRANULARITY_0   0
ADDRESS_GRANULARITY_1   0
X (bit 3)               0
X (bit 4)               1
X (bit 5)               0
SLAVE_BLOCK_MODE        1
OPTIONAL                1

Address granularity: 1 byte(s) per address
--------------------
Max CTO message length: 0 bytes
Max DTO message length: 0 bytes
Protocol layer version: 0
Transport layer version: 0
Found XCP at arb ID 0x027a, reply at 0x1507
####################



Found XCP (with a bad reply) at arbitration ID 0x27a, reply at 0x1507
Received error message:
Timestamp: 1657981297.525797    ID: 00001507    X                DLC:  8    fe 01 dc 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error

Found XCP (with a bad reply) at arbitration ID 0x27a, reply at 0x1507
Received error message:
Timestamp: 1657981297.536224    ID: 00001507    X                DLC:  8    fe 01 d2 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error
Sending XCP connect to 0x027c
Found XCP (with a bad reply) at arbitration ID 0x27c, reply at 0x1507
Received error message:
Timestamp: 1657981297.656288    ID: 00001507    X                DLC:  8    fe 01 c8 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error
Sending XCP connect to 0x027e
Found XCP (with a bad reply) at arbitration ID 0x27e, reply at 0x1507
Received error message:
Timestamp: 1657981297.906742    ID: 00001507    X                DLC:  8    fe 01 c6 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error
Sending XCP connect to 0x0286
Found XCP (with a bad reply) at arbitration ID 0x286, reply at 0x1507
Received error message:
Timestamp: 1657981298.685625    ID: 00001507    X                DLC:  8    fe 01 cb 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error

Found XCP (with a bad reply) at arbitration ID 0x286, reply at 0x1507
Received error message:
Timestamp: 1657981298.696265    ID: 00001507    X                DLC:  8    fe 01 d0 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error
Sending XCP connect to 0x0287
Found XCP (with a bad reply) at arbitration ID 0x287, reply at 0x1507
Received error message:
Timestamp: 1657981298.845688    ID: 00001507    X                DLC:  8    fe 01 b9 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error
> DECODE CONNECT RESPONSE
Timestamp: 1657981298.865675    ID: 00001507    X                DLC:  8    ff 01 dc 00 00 00 00 00     Channel: can0
--------------------
Resource protection status

CAL/PAG     True
X (bit 1)   False
DAQ         False
STIM        False
PGM         False
X (bit 5)   False
X (bit 6)   False
X (bit 7)   False
--------------------
COMM_MODE_BASIC

BYTE_ORDER              0
ADDRESS_GRANULARITY_0   0
ADDRESS_GRANULARITY_1   1
X (bit 3)               1
X (bit 4)               1
X (bit 5)               0
SLAVE_BLOCK_MODE        1
OPTIONAL                1

Address granularity: 1 byte(s) per address
--------------------
Max CTO message length: 0 bytes
Max DTO message length: 0 bytes
Protocol layer version: 0
Transport layer version: 0
Found XCP at arb ID 0x0287, reply at 0x1507
####################


Sending XCP connect to 0x0291
Found XCP (with a bad reply) at arbitration ID 0x291, reply at 0x1507
Received error message:
Timestamp: 1657981299.855837    ID: 00001507    X                DLC:  8    fe 01 d5 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error
Sending XCP connect to 0x0292> DECODE CONNECT RESPONSE
Timestamp: 1657981299.936238    ID: 00001507    X                DLC:  8    ff 01 d5 00 00 00 00 00     Channel: can0
--------------------
Resource protection status

CAL/PAG     True
X (bit 1)   False
DAQ         False
STIM        False
PGM         False
X (bit 5)   False
X (bit 6)   False
X (bit 7)   False
--------------------
COMM_MODE_BASIC

BYTE_ORDER              1
ADDRESS_GRANULARITY_0   0
ADDRESS_GRANULARITY_1   1
X (bit 3)               0
X (bit 4)               1
X (bit 5)               0
SLAVE_BLOCK_MODE        1
OPTIONAL                1

Address granularity: 1 byte(s) per address
--------------------
Max CTO message length: 0 bytes
Max DTO message length: 0 bytes
Protocol layer version: 0
Transport layer version: 0
Found XCP at arb ID 0x0292, reply at 0x1507
####################



Found XCP (with a bad reply) at arbitration ID 0x292, reply at 0x1507
Received error message:
Timestamp: 1657981299.945595    ID: 00001507    X                DLC:  8    fe 01 d2 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error
Sending XCP connect to 0x029a
Found XCP (with a bad reply) at arbitration ID 0x29a, reply at 0x1507
Received error message:
Timestamp: 1657981300.765557    ID: 00001507    X                DLC:  8    fe 01 d0 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error

Found XCP (with a bad reply) at arbitration ID 0x29a, reply at 0x1507
Received error message:
Timestamp: 1657981300.806674    ID: 00001507    X                DLC:  8    fe 01 d5 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error
> DECODE CONNECT RESPONSE
Timestamp: 1657981300.817328    ID: 00001507    X                DLC:  8    ff 01 d5 00 00 00 00 00     Channel: can0
--------------------
Resource protection status

CAL/PAG     True
X (bit 1)   False
DAQ         False
STIM        False
PGM         False
X (bit 5)   False
X (bit 6)   False
X (bit 7)   False
--------------------
COMM_MODE_BASIC

BYTE_ORDER              1
ADDRESS_GRANULARITY_0   0
ADDRESS_GRANULARITY_1   1
X (bit 3)               0
X (bit 4)               1
X (bit 5)               0
SLAVE_BLOCK_MODE        1
OPTIONAL                1

Address granularity: 1 byte(s) per address
--------------------
Max CTO message length: 0 bytes
Max DTO message length: 0 bytes
Protocol layer version: 0
Transport layer version: 0
Found XCP at arb ID 0x029a, reply at 0x1507
####################


Sending XCP connect to 0x029b> DECODE CONNECT RESPONSE
Timestamp: 1657981300.825576    ID: 00001507    X                DLC:  8    ff 01 d5 00 00 00 00 00     Channel: can0
--------------------
Resource protection status

CAL/PAG     True
X (bit 1)   False
DAQ         False
STIM        False
PGM         False
X (bit 5)   False
X (bit 6)   False
X (bit 7)   False
--------------------
COMM_MODE_BASIC

BYTE_ORDER              1
ADDRESS_GRANULARITY_0   0
ADDRESS_GRANULARITY_1   1
X (bit 3)               0
X (bit 4)               1
X (bit 5)               0
SLAVE_BLOCK_MODE        1
OPTIONAL                1

Address granularity: 1 byte(s) per address
--------------------
Max CTO message length: 0 bytes
Max DTO message length: 0 bytes
Protocol layer version: 0
Transport layer version: 0
Found XCP at arb ID 0x029b, reply at 0x1507
####################


Sending XCP connect to 0x029c
Found XCP (with a bad reply) at arbitration ID 0x29c, reply at 0x1507
Received error message:
Timestamp: 1657981300.965577    ID: 00001507    X                DLC:  8    fe 01 d7 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error

Found XCP (with a bad reply) at arbitration ID 0x29c, reply at 0x1507
Received error message:
Timestamp: 1657981300.985570    ID: 00001507    X                DLC:  8    fe 01 cb 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error
Sending XCP connect to 0x029e
Found XCP (with a bad reply) at arbitration ID 0x29e, reply at 0x1507
Received error message:
Timestamp: 1657981301.136083    ID: 00001507    X                DLC:  8    fe 01 d5 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error
Sending XCP connect to 0x02a6> DECODE CONNECT RESPONSE
Timestamp: 1657981302.036203    ID: 00001507    X                DLC:  8    ff 01 c3 00 00 00 00 00     Channel: can0
--------------------
Resource protection status

CAL/PAG     True
X (bit 1)   False
DAQ         False
STIM        False
PGM         False
X (bit 5)   False
X (bit 6)   False
X (bit 7)   False
--------------------
COMM_MODE_BASIC

BYTE_ORDER              1
ADDRESS_GRANULARITY_0   1
ADDRESS_GRANULARITY_1   0
X (bit 3)               0
X (bit 4)               0
X (bit 5)               0
SLAVE_BLOCK_MODE        1
OPTIONAL                1

Address granularity: 4 byte(s) per address
--------------------
Max CTO message length: 0 bytes
Max DTO message length: 0 bytes
Protocol layer version: 0
Transport layer version: 0
Found XCP at arb ID 0x02a6, reply at 0x1507
####################


Sending XCP connect to 0x02a9> DECODE CONNECT RESPONSE
Timestamp: 1657981302.276188    ID: 00001507    X                DLC:  8    ff 01 cb 00 00 00 00 00     Channel: can0
--------------------
Resource protection status

CAL/PAG     True
X (bit 1)   False
DAQ         False
STIM        False
PGM         False
X (bit 5)   False
X (bit 6)   False
X (bit 7)   False
--------------------
COMM_MODE_BASIC

BYTE_ORDER              1
ADDRESS_GRANULARITY_0   1
ADDRESS_GRANULARITY_1   0
X (bit 3)               1
X (bit 4)               0
X (bit 5)               0
SLAVE_BLOCK_MODE        1
OPTIONAL                1

Address granularity: 4 byte(s) per address
--------------------
Max CTO message length: 0 bytes
Max DTO message length: 0 bytes
Protocol layer version: 0
Transport layer version: 0
Found XCP at arb ID 0x02a9, reply at 0x1507
####################


> DECODE CONNECT RESPONSE
Timestamp: 1657981302.336199    ID: 00001507    X                DLC:  8    ff 01 d2 00 00 00 00 00     Channel: can0
--------------------
Resource protection status

CAL/PAG     True
X (bit 1)   False
DAQ         False
STIM        False
PGM         False
X (bit 5)   False
X (bit 6)   False
X (bit 7)   False
--------------------
COMM_MODE_BASIC

BYTE_ORDER              0
ADDRESS_GRANULARITY_0   1
ADDRESS_GRANULARITY_1   0
X (bit 3)               0
X (bit 4)               1
X (bit 5)               0
SLAVE_BLOCK_MODE        1
OPTIONAL                1

Address granularity: 4 byte(s) per address
--------------------
Max CTO message length: 0 bytes
Max DTO message length: 0 bytes
Protocol layer version: 0
Transport layer version: 0
Found XCP at arb ID 0x02a9, reply at 0x1507
####################


> DECODE CONNECT RESPONSE
Timestamp: 1657981302.345551    ID: 00001507    X                DLC:  8    ff 01 d2 00 00 00 00 00     Channel: can0
--------------------
Resource protection status

CAL/PAG     True
X (bit 1)   False
DAQ         False
STIM        False
PGM         False
X (bit 5)   False
X (bit 6)   False
X (bit 7)   False
--------------------
COMM_MODE_BASIC

BYTE_ORDER              0
ADDRESS_GRANULARITY_0   1
ADDRESS_GRANULARITY_1   0
X (bit 3)               0
X (bit 4)               1
X (bit 5)               0
SLAVE_BLOCK_MODE        1
OPTIONAL                1

Address granularity: 4 byte(s) per address
--------------------
Max CTO message length: 0 bytes
Max DTO message length: 0 bytes
Protocol layer version: 0
Transport layer version: 0
Found XCP at arb ID 0x02a9, reply at 0x1507
####################



Found XCP (with a bad reply) at arbitration ID 0x2a9, reply at 0x1507
Received error message:
Timestamp: 1657981302.356181    ID: 00001507    X                DLC:  8    fe 01 cb 00 00 00 00 00     Channel: can0
Error code (0x01): UNKNOWN
Description: Unknown error
Sending XCP connect to 0x02aa> DECODE CONNECT RESPONSE
Timestamp: 1657981302.456122    ID: 00001507    X                DLC:  8    ff 01 d0 00 00 00 00 00     Channel: can0
--------------------
Resource protection status

CAL/PAG     True
X (bit 1)   False
DAQ         False
STIM        False
PGM         False
X (bit 5)   False
X (bit 6)   False
X (bit 7)   False
--------------------
COMM_MODE_BASIC

BYTE_ORDER              0
ADDRESS_GRANULARITY_0   0
ADDRESS_GRANULARITY_1   0
X (bit 3)               0
X (bit 4)               1
X (bit 5)               0
SLAVE_BLOCK_MODE        1
OPTIONAL                1

Address granularity: 1 byte(s) per address
--------------------
Max CTO message length: 0 bytes
Max DTO message length: 0 bytes
Protocol layer version: 0
Transport layer version: 0
Found XCP at arb ID 0x02aa, reply at 0x1507
####################


Sending XCP connect to 0x02ab> DECODE CONNECT RESPONSE
Timestamp: 1657981302.465576    ID: 00001507    X                DLC:  8    ff 01 dc 00 00 00 00 00     Channel: can0
--------------------
Resource protection status

CAL/PAG     True
X (bit 1)   False
DAQ         False
STIM        False
PGM         False
X (bit 5)   False
X (bit 6)   False
X (bit 7)   False
--------------------
COMM_MODE_BASIC

BYTE_ORDER              0
ADDRESS_GRANULARITY_0   0
ADDRESS_GRANULARITY_1   1
X (bit 3)               1
X (bit 4)               1
X (bit 5)               0
SLAVE_BLOCK_MODE        1
OPTIONAL                1

Address granularity: 1 byte(s) per address
--------------------
Max CTO message length: 0 bytes
Max DTO message length: 0 bytes
Protocol layer version: 0
Transport layer version: 0
Found XCP at arb ID 0x02ab, reply at 0x1507
####################


Sending XCP connect to 0x0546
CanError: Failed to transmit: [Errno 105] No buffer space available

Antworten