Hi everyone!

I've been building a drone as part of a senior design program I'm a part of to lift some objects.  Our team has been having intermittent issues with our remote controller (a RadioLink AT9S) communication with our flight controller (DJI N3).  We are using the RadioLink AT9S Remote Control with a R9DS S-Bus receiver.

Our entire system was working yesterday, our AT9S controller was properly communicating with the N3 controller and would turn on/control the drones motors.  We were able to properly see all the channels being outputted from the AT9S controller on the DJI Assitant 2 computer software when the drone was plugged in.  However, now when we turn our N3 Controller on the LED module flashes yellow rapidly indicating "remote controller signal lost" yet our AT9S remote controller is on as it was yesterday?

Troubleshooting that has taken place: Have turned all systems off/on again, tried moving the S-BUS reciever around the frame to different locations, and tried plugging the drone into the DJI Assistant 2 software to view the controller outputs.  Today when the drone was plugged into the DJI Assistant 2 software, we are no longer able to see the channels being outputted from the AT9S remote control (we could see live controller inputs in these channels yesterday).  All channels are dead/inactive and read "0".  When the drone is turned on, the AT9S remote controller indicates it sees a signal being broadcasted in the area (with a 5/5 bar signal), however it does not receive any telemetry from the drone such as voltage, positioning, altitude, etc.

Does anyone know why this might have happened?  The S-Bus indicates it is still receiving the AT9S's signal.  DJI Support was no help, their only suggestions were to make sure software was up-to-date.  No changes were made to the hardware or programming between yesterday (when it worked) and today (when it no longer recieves signal).  Any help or suggestions are appreciated, as we are incredibly stumped at the moment.

Thanks,

Cooper

Scratch that.  It ended up being an issue with an input on the remote controller.  We no longer need help with this problem!