Codesys 3.5.17 on Wago PFC200

DCJarle
2022-01-05
2022-01-07
  • DCJarle - 2022-01-05

    I am trying to get a PFC200 to run on codesys.

    I am able to add the internal bus and the device is shown as active, but when I go to the bus it's status says PFC200Bus: Not running.
    I seem to be able to compile and download programs, but IO interactions wont work.

    When scanning for connected devices i get a kbus error.
    There also a could not create directory /var/run/codesyscontrol/ error.

    Setup:
    pfc200 8212 fw 03.07.14(19) runtime V4.3.0.0
    CODESYS Sp17 Patch 2

    Any suggestions on how to solve this?

     
  • eschwellinger

    eschwellinger - 2022-01-05

    Is it possible that you are missing the end terminal on k-bus?
    740-600 is mandatory to have connected

     

    Last edit: eschwellinger 2022-01-05
  • DCJarle - 2022-01-06

    Can confirm that i have a 750-600 end module connected. I had everything running fine with e!Cockpit before i decided to try codesys.

     
  • DCJarle - 2022-01-06

    Update:
    I removed some of my IO modules, so that i was left with only a 750-1506 and and the end-terminal.
    This got the program running. Will do some more testing to see if one of the modules are faulty.

    I do however still get the could not create the directory error.

     
  • eschwellinger

    eschwellinger - 2022-01-06

    never seen this error - could you check if enough space is left on your PFC ... login by ssh and 'df'.
    and check if the eCockpit runtime is disabled by WBM

     
  • DCJarle - 2022-01-06

    So i got all IO modules connected and PLC online. PLC might have some conflict with e!cockpit since it was running that, before i switched. At least it works now.

    Not able to see anything about e!Cockpit in wbm, since swaping to codesys 3.5.

    Storage does not seem to be full.
    df returns:

    Filesystem           1K-blocks      Used Available Use% Mounted on
    /dev/root               292251    113365    159277  42% /
    devtmpfs                250420        60    250360   0% /dev
    none                    250932        72    250860   0% /tmp
    none                    250932         0    250932   0% /media
    none                      4096       128      3968   3% /var/log
    none                    250932       100    250832   0% /var/run
    none                    250932         0    250932   0% /var/lock
    none                    250932         0    250932   0% /var/tmp
    none                    250932         0    250932   0% /sys/fs/cgroup
    tmpfs                   250932       112    250820   0% /run
    /dev/mmcblk0p1        30638016    616492  28442160   2% /media/sd
    /dev/mmcblk1p1           16334      2774     13560  17% /boot/loader
    /dev/mmcblk1p9         1514352    234284   1185092  17% /home
    /dev/mmcblk1p6            5915        41      5373   1% /settings
    /dev/mmcblk1p5            5915        49      5365   1% /log
    none                    250932       100    250832   0% /var/run/netns
    /dev/mmcblk0p1        30638016    616492  28442160   2% /media/sd/docker
    root@PFC200V3-4DB391:~ ll
    drwx------    3 root     root          1024 Dec  6 21:30 .
    drwxr-xr-x   19 root     root          1024 Jan  6 15:45 ..
    -rw-------    1 root     root           638 Jan  4 10:54 .bash_history
    drwx------    4 root     root          1024 Dec  6 21:30 .config
    -rw-------    1 root     root            35 Aug 11 21:56 .profile
    

    Should i try to create the folder manually as root?

     

    Last edit: DCJarle 2022-01-06
  • eschwellinger

    eschwellinger - 2022-01-06

    hm..you still see this message in the logger?

     
  • DCJarle - 2022-01-07

    Yes the error is still there.

     

Log in to post a comment.