PicoNet.1 messages

A PicoMessage.1 is sent by a master PicoNode.1 after bounding the bus. It has the following format:

Bytes	Bits	Name	Description
0	0	REQ	1 if the message is a request, 0 if it's a notification.
0	1..3	RSV	Reserved
0	4..7	LEN	Length of the DAT field in bytes
1	*	CMD	Message command
2..LEN+1	*	DAT	0 to 15 bytes of message data
LEN+2	*	CRC	A 8-bit CRC checksum

There are two types of message: request and notifications. Requests was the REQ bit enabled expects a response, while notifications only expects an ACK bit.

After the message, a bit (60ms) of silence must be inserted.

Then, if the message was a notification, the slave nodes should send the ACK bit. The ACK bits are transparently AND'ed by the physical layer and the master can send another message after inserting another bit of silence.

If the message was a request, a response with the following structure must be send by the slave nodes.

Bytes	Bits	Name	Description
0	0	ACK	1 if the request was correctly received.
0	1..3	RSV	Reserved
0	4..7	LEN	Length of the DAT field in bytes
1..LEN	*	DAT	0 to 15 bytes of message data
LEN+1	*	CRC	A 8-bit CRC checksum

When sending the response, all the slave nodes must check every 1 symbol which is sent. If it's overwritten by another node, then the node inhibits and changes to the idle state.

When the request CRC isn't correct, a 0 is sent in the ACK field and all the nodes return to the idle state and no more bits are sent. Then, the master must release the bus and a new master election begins.