Jump to content

Fausto

MCC Staff
 View Profile  See their activity

  • Posts

    1,410

  • Joined

  • Last visited

 Content Type 

Everything posted by Fausto

  1. Fausto
    Hello @Labrat. Which version of DASYLab and Windows OS are you using? If someone with admin rights installed DASYLab on the target system and now your Windows user account no longer has those privileges, then you will need someone with admin rights. Try installing DASYLab on a different system using your non-admin user account. Do you still have an issue using the Configurator? If not, check with your IT to determine if DASYLab can be reinstalled on the initial system using a non-admin user account. Regards, Fausto
  2. Fausto
    Hello @Micka1792. There is no other method to search for the MCC daq via Ethernet. Suggest testing the daq on a separate network with fewer devices to determine if your network adds to the delay. Regards, Fausto
  3. Fausto
    Hello @Micka1792. UDP or TCP protocols are not directly supported. Access to the E-1608 is only via InstaCal/Universal Library on Windows or via libuldaq and uldaq libraries on Linux. This applies to other MCC's Ethernet devices such as the E-DIO24 and E-TC. Regards, Fausto remote_discovery_v2.py
  4. Fausto
    Hello @jesusvaquerizo. In MATLAB, the 'Data Acquisition Toolbox Support Package for Data Translation Hardware' (a.k.a DT daq adapter for MATLAB) must be installed via the Add-On Manager to communicate with the DT9847. If you intend to use the analog output channel, please refer to the following forum post. Regards, Fausto
  5. Fausto
    Hello @jesusvaquerizo. I've moved your question to the MCC section on the Forum. Regards, Fausto
  6. Fausto
    Hello @aminoh. Hello, I have moved your thread to a more appropriate section of the Forum where the WaveForms developer may be able to provide some insight into this. Regards, Fausto
  7. Fausto
    Hello @Henry Walker. The following link has an option for the Dimensional Drawings file directory, which has the USB-xx08PLUS-OEM.STEP file. https://digilent.com/reference/daq-and-datalogging/start Direct link: https://files.digilent.com/drawings/USB-xx08PLUS-OEM.STEP Regards, Fausto
  8. Fausto
    Hello @Micka1792. I've moved your question to the MCC section on the Forum. Regards, Fausto
  9. Fausto
    Hello @G_M. Please refer to the following forum post. Regards, Fausto
  10. Fausto
    Uninstall 7-Zip and then install DAQami. You can reinstall 7-Zip afterward. Regards, Fausto
  11. Fausto
    Hello @CBliss. Thank you for the additional information and images. Please inspect the RJ45 port on each DT9837A module. Any debris or damaged leads? Did you use the same type of ethernet patch cable? If the cable was custom-made in-house, then please try an off-the-shelf cable. Next, create a new configuration in QuickDAQ, using both modules and selecting only one analog input channel from each module. Do you still have that issue? Regards, Fausto
  12. Fausto
    Hello @Martin Rønnov Andersen. Download and save the DAQami installation executable from this location: https://files.digilent.com/#downloads/DAQami/ Once the file is on your Windows system, run the executable. If you continue to get the 7-Zip Error, then your system is using the 7-Zip utility to launch the executable which it should not be doing. Please contact your IT Administrator to remove that file association. Regards, Fausto
  13. Fausto
    Which application are you using for your development environment? Which version of Windows OS are you using? Which version of MCC's InstaCal do you have installed?
  14. Fausto
    Hello @TFisherIRA. Which version of Visual Basic are you using, i.e. VB6, VB.NET? Use the MCC UL Help as a reference guide for supported functions. MCC UL examples are located in the C:\Users\Public\Documents\Measurement Computing\DAQ directory. Regards, Fausto
  15. Fausto
    Hello @Rob Clements. Do you have files in the C:\Program Files (x86)\Data Translation\DeviceDrivers\DT9816 directory on those systems? Is the Data Translation package enabled in DASYLab's Configurator? Is the Data Translation modules branch missing in DASYLab? Close DASYLab and install the current release of Data Translation's OMNI software. https://files.digilent.com/#downloads/DTSoftware/Omni-CD/ Afterward, open DASYLab's Configurator and disable the Data Translation package. Restart the Configurator and then reenable the Data Translation package. Are any errors exiting the Configurator? Open the Configurator again to verify the Data Translation package remains enabled. Close the Configurator and launch DASYLab. Is the Data Translation modules branch visible? Regards, Fausto
  16. Fausto
    Hello @Martin Wollatz. The MCC 172 only supports AC coupling, no DC coupling support. Regards, Fausto
  17. Fausto
    Thank you for the additional information, scope trace, and code. Is the DIO voltage (W3 jumper) configured to 3.3V or 5V?
  18. Fausto
    Hello @Bret.PID.Analyzers. I moved your question to the Measurement Computing (MCC) section of the Forum. Is the MCC USB-DIO24/37 device new or has it been in use and working correctly? Do you have another USB-DIO24/37 device to swap in and test with your equipment? Regards, Fausto
  19. Fausto
    Hello @CBliss. Were both modules reconnected to a different Windows system when you noticed this issue or "just noticed issue overnight" without disconnecting the USB and ethernet cables? Which version(s) of Windows on your system(s)? Which version(s) of QuickDAQ on your system(s)? Which version(s) of the DT9837A driver on your system(s)? Are you using a saved preconfigured QuickDAQ configuration .xml file or do you update the options in QuickDAQ each time? Try deleting the configuration file and copy/pasting a known good configuration file to retest with the modules. The .xml configuration file resides in the "C:\Users\{username}\AppData\Local\Data Translation\QuickDAQ\Config" hidden folder. Please reply with screen captures (i.e. QuickDAQ configuration) and hardware pictures as well to get a visual understanding. Regards, Fausto
  20. Fausto
    The skipped channels.
  21. Fausto
    Hello @DAQNoob. The MCC USB-CTR04 and MCC USB-1608G support PWM with the Timer output subsystem and both are supported by the MCC mcculw Python library and MCC UL for Linux Python API (ULDAQ). https://files.digilent.com/manuals/UL-Linux/python/hwov.html#ctr0x https://files.digilent.com/manuals/UL-Linux/python/hwov.html#usb-1608g-series Supported products list: https://files.digilent.com/manuals/PyWin-hw.pdf https://files.digilent.com/manuals/Linux-hw.pdf UL Help Windows Guide: MCC Universal Library Help Regards, Fausto
  22. Fausto
    Hello @maxUniqueName. Thank you for the update. The MCC Universal Library for Android is an active product. I will submit a request to our S/W team for a library update. This post and the product page will be updated once a new release is available. Regards, Fausto
  23. Fausto
    Hello @Jarrod Smith. The MCC USB-2001-TC is supported by MCC's mcculw package. https://files.digilent.com/manuals/PyWin-hw.pdf The MCC Universal Library Help shows the supported function and example. Regards, Fausto
  24. Fausto
    Hello @Display Name. Thank you for sharing the results of your investigation. Kindly provide a wiring diagram of how the MCC 152 is connected to your circuit. Please include the voltages involved and any other details. Also, please confirm that your code does not accidentally put the MCC 152's IO into output mode when connected to the encoder. Regards, Fausto
  25. Fausto
    Hello @Sirius. Use MCC's InstaCal software utility to set the thermocouple type for each channel pair on the MCC USB-TC. There is no option listed in the MCC Universal Library Help to suppress the message, so you will need to trap those errors and handle them accordingly. Recommend not selecting a channel without a thermocouple connection obviously, but understand that thermocouples can break, so the error is helpful. Error temperature values: -9999 is returned when a value is out of range or an open connection is detected. -9000 is returned when the device is not ready. This usually occurs right after the device is powered up and calibration factors are being loaded. Regards, Fausto
×
×
  • Create New...