Error 63/cFP-2020 on the network talking with PC

[Coop]

How do I know if I have firewall running on my local machine?
Let's assume I have it.
How do I open it for the specific ports?

It is all regarding the Error 63 I get when I run the Host VI on my computer after the Normal Priority and Time-Critical Loops VIs were downloaded to the Remote Run-Time Engine (cFP-2020 Controller) placed on the network.

Thanks,
Pedja

[Ames]

Pedja,

Firewalls vary a lot depending on the vendor, so it is hard to say how you would do that for your specific case.

Which specific VI do you get the error 63 VI from? Are you running an embedded LabVIEW program on the cFP-2020 as well as a distributed application on the host? Please try to explain the details of what you are doing in more depth and I think we can find a solution.

Ames
Applications Engineering
National Instruments

[Coop]

Hi Ames,

I think I found the cause for Error 63.
It is something with my code that is making cFP-2020 get into wrong state so when TCP Open block tries to open TCP session it receives the error.

Thanks for your time,
Pedja

[Coop]

Hi Ames,

At first I thought the problem comes from the code I wrote but after a couple of days of troubleshooting I did not progress far.

So I will try to answer your questions so that you can get better picture of my communication system.

Which specific VI do you get the error 63 VI from?

I would receive Error 63 inside of my Host VI.
However when I matched the port number in Tools>>Options with the port that is assigned to my NPL, TCL and Host VIs by RT Communication Wizard I was able to pass the TCP Open Connection Function point without getting an error but then I received error 66 outside of TCP Read VI.

Are you running an embedded LabVIEW program on the cFP-2020 as well as a distributed application on the host?

I run/download my NPL (
together with TCL as a subVI inside of it) to the RT Target (cFP-2020) through crossover cable.

If I then switch LabVIEW target without
closing RT VIs while the NPL is running on the target
the message would pop up saying:
"Connection to the RT target has been lost.
Switching back to host LabVIEW."

I still open Host in LabVIEW and try to communicate and I get error 56 outside of TCP Open Connection function.

I know everything about the meaning of the errors. I printed out a lot of documents from the knowledge base/Discussion Forum but I do not know how to remove the errors.

I noticed that few people were suggesting to use No EOC Error VI to ignore some errors.
I have this VI inside of my NPL VI but not inside of Host VI. Should I add it to Host too?

If you want me to attac my VI I can do that too next time.

thanks for your time,
Pedja

[Remzi]

Hi Pedja,
You shouldn't be receiving the "Connection to the RT target has been lost. Switching back to host LabVIEW." error. Once you receive this error, your host VI won't be able to communicate with NPL VI running on the RT target. In your first message, you asked about how to know if you have firewall software running on your local PC. The error above might be related to a firewall software if this is the case. I would recommend you to disable the firewall and try to switch the execution target to LabVIEW for Windows after you run the NPL on the RT target. If you do not know if you have a firewall software, or how to disable it, you can try another PC with LabVIEW RT to test your application. I hope this helps.
Best Regards,
Remzi A.
Appl
ications Engineer
National Instruments.