Issue with Microhard IP configuration.
-
@rogerli There are a couple of options that come to mind. One it to use the VOXL2 as a router such that you can directly pass messages between the TRIP2 and QGC. That would require some messing with routing tables and such on VOXL2. If you are comfortable with networking then maybe this is the cleanest route to go. Otherwise you can just write a custom relay node that runs on VOXL2 and shuttles the messages between the two endpoints.
@Eric-Katzfey Thank you for your suggestion, I will try it out. However, I am not familiar with networking , so I plan to use a custom relay node. Is it possible to achieve this goal using MAVProxy?
-
@Eric-Katzfey Thank you for your suggestion, I will try it out. However, I am not familiar with networking , so I plan to use a custom relay node. Is it possible to achieve this goal using MAVProxy?
@rogerli I don't have any experience with mavproxy but seems like it's possible. Worth a try at least.
-
@rogerli I don't have any experience with mavproxy but seems like it's possible. Worth a try at least.
@Eric-Katzfey I can use Mavproxy for message forwarding, but when I connect trip2 to the MH add-on board via Ethernet, the IP of MH keeps changing. How can I make the IP of MH fixed? (The IP of MH is fixed when not connected to trip2 via Ethernet.)
-
@Eric-Katzfey I can use Mavproxy for message forwarding, but when I connect trip2 to the MH add-on board via Ethernet, the IP of MH keeps changing. How can I make the IP of MH fixed? (The IP of MH is fixed when not connected to trip2 via Ethernet.)
-
@rogerli Hmm okay I wonder if voxl-modem is getting confused. If you disable the voxl-modem service with
systemctl disable voxl-modemand runvoxl-modem-startmanually 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 Hmm okay I wonder if voxl-modem is getting confused. If you disable the voxl-modem service with
systemctl disable voxl-modemand runvoxl-modem-startmanually 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.@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 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.)
-
@rogerli Is the serial python3 library installed? If you run
python3from the command line and runimport serialdo you get the same error? It might need to be installed withpip3@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 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.
-
-
@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
@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.
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