Dasylab 2016 and DAQ V7.8.2

[Rob Clements]

I am having an issue setting up our worksheet for one of our machines which uses Dasylab software. We are using Dasylab 2016 and DAQ V.7.8.2 with a DT9816 card. I really have no knowledge of the software as the person who wrote the worksheets no longer works with us so I may ask some stupid questions.

The issue I have is that I cannot get Dasylab to see the DAQ software, the DAQ is seeing the machine but Dasylab is not.

That is the first issue, the second issue is with the worksheet itself as we did have the worksheet running until I managed to mess it up!

The worksheet is supposed to record the flexing angle of the machine for 25 cycles then stop the logging and calculate the average of the last 5 cycles. Previously once started it would log constantly until it saw 25 cycles then would stop the test and calculate.

Now the worksheet only logs for 8s regardless of any cycles.

[DAQman]

Hello,

My suggest is to start a new worksheet and put down only a Data Translation Analog Input module. Set the module to the DT9816 board and press Start. If you don't get an error then DASYLab can control it. If you cannot set the module to the device, remove it and restart the computer. Plug it back in after the restart and try the above test again. If it works, attach your worksheet to your reply.

Best regards,
John

[Rob Clements]

Hi John,

thank you for the advice. We have solved the communication issue stupid oversight on our side, we hadn't entered any scaling values into our worksheet! I have attached the worksheet and will do my best to explain the issue.

95% of it is working ok the only issue is with the software seeing the machine cycles, as I mentioned it is only currently logging for 8s regardless of activity. We need it to only stop logging when it sees 25 cycles.

Thank you for any help you can give it's melted my brain!

 

STM507 L V3 TM194 2020.DSB

[DAQman]

Hi Rob,

I don't see anything obvious but then again I can't simulate your system. If this is a critical application, I can recommend a consultant to help figure it out.

best regards,

John

[Rob Clements]

Hi John,

that would be great, I think we have narrowed it down to the worksheet not seeing each cycle as 1. It is counting each cycle as various values other then 1 so it does actually stop the test when the number of cycles reaches 25 but it has seen each cycle as 5 for example so stops after 5 cycles.

Thank you,

Rob.