The Gen3 devices do offer the ability to divert their entire network traffic to Ethernet but then you will not be able to use WiFi or Cellular anymore.
If this would be acceptable you can have that out the box.
https://docs.particle.io/reference/device-os/firmware/boron/#ethernet
For more info around that topic I'd have to defer to @rickkas7 who has previously answered similar questions that can be found in this forum too.
e.g. here
There will be a couple problems with this setup.
One is that the the Ethernet FeatherWing only supports DHCP addressing. It does not support static IP addressing, so it won’t work on an isolated network that doesn’t have DHCP.
The other problem is that as soon as the Ethernet has link and an IP address, Device OS will attempt to use it for the Internet/cloud connection, even if the network is isolated and can’t connect to the Internet. It will never fall back to cellular once the Ethernet inte…
It’s hard to say for sure which would be easier. There’s also a third option, which is probably the one I would do:
Use the Particle Ethernet FeatherWing hardware, but not the Device OS support.
Leave the Ethernet detection feature flag off so Device OS won’t look for the port.
The Ethernet FeatherWing is just a Wiznet W5500. It has a simple AT interface with a socket implementation for TCP and UDP. There are some libraries available for it, I would just use one of those.
Since you have direc…
1 Like