JRys

If the E-TC is not networked and connected to the computer, it should auto-link to an address like 169.254.100.100. Then, the standard examples will work. I've used the command arp -a to list IPs when on a network. Please be sure to look for a device name that begins with E-TC-xxxxxx. The xxxxxx is the last six digits of the MAC address. Once you have the IP, run the remote net discovery example program to learn how to get the device handle. If you need to assign a fixed address, you must use the InstaCal utility.

The USB-1608FS-Plus input impedance is approximately 100M ohms, and I suspect your probe is also close to 100M ohms. The probe creates a divider that reduces the measured voltage. The input impedance spec is 100M ohm minimum. Each channel could be different, which may explain the voltage difference. You can test the inputs by connecting them to a battery or a function generator without using the probe. Consider using a transformer to reduce 330 VAC to a more manageable level and minimize the source impedance.

Either software package will work for your application. However, I prefer DAQami because running InstaCal is not required. We offer the DASYLab software, which has many more capabilities depending on your chosen level. DASYLab will allow you to do the math on the data in real-time. You could use the reference curve feature to qualify the data in real-time. First, you must generate the reference curve data consisting of minimum, mean, and maximum curves. The data is saved to a file using the reference curve tool. In the chart recorder display, you specify the reference curve file. When data is collected, it will be shown with the reference curves. The operator can then visually check to ensure the data remains with the maximum and minimum curves before giving the belt furnace a passing grade. DASYLab BASIC or better is required for the reference curve feature.

Unfortunately, I don't have access to Modbus equipment, so I cannot test your worksheet. However, if the serial port Modbus is similar to the Ethernet Modbus, setting the Startbyte to 16 and enabling bitwise operation will begin writing at 17. A customer confirmed that it writes the following location. Otherwise, setting Startbyte to 17 starts at 136 because a byte is 8 locations. Use bitwise and try updating 16 and 17 to see if either works.

You must be UL Daq for Linux instead of our Python Windows support.

This is a duplicate inquiry by the customer.

That sounds like the maximum length of the USB cable. The USB Specifications section on page 31 of the user manual lists 3 meters or 9.84 feet. If your sensor has a differential output, you could run 300 meters or more of cable, assuming it is shielded twisted pair wire.

The UL Create Channel VI can get confused if you connect a control to the physical channel input before selecting the channel type. I've seen this when channels are duplicated by copying voltage channels. You can copy the VI but not its inputs. Set the channel type to temperature and then connect a physical channel control. It's unclear if this is what happened, but it is something to keep in mind.

First, you must have a signal connected to the channel. If you leave them unconnected, they will float to a strange value like 1.4 volts. If you are getting started and your sensors have yet to be connected, wire the inputs to analog ground. If you do, they should read close to zero. Both DAQami and TracerDAQ Pro have a voltage range setting. In the DAQami configuration, select Channels, then click one of the Analog Input channels so that it appears selected. Next to it will be a voltage range and a unit selection. In TracerDAQ Pro, choose DAQ Hardware Settings from the Edit menu. Use the DAQ Range/Mode column to change the voltage range.

Have a look at v_out.py and ULAO01.py. These two examples will work with your device. Outputs can be set with either the v_out or the a_out function. The v_out function takes floats for data and a_out an integer. data_value = 3.0 channel = 0 ul.v_out(board_num, channel, ULRange.UNI10VOLTS, data_value, 0) You could use a_out_scan, but the rate cannot exceed 100 divided by the number of scanned channels. Underneath, it uses a_out to update the channels. However, it has a SIMULTANEOUS scan option that can be used to update all the channels simultaneously.

They are simple 2x20 40-pin female stacking connectors. They are inexpensive and available on Amazon. Here's an Amazon link. A slightly taller version is also available, but it will require slightly taller standoffs.

Could you share the requirements? For instance, how many channels are required, and how quickly will they be able to sample? Do you require channel isolation because you will attach grounded thermocouples to metal surfaces? A grounded thermocouple has the bare wire exposed at the temperature end. Is the furnace electric, and what is the temperature range? Remember that I'm not an expert in measuring temperatures in a belt furnace.

If you were writing a program using Python or C/C++/C#, I recommend using the external clock instead of the external trigger. The external trigger starts an acquisition, while the external (pacer) clock input controls sampling. Unfortunately, neither the trigger nor the external clock is supported when using MCC devices and the MatLab Data Acquisition Toolbox. Contact the Mathwork if you have questions or need support. Another approach is to access our API from within Matlab. The following provides a brief example of what I mean: https://digilent.com/reference/daq-and-datalogging/documents/using-ul-for-dotnet-with-matlab To enable the external clock, include ExtClock in myscanoptions: myscanoptions = MccDaq.ScanOptions.ScaleData | MccDaq.ScanOptions.ExtClock; The UL Help documentation download can be found here: https://digilent.com/reference/software/universal-library/windows/start

Use the DAQami software.

Please provide a list of the MCC devices you will be using.

DAQami is newer than TracerDAQ Pro, but they both have their place. TracerDAQ supports most MCC devices, including PCI boards, while DAQami primarily supports USB devices, but not all of them. DAQami has support for Analog & Digital Input/Output. TracerDAQ Pro has no Analog or Digital output - only input. However, TracerDAQ Pro has more triggering options and you can schedule when to acquire data.

Could you provide more information, like what software you used to enter 7A and what it is for? Many customers use the DAQami program to ensure their devices are working. You can request a free activation code or use it as is for 30 days.

Your Windows 7 64-bit system uses the old way of driver signing. So, the solution is to use an older version of InstaCal before the signature upgrade. Uninstall InstaCal, and once this is done, use the following link to install version 6.55: https://files.digilent.com/archive/InstaCal/Archive_6.55/icalsetup.exe

It is impossible to connect both to appear as a device with twice the number of channels. However, you can use both in the same program, which means there will be two buffers to manage. The data buffers can be synchronized if you use the clock from one device to clock the other device. Configure both using the AInScan function. Information about this function is in the UL Help document. Configure the first device to scan the channels, and when it begins, the scan clock will appear on AICLKO. Configure the second device to use the external clock scan option. It will wait until the clock appears before it begins. You'll need to configure the second device first; otherwise, the clock could run before it is ready. Using a short wire, connect AICLKO on the first device to AICLKI on the second.

It is easier to use d_bit_out instead. When using d_bit_out or d_bit_in, use FirstPortA exclusively. These functions write or read individual channels. I modified digital_out.py to use d_bit_out and attached it below. It configures both ports as output and sets each bit individually. Notice the bit numbers are 0 - 15. PortB are bits 8-15. Configuring the ports resets their state, so configure them early in your program before you read or write them. digital_out.py

I have attached the UL Redistribution PDF, and the minimum InstaCal installation program is https://files.digilent.com/downloads/InstaCal/icalsetup.exe. The PDF lists the necessary files for a custom installer program. Use a program like 7-Zip to extract icalsetup.exe to gain access to the driver folders and other necessary files described in ULRedistribution.pdf. Ignore the download links, as they are outdated. The attached VB6 DaqDevDiscovery01 example program will demonstrate how to programmatically discover the device (without InstaCal) and get the serial number (UniqueID). For additional information about the UL API, refer to the UL Help document. ULRedistribution.pdf DaqDevDiscovery01.FRM DaqDevDiscovery01.vbp

If you previously added the miniLabs to InstaCal's board list, its configuration file contains all the required information to run the C# program. If you were to rename InstaCal, it may give you a clue. InstaCal is located in C:\Program Files (x86)\Measurement Computing\DAQ\. Rename inscal32.exe to inscal32.bak. If the results are the same, search your C drive for the following: cbw32.dll => The correct location is C:\Program Files (x86)\Measurement Computing\DAQ\ cbw64.dll => The correct location is C:\Program Files (x86)\Measurement Computing\DAQ\ cb.cfg => The correct location is C:\ProgramData\Measurement Computing\DAQ\ (usually a hidden location) inscal32.exe => The correct location is C:\Program Files (x86)\Measurement Computing\DAQ\ If the search turns up multiple copies of the above files, delete those not in the above location.

The MCC 172 is a non-serviceable item. If it's less than 30 days old, contact your distributor for a replacement.

You could contact Advantech regarding how their utility program works. They should be able to tell you the register/value that must be written to reset the latch. It might be that the inputs are mirrored on the output side (coils), and writing 0 to the corresponding output resets the latch.

It works best if the read request size is set to READ_ALL_AVAILABLE. The inverse of scan_rate is the time for each sample and is very accurate. Keep track of the number of scans read and multiply each by the sample time to generate the timestamps. When read_request_size is set to a positive number, the mcc172_a_in_scan_read function blocks your program and won't return until it fulfills the amount. Depending on the state of the internal buffer, execution times can vary. For instance, when it reaches the end of the internal buffer, it performs an extra read so that the next one starts at index zero. This is all behind the scenes but results in different execution times. There are also unread samples left behind after each read. These slowly build up to an extra read that takes less time.