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: NASA's Edian Lite, Revisited
  • Blog
  • Documents
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
  • Share
  • More
  • Cancel
Group Actions
  • Group RSS
  • More
  • Cancel
Engagement
  • Author Author: phoenixcomm
  • Date Created: 16 Nov 2019 7:07 PM Date Created
  • Views 298 views
  • Likes 3 likes
  • Comments 0 comments
  • diy hardware
  • diy aircraft cockpit
  • diy software
  • nexgen flight simulator
Related
Recommended

Nexgen: NASA's Edian Lite, Revisited

phoenixcomm
phoenixcomm
16 Nov 2019

To give you all a refresher about NASA's EADIN Lite Communications Protocol, I was happy to embrace it.image

The problem is the downsides for me:

  • Only an 8-bit payload.
  • Before the Data Field, I need a Data Lenth Field of 1 byte
  • Each board must be programmed for its unique address in the chain. As I am very lazy, I can resolve this by installing a 4-bit switch that can be set be for installing into the network. This address is read at startup.
  • And I don't need the CRC check
  • Also, the node_ID and sender_ID can be put into one byte where sender =0x00 and a destination or slave is 0x00. As one byte is eight bits I can use the high order for the sender and low order for the destination. So "0014" the sender is 00 and the slave is 14 fins.

This leaves me with

 

BEFOREAFTER
  • Preamble: 3 bytes
    • 2 bytes start of message (0x00, 0x01)
    • 1 byte a sync byte (0x55)
    • Header: 5 bytes
      • 1 byte request type (ENQ/ACK/NAK = 0x05/0x06/0x15)
      • 1-byte node_ID of destination
      • 1-byte node_ID of the sender
      • 1-byte unique message number
      • 1-byte extra space to be used in future development
    • Data: X bytes (8 bytes Default)
      • 8 bytes DATA_L (can be modified)
    • Footer: 2 bytes
      • 2 bytes CRCFast (a 16 bit CRC, Default)
  • Preamble: 3 bytes
    • 2 bytes start of message (0x00, 0x01)
    • 1 byte a sync byte (0x55)
  • Header: 4 bytes
    • 1 byte request type (ENQ/ACK/NAK = 0x05/0x06/0x15)
    • 1-nibble node_ID of destination
    • 1-nibble node_ID of the sender
    • 1-byte unique message number
    • 1-byte payload length in bytes
  • Command:
    • 1-byte Command Payload (Simple commands for reading and writing)
  • Payload
    • Variable Length (one-byte standard (longer payloads such as Time Lat/Long etc.
  • Footer:
    • 2 bytes - End of Message
18 Bytes11 Bytes minimum
  • Sign in to reply
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