DMIO Update issues

[PLCwannabe]

   I finally got around to updating my DMIO-M-D modules to the latest firmware (4.2.134) to clear up slaves offline issue. But now I'm getting multiple channel failure alarms on multiple BX-08NTC temp modules. I had to disable all unused channels and disable the burnout mode on all modules to clear this up. Is this by design or do i have to update the individual temp modules as well?
   I'm also getting a self-test failed bit on one channel  going on periodically, which causes a module error. What can cause this error?
       Update. When I had done all the firmware updates, I noticed that a couple of the BX-08NTC modules were showing degrees fahrenheit, even though on module configuration they are all set to celcius.(6 modules total, all on DMIO-M-D modules.). I had to set the modules to fahrenheit, save, set them back to celcius and that cleared it up. So now a couple days ago the barn manager calls and tells me some of the rooms are showing fahrenheit readings causing all the hi temp alarms to trigger. I had to do the same procedure, set modules to fahrenheit, and then set them back to celcius to clear it up. Is this a known issue with latest version firmware, and is there an earlier version that wouldn't have this issue, but also doesn't have the slaves offline issue?

[PLCwannabe]

.

[BobO]

   I finally got around to updating my DMIO-M-D modules to the latest firmware (4.2.134) to clear up slaves offline issue. But now I'm getting multiple channel failure alarms on multiple BX-08NTC temp modules. I had to disable all unused channels and disable the burnout mode on all modules to clear this up. Is this by design or do i have to update the individual temp modules as well?
   I'm also getting a self-test failed bit on one channel  going on periodically, which causes a module error. What can cause this error?
       Update. When I had done all the firmware updates, I noticed that a couple of the BX-08NTC modules were showing degrees fahrenheit, even though on module configuration they are all set to celcius.(6 modules total, all on DMIO-M-D modules.). I had to set the modules to fahrenheit, save, set them back to celcius and that cleared it up. So now a couple days ago the barn manager calls and tells me some of the rooms are showing fahrenheit readings causing all the hi temp alarms to trigger. I had to do the same procedure, set modules to fahrenheit, and then set them back to celcius to clear it up. Is this a known issue with latest version firmware, and is there an earlier version that wouldn't have this issue, but also doesn't have the slaves offline issue?

Not aware of an issue with the config on DMIO, but we'll investigate.

[MikeS]

Can you check the hardware version of the 08NTC (what I'm interested in is the last letter of the S/N). There was a change from B to B1 that specifically dealt with the burnout bits and the burnout mode being wrongly reported.

If your module is Rev B, it will need to be updated at the factory - it's not field upgradable. They will be update it for free; let me know and i'll send you their contact info.

As for the DegC / DegF problem you're seeing, we don't see that happening here. One possibility revolves around the module's required external 24VDC when the PLC & DMIO are powered up. If for some reason the external 24VDC is not ready when the CPU goes to program the DMIO (and in turn the NTC module), you get default values for these configuration fields. Did the barn manager notice these Deg F after the system was power-cycled?

[PLCwannabe]

The last letter of serial numbers is a B. But I can;t have those modules removed for any lenght of time due to safety issues.
I'm not too worried about the burnout bits, I just disabled those, I'll know it's burned out when I get a temp alarm. I'm more worried about the celcius /fahrenheit thing. The whole setup is on the same 24vdc power supply, connected to a battery backup,so I know the 24vdc is not an issue.
  I had the barn manager cycle the 24vdc after he reported this issue, and that did not clear it up. What I find confusing is that the module configuration still showed Celcius selected but was outputting Fahrenheit values.

  While troubleshooting the last couple days, I noticed that any computer on this same local network can actually access a configuration screen for these DMIOs and their modules just by browsing to that IP address. Is there some way to lock that so the modules can only be configured with Designer software?

[Bolt]

While troubleshooting the last couple days, I noticed that any computer on this same local network can actually access a configuration screen for these DMIOs and their modules just by browsing to that IP address. Is there some way to lock that so the modules can only be configured with Designer software?

In the System Configuration, there is a choice to Enable HTTP Server, change HTTP Settings... and Enable Server Whitelist, change Whitelist Settings...  This will disable what you are asking.  However, this is all read only, so configurations are not being changed from these web accessed pages.

[Controls Guy]

I'm more worried about the celcius /fahrenheit thing.

If the module has some propensity to disregard the scale setting and report in Fahrenheit, why not just work around it and scale from F to C in the PLC?

Or put 4-20 transmitters on all the thermistors and just use generic analog modules, and again, scale in the PLC.

[PLCwannabe]

While troubleshooting the last couple days, I noticed that any computer on this same local network can actually access a configuration screen for these DMIOs and their modules just by browsing to that IP address. Is there some way to lock that so the modules can only be configured with Designer software?

In the System Configuration, there is a choice to Enable HTTP Server, change HTTP Settings... and Enable Server Whitelist, change Whitelist Settings...  This will disable what you are asking.  However, this is all read only, so configurations are not being changed from these web accessed pages.

Are you very sure that these screens are read-only? I can actually change all config values for individual modules on that screen, not sure how it would be written to the modules though.
 I have confirmed that someone browsed to these config screens while attempting to login to a different device. I think that is what caused the issue. But that still doesn't explain why the modules didn't show the config changes.

[PLCwannabe]

 This same issue happened again today, temp module starts reporting in Fahrenheit causing a bunch of hi temp alarms. (save and download fixes it).
  What needs changing, the temp module or the DMIO?

[PLCwannabe]

As for the DegC / DegF problem you're seeing, we don't see that happening here. One possibility revolves around the module's required external 24VDC when the PLC & DMIO are powered up. If for some reason the external 24VDC is not ready when the CPU goes to program the DMIO (and in turn the NTC module), you get default values for these configuration fields. Did the barn manager notice these Deg F after the system was power-cycled?
[/quote]


  I had this happen again today where 5 out of 6 temp modules switched to fahrenheit after a power cycle.
   I had moved this plc setup (with 2 DMIOs) to its own ethernet network with nothing else connected except those three devices.I thought that solved the issue till the power cycle triggered it again today.
   If the 24vdc was the issue, wouldn't some of the other config values be changed back to default as well? (They're not) Also can someone confirm if Fahrenheit is the default for temp modules? I would change everything to Fahrenheit and just scale to Celcius within the program.

 I hate having to keep harping about this issue, but it has the potential to cost me a huge customer.

[Controls Guy]

Why not just *preemptively* leave the modules in F and scale?  I don't see any advantage vs. trying to troubleshoot it.

[BobO]

  I had this happen again today where 5 out of 6 temp modules switched to fahrenheit after a power cycle.
   I had moved this plc setup (with 2 DMIOs) to its own ethernet network with nothing else connected except those three devices.I thought that solved the issue till the power cycle triggered it again today.
   If the 24vdc was the issue, wouldn't some of the other config values be changed back to default as well? (They're not) Also can someone confirm if Fahrenheit is the default for temp modules? I would change everything to Fahrenheit and just scale to Celcius within the program.

 I hate having to keep harping about this issue, but it has the potential to cost me a huge customer.

There were early bugs with some of the FACTS built analog modules not initializing with the correct settings. I thought it was primarily due to the module's external power supply not being in sync with the PLC's, but there may have been more to it. I also thought those problems were fixed long ago.