Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
UcmPI not communicating with Comfort
#1
I upgrade to Comfort 4.x a few days back, I had to restart the ucmPi tonight after updating my network gear.  The ucm can no longer be polled,  the pi seems to reboot as node-red seems to be running.

Trace produced the shared results


Attached Files Thumbnail(s)
   
Reply
#2
You mean Comfigurator v4.0.3?
Comfigurator cannot affect the UCM/Pi and cause it to rebooot. Can you try it with Comfigurator 3.14.14. Comfigurator 3 is noty uninstalled when you install comfigurator 4
Reply
#3
(10-29-2025, 02:02 AM)slychiu Wrote: You mean Comfigurator v4.0.3?
Comfigurator cannot affect the UCM/Pi and cause it to rebooot. Can you try it with Comfigurator 3.14.14. Comfigurator 3 is noty uninstalled when you install comfigurator 4

I am not saying that is the cause, I am saying the only changes lately were the Comfigurator to v4.0.3 and the firmware updates, nothing else was done on the setup. Using Comfigurator v3.x does not make any difference.


Attached Files Thumbnail(s)
   
Reply
#4
The reply UBF2 means that the UCM/PI firmware  has been corrupted somehow.  You can try to use the UCM with firmware programming cable to ureprogram the firmware of the UCM/Pi
Reply
#5
(10-30-2025, 01:08 AM)slychiu Wrote: The reply UBF2 means that the UCM/PI firmware  has been corrupted somehow.  You can try to use the UCM with firmware programming cable to ureprogram the firmware of the UCM/Pi

Thanks, I have never done that, can you walk me through the process or point me documentation that goes through the process?
Reply
#6
see instructions here http://www.comfortforums.com/thread-1782.html
Reply
#7
The UCM/Pi software will automatically reboot if it does not see the Watchdog toggling the Output pin every few seconds. You can click on the pause button while you are debugging to prevent this:


Attached Files Thumbnail(s)
   
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)