USB-TEMP modules will not configure in InstaCal

DBraith · July 5, 2023

I have a pair of USB-TEMP modules that have been working great. Used the 'config' function in InstaCal and noted odd/slow response from them. Now in InstaCal it recognizes the boards (i.e. 'refresh' finds them and reports the correct S/N), but when I hit 'config' the program hangs and will not respond. I have tried this on several different computers and get the same results. It's only these two modules, we have multiple other USB-TEMP modules that still work properly. So I suspect the on-board memory/configuration on the modules has somehow been corrupted. Is there any way to reset/repair it?

I'm running the latest version of Instacal on Windows 10 computers.

Thanks

Fausto · July 5, 2023

Hello @DBraith.

What are the serial numbers of your USB-TEMP modules?

Using one Windows 10 system to test your problematic modules, are you able to use other USB-TEMP modules without any issues?

Close InstaCal and cycle the USB connection between the module and the host system. Does the HID Registry Updater appear when you connect those problematic modules and launch InstaCal?

When the HID Registry Updater appears, press the UPDATE button once and then the CLOSE button. Afterwards, restart InstaCal and select INSTALL - CONFIGURE from the top menu. Does it show the Board Configuration window without any issues? Please reply with a screen capture if possible.

Regards,

Fausto

DBraith · July 6, 2023

The S/Ns for my problem devices are 144C951 and 13E4A37

For both these modules the HID registry updater did pop-up; and both modules said they were successfully updated. I cycled the power to (disconnected) both modules before restarting InstaCal; but the problem remains...When I go to Install - Configure the program locks up and the configuration window never opens.

image.png.0fb3b91f35cc21b231e76377013d2af5.png

Fausto · July 6, 2023

Hello @DBraith.

Unfortunately, those two serial numbers are too old to be serviced, because of a legacy PCB design and obsolete components.

Regards,

Fausto

DBraith · July 6, 2023

Can you please clarify? Does this mean the two units cannot be restored to the state they were in just the day before yesterday?

Fausto · July 6, 2023

@DBraith,

The modules are corrupted if the configuration locks up in InstaCal, while other similar modules do not show that issue. You can try connecting those problematic modules to a different PC, but if you experience the same results, then the modules cannot be fixed.

Regards,

Fausto

DBraith · July 6, 2023

Thanks for the clarification...And one more question please: I believe these modules became corrupted when I connected them to a new laptop. I did not get the HID registry popup on the laptop but did get it when connecting them to another computer for checkout. So I'm leery of connecting anything else to that laptop. Would you recommend reinstalling the Instacal software? (I'm not sure, but it may have an older InstaCal version).

Also, I noticed in your forum that you have a software download called 'MCCRegistryFix.exe'. Would you recommend running that on the laptop?

Fausto · July 6, 2023

@DBraith,

On your target Windows system, disconnect the problematic USB-TEMP module. Uninstall 'InstaCal and Universal Library for Windows' via Windows Control Panel - Programs and Features. Next, delete any related leftover folders.

C:\Program Files (x86)\Measurement Computing\DAQ

C:\Users\Public\Documents\Measurement Computing\DAQ

C:\ProgramData\Measurement Computing\DAQ

----------

Restart your system and then download the latest MCC DAQ Software, from https://www.mccdaq.com/Software-Downloads

Install the MCC DAQ software and then reconnect your problematic USB-TEMP module. Afterwards, launch InstaCal to determine whether or not the issue has been resolved.

Lastly, which forum post referenced the 'MCCRegistryFix.exe'?

Regards,

Fausto

DBraith · July 6, 2023

I found the link to it here: https://kb.mccdaq.com/KnowledgebaseArticle50499.aspx?Keywords=Windows-8&Keywords=Windows-8

Fausto · July 7, 2023

@DBraith,

You should be using the latest version of InstaCal and Universal Library for Windows. The MCC DAQ Software installer is available via the following link. https://www.mccdaq.com/Software-Downloads

Therefore, it is not necessary to download and run the 'MCCRegistryFix.exe' utility.

Did you uninstall InstaCal and then download the latest version?

Regards,

Fausto

DBraith · July 10, 2023

I deleted all Measurement Computing programs on the suspect laptop, then downloaded and reinstalled the 'InstaCal and Universal Library for Windows' to make sure I had the latest version. The HID updater did popup on first run of Instacal; and the updater said the update was successful.

However, still no luck communicating with the two modules. Both are recognized, with the correct SN; but both still hang whenever Config is selected. I've tried it on multiple PCs, including the laptop where the trouble started.

Is there anything else to try, or a both these modules dead?

Fausto · July 10, 2023

@DBraith,

Do you have any custom Universal Library applications installed on your systems for the USB-TEMP?

Scan your hard drive for cbw32.dll and cbw64.dll. These two files should only reside in the 'C:\Program Files (x86)\Measurement Computing\DAQ' directory. Remove the files if found in another directory.

Also, confirm the 'ulprops.txt' file is in the 'C:\Program Files (x86)\Measurement Computing\DAQ' directory.

Regards,

Fausto

Fausto · July 10, 2023

38 minutes ago, DBraith said:

The HID updater did popup on first run of Instacal; and the updater said the update was successful.

However, still no luck communicating with the two modules. Both are recognized, with the correct SN; but both still hang whenever Config is selected.

@DBraith,

After the HID updater reported a successful update and you closed the utility, did you cycle the USB cable connection to the module, before launching InstaCal?

DBraith · July 10, 2023

I can confirm that cbw32.dll and cbw64.dll both exist on the hard-drive of the laptop, but only at C:\Program Files (x86)\Measurement Computing\DAQ. A scan of the hard-drive did not find any additional copies.

Also, 'ulprops.txt' does exist in the same folder.

And after the HID updater ran I rebooted the computer.

KMcCutcheon · March 18

I am having the same issue that DBraith has described above. My USB-TEMP module was working fine until I tried to reconfigure it in InstaCal, where it got hung up and would not respond. I have tried this module on a different computer and I am seeing the same thing (both with the latest version of InstaCal on Windows 10). I have another USB-TEMP module that works fine on both computers. The problematic serial number is 1675C79.

When using 1675C79, the HID Registry Updater did appear and I cycled the USB connection after updating. After opening InstaCal and letting it get hung up, if I remove the USB cable from the USB-TEMP, the Board Configuration window pops up (this behavior was not described above). I can then configure it, but it will not save unless I pull the USB cable again. Once plugged back in, the configuration saves. However, in DAQami, it gets hung up once I start an acquisition. I tried using a different cable, and I also removed cbw32.dll and cbw64.dll from an incorrect directory. I confirmed the 'C:\Program Files (x86)\Measurement Computing\DAQ' directory contains the correct files, but I have seen no change.

Is there anything else that can be done to salvage this USB-TEMP? Is this serial number too old to be serviced?

Fausto · March 18

Hello @KMcCutcheon.

With the problematic USB-TEMP connected directly to a USB port on the target Windows 10 system, close InstaCal, DAQami or any other device communicating with the USB-TEMP. Browse to the 'C:\Program Files (x86)\Measurement Computing\DAQ' directory, right-click on the 'HIDRegUpdater.exe' file, and select 'Run as administrator'. (If your Windows user profile does not allow access, then reach out to your IT Dept for assistance.) Follow the steps for the HID Registry Updater utility. Close the utility software and cycle the USB cable connection to the USB-TEMP. In the 'C:\Program Files (x86)\Measurement Computing\DAQ' directory, right-click on the 'inscal32.exe' file, and select 'Run as administrator'. Is the USB-TEMP recognized in InstaCal and can you configure the channels? If not, then the next step would be a repair RMA quote.

Which version of InstaCal are you using?

Regards,

Fausto

KMcCutcheon · March 18

After following those steps, the USB device is recognized but not configurable. I am actually using version 6.55 (not the most recent version as I had previously stated, my apologies).

Fausto · March 18

Please close InstaCal and install the current release over your existing version.

https://digilent.com/reference/software/instacal/start

Retest the USB-TEMP configuration after.

KMcCutcheon · March 18

After installing InstaCal 6.74 there is no change in the behavior of the USB-TEMP Module.

Fausto · March 18

@KMcCutcheon,

I sent you a private message for a RMA repair quote.

Sign In

USB-TEMP modules will not configure in InstaCal

Question

DBraith

19 answers to this question

Recommended Posts

Fausto

DBraith

Fausto

DBraith

Fausto

DBraith

Fausto

DBraith

Fausto

DBraith

Fausto

Fausto

DBraith

KMcCutcheon

Fausto

KMcCutcheon

Fausto

KMcCutcheon

Fausto

Create an account or sign in to comment

Create an account

Sign in

Browse

Activity