12-15-2011 07:29 AM
Just before a time critical job we started to get an error when loading worksheets in Dasylab 10.0.3. It was one of those 'windows has encountered an error and needs to close' things. Looking at the details it said the problem was with displ1.dll.
It made our saved worksheets unuseable as they could no longer be loaded into Dasylab without the crash occuring.
I eventually got around the problem by deleting displ1.dll from the \windows\program files\dasylab 10 folder then running Dasylab.
This allowed me to open our exisitng worksheets but with a red cross on modules that required displ1.dll - notably the yt chart and the list. If I deleted these modules, I could at least save and re-use the worksheets (but without our chart and list displays).
My quick workaround solution was to then re-instate displ1.dll and reload Dasylab. I could now open my old worksheets - because they had none of the modules that needed displ1.dll in them. Before starting my data acquisition, I could then manually add the yt chart and the list displays and then commence with the work. No problems as long as I didn't save the worksheet with a yt chart or list on it - if I did then then I would get the same error as previously described. So, with timescales short (a matter of hours) I came up with a 75% work around solution that required minimum re-work whenever we wanted to use the worksheet.
Has anyone encountered this problem before and why is it happeneing?
In my initial confusion, I uninstalled Dasylab then re-installed as 10.0.1 to see what would happen. Still got displ1.dll error. Then I applied service pack 2 to take the install back to 10.0.3 and it still didn't work. I note that there was a new version of displ1.dll in SP2.
We have been using Dasylab 10 for a number of years with the same DAQ hardware (IOtech Wavebooks) for a few years now with no problems - how come this problem has seemingly emerged from nowhere?
Andy Phillips
Solved! Go to Solution.
12-15-2011 07:35 AM
Andy,
Considering that we have now version 12.0, it would be intereting to see what happen with that version.
You could download the 30 days evaluation and open a backed up version of that file. If this work, I wouls suggest to upgrade The upgrade price offered by DASYLab is very interesting and affordable.
You can download this version from
http://www.dasylab.com/content/sendfile.php?fid=311
12-15-2011 07:59 AM
Hmmm, thanks for taking an interest but getting Dasylab 12 does not provide an explanation or solution to my problem.
As I stated in OP, we only recently encountered this problem - years of mostly stress free data acquisition with Dasylab 10.0.3 using charts and lists.
So, chances are everything would work fine in Dasylab 12, for a few years at least, then just at critical time......
We are unlikely to upgrade Dasylab, we are in process of moving over to LabView. However, no point re-inventing wheel with exisitng worksheets - unless they suddenly decide to start crashing out on us for no reason.
It baffled me and put me under pressure at the time. I came up with a bit of a work around. Now I would like to know what the experts think because I would like to avoid this kind of behaviour from Dasylab in the future, if at all possible.
Andy
12-15-2011 09:24 AM
Hi,
Were the Y/t Charts configured to use Time, rather than blocks?
I've seen the behaviour that you described when the Y/t Chart module did some bad math when trying to figure out the X-axis width if it was configured as time, rather than blocks. I'm pretty sure that it's fixed in V11 and later.
To avoid the behavior, use the block setting.
I'm sorry for the annoyance and inconvenience. I'll research to see if a V10 fix was released.
12-15-2011 09:37 AM
Ok... my research says that the bug that you described was fixed in V10.0.3.
So, please go to www.mccdaq.com, and request support. Please put in the text that CJ asked you to do it, so that they will assign it to me.
I'll want the following from you:
- copy of the worksheet
- list of DAQ hardware used by the worksheet
- the DASYLab Help->Report
I need to verify that you haven't found a new unique bug....
12-15-2011 09:47 AM
Ok CJ. Thanks for looking into this.
I'll get the info over to you first thing tomorrow morning (in UK at least).
Best Regards,
Andy Phillips