N.T.

Ok, I got it after a whole day of debugging (and crashing): I had a race condition with closing two other important references and if the first one was closed prior to the second one, lv had a hard crash. Which is unfortunate but it means my map construction is working fine. Seems like i made this important chance without noticing it.

Hi Volks, i have a problem which arose when I switched within my code from single references to a map containing a key (string) and a value (reference). The reference is pointing to an ActiveX object. Is there any known issue with maps and references? If the code is running earliest the second time but sometimes after a few runs (8 was my max) LV IDE has a hard crash without any error message. I got the feeling that the reference within the map is somehow messed up and the activex call is overwriting program memory. My first tries were hard crashes, another attempt showed at least something like "MEMORY_WORKER.cpp" in an error message (just appeared once). I tried searching the changelog but couldn't find anything. Is there a known issue in LV21? Thank you!

It took me a while to figure out, what's from. Sure it doesn't look beautiful and there's enough room for improvement, but the code does exactly, what it should.

Thank you for your help. Unfortunately the lenght is not normalized. But that's, what Interpolate 1d does. It's quite a mess, but it's working. A real pain is the behavior of the interpolate 1d vi, as it is using the given points as center for it's interpolation. You cannot specify the given point to be the beginning. Direction and Servo Load are binary values (as doubles) that have only 11 members, whereas the other arrays have around 2000-6000 members. The interpolation doesn't help that much. But that's another matter.

I have a test rig capturing different values from sensors (momentum, position etc). Unfortunately those devices are USB, non-realtime and don't give a timestamp. I record the values within parallel loops and also storing the current time stamp value using the timer with high accuracy. Access times to the usb devices differ so I don't have a common timebase for the measurement. I eventually have a couple of arrays containing the values and timestamps. Now I try to bring them all to a common time base. I look up the first and the last timestamp, use the ramp pattern vi to create a fixed time interval and use the sum of the number of all arrays to not loose values inbetween. Unfortunately, the Interpolate 1D array vi is not capable of shifting the start time to bring the specific array within the start/end Range. As a very simplified example: Array A Timestamp 1 2 3 4 5 6 7 Value 10 30 50 70 90 110 130 Array B Timestamp 1.5 2.5 3.5 4.5 5.5 6.5 7.5 Value 20 40 60 80 100 120 140 Data after merging Timestamp 1.0 1.5 2.0 2.5 3.0 3.5 4.0 4.5 5.0 5.5 6.0 6.5 7.0 7.5 Value A 10 20 30 40 50 60 70 80 90 100 110 120 130 --- Value B --- 20 30 40 50 60 70 80 90 100 110 120 130 140 Have you any idea how to solve this?