• H
    hayden_AUS

    Hi,

    I have an instance that has a function to turn on THREE Modbus outputs, when ONE data point goes high, and then subsequently turning them all back off when the point goes back low.
    This all works fine using "Point Links", with no scripts.

    Recently I had an event appear :
    9/5/2018 06:33:30 Cannot execute point link because it is currently running 9/5/2018 06:37:30 - Returned to normal 4 minutes

    The status of the output changed to active in Mango, but didn't actually change the output to high.

    I checked the point link, and it's settings are the same as the other two. Each point is on a different data source, but I did not get any data source events.

    I cannot find any more info in the logs.

    Does anyone know why this would of occurred, or exactly where to look in the logs?

    posted in Mango Automation general Discussion read more
  • H
    hayden_AUS

    Hi,

    I have done Linux installs before, but just experiencing the problem below.
    Getting "command not found" but the ma.sh file is there.
    Any ideas?

    pi@raspberrypi:/opt/mango/bin $ ls
    ext-available       h2-web-console.sh  ma.sh         ma-stop.sh
    ext-enabled         ma-init.sh         ma-start.bat  upgrade.bat
    h2-web-console.bat  ma-restart.sh      ma-start.sh   upgrade.sh
    pi@raspberrypi:/opt/mango/bin $ ./ma.sh start
    -bash: ./ma.sh: Permission denied
    pi@raspberrypi:/opt/mango/bin $ sudo ./ma.sh start
    sudo: ./ma.sh: command not found
    pi@raspberrypi:/opt/mango/bin $
    
    

    Also my service won't start...

    pi@raspberrypi:/opt/mango/bin $ sudo service mango start
    Job for mango.service failed because the control process exited with error code.
    See "systemctl status mango.service" and "journalctl -xe" for details.
    pi@raspberrypi:/opt/mango/bin $ systemctl status mango.service
    ā— mango.service - LSB: Start or stop the Mango Automation
       Loaded: loaded (/etc/init.d/mango; generated; vendor preset: enabled)
       Active: failed (Result: exit-code) since Thu 2018-05-03 17:50:13 AEST; 30s ag
         Docs: man:systemd-sysv-generator(8)
      Process: 734 ExecStart=/etc/init.d/mango start (code=exited, status=126)
    
    May 03 17:50:13 raspberrypi systemd[1]: Starting LSB: Start or stop the Mango Au
    May 03 17:50:13 raspberrypi systemd[1]: mango.service: Control process exited, c
    May 03 17:50:13 raspberrypi systemd[1]: Failed to start LSB: Start or stop the M
    May 03 17:50:13 raspberrypi systemd[1]: mango.service: Unit entered failed state
    May 03 17:50:13 raspberrypi systemd[1]: mango.service: Failed with result 'exit-
    lines 1-11/11 (END)...skipping...
    ā— mango.service - LSB: Start or stop the Mango Automation
       Loaded: loaded (/etc/init.d/mango; generated; vendor preset: enabled)
       Active: failed (Result: exit-code) since Thu 2018-05-03 17:50:13 AEST; 30s ago
         Docs: man:systemd-sysv-generator(8)
      Process: 734 ExecStart=/etc/init.d/mango start (code=exited, status=126)
    
    May 03 17:50:13 raspberrypi systemd[1]: Starting LSB: Start or stop the Mango Automation...
    May 03 17:50:13 raspberrypi systemd[1]: mango.service: Control process exited, code=exited status=126
    May 03 17:50:13 raspberrypi systemd[1]: Failed to start LSB: Start or stop the Mango Automation.
    May 03 17:50:13 raspberrypi systemd[1]: mango.service: Unit entered failed state.
    May 03 17:50:13 raspberrypi systemd[1]: mango.service: Failed with result 'exit-code'.
    
    
    pi@raspberrypi:~ $ sudo service mango start
    Job for mango.service failed because the control process exited with error code.
    See "systemctl status mango.service" and "journalctl -xe" for details.
    pi@raspberrypi:~ $ journalctl -xe
    May 03 18:00:46 raspberrypi systemd[618]: Startup finished in 156ms.
    -- Subject: System start-up is now complete
    -- Defined-By: systemd
    -- Support: https://www.debian.org/support
    --
    -- All system services necessary queued for starting at boot have been
    -- successfully started. Note that this does not mean that the machine is
    -- now idle as services might still be busy with completing start-up.
    --
    -- Kernel start-up required KERNEL_USEC microseconds.
    --
    -- Initial RAM disk start-up required INITRD_USEC microseconds.
    --
    -- Userspace start-up required 156093 microseconds.
    May 03 18:00:46 raspberrypi systemd[1]: Started User Manager for UID 1000.
    -- Subject: Unit user@1000.service has finished start-up
    -- Defined-By: systemd
    -- Support: https://www.debian.org/support
    --
    -- Unit user@1000.service has finished starting up.
    --
    -- The start-up result is done.
    May 03 18:00:46 raspberrypi kernel: Under-voltage detected! (0x00050005)
    May 03 18:01:00 raspberrypi systemd[1]: Time has been changed
    -- Subject: Time change
    -- Defined-By: systemd
    -- Support: https://www.debian.org/support
    --
    -- The system clock has been changed to REALTIME microseconds after January 1st, 1970.
    May 03 18:01:00 raspberrypi systemd-timesyncd[265]: Synchronized to time server 13.55.50.68:123 (2.debian.pool.ntp.
    May 03 18:01:00 raspberrypi systemd[618]: Time has been changed
    -- Subject: Time change
    -- Defined-By: systemd
    -- Support: https://www.debian.org/support
    --
    -- The system clock has been changed to REALTIME microseconds after January 1st, 1970.
    May 03 18:01:00 raspberrypi systemd[1]: apt-daily.timer: Adding 5h 25min 53.755639s random time.
    May 03 18:01:00 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding 33min 55.036043s random time.
    May 03 18:01:02 raspberrypi kernel: Voltage normalised (0x00000000)
    May 03 18:01:22 raspberrypi sudo[661]:       pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/usr/sbin/service
    May 03 18:01:22 raspberrypi sudo[661]: pam_unix(sudo:session): session opened for user root by pi(uid=0)
    May 03 18:01:23 raspberrypi systemd[1]: Starting LSB: Start or stop the Mango Automation...
    -- Subject: Unit mango.service has begun start-up
    -- Defined-By: systemd
    -- Support: https://www.debian.org/support
    --
    -- Unit mango.service has begun starting up.
    May 03 18:01:23 raspberrypi systemd[1]: mango.service: Control process exited, code=exited status=126
    May 03 18:01:23 raspberrypi systemd[1]: Failed to start LSB: Start or stop the Mango Automation.
    -- Subject: Unit mango.service has failed
    -- Defined-By: systemd
    -- Support: https://www.debian.org/support
    --
    -- Unit mango.service has failed.
    --
    -- The result is failed.
    May 03 18:01:23 raspberrypi systemd[1]: mango.service: Unit entered failed state.
    May 03 18:01:23 raspberrypi systemd[1]: mango.service: Failed with result 'exit-code'.
    May 03 18:01:23 raspberrypi sudo[661]: pam_unix(sudo:session): session closed for user root
    May 03 18:01:23 raspberrypi kernel: Under-voltage detected! (0x00050005)
    May 03 18:01:29 raspberrypi kernel: Voltage normalised (0x00000000)
    lines 1375-1435/1435 (END)
    
    

    posted in Mango Automation Installation read more
  • H
    hayden_AUS

    Thanks Phil,
    I was using the "Take timestamp, add delay, and then check to see if current timestamp was greater than that value".
    It didn't work in that environment.

    I will give the RuntimeManager method a go, thanks.

    H

    posted in Mango Automation general Discussion read more
  • H
    hayden_AUS

    Hi all, I have a site that I have it's internet connection OFF most of the time, to conserve battery power.

    When I get an urgent event or alarm, I need to turn on the Internet, and send an email.

    The issues I have is that I need to add a delay between the time the event occurs, and the email is sent, to allow the router and satellite receiver to boot.

    I have tried using Javascript in a Meta data point, but can't get that to work.
    It would be good to have a delay option in "Event handlers".

    Does anyone know the best way to do this?

    Thanks

    posted in Mango Automation general Discussion read more
  • H
    hayden_AUS

    Hi,

    Does anyone know a simple way to label these gauges?

    Putting text in "text and Font" shows up, but not after I save.

    ....can't be this hard!!!

    H

    posted in Mango Automation general Discussion read more
  • H
    hayden_AUS

    Thanks for the reply Joel,
    I'll let you guys know if I have real trouble.
    Hayden

    posted in User help read more
  • H
    hayden_AUS

    Thanks Phil,
    Let's assume there are two types of Mango users, those who are programming veterans, who like and use Mango for the way it works and focus on the operation of it, and those that install sensors, equipment, and want to report useful data from the system.
    I am the latter, and while I have grounded basic programming skills, the information provided on this data source is inadequate for those who do not spent a large portion of their days banging out code.
    I will try to work through the info, but cannot see why Infinite Automation cannot produce some step by step guides or video on some of the more technical aspects of Mango. The time spent by one person would benefit many.
    Hayden

    posted in User help read more
  • H
    hayden_AUS

    Hi has there been a tutorial for setting up the data file data sources, including CSV file types? Video?
    Even something to point in the right direction to get started.
    Any help appreciated.

    Hayden

    posted in User help read more
  • H
    hayden_AUS

    Hi Jeremy,

    After trying pretty much everything with the Dlink DWR-921, I decided to swap it out with a Digi Connectport X4 with built in 3G module (and Xbee). I had been using it in the office for my Xbee sensor network.

    The X4 has solved the problem, and I can now connect to the ES and CCTV remotely, no problem. Although it is a bit of a relic now, 2010 vintage, the speed is still pretty good.

    Dlink DWR921 - Of no use for M2M.

    Thanks for you help Jeremy

    posted in MangoES Hardware read more