HITL with voxl 2
-
Hi @Tamas-Pal-0 - looks like you are correct in that the voxl-px4-hitl has not been pulled into voxl-master. I would recommend for now switching over to the
voxl-devbranch and running with the steps through there. Once it has been pulled into voxl-master, then you can recompile, reflash, and run through it on that branch. Other options as well is you can copy the filevoxl-px4-hitlfrom thevoxl-devbranch into your current workingvoxl-master, recompile, and reflash the voxl2 with the newer firmware containing the correct executable. -
Unable to run this command
echo 1 | sudo tee /sys/bus/usb-serial/devices/ttyUSB0/latency_timer
In the terminal it is showing permission denied after running the command
tamas@tamas:~$ echo 1 | sudo tee /sys/bus/usb-serial/devices/ttyUSB0/latency_timer
tee: /sys/bus/usb-serial/devices/ttyUSB0/latency_timer: Permission denied
1
How to fix the problem? -
@Tamas-Pal-0 said in HITL with voxl 2:
0
This seems like a permissions issue on your end and that your user doesnt have super user permissions.
-
tamas@tamas:~$ echo 1 | sudo tee /sys/bus/usb-serial/devices/ttyUSB0/latency_timer tee: /sys/bus/usb-serial/devices/ttyUSB0/latency_timer: Permission denied 1 tamas@tamas:~$ ls /sys/bus/usb-serial/devices/ttyUSB0/latency_timer ls: cannot access '/sys/bus/usb-serial/devices/ttyUSB0/latency_timer': No such file or directoryHow to fix it ?
-
@Tamas-Pal-0 What do you get with
ls /dev/ttyUSB*? -
@Eric-Katzfey
I got thistamas@tamas:~$ ls /dev/ttyUSB* /dev/ttyUSB0I am unable to modify anything inside /sys/bus/usb-serial/devices/ttyUSB0 with root user also. How to fix it?
-
@Tamas-Pal-0 I'm not sure. This works in our development environment so something must be different in your environment. What version of Linux are you using? What cable are you using?
-
@Eric-Katzfey
The issue is fixed. It was a hardware issue. I changed the ftdi cable and the issue was solved. The previous FTDI cable was not allowing me to change anything in /sys/bus/usb-serial/devices/ttyUSB0 directory. The file latency_timer was also not there. However with the other cable, there is no such issue. Thank you for your valuable input. -
For 3.3v J18 jst port which port of ftdi cable should be used, CTS# or RTS# ?
-
@Tamas-Pal-0 For UART it is just GND, TX, and RX
-
@Eric-Katzfey you mean we only have to connect 3 pins in j18 port ?
-
@Tamas-Pal-0 Yes, the fourth pin is power and we don't want that one.
-
Is there any way to verify that FTDI cable is connected properly with J18 port ?
-
@Tamas-Pal-0 The easiest way would be to recompile the modalai_dsp PX4 driver to add more debug messages. But if you aren't comfortable with that then we'll need to come up with something else.
-
How to do that? Is there any other way to this ?
-
@Tamas-Pal-0 The simulator will be sending heartbeat messages out over the serial cable. You can use the
screenprogram to see if anything is coming from voxl 2 in the serial cable. -
@Eric-Katzfey How to use screen program in this case ?
-
@Tamas-Pal-0
screenis just a standard Linux program. There are many ways to check the output of the serial port. To start, you could always just docat /dev/ttyUSB0and see if anything is coming out. This post shows how to get a hex dump: https://superuser.com/questions/1402386/view-serial-device-output-in-console-in-hex -
The problem is solved. The problem was with ftdi cable. Thank you for your valuable inputs
-
@Tamas-Pal-0 Excellent! How were you able to determine that it was the cable?
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login