EPICs Communication broken in Windows 11

[GretchenSkellyZimmer]

I have a small test Labview VI that communicates with EPICs.  It has worked great on a Windows 10 host.  But it does not work in Windows 11.  Has anyone had a similar experience?  Any fixes?

[altenbach]

Can you define your use of the term "does not work"? Sounds very vague.

Same computer upgrade from W10 to W11? Different computer?

Same LabVIEW version and bitness?

Who wrote the VI? Is it plain LabVIEW or does it use e.g. drivers or DLLs?

Any error messages?

How does it "communicate"? (Serial, Ethernet, GPIB? Telepathy?, etc.)

[Bob_Schor]

What version of LabVIEW are you running?  Do you realize that going to Windows 11 means that almost all versions of LabVIEW are not compatible with Windows 11.  Does EPCs Communicaition have a WIndows version requirement?

Bob Schor

[rolfk]

EPICs is a network communication protocol similar in some ways to MQTT or RabbitMQ.

https://www.ni.com/en/shop/seamlessly-connect-to-third-party-devices-and-supervisory-system/introduc...

There exists a NI Toolkit for this https://www.ni.com/en/support/downloads/drivers/download.labview-epics-client-i-o-server.html#559049

It was part of the LabVIEW Datalogging and Supervisory Control Module but separated out as an individual download with above installer. However it is still very much limited to the original LabVIEW DSC Module restrictions and the according readme link refers to the LabVIEW 2020 Datalogging and Supervisory Control Module readme, as there was no individual readme created for this module.

Specifically you should assume following limitations:

- LabVIEW 32-bit only support

- official support for Windows 7 SP1, 8.1 Update 1 and Windows 10 (version 1909 or higher) only

Anything else may work or it may not.

That all said there is a good chance it might work on Windows 11 but being a network technology and the increased security restrictions in recent Windows versions and the fact that the installer does not know about such requirements in Windows 11 to be able to configure the necessary authorisations during installation, it may be actually more a firewall/permission issue than a technical compatibility issue. 

[GretchenSkellyZimmer]

altenbach,

Thanks for responding to my post.

Attached is an image of my scaled-down version of my 'Beacon' program.

I wrote this VI on a Windows 10 host; then created an executable and transferred it to the target Win11 host.

I am using Labview 2022 Q3 32-bit on an 64 bit OS.

The target host is a brand new Win11 PC.

error message?  see 2nd attached image.

How do I know its not working?  The 'flag' on the Beacon Indicator is red.

Plus, the Epics pv on the EPICs page is not updating.

Error −311118 is "Failed to connect to the MAX database (MXS) when deploying the EPICS Client I/O server."

This small test VI works fine on Windows 10 - also the executable works fine.

I have the Environment Variables for EPICs set properly.

Attaached is a Zip file of the Labview VI.

Gretchen

[altenbach]

Sorry, I cannot open your VI (version too new, and of course I also don't have the toolkit or access to your beacon).

(There is some code smell (but these should not cause the observed problem). For example why is the error out inside the loop? It is never modified inside the loop. You can eliminate that ugly local variable by setting VI options "clear indicators when called". Clearing an error with no inputs wired seems weird.)