Servers by jDrones

About the APSync / Companion Computers category

nvidia-tx1
apsync
raspberrypi
intel-edison
ardupilot

(rmackay9) #1

Discussion and support for APSync and Companion Computers

APSync wiki: http://ardupilot.org/dev/docs/apsync-intro.html
Companion Computer wiki: http://ardupilot.org/dev/docs/companion-computers.html
Gitter chat (for developers): https://gitter.im/ArduPilot/companion
GitHub repo: https://github.com/ArduPilot/companion


(Randy Bachtell) #2

Thanks Randy for starting this discussion. I realize that we are on the bleeding edge of this whole process but this is why I am investing in Pix2 and I want to help out any way I can. I am not a programmer but understand the process and systems.
I have posted in hardware and the P2 discussions and will add my findings so far here.
I have successfully flashed APSync on two Edisons, one in my P2 and one on a breakout board. In both cases I do not get an access point to show up on my network or UDP on APM Planner. I have wifi access on both my piercer and my solo. With the latest flash the password to the root file system on the Edison has been changed so I can’t get in to look around, leaving me with a couple of Edisons that apparently do nothing at all. I saw on gitter chat that there is some discussion around similar issues. I want to help but at this point all I can do is report what I have done.

Thanks,
RB


(LeonDwyer) #3

rmackay9.

Having an issue getting MavLink talking over UDP.
I install apSync on the Edison, plugged into telemetry port 2 on PixHawk 1
Set up the prams on Pixhawk,

Connected to Wifi on Edison.
UDP connects
But then MavLink fails to download parameters

When I ssh into the Edison and run mavproxy.py I get
Link 1 okay
Link 1 down
Cycling on and off.

What am I missing? Thanks for your Help.


(Randy Bachtell) #4

Big giant thank you to Peter. After flashing the revised image all is well, I have wifi UDP connection. I am really looking forward to all that is in store with the P2 and companion computers. Thanks to all for all the time and effort you put in.

Cheers,
Randy Bachtell


(peterbarker) #5

Having an issue getting MavLink talking over UDP.
I install apSync on the Edison, plugged into telemetry port 2 on PixHawk 1
Set up the prams on Pixhawk,

Connected to Wifi on Edison.
UDP connects
But then MavLink fails to download parameters

Try adding “–mav10” to the MAVProxy command line.


(LeonDwyer) #6

I should say, I’m trying to connect with mission planner.
UDP connect, but the parameters fail to download.

I can get it to work with a PixHawk 2.1 but I want to use an old Pixhawk 1 for this project.


(peterbarker) #7

I should say, I’m trying to connect with mission planner.
UDP connect, but the parameters fail to download.

Are you getting packets of any sort? I assume so if the udp connect
completes.

I can get it to work with a PixHawk 2.1 but I want to use an old Pixhawk 1
for this project.

That’s … weird.

Is the firmware up-to-date on the PixHawk1?

Are you using the latest image on the CC? There was an issue where a
parameter was missing on the mavproxy commandline on the CC, which has
been fixed in the most recent images.


(LeonDwyer) #8

PH1 has the latest firmware.
CC has the image from yesterday.

Connecting the Edson vir telemetry 2 with a UART breakout board from spark
fun.


(John R) #9

I missed this post when I started a new thread here Connecting an Edison to a Pixhawk 1 , was wondering if you could look at the other thread and comment??

Thanks!


(Akshay Timmalapur) #10

LeonDwyer.

I am doing something very similar to what you are doing. In my case I am using Raspberry pi 3 Model B instead of Edison. Even in my case MAVlink fails to download parameters via UDP.

Any help? Thanks.