element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Personal Blogs
  • Community Hub
  • More
Personal Blogs
NexGen Flight Simuator NexGen RSS Continued.. The Protocols
  • Blog
  • Documents
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
  • Share
  • More
  • Cancel
Group Actions
  • Group RSS
  • More
  • Cancel
Engagement
  • Author Author: phoenixcomm
  • Date Created: 13 Feb 2013 11:37 PM Date Created
  • Views 710 views
  • Likes 0 likes
  • Comments 1 comment
  • serial_communications
  • hardware
  • flight_simulation
  • usb
  • software_design
  • radio
  • protocol
  • diy_cockpit
Related
Recommended

NexGen RSS Continued.. The Protocols

phoenixcomm
phoenixcomm
13 Feb 2013

Protocols again? Are we ever done talking about protocols? No not really. And BTW this is really RSS version 2!  RSS v1 can be found on my other wordpress blog. This version eliminates most of special hardware and its bus and chassis. Most radios heads can be handled by a Arduino Mega256 as it will handle two radios or that is one radio head. If the Mega256 can't handle the job I can then use the Stellaris Launchpad from TI. 

 

We will use one of my Gables G-3717 Dual Nav Head as the guinea pig. http://phoenixcomm.files.wordpress.com/2012/02/nav-pinout.jpg

Gables G-3717 Dual Nav Head

Ok so lets get to work first we need to gather some information.
  • Does this radio head have more than one radio? YES
  • If yes, how many radios are in this head? 2
  • What type of radio head is this? ARINC-410
  • Do we have a pin-out? YES

 

As you can see from the pictures and the table on the right we need ether 5 ASCII letters or 2 ½ bytes for packed format. We also need to label each radio not the head. So that's another ½ byte for a total of 3 bytes. So why are there 4 bytes? The first is byte is a START signal to the receive side to start looking at the input, and start counting bytes. But wait ARINC-410 is a 2 of 5 code and its LOW ACTIVE! And BTW is 28 volt logic to boot, that's in the aircraft, so we will use 5volts.  Well not going to send them low active and we will convert the ARINC-410 to Packed Binary or Packed BCD so we can pack each nibble..

 

2 of 5 Code Table
No.ABCDE
0
X

X
1XX


2X
X

3
XX

4
X
X
5

XX
6

X
X
7


XX
8X

X
9X


X
Slave Transmit
Byte 1Byte 2Byte 3Byte 4
FF0001 - 00010000 - 10000111 - 0101

start-byte

11

08

75

 

So you can see that the Slave is transmitting what radio #1 (first nibble of Byte 2) is tuned to 108.75 as you can plainly see in the photograph.

 

Ok so that takes care of the tuning. But what about the other switches. Ok lets make this eazy lets add another byte, making that number 5. And since there are 8 bits in a byte we now have up to eight switches, or by using the whole byte we could have 256 switches, so why don't we just use the 7 low order bits and the MSB the state of the switch so now we have 128 switches and their states. This way we can assign the switches to numbers in a table. So we can safely say that the OFF/ON or Power switch is #1. In the table below bit 7 is the MSB, and the x indicates the state which is a 0 or 1.

 

Switch Byte and Table Layout
bit 7bit 6bit 5bit 4bit 3bit 2bit 1bit 0Radio #Radio NameSwitch Name
x00000011NAVPower
x00000101NAVVOR_TEST
x00000111NAVUP_RIGHT
x00001001NAVDME_STBY
x00001011NAVOVER_RIDE

 

 

So this really takes care of the Slave_410.tx.c this runs on the embedded microprocessor. We sill need Slave_410.rx.c thats so we can comand the radio head to turn off etc.

 

So this really takes care of the Slave_410.tx.c this runs on the embedded microprocessor for ARINC-410 class of control head.

 

image Keep Tuned in More to Come

~Cris

 

BTW Next blog is the Linux Side Control

  • Sign in to reply
  • phoenixcomm
    phoenixcomm over 12 years ago

    here is a quick update to the output of the slave...

    It is now a 5 byte stream

    The following are the nibbles in the output stream:

    1. F - first nibble of the Start Byte
    2. F - second nibble of the Start Byte
    3. x - class of radio that will give me 16 classes. ie ARINC-410 is a class. This is our interrupt helper
    4. x - what radio panel is it. 1 - F
    5. x - what radio in that panel is it. normally 1 or 2 but could be more.
    6. x - frequency hundreds
    7. x - frequency tens
    8. x - frequency units
    9. x - frequency tenths
    10. x - frequency hundredths
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube