LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error running EPICS Server-Client Example on cRIO

Did you follow the steps on the example page to create a new EPICS server on the cRIO and client on the host computer? This is necessary so the EPICS client is pointing to the correct IO Server.

 

Having a reference to the wrong host machine for the variables causes the error you posted.

Zach P.

Staff Software Engineer | LabVIEW R&D | National Instruments
0 Kudos
Message 11 of 17
(1,753 Views)

I was able to create a working Client and Server on a Real-Time target and host PC using the steps found in the example. You will need to make the EPICS Server, EPICS client, and client variables from scratch. You will also need to drag into your Client.VI the variables you bind on the Client side 

Zach P.

Staff Software Engineer | LabVIEW R&D | National Instruments
0 Kudos
Message 12 of 17
(1,747 Views)

So we tried something very similiar.  We renamed the variables to more simple names on the server and then connected to the on the client side and were able to communicate. There seems to be a problem with PV names such as "NI-cRIO9024-EPICS:Server_Library:Amplitude" and "192.168.0.249:Server_Library:Amplitude" (in fact the software will not let you enter periods in the text box),  but "Amplitude" works just fine. Do you know what the specific restrictions are on the names?

0 Kudos
Message 13 of 17
(1,743 Views)

There are a few characters you cannot use in variables names (language characters that are not installed); some others are listed in this screenshot.

 

names.png

Zach P.

Staff Software Engineer | LabVIEW R&D | National Instruments
0 Kudos
Message 14 of 17
(1,737 Views)

Hi guys,

 

I am trying to do the same at the moment and experiencing similar issues.

 

How did you manage to get an IP address for the variable in your EPICS Client? (as in your screenshot)

 

I am wondering if this is my issue - I can see the server library working in DSM but the EPICS client on the host computer times out.

 

I am running on link-local but surely that should make no difference? I am using the hostname of the cRIO as I can't enter an IP on the client, so maybe that is not being recognized with link-local?

 

Could you give an explanation of your fix? Surely the addresses must be server:library:variable (ie 'mycrio:library:amplitude'), not just 'amplitude'?

 

Thanks

0 Kudos
Message 15 of 17
(1,705 Views)

Hi LaThoS,

 

Can you ping your cRIO to ensure you're connected to it?

 

Also, this threat is pushing a year old, you may want to post in a new thread if this is a different issue.

 

Regards,

Bobby Breyer
Applications Engineer
National Instruments
0 Kudos
Message 16 of 17
(1,680 Views)

Hi Bobby,

 

I tried from scratch again and this time managed to copy an IP into the PV field. All working now 🙂

 

Cheers.

0 Kudos
Message 17 of 17
(1,662 Views)