Australian support
- Thread starter Fenshome
- Start date
Murray Martz
Premium Pilot
- Joined
- Jan 29, 2017
- Messages
- 1,370
- Reaction score
- 768
Hey mate I can help.
You can call me anytime.
Except Saturday.
www.mountainview.enterprises
For my phone number.
- Joined
- Jan 1, 2019
- Messages
- 91
- Reaction score
- 31
- Age
- 77
Hi folks, my first post here.
Flew my Chroma on a Saturday (a few weeks ago), Sunday , turn on ST10+ controller and all the screen said was NA everything! *&$#%! and #$@%%^&.
Video is good and think I tried every thing that my pea brain could think off.....I am not very clued up with all this electronic jiggery pokey stuff.
Being an old hand at RC planes and stuff, all I can fly now are Drones coz I'm in a wheelchair.
Can land beside me see.
Re calibrated controller, connected the GUI- all seems well with the bird, still got the NA messages.
What to do now?
Thanks in advance.
I'm in Kellyville NSW.
Flew my Chroma on a Saturday (a few weeks ago), Sunday , turn on ST10+ controller and all the screen said was NA everything! *&$#%! and #$@%%^&.
Video is good and think I tried every thing that my pea brain could think off.....I am not very clued up with all this electronic jiggery pokey stuff.
Being an old hand at RC planes and stuff, all I can fly now are Drones coz I'm in a wheelchair.
Can land beside me see.
Re calibrated controller, connected the GUI- all seems well with the bird, still got the NA messages.
What to do now?
Thanks in advance.
I'm in Kellyville NSW.
[QUOTE="Sunday , turn on ST10+ controller and all the screen said was NA everything! [/QUOTE]
@Chroma Pilot. please let us know what you find, and how things turned out.
@Chroma Pilot. please let us know what you find, and how things turned out.
Your issue sounds like there is no 2.4 GHz communication with the Chroma. One real possibility is a bad Chroma receiver or just a corroded/bad receiver connector.
Some symptoms to look for:
NOTE: None of these wires are related to video. If no video is present, it is likely the problem is elsewhere.
Bad Gray Wire: No telemetry available on ST10+. May be able to control the drone.
Bad Yellow Wire: No flight control of drone (big problem if it fails during flight.). May have telemetry.
Bad Black OR White wire: No flight control, no telemetry. (Again, big problem if failure occurs during flight)
The first thing to try is to pull the connector apart a few times to see if it will restore the connection. This may or may not help, but it is not very difficult. The first two pictures show how to access the connector, and which connector to work with.
The drawing at the end is a little hard to follow, and isn't real important. It is included in case you need to troubleshoot.
This drawing is a little hard to read, but it can show you what color wire is associated with which function, and which overall “paths” should have continuity. The wires change color at the connector, so the functions are NUMBERED at each measurable point.
Some symptoms to look for:
NOTE: None of these wires are related to video. If no video is present, it is likely the problem is elsewhere.
Bad Gray Wire: No telemetry available on ST10+. May be able to control the drone.
Bad Yellow Wire: No flight control of drone (big problem if it fails during flight.). May have telemetry.
Bad Black OR White wire: No flight control, no telemetry. (Again, big problem if failure occurs during flight)
The first thing to try is to pull the connector apart a few times to see if it will restore the connection. This may or may not help, but it is not very difficult. The first two pictures show how to access the connector, and which connector to work with.
The drawing at the end is a little hard to follow, and isn't real important. It is included in case you need to troubleshoot.
This drawing is a little hard to read, but it can show you what color wire is associated with which function, and which overall “paths” should have continuity. The wires change color at the connector, so the functions are NUMBERED at each measurable point.
Last edited:
