JW

Forum Replies Created

Viewing 12 posts - 136 through 147 (of 147 total)
  • Author
    Posts
  • in reply to: fit to screen/width by default #7260
    JW
    Participant

    I mean no matter what scale the user choose previously, e.g. fit to width, 50%zoom, or 100%zoom before he close the web, next time he opens scheme view again, it will be “fit to screen”. is it possible?

    in reply to: fit to screen/width by default #7255
    JW
    Participant

    The scale setting can be remember by browser, which is a nice solution.

    However, sometimes I wanted to force the browser use “fit to screen” every time the user open a scheme view, is there a way to do it?

    Because I usually use a very high-res map/cad drawings (e.g.6000×4000) as background image to allow user to zoom-in to see details. if it’s not “fit to screen” at the beginning, some user lost track of where they are looking at.

    in reply to: version 5.8.1 not working on ubuntu 20.04 #6951
    JW
    Participant

    here maybe the root cause.

    the line different from 2 version in daemon files scada
    5.8.1
    EXE_DIR=/etc/scada/ScadaServer/
    5.8.0
    EXE_DIR=/opt/scada/ScadaServer/

    in reply to: version 5.8.1 not working on ubuntu 20.04 #6950
    JW
    Participant

    Hi manjey73, thanks for your help.

    it turns out it wasn’t the ScadaData.Svc.dll make it work. it was the daemons of 5.8.0 make it work.

    I tried the following tests:
    1. fresh install of 5.8.1, does not work;
    2. fresh install of 5.8.0, work;
    3. update /opt/scada to5.8.1 + keep daemons from 5.8.0, work.

    the file size and edit time are slightly different between 2 set of daemon files, but i can’t find the difference between the content.
    5.8.0———-
    -rw-rw-r– 1 jw jw 1666 2019-04-19 12:18:02.000000000 +0800 scadaagent
    -rw-rw-r– 1 jw jw 1675 2018-11-22 10:02:24.000000000 +0800 scadacomm
    -rw-rw-r– 1 jw jw 1735 2018-11-22 10:02:24.000000000 +0800 scadaserver
    5.8.1———-
    -rw-rw-r– 1 jw jw 1666 2019-04-19 12:18:00.000000000 +0800 scadaagent
    -rw-rw-r– 1 jw jw 1748 2018-11-22 09:35:06.000000000 +0800 scadacomm
    -rw-rw-r– 1 jw jw 1810 2018-11-22 09:35:06.000000000 +0800 scadaserver

    in reply to: version 5.8.1 not working on ubuntu 20.04 #6942
    JW
    Participant

    Are ScadaData.Svc.dll in ScadaServer and ScadaComm folder needed for version 5.8.1?

    I copied those 2 files from 5.8.0 to 5.8.1. It seems working now.

    in reply to: version 5.8.1 not working on ubuntu 20.04 #6941
    JW
    Participant

    in admin app, the status show Undefined instead of error.
    there is no log files in /opt/scada/ScadaServer/Log, /opt/scada/ScadaServer/Log

    ——————————————————————-
    service status:

    jw@jw-ubuntu:~/Desktop$ sudo service scadaserver status
    scadaserver.service – LSB: SCADA-Server daemon
    Loaded: loaded (/etc/init.d/scadaserver; generated)
    Active: failed (Result: exit-code) since Fri 2020-06-26 09:41:07 HKT; 2min 36s ago
    Docs: man:systemd-sysv-generator(8)
    Process: 883 ExecStart=/etc/init.d/scadaserver start (code=exited, status=203/EXEC)

    Jun 26 09:41:07 jw-ubuntu systemd[1]: Starting LSB: SCADA-Server daemon…
    Jun 26 09:41:07 jw-ubuntu systemd[1]: scadaserver.service: Control process exited, code=exited, status=203/EXEC
    Jun 26 09:41:07 jw-ubuntu systemd[1]: scadaserver.service: Failed with result ‘exit-code’.
    Jun 26 09:41:07 jw-ubuntu systemd[1]: Failed to start LSB: SCADA-Server daemon.
    jw@jw-ubuntu:~/Desktop$ sudo service scadacomm status
    ● scadacomm.service – LSB: SCADA-Communicator daemon
    Loaded: loaded (/etc/init.d/scadacomm; generated)
    Active: failed (Result: exit-code) since Fri 2020-06-26 09:41:07 HKT; 2min 39s ago
    Docs: man:systemd-sysv-generator(8)
    Process: 896 ExecStart=/etc/init.d/scadacomm start (code=exited, status=203/EXEC)

    Jun 26 09:41:07 jw-ubuntu systemd[1]: Starting LSB: SCADA-Communicator daemon…
    Jun 26 09:41:07 jw-ubuntu systemd[1]: scadacomm.service: Control process exited, code=exited, status=203/EXEC
    Jun 26 09:41:07 jw-ubuntu systemd[1]: scadacomm.service: Failed with result ‘exit-code’.
    Jun 26 09:41:07 jw-ubuntu systemd[1]: Failed to start LSB: SCADA-Communicator daemon.

    ————————————————–
    journalctl log: but the scadaserver and scadacomm file are in /etc/init.d already

    Jun 26 10:04:40 jw-ubuntu systemd[1]: Starting LSB: SCADA-Server daemon…
    — Subject: A start job for unit scadaserver.service has begun execution
    — Defined-By: systemd
    — Support: http://www.ubuntu.com/support

    — A start job for unit scadaserver.service has begun execution.

    — The job identifier is 1786.
    Jun 26 10:04:40 jw-ubuntu systemd[3498]: scadaserver.service: Failed to execute command: No such file or directory
    Jun 26 10:04:40 jw-ubuntu systemd[3498]: scadaserver.service: Failed at step EXEC spawning /etc/init.d/scadaserver: No such file or directory
    — Subject: Process /etc/init.d/scadaserver could not be executed
    — Defined-By: systemd
    — Support: http://www.ubuntu.com/support

    — The process /etc/init.d/scadaserver could not be executed and failed.

    — The error number returned by this process is ERRNO.
    Jun 26 10:04:40 jw-ubuntu systemd[1]: scadaserver.service: Control process exited, code=exited, status=203/EXEC
    — Subject: Unit process exited
    — Defined-By: systemd
    — Support: http://www.ubuntu.com/support

    — An ExecStart= process belonging to unit scadaserver.service has exited.

    — The process’ exit code is ‘exited’ and its exit status is 203.
    Jun 26 10:04:40 jw-ubuntu systemd[1]: scadaserver.service: Failed with result ‘exit-code’.
    — Subject: Unit failed
    — Defined-By: systemd
    — Support: http://www.ubuntu.com/support

    — The unit scadaserver.service has entered the ‘failed’ state with result ‘exit-code’.
    Jun 26 10:04:40 jw-ubuntu systemd[1]: Failed to start LSB: SCADA-Server daemon.
    — Subject: A start job for unit scadaserver.service has failed
    — Defined-By: systemd
    — Support: http://www.ubuntu.com/support

    — A start job for unit scadaserver.service has finished with a failure.

    — The job identifier is 1786 and the job result is failed.

    in reply to: User Definded Event Type #6753
    JW
    Participant

    for the default event 1-5, 11-15 101-114, changing color works.

    but the custom event I added 1001-1010, changing color does’t work.

    in reply to: User Definded Event Type #6745
    JW
    Participant

    Because i set have an array of reading, i put them to different input channel. say 1000 or more. then I over laid them to a scheme. I want to use color to represent the temperature. so it form a line of temperature to simulate a power cable.

    about the text, the 1st text is the value of input channel 1.
    the 2nd text is the value of 2, which i set equal to status of channel 1.

    I use dynamic text to display the 2 values above. which have a 0,000 format.
    so 1003 will be display as 1,003

    in reply to: User Definded Event Type #6742
    JW
    Participant

    achieve this using an alternative solution by adding a lot of condition to the led condition.

    but still wander about the when and how the custom event type work.

    tested item
    1. the channel status CAN be change to custom event type value.
    2. the event log can detect event change of custom event.
    3. the event log that detect event change of custom event are black, not custom event color.
    4. the led and dynamic picture set as “status” color are black, not custom event color.

    in reply to: Log in web page #6599
    JW
    Participant

    I downloaded the plugin from reply #5729. But I can’t find it from plugin store. where can i check for latest version?

    in reply to: Log in web page #6598
    JW
    Participant

    it seems the auto login url use first user account in user table to login for the first time. later, it use admin account login.

    is there any other way to config the auto login to use a specific account?

    in reply to: Unable to receive list of plugins #6594
    JW
    Participant

    I experienced the same issue after updated to version 5.8. haven’t find a solution yet

Viewing 12 posts - 136 through 147 (of 147 total)