MMP » Historie » Version 1
Maximilian Seesslen, 11.07.2023 14:22
1 | 1 | Maximilian Seesslen | h1. Multipacket-Strings |
---|---|---|---|
2 | |||
3 | There should be the posssibillity to write the complete SPI-Flash even if it takes forever. |
||
4 | Not every slave needs to be able to send super big blocks. But every slave should be able to |
||
5 | send e.g. descriptions. |
||
6 | There can not be multiple transfers at the same time from one node because there is no identification. |
||
7 | |||
8 | |_. Size |_. Type | |
||
9 | | 0x4 | Package number (0: Data contains package count) | |
||
10 | | 0x4 | Data | |
||
11 | |||
12 | h2. Header |
||
13 | |||
14 | |_. Size |_. Type | |
||
15 | | 0x4 | Total size | |
||
16 | | 0x4 | Type (1=SDCard) | |
||
17 | | 0x4 | Target node ID | |
||
18 | | 0x4 | CRC32 of data | |
||
19 | |||
20 | |||
21 | h2. Example: CANRec |
||
22 | |||
23 | PC requests an complete dump from single Node. Node will just stream it out. |
||
24 | |||
25 | |||
26 | h1. V2 |
||
27 | |||
28 | |_. Size |_. Decription |_. Examples | |
||
29 | | 1 | Packet type | Standard TDT packet | |
||
30 | | 1 | Sub-Id; | Futher index; Sub-Sensor or more specifi kind of thing to be set | |
||
31 | | 1 | Data type | Int, Float, Time, Date, Percent, Promil, Multipacket-String | |
||
32 | | 1 | Unit | Hz, °C, Time, Date, PWM, CAN-ID, Name, Description, Room | |
||
33 | | 4 | Value | 32Bit | |
||
34 | |||
35 | h1. V3 |
||
36 | |||
37 | |_. Size |_. Decription |_. Examples | |
||
38 | | 2 | Object | | |
||
39 | | 1 | Sub-Id; | Flags, Subid | |
||
40 | | 1 | Unit/Type | Hz_int, °C_centi, Time, Date, PWM_milli, CAN-ID, Name, Description, Room | |
||
41 | | 4 | Value | 32Bit | |
||
42 | |||
43 | h2. Flags |
||
44 | |||
45 | 4 Bit multi message count |
||
46 | 4 Bit multi message pos |
||
47 | |||
48 | Length in Bytes given via CAN? |
||
49 | Strings with max. 64 characters. |
||
50 | |||
51 | h2. Multimessage package |
||
52 | |||
53 | There should be the possibillity to write the complete SPI-Flash even if it takes forever. |
||
54 | Not every slave needs to be able to send super big blocks. But every slave should be able to |
||
55 | send e.g. descriptions. |