Skip to content

Latest commit

 

History

History

NodeTest

README.md

NodeTest

Current rev 1.16

Notes:

  • Compiled by Lazarus 2.0.4 with installed Cportlaz_v1.0.0 serial port component

Scope

NodeTest.exe is a Windows application to test and to configure HBus nodes. NodeTest uses a USB-UART bridge with CAN transceiver. It could be a dedicated galvanically isolated HBus USB bridge, or a cheap generic USB-UART bridge with a CAN transceiver board.

1. Initial settings

  • Assign NodeTest Own ID. In the sample shown NodeTest ID is set to 0x0404. Value should be in the range 0x0001...0x07FF.
  • Select COM port connected to HBus. Pic1_1
  • When NodeTest closed, it stores its settings in .ini files.

2. Discover HBus nodes and assign permanent ID

  • Connect HBus node to network. After reset the sample node issued a splash screen with ASCII text. For debug purposes, NodeTest prints all data appeared between HBus messages. If data bytes can be represented as visible ASCII chars, nodeTest prints ASCII chars, otherwise it prints hex value in square brackets. NodeTest marks these prints with " - dbg " prefix. Pic2_1
  • At splash screen the node reports its ID, it is 0xFBD9. First hex digit "F" indicates that node ID is temporary. After every reset node changes its temporary ID randomly.
  • NodeTest issues COLLECT command, its code is 0x03, source node ID 0x0404. Replies should be within 128 time slots 10 ms each.
  • So far only one reply arrived. Reply code is 0x83. It was issued by node 0xFBD9 to node 0x0404.
    Pic2_2
  • NodeTest issued SET_ID command (code 0x05) to node 0xFBD9. New ID is 0x0021.
  • Node replied OK, reply code 0x85. Its ID now is set to 0x0021. It is a permanent ID. Pic2_3

If device has topics, it tries to retrieve topic IDs from the net. For every topic it broadcast REGISTER command with TopicID=0 and waits for reply. If nobody replies, node asssigns a TopicID based on its own NodeID and then broadcasts the pair [TopicID, TopicName] by REGISTER command/

In the following sample node 0x021 requests TopicIDs for topics "test1", "test2", "test3", "test4". Nobody repies, therefore the node assignes TopicIDs as follows: "test1"=1056 (0x0420), "test2"=1057 (0x0421), "test3"=1058 (0x0422), "test4"=1059 (0x0423):

FF MQTT 1A 00 21 00 00 02 AC 01  00 00 10 C2 test1 -- <TopicId=?>
FF MQTT DA 00 21 04 20 03 93 01  00 00 10 C3 test1 -- <TopicId=1056>
FF MQTT AA 00 21 00 00 04 F6 01  00 00 10 C3 test2 -- <TopicId=?>
FF MQTT 0A 00 21 04 21 05 91 01  00 00 10 C4 test2 -- <TopicId=1057>
FF MQTT 3A 00 21 00 00 06 29 01  00 00 10 C4 test3 -- <TopicId=?>
FF MQTT 3A 00 21 04 22 07 FC 01  00 00 10 C5 test3 -- <TopicId=1058>
FF MQTT AA 00 21 00 00 08 59 01  00 00 10 C5 test4 -- <TopicId=?>
FF MQTT 2A 00 21 04 23 09 F3 01  00 00 10 C6 test4 -- <TopicId=1059>

3. Explore HBus node and set description

  • Double click to NodeTest list box to clear it.
  • Set NodeID = 0x21 and click to "Read Revision" button. NodeTest issues REV command to node 0x0021, code 0x01. Node 0x0021 replies its hardware and software revisions:
FF HBus 01 04 04 00 21 D7 BD 00  23 53 08 6F 
FF HBus 81 04 04 00 21 D7 C3 00  00 00 1C 3A 02 01 00 01  00 01 01 00 01 03
  • Click to "Read Status" button. NodeTest issues REV command to node 0x0021, code 0x02. Node 0x0021 replies its status, it has 4 topics with TopicIDs of 1056, 1057, 1058, 1058, but those topic values are not valid and displayed as 0:
FF HBus 02 04 04 00 21 D8 82 00  23 53 09 43 
FF HBus 82 04 04 00 21 D8 3D 01  00 00 1D 0E {tid:[1056,1057,1058,1059], val:[0,0,0,0]}
  • Click to Description "Read" button. NodeTest issues RD_DESCR command, code 0x08. Node replies zero length string.
FF HBus 08 04 04 00 21 DD 08 00  23 53 0F 82 
FF HBus 88 04 04 00 21 DD 54 00  00 00 23 49
  • Type "Demo_node" in the Description edit box. Click to Description "Write" button. NodeTest isuies WR_DESCR command, code 0x09. Node replies "OK".
FF HBus 08 04 04 00 21 DE B6 01  23 53 10 78 09 44 65 6D  6F 5F 6E 6F 64 65 
FF HBus 88 04 04 00 21 DE F3 00  00 00 24 3E 00
  • Click to Description "Read" button again. Node replies description string.
FF HBus 08 04 04 00 21 DF 55 00  23 53 10 D5 
FF HBus 88 04 04 00 21 DF 0F 00  00 00 24 9B 09 Demo_node

4. MQTT mode

  • Select MQTT tab and issue MQTT message, value 12 to topic 1057 . Issuing node ID 0x0404, eg it is NodeTest.
FF MQTT 2C 04 04 04 21 00 E0 01  23 53 11 3F {val:12} -- <TopicId=1057>
  • Select HBus tab and issue STATUS command to node 0x21. In the reply node 0x21 reports its topics:
FF HBus 02 04 04 00 21 E1 F6 00  23 53 12 0A 
FF HBus 82 04 04 00 21 E1 11 01  00 00 25 CF {tid:[1056,1057,1058,1059], val:[0,12.00,0,0]}

Now topic 1057 has a valid value 12.00, other topics do not have valid values and displayed as 0.

  • After a while node 0x21 will broadcast topic 1057 with value 12.00. It will repeat the broadcast approximately every 40 sec.
FF MQTT 2C 00 21 04 21 0E 06 01  00 00 25 DF {val:12.00, topic:test2} -- <TopicId=1057>

5. Notes

  • You can select text in ListBox. Using Ctrl+C you can copy selected text lines to Clipboard.