Here’s what more than 2,500 business decision-makers around the world say.Download the report
...with the Facility Hero app in hand! Discover how you can optimize your maintenance efforts today.Learn more
Access tailored services, 24/7 self-service and expert help. Anywhere, anytime, any project.Discover now
Everything you need to know about our IoT technology backbone.Learn more
Explore our global offerings or select your country from one of our five regions.Global
Découvrez nos offres globales ou sélectionnez votre pays dans l’une de nos cinq régions.
Goals and Symptoms
NOE771xx shows up as an ETY410 when viewed in OS Loader.
Facts and Changes
Causes and Fixes
The 140NOE771xx (i.e., 140 NOE77111, etc.) shows up as an ETY410 when viewed in OS Loader.
The reason the 'OS Loader' shows the NOE as an EY410 is because the NOE received a bad or
incomplete download of the exec firmware. This caused the module to be missing a hardware
identification file that tells 'OS Loader' what type of module it is connected to. When this hapens,
it defaults to the ETY410 identification.
Attempts to download a new exec will fail because the OS Loader will not allow a download
when there is a mismatch in the hardware identification
To resolve the problem, the module will need to be sent back to the factory for repair.
Sign up for all the latest solutions, offers and best practices straight to your inbox.
We are excited that you have joined the group. You will receive your welcome email soon describing the program and what to expect in the upcoming weeks. Enjoy!