Rob Clements

Hi Fausto, Data translation package version 14.0.0.477 Try to create new worksheet and no module available There is only one DT9816 module in target system When we install the Omni software the DT9816 files are not being installed We had previously manually copied them to that location but they weren’t linked to the drivers file so when we uninstalled the DAQ software the DT9816 drivers file remained. Thank you, Rob.

Hi, is anyone able to help on this? Our worksheet will just not recognise the data translation drivers. The module can be manually added and saved but when the worksheet is re-opened the drive module is not recognised again. I have tried different versions of the Omni software and different versions of the worksheet but the problem remains.

Hi Fausto, I installed the latest version of the Omni software but no joy. The worksheet is just not recognising the DT9816, there was no actual DT9816 file in C:\Program Files (x86)\Data Translation\DeviceDrivers\DT9816 directory on those systems it was in C:\Windows\System32\drivers We dragged a drivers file into the location you suggested it should be but DT9816 is still not recognised.

Hi Fausto, thank you for your reply. The 'Data Translation' is active and the module branch is there, that's we're a little baffled. I have to remote onto the machine so when I do I will try out the updated Data Translation software and let you know how I get on. Thanks again, Rob.

Can anyone help me please? We have a worksheet for one of our machines that requires Dasylab 2016 and DataAcqOMNI V7.8.2, there are many of these machines in the field but I have three machines in one location where the driver is not initialising when we open the worksheet. The laptops are running Windows 10 pro, we can manually install the DT9816 driver after opening the worksheet and closing the error message but after saving and closing the modified worksheet the driver will not initialise again when we re open the worksheet. Any ideas are gratefully welcome. Thank you, Rob.

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.

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

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.