Activity for eschwellinger
-
eschwellinger posted a comment on discussion Runtime 🇬🇧
ok now it is clear - this is a single core Pi Zero W. For this device there is no edge device available. But just for working with CODESYS it is not really needed and yes plc runs only for 2h unlicensed.
-
check 'uname -a' by ssh connection - addtional you'll probaly find the reason for not running with application by 'cat /var/opt/codesys/codesyscontrol.log' incase you are using 4.9.0.0 runtime version
-
SPI enabled on 'sudo raspi-config' reduce _diMaxSpeed
-
Think just add some CANopen Slaves and end resistors - then it will work ;-)
-
CODESYS runtime version 4.9.0.0 for your Pi. ssh user should be pi. This is for RasperrPi Os 32 bit. If you are on RasperryPi OS 64Bit use Arm 64bit SL product as Runtime.
-
CODESYS runtime version 4.9.0.0 for your Pi. ssh user should be pi.
-
please use latest version 4.9.0.0 and it is mandatory to have a user pi on your device.
-
I fear you need to update if you need a solution for this.
-
I fear you need to update if you neef a solution for this.
-
will start with next relaese on RTE, at the moment not possible.
-
see here:
-
Give CODESYS Automation Server a try!
-
Add existing version (with SM drive) - without scan - disable under expert settings in the slave the revision check.
-
this is a security issue not to read/write in the plc allowed path I would recommend to update and change the path in the application were the files are😏
-
this is a security issue not to read/write in the plc allowed path I would recommend to update and change the path in the application 😏
-
Since 1.31.0.0 version there is this really helpful feature to browse the plclogs remote via CODESYS Automation server:
-
https://store.codesys.com/en/codesys-automation-server-connector.html Programming System CODESYS Development System V3.5.15.0 or higher
-
Guess you could just add two modbus slaves with the same ip, to enlarge the 10 channel limit.
-
think this will be solved with 4.3.0.0 version.- sorry i was wrong with this..4.4.0.0
-
Hi Rossano, thank you for the feedback, you are right this need to be changed in the faq section. Regards Edwin
-
I've send out a workaround for this.. Best Regards Edwin
-
check this faq section here: https://faq.codesys.com/plugins/servlet/mobile?contentId=102137886#content/view/102137886
-
just open http://localhost:8080 in Chromium then it will show the webvisu ( sure you need to this in your CODESYS Application)
-
is there a way to check the plclog on Opus A3 by using cmd line under Linux? This log is what you need to check for the disconnection problem
-
you need to use 'my question ' in the CODESYS store
-
/var/opt/codesys/PLCLogic as soon you have dowloaded the project to the Pi it will run the bootapplication no connection to the pc is needed anymore
-
/var/opt/codesys/PLCLogic as soon you have dowloaded the project to the Pi it will run the bootapplication no connection tontge pc is needed anymore
-
depends on if you use PFC200 SL from CODESYS store or the Wago target for the PFC. If you use the SL product you need to setup the interface by a plcshell command...
-
Installier bitte doch mal das Edge Gateway auf dem Pi mit und scan dann ueber dieses. Im Codesys Projekt hast du schon den Pi MC im Gerätebaum ? nicht den Pi Sl ?
-
installier doch mal das Edge Gateway au dem Pi mit und scan dann ueber dieses und im Codesys Project hast du schon den Pi MC im Geratebaum ? nicht den Pi Sl ?
-
because of security reason it is not allowed anymore to access files outside the IEC accsible path.
-
use the PLClogic directory to read / write files. /var/opt/codesys/PLClogic/ this is due security reasons forced to use.
-
I would recommend to add your one wire path here: [SysFile] FilePath.1=/etc/, 3S.dat IecFilePath.1=/proc/, cpuinfo IecFilePath.2=/proc/, iomem IecFilePath.3=/mnt/1wire/temperatur PlaceholderFilePath.1=/sys/devices/w1_bus_master1, $OneWire$ PlcLogicPrefix=1 instead of changing the ForceIecFilePath setting
-
check the plc logger and the axis stucture & what about quickstop Bit5 in the statusword?
-
which Softmotion driver do you use? the generic DS402 or the drive specific ( which is recommended)? please show us the device tree.
-
remove the cifx kernel module..check the plc logger are the next steps
-
you need to add in: /etc/CODESYSControl_Users.cfg [ComponentManager] Component.1=SysPci Component.2=CmpHilscherCIFX then execute in the linux cmdline: lspci if you get: "Kernel driver in use: netx" -> this is a problem please remove it by modprobe -r netx or rmmod netx
-
CODESYSControl.cfg die Sektion entfernen und CODESYSControl_User.cfg folgendes einfügen: [SysCom] Linux.Devicefile.1=/dev/ttyAMA0 dann gehts als Com1 in CODESYS!
-
..einzelne Scheiben des Wago Slaves dürfen nicht fehlen - der ganze Slave schon - entwedcer also über "optional Slaves" (Setting im Slave) dann mußt du aber Alias Adressen zwingend setzen oder aber Abzweige Beckhoff EK1110 könntest du verwenden um eben auch Teile der Anlage "Optional" zu machen.
-
man kann nur echte Slaves disablen/enablen, beim 750-354 ist ja nur der Kopf ein Ethercat Slave, die einzelnen Scheibchen sind KBus keine Ethercat Slaves , daher gehts das mit diesen nicht.
-
this is a new/other issue: https://faq.codesys.com/pages/viewpage.action?pageId=153321520 should fix it & will be solved with 4.9.0.0 release
-
welche version der runtime verwendest du - das script wird als 'root' ausgeführt..
-
welche version der runtime vwerwendest du - das script wird als 'root' ausgeführt..
-
just select the device in the CODESYS device tree - then rightclick on that and execute 'update device' to current/proposed version - if you are using CODESYS Development System 64Bit - change the Control Win to Control Win x64 to be able to login to your local Control Win x64 instance (start your plc in the tasktray - then scan it and login to it)
-
Guess not there should be a network card which is capabale for using with Control RTE ( Intel chipset etc) in that case you need to install a CODESYS driver unter windows for the networkcard which should do the Ethercat communication..
-
use either the CODESYS Installer and install IIoT libraries or download the IIoT libs here: https://store.codesys.com/en/codesys-iiot-libraries-sl.html (csv is part of this bundle)
-
no need to add anything in CODESYSContro.cfg (Communication already works - just waiting for dc sysnc state 80) the remaining problem is - that Control Win is not capable for SoftMotion & Ethercat with distributed clocks enabled. I would switch to Control RTE (latest version) as Target plc system.
-
write to my question in CODESYS store please
-
https://faq.codesys.com/pages/viewpage.action?pageId=153321520 should fix it
-
for a test disable under expertsettings the revision check - then contact the drive manufacturer (if your Soft Motion version is latest)
-
you need to change the drive in the device tree to the existing driver for this drive - I would not use the generic DS402 if a driver is available. See screenshot.
-
you need to change the drive in the device tree to the existing driver for this drive - I would not use the generic DS402 if a driver is available. See screenshot.
-
https://store.codesys.com/en/codesys-softmotion-sl-bundle.html Softmotion SL
-
please write to 'my question' in the CODESYS store -
-
I would recommend to ask the Wago support 😄 in that case.
-
I would use a CODSYS Gateway on remote side if possible.
-
https://store.codesys.com/de/codesys-opc-da-server-sl-demo.html
-
you need to buy the demo license 0€ or full licence in the CODESYS store , then you'll get a license number which you need to activate by licence.codesys.com (on the machine where the DA. server run)
-
use my 'question' in the CODESYS store..
-
this is not a known, which version of csvreader is it? Possible that you are using not latest version?
-
if you call the amixer command via CODESYS?
-
google for 'amixer' cmd under linux
-
which runtime & version are you using?
-
I do it for example on a Wago Touchpanel 600 that way: (Play sound) IF xTest OR PLC_PRG.xAlarm THEN //SysProcess.SysProcessExecuteCommand('aplay /var/opt/codesys/alarm1.wav', ADR(Result)); SysProcess.SysProcessExecuteCommand('aplay /var/opt/codesys/PlcLogic/Application/alarm1.wav', ADR(Result)); xTest := FALSE; END_IF
-
it depends on - if needed contact store-support@co...
-
Wenn ich das richtig verstehe, versuchst du ein Projekt das SIL2 enthält auf einen PFC zu laden, aber das kann nicht funktionieren, weil der PFC kein SIL2 unterstützt.
-
Without ESI file no chance to use the drives.
-
I would try to contact them here: http://liftcontrolsystem.com/16-1-2-ac-servo-drive-ik3-series.html
-
i would try to xo takt them here: http://liftcontrolsystem.com/16-1-2-ac-servo-drive-ik3-series.html
-
Hallo Andre, das ist halt alles nicht so einfach, ich versuchs mal zu erklären. So generell funktioniert dieser Retain Mechanismus eigentlich nur wenn man auch ne USV hat also die Runtime und das OS korrekt herunterfährt! So ist das ganze designed. (die Runtime selber schreibt das Retain file beim beenden und läd das Retain File beim starten) Das was ihr/Tutorial da tut ist eigentlich ein Workaround um das verwenden einer USV zu umgehen. (also manuell das File schreiben und auch wieder herstellen)...
-
Hallo Andre, das ist halt alles nicht so einfach, ich versuchs mal zu erklären. So generell funktioniert dieser Retain Mechanismus eigentlich nur wenn man auch ne USV hat also die Runtime und das OS korrekt herunterfährt! So ist das ganze designed. (die Runtime selber schreibt das Retain file beim beenden und läd das Retain File beim starten) Das was ihr/Tutorial da tut ist eigentlich ein Workaround um das verwenden einer USV zu umgehen. (also manuell das File schreiben und auch wieder herstellen)...
-
wird auch mit 4.9.0.0 behoben - Workdaround wäre die Onewire Filepfade einzutragen: in /etc/CODESYSControl.cfg [SysFile] .. .. IecFilePath.1=/proc/, cpuinfo IecFilePath.2=/proc/, iomem PlaceholderFilePath.1=/sys/devices/w1_bus_master1, $OneWire$ ..
-
ja genau, das wird mit 4.9.0.0 Release dann behoben das man das nicht mehr eintragen muss.
-
ja geht, welche runtime version verwendest du?
-
you could try 2 things: 1. install the EdgeGateway from CODESYS store on the RTE side add a new Gateway in CODESYS - name of RTE or IP then use this to login to the RTE 2. use the CODESYS network driver on the Interface which you login on RTE.(means install the driver on Windows device manager) - RTE pc side
-
if you are using PFC200 SL from CODESYS Store add Kbus Connector in the device tree - dowload the application - rightclick - scan the Kbus slices in Stop mode of the plc. ( keep in mind 'end terminal' for kbus is mandatory to have)
-
add a pou - 'structured text' and call it in your task
-
plc always execute bootproject and runs without doing anything additional.. if not check the plc logger
-
check again with 'top' if the runtime runs with the setting..it will i'm sure. then add new Gateway in CODESYS with the the IP of your PI an scan via this new added Gateway
-
check again with 'top' have if the runtime runs with the setting..it will i'm sure. then add new Gateway in CODESYS withe the IP of your PI an scan via this new added Gateway
-
not needed to add anything in the config file. winpcap 4.3.1 or use SP19 runtime and npcap
-
if it shows a 64bit kernel as result add with sudo nano /boot/config.txt arm_64bit=0 after reboot it should work https://faq.codesys.com/pages/viewpage.action?pageId=153321520
-
if it shows a 64bit kernel as result add with sudo nano /boot/config.txt arm_64bit=0 after reboot it should work
-
no only the gateway is up and running.. could you do a 'uname -a'?
-
no only the gateway is up and running.. could you do a 'uname -a'
-
no only is up and running.. could you do a 'uname -a'
-
no only is up and running.. could you do a uname -a
-
could you login to the Pi by ssh and check 'top' see if gateway and runtime are up and running...
-
Profinet I think 1ms Ethercat < 1ms ( if your slaves support this)
-
...wenn es ein PI4 HW Version 1.5 ist musst du 4.8.0.0 runtime version verwenden.
-
I think the only way is using on the IPC: https://store.codesys.com/de/codesys-safety-for-ethercat-safety-module-for-el6900-sl.html
-
Hi, could you please give 4.8.0.0 version a try? (Current version) Regards Edwin
-
Isn't in DS402 CANopen Spec Homing-Done-Bit Bit 12 - this might be your problem - check this with your drive manufacturer
-
Retain/Persistent variables work that way: On exit/shutdown for the runtime - these retain variables will be saved to a retain file. On startup of the runtime they will be restored from that file. If you have no UPS connected how should this work on just switching off the Raspberry Pi? - there are only two options 1. use a UPS (which makes the whole Pi more robust against SD card corruption 2. an other option might be to use persistence manager from application composer (https://content.helpme-codesys.com/en/CODESYS%20Application%20Composer/ac_pm_overview.html)...
-
does setting from application work?
-
which device? are they written on graceful shutdown?
-
think this will be solved with 4.3.0.0 version.
-
think this will be solved with next 4.3.0.0 version..
-
which device and which version? use pcload in the plcshell toi check the load on your device...
-
bitte mal: tail -f /tmp/codesyscontrol.log ausführen und mit dem Update Tool die SPS starten.. hier müsste man dann sehen welches Problem die Runtime hat in dem SPS log