Problem: What are the DASYLab Error Messages?

Solution: The following error messages may be encountered while using DASYLab.
 

• Analog output had to be interrupted
  
  • Cause: The Digital to Analog (D/A) buffer is empty, DASYLab could not generate data to be sent by the D/A module fast enough
     
  • Correction: Reduce the output rate, or increase the output buffer size
    
     
• Cannot create DDE Link
  
  • Cause: The specified server application is not active or the specified Topic or Theme is not available
     
  • Correction: Start application and make sure that Topic and Theme are defined
      
• Cannot execute the worksheet at this module - aborted
  
  • Cause: The worksheet contains a loop that means the output of a module is (indirectly) needed for its input
     
  • Correction: Insert a time delay module or remove the loop completely
     
• Cannot open COMx
  
  • Cause: The serial port is used by another application under Windows and is not available for DASYLab
     
  • Correction: Make sure that the specified COM-port is not used by the mouse or by any other Windows application
     
• DDE Link was interrupted
  
  • Cause: The DDE Link was interrupted by the Server program
     
  • Correction: Make sure that the Server program is still running  
     
• Digital output had to be interrupted
  
  • Cause: The digital output buffer is empty, DASYLab could not generate data to be sent by the Digital Out module fast enough
     
  • Correction: Reduce the output rate, or increase the output buffer size
     
• Error No 15
  (This message may occur with some drivers that have not replaced the default message text.)
  
  • Cause: Data acquisition could not be started because a hardware conflict (like interrupts) has been detected.
     
  • Correction: This is a driver error code and you should report this message to technical support for more information. Please be prepared to describe the exact situation in which it occurs.
     
• File read error
  
  • Cause: The data file you want to read is corrupt or has the wrong file format
     
  • Correction: Check for the correct settings in the dialog box and make sure that the file format is correct
     
• Illegal block size
  
  • Cause: The FFT related module can only handle block sizes that are a power of two
     
  • Correction: Use the Data Windows module to change the block size at the FFT input to a power of twp
     
• Output rate does not match the channel rate for one channel or
  Output rate does not match the input rate at an input
  
  • Cause: These messages indicate that the global acquisition rate is not an integer multiple of the defined output rate. Synchronized output can only be realized in a way that one sample is sent to the D/A Card after a certain number of input samples has been acquired. Therefore the input rate divided by the output rate has to be an integer value. In both cases DASYLab does not use the channel rates, but the summed rates.
     
  • Correction: Adjust the analog or digital output rate
     
• The sample frequency is too high for this module
  
  • Cause: Up to version 1.54 of DASYLab the Chart Recorder was limited to 100 Hz per channel. From 1.55 it does not check the rate of input signals.
     
  • Correction: Slow down the input rate by separate or average modules
     
• The sampling rate is too fast. The measurement has been stopped
  
  • Cause: The speed DASYLab can acquire data from an analog input card is limited. The limits depend on the hardware structure and the computer you use as well as on the worksheet you run. There may be different circumstances causing this message. The most common reason is that the driver buffer in DASYLab had an overrun and that the driver did not know where to store the next samples. In this case the measurement is stopped. Usually the bar in the status line indicates how much of the driver buffer is used; there are some situations where there may be no time to update the indicator. Another possible reason is that the interrupt frequency that is needed to acquire data at the desired rate was too high and that DASYLab noticed that interrupts had been lost. This may be caused by extreme bus activities of the graphics or hard disk controllers. When this happens, the message also appears without having the buffer status indicator filled.
     
  • Correction: Slow down the sampling rate or increase the driver buffer
     
• You cannot display signals from these input channels together in one scope
  
  • Cause: The Y/t Chart module can only display signals of the same type in one display. The same type means that they are all time dependent, all frequency dependent or all histograms. When the signals are time dependent they have to have the same gap structure; that means that they may have gaps, but all at the same time and of the same length.
     
  • Correction: Use the Signal Adaptation module before the Y/t Chart or use different Y/t Charts for the different types
     
   
• You cannot display signals from these input channels together in one X/Y chart
  
  • Cause: The X/Y Chart module can only display signals of the same type in one display. The same type means that they are all time dependent, all frequency dependent or all histograms. When the signals are time dependent they have to have the same gap structure; that means that they may have gaps, but all at the same time and of the same length
     
  • Correction: Use the Signal Adaptation module before the X/Y Chart or use different X/Y Charts for the different types