1) Does this issue occur with the D2-260 and H2-ERM100?
The issue is in the EBC100 itself, and is a bug...in a workaround...for an unintended hardware change in an analog module...due to a part going obsolete. Yeah.
I would assume it could show up in anything driving an EBC100, although I'm thinking it only showed up when the poll rates were very slow (like 2Hz, slow).
2) Which firmware versions of the Do-more have a problem without this?
Not sure I follow. It isn't a Do-more issue.
3) It sure would be nice if DmD would download the firmware and notify us that it did and to use NetEdit3. I'll admit to going far astray trying to figure out what I had to do. (NetEdit3 is an iffy thing to use as it is, due to sometimes crashing and other times refusing to see what is there without having all the right combinations selected. Even single device won't work with the wrong protocol selected. Not all of us are networking wizards.
Some crashes have been fixed in the latest version...which might have actually been published...or not. I suspect there are still some, specifically related to the ever changing interface detection landscape. Microsoft...:rolls eyes:.
The only protocol that matters in everything since XP is IP.
Selecting the interface is required due to Microsoft making IP stack changes. Specifically, they stopped sending broadcasts out of every NIC, and instead grab some random one, unless you bind the connection to a specific one...which you do by picking from the list. I'm sure that if we weren't eyeballs deep in developing products, we could spend time on NetEdit, but we are.
4) Well, while I am here. It would also be nice if DmD warned us another Master was already using the EBC when we try to slave it again to a different Master. I guess all the flashing comms errors for the module was a give-away, but I couldn't lay eyes on either PLC to see the blinky red ERR lights on both.
On the one hand, yeah, we could probably come up with some improvements (but remember the eyeballs thing). On the other hand, a network environment that has multiple masters and slaves all visible to each each seems bad...right?