User's Manual

microNode Integration Specification Messaging Protocol
On-Ramp Wireless, Inc. 35 014-0033-00 Rev. H
opcode =MmsgREQ (1001)
payload size=6 (00000110)
The MMsg exchange is followed by the MHdr exchange, which includes the payload of the
CONNECT message.
 MISO: 01101010000000010000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000
 MOSI: 10101010000000010000110000000000001100100100000000000001000000000000
00000000000011110000111100001010010110100101
These bits indicate:
MISO: from slave to master (01)
length of message=2 (10)
opcode=MHdrACK (1010)
Hard coded byte=1 (00000001)
Unused Extra Data (0000…...0)
MOSI: from master to slave (10)
length of message=2 (10)
opcode =MhdrREQ (1010)
Hard coded byte=1 (00000001)
Payload:
length=12 (0000110000000000)
message type=CONNECT (0011001001000000)
host interface=True (00000001000000000000000000000000)
trailing sequence (11110000111100001010010110100101)
The payload of the message includes first the length, which is the number of bytes in the
payload including the length and the trailing sequence.
It is followed by the message type, which in this case is 0x4032, and corresponds with CONNECT.
The CONNECT message has a 4-byte field that is a Boolean flag specifying whether or not the
Node should send asynchronous SPI messages to the Host. To specify that the Node should send
messages to the Host, the value of 0x00000001 is used.
It is then followed by the standard fixed trailing sequence.
This message exchange is followed by a Node-initiated message exchange for the purpose of
sending an ACK of the CONNECT message to the Host. This starts with a SmsgREQ/SMsgACK
exchange over the SPI bus.
 MISO: 0110101100000100
 MOSI: 1010101111111111