| Posted: Friday Jul 2nd, 2010 10:01 pm |
|
1st Post |
juwi_uk
Member
back to top
|
Can I suggest a enhancement request.
Currently when you send RS or RS00, then Comfort is reset. Thats fine!  But also any UCM/Ethernet connection is also dropped. Not good 
Please can this be changed such that the above commands JUST reset the Comfort CPU and leave the UCM running such that the TCP socket/session remain connected.
Maybe RS00 just resets the comfort CPU whereas RS resets everything. If I want to reset the UCM/Ethernet I can send an individual RSxx command to for that specific UCM ID.
Julian
|
| Posted: Saturday Jul 3rd, 2010 02:28 am |
|
2nd Post |
ident
Administrator
| Joined: | Wednesday Aug 9th, 2006 |
| Location: | Singapore |
| Posts: | 3493 |
| Status: |
Offline
|
back to top
|
There cannot be a command that resets Comfort alone, because part of the Comfort boot-up sequence resets all modules including keypads, SCS, UCMs, RIOs and.door stations so that all modules are at a known state.
You can reset individual modules using RSxx where xx is the ID eg RS12 resets the UCM ID2, RS41 resets Keypad 1
|
| Posted: Saturday Jul 3rd, 2010 10:32 pm |
|
3rd Post |
juwi_uk
Member
back to top
|
Sure, I appreciate you can reset individual modeles, that's fine.
I dont see why though that the firmware could not be enhanced such that at least you could decide whether to reset the UCM module you are using to communicate/action Comfort be it via UCM Ethernet/Serial/USB.
Julian
|
| Posted: Sunday Jul 4th, 2010 02:33 am |
|
4th Post |
slychiu
Administrator
| Joined: | Saturday Apr 29th, 2006 |
| Location: | Singapore |
| Posts: | 5498 |
| Status: |
Offline
|
back to top
|
It is just like rebooting a PC remotely using a TCP session.
You would expect to have to log in again to access the PC, it would not make an exception for the TCP socket that caused the reboot
|
| Posted: Sunday Jul 4th, 2010 07:23 am |
|
5th Post |
juwi_uk
Member
back to top
|
Hi Chiu,
I dont know what WizComfort does then but as far as my ComfortClient is concerned I get a "An existing connection was forcibly closed by the remote host" error back from the TCP connection when Comfort is reset. I currently try to auto reconnect but would rather that I didnt have to do that in code. From everything I see it definately does drop the TCP session.
I tried in Comfigurator, doing an RS from the IO Monitor window and whilst this doesnt show a drop/reconnection, it doesnt show anything; it just stays in a logged on state and ignores all further commands. I had to press log Logout and Login again before it started accepting commands again.
Regards
Julian
Last edited on Sunday Jul 4th, 2010 07:46 am by juwi_uk
|
| Posted: Sunday Jul 4th, 2010 07:35 am |
|
6th Post |
slychiu
Administrator
| Joined: | Saturday Apr 29th, 2006 |
| Location: | Singapore |
| Posts: | 5498 |
| Status: |
Offline
|
back to top
|
What I mean is that when you reset/reboot Comfort it resets everything. All modules are reset. It cannot be avoided. The UCMs have to log in again
If Comfigurator resets Comfort, it is logged out, although the software does not know, so you have to log out and log in again
|
| Posted: Sunday Jul 4th, 2010 07:44 am |
|
7th Post |
juwi_uk
Member
back to top
|
Yes I know what you mean, in the ComfortClient I have a "Connection Check" thread that tests the connection every 10 secs, if the connection is dropped I reset button state too so that the Login/LogOff button (and other UI features) shows the correct state.
That same thread also attempts a reconnect for up to 10 retries. If the connection was dropped due to a temporary blip (a reset for example) then it'll try to reconnect and log you back on (if you were previously logged in at the time the session was dropped) using cached credentials. If the WAN/LAN failure is more serious then the maximum retries will be reached and the re-connection attempts aborted.
Regards
Julian
|
|
