Activity for eschwellinger
-
eschwellinger modified a comment on discussion Engineering 🇬🇧
but there is no difference on license if you start manually or automatically.. so it should run more then 2h and which system i s it - Linux SL oder Raspberry Pi...or?
-
but there is no difference on license if you start manually or automatically.. so it should run more then 2h
-
Hallo, kannst du bitte dich mit ssh (Putty oder sowas) auf dem PFC einloggen und dann tail -f /var/opt/codesys/codesyscontrol.log ausführen und dann dich einloggen - dann müsstest du "live" sehen welche Loggermeldungenkommen wenn CODESYS rausfliegt. Denke das bringt uns weiter.
-
ja genau die RTE ist fur Industrie PCs. Denke du musst bei Festo nachfragen.
-
Control Win die du verwendest unterstütz das nicht, du müsstest Control RTE im CODESYS Store runterladen und verwenden, die kann das und das entspricht dann dem Twincat system was du hier vergleichst.
-
could you check if reading by cli does work? no changes on OS side?
-
https://forums.raspberrypi.com/viewtopic.php?p=2093006#p2093006 this is caused by the upgrade - Workaround is: add in /boot/config.txt arm_64bit=0
-
hm -> Ip change not allowed - means you have not set your Windows Adapter name in the configuration file c:\ProgramData\CODESYS\CODESYSControlWinV3x64\xxxxxx\CODESYSControl.cfg [SysSocket] Adapter.0.Name="Ethernet" Adapter.0.EnableSetIpAndMask=1 Then next step is to scan the PN device on the PN Controller to have the same IO sizes/configuration it would say.
-
Since 3.5.19.0 we recommend NPCap please uninstall Win10Pcap. Then it will work on Control Win and for the other device you need: https://content.helpme-codesys.com/en/CODESYS%20PROFINET/_pnio_runtime_configuration_device.html the syssocket setting in the config file on windows and Control Win disable the firewall to bring it up and running.
-
Since 3.5.19.0 we recommend NPCap please uninstall Win10Pcap. Then it will work on Control Win
-
you could set the placeholder to emtpy as solution (beside updating the runtime version):
-
you could set the placeholder to emtpy as solution:
-
...dann müsste er auch mit aktuellem Image funktionieren. sudo apt-get upgrade sollte man nicht machen aktuell dann gehts nimmer.
-
auf dem 3B ist wohl das dein Problem: https://forge.codesys.com/forge/talk/Runtime/thread/747b95a7ba/#784a PI4 nur wenn es die ganz neue Hardware version ist musst du auf 4.8.0.0 warten -> nächste Woche Release: https://de.codesys.com/das-system/codesys-release-plan.html
-
auf dem 3B ist wohl das dein Problem: https://forge.codesys.com/forge/talk/Runtime/thread/747b95a7ba/#784a
-
you need to install the CODESYS networkdriver: https://youtu.be/10oj4wABaKc this will solve it
-
for PI4 you need 4.8.0.0 runtime version in case it is the new hardware revision.
-
for PI4 you need 4.8.0.0 runtime version in cast it is new revision.
-
wenn du dich nicht mehr ssh einloggen kannst um zu untersuche wo das Problem liegt, musst du denke ich leider einen Monitor (über HDMI) und Tastatur anschließen und lokal schauen ob und was das Problem ist..! Wie gesagt ich kann es fast nicht glauben (den Logs nach zu urteilen) das es CODESYS sein soll.. Welche Einträge meinst du mit "Mich machen im Log die Einträge mehrere Stunden bevor der Absturz kommt stutzig" Die Modbus Einträge?
-
Hi, ich würde vorsichtig behaupten das es kein CODESYS Problem ist, die Log sagen nichts von einem Absturz oder sonstigen Problemen. Wenn du per ssh nicht mehr drauf kommst, würde ich meinen ist das was eher was PI OS bedingtes. Also paar Fragen: - Netzteil stark genug? - Was läuft sonst noch auf dem PI?
-
Hi, not 100% sure, but I guess this happens only in case you ugrade an existing Bullseye to current version by sudo apt-get upgrade, see here: https://forums.raspberrypi.com/viewtopic.php?t=349291 the solution/workaroundn is: 1. Use a new flashed Bullseye -> February release 2. or add in /boot/config.txt arm_64bit=0 and reboot
-
You need to ask the Beijer support for this -
-
sorry - it turned out that it seems to be a problem in the EthercatMaster on mapping the pdo's The workaround is to use Ethercat master version 4.2.0.0 - should be solved then with 4.5.0.0 release -> scheduled for: https://de.codesys.com/das-system/codesys-release-plan.html 26.4.23
-
sorry - it turned out that it seems to be a problem in the EthercatMaster on mapping the pdo's The workaround is to use Ethercat master version 4.2.0.0 - should be solved then with 4.5.0.0 release.
-
If you use MC_Power in the Motiontask (execute it below EthercatMaster) does it work to enable? @ I would for a test go back to 4.11.0.0 to check if the config mode works in there. I expect that it is not SP19 related it is more SM version related
-
If you use MC_Power in the Motiontask (execute it below EthercatMaster) does it work to enable? @ I would for a test go back to 4.11.0.0 to check if the config mode works in there. I expect that it is not SP19 related it is more SM version relatated
-
If you use MC_Power in the Motiontask (execute it below EthercatMaster) does it work to enable?
-
If you use MC_Power and in the Motiontask (execute it below EthercatMaster) does it work to enable?
-
please attach the project this should work!
-
this does only work on non modular slave devices, your slaves is basically only one Ethercat slave (modular extension are non ethercat slices)
-
sudo /etc/init.d/codesyscontrol stop sudo /etc/init.d/codesyscontrol start
-
Are you sure that the runtime is still up and running? check with ssh and 'top'. If so I would install the edge gateway on your PI and add this to CODESYS..as Gateway 2 and try to license that way.
-
Beispiel: [SysSocket] sysLog.IPAddress=192.168.100.0 sysLog.Port=514
-
if you use current version this should be solved ( working with PI and SPI) all others: https://faq.codesys.com/pages/viewpage.action?pageId=128253958
-
Hallo David, ich würde so vorgehen: Nachdem nachgewiesen wurde, dass es sich nicht um ein Checkbounds-Problem handelt (in IEC oben), https://faq.codesys.com/pages/viewpage.action?pageId=3538982 würde ich empfehlen, in solchen Fällen auf der SPS-Seite wie folgt vorzugehen: Anmeldung per ssh-Client (oder lokal auf der PI) Runtime stoppen 1.sudo /etc/init.d/codesyscontrol stoppen cd /var/opt/codesys sudo /opt/codesys/bin/codesyscontrol.bin -d /etc/CODESYSControl.cfg Öffnen Sie eine zweite ssh-Verbindung...
-
Hallo David, ich würde so vorgehen: Nachdem nachgewiesen wurde, dass es sich nicht um ein Checkbounds-Problem handelt (in IEC oben), https://faq.codesys.com/pages/viewpage.action?pageId=3538982 würde ich empfehlen, in solchen Fällen auf der SPS-Seite wie folgt vorzugehen: Anmeldung per ssh-Client (oder lokal auf der PI) Runtime stoppen 1.sudo /etc/init.d/codesyscontrol stoppen cd /var/opt/codesys sudo /opt/codesys/bin/codesyscontrol.bin -d /etc/CODESYSControl.cfg Öffnen Sie eine zweite ssh-Verbindung...
-
if this is a Pi4 Rev 1.5 this will be solved with 4.8.0.0 version
-
anything here? /tmp/codesyscontrol.log open second CLI tail -f /tmp/codesyscontrol.log while it stops?
-
which versions are involved? (Runtime and CODESYS version is always needed as additional information): In such cases I would recommend the following: stop the plc runtime by login by ssh to the pi(or exceute this local): 1. sudo /etc/init.d/codesyscontrol stop start the runtime manually by command line to have the debug output (for non multicore runtime) cd /var/opt/codesys sudo /opt/codesys/bin/codesyscontrol_armv6l_raspberry.bi -d /etc/CODESYSControl.cfg in case of multicore runtime use: cd /var/opt/codesys...
-
wenn du mal für einen Versuch zuerst das Extension Package über den Installer installierst? Weil das ist schon verfügbar..
-
Es wird kein weiterer Port benötigt. Es könnte aber sein, dass Windows bzw. .NET versucht ein fehlendes zwischenzertifikat zu laden, was aber über eine URL gemacht wird. Könntest du uns die Fehlermeldung schicken, vielleicht hilft das weiter.
-
either wiring or end resistor on RS485
-
PFC side is ok, check your slave side..copy the slave name to the watch window to see the diagnosis of the fb
-
https://deployment.codesys.com & Port 443 für HTTPS
-
https://deployment.codesys.com & port 443 für HTTPS
-
If you are on PFC200 SL in the plcshell + restart the device
-
why not just use Webvisu in fullscreen kiosk mode in the browser, this is what most of the users are doing in that case
-
isn't this the same like with Modbus tcp? https://faq.codesys.com/pages/viewpage.action?pageId=24510480
-
thanks for the feedback!
-
Example for doing this ( I assume you have connected a USB serial device for this example) etc/CODESYSControl_Users.cfg [SysCom] Linux.Devicefile.1=/dev/ttyUSB0
-
Example for doing this ( I assume you have connected a USB serial device for this example) etc/CODESYSControl_Users.cfg code [SysCom] Linux.Devicefile.1=/dev/ttyUSB0 code
-
here
-
here
-
Check Drive.fbeFBError in the watch window for the error history.
-
use: https://store.codesys.com/de/codesys-control-for-linux-arm-sl-bundle.html if AM335x or AM57x depends on your application needs - how many axis, which size ha the application etc For EtherCAT with SoftMotion a realtime patch is needed on your Linux (rt_preempt) Would recommend to start with Debian based (at least Debian package management is needed)
-
yes and yes 👍
-
From my experience, this is usually a low level problem, can mini driver loses messages.. as soon you have higher load on CANbus. ( This is not a problem of the CANopen Manager)
-
thanks for the feedback & information, we try to support the Rev1.5 with the next release
-
could you give the result of 'ifconfig -a' and 'cat /proc/cpuinfo'
-
could you give the result of 'ifconfig -a'
-
no, why not just check the license.. attached example: https://content.helpme-codesys.com/en/LibDevSummary/deployment.html
-
no, why not just check the license.. attached example: https://content.helpme-codesys.com/en/LibDevSummary/deployment.html
-
check what happens if you start the runtime manually by sudo /etc/init.d/codesyscontrol stop then cd /var/opt/codesys sudo /opt/codesys/bin/codesyscontrol_armv7l_raspberry.bin -d /etc/CODESYSControl.cfg for the multicore runtime for the SL (without MC ) runtime: cd /var/opt/codesys sudo /opt/codesys/bin/codesyscontrol_armv6l_raspberry.bin -d /etc/CODESYSControl.cfg
-
reduce SPI Maxspeed in the CODESYS config.
-
Is that current version? Bullseye?
-
Use CmpEt1000Drv and install the CODESYS network driver in the Windows device manager
-
Hi, for me it works that way on br1 and with separated interfaces. If you let CODESYS change the IP Adress you need additional: [SysSocket] Adapter.0.Name="br1" Adapter.0.EnableSetIpAndMask=1 added in /etc/CODESYSControl_Usr.cfg ( then you could enable the setting 'Adjust operating system setting'
-
seperate the ethernet interfaces (wbm) on PFC200 use the br1 on the controller
-
seperate the ethernet interfaces on PFC200 use the br1 on the controller
-
guess you need to use current version 3.5.18.40
-
Is it really latest runtime 4.7.0.0?
-
add the following entry in /etc/CODESYSControl_Usr.cfg [SysMem] Linux.Memlock=0
-
mach mal diesen Eintrag ins /etc/CODESYSControl_Usr.cfg [SysMem] Linux.Memlock=0
-
I would recommend to ask Weintek.
-
..for me it works like charm
-
you need to add the project - to check Guess you missed to set your attributs
-
would be great if you report this to my question - bug report
-
yes, just activate the license on the key and the Pi which has the usb key plugged is then licensed...
-
you have the following options: 1. Use the USB KEY (https://store.codesys.com/de/catalogsearch/result/?q=KEY) - probably most convenient 2. Use the license backupfile to reactivate the softlicense like mentioned in the faq 3. Use CODESYS Automation Server - no need to travel to the plant - just do it from your office ( reactivation of the softlicense - what ever is needed to do - login by CODESYS - or open the visualization Many users have a license on the key if they have several plc's ( in one...
-
https://faq.codesys.com/pages/viewpage.action?pageId=1310825 with the update file you could restore the license whenever it is needed on the same Pi
-
https://faq.codesys.com/pages/viewpage.action?pageId=1310825 with the update file you could restore the license whever it is needed ont the same Pi
-
please unselect the "Multitouch-Bedienung"
-
Hi, This is not really new and really not experimental - years available. I would recommend in any case to use the 64Bit version- we are sure most of the User are on 64Bit version, except a special Plugin force you to use 32Bit (V2.3Converter for example) 64Bit has advantages on huge projects as you already mentioned.
-
versionen? wie ist das Overlay settig? Mach mal an..
-
I would give this a try to remove...
-
on BeagleBone for sure solution is to update to 4.7.0.0 version, for this memory leak problem.
-
dmesg | grep -i tty
-
agree, not really clear at least this should be clear stated in the Linux SL product.
-
This is not available, the only way is to use Webvisu and start your system in fullscreen kiosk mode in a browser. Boot into that and execute: 'http://localhost:8080'
-
EtherCAT_Master2.xError usw sonst greifst du ja in die falsche Instanz.
-
du musst die Slave Instanzen aufrufen, bitte keine neue Slave Instanzen anlegen (in deinem Deklarationsteil) dann gehts: Also im Programm einfach die Slaves so aufrufen wie diese im Gerätebaum heißen Beipiel: EK1100(); EL1004(); usw
-
...diese version deinstallieren und die offizielle aus dem CODESYS Store verwenden: https://store.codesys.com/de/oscat-basic.html nicht die Version 3.31
-
du musst den CODESYS Installer verwenden um Packages zu installieren: "c:\Program Files (x86)\CODESYS\APInstaller\APInstaller.GUI.exe"
-
check with 'dmesg'
-
nein alles gut...du musst so vorgehen: 1. SD neu flashen 2. alte runtime (4.4.0.0 am besten) nochmal drauf und damit Lizenz reaktivieren 3.dann lizensierte Rutime updaten auf aktuelle Version
-
nein alles gut...du musst so vorgehen: 1. SD neu flashen 2. alte runtime nochmal drauf und damit lizenz reaktivieren 3.dann lizensierte Rutime updaten auf aktuelle Version