Host Engineering Forum
General Category => Do-more CPUs and Do-more Designer Software => Topic started by: Controls Guy on June 10, 2022, 03:41:38 PM
-
I flashed a couple 10ER3s to OS 2.9.4 with no apparent issue. Loaded them with a stock program, and on testing found issues with the IO address mapping, which were due to the CPU showing up in the I/O config as a DM1E-M (ID 80)
It shows as an M in the I/O Map dialog and in Dashboard, but the name shows correctly as a 10ER3 in System Info (probably a correctly loaded DST register I assume).
I flashed one back to 2.9.3 and it works correctly now. I swapped in another 2.9.3 CPU and kept one of the malfunctioning ones at 2.9.4 in case you need me to reproduce it.
-
I flashed a couple 10ER3s to OS 2.9.4 with no apparent issue. Loaded them with a stock program, and on testing found issues with the IO address mapping, which were due to the CPU showing up in the I/O config as a DM1E-M (ID 80)
It shows as an M in the I/O Map dialog and in Dashboard, but the name shows correctly as a 10ER3 in System Info (probably a correctly loaded DST register I assume).
I flashed one back to 2.9.3 and it works correctly now. I swapped in another 2.9.3 CPU and kept one of the malfunctioning ones at 2.9.4 in case you need me to reproduce it.
Weird. Wonder if something got broken while removing the -10 module limitation. Can't think of anything else that might be different.
-
Do you have a -10 you can test? I know ADC is out of inventory right now. If you need me to, I can ship this one back to Host.
-
Do you h have a -10 you can test? I know ADC is out of inventory right now. If you need me to, I can stop this one back to Host.
Just tried it with a -10AR3 and it's working fine. Still digging...
-
Hmmm. When I'm back in the shop, I'll try another one. I may have only ED23's though.
-
I'll also try taking that one back to 2.9.3 and doing the upgrade again and see what happens. Shouldn't be anything too random though if it happened to two units.
-
They only differ by IDs stored in a small discovery flash. Really shouldn't matter at all, but I can fake others to see what happens.
-
I swapped ID's to fake the ED23, no difference. If it is repeatable, I guess we should look at your hardware.
-
Well, grabbed a ED23, checked that it was correct on 2.9.3, and flashed forward to 2.9.4. Still shows correctly on Dashboard, System Info, and I/O Map. Grabbed the 'malfunctioning' ER that I kept in case I needed to reproduce, powered it up, and it was also showing correctly in all three places, despite still being on 2.9.4. Never even got the chance to go back to 2.9.3 and then back to 2.9.4. No idea what happened. [shrug]
-
Well, grabbed a ED23, checked that it was correct on 2.9.3, and flashed forward to 2.9.4. Still shows correctly on Dashboard, System Info, and I/O Map. Grabbed the 'malfunctioning' ER that I kept in case I needed to reproduce, powered it up, and it was also showing correctly in all three places, despite still being on 2.9.4. Never even got the chance to go back to 2.9.3 and then back to 2.9.4. No idea what happened. [shrug]
It's possible the board-to-board connector isn't well seated. Sometimes knocks while in transit have done that. We're still happy to look at it.