malef

Joe, your guess and feeling was the right one. We stopped the data logging application and now there is still one timestamp every 10 minutes. We will have a look by ethernet sniffer for the remaining instance. Thank you and have a nice weekend Manfred

sorry - I have to correct the above I am using a timeout every 10 minutes = 10 * 60.000 ms = 600.000 ms

Ton, yes correct - I am using a timeout every 60.000 ms. As we don't need the seconds in stamp we don't log them. I have atteched samples of the timestamps. Sometimes there is a difference of seconds?, sometimes of 5 minutes? and everything else. I think it has something to do how LV generates timeouts and how the application has been built. The application was built on a 32bit XP machine - now it may run under 64bit W7 machine. Manfred TimeStamps.txt

Hi all, every 10 minutes we are logging data by a LabVIEW 8.2.1 application from a remote control in a 24/7 process. Timing is realized by a timeout in a event structure. This worked well for several years. Some months ago our IT moved the application and RunTimeEngine to a VMware machine. Since that time we have a second data logging within 10 minutes. As I am not familiar with VMware I have no clue what happens. Any ideas appreciated. Thanks in advance Manfred

Joe thx for your sugesstions, being short in time I had to build the cluster manually. Manfred

I am a newbie to .NET We use a .NET DLL and have a public C# structure (public struct) which is defined in the .NET class. Is it possible to generate this structure automatically in LabVIEW?

thx for info there is a new release of Modbus library. In 2006 two errors have been reported to forums. 1. "The "MB Modbus Command to Data Unit.vi" has a mistake in it. The "Write Multiple Coils" Function Code will not work properly past 8 bits of data. In case "15", the index to the "Split Array" VI should just be 8. Either that or you could remove the shift register and use an index array instead. The current implementation however corrupts the output data past 8 bits." - Jim Gruenbacher - Feb 21, 2006 This seems to be fixed in current Version. 2. "The 'MB Registers Manager.VI' is used as the repository for the Slave registers. In the case of Write, however, the Start Address is not being taken into account (compare this with the Read cases to know what I mean). The Start Address defaults to 0, always! The fix is to wire-in the Start Address to the Index input of the Array Subset primitive. This alongwith the (already present) Length input should write to the correct set of registers, coils, etc." - Khalid - March 18, 2006 This has not been fixed by NI up to now and may cause trouble. :thumbdown:

A snippet how to make use of LPT via OutPort.vi

Some comments ... Integration is not a simple cumulation of values ! http://en.wikipedia.org/wiki/Integral Hardware configuration is most important for a correct Dynamic Signal Acquistition - even if 10 Hz is not very dynamic. Please give us some more information about hardware : - Sensor (type, frequency range, sensitivity) - amplifier - hardware filter - DAQ board (type, coupling, sampling rate, number of samples) To answer questions about software filtering and further more we need information like : - Do you need just time domain or also frequency domain information? - Do you need phase information between axes? - Or do you just want to measure and calculate amplitude of 10 Hz displacement? - ??? Manfred Links relating acceleration -> displacement conversion acc to displhttp://zone.ni.com/devzone/cda/tut/p/id/4093 example acc to displhttp://zone.ni.com/devzone/cda/epd/p/id/2495

Hi Gianmarco, some multimeters abuse handshake lines DTR and RTS to supply builtin opto couplers with power. To investigate this please Unplug Multimeter. Close LabVIEW and run the Mas-VIEW program. One way to verify states of lines is to measure voltage at pin4=DTR and pin7=RTS versus pin5=ground. Or investigate states of lines with MAX by opening VISA Test Panel of the Com-Port. Please report your results to the forum and we can give further help how to control handshake lines out of LabVIEW by a property node. Your Start.vi executes write and read in parallel. Modify like tcplomp did. ...pass the VISA-resource from one subvi into the next. Manfred

Mat, process the checksum in a for loop like in attached snippet. Greetings Manfred Download File:post-831-1153377427.vi

AI Read is a polymorphic VI that you can configure to output the waveform. Right click on AI Read and select type - waveform. good luck Manfred

Sorry Henning, I fixed faulty VI and simplified it. Manfred Download File:post-831-1147336333.vi

Henning, string manipulations are very time consuming. If you handle large files a byte conversion with ascending manipulation will save a lot of computing time. Manfred Download File:post-831-1147260271.vi