Jump to content

Fausto

MCC Staff
  • Posts

    1,404
  • Joined

  • Last visited

Community Answers

  1. Fausto's post in QuickDAQ fails to start on fresh Win 10 install was marked as the answer   
    Hello @fdix.
    Please uninstall Data Translation's QuickDAQ software via Windows Control Panel.  Run appwiz.cpl to access the Control Panel.

     
    Next, download and install Data Translation's OMNI software, which includes QuickDAQ.  Does the new installation resolve your issue?
    Regards,
    Fausto
  2. Fausto's post in MCC134 Sampling rate limit was marked as the answer   
    Hello @vick.
    The sampling rate of the MCC 134 is 1 S/sec per channel.  The result stems from the components and design.  There are no plans to change the design to increase the sampling rate.
    For sampling rates up to 60 Hz, consider the MCC USB-2408 for supported MCC hardware with Linux and MCC hardware with Windows. 
    (The MCC USB-2408 can sample at a faster rate.  However, since thermocouples are susceptible to pick up noise from the surrounding environment, a data rate based on the primary noise frequency is recommended.  For example, to reduce the effect of 60 Hz noise, select a data rate of 60 (or a supported submultiple of 60, such as 
    10 or 5).)
    Regards,
    Fausto
  3. Fausto's post in One DAQ with Multiple PCs? was marked as the answer   
    Hello @mikeg.
    The QuickDAQ license is a single user license.  We understand that the license may not be used on a mobile Windows system and end-users may have systems in multiple locations.  As long as multiple users are not using QuickDAQ with the same license concurrently, your scenario should be within the policy rules.
    Regards,
    Fausto
  4. Fausto's post in Can DT9834-8-4-16-BNC be disassembled into OEM version? was marked as the answer   
    Hello @TAnd.
    The MCC DT9834-8-4-16-BNC device can be disassembled to access the MCC DT9834-16-4-16-OEM board.  Please note that doing so will void the device's warranty.
    Regards,
    Fausto
  5. Fausto's post in Frequency measurement using 1208LS was marked as the answer   
    Hello @vmrak.
    Thank you for the example.  Your device does not appear to have an issue if it is capturing expected data values with valid signal connections.  Without a signal connected to the input channels, the USB-1208LS is measuring surrounding environmental noise.  MCC devices were designed to work with low impedance signal sources.  MCC device inputs that are unconnected (open) are considered high impedance and will charge up to various stray voltages.  Notice that your detected amplitudes are in the microvolt range, so disregard those values.
    Also, as you increase the signal frequency to the device, consider increasing the sample rate and number of samples per channel.
    Regards,
    Fausto
  6. Fausto's post in Example Programs was marked as the answer   
    Hello @Simple Minded Engineer.
    On your Windows system, use the Windows search field in the Taskbar to locate the appwiz.cpl applet.  Once the applet is showing, click on the Turn Windows features on or off option in the upper left corner.  In the Windows Features, select the .NET Framework 3.5 (includes .NET 2.0 and 3.0) feature.

     
    Click the OK button to close the window and then minimize or close the applet.
    Launch Microsoft Visual Studio and then open a MCC UL example.  In the Solution Explorer, right click on the example name and then select Properties.  On the Application tab, select the Target Framework (i.e. .NET Framework 3.5).

    In the popup change window, click the YES button.  You should be able to use the example and develop your own application.

     
    What Universal Remote are you attempting to use with the Universal Library?  The MCC Universal Library supports MCC devices.
    Regards,
    Fausto
  7. Fausto's post in OMB-DAQ-2416 Configuration Issues was marked as the answer   
    Hello @tycbrown32.
    Please test the attached MCCULW Python example, usb_2408_2416.py, with your OMB-DAQ-2416 daq device.  usb_2408_2416.py
    The example configures four analog input channels.  Make the necessary code changes to match the first four channels wired on your device.
    Regards,
    Fausto
  8. Fausto's post in USB-202 not recognized by InstaCal was marked as the answer   
    Hello @SLee.
    Uninstall InstaCal v6.74 from that Windows 7 system.  Afterwards, using the following link, download the installer to the host system and run the installation. 
    https://files.digilent.com/archive/MCCDAQ_CD/Archive_6.55/mccdaq.exe
    Once installed, please launch InstaCal to detect the USB-202. 
    If the device remains undetected, then open Windows' Device Manager.  Is there a 'DAS Component' branch with a device?  Please reply with screen captures and any error codes in the Device Status field.
    Lastly, please test the USB-202 with InstaCal v6.74 on a different system running Windows 10 or newer.
    Regards,
    Fausto
  9. Fausto's post in USB-1208HS-4AO terminal block pitch or part number was marked as the answer   
    Hello @Jason Tost.
    Mechanical drawing for the USB-1208HS-4AO:  https://files.digilent.com/drawings/USB-1208HS-4AO.pdf
    The connectors have 3.50 mm spacing.  Attached is the connector's datasheet.
    connector.pdf
    User Manual:  https://files.digilent.com/manuals/USB-1208HS-4AO.pdf
    Regards,
    Fausto
  10. Fausto's post in USB-3101FS FIFO capabilities? No mention in manual was marked as the answer   
    Hello @TAnd.
    The USB-3101FS does not support synchronization with other devices.  With regards to your waveforms data, the host system is used to store the data, in user created buffers, and then the data passed to the USB-3101FS via the USB cable.  The analog output update rate is 100 kS/s per channel, which meets your requirements.
    https://files.digilent.com/manuals/USB-3101FS.pdf
    Regards,
    Fausto
  11. Fausto's post in CIO-EXP-GP was marked as the answer   
    Hello @Pedro Sosa.
    The CIO-EXP-GP is an obsolete item, as is the CIO-DAS802/16.  The CIO-DAS802/16 has a 37-pin D type connector and compatible with a C37FF-x cable (also obsolete).  This cable is compatible with a CIO-MINI37 board (SKU: 6069-410-204).  
    The PCIe-DAS1602/16 (SKU: 6069-410-078) is still available.  Take a look at the user's guide to confirm necessary connections.
    PCIe-DAS1602-16.pdf
     
    Regards,
    Fausto
  12. Fausto's post in USB1024HLS - switching 24V signal output was marked as the answer   
    @Drew,
    The 5V Panasonic relay should work with the USB-1024HLS device.
    Regards,
    Fausto
  13. Fausto's post in Reading a Digital Output State was marked as the answer   
    There is no command to read the physical state of a digital output bit.  You would need to physically loop a wire to a digital input line and then read the digital input line.
  14. Fausto's post in DT9837A Sync Mode/ Master Slave/ Software Trigger was marked as the answer   
    Hello @DAQIEPE.
    Please reply with screen captures of the Traceback from running your example and include your Python code in the response. If attaching a file, rename the PY extension to TXT.  The DT9837A does not support the 'set_sync_mode()' method in UL for Linux.
    https://www.mccdaq.com/PDFs/Manuals/UL-Linux/python/hwov.html#dt9837
    Regards,
    Fausto
  15. Fausto's post in MCC172 Multi boards can not found address was marked as the answer   
    Hello @1zhangyo.
    I have four MCC DAQ HATs on a RPi 3B.  When I press the 'Read EEPROMs' button, the display shows four EEPROMs found at addresses 0-3.  On my RPi 4B, I have two MCC DAQ HATs.  When I press the 'Read EEPROMs' button, the display shows two EEPROMs found at addresses 0 and 1.  With four MCC DAQ HATs on your RPi 4B, the 'Read EEPROMs' button finds eight EEPROMs at addresses 0-7.  
    Remove all HATs from your module and restart by adding one MCC DAQ HAT with the corresponding address jumper configuration.  Afterwards, run the MCC DAQ HAT Manager and press the 'Read EEPROMs' button.  How many EEPROMs found?  Press the 'List Devices' button as well.  Any issues with just one MCC DAQ HAT?  If not, continue to repeat this process for each of the other MCC DAQ HATs.
    Regards,
    Fausto
  16. Fausto's post in Not recommended for new applications was marked as the answer   
    Hello @sam56.
    If your intention is only to purchase one device, then choose the best one suitable for your needs.  If you're designing an application to purchase these devices for years to come, then choose the USB-1808X.
    Regards,
    Fausto
  17. Fausto's post in End User License Agreement (EULA) for WDFileConverterSetup software was marked as the answer   
    Hello @ScottTa.
    There is no EULA for the WebDAQ File Converter utility.  However, since the utility is a MCC software product, you can use MCC's InstaCal EULA for guidance; see attachment.
    Regards,
    Fausto
    InstaCal-EULA.pdf
  18. Fausto's post in Are the analog outputs updated simultaneously from USB-2627? was marked as the answer   
    Hello @sonbeing.
    The USB-2627 has four 16-bit, 1 MHz analog output channels (XDAC0 to XDAC3).  All outputs can be updated at 1 MS/s, regardless of the number of channels in a scan, when set to hardware paced.  A 'simultaneous' scan option in software is not supported.
    Regards,
    Fausto
  19. Fausto's post in Do I need a WiFi adapter to use the WebDAQ 504? was marked as the answer   
    Hello @burnsja2.
    The WebDAQ 504 will work with an ethernet cable.  A WiFi adapter is only needed if you desire a wireless connection.
    Regards,
    Fausto
  20. Fausto's post in MCC 134 GPIO13 function was marked as the answer   
    Hello @tomaszciesla.
    GPIO 13 is used by all MCC DAQ HAT boards and it should not be used by other non-MCC HATs.  The image below shows which subset of the GPIO pins are used for each MCC DAQ HAT. 

    The Raspberry Pi board's 40-pin GPIO (general-purpose input/output) header is used by Measurement Computing's HAT modules:  MCC 118, MCC 128, MCC 134, MCC 152, and MCC 172.
     
    Regards,
    Fausto
  21. Fausto's post in Download page seems broken was marked as the answer   
    Hello @Tim42.
    It could be your browser settings or company restrictions.  Check you 'Downloads' folder or try a different browser.

     
    If you continue to have an issue, below are direct links to the MCC DAQ Software and InstaCal download folders.
    https://mcc.download.ni.com/#downloads/MCCDaqCD/
    https://mcc.download.ni.com/#downloads/InstaCal/
    Regards,
    Fausto
  22. Fausto's post in WebDAQ 504 Inductive Proximity Sensor (PnP) as Keyphasor was marked as the answer   
    Hello @Tobias Z.
    That is correct.  Refer to page 22 of the WebDAQ 504 User's Guide.  https://www.mccdaq.com/pdfs/manuals/WebDAQ-504.pdf
    Regards,
    Fausto
  23. Fausto's post in DT9818 Dynamic Resolution? was marked as the answer   
    Hello @TM178.
    The DT9818 uses one 16-bit A/D converter for its analog input subsystem.  However, since the DT9818 (as any other daq module) has other components and circuitry in the design, the 'effective number of bits' (ENOB) is 14.1 bits; as reported on Table 28 on page 123 in the DT9818 User's Manual.  
    https://www.mccdaq.com/PDFs/Manuals/UM9818.pdf
    Your calculations would use 14.1 bits and a total range of 2.5 V (for the +/-1.25 V input range).
    17560 discrete points & a 2.5 V range
    (2.5 V) / (17560) = 1.4E-4 V/bit
    For an acquisition, definitely use the smallest input range available on the DT9818 for your voltage level.
    Regards,
    Fausto
     
  24. Fausto's post in Connecting MCC DAQ to Recompiled LabView Executable was marked as the answer   
    Hello @JamesH.
    Which version of Windows OS is running on the target system?
    How much do you know about the history of your executable?
    Which versions of LabVIEW and InstaCal were used to create the executable?
    Download and install the current version of InstaCal v6.73 onto the target system.  https://mcc.download.ni.com/#downloads/InstaCal/
    Close the LabVIEW executable and connect the USB-234 to the system.  Launch InstaCal.  Does the USB-234 show up in the board list?  If it does not, then it may be a hardware issue.  
    If the USB-234 is detected by InstaCal, then close InstaCal and retest your LabVIEW executable.  If the LabVIEW executable continues to not detect the USB-234 module, then you may need to recompile the VI with current versions of InstaCal, ULx for NI LabVIEW, and LabVIEW.   Reference the following MCC knowledgebase article and the 'ULx for NI LabVIEW Help' for 'Distributing a ULx for NI LabVIEW application'.
    https://kb.mccdaq.com/KnowledgebaseArticle50609.aspx
     

     
    The MCC DAQ Software contains InstaCal and ULx for NI LabVIEW.
    https://www.mccdaq.com/Software-Downloads
     
    Regards,
    Fausto
  25. Fausto's post in LABView Retriggering of DT9844 was marked as the answer   
    Hello @Grata.
    Yes, the DT9844 is supported in LabVIEW.  A user must install Data Translation's LV-Link library of VIs for NI LabVIEW.  The LV-Link installer also includes Data Translation's Open Layers library and drivers.  Here is the download link folder.  https://mcc.download.ni.com/#downloads/DTSoftware/LVLink/
    Connect the DT9844 to the target Windows system before launching LabVIEW.  Open the 'DtAinTriggeredScan.vi' example to test the external retriggering capabilities of the DT9844.

     

     
    Regards,
    Fausto
×
×
  • Create New...