Comfort  Automation/ Security System Forums Home
Home Search search Menu menu Not logged in - Login | Register

multiple access
 Moderated by: slychiu, mattbrain, benstinton
 New Topic   Reply   Printer Friendly 
 Rate Topic 
AuthorPost
 Posted: Sunday Mar 5th, 2017 06:55 pm
   PM  Quote  Reply 
1st Post
bagushandhoko
Member
 

Joined: Saturday Jul 25th, 2015
Location: Jakarta, Indonesia
Posts: 91
Status: 
Offline

  back to top

i can not access comfort , even from "settings" comfigurator detect right IP. but there is notification port is busy.  Is it because PI access it at the same time ?



 Posted: Sunday Mar 5th, 2017 07:33 pm
   PM  Quote  Reply 
2nd Post
Swiss-Toni
UCM Pi Users


Joined: Thursday Sep 15th, 2011
Location: Greater London, United Kingdom
Posts: 349
Status: 
Offline

  back to top

Possibly, you may have to do a hard reset on the etho if you cant free up from comfigurator



 Posted: Monday Mar 6th, 2017 10:01 am
   PM  Quote  Reply 
3rd Post
bagushandhoko
Member
 

Joined: Saturday Jul 25th, 2015
Location: Jakarta, Indonesia
Posts: 91
Status: 
Offline

  back to top

yes ... reboot can not solve the problem 



 Posted: Monday Mar 6th, 2017 03:49 pm
   PM  Quote  Reply 
4th Post
Swiss-Toni
UCM Pi Users


Joined: Thursday Sep 15th, 2011
Location: Greater London, United Kingdom
Posts: 349
Status: 
Offline

  back to top

If you are saying that the R-PI is locking you out you have two different ports which can be accessed etho 3 1001 & 1002 are you locked out on both have you tried disconecting R-PI



 Posted: Monday Mar 6th, 2017 08:34 pm
   PM  Quote  Reply 
5th Post
mattbrain
UCM Pi Users


Joined: Tuesday Jun 12th, 2007
Location: United Kingdom
Posts: 185
Status: 
Offline

  back to top

The RPi requires continual access to the UCM/Eth device. The UCM/Eth3 has 2 available ports whilst the original UCM/Eth only has one.

The RPi will release the port when the service is stopped, and the Eth3 will kick the RPi out if comfigurator is asked to update the Comfort system (the RPi will reconnect once Comfigurator has finished - it can take a moment or 2).

If the RPi is disconnected ungraciously (by pulling the network cable for example), The UCM/Eth3 will wait for the timeout before releasing the port (the timeout if defined in the UCM/Eth3 manager in Comfigurator).

A future version will use/require a dedicated UCM and if funds allow I would recommend this now.

Thanks,

Matt



 Posted: Tuesday Mar 7th, 2017 08:48 pm
   PM  Quote  Reply 
6th Post
Pgordon
Member
 

Joined: Saturday Sep 23rd, 2006
Location: London, United Kingdom
Posts: 237
Status: 
Offline

  back to top

I'm also aware that there's a problem with the UCM-ETH03 not resetting correctly after the Bus monitor has been used in Comfigurator... I've experienced this myself a few times. After using bus monitor, the UCM remained unresponsive until the UCM was reset (by the miniature pushbutton on the UCM in my case).



 Posted: Wednesday Mar 8th, 2017 06:31 am
   PM  Quote  Reply 
7th Post
slychiu
Administrator


Joined: Saturday Apr 29th, 2006
Location: Singapore
Posts: 5493
Status: 
Offline

  back to top

Yes this is a known problem with UCM/ETH03 after Bus monitor mode
The next ucm firmware should improve it



 Posted: Thursday Mar 9th, 2017 04:07 pm
   PM  Quote  Reply 
8th Post
bagushandhoko
Member
 

Joined: Saturday Jul 25th, 2015
Location: Jakarta, Indonesia
Posts: 91
Status: 
Offline

  back to top

so using diifferent port for ucm/eth and PI can not solve the issues, isnt it ?



 Current time is 06:23 am
Top




UltraBB 1.172 Copyright © 2007-2014 Data 1 Systems