Hi Guys,
I am trying to connect an IFM IO-Link Master AL1304 to an edge IO using IOT Port for the master and the LAN port for the Edge IO. The problem is that the edge IO want communicate with the master and i don’t know why. Knowing that i tested the same configuration with an Edge MC and the master is correctly communicating with it. I don’t know if there is any difference between the Edge IO and the Edge MC on the LAN port but any one can help me with this please ?
thanks,
Hi there,
Edge MC often works out of the box because it can provide a device network with DHCP/NAT. Edge IO has a single Ethernet interface and does not provide DHCP, so a device connected directly may not get an IP.
Two ways to get the IFM AL1304 talking to Edge IO:
Static IPs
Set both devices to static addresses in the same subnet (for example 192.168.x.x/24).
Leave the gateway blank if it is a direct link.
Point the Tulip machine driver on Edge IO to the AL1304’s IP using the correct protocol.
Provide DHCP
Place a small router or a network with DHCP between Edge IO and the AL1304.
Confirm both receive addresses in the same subnet.
Configure the Tulip driver to the master’s assigned IP.
To help narrow it down, please confirm:
DHCP or static addressing?
Private range class only (10.x, 172.16–31.x, or 192.168.x)
Subnet size (for example /24) and that both devices are on the same subnet
Protocol you plan to use (EtherNet/IP, Modbus TCP, OPC UA, HTTP/MQTT) and required ports
Link lights on both sides, and whether you can ping or open the AL1304 web UI from a laptop on that subnet
Firmware version of the AL1304 and the Edge IO driver you selected
If you prefer to share configs privately, feel free to let me know and I can open a support ticket for you.
Best,
Nicolo
Hi @nicolo.lagravinese ,
Thank you for your answer.
In fact, here is the element you should know about what i want to do :
For the first configuration you mentioned, the edge don’t let me to fix the adress on the range 10.0.X.X and also don’t let me to keep the router blank.
is it normal ?
thanks,
Hi @nicolo.lagravinese ,
I tried also to provide DHCP via a small router but i didn’t know if i have to let the edge on downstream or upstream. Because, on donwstream, i can’t change the gateway value and on upstream i have to choose a static ip for the router and i can’t chose the 10.0.5.X range.
Can you tell me how to do it with a router please?
thank you,
Hi @FahdERM,
Thanks for the extra context. Here are a few things to try:
Ports
The Edge IO has two bridged Ethernet ports (unlike the IO Gateway which only has one), so either port can be used. The issue you’re seeing is more likely addressing or link negotiation.
Static IPs
Try using a 192.168.1.x/24 range instead of 10.0.5.x, since Edge IO can be restrictive with certain ranges. Example:
Edge IO = 192.168.1.10
AL1304 = 192.168.1.11
Mask = 255.255.255.0
If it requires a gateway, set it to the Edge IO’s own IP.
Router with DHCP
If using a router, connect both devices to the LAN side. The router will hand out IPs in the same subnet, and you can point Node-RED to the AL1304’s address.
Link Lights
Blinking-then-off link lights suggest a negotiation issue. Try:
A different Ethernet cable
Adding a small unmanaged switch between the devices
Next Step
Test with the 192.168.1.x static setup and see if the link stays steady. If it still doesn’t come up, let me know and we can dig deeper.
Best,
Nicolo
Hi there,
Just sharing our experience with the IFM Master IO-Link Modules.
We just received our Tulip Edge IO and Edge MC devices recently. However, we never considered hooking up the IFM Master to the Tulip Edge devices. Instead we follow the Unified Namespace approach and therefore we publish the IFM values to an MQTT broker which acts as a single source of truth. The MQTT broker can then be configured as a data source in Tulip and you are done.
I feel like this would be much easier.