@Κωνσταντίνος-Κλέων-Χριστόπουλος In that case we can't help you with SSH or WiFi, that's not our hardware
Posts made by tom
-
RE: Complete reset of M0018 flight core
-
RE: Complete reset of M0018 flight core
@tom And I can't see from the video whether you have a VOXL on board or not?
-
RE: Complete reset of M0018 flight core
@Κωνσταντίνος-Κλέων-Χριστόπουλος You need to have the 4-pin JST to USB cable plugged into the blue connector if you want to access QGC over USB
https://docs.modalai.com/flight-core-datasheets-connectors/#j3---usb-connector
J3
-
RE: Complete reset of M0018 flight core
@Κωνσταντίνος-Κλέων-Χριστόπουλος It doesn't appear that VOXL is being detected at all. Can you share a photo of how you have it connected to your host machine?
-
RE: VOXL2 - Cube Orange External Flight Controller Integration
@Jetson-Nano You can disable px4 on voxl with
systemctl disable voxl-px4
to ensure its not running -
RE: Complete reset of M0018 flight core
@Κωνσταντίνος-Κλέων-Χριστόπουλος When connected to an ubuntu machine, what do you see with
lsusb
-
RE: Cannot communicate over adb/fastboot after flashing image
@Kashish-Garg-0 It's possible your board has a QSM8250 (M0054-2) instead of a QRB5165 (M0054-1), see here for the diffs: https://docs.modalai.com/m0054-versions/#m0054-1-and-m0054-2
If that is the case then you will have to QDL using a different build, which you can download from downloads.modalai.com, look for
M0054-2 Starling QDL Image 1.7.4 2024-02-09-1.7.4-M0054-2.zip
under the "All" category -
RE: Complete reset of M0018 flight core
@Κωνσταντίνος-Κλέων-Χριστόπουλος We only really use Ubuntu here so that would be a good thing to try.
I missed that you said the drone was in WiFi AP mode
You can SSH onto the drone by connecting to that wifi (password 1234567890) and running:
ssh root@192.168.8.1
the ssh password is
oelinux123
-
RE: Can not connect to VOXL2
@rogerli What does the device enumerate as when you list usb devices with
lsusb
? -
RE: Complete reset of M0018 flight core
@Κωνσταντίνος-Κλέων-Χριστόπουλος No hardware reset but you can easily load the latest PX4 release through QGroundControl after downloading voxl_SDK_1.2.0.tar.gz from our downloads page (downloads.modalai.com) and finding the FCv1 .px4 file in the flight-core directory
-
RE: VOXL2 flash error
@Nathan-Sullivan-0 Interesting... can you try forcing the board into fastboot using the button https://docs.modalai.com/voxl2-voxl2-mini-system-image/#force-voxl-2-into-fastboot
then flashing and see if that changes anything? (make sure to select M0054-1 when prompted as your board has a QRB5165)
-
RE: VOXL2 starling bootable images
@Darshit-Desai You can generate a .deb file for any apt-installable package by doing the following onboard:
sudo apt download $PACKAGE_NAME
Keep in mind that this won't automatically download/install any other dependencies that would automatically get installed if you were to run a normal
apt install
command so you may need toapt download
those packages as well and install them beforehand. -
RE: VOXL2 flash error
@Hyunsoo-Kim-0 Can you post a picture of your hardware setup so we can confirm you're flashing the correct image?
-
RE: Starling not arming. Un reliable product!!?
@david-devassy I'd recommend sending in an RMA: https://www.modalai.com/pages/rma and we'll get things sorted
-
RE: VOXL2 RTSP decoding fails
@Aaky The source of truth for SDK 1.2 packages can be found here: http://voxl-packages.modalai.com/dists/qrb5165/sdk-1.2/binary-arm64/
-
RE: How to do SLAM and VOXL-Mapper flying with Starling Drone ?
@david-devassy That's not something I'm in control of but you can look into https://www.modalai.com/pages/rma
We do test all sensors and flight test each drone before shipping so the failure would've occurred sometime after
-
RE: PX4 Firmware flashing - Flight Core V2
@Jetson-Nano Unfortunately not given the state of the board
-
RE: PX4 Firmware flashing - Flight Core V2
@Jetson-Nano Sounds like there's either a hardware issue with your PC or an issue with the board, I'd recommend submitting an RMA: https://www.modalai.com/pages/rma
-
RE: voxl-px4 service pipeline uORB failure
@swickliff If you believe that the file system is corrupted you can reflash the latest SDK release using the
-w
arg,./install.sh -w
This will wipe all partitions, ensuring your board is in a factory state