SABINE NAVIGATOR - SERIAL PROTOCOLS Manual

Sabine Navigator Communication Protocol (October 19, 2007)
This document applies to the following Sabine Navigator Models:
NAV240, NAV360, NAV480, NAV4802, NAV8802.
General structure of communication packets:
<0x01><R/W><SRC><COMMAND
1 1 1
<R/W> -
<SRC> -
The <COMMAND HEADER> is used to identify the types of value following the header. The value of the header indicates
the number of readable ascii bytes in the value that follows.
NAME
Command Header <0x03 to 0x07>; 0x03 = 4 bytes ... 0x07 = 8 bytes
Device Header <0x08> 1 byte
I/O Header <0x09> 1 byte
Channel Header <0x0A> 1 byte
Aux Header <0x0B> 1 byte
Column Header <0x0C> 1 byte
Data Header <0x10 to 0x18>; 0x10 = 1 byte ... 0x18 = 8 bytes
<VALUE> must always follow the <HEADER>.
Command Value
Device Value
I/O Value
Channel Value
Aux Value
Column Value
Data Value
HEADER><VALUE>...<0x1F><CHKSUM><0x02>
4 1
Read = 4 (ascii 0x24), Write = 5 (ascii 0x25)
Device number which sent packet: <0x7f> => PC
CODE
Command ID in ASCII character (see table below)
Device # where this command is sent to
0x20 for Input, 0x21 for Output
Channel #, zero-based
For extra information such as EQ Num, FBX Num ,etc
Reserved for later use
The actual value to change for the command targeted
•
S a b i n e , I n c .
( 3 8 6 ) 4 1 8 - 2 0 0 0
1 1 1<= sizes in readable ascii bytes
1 3 3 0 1 N W U S H i g h w a y 4 4 1
• ( 8 0 0 ) 6 2 6 - 7 3 9 4 •
Comment
How many bytes follow for the command
name (usually 4)
Always set to 0
# of bytes that follow
•
A l a c h u a , F l o r i d a 3 2 6 1 5 - 8 5 4 4 U S A
•
F a x ( 3 8 6 ) 4 1 8 - 2 0 0 1
E - m a i l : s a b i n e @ S a b i n e . c o m
w w w. S a b i n e . c o m