TDT-Eval » Historie » Version 12
Maximilian Seesslen, 26.02.2024 16:10
| 1 | 1 | Maximilian Seesslen | h1. TDT-Eval |
|---|---|---|---|
| 2 | |||
| 3 | Devices _should_ not use same IDs. |
||
| 4 | 5 | Maximilian Seesslen | CANOpen is limited to 128 devices (some manufactures support only 64). |
| 5 | 7 | Maximilian Seesslen | CAN 2.0.A: 0x800 |
| 6 | 1 | Maximilian Seesslen | |
| 7 | 11-Bit-Identifier, auch „Base frame format“ genannt (CAN 2.0A) |
||
| 8 | 29-Bit-Identifier, auch „Extended frame format“ genannt (CAN 2.0B). |
||
| 9 | |||
| 10 | 7 | Maximilian Seesslen | Bei 4Bit Sub-ID waeren noch 128 Nodes möglich; 0x?80. |
| 11 | 4 | Maximilian Seesslen | |
| 12 | Wenn alle Informationen im Daten-Feld sind, koennen Nodes nicht filtern. |
||
| 13 | Use-Cases: |
||
| 14 | * Node will nur System-Kommandos haben |
||
| 15 | * Node will nur Messwerte haben; overhead aber nicht so relevant |
||
| 16 | * Node will nur hoch-priore Alarme haben |
||
| 17 | 1 | Maximilian Seesslen | |
| 18 | CANOpen geht bei der Nachrichtenart ueber Ranges; in den heoheren Bits ist der Type eincodiert. Some IDs are fixed for a single "CAN network manager". |
||
| 19 | 16 Typen; NMT; Alerts, PDOs |
||
| 20 | 7 | Maximilian Seesslen | |
| 21 | |0 | NMT | |
||
| 22 | |1 | Alert | |
||
| 23 | |8 | System commands; set Date, set ambient light | |
||
| 24 | 6 | Maximilian Seesslen | |14| | |
| 25 | |15| Broadcastet Sensor values | |
||
| 26 | 8 | Maximilian Seesslen | |
| 27 | h2. Usecases |
||
| 28 | |||
| 29 | * Sensor verschickt messdaten |
||
| 30 | * Controller setzt Licht |
||
| 31 | * Controller setzt Datum/Uhrzeit |
||
| 32 | * Sensor sendet firmware version |
||
| 33 | * Sensor sendet Unique ID |
||
| 34 | * Controller weist Unique ID eine Node-ID zu |
||
| 35 | 9 | Maximilian Seesslen | * Binary Blobs lesen/schreiben; Temprec auslesen |
| 36 | 10 | Maximilian Seesslen | |
| 37 | h3. Set CAN-ID |
||
| 38 | |||
| 39 | Ueber CAN die ID zu setzen waere praktisch. Die Boards keonnen sich ueber Produkt-ID und Serennummer vorstellen. |
||
| 40 | Product-ID + serial 32 Bit. |
||
| 41 | Die CAN-Id ist die Ziel-CAN-ID. |
||
| 42 | |||
| 43 | |_. Size |_. Decription |_. Examples | |
||
| 44 | | 2 | Object | Node-ID | |
||
| 45 | | 1 | Data type | Int, Float, Time, Date, Percent, Promil, Multipacket-String | |
||
| 46 | | 1 | Unit | Hz, °C, Time, Date, PWM, CAN-ID, Name, Description, Room | |
||
| 47 | | 4 | Value | 32Bit | |
||
| 48 | 11 | Maximilian Seesslen | |
| 49 | h3. Network |
||
| 50 | |||
| 51 | 1 | Maximilian Seesslen | User wants to know which nodes do not support current protocol. |
| 52 | 12 | Maximilian Seesslen | |
| 53 | h3. Alerts/Events/Status |
||
| 54 | |||
| 55 | * Send objects could be set as 'Alert' by flag. Cordyceps can mark it red. |
||
| 56 | ** Example: Overtemperature; undervoltage |
||
| 57 | |||
| 58 | * Events; integrated in logging. |
||
| 59 | ** Simple Event-Object. Cordyceps has to keep list in order to have history. |
||
| 60 | |||
| 61 | * Device Status |
||
| 62 | ** Good, Warning, Error, Bootloader |