Jump to content

Anna.Gardner

Members
  • Posts

    7
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Anna.Gardner's Achievements

Newbie

Newbie (1/4)

0

Reputation

  1. Hey Fausto! I'm unsure if these cells worked previously within the worksheet. The worksheet is pretty old (maybe 2014 or before creation date). The employee that created these has since retired. I've been trying to revamp them so I apologize for my lack on origination knowledge. Recently, we upgraded from an older version of Dasylab to Dasylab 2022. We also moved all the sheets from a Windows 7 computer to a Windows 11 computer. There has a been a few issues getting the sheets to load, but nothing within the worksheet has changed- just the Dasylab version. I have attached the sheet and I listed below the few issues that I noticed right off. Issues that I've noted in the worksheet are: Global variables for all "mid" gas values do not update. Global variables for continuous logging do not update. Thank you for looking into this AG InitialCal.DSB COMPLIANCE RAWDATA TEMPLATE.xls
  2. Good afternoon, My company uses DasyLab along side of a personal DAQ for air emission testing. For this process, we've primarily relied on assigned global variables (along with some other functions) to use throughout the datalogging process. However, it seems our global variables are having a glitch. To summarize, we have assigned global variables for gas calibrations (a low, mid, and a high gas.) All of these global variable values update continually based on what the gas analyzer is reading in real time. We have a one-stop switch and a write to excel that logs the value in the spreadsheet at a specific time for each variable. Our low and high variable work fine- updates every minute or so. Our mid only reads what is input in the "value" line of the global variable description. Please see attached image for where 7,8, and 9 are the global variables in question. 7 and 9 read real-time while 8 sits at 0 (input value) I'm curious as why the value is updating for certain global variables and not others. We wrote these sheets a while ago and I am having trouble backtracking the steps. Anna G.
  3. My company recently purchased the FULL version of DasyLab 2020 to replace an old version of DasyLab (7, I believe.) We were told that we could import all of our old layouts/workbooks into the new DasyLab 2020 version. We did the trail version, and everything seems to work fine and we did not have any compatibility issues. However, this was tested about a year ago. For some reason, we are now having several error messages pop up since purchasing the full version. Since the employee that created these workbooks is now retired, we are left to figure all of this out ourselves. We are now looking to fix the problems associated with the error messages that continue to pop up and, ultimately, run the workbooks in the new DasyLab version. Here are the steps that we took that open up this error message: 1. Opened DasyLab 2. Opened the file locator and opened the associated workbook This error message pops up. We can continue onto the workbook if we click "continue." However, we get more error messages and are not able to "play" within the workbook. After we click through that error message and click "play," the second error message pops up for all our ODBC cells. I believe this might have something to do with a drier not being installed correctly or not loading correctly, see on image 3. What can we do to fix these two issues?
  4. Thank you for such a quick response! Please excuse my ignorance. I do understand the concept behind running it as an administrator but I am unsure how to make that happen. Would you mind sending a step-by-step? The last six of our serial number is C-42459
  5. My company recently just upgraded to the DASYLab 2020 after previously having DASYLab 7. We have a large library of worksheets that were developed under DASYLab 7 using a personal daq, so we were careful when deciding to upgrade as those worksheets would have to transfer over to the newly purchase version. After ensuring that all of the sheets could transfer over and be used with our personal daq, we made the plunge. Everything worked fine until a few months ago. We are unsure of what happened but are now getting an error message when any worksheet is opened. (See image 1) IT states that the .XML Hardware Configuration file associated with the DASYLab work sheets cannot be opened. Additionally, all of our action modules and ODBC out modules within the worksheets are not recognized at all. (See images 2 and 3). This seems to only be the case under the DASYlab 2020 software as the DASYlab 7 is still fine and able to be used. We are unsure as to what steps we need to take in order to move forward and make these worksheets usable again under the Dasylab 2020 software.
×
×
  • Create New...