Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
C? and s? queries not working
#1
Hi,

Flashed my UCM\'s from 5.178 to 5.192 today.

(1) C?xx and s?xx requests no longer send me reports back on the RS232 bus.  I only seem to get when Comfort decides to send them.

(2) Scan UCM\'s in Comfigurator 3.1.3 doesn\'t recognise the UCM05 either or report flash version (shows as 0.0) though \"System Information\" does show correctly.

Should I roll-back to 5.178 as this worked correctly.

Do I need a specific MPU firmware;  I\'m running 5.166 (because I needed the Celsius announcement).

Regards

Julian

 

 
Reply
#2
There was a bug in UCM 5.192 that stopped the C? and S? commands from working
UCM 5.200 (Not released yet) fixes this, see attached. Please try it


Attached Files
.zip   UCM5_200.zip (Size: 17.58 KB / Downloads: 6)
Reply
#3
Thanks Chiu, I\'ll try it and report back.

It would be good though if you could publish known errors like this on the forum as well like you do with Comfigurator as this firmware has been out for a while and you\'ve presumably also known of the issue. 

If I\'d known these features were broken I would have waited until the next build and saved myself a few hours effort yesterday upgrading my UCM\'s (and trying to work out why my ComfortClient was doing strange things).  Sad

The firmware section of the forum is where I would have looked for this.

Regards

Julian
Reply
#4
OK, just flashed teh UCM05 to 5.200 and as you say the counters and sensors are now reporting correctly.  Phew....!

The UCM still doesnt seem to want to report it\'s version to Comfigurator 3.1.3 but 5.178 did seem too. As mentioned before teh System Information report looks OK though.

See screenshots attached

 
Reply
#5
Hi Chiu,

Upgraded to 5.200 and the counters and sensors are now reporting correctly...phew!

The UCM scan in Comfigurator 3.1.3 still is incorrect but did work with 5.178.  See screenshots attached.  Works ok in System Information though.

Regards

Julian

p.s you also see the issue I menationed in another thread about my UCM_Smartfit entry being overwritten each time by a scan.

 



Attached Files Thumbnail(s)
   
Reply
#6
[user=876]juwi_uk[/user] wrote:
Quote: It would be good though if you could publish known errors like this on the forum as well like you do with Comfigurator as this firmware has been out for a while and you\'ve presumably also known of the issue. 

If I\'d known these features were broken I would have waited until the next build and saved myself a few hours effort yesterday upgrading my UCM\'s (and trying to work out why my ComfortClient was doing strange things).  Sad

The firmware section of the forum is where I would have looked for this.

Regards

Julian
As a matter of fact this bug is reported in the Firmware History section, see http://www.comfortforums.com/forum81/1619.html

Firmware History is now split up into subforums for each type of device so it is easy to find what you are looking for

Reply
#7
[user=876]juwi_uk[/user] wrote:
Quote:Hi Chiu,

Upgraded to 5.200 and the counters and sensors are now reporting correctly...phew!
The UCM scan in Comfigurator 3.1.3 still is incorrect but did work with 5.178.  See screenshots attached.  Works ok in System Information though.
p.s you also see the issue I menationed in another thread about my UCM_Smartfit entry being overwritten each time by a scan.
The Scan for UCMs does not work if you connect the UCM after you reset Comfort
This is because the information for the scan is taken when Comfort starts up
The bahaviour is the same for UCM 5.178 and 5.192
If you reset Comfort with the UCM/Ethernet connected and do a scan you will get the correct version

Reply
#8
Apologies Chiu I missed this.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)