Leif N.
The delivery is quick
The delivery is quick, the card is good but the price is a little to high.
LabJack produces Low Cost USB/Ethernet/WiFi based measurement and automation devices providing PCs with analog inputs/outputs, digital inputs/outputs, and more.
LabJack (labjack.com) has 276 customer reviews on Five Star Index, with an average rating of 4.7 out of 5.
Is this your business?
Correct your details and reply to customers in public. Both are free.
Claim this listingShowing 27 reviews with 4 stars · Clear filters
Leif N.
The delivery is quick, the card is good but the price is a little to high.
Soner B.
Labjack - great products, great product information and I hope great support (but I have yet to put it to the test which I guess is a good thing). Only thing that I would have changed in the buying process was a heads-up on the import duties, as the use I am making of the equipment (wastewater plant management) is actually import duty exempt - providing you make the import declaration correctly when you send it - meaning I could have avoided a $350 AUD import duty charge.
Response from LabJackJan 10, 2024
Thanks for your feedback. Hate to hear that you had to pay unnecessary import fees ... sounds like you made an involuntary donation to your fine country. We are not familiar with anything we can do on our end related to duty exempt international recipients, so we will contact you by email to discuss.
Walter
What was great was that you had the items to ship, what is not so great is the length of time to actually get orders delivered.
Response from LabJackMay 26, 2023
Hi Walter, thanks for the feedback. Our records show your order was shipped the same day and delivered the following day. If that wasn't the case let us know so we can contact the shipping carrier. [email protected]
Alan G.
The LJtick-R device doesn't give stable enough data for my application (measuring R around 25 ohms). I received a call from tech support that confirmed the device will not work well to measure such lo resistance. So I built my own interface for the measurement, which is working better.
Response from LabJackFeb 23, 2023
Thank you for taking the time to provide feedback. We apologize that you did not get a reply, but we can't find that we ever received a message. You did have phone conversations with a couple of us today so we could try and fix any outstanding problems. You have a resistance around 20 ohms and want to resolve changes of around 0.0005 ohms. We looked and discussed and agree that is beyond the ability of the LJTick-Resistance-1000, even with the T7-Pro. The circuit you have set up yourself is working well for you and improving on that would likely require a custom circuit involving at least 1 precision op-amp. Not getting a reply is never okay. Whether you use direct email, comment in offline chat, or our contact form, they all result in an email to our main support box. We respond to most emails the same day, so if you have not heard back in a day or 2 there is definitely some problem. If this ever happens to anyone please contact us again and if you don't hear back quickly get on chat or call us to figure out what is wrong with the email. We really hate that someone would ever think they contacted us and then get no reply. As of this writing, our live chat hours are Monday through Friday from 9-11 am and 2-4 pm, Denver time. Yes that is only 50% of business hours, but we find that this schedule allows us to efficiently provide real support (Colorado engineers) and never use a chat robot or overseas support.
kalpakpune
Happy ......!
Leslie G.
Review of U3-HV. The physical connector interface (screw terminals) is very convenient. I set this up for lab testing using LabJack Python. Mine is a very simple application: read an analog input, test the value, and signal if that value changes. A single test runs for 50 hours, so a reliable device is required. I found the Python program crashed randomly with “Got a zero length packet” when reading an input from a circuit powered from the U3 itself. I had to invest significant time to realise this was a systematic problem with the U3 interface itself. It throws exceptions which you have to catch then discard. Labjack tech support didn’t give an example exception handler or report back as to whether other units have the same problem (despite me sending them test code to do so). // Update: A third support person did use the code, and reported no error. Connecting up a single output to the system under test increased the exception count to hundreds during the course of any test run. I had to opto isolate the output to reduce the common mode digital noise on the interface, thereby reducing the exception count down to a level around 100. Basically I was having to do a lot of work to make the device function properly. Given that I have 25 years experience as a designer of “big box” acquisition systems, I am disappointed with this device. // Update: it works fine IF and ONLY IF you use an exception handler to throw away the null-packet errors. // Update: I had some useful interaction with a third support engineer, so I have upgraded the review from 3 to 4 stars. My new conclusion is that the driver software is "hyper vigilant". It arguably shouldn't report the null packet errors. You absolutely need an exception handler (for 'self-created' problems) and then the device is fine. They have said they will update the examples which is a GOOD RESULT for future customers.
Response from LabJackJan 27, 2023
***Jan 27, 2023 Hello Leslie, Thank you for taking the time to provide feedback and I'm sorry to hear you had a less than stellar experience. Before researching your communication with us, here is some initial feedback on your comments here. We will investigate further and we will likely follow up directly and perhaps also with an update to this trustpilot review response: 1. You are using the U3-HV and found the screw terminals very convenient. ***Glad to hear they fit your needs. They are convenient and reliable for most applications, but for those that need other options we have OEM versions of our devices and most of our devices have a mix of screw terminals and cable-friendly connectors. 2. You repeat the following for 50 hours using your own Python program: Get a single reading from 1 analog input, control 1 digital output. ***Sounds routine. Many customers do the same and in fact running for years unattended is routine. 3. Your Python program crashes randomly upon getting a "zero length packet" error. ***Does not sound acceptable. There are certainly things that can cause a function call to return an error, but our driver should not cause your program/computer to crash. We will follow up. 4. LabJack's driver returns errorcodes/exceptions that the user must catch and decide what to do with. ***This sounds normal and expected. 5. Our Python examples do not demonstrate error handling. ***All our examples should check every call for an errorcode, and if there is an error, stop and show the error. I myself am not particularly familiar with Python, but will take a look at our examples and follow up. 6. You sent us example code that causes the problem for you, but did not get a response from us on what the code does when we run it. ***Not getting a response from us is never normal. We will follow up. 7. You had to put an isolator between the U3 digital output and your system to reduce the number of errors. ***If you are getting USB errors related to what is connected or not-connected to the U3, it suggests a serious electrical problem or major EMI transients. This is not a good way to operate, but can happen with some systems and needs to be tackled. Certainly Ethernet is superior, but even with the consumer grade USB port found on any computer, things can be done to help stop your USB host from having trouble. ***Update Feb 2, 2023 2. The customer quickly added error handling and the application now runs indefinitely without human intervention. 3. The crash is actually just the python example stopping and displaying an error. This is actually the expected behavior of the simple examples. 5. Some of our examples show the use of a try-except block where the user can decide how to handle errors, while other examples just stop on any error and display the error. We will add error handling comments to all examples and perhaps also show at least 1 try-except block in every example. 6. We did not run the test code when it was first sent, but we have run it now and at our office it runs indefinitely without any errors. We should have run this when first sent as it was useful for the customer to know that the problem is unique to their environment. 7. Further customer testing has shown that even with nothing connected to the U3 they get perhaps 1-2 errors a day. This is not normal and suggests the environment is particularly hostile or the USB host is not quite right. Our USB Communication Failure app note applies here.
Gary P.
Have always found the support great. I would have given 5 stars but think you did NOT improve the website in changing. And I had to sign up again...
Response from LabJackNov 9, 2022
Thanks for the kind words and feedback Gary. While there is always room for improvement, I apologize our new website was more work/time for placing your repeat order. Thanks for your ongoing partnership with LabJack!
rich.maddox
First time Labjack user. The first datalogging project involved using the SD card to log temperature/voltage data. At first documentation was a bit confusing regarding how to access the SD card. Customer support was able to get me the SD card utility to read out the logged data which was helpful. The lua scripting language was easy to get voltage/temperature logging implemented. Noticed that there is an intermittent "hardware" failure indicated when the unit is connected to Kipling. The docs indicated that there is an ADC test performed when the unit is powered up. It seems half the time this error is reported so not sure if this is a real problem or not. Will need to log some real data to see how the unit performs.