Howdy we have been having troubles with a chamber locking up on us. Not trusting how it handles the temp when this happens we wanted to monitor it seperately, we had a U12 Labjack on hand with EI-1022. After familiarizing myself with it, installed latest tools from website (got them last week) on spare PC configured it up and started logging.
2 attempts now; first time about 36 hours in, second attempt about 40 hours in LJlogger reports in windows it is not responsive and I have to close the program and restart. As expected with program dead U12 stops working.
My setup is very simple:
1- EI-1022 setup for differential is using lines 0 and 1, then 2 I use to calc C and 3 I calc F.
2- Only other thing going on is in Triggers I setup a heartbeat on the U12 LED to monitor it easier. Rather simple trigger runs for 2 seconds turns off LED for 0.5 seconds. Its blinking its working basically.
At the very least I need this to run over a weekend. Any ideas on what could be killing the program, guessing memory leak of some sort.
Thanks for any help.
.png%3Fitok=PHGBxf6M "EEV Blog Reviews LabJack T7-Pro & Software Tools")
.jpg%3Fitok=B1YcuDFK)
.png%3Fitok=Ybt-OlgU "LabJack + JEDI One Can Create a Powerful Distributed DAQ Ecosystem")
Have not heard of anything similar. Please send/post a screenshot of the main screen and configure screen so we can set up the same and run it here.
What is the minimum you have to do to get going again?
https://labjack.com/support/app-notes/usb-communication-failure
I have to force close the program and restart. That mostly does it the LED heartbeat seems to start up totally off have to edit Trigger to get it going again.
See pictures of setup and included PC details, Logger tells me op sys is Vista when PC is Win 7 Prof.
Let me know if you need anything else. Really like to get this working right, a couple of these (well the T7 Pro version) would come in handy, but no one will buy anything if keeps crashing.
We are currently running some tests to try and reproduce your issue. We will follow up here in the next few days.
Hello just to update ran over weekend and got about 28 hours, then ran again from yesterday morning it went about 24 hours. I took a screen cap of the end error in case its of some help, but its the usual not to helpful Windows error.
Thanks
We were able to reproduce the issue and we are going through some further troubleshooting.
Just wondering if there has been any new information on this. Thank you
Hello, just wondering if you have gotten anywhere with this issue, thank you.
We are seeing that disabling selective suspend seems to cause the problem, and are looking into it further.
Thank you for your patience. We will keep you updated as we continue to troubleshoot this issue.
Please update when you can I appreciate it.
After further testing, we have found that disabling Selective Suspend in Windows causes this problem with the U12. We will update documentation to reflect this.
Testing UD and LJM devices (all our other devices), we did not see any problems whether Selective Suspend was disabled or enabled.
The U12, our original devices released in 2001, is unique compared to our other devices in that it enumerates as an HID device and uses the operating system's HID drivers. Best guess at this point is that some Windows update has introduced a problem with Selective Suspend and HID devices, so just leave Selective Suspend enabled which is the default.
The following could be the same issue:
https://answers.microsoft.com/en-us/windows/forum/windows_10-hardware/us...
I was a little confused on your statement of, "...we have found that disabling Selective Suspend in Windows causes this problem with the U12." while the MS link you have tells me to DISABLE the selective suspend. I assumed DISABLE is what we wanted as every PC I looked at has them by default ENABLED. So I set both to DISABLE and ran test over weekend.
With weekend had some time to setup a test run see how this works and it failed basically the same as before. Ran for about 40 hours taking readings every 60 seconds and failed. Sunday morning Data kept being written to file but it was not getting info from unit anymore. Would occationally see unit send what looked like good infor every few hours but that was all. Attached the log for for you if you wish to check it over. I did insert a column that converts time/date to readable values.
You should leave selective suspend enabled, which should have been the default configuration when Windows was first installed. Disabling selective suspend is what we have observed causes the issue.
Well ran the test over weekend with them DISABLED. As they were ENABLED to begin with. So Selective Suspend does not appear to be a problem on or off it made no difference to my attempts.
On chance I am somehow in wrong area, attached a picture of the settings I am changing this was right after ENABLING them again.
Yes that looks like the right setting, but looks a little different than my machine as shown in the attached screenshot. I'm thinking you have a laptop, and we did not test on any laptops, so there might be another setting in play. We will find some laptops to test on to see anything different than what we saw on desktops. Also, all the machines we tested on were likely Windows 10, so will have to see if we can find anything with Windows 7.
On your end, some things you could try to help isolate the problem:
Try different computers (with selective suspend enabled).
Test with nothing connected to the U12, except USB.
Test in an electrically quiet location, like on a desk in an office.
We ran a test many days without problem on a Windows 10 laptop. On another laptop with Windows 7, we did see the problem happen over the weekend, so we will now focus on that laptop and try to see if this is a general problem Windows 7 has with HID devices (like the U12), or is related to other power settings on that laptop.
Hello, jsut wondering if there are any updates to this. Thank you.
Sorry for the delay. We are still running tests on this and trying to narrow down the problem. It takes some time as we only have 1 old machine with Windows 7 and it takes at least a few days to decide if there is no problem. Currently it seems that the problem only affects LabVIEW (ljlogger.exe is written in LabVIEW 7.1) on Windows 7. As Windows 7 is officially no longer supported by Microsoft, there is likely no fix possible for whatever problem we isolate, but perhaps a workaround. Perhaps there are some settings we can change in Windows 7, or perhaps we can build ljlogger.exe in a different version of LabVIEW.
Howdy just checking to see if there have been any updates.
In mean time I did get my hands on a Win 10 Laptop and it did seem to run much better but still seemed to I would guess hit a memory leak issue but I am not sure. I started testing it 4/30 and have let it go since then. Checked on it this morning and LED was dead. PC was dog slow noticed was still writing to the log and was able to go into LJLogger and start a new data file just real slow. Ended up rebooting the PC and this seemed to get everything going again. Looking in the original data file I got good data from.
4/30/2021 9:54:16 AM
5/9/2021 8:26:29 PM
9 days 10 hours and 32 minutes.
After the 5/9 8:26 the data was effectively Blank. Was logging data every minute so was alot of data but was in no means excessive amounts the DAT file was only 1495 kb. Only other thing was the LED heartbeat cycle 2 seconds then off for 0.5 sec.
Much better then we had been getting and much more useful but still surprised its still not running. Any thoughts on this? Thank you again for your help.
Thanks for the info. Did you have Selective Suspend disabled? We have not seen this issue on Windows 10 with Selective Suspend enabled.
Selective Suspend was enabled for both Battery and Plugged in. Have disabled both and started things again.
Retried with Selective Suspend Disabled as expected did not last, went barely a day before failing. Will re-enable and let it run over weekend.
So with WIN 10 selective suspend Enable have seen by far the best results. With the setup I have detailed.
This is stand alone Laptop sitting on desk with nothing else connected to it other then wireless mouse.
Ran over weekend with Selective Suspend Enabled looks to have failed little over 24 hours later see LOG attached. When I went into Task Manager LJLogger was not responding I had it give me a Dump if that is of any use to you also included with the log.
Thank you
That is new for us as we have not seen any issues on Win 10 with SS enabled. Maybe it is something unique to a laptop as most of our Win 10 testing was on desktops? Appreciate the added information and we are still running tests.
We are intent on figuring out this issue. That might mean a comprehensive solution, or it just mean being able to specify what conditions are not supported. For the purpose of this forum topic, though, I want to reiterate that this issue is unique to the U12 which was released 20 years ago and uses a different type of USB driver compared to all our other devices. We have not seen any issues with our other devices.
After further testing, we discovered that there was a memory issue specific to LabVIEW 7.1 that was causing LJLogger to fail. We rebuilt the logger under a newer version of LabVIEW and could not reproduce the issue.
The following link is to a basic installer that should install the necessary LabVIEW runtime and replace the current version of LJLogger on your system with the new version. I also attached a zip file with the executable and support files by themselves.