Just written image, working ok

But for some, it’s more important that it doesn’t work the right way,

That’s just dandy. Be up front about it, and the people who don’t like it can simply not use it.

For some, any way is better than no way at all…

;-)

The rest? What Steve wrote. +1

I had a nosey at the EtherUSB source last night and it doesn’t appear to raise an event when the cable state changes. Hopefully the “generic” Ethernet code does; I didn’t get that far.

Once we’ve found a way to detect the cable state change cleanly, it seems to be a simple matter of calling *DHCPExecute, so at least that part looks easy enough :)

Once we’ve found a way to detect the cable state change cleanly, it seems to be a simple matter of calling *DHCPExecute,

Or at least the code for that that instruction.

Perhaps if you made the source available so that other people1 could see the effect and make an alteration to the RO (open source) build then maybe something would work.

In order to see the SWI (DCI4) documentation I had to sign an NDA, so I can’t just release source code as that would reveal how the SWI works to people who haven’t signed an NDA!

it doesn’t appear to raise an event when the cable state changes

You’re right, it doesn’t. Connection state is available from a SWI though, so it needs polling repeatedly.

it seems to be a simple matter of calling *DHCPExecute, so at least that part looks easy enough

You’d think so, wouldn’t you! I thought so too, initially!

You’re right, it doesn’t. Connection state is available from a SWI though, so it needs polling repeatedly.

Well, that’s less than ideal!

You’d think so, wouldn’t you! I thought so too, initially!

Eep.

You’re right, it doesn’t. Connection state is available from a SWI though, so it needs polling repeatedly.

It doesn’t, but if I’m reading correctly then it should. The documentation states that Service_InternetStatus 2 is issued “when an interface goes up or down”. However, this doesn’t seem to happen. I’ve made a quick and dirty module that just looks at everything in Service_InternetStatus but I’m not getting the results that I’d expect.

1. I disconnect the Ethernet cable and reboot the machine.
2. I start my module.
3. At this point *EJInfo is reporting that the interface is down.
4. I connect the cable. No Service_InternetStatus calls are issued.
5. *EJInfo now reports that the interface is up. Still no Service_InternetStatus calls.
6. I run *DHCPExecute ej0
7. I start seeing DHCP-related Service_InternetStatus calls.

At no point do I see Service_InternetStatus 2. Am I interpreting the documentation incorrectly or does it simply not match reality?