View single post by slychiu | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Posted: Saturday Jan 12th, 2019 07:54 am |
|
||||||||||||
slychiu
|
It would be good to have a better idea of the STATE of the remote connection.... currently there are 2 indicators 1st is that the login changes to logout (indicating that you are logged in !)2nd is that the remote address is displayed in the bottom right hand corner of comfigurator. So perhaps use the remaining space at the bottom of the page where the current network (remote) is located to indicate login and port number and time logged in etc etc etc. Currently the information on the bottom status bar is; Network IP address and Port, Comfort Model, Vocabulary, File System. Comfort time.On the left of the bottom status bar, status info about UCMs which are in focus is shownSo a lot of useful info already. The only one we do not have is login time but I am not sure if that would be very useful Engineer advanced and Engineer simplified - really don't see the point of this ! Engineer simplified is to make it lkess confusing for newcomersAdvanced and simplified menu options is not an uncommon feature in software. Anyway if you dont need the simplified option, set in advanced. The cclx file will retain the last option Event log - greater visibility in the event log when remote sign in is enabled or disabled this applies to both configurator and the app. Remote sign in is already recorded in the event log Access to engineer menu by end user - I think its not a good idea to allow the end user ready access to the engineer screen. I think that you should password protect the engineer menu by use of the engineer code (which should be greyed out or not visible in the user menu!). There is an option "Require Engineer Code to write to Comfort" which requires the engineer code to wrote to Comfort and prevents the user from doing a write.However use of Engineer ccode requires the user to press F0 on the keypad to protect the user from unauthorised Engineer programming. I dont recommend that as it may be inconvenient but it is there if you need to prevent the user from doing things Or you just do not let the user have access to the cclx file which is simpler
|
||||||||||||
|