Seeker connection to QGC

[tom]

@Pooyan apt is only available on voxl2

See here for how to upgrade to the latest voxl SDK: https://docs.modalai.com/flash-system-image/#flashing-a-voxl-sdk-release

Make sure you follow the instructions for voxl1

[Pooyan]

@tom Thank you so much for helping.

I flashed the seeker as you said, but still I can't see all of the features!

As you can see the following services are missed:
voxl-feature-tracker
voxl-flow-server
voxl-px4-imu-server
voxl-px4
voxl-softap
voxl-static-ip

After flashing there was a window about welcoming, and I choose "Seeker" and keep entering for the configurations.

After flashing will the factory configurations stay remained? and do we need to do the SDK configurations?

I would really appreciate it if you could help me through this.

Best,

[tom]

@Pooyan Okay great, it seems as though you have the latest SDK loaded on the voxl.

I would now flash the flight core portion of the seeker with the latest px4 release which can be found in the flight-core directory of the voxl_SDK_1.1.2 directory. You can load this binary via. QGC

[tom]

@tom It can also be flashed with the px_uploader python script. See instructions for both options here: https://docs.modalai.com/flight-core-v2-firmware/#qgroundcontrol-fw-update

[tom]

@tom If your seeker has a Flight Core v1 it'll be the same process but just loading the FCv1 binary instead

[Pooyan]

@tom Thank you for the information.

For the QGC, I should connect it through the USB while when I do it with either Windows or Ubuntu, nothing will happen and QGC will not recognize the Seeker! I would appreciate it if you could give me some hints on this situation.

I have tried the link you sent me on Ubuntu, but the bootloader will not find the Seeker after using the following code:
./Tools/px_uploader.py --port /dev/ttyACM1 --baud-bootloader 1152000 /home/hulabs/Downloads/seeker/voxl_SDK_1.1.2/flight-core/modalai_fc-v2_1.14.0-2.0.63.px4
The location of the fc-v2, is from downloading the SDK 1.1.2 and the directory you told me to find it from.
I have tried both v1 and v2.
How can I know my flight Core is v1 or v2?

I think maybe the problem is with "/dev/ttyACM1" which I don't know my USB name in /dev location. what I have in my /dev directory is as follow:

The other thing is that in the link you sent me, it was said that for the bootloader step I have to connect the USB and I dont need to use external power source, however, if I dont power up the Seeker using its battery, there would be no USB connection. Is using USB connection with powering up the Seeker with its battery correct?

Sorry for providing too many problems and question at the same time.

[tom]

@Pooyan What is the serial number of your seeker? There should be a sticker on the frame of the drone with a number in the form MXX00000XXX

I should be able determine whether you have a v1 or v2 based off of that

If you're able to get a QGC connection via. USB you should be able to see the hardware version in qgc

[Pooyan]

@tom The serial is this: M22000001WW. Thank you for Checking. Do you think if you could give me some hints about the problems as well?

[tom]

@Pooyan That serial number seems to be the number for your power module. Maybe there's another elsewhere.

As for other tips...

Make sure you don't have the package brltty installed as that will often hijack devices on ttyACM, you can remove it with sudo apt remove brltty

Also, if you do in fact have a FCv2, you have to remove both power and usb and then only plug in power. It'll provide enough power via. usb in order to flash the device.

[Pooyan]

@tom Hello again and sorry for my late response.

There is another serial number: M2100000J6P

Thank you so much for checking that.

One thing I want to mention is that I couldn't ever get connected via USB only. I have tried both Windows and Linux. I need to connect the battery first, and then the USB will be recognized. Having said that even in that situation, it will not be recognized with QGC. I would appreciate it if you could give some hints on this.
On Ubuntu, I tried dmesg -w and made sure that till the power is not connected, the USB will not get connected.

I did sudo apt remove brltty as you said, and tried again but everything is still the same as screenshots I sent previously.

Do you have any more suggestions?

[tom]

@Pooyan Okay great thanks, It does appear that you have a FCv2. Can you show point out the USB port you are using in order to connect the flight core to your PC?

[Pooyan]

@tom Thank you.

Hope this is the answer to your request:

[tom]

@Pooyan So in the voxl-cam there are two separate boards: VOXL and Flight Core. That connector you're plugging into is USB port that allows you to access ADB on VOXL, seen here: https://docs.modalai.com/voxl-cam-user-guide-core/#connect-to-voxl-cam-with-adb

What you need to connect to in order to flash flight core is J3, which can be seen here: https://docs.modalai.com/flight-core-v2-usb-to-qgc/#j3---usb--qgroundcontrol

In the photo on this page it is the blue connector: https://docs.modalai.com/voxl-cam-user-guide-flight/#voxl-cam-v1-flight-core-setup

You need to use an MCBL-00010, seen here: https://docs.modalai.com/cable-datasheets/#mcbl-00010 in combination with a usb to micro-usb cable to plug into your pc

It can be purchased here: https://www.modalai.com/products/mcbl-00010?_pos=26&_sid=5684dd53e&_ss=r

[Pooyan]

@tom Thank you so much for letting me know. I didn't know they mean that when they say USB in the documents. I will buy that and get back to you. Thanks again.

[Pooyan]

@tom Hello again,

I got the USB cable and did the update for the FC2 using the QGC application. The versions I can see in QGC are as follow:

At first the Airframe and Actuators tabs were red, but now they are not. I tried to update the parameters through QGC, however, still in Actuators I am not sure if everything is fine:

Now, if I disconnect the USB and connect through wi-fi, still I can't get connected to the QGC, the red led will blink and the VOXL-inspect-services is as it was after flashing (no px4 is there in the list):

I will appreciate it if you could give me some hints on that.

[Pooyan]

@tom to get connected to the QGC, I need to configure the voxl-vision-px4 and add the ip to it in order to be able to get connected to the QGC, but this file does not exist and when I try voxl-vision-hub, there is no place for an ip to get connected to QGC.

[tom]

@Pooyan You won't see voxl-px4 in the last because that is only on voxl2 where px4 runs on voxl itself. In your case, px4 is running on the flight core.

In newer SDKs, you can set the gcs ip in /etc/modalai/voxl-mavlink-server.conf

{
        "primary_static_gcs_ip":        "192.168.8.10",

[Pooyan]

@tom Thank you so much. It is done.