In this case, a static IP is not needed for the ethernet port since I am only transmitting data to the DMX interface box. The ethernet port is connected to a DMX interface box. I've also experienced this issue when I use a Pi to control an LED setup via the Artnet protocol. However, this doesn't solve my issue when I need to update the Pi or download a file. I know I could connect to each if I connect my computer to the desktop switch, then use VNC over my ethernet port. I've tried to follow the example set here: I would like to be able to access each Pi over wifi via VNC but seem to be unable to get the wifi to work on the Pi when an ethernet cable in connected to the port. I can get each Pi to connect to a wifi network but I cannot load any pages or download any updates via the apt-get update commands in terminal. The problem comes when I need to troubleshoot or adjust the code running on each of the Pi's. I can setup a static IP for each of the Pi's ethernet ports, connect them all via a desktop switch and have them all talk to each other without issues. I'm using OSC protocol for communication between them which needs each to have a static IP address. What I'm trying to do is connect 4 Raspberry Pis as nodes/slaves to a single Pi which will act as the server/master. I'm having issues with using a static IP for a Raspberry Pi 3.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |