Just received the Wireless Ethernet Modem and a Machine Uptime Monitor so that I can trial them before I recommend a purchase for one of my customers.
I am unable to connect to the Wireless Ethernet Modem via any method. It does not broadcast a SSID, it does not have an IP address that is pingable (via Angry IP Scanner), and nothing happens when connected directly to a PC. I have reviewed the online documentation and followed the various connections method with no luck. I can see some lights turn on when I plug in the device but when I plug in an ethernet cable to a local unmanaged switch, the port lights do not indicate a valid connection (orange instead of green).
This has put your devices at the bottom of the list for my customer unless I receive fast support that can resolve this issue.
Thank you for the reply. But let me get this straight…these devices aren’t able to connect to out of the box? I have to get more hardware/software 'n such? The website documentation does NOT mention the need for any of what you listed. I have a dumb net gear switch and per the documentation the device should be able to communicate via a simple connection, even directly to a PC or via WiFi!
This isn’t a viable solution, unless anyone else has a suggestion. The price isn’t that much cheaper compared to Keyence or SICK, which are much easier to config so far and don’t require node-red for protocols like MQTT, Modbus, or OPC UA.
I do like the concept of using node-red (after a bit of thought), since I’m using Inductive Automation Ignition as the SCADA. But still…almost any device I’ve trialed for any customer I have at least been able to connect to it straight out of the box (even random Chinese modbus devices).
Otherwise you can use the static IP address jumper on the Ethernet module as outlined in this guide: NCD Gen3 Ethernet Module User Guide - NCD.io under Force Static IP for Configuration.
The Ethernet Modem doesn’t have WiFi capabilities. The Wireless part of the Wireless Ethernet Modem refers to the 868/900/2400 mhz wireless protocol used to communicate with the receiver.
If connected directly to your PC you will need to set a static IP address within the subnet of the network your PC is using for the attached network interface card. i.e. if you Ethernet port on your PC has an IP/subnet of 172.0.0.27/24 you’ll want to set a static IP address of something like 172.0.0.28 with a subnet of 255.255.255.0.
Once you know the IP address you can open a TCP socket to the modem and receive the sensor data. It is recommended to use Node-Red to receive the sensor data as it can parse the raw byte information that you’ll receive over the socket into JSON objects for easier manipulation and use.
Much more understandable response, thank you Jacob! But I’ve already decided to go a different direction. Technically the device should come with a static IP address so that I can connect to it even if a router isn’t involved (at least that is how most other devices work) - yes, I know how to connect to a device directly to my PC, it didn’t work and a device should not come with an IP address of x.x.0.1 (per the online documentation!) as that is typically the gateway address - like an actual router. And NCD needs to update their documentation - or provide better navigation, I’m not in the business of hunting down configs and troubleshooting documents or even having to jump through hoops just to connect a simple device.
This isn’t even to mention the screws on the Wireless Modem were so tight that I couldn’t get them to come loose without risking rounding the screw heads - so yeah…not worth my time. Maybe my experience is a one-off but I don’t have the time to mess around with an unusable solution.
If NCD makes the config easier in the future then I’ll reconsider but there are better techs out there right now. Thanks for the more detailed response - I might consider NCD for more home/hobbyist stuff but definitely not for my customers.