Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
CBUS firmware update 6.011 to 7.045
#11

ETH02
The ETH02 has a tall component just behind the RJ45 which you can just see



ETH03


Do you have a USB interface?
Reply
#12
You can also click on DS manager and CS Manager in Comfigurator Options > Settings UCM connections
if you see the IP in DS manager it is ETH02
If you see the IP in CS Manager then it is ETH02

Can you also check the idle time out of the ETH02 in DS Manager ? Set to 0 for no time out
Reply
#13
OK, so it\'s definitely an ETH02. By idle time out, do you mean connection timeout? I\'ve set this to 0. It did get to 76% on the update (cable) first time of trying after that, but again timed out with the error \'unable to write to the transport connection: an existing connection was forc...\'.

Are there any other DS Manager settings that need to change? I have everything as default except the IP is DHCP enabled and now the connection timeout as 0.

Also - I can now ONLY connect to the UCM through comfigurator in update firmware mode with update cable attached. With the cable removed, Comfigurator can no longer connect to the UCM even though DS MAnager can see it.

I don\'t have a UCM USB
Reply
#14
You will not be able to connect to the Comfort now that the firmware has been erased
You cana only connect by UCM/eth02 when the programing cable is connected

There are no other relevant settings on DS manager
There seems to be a problem on the network
Try connecting the ETH02 direct to the PC and set a IP address in the same subnet as your PC. Your PC also need to fix the IP address as there is no DHCP server

If your upgrade goes to 70% you should be abble to complete it is there is no interruptions


Reply
#15
When the upgrade timed out, did you get a message \"Time out, Upgrade from Last Address?\"
This should allow you to continue the upgrade from he last address and not start again so it shoudl complete even if it times out a few times
Reply
#16
Hi Chiu - your suggestion on connecting directly to the PC worked, so I\'m back up and running with all UCMs updated. THANKS! I guess there is a network issue with the router, though I\'m not having any problems with anything else.

In answer to your question, Yes, I did get that message. If I click yes when using the cable method it says it is not supported. When I did that using the network update, I got a subsequent error that DUT wasn\'t present, I then get a message asking to do the update again, comfigurator takes a while to respond but then does the firmware update again from 0% but then same error.

Will there be a firmware update to ETH02 to fix the timout issue or can I assume it is in fact another issue with the router and not dare to try a network update again until I perhaps replace the router?
Reply
#17
If it is due to the network, it cannot be fixed by  firmware
We will do more testing with ETH02
But the next version of Comfigurator should allow you to contiinue from the last address without any other error messages
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)