Codesys runtime break Python Scripts

2020-03-17T00:15:12.017000Z

Hi Edwin,

I'm trying to replicate your solution by having the script Stop/Start the codesyscontrol with UPS state change but have been unsuccessful.

Was your only change to add these lines to bb_core_power.py? Double quotes or single quotes around the start/stop command?

  if isUPS:
        subprocess.run("sudo bash /etc/init.d/codesyscontrol start", shell=True)
    else:
        subprocess.run("sudo bash /etc/init.d/codesyscontrol stop", shell=True)

Codesys runtime break Python Scripts

2020-02-27T16:30:39.587000Z

Hi,
no I see no way ... no chance to do this.
BR
Edwin

Codesys runtime break Python Scripts

2020-02-27T16:30:37.137000Z

Do I have any options to keep Codesys from abruptly dumping out when the Ethernet port loses power?

Codesys runtime break Python Scripts

2020-02-27T16:30:36.251000Z

no, this is not possible!

Codesys runtime break Python Scripts

2020-02-27T16:30:33.793000Z

Based on this:

"ooops... this runtime was built for RASPBERRYPI (-22, 0x00000BB8, 0xFFFFFFFB)"

Does Codesys use the Ethernet port in some way to determine if the device is a Raspberry Pi? If so, can that check be delayed for 2 minutes before closing out?

Codesys runtime break Python Scripts

2020-02-27T16:30:32.918000Z

Edwin Schwellinger hat geschrieben:
Think if you let eth0 up and running it might work... give this a try if possible.

Tech support at Brainboxes tells me it is not possible. They said it is a hardware design that shuts down peripheral power and cannot be controlled by the power management unit firmware. They would not share the schematics with me, so I am unable to verify this.

Codesys runtime break Python Scripts

2020-02-27T16:30:32.008000Z

Think if you let eth0 up and running it might work... give this a try if possible.
Br Edwin

Codesys runtime break Python Scripts

2020-02-27T16:30:29.360000Z

The BB-400 goes into alert mode, then powers down the peripherals, but keeps the CPU running. If power is restored in less than 60 seconds, it will power the peripherals back up. If no power longer than 60 seconds, it will perform the shutdown -h now

Here is the last few lines from running the recommended test:

SysTaskFrame[425]:  OPCUAServer(tid:1603,OSprio:0) running
SysTaskCreate[497]: create CommCycleHook(prio:223,interval:0us,stacksize:131072)
SysTaskFrame[425]:  CommCycleHook(tid:1604,OSprio:0) running
SysTaskCreate[497]: create X509AsyncTask(prio:255,interval:0us,stacksize:131072)
SysTaskFrame[425]:  X509AsyncTask(tid:1605,OSprio:0) running
SysSockSendTo[1268]: sendto(5,0x76a309f4,8,0x0,...):Invalid argument
SysSockSendTo[1268]: sendto(5,0x76a309f4,8,0x0,...):Invalid argument
SysSockSendTo[1268]: sendto(5,0x76a309f4,8,0x0,...):Invalid argument
SysSockSendTo[1268]: sendto(5,0x76a309f4,8,0x0,...):Invalid argument
SysSockSendTo[1268]: sendto(5,0x76a309f4,8,0x0,...):Invalid argument
SysSockSendTo[1268]: sendto(5,0x76a309f4,8,0x0,...):Invalid argument
SysSockSendTo[1268]: sendto(5,0x76a309f4,8,0x0,...):Invalid argument
SysSockSendTo[1268]: sendto(5,0x76a309f4,8,0x0,...):Invalid argument
SysSockSendTo[1268]: sendto(11,0x76a309f4,8,0x0,...):Invalid argument
SysSockSendTo[1268]: sendto(11,0x76a309f4,8,0x0,...):Invalid argument
SysSockSendTo[1268]: sendto(11,0x76a309f4,8,0x0,...):Invalid argument
SysSockSendTo[1268]: sendto(11,0x76a309f4,8,0x0,...):Invalid argument
SysSockSendTo[1268]: sendto(11,0x76a309f4,8,0x0,...):Invalid argument
SysSockSendTo[1268]: sendto(11,0x76a309f4,8,0x0,...):Invalid argument
SysSockSendTo[1268]: sendto(11,0x76a309f4,8,0x0,...):Invalid argument
SysSockSendTo[1268]: sendto(11,0x76a309f4,8,0x0,...):Invalid argument
ooops... this runtime was built for RASPBERRYPI (-22, 0x00000BB8, 0xFFFFFFFB)

Codesys runtime break Python Scripts

2020-02-27T16:30:28.355000Z

Hi,
guess not.

Could you please stop the plc , followed by a (as sudo):

cd /var/opt/codesys
/opt/codesys/bin/codesyscontrol.bin -d /etc/CODESYSControl.cfg

Then you should a litte more information on this manual start of the runtime.

Why does your UPS not a simple trigger a 'shutdown -h now' - then I think it will close/shutdown the runtime in correct way

BR
Edwin

Codesys runtime break Python Scripts

2020-02-27T16:30:25.812000Z

These are my latest results after further testing:

In the UPS Alert event:

Process List of co* : In UPS Alert Event
   37 ?        00:00:00 kcompactd0
   69 ?        00:00:00 mmc_complete
   73 ?        00:00:00 ext4-rsv-conver
   75 ?        00:00:00 ipv6_addrconf
  607 ?        00:00:01 codesyscontrol.
  714 ?        00:00:13 codesyscontrol.
 1080 ?        00:00:00 COEX-TX-Thread

Codesys Log File
2019-09-09T08:48:43Z, 0x00000071, 1, 0, 0, **************************************************************
2019-09-09T08:48:58Z, 0x00000007, 1, 0, 6, Network interface: <ipaddress>192.168.63.1</ipaddress>, subnetmask <subnetmask>255.255.255.0</subnetmask>
2019-09-09T08:48:58Z, 0x00000018, 1, 0, 4, Network interface <interface>ether 5</interface> at router <instance>2</instance> registered
2019-09-09T08:48:58Z, 0x00000018, 1, 0, 1, Setting router <instance>2</instance> address to <address>(0001)</address>
2019-09-09T08:49:04Z, 0x00000007, 1, 0, 6, Network interface: <ipaddress>169.254.185.103</ipaddress>, subnetmask <subnetmask>255.255.0.0</subnetmask>
2019-09-09T08:49:04Z, 0x00000018, 1, 0, 4, Network interface <interface>ether 4</interface> at router <instance>3</instance> registered
2019-09-09T08:49:04Z, 0x00000018, 1, 0, 1, Setting router <instance>3</instance> address to <address>(0000:b967)</address>
2019-09-09T08:49:13Z, 0x00000111, 2, 0, 2, !!!! Warning: Duplicate IP detected. Skipping second one.
2019-09-09T08:49:46Z, 0x00000001, 1, 0, 0, runtime licensed

In the Shutdown_Signal event:

Process List of co* : In Shutdown_Event
   37 ?        00:00:00 kcompactd0
   69 ?        00:00:00 mmc_complete
   73 ?        00:00:00 ext4-rsv-conver
   75 ?        00:00:00 ipv6_addrconf

Something has caused the Codesys process to close.

Codesys Log File
2019-09-09T08:48:43Z, 0x00000071, 1, 0, 0, **************************************************************
2019-09-09T08:48:58Z, 0x00000007, 1, 0, 6, Network interface: <ipaddress>192.168.63.1</ipaddress>, subnetmask <subnetmask>255.255.255.0</subnetmask>
2019-09-09T08:48:58Z, 0x00000018, 1, 0, 4, Network interface <interface>ether 5</interface> at router <instance>2</instance> registered
2019-09-09T08:48:58Z, 0x00000018, 1, 0, 1, Setting router <instance>2</instance> address to <address>(0001)</address>
2019-09-09T08:49:04Z, 0x00000007, 1, 0, 6, Network interface: <ipaddress>169.254.185.103</ipaddress>, subnetmask <subnetmask>255.255.0.0</subnetmask>
2019-09-09T08:49:04Z, 0x00000018, 1, 0, 4, Network interface <interface>ether 4</interface> at router <instance>3</instance> registered
2019-09-09T08:49:04Z, 0x00000018, 1, 0, 1, Setting router <instance>3</instance> address to <address>(0000:b967)</address>
2019-09-09T08:49:13Z, 0x00000111, 2, 0, 2, !!!! Warning: Duplicate IP detected. Skipping second one.
2019-09-09T08:49:46Z, 0x00000001, 1, 0, 0, runtime licensed
2019-09-09T08:49:54Z, 0x00000018, 1, 0, 5, Network interface <interface>ether 5</interface> unregistered
2019-09-09T08:49:54Z, 0x00000018, 1, 0, 5, Network interface <interface>ether 4</interface> unregistered
2019-09-09T08:49:54Z, 0x000010f0, 1, 0, 1, <NetworkName>eth0</NetworkName><IPAddress>0.0.0.0</IPAddress><Subnetmask>0.0.0.0<Component>IoDrvEthernet</Component>

The log file only reported "unregistered" of ethernet interfaces. I assume this is because the ethernet ports are powered down in UPS Alert state. Could this cause Codesys to close abruptly?

Recent posts to Codesys runtime break Python Scripts

Codesys runtime break Python Scripts

Codesys runtime break Python Scripts

Codesys runtime break Python Scripts

Codesys runtime break Python Scripts

Codesys runtime break Python Scripts

Codesys runtime break Python Scripts

Codesys runtime break Python Scripts

Codesys runtime break Python Scripts

Codesys runtime break Python Scripts

Codesys runtime break Python Scripts