Tim Erickson

I use a state machine that has two parallel loops in the meat of it. If the connection is lost, it will attempt to reconnect on a separate port. The code for the connect is in separate states of the state machine. The screen shots show the cRIO TCP Server run state and the HMI TCP Client run state. Let me know if you have any specific questions. I am limited to what code I can share but am can at lease offer screen shots.

Here are a couple of suggestions: 1) Create an About VI that has a version number embedded in it. When called it supplies a version number. It would have to be updated when you update your application. 2) Put a version number in a configuration file that can be either opened manually or retrieved using a VI. 3) You can enter a version number in a built exe. 4) You can enter a version number in an installer. 5) Put the version number in a Help\About pull down menu choice (in the case of an HMI) 6) Use the revision number in the title bar of the top level VI.

You keep getting a reference to Meetbox FIFO but never close it.

I am using with LabVIEW 9.0.1

I am using MySQL and LabSQL and it works great. No toolkit required. http://jeffreytravis.com/lost/labsql.html

Does the Scan Engine Advanced IO access API work with a remote Ethercat Chassis?

You have to use User Defined IO variables. There is a limit on how many you can use. See: http://zone.ni.com/devzone/cda/tut/p/id/10618

This is a great set of code for logging data from a cRIO to a mySQL database. I am running a 99 field insert query in a 250 msec timed loop, the query only takes 2 msec to execute.

If the application requires a piece of hardware, such as a DAQ card, you can use its serial number.

I would look at the data logging examples first. That is where I started. 1) If you need to log data continually: Set up a real time FIFO. Put data into the FIFO in your data acquisition loop. Remove data from the FIFO and write it to a file in a separate loop. Log the data to a USB memory stick but you could also send the data to a host computer over Ethernet. OR 2) If you need to collect data at a high rate for a short period of time and then save: Set up a state maching that looks for a trigger. When the trigger is detected change states and to collect data for the preset time and then save. I ended up using 2) above. We are looking at impact data resulting from the collision of two locomotives.

Great! When will native OO be available for cRIO? I am currently using 8.6.

Use Windows Performance Monitor. Select "Process" in the Performance Object control. Then select "Page File Bytes" in the Counters List control. Then select "LabVIEW" (or the name of your LabVIEW executable) in the Instances List control. Add this to the graph and watch it over time while your vi is running. If graph trends up, you have a memory leak. If you do have a memory leak, look for instances where you open a reference without closing it over and over (queues, vi ref's, notifiers, etc.). Tim

Hi All, I have recently been exposed to a project that used a dSpace controller, Simulink, ControlDesk, and some other dSpace toolkits. Do any of you have any experience using these products as well as LabVIEW and NI hardware? What are the benefits/drawbacks of each? Just trying to educate myself! Thanks!

I posted this in the LabVIEW section but am duplicating it hear. Hello, Does anyone have a LabVIEW driver for MiniNet? MiniNet is a communications protocol used with B&R PLC's over RS-485. Thanks!