Is there another way to input waypoints into 2.2.3. I am unable to get the utility to read or write data, comes up with something is wrong!Any suggestions as to why the utility program wont read/write or importing the points, I have been told they can't be entered manually into the programPaul
You need to be a member of diydrones to add comments!
If you are using the Adafruit FTDI cable to communicate with the Ardupilot, make sure that you have the latest FTDI drivers (2.04.16) installed on your PC.
Originally I could only upload with the GPS disconnected when using the Adafruit FTDI. An update to the latest FTDI drivers resolved the issue with the GPS being connected and not being able to upload. I did notice that the FTDI cable will not always reset the Ardupilot and will appear to hang though you will not get the usual upload problem message. All you have to do is manually reset the Ardupilot and the upload should proceed as normal.
Sounds like your'e having good success Damon. How far have you progressed with your Ardupilot? Can you upload through the shield with the GPS attached? Are you able to read/write from the configuration utility?
No, I didn't have the jumper in before I turned on Ardupilot.
Thanks!
Jerry,
I was thinking along the same lines. How to get around the configuration utility to do some flight testing. One idea was to turn on the fake bearing (line 9-1 in the .h file) and hard code the flying altitude. Basically, the same idea as using RTL.
That's pretty cool Reto that you have the Ardustation "in the loop" for feedback. The progress bar only reaches halfway and then I get the "somethings wrong". I just ordered the latest recommended FTDI cable so I'll probably just wait until it comes in or Jordi finds another solution.
Damon,
I just tried your idea to fix the read/write to the Config utility. I've got the 3.3V FTDI board and disconnected the #6 pin. Followed your instructions but still cannot read or write. It was worth a try!
He fellows,
For those of you that are still having problems uploading the software, I think I’ve found the fix.
I just read on another post about one of us had found a bad solder joint on the headers and so I went to double check mine. The solder joints looked good but I found the DTS or GRN line still didn’t have continuity point to point between the headers.
At the risk of sounding obscene, the pins being provided are almost too small for the female header. That’s right, she wants it fatter! I tinned the pin and even bent it slightly, (all of them) and now I can consistently upload the program through the shield board.
I tried the utility program and I could see it talking that I haven’t seen before, but still got “something’s wrong” and “can’t read” errors, but that’s ok, I’m going back to the manual.
Good Luck
Sorry Guys,
I was getting a little frustrated last night. So close to flying! I'm sure Chris and Jordi will get this straitened out. There's an old saying about production. There is cheap, fast and quality but you can never have all three at the same time. I'll just have to be patient because a low cost, high quality Ardupilot will be worth the wait!
It’s a little disconcerting when Chris says, “when I try the Sparkfun 3.3v board, I get the same problem you do”. The manual shows the Sparkfun FTDI board being used. Here is the picture taken directly from the manual. Notice the small, red wire in the lower right corner of the board. Does anyone else have this wire on their Sparkfun boards? I don’t and I’m guessing someone had to add it to get the board to work with the ATmega 328.
I am using the Sparkfun FTDI cable. It works fine with the ATmega168 board so shouldn't it also work with the ATmega328? I don't think it's an issue Sparkfun has to address.
I just removed the shield and plugged the FTDI directly into the board(GPS removed)---same problem. So it looks like the problem is localized to the ATmega 328 board.
Replies
If you are using the Adafruit FTDI cable to communicate with the Ardupilot, make sure that you have the latest FTDI drivers (2.04.16) installed on your PC.
Originally I could only upload with the GPS disconnected when using the Adafruit FTDI. An update to the latest FTDI drivers resolved the issue with the GPS being connected and not being able to upload. I did notice that the FTDI cable will not always reset the Ardupilot and will appear to hang though you will not get the usual upload problem message. All you have to do is manually reset the Ardupilot and the upload should proceed as normal.
Hope this helps.
Regards,
TCIII
No, I didn't have the jumper in before I turned on Ardupilot.
Thanks!
I was thinking along the same lines. How to get around the configuration utility to do some flight testing. One idea was to turn on the fake bearing (line 9-1 in the .h file) and hard code the flying altitude. Basically, the same idea as using RTL.
I just tried your idea to fix the read/write to the Config utility. I've got the 3.3V FTDI board and disconnected the #6 pin. Followed your instructions but still cannot read or write. It was worth a try!
For those of you that are still having problems uploading the software, I think I’ve found the fix.
I just read on another post about one of us had found a bad solder joint on the headers and so I went to double check mine. The solder joints looked good but I found the DTS or GRN line still didn’t have continuity point to point between the headers.
At the risk of sounding obscene, the pins being provided are almost too small for the female header. That’s right, she wants it fatter! I tinned the pin and even bent it slightly, (all of them) and now I can consistently upload the program through the shield board.
I tried the utility program and I could see it talking that I haven’t seen before, but still got “something’s wrong” and “can’t read” errors, but that’s ok, I’m going back to the manual.
Good Luck
I was getting a little frustrated last night. So close to flying! I'm sure Chris and Jordi will get this straitened out. There's an old saying about production. There is cheap, fast and quality but you can never have all three at the same time. I'll just have to be patient because a low cost, high quality Ardupilot will be worth the wait!
-
1
-
2
of 2 Next