DHCP support for @IntEthernet

[Andrew S]

Is there any possibility that the inboard Ethernet port might support DHCP at some point? I'd missed this vital piece of information and although I know I can work around it using a POM I could really use DHCP support on the built-in NIC.

Andrew,

[BobO]

Is there any possibility that the inboard Ethernet port might support DHCP at some point? I'd missed this vital piece of information and although I know I can work around it using a POM I could really use DHCP support on the built-in NIC.

Andrew,

DHCP is not well suited to a control platform; having addresses change at will is a potentially a very bad thing. It makes sense for your app, since the PLC is controlling the flow of information, but for most users it does not. The problem is that it encourages people to do things that aren't going to work well for them (or worse), and causes more trouble than benefit. I guess we could look at adding it, but we have a lot on our plate right now and I'n not entirely sure how we can do it without causing more harm than good.

[Andrew S]

Perhaps you should add an "idiot Mode" flag that enables stuff like this ;-)

[BobO]

Perhaps you should add an "idiot Mode" flag that enables stuff like this ;-)

Idiots do factor into the discussion, but pretty sure you aren't one.

Of late, a major consideration for what we do or don't is trying to guess the impact to ADC's market at large. Our experience is that when you build a product capable enough to satisfy the experts, you've built one so complex that only experts will use it. Unfortunately there is a whole lot more not experts than experts.

[Andrew S]

Absolutely. I've seen devices (not PLCs) that have an 'advanced' mode that removes certain restrictions for features that would otherwise cause problems. Perhaps something to think about for the future. I do agree though that the KISS model is advantageous most of the time.

[Andrew S]

I've been noodling on this and I'd really like to be able to convince you to add DHCP support for @IntEthernet. Here's my pitch - perhaps you could add a DEVWRITE option for it. That way it's not in the regular config, but for tech-heads who are willing to live with the consequences there's an option available.

Or I could buy you beer ;-) 

[BobO]

I've been noodling on this and I'd really like to be able to convince you to add DHCP support for @IntEthernet. Here's my pitch - perhaps you could add a DEVWRITE option for it. That way it's not in the regular config, but for tech-heads who are willing to live with the consequences there's an option available.

Or I could buy you beer ;-) 

I'm thinking about it. I wasn't in support, but considering it from the perspective of an IIoT edge node that just needs the Ethernet port to hit an MQTT server in the cloud, I see the advantage. We are also kicking around Sparkplug B, and for a monitoring node in a SCADA system I can see a similar advantage.

Still debating the implementation. As easy answer would be an instruction that would put the internal port under DHCP control. Dropping the enable would free the lease and return to the flash config. That has the advantage of requiring either a fixed IP or another port for programming, and allowing the use of DHCP for the cases it actually makes sense for. I think that resolves much of the support headache.

[Andrew S]

I could certainly get behind that implementation Bob. Thanks for looking at it again.

[Andrew S]

I've been noodling on this and I'd really like to be able to convince you to add DHCP support for @IntEthernet. Here's my pitch - perhaps you could add a DEVWRITE option for it. That way it's not in the regular config, but for tech-heads who are willing to live with the consequences there's an option available.

Or I could buy you beer ;-) 

I'm thinking about it. I wasn't in support, but considering it from the perspective of an IIoT edge node that just needs the Ethernet port to hit an MQTT server in the cloud, I see the advantage. We are also kicking around Sparkplug B, and for a monitoring node in a SCADA system I can see a similar advantage.

Still debating the implementation. As easy answer would be an instruction that would put the internal port under DHCP control. Dropping the enable would free the lease and return to the flash config. That has the advantage of requiring either a fixed IP or another port for programming, and allowing the use of DHCP for the cases it actually makes sense for. I think that resolves much of the support headache.

Hi Bob. Did this functionality ever get implemented? My IoT project is still on hold until DHCP on the on-board Ethernet port is in place.

Thanks, Andrew.

[BobO]

Hi Bob. Did this functionality ever get implemented? My IoT project is still on hold until DHCP on the on-board Ethernet port is in place.

Thanks, Andrew.

It has not, but we'd still like to. We are working on a client-centric Ethernet POM, and I'd definitely like it to be DHCP capable.

[Andrew S]

Thanks Bob. I'd love for @IntEthernet to be DHCP-capable as opposed to (or in addition to) the POM though, if at all possible.

I'll check back at a later date. My project is still 'alive' but it obviously won't be for ever, so fingers crossed it's not too long until there's a solution.

Hope you're keeping well in these strange times!
Andrew.