Ok, there has been a lot of movement in my design or should I say architecture? We have moved from my hatred of USBs where things never come up on the same address twice. A prime example is the Arduino IDEs virtual serial port. Oh, well I'm digressing. The way the system works is simple there are two communications systems going on here.
- Ethernet which is used for NAVbus communications. This network controller is the NAV model, and it connects to boxes that rely on the aircraft position, in the three axes, plus the accelerations in the three axes as well, it also gives latitude and longitude on the earth. The Radio Sub System or RSS also must have both the aircraft position and the position on the earth, as well as its altitude, for some of its math problems.
- CANaerospace which is used for most of the intercommunication between the Feild Replaceable Units or, FRUs and the servers like NAV, RSS, etc.
- CANbus which is used in some cases only if the device is a standard CANbus device.
Please Note that this system is much easier to implement as the CANaerospace protocol uses the ISO stack as well as Ethernet, So the protocol converter is written in a few lines of JAVA. Also, CANaerospace is self-identifying. That is to say that the data payload, is identified by the header, which includes number/string types, as well as other info.
I could not find a good icon for Radio FRU, so it now has blinking lights, al la modem. The same holds true for the Protocol Converter.
