Terminal Specific Control Mode Fails on PFC300-8302 With DALI-configurator 4

Hardware and Linux
1

Hello, I have a problem with my brand new PFC-300-8302, what i normal can do in the PFC200-8212, is for me impossible with this one. The thing is, when in Codesys have made a project, added the DALI 753-647 Kbus DALI module, setup all runtime, everything is fine, in RUN mode, when i am entering the DALI-configurator in “codesys mode” then i can connect, but nothing happens, either Addressing, Compare,Query diagnostic. Im used to be able to do this in the older PFC200. When i set the PFC300 in STOP AND logging off in codesys, then i can use the DALI configurator as wanted.
there is fine traffic on TCP/6626

  1. 753-647 is FW 24, upgraded the card, no difference.

  2. Codesys 3.5.19 Patch 7

  3. Libraries: WagoAppDALI 1.3.1.10, WagoSysKbusServices 2.0.2.3,
    WagoSysKbusTerminalControl 2.2.2.2

  4. Firewall is turned off for now.

  5. Tried to execute Daliconfigurator as /abmode , /csmode or standalone (i suspect that the params defines a REST API between the codesys for sync of data vars)

I know that the DALI configurator has some ways to communicate “standard Modbus”, “pfc200 modbus” and “mbx”, and the Configurator looks if the controller is a “PFC200” !! So is the Dali configurator not up to date with the PFC300, or am i overseeing some version mismatch?
The Log from the Linux is just telling me this on the picture, not what is causing trouble :wink: ?
image

2

UPDATE WAGO has answered, that this issue will be fixed in the next firmware for PFC300. until they made a IPK to install on the PFC300, that will fix this, im currently awaiting this IPK to test.