need some help for designing a NMEA to gyro (STD 20) course bus converter

[hanif]

Hi,

i want to design a miccroncontroler based to NMEA to heading/course bus converter for STD 20 gyro heading/course output. b/c the receiving device (display) is Anschütz (STD 20) course bus compatible.

please follow below link to understand what i want

Aardvark 8 NMEA 0183 to Anschutz STD20 data.
Aardvark

anybody has any information regarding Anschütz (STD 20) course bus like baud rate , data format i.e how heading information presented in it. what i so far understand is this is a type of data transmission of gyro heading/course. i have read its name along with NMEA 0183.

i need this information badly because i a device which is transmitting heading data in this format instead of NMEA and i can't understand it.


PLEASE HELP. i would be very thankful

 

[bigdogguru]

The Anschutz standard 20 gyro – EIVA 121 Binary std. 20 format:

<stx><gyro><chg><mc1><mc2><rot><status><compass><chk><eot>

Hope this info helps.

---------- Post added at 04:07 ---------- Previous post was at 03:21 ----------

Here is a detailed Anschutz standard 20 gyro – EIVA 121 Binary std. 20 format:

 

[hanif]

THANKS SO MUCH,

But if i want to convert the heading/course reading from NMEA 0183 to course bus standard , which byte should i focus?

what i understand from the format , i would like to share with you, please correct me if i am wrong.

The Anschutz standard 20 gyro – EIVA 121 Binary std. 20 format:

<stx><gyro><chg><mc1><mc2><rot><status><compass><c hk><eot>


stx ---> starting byte ,

gyro --> gyro identy code

chg ---> ? (not cleared)

mc1 mc2 ---> magnetic compass 1 & 2 identy code

rot --> rate of turn

status ----> ?

compass ---> value of compass (gyro , mc1, mc2 or rot)

eot --> ending byte

chk ---> check sum

 

[bigdogguru]

Bytes 1 and 2 containing the heading information. While bytes 8, 9 and 10 contain the heading rate in degrees/min (velocity). You'll need to convert the NMEA 0183 information into these parameters. What is the device originating the NMEA data? Does it have a custom NMEA sentence which might already contain this information?