Anybody else have Dasylab stop after 381 hours when using an IOTech board?

[ic0517]

After running approximately 381.1 hours, my Dasylab 10 worksheet locks up, displaying a dialog that states (retyped):

"Mismatched input channels: the time information or block length of the input channels do not match. These channels cannot be linked in this module. STOP!"

This has happened twice.

I believe the module is called an 'Arithemetic', It does a logical OR of 13 channels of 0 to 5V logic into one channel of logic. I could find out, but I would have to stop the test.

I am using Dasylab 10.0.0.3 and an older IOTech board. I had to install some special IOTech driver to get it to work. Previously the computer had been using Dasylab 5, and I do not recall the issue showing up, but I am not 100% sure I had a test run for over 381.1 on the old version. There are some, but not many, changes between the DL5 an DL10 worksheets.

One of the inputs to the Arithemetic is a signal derived from an Integrator integrating 1.00 to get a timer in seconds. It is possible a loss of resolution occurs, and some how causes an error to show up some place else. This is only a guess.

I have also taken the worksheet, removed references to the IOTech hardware, and am running it on my desk top. I tried to integrate 1000.0 to make the error occur faster, it did not.

The computer that the error occurred on is running an important test and cannot be stopped. Luckily there is less than 381 hours to completion, but the question is of course, what happens next time a test exceeding that duration has to be run.

I have worked with Measurement Computing, and even with much effort on their part, I still don't have anything really good to go on, so I decided to try this forum. As I understand, NI bought MCC and Dasylab, and MCC bought IOTech. That's how they got pulled into this. I also have a new stand running all MCC hardware - but I do not have the luxury of allowing it to run 381 hours either.

[JtotheB]

Hey ic0517,

While it is true that National Instruments owns DASYLab, our engineers can only support the software when it is used to interface with NI hardware. I would recommend taking this issue to DASYLab's online technical support system. That should be a better venue to address your issue, with engineers and users who will be more familiar with the software and interfacing it with third party hardware. Have a great day!

[ic0517]

Attempting to go the English Dasylab forum just brings me back here.

I will try online Dasylab support system.

[CJ_Butler__DASYLab_Pro]

This is the only English language forum.

Can you email or post your worksheet with all of the hardware replaced with Generators?

I'm wondering if I can reproduce the problem by changing all of the software generating modules to disable real time, and run them through the equivalent of 381 hours.

If it doesn't reproduce without hardware, then it's likely to be an error with the IOtech drivers.

I've seen this type of error before when an internal counter overflowed - back then it was related to an internal clock that DASYLab used. It should have been fixed in V10 and V11, and it took about 45 days, 381 hours.

I know that you're already working with the correct support people, since I've seen this error report internally. So, don't bother to send a DASYLab.com support request... it will just come back to the same support person. 😞

[JtotheB]

Yep, that was my fault, I got confused as to which forum I was browsing for a moment and posted with my foot in my mouth. Sorry to both of you, please feel free to heap scorn in my direction.

In either case, happy Cinco de Mayo!

[ic0517]

CJ, sorry, I have not looked at this forum for a while, because I wanted to try to recreate the problem on another computer. Take matters into my own hands.

MCC did not offer any more help, and I did not go to Dasylab.com.

What I did was remove all IOTech modules and replace with function generators on the suspect worksheet. I do not have the freedom to run on the same computer, so I took it home, and ran it there (or here, as you may figure out, since its Sunday).

And the results are ... did not lock up after 381 hours. So that would seem to point the problem at the IOTech driver. Just for the record, its Dasylab 10.0.0.3.

Are you still open to receiving the worksheet?

At the moment I went back to Dasylab 5 and tried some of the suggestions the MCC rep had. I will not know if that solved the problem until I get a test that runs for 381 hours - I am at the mercy of a schedule, AC power, and the product under test.

Side note - I can't do any Microsoft updates, and my kids some how got some Norton virus scanner on the computer, and I cannot resolve either issue until the experiment stops- this would seem to fortify my personal opinion that computers doing long term experiments should not be connected to a network that is in turn connected to the internet.

Regards,

Michael

[CJ_Butler__DASYLab_Pro]

Hi,

If you want to post the worksheet, or send it as a private message... I can try to look at it. I won't have access to a second computer for two weeks while I'm out of the office... but, the driver is certainly suspect in this case. That means that you have to talk to the MCC tech support guys again, as they provide support for IOtech now.