@Eric-Katzfey
the versions of px4 are different...
I am git clone from https://gitlab.com/voxl-public/voxl-sdk/services/voxl-px4
in which there is only one parameter in https://github.com/modalai/px4-firmware/tree/0a47ec5d8650f4e97f1eb929405df5dcdb91989f/src/drivers/distance_sensor/lightware_laser_i2c
Anyway, qshell lightware_laser_i2c start is not working with I2C port on VOXL2 J19 - QUP3
@Eric-Katzfey
Understood. I just figured out address and bus. I am sorry for disturbing you for the basic concept.
Now, I am trying to run it with SENS_EN_SF1XX=6, the command in px4-start is just qshell lightware_laser_i2c start.
By the way, I am wondering where the bus info is described in the driver cpp file. Should I change the code? Because lightware_laser_i2c accepts only R as an option..
@Eric-Katzfey
Eric, this is not working...
Please refer to the driver for i2c....
https://github.com/modalai/px4-firmware/blob/main/src/drivers/distance_sensor/lightware_laser_i2c/lightware_laser_i2c.cpp
Default i2c address is defined 0x66 (102) in this code.
I am wondering what is the i2c address of the VOXL2 J19 - QUP3 port.
I am not familiar with the above cpp driver code... could you please have a look the code and teach me how to enable the i2c connection for the lightware rangefinder?
Thank you in advance....
Hi, Eric.
I tried
qshell lightware_laser_i2c start -a 0x66 # I2C address 102
it did not work..
So are you meaning
qshell lightware_laser_serial start -b 4
or
qshell lightware_laser_i2c start -b 4
?
Hi,
I connected Lightware LW20/C on one of the I2C port on VOXL2 J19.
It is QUP3, and the pins I used are
7 I2C3 SDA 3P3V slpi_proc, SSC_QUP3
8 I2C3 SCL 3P3V slpi_proc, SSC_QUP3
and power & ground.
I also installed a customized voxl-px4 which will start lightware_laser_i2c with the I2C address 0x66.
On VOXL2, I edited voxl-px4.conf file by adding DISTANCE_SENSOR=LIGHTWARE_SF000.
However, I cannot see any parameter regarding rangefinder... like SENS_EN_SF1XX.
I have done using LW20/C with UART connection successfully, but I2C does not work..
Can anyone give me any advise to use it via I2C?
@Eric-Katzfey
I see. If VOXL2 is connected to a local laptop that has internet access, but VOXL2 itself does not have internet access, will VOXL2 update its date and time through the laptop?
Hi,
I am wondering when the time sync function is updated on VOXL2?
When I run date on VOXL2, it shows the old time when the SDK developed.
But this time, after upgrading the SDK, it is showing the current time!
How is it working?
Thank you.
@Eric-Katzfey @Vinny @tom
This is totally the power cable problem...
Is there any future plan to make it stable?
It is horrible to imagine the drone crashing due to a reboot issue caused by the power cable.....
I will have a look.
This is very randomly happening...
I changed power source (battery, wall power), but it is working well now...
Is there any way to check GPU usage on VOXL2?
I have the rebooting issue with a VOXL2 flight deck with Microhard radio.
I have tested with 5G board (M0090-3-01) as well. I connected a USB3 ethernet adapter on the 5G board to communicate with my laptop through ethernet cable. The same issue happened.
When I directly powered the system by using a power supply (5V) without a power module, it did not show any rebooting issue....
I am still figuring out, so please let me know what I need to try...