Hug

Sorry for the late response, Here is some information from my Rockwell Rep. Unlike the 1756-ENBT, the 1768-ENBT will not function without the controller. This ENBT may time-out on power-up if it doesn't see the controller in time. Sometimes the boot-up of the controller takes longer than the boot of the ENBT causing this timeout. It can appear to be fixed when a soft restart is issued (After a Flash, Reset from Logix,, or a change of duplex setting). There are 2 possible work-arounds for this: #1. Add code in the controller to automatically reset the ENBT using an explicit message and the First Scan bit. OR #2. Change the ENBT to Autobaud - This will make the ENBT boot up slower and in turn allow more time for the controller to boot. Firmware Version 4.004 which is now released is supposed to fix the issue. I have not personally tried it yet though.

Sorry for the late response, Here is some information from my Rockwell Rep. Unlike the 1756-ENBT, the 1768-ENBT will not function without the controller. This ENBT may time-out on power-up if it doesn't see the controller in time. Sometimes the boot-up of the controller takes longer than the boot of the ENBT causing this timeout. It can appear to be fixed when a soft restart is issued (After a Flash, Reset from Logix,, or a change of duplex setting). There are 2 possible work-arounds for this: #1. Add code in the controller to automatically reset the ENBT using an explicit message and the First Scan bit. OR #2. Change the ENBT to Autobaud - This will make the ENBT boot up slower and in turn allow more time for the controller to boot. Firmware Version 4.004 which is now released is supposed to fix the issue. I have not personally tried it yet though.

I have had this same issue with the Compact ENBT with the same firmware, If you reset the ENBT Module the Processor will appear for an unknown amount of time. Resolution: Rockwell replaced both ENBT Modules under warranty.