Here's a step-by-step procedural outline on how the validate if the connection and comm is working:
#1- Launch the mDACS app, and ensure the RRC3 is connected physically, but powered OFF (USB power switch is OFF). The required connections are the USB cable connected into your PC and USB-IO dongle, and the blue comm cable connected to USB-IO dongle and RRC3.
#2- Go to System Preference tab and check to see that the correct COMM port is selected. If you have already configured your COMM port, the mDACS app Status Bar should display a "green check icon" in Port Status. It may also require a couple clicks on the "Active Comm Port" dropdown to correctly show available ports (an improvement I'll be working on). Also ensure your selected comm. port matches the port number assigned to the USB-IO dongle (you can validate this in the Windows Device Manager).
#3- Switch over to Diagnostics tab.
#4- Click the "RRC3 Host Connect" button. Validate the TX LED on the interface board is blinking, then switch the USB power switch on. The big red LED should light on RRC3 and connection should get established. (note: You have a 15 second countdown where mDACS will attempt connection. When the RRC3 powers up, it looks for connection during its first 5 seconds of operation).
#5- If you are connected to the RRC3, the "Host Connect" button, should gray out and all the other Diagnostic buttons should be enabled. Click once on the "Manual Loop" button. This will query the RRC3 for data and should result in an update to the all Diagnostic indicators. If you have diagnostic data displayed, try clicking on the "Auto Loop" monitor button. This will repeatedly query the altimeter every second for data, and will continue until you click the "Manual Monitor" button again.
If you can get this level of operation, this means all the hardware is operational.
If you have made previous flights, you should be able to click on the "Flight Viewer" tab, and "upload" your flight data into the Viewer graph and Summary controls.
There is a known issue with the mDACS code which may occur if you experience a communications error. If the app becomes unresponsive after an error, the communications process may be hung in the background. Close down the mDACS app and ensure there's no lingering 'mDACS" process in your Task Manager. If the app is closed an you see an active "mDACS" process, kill that process before re-launching the mDACS app and attempting another Host Connect session.
