• State Not Answered
  • Replies 4 replies
  • Subscribers 10 subscribers
  • Views 143 views
  • Users 0 members are here
Options
Related

wireless HART mote (DC9003A) link to STM32F103 development board

Ykuang929
on Jun 27, 2019

I use the STM32F103 development board which deal with the sensor data and send it to wireless HART mote . I follow the process of mote connecting to the network(get mote state -> set joinkey -> set networkID -> join -> get notification -> connect state) and call the function follow this sequence(using the dn_whmt.c file which is suitable for wireless HART Mote). But there is only one mote can complete the process (when call the dn_event_join function the mote can send notification),the other mote will stay after the completer join function( manager show the mote has connected to the network) .  The implementation as follow:

DEBUG ..\Src\dn_fsm_whmt.c:812: Join
DEBUG ..\Src\dn_fsm_whmt.c:406: Got reply: cmdId; 0x06 (6)
DEBUG ..\Src\dn_fsm_whmt.c:830: Join reply
DEBUG ..\Src\dn_fsm_whmt.c:842: Join operation started

  • 0 on Jul 1, 2019 8:51 AM

    //mote 3 log information
    DEBUG ..\Src\dn_fsm_whmt.c:103: QSL: Init
    DEBUG ..\sm_clib\ports\msp430fr4133\dn_uart.c:39: SMIP Serial Initialized
    DEBUG ..\Src\dn_fsm_whmt.c:1277: FSM state transition: 00 --> 0x01 (0 ms)
    Mote initzates successfully!
    This is a test code
    DEBUG ..\Src\dn_fsm_whmt.c:122: QSL: isConnected
    [INFO] (../Src/main.c:222) Connecting...
    DEBUG ..\Src\dn_fsm_whmt.c:132: QSL: Connect
    DEBUG ..\Src\dn_fsm_whmt.c:1328: No network ID given; using default
    DEBUG ..\Src\dn_fsm_whmt.c:1341: No join key given; using default
    DEBUG ..\Src\dn_fsm_whmt.c:144: Starting connect process...
    DEBUG ..\Src\dn_fsm_whmt.c:1277: FSM state transition: 0x01 --> 0x02 (555 ms)
    DEBUG ..\Src\dn_fsm_whmt.c:572: Mote status
    DEBUG ..\Src\dn_fsm_whmt.c:275: Got notification: cmdId; 0x0f (15), subCmdId; 0xff (255)
    DEBUG ..\Src\dn_fsm_whmt.c:310: State: 0x01 | Events: 0x0001
    DEBUG ..\Src\dn_fsm_whmt.c:1277: FSM state transition: 0x02 --> 0x02 (318 ms)
    DEBUG ..\Src\dn_fsm_whmt.c:572: Mote status
    DEBUG ..\Src\dn_fsm_whmt.c:435: Response timeout
    DEBUG ..\Src\dn_fsm_whmt.c:1277: FSM state transition: 0x02 --> 0x02 (616 ms)
    DEBUG ..\Src\dn_fsm_whmt.c:572: Mote status
    DEBUG ..\Src\dn_fsm_whmt.c:418: Got reply: cmdId; 0x02 (2)
    DEBUG ..\Src\dn_fsm_whmt.c:590: Mote status reply
    DEBUG ..\Src\dn_fsm_whmt.c:597: Mote state: 0x01
    DEBUG ..\Src\dn_fsm_whmt.c:680: Set join key
    DEBUG ..\Src\dn_fsm_whmt.c:418: Got reply: cmdId; 0x03 (3)
    DEBUG ..\Src\dn_fsm_whmt.c:699: Set join key reply
    DEBUG ..\Src\dn_fsm_whmt.c:711: Join key set
    DEBUG ..\Src\dn_fsm_whmt.c:754: Set network ID
    DEBUG ..\Src\dn_fsm_whmt.c:418: Got reply: cmdId; 0x03 (3)
    DEBUG ..\Src\dn_fsm_whmt.c:773: Set network ID reply
    DEBUG ..\Src\dn_fsm_whmt.c:785: Network ID set
    DEBUG ..\Src\dn_fsm_whmt.c:1277: FSM state transition: 0x02 --> 0x03 (661 ms)
    DEBUG ..\Src\dn_fsm_whmt.c:876: Join
    DEBUG ..\Src\dn_fsm_whmt.c:418: Got reply: cmdId; 0x06 (6)
    DEBUG ..\Src\dn_fsm_whmt.c:894: Join reply
    DEBUG ..\Src\dn_fsm_whmt.c:906: Join operation started
    DEBUG ..\Src\dn_fsm_whmt.c:275: Got notification: cmdId; 0x0f (15), subCmdId; 0xff (255)
    DEBUG ..\Src\dn_fsm_whmt.c:310: State: 0x02 | Events: 0x0002
    DEBUG ..\Src\dn_fsm_whmt.c:275: Got notification: cmdId; 0x0f (15), subCmdId; 0xff (255)
    DEBUG ..\Src\dn_fsm_whmt.c:310: State: 0x03 | Events: 0x0100
    DEBUG ..\Src\dn_fsm_whmt.c:275: Got notification: cmdId; 0x0f (15), subCmdId; 0xff (255)
    DEBUG ..\Src\dn_fsm_whmt.c:310: State: 0x04 | Events: 0x0002
    DEBUG ..\Src\dn_fsm_whmt.c:275: Got notification: cmdId; 0x0f (15), subCmdId; 0xff (255)
    DEBUG ..\Src\dn_fsm_whmt.c:310: State: 0x04 | Events: 0x0004
    DEBUG ..\Src\dn_fsm_whmt.c:275: Got notification: cmdId; 0x0f (15), subCmdId; 0xff (255)
    DEBUG ..\Src\dn_fsm_whmt.c:310: State: 0x05 | Events: 0x0020
    DEBUG ..\Src\dn_fsm_whmt.c:1277: FSM state transition: 0x03 --> 0x04 (41942 ms)
    DEBUG ..\Src\dn_fsm_whmt.c:936: Set service Id
    DEBUG ..\Src\dn_fsm_whmt.c:418: Got reply: cmdId; 0x01 (1)
    DEBUG ..\Src\dn_fsm_whmt.c:958: Request service accept
    DEBUG ..\Src\dn_fsm_whmt.c:970: Service request accepted
    DEBUG ..\Src\dn_fsm_whmt.c:275: Got notification: cmdId; 0x0e (14), subCmdId; 0xff (255)
    DEBUG ..\Src\dn_fsm_whmt.c:295: Service Indication
    DEBUG ..\Src\dn_fsm_whmt.c:1000: Get service info
    DEBUG ..\Src\dn_fsm_whmt.c:418: Got reply: cmdId; 0x02 (2)
    DEBUG ..\Src\dn_fsm_whmt.c:1019: Get service info reply
    [INFO] (..\Src\dn_fsm_whmt.c:1031) service state:0x82
    DEBUG ..\Src\dn_fsm_whmt.c:1036: Granted service of 0 ms (requested 5000 ms)
    DEBUG ..\Src\dn_fsm_whmt.c:1277: FSM state transition: 0x04 --> 0x0f (3160 ms)
    [INFO] (../Src/main.c:226) Connected to network
    This is a test code
    DEBUG ..\Src\dn_fsm_whmt.c:122: QSL: isConnected
    DEBUG ..\Src\dn_fsm_whmt.c:219: QSL: Send
    DEBUG ..\Src\dn_fsm_whmt.c:1277: FSM state transition: 0x0f --> 0x10 (21 ms)
    DEBUG ..\Src\dn_fsm_whmt.c:1077: Send
    DEBUG ..\Src\dn_fsm_whmt.c:418: Got reply: cmdId; 0x05 (5)
    DEBUG ..\Src\dn_fsm_whmt.c:1110: Send reply
    DEBUG ..\Src\dn_fsm_whmt.c:1122: Packet was queued up for transmission
    DEBUG ..\Src\dn_fsm_whmt.c:1277: FSM state transition: 0x10 --> 0x0f (131 ms)
    [INFO] (../Src/main.c:205) Sent message nr 0: 29102
    DEBUG ..\Src\dn_fsm_whmt.c:194: QSL: Read
    DEBUG ..\Src\dn_fsm_whmt.c:210: Inbox empty
    DEBUG ..\Src\dn_fsm_whmt.c:275: Got notification: cmdId; 0x0e (14), subCmdId; 0xff (255)
    DEBUG ..\Src\dn_fsm_whmt.c:295: Service Indication

  • 0 on Jul 1, 2019 8:51 AM

    //mote3 send to stm32f103
    【2019-07-01 16:41:40:905】7E 0E 01 0A 00 00 00 01 01 00 00 00 00 99 3E 7E
    【2019-07-01 16:41:41:748】7E 00 03 02 00 0E 01 00 00 00 00 00 00 00 00 00 89 AB 7E
    【2019-07-01 16:41:42:013】7E 02 01 00 00 02 CC B7 7E
    【2019-07-01 16:41:42:231】7E 02 01 02 00 03 FF 13 7E
    【2019-07-01 16:41:42:465】7E 04 00 00 00 9C 2E 7E 7E 0F 09 00 00 00 00 02 00 00 00 00 08 07 93 7E
    【2019-07-01 16:41:57:566】7E 0E 01 02 00 00 00 00 03 00 00 00 08 8E 57 7E
    【2019-07-01 16:42:00:873】7E 0E 01 00 00 00 00 02 04 00 00 00 00 D7 24 7E
    【2019-07-01 16:42:21:590】7E 0E 01 02 00 00 00 00 04 00 00 00 00 63 64 7E
    【2019-07-01 16:42:24:149】7E 0F 08 00 00 00 00 20 01 00 00 00 00 A1 A2 7E
    【2019-07-01 16:42:24:383】7E 01 02 02 00 08 00 21 0E 7C
    【2019-07-01 16:42:26:723】7C 0C 0C 00 00 00 80 01 03 02 F9 01 00 01 86 80 F9 D3 7E
    【2019-07-01 16:42:27:347】7E 00 03 01 00 00 00 82 01 00 F1 81 00 00 00 00 D0 C3 7E
    【2019-07-01 16:42:27:534】7E 04 00 02 00 E1 B8 7E

  • 0 on Jul 1, 2019 8:55 AM

    the mote3 is the normal execution,while the mote 4 is failed.

    mote4 log information
    DEBUG ..\Src\dn_fsm_whmt.c:435: Response timeout
    DEBUG ..\Src\dn_fsm_whmt.c:1277: FSM state transition: 0x02 --> 0x02 (622 ms)
    DEBUG ..\Src\dn_fsm_whmt.c:275: Got notification: cmdId; 0x0f (15), subCmdId; 0xff (255)
    DEBUG ..\Src\dn_fsm_whmt.c:310: State: 0x01 | Events: 0x0001
    DEBUG ..\Src\dn_fsm_whmt.c:1277: FSM state transition: 0x02 --> 0x02 (27 ms)
    DEBUG ..\Src\dn_fsm_whmt.c:572: Mote status
    DEBUG ..\Src\dn_fsm_whmt.c:418: Got reply: cmdId; 0x02 (2)
    DEBUG ..\Src\dn_fsm_whmt.c:590: Mote status reply
    DEBUG ..\Src\dn_fsm_whmt.c:597: Mote state: 0x01
    DEBUG ..\Src\dn_fsm_whmt.c:680: Set join key
    DEBUG ..\Src\dn_fsm_whmt.c:418: Got reply: cmdId; 0x03 (3)
    DEBUG ..\Src\dn_fsm_whmt.c:699: Set join key reply
    DEBUG ..\Src\dn_fsm_whmt.c:711: Join key set
    DEBUG ..\Src\dn_fsm_whmt.c:754: Set network ID
    DEBUG ..\Src\dn_fsm_whmt.c:418: Got reply: cmdId; 0x03 (3)
    DEBUG ..\Src\dn_fsm_whmt.c:773: Set network ID reply
    DEBUG ..\Src\dn_fsm_whmt.c:785: Network ID set
    DEBUG ..\Src\dn_fsm_whmt.c:1277: FSM state transition: 0x02 --> 0x03 (342 ms)
    DEBUG ..\Src\dn_fsm_whmt.c:876: Join
    DEBUG ..\Src\dn_fsm_whmt.c:418: Got reply: cmdId; 0x06 (6)
    DEBUG ..\Src\dn_fsm_whmt.c:894: Join reply
    DEBUG ..\Src\dn_fsm_whmt.c:906: Join operation started

    after the Join operation started the state machine can not execute,but the manager show the mote is connecting the network.

    //mote4 send to stm32f103
    【2019-07-01 16:45:07:759】7C 0F 08 08 00 00 00 01 01 00 00 00 00 99 3F 7E
    【2019-07-01 16:45:07:883】7C 00 0B 02 00 0E 01 00 00 00 00 00 00 00 00 00 89 AB 7E
    【2019-07-01 16:45:08:024】7C 03 01 00 00 02 8E B7 7E
    【2019-07-01 16:45:08:149】7E 02 01 03 00 03 FF 13 7E
    【2019-07-01 16:45:08:289】7C 04 00 00 00 9C AE 7E 7C 0F 01 00 00 00 00 02 02 00 00 00 08 07 93 7E
    【2019-07-01 16:45:08:804】7C 0F 09 00 00 00 00 02 02 00 00 00 08 07 93 7E
    【2019-07-01 16:45:09:303】7C 0F 08 00 00 00 00 02 02 00 00 00 08 07 93 7E
    【2019-07-01 16:45:09:802】7C 0F 09 00 00 00 00 02 02 00 00 00 08 07 93 7E
    【2019-07-01 16:45:10:301】7E 0F 01 00 00 00 00 02 02 00 00 00 08 07 93 7E
    【2019-07-01 16:45:10:801】7E 0E 01 00 00 00 00 02 02 00 00 00 08 07 93 7E
    【2019-07-01 16:45:11:300】7E 0E 09 00 00 00 00 02 02 00 00 00 08 07 93 7E
    【2019-07-01 16:45:11:799】7C 0F 09 00 00 00 00 02 02 00 00 00 08 07 93 7E
    【2019-07-01 16:45:12:298】7E 0E 01 00 00 00 00 02 02 00 00 00 08 07 93 7E
    【2019-07-01 16:45:12:797】7E 0F 08 00 00 00 00 02 02 00 00 00 08 07 93 7E
    【2019-07-01 16:45:13:312】00
    【2019-07-01 16:45:13:811】7E 0E 09 00 00 00 00 02 00 00 00 00 08 07 93 7E
    【2019-07-01 16:45:14:311】7E 0F 08 00 00 00 00 02 02 00 00 00 08 07 93 7E
     Can anyone give the mean of  each commad? I don't know the data means 

  • 0
    •  Analog Employees 
    on Aug 19, 2019 7:27 AM

    Hi,

    For questions regarding Smartmesh/Dust network, please contact Dustsupport@analog.com.

    Regards,

    Aldrich