Thanks to you that helped out a gray haired old man. :-) This fixed the problem. Now to go grovel to a module supplier. :-( Robert Balmer Senior Process Controller Climax Molybdenum Fort Madison Ia. 319-463-2206 CCST -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of dave.caldwell@xxxxxxxxxxxxxx Sent: Thursday, May 09, 2013 10:07 AM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] Interesting Happenings with FBM 242 modules I think Jerry nailed it. It's been awhile, but I now recall having to do the same thing. Apparently the EEPROM rev was not compatible with the extended fieldbus. Regards, Dave -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Gordon, Jerry Sent: Thursday, May 09, 2013 11:00 AM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] Interesting Happenings with FBM 242 modules I have had that happen. I had to put the FBM242 in the first baseplate of fieldbus 1 and do an E prom update and then it will work in the other baseplates. Jerry Gordon Public Service Co of NM ________________________________________ From: foxboro-bounce@xxxxxxxxxxxxx [foxboro-bounce@xxxxxxxxxxxxx] on behalf of Balmer, Robert D. [Robert_Balmer@xxxxxxx] Sent: Thursday, May 09, 2013 8:40 AM To: Foxboro DCS Mail List Subject: [foxboro] Interesting Happenings with FBM 242 modules Has anyone lived through this kind of happening Testing an upgrade with FCP 270 and FEM100's. We can get all modules to work on any extended fieldbus except the FBM 242's. The 242's will only work on Extended fieldbus 1. You put the 242 on a backplate in any other extended fieldbus they will not go online. Checked and rechecked everything we could think of. Any one seen this and got a fix? Thanks Robert Balmer Senior Process Controller Climax Molybdenum Fort Madison Ia. 319-463-2206 CCST _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave