Projekt

Allgemein

Profil

NMT » Historie » Version 1

Maximilian Seesslen, 11.07.2023 13:50

1 1 Maximilian Seesslen
h1. NMT
2
3
h2. Actuator introduction
4
5
When introduction is requested by system command, each device must send Its UID (function code "NMT introduce") and an description.
6
The NodeId may conflict due to an network error. But the master can detect different UUIDs with same NodeId.
7
8
h2. 
9
|_. Size |_. Decription |_. Examples                                                       |
10
| 2      | Object       | Object                                                           |
11
| 6      | MAC/Unique ID| 48Bit                                                            |
12
13
h3. Objects
14
15
|_. Size |_. Decription          |
16
|1       | Request intoruction   |
17
|2       | MAC low               |
18
|3       | MAC high              |
19
|4       | Protocol versions     |
20
|5       | Firmware version      |
21
|6       | Product Code          |
22
|7       | Node-Id               |
23
24
25
h3. Protocol versions
26
27
|_. Size |_. Decription            |
28
|1       | TDT Major               |
29
|1       | TDT Minor               |
30
|1       | NMT Major               |
31
|1       | NMT Minor               |
32
|1       | Blob Major              |
33
|1       | Blob Minor              |
34
35
h2. Usecase: Setting Node-ID
36
37
Two nodes may have the same Node-ID. When scanning the network, the nodes will overwrite the counterparts information.
38
The "NMT-Introduce"-function code is used by the nodes to send theyr complete UID. NMT can then send 
39
The new NodeID can not be part of the CAN-ID because the device may be filtering it out. (The whole NMT )