EM 406 BINARY?!
Hello all!
I finally got around to buying the necessary parts to setup an autopilot configuration for a Ground Unmanned Vehicle.
Anyways, here's my issue, and I really need your help (my sanity depends on it).
I'm using the current ardupilot board, the current ardupliot code, and an em406 gps module.
I am NOT using a shield as it was unnecessary to purchase as I will not be in the air.
Well, my gps wont fix. The red LED on the gps module is solid, suggesting that I'm in not in binary mode, and I need to be in binary mode, right?
I've tried the sirf demo from the sparkfun website and I can't get the sirf demo to connect to the gps.
(this might be an issue because i use an ftdi cable into a ardupilot which is also connected to a gps, but they use the same serial port, but if i don't connect both the gps and ftdi port how can I change to binary protocol?)
I've also heard that the arduino code should change the gps module into binary automaticaly. I've run the code, and no, this is still not the case. (solid LED).
I'm |this| close to just..losing it :(
Replies to This Discussion
-
Permalink Reply by andrew bae on -
I just want it to change the em406 to binary. Any thoughts?
-
Permalink Reply by Jeremy on -
I am no expert but I have the same GPS module as you and mine the first time using the em406_test file it took roughly 25 min to get a solid lock for the GPS and then seems to have no problems since then. So maybe you havent left it running long enough for the code to do what it should and for the module to connect. Is it at least close to a window ledge? I have mine one a flat piece of wood as close to the window as I can be and seemed to work. Hope maybe some of this will help you out. My LED also started super bright then after the first lock its now dim which from what I read is normal. But I have a shield on mine so not sure
-
ModeratorPermalink Reply by Chris Anderson on -
It won't switch into binary unless you go through the startup procedure. Either:
1) If you've soldered on the two wires on the bottom and have RC signals plugged into Channels 1-3 and Mode
or
2) You're using the bind plug
-
DeveloperPermalink Reply by jasonshort on -
The 406 tester file contains the startup procedure that will make the 406 go into binary.
http://ardupilot.googlecode.com/files/EM406_tester.zip
The 406 will jump back to ascii at startup sometimes. So I put the binary mode function at Ardupilot startup.
Jason
-
Permalink Reply by andrew bae on
-
well, i got the code to load up and the LED is dim now. I tried loading the code form different computers and the mode finally switched over. thanks for the great help guys, i'll probably need more debugging help soon :). gps seems like it's taking forever to lock..
-
Permalink Reply by andrew bae on
-
okay, i got the gps to lock, haha. Sorry to be blowing up your e-mail accounts, but now my config tool wont write. Before I got the code working (or shall I say "binary" working), i was able to configure waypoints via config tool. Now, after I select my board and com port, I click write before I do anything. And it just stays on "writing data..." and by the way the gps LED is blinking.
The FTDI cable is the only thing plugged in (along with a 9v battery) and there is NO gps module plugged in while I am trying to configure the ardupilot.
More help? :D
-
ModeratorPermalink Reply by Chris Anderson on -
Reboot and try again. I assume if you're using a 9v battery that you've switched the power solder jumper, etc?
-
Permalink Reply by andrew bae on
-
yes. and I've booted many many times. By power solder jumper you mean the solder bead that you move over so I can have it run off the 9v battery and not the esc?
In that case, yes. By "etc", I don't knwo what you mean, I hope there wasn't more you needed to do.
Also, I didn't solder the two 30 gauge wires under the ardupilot. I understand they're for throttle control but I will not be using any sort of throttle control. would this have any other adverse effects on the board? The gps locked, the gps switched from nmea to binary, so things are looking good so far...
-
ModeratorPermalink Reply by Chris Anderson on -
Yes, that's what I mean, and by "etc, I mean that you're powering it from the BATT +- pins.
One of the problems with open source projects is that there are an infinite number of ways people will try to use the hardware (and an infinite range of hardware they will try to combine it with) and software and it's impossible for us to try and test each one, so we only support the recommended configurations. I really don't know why your config utility isn't writing to the board. Try it on another computer?
You might also want to try the WaypointWriter.pde in the Test Suite.
-
Permalink Reply by andrew bae on
-
well, thanks anyway, and for the quick replies, too!
I'm getting the darn avr_dude not in sync error again...christ. Well, it happened before and miraculously fixed itself, hopefully that will be the case again.
-
Permalink Reply by andrew bae on
-
Alright, Chris, I've gotten it to work it was a problem with the FTDI cable but it is now fixed! BUT ANOTHER ISSUE. Darn, this process is just...painful.
Last thing. I get the "something is wrong" statement from the configuration tool, but after reading, it reads successfully, with the correct gps coordinates.
when i plug the gps in, that "stat" LED blinks rapidly.
NOW after I plug in the gps module (and nothing else, no servos, motors or motor controllers, radio in, etc) to test a gps lock, the gps lock LED no longer blinks. if I take the gps module out and just have the arduino board powered, the gps LED will blink. will the board not work without any hardware?
edit: and NOW the red LED on the gps module (em406) is now BRIGHT red. Perhaps the incorrect writing is overwriting the gps parser code?
-
DeveloperPermalink Reply by jasonshort on -
The 406 will randomly drop out of binary at startup. I never figured out why. But, the current code should force it back into binary at startup.
"something is wrong" That's a known issue with the config tool. Just ignore it. The new GCS will replace this tool.
The stat LED is the Arduino pin 13. It blinks with every loop of main if it has not been overridden. Most people here override it for the throttle input.
The board should blink with nothing attached. It would be easier to help if you zipped your files up, including the header file, and your log files. Please post them here.
Thanks,
Jason
Contests
Season Two of the Trust Time Trial (T3) Contest has now begun. The third round was a reliablilty/aerial photography round for both planes and copters, which is now closed. Stay tuned for the next round, beginning soon.A list of all T3 contests is here.
Top Content
Groups
-
Moderators
58 members
-
ArduCopter Evolution Team
106 members
-
Learning to program the …
54 members
-
UK Ardupilot Group
27 members
-
DIYDrones - CNC Project
59 members
© 2012 Created by Chris Anderson.
