04-25-2007 10:23 PM
04-25-2007 10:36 PM - edited 04-25-2007 10:36 PM
This may be a hint:
The shared variables are deployed and the routines are running. If I kill the shared variable engine, the routine running on the computer stops with an error. The routine running on the cFP keeps running happily along, and acts like it's still writing to the shared variables. It can't be of course, because the shared variable engine is stopped now.
Message Edited by rgentry on 04-25-2007 10:37 PM
04-26-2007 06:00 AM
One more hint:
If I move the host location for the shared variable from the computer to the cFP, the variable can be read and written to. So, it appears that the shared variable hosting on the PC is to blame here.
04-29-2007 07:59 PM
Hi,
You mentioned that upon closing the shared variable engine, you recieve an error. What is this error? Meaning, what was the message associated with this error? Was there an error code?
This may lend some more clues as to why you are encountering this problem.
Cheers,
Emilie Kopp | Applications Engineer | National Instruments
04-29-2007 08:24 PM - edited 04-29-2007 08:24 PM
Message Edited by rgentry on 04-29-2007 08:24 PM
04-30-2007 10:08 AM
Excellent work, rgentry.
Yes, often times, when one has a wireless card in addition to a LAN ethernet port, any shared variable communication can show symptoms of incorrect behavior. This is because the logos thread is tied to a primary MAC address and it seems as though the application was automatically assigning the address of your wireless card. When you disabled the wireless card, the LAN port became the primary port and the alias file was automatically assigned to it.
While it certainly is possible to have both ethernet ports configured in your application, there are certain precautions one must take to ensure proper functionality. You can visit this KnowledgeBase article for a discussion regarding these precautions.
Also, I am wondering if perhaps rather than disabling the wireless card, you might try simply modifying the .aliases file to use the static IP of your ethernet card. Had you tried simply changing the IP address in the alias file to match that of your wired port?
Cheers,
Emilie Kopp | Applications Engineer | National Instruments
04-30-2007 11:43 AM