I have just bought the ArduPilot Mega 2560 Full Kit... plus the Triple Axis Magnetometer HMC5883L. I should have it built over the weekend.. then i'm off to a my mates machine shop, and i'll make the splitter plate for the lower frame onto which i am going to fit the Ardupilot. the magnetometer i'll put on the tail as suggested. I am going to use my X-cell Razor 600E. For those that dont know its around the 50 size nitro heli.
Do i need to buy any other sensors i.e. the Sonar... i can fly a helicopter all day long but this is my first time flying one with stabilisation so any tips would be gratefully appreciated.
If this works well then i am going to try and use it on my x-cell gasser. i can get up to 20 minute flights with this. But i think for the time being a battery 600 is the way to go.
i'll post some pictures when i have it all together.
Anyone tested .49? We have a problem with the yaw. The heli spins. We saw that the yaw doesn't compensate when in flight mode but then in CLI the yaw seems to be working. Inshort, the motors is in reversed mode. Any idea?
we are using gy401, with gyro gain of 1680. Would the gyro not working?
dropped you a PM a minute ago. I think you said that you're seeing ver .39 in CLI? I suspect you're running an old version of the AP_MissionPlanner so you're uploading a very old version of the code.
The other likely possibility is that you're pulling the code directly from git and there's been a change to the way the servos update. You could add the following line to your AP_Config.h:
#define INSTANT_PWM ENABLED
Just for clarity, you gguys all got your ftdi drivers from here, right?: http://www.ftdichip.com/FTDrivers.htm
I just got a new Windows PC and I didn't have to do much..I just went into control panel, found the unknown device, selected "trouble shoot" and it went off and searched the internet for the driver and all was well...
Yes I have tried every action available to me, including manually selecting and loading the drivers, which then tells me the uknown device is a "serial converter", but has been unable to start (code 10) which means it is still defunct, do you know which pinouts or where I can get the pinouts for the ftdi chip on the oilpan to try connecting with the ftdi cable supplied for the xbee, because whenever I plug the xbee in it works no problem, creates a port an everything :/p>
Have you tried a different USB cable? Just in case...
I had to reinstall the drivers on my machine and found them in the arduino/hardware directory. The board also appears as a serial converter but I don't see the "unable to start" message like you do.
the ftdi pins for the APM board are on the left side near the back. You can see "FTDI" written on the top of the APM board.
Thanks Randy, what exactly would I be looking for in the hardware folder?? (Still a noob)
Great News, Kinda..!!
Using the ftdi device on the APM board it is working exactly right and shows up as a port, that I can then upload firmware and talk to it through the terminal however is it possible to do the setup without the oilpan, and if not, can I just solder pins from the top of the oilpan at the APM's FTDI out pins thing (If you can understand what I just said)??
I've never tried to do the set-up without the oilpan. I suspect it won't work because it should freeze when it tries to connect to the Data Flash. No idea if you can extend the pins on the top of the oilpan and continue to use the ftdi ports.
Actually, thinking about it more, it was a new arduino uno that I installed the drivers for by doing this. the procedure may be different for the APM.
1. open up control panel
2. view devices and printer
3. it appeared as an unknown device at the bottom
4. right-clicked on the unknown device, properties
5. change settings
6. clicked driver tab, update driver
7. browse my computer for driver software
8. selected "C:\Program Files (x86)\arduino-0022\drivers" and pressed Next
9. said "yes, install anyway" when it complained about the driver.
Thanks for your effort!
But still not functioning, I will try connecting the ftdi cable to the ftdi pins on the top of the oilpan as I could enter the setup menu's and all from the APM ftdi through the terminal.
I have really tried approaching this issue from every angle since day one - I had figured that it was simply a conflict with the 64bit windows I have, so left it alone until I had the heli assembled with all the gear ready to setup which I then went to set up on a friends computer running 32bit vista and then repeat ad nausem on a couple other computers, manually installing drivers etc. Now considering it did actually work two or three times, I know that it is possible, however the only logical conclusion I can reach is a defect/faulty part from the assembly.
I remember you said thatyou knew the owner/ operator/ someone from udrones.com - as I have had no reply from them could you possibly ask them about their item return/swap policies?
If there is no progress from that end by the time I get paid, Ill just order another one.