Issue with Microhard IP configuration.

[tom]

@rogerli What is the network interface that isn't using a fixed IP as you expect? eth0? usb0?

[rogerli]

@tom It's usb0, eth0 is always 169.254.4.1

[tom]

@rogerli Hmm okay I wonder if voxl-modem is getting confused. If you disable the voxl-modem service with systemctl disable voxl-modem and run voxl-modem-start manually from the command line it might give you a clue of what interface it's targeting. It's possible with this custom setup that some tweaking to the startup script needs to be made, whether it's a sleep to wait until the device fully boots or a change in network interface name somewhere.

[rogerli]

@tom I disabled the voxl-modem service and manually ran voxl-modem-start from the command line, but I didn't see any hints about the interface, so I'll try modifying the script directly.

Additionally, I'm currently writing a script to automatically execute mavproxy.py, but during the automatic execution, I encounter the issue "No module named 'xxx'". Even though I've included the Python path used by mavproxy.py in the script, it doesn't resolve the issue. Is there a way to fix this problem? (I can run mavproxy.py normally by manually entering commands.)

[tom]

@rogerli Is the serial python3 library installed? If you run python3 from the command line and run import serial do you get the same error? It might need to be installed with pip3

[rogerli]

@tom I'll need to confirm tomorrow, but I believe I have it installed because I can manually run mavproxy.py from the command line. However, when executing it automatically with a script in the system, I encounter the aforementioned issue.

[tom]

@rogerli When you run /usr/bin/mavproxy-start.sh from the command line does it work?

[rogerli]

@tom Yes, it can run normally

[tom]

@rogerli Hmm that's interesting, I'm unsure why it would have issues seeing the serial library when running as a service but not when run manually.

I've never used a python venv or anaconda before on voxl2 so I'm guessing that's where the issue lies

[rogerli]

@tom I had the same idea, so I directly installed Mavproxy and related packages on VOXL2, and successfully resolved the issue with the serial library. However, when running the service, I still couldn't import the Python files related to Mavproxy. Even adding the paths of those Python files to the environment variables didn't solve the problem.