wago/pfc-firmware

This repository contains official Wago firmware releases for 750-8xxx(PFC) series.

How to install:

WAGO recommends exclusive use of original WAGO SD cards, as the new firmware has been tested and released based on these cards. If using cards other than WAGO, WAGO cannot guarantee and take responsibility for proper functioning of the controller/coupler.

Installation

1. Delete full content of the card with tools like "DiskPart" or any other, google is your friend:)
2. Write image on the WAGO SD card with "Win32DiskImager" Download
3. Plug-in the WAGO SD card first before booting the PFC100/200.
4. Connect the Wago Servicecable between PC and PFC100/200. This is needed since a factory-image PLC is set to use DHCP and therefor has no fixed IP address.
5. Adjust the static IP address with "Wago Ethernet Settings".
6. Due to changes in the WebBasedManagement (WBM), make sure to delete the full browser cache (!) and restart the browser after.
7. Open "WebBasedManagement / Administrations – Menue / Create Image // Create bootable image from active partition (SD) // Start Copy".
8. WAGO Ethernet settings is at least required in version 6.8.2.2. Download

pfc-firmware's Issues

Expose known issues to GitHub

When looking at the releasenotes, I see WAT-xxxx numbers, with fixes.

Please expose these issues here in the github Issue tracker.

eg.
"[FIXED] WAT33412 Fix temporary network loop/network bridge within the FW update process, if the network is separated and connected to more than one network"

It is not clear from the fixed msg, where/when this was a problem. Just spend 4 days trying to debug a problem with a firmware 14 and separated networks.

FW19 (03.07.14) is not yet available in this repository

but it is on this website https://www.wago.com/de/d/6599873

WAGO Ethernet settings download link seems to be broken

When you follow the link it says no items available

When will CODESYS V3 for PFC100 follow?

As stated in the title: When is it planned to migrate PFC100 controllers away from e!Cockpit?

We use both, PFC200 and PFC100, and it's a little costly to maintain both environments now.

Feature Request: Allow domain-names in NTP config

Hi there

I hope i'm in the right place here to drop a feature request. If not, feel free to move this issue whereever it belongs.

All NTP-clients that I know support domain names as ntp server address. However, for some reasons, wbm-config does only allow IPs. I think, domain names are much more reliable in the long shot, as it allows to use a server pool like ntppool.org. Are there any chances, that future version will allow this?

Setting the status code of a node to "bad" through OPCUA doesn't work

When setting up variables in WAGO's eCockpit, they have the StatusWrite bit disabled in their OPCUA node's AccessLevel. This means that when trying to set the StatusCode of the value to any other value than Good, the server answers with the following error:

0x80730000 (BadWriteNotSupported): The server does not support writing the combination of value, status and timestamps provided.

We haven't found any way to change this AccessLevel.

Here is a small python script that can be run to trigger the error :

import asyncio
from datetime import datetime

from asyncua import Client, ua  # type:ignore


async def main():
    client = Client("opc.tcp://ip_of_the_wago_device:4840")
    await client.connect()
    params = ua.WriteParameters()
    attr = ua.WriteValue()
    attr.NodeId = ua.NodeId.from_string("ns=4;s=|var|WAGO 750-8212 PFC200 G2 2ETH RS.Application.GVL.BESS_WATCHDOG_FEEDBACK")
    attr.AttributeId = ua.AttributeIds.Value
    attr.Value.Value = ua.Variant(42, ua.VariantType.UInt16)
    attr.Value.SourceTimestamp = datetime.now()
    attr.Value.StatusCode = ua.StatusCode(ua.StatusCodes.Bad)
    params.NodesToWrite.append(attr)
    write_results = await client.uaclient.write(params)
    for status_code in write_results:
        status_code.check()


if __name__ == "__main__":
    asyncio.run(main())