From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
12-23-2006 02:12 AM
12-27-2006 05:31 PM
Dear Sharonoff,
It is very strange that you are completely losing connection sometimes and you have to reboot the controller. I would encourage you to format your controller and reinstall the software from MAX.
Half duplex connection is supposed to speed up the traffic between your PC and the Real-Time target when using a crossover cable. Make sure your settings for the remote RT target and your Host PC network card are set to 100Mb Half duplex. For the remote target, you simply click on the icon in MAX, and then click on the "Advanced Ethernet Settings" button. Use the "Media Mode" drop down menu to select the connection mode.
For you Host PC network card, go to Start>Settings>Network Connections>Local Area Connection. Then click on Properties. Then click on Configure>Advanced>Speed & Duplex. Select 100 Mb Half from the drop down menu.
Hope that helps!
12-29-2006 03:09 AM
01-02-2007 11:31 AM
Hi Sharonoff,
Here is the description of Halt system if TCP/IP fails
"Enable this checkbox to stop the LabVIEW Real-Time Module if the network connection fails when you boot the remote system. If you clear the Halt system if TCP/IP fails checkbox, LabVIEW RT starts and runs startup applications you created, even if TCP/IP fails when you boot the system.
Note: DHCP failure is considered a TCP/IP failure. "
In other words, it should only affect your Real-Time Module when it initially boots up. You can try running your application with the box checked and cleared.
As I mentioned in my previous message, there might be something wrong with one of the installed drivers on your Real-Time controller, specifically the driver for your Ethernet network card. Formatting the controller would be the first step I would take.
Please let me know if you continue seeing the error after formating the RT controller. Also provide me with some information on what kind of traffic you observe between your PC and your RT controller. More detailed information on your application will be helpful to pinpoint the problem..
Hope that helps!
02-08-2007 08:01 AM
02-09-2007 09:31 AM
02-10-2007 12:14 AM
02-14-2007 07:12 AM
02-15-2007 05:30 PM
Hi Sharonoff,
I did not know you were using LabVIEW FPGA. Your timed loop shows that you are using a 1MHz clock and your wait time is 2us. I can't really tell what resolution you are using in the regular loop - millisecond or microsecond? Did you try setting different wait periods just to see how your loops would respond to that?
I think you are not giving enough sleep time to your Timed Loop, so the CPU does not allocate time for any other process besides your Read and Write operations. Hence, your communication process fails.
Also you should consider special architecture.
Host VI (on PC)
Noncritical loop VI (on RT) - it handles all communication with the Host VI on the PC via Network Shared Variables or other communication techniques.
FPGA VI (on RIO) - handle al I/O and sending data back to the Noncritical loop VI.
Hope that helps!
02-16-2007 02:50 AM