Products > Test Equipment
Program that can log from many multimeters.
HKJ:
--- Quote from: motato on March 15, 2023, 05:10:55 pm ---Thank you. Unfortunate to need the resources of an entire OS or VM for one app, but I also completely understand.
--- End quote ---
Do a windows emulator use all resources, TC do not?
--- Quote from: motato on March 15, 2023, 05:10:55 pm ---I see in the About section "Uses hid4Jave to scan for HID devices (Could not get reading to work)," so sounds like the "can't read" behavior is not entirely unexpected. If I can find/make time, maybe I can dig into why hid4java won't work, or maybe look into http://usb4java.org/
--- End quote ---
I would be nice.
--- Quote from: motato on March 15, 2023, 05:10:55 pm ---Anyone have luck attempting to run TC on Mac using Wine? I made a quick effort to run the Brymen app in Wine, but it didn't even get to the point of recognizing the device.
--- End quote ---
I believe some people has posted, in this thread, about using windows emulator to run TC with Brymen, but I do no remeber if it was on Linux or Mac.
jmurray:
Hi HKJ,
I might be missing something: Is it possible to use the matchBitsList function as a formula on the math page? I've tried a few variations and it keeps getting disabled and highlighted in red.
I'm trying to return different short strings based on the bit specification to make it easier to write a script.
HKJ:
--- Quote from: jmurray on March 17, 2023, 05:32:18 am ---I might be missing something: Is it possible to use the matchBitsList function as a formula on the math page? I've tried a few variations and it keeps getting disabled and highlighted in red.
I'm trying to return different short strings based on the bit specification to make it easier to write a script.
--- End quote ---
It is, but all formulas must return numbers, not strings. You can do that with matchBitsList().
All regular values (i.e. values that goes into table or chart) must be numbers. You can use deviceRead() to get the string answer directly from the device. For settings you can define get/set functions and they can return strings https://lygte-info.dk/project/TestControllerConfigDevice%20UK.html#A_generic_interface.
Curious:
Hi HKJ,
I finally got TC to work great for running battery capacity tests with East Tester 5410 Electronic Load, see https://www.eevblog.com/forum/index.php?action=post;quote=4765331;topic=228058.25
So now wanting to plot I-V curves for Solar Panels. Thought that would involve many days of understanding how to write scripts, but then saw your "Parameter Sweep" pop-up, awesome!
Practicing usage, I started with Parameter sweeping (in Constant Current mode) current set point from 0-1.0 amps in 100 steps while recording a battery voltage. I'm having a strange problem running parameter sweeps while logging..randomly TC reports Current and voltage dropping to precisely 0.00, then recovering to actual values. Please see attached Chart image, as well as Parameter Sweep popup windows images. The ET5410 LCD display does NOT show 0volts, 0amps but actual values. Any idea why TC is randomly recording 0, 0? I'm guessing there might be a USB communications collision, since log sampling interval >=10 seconds seems to mostly resolves the problem, but takes much time.
Thanks!
HKJ:
--- Quote from: Curious on March 22, 2023, 02:12:41 am ---Practicing usage, I started with Parameter sweeping (in Constant Current mode) current set point from 0-1.0 amps in 100 steps while recording a battery voltage. I'm having a strange problem running parameter sweeps while logging..randomly TC reports Current and voltage dropping to precisely 0.00, then recovering to actual values. Please see attached Chart image, as well as Parameter Sweep popup windows images. The ET5410 LCD display does NOT show 0volts, 0amps but actual values. Any idea why TC is randomly recording 0, 0? I'm guessing there might be a USB communications collision, since log sampling interval >=10 seconds seems to mostly resolves the problem, but takes much time.
--- End quote ---
You might be able to ignore the problem by using the configuration "Delay timeout by x samples" and use a value of 1 or 2 for x.
The actual problem may very well be a communication problem where the load has trouble with the intermixing of settings and readouts.
A check in the definition:
--- Quote ---#cmdSetup number Set_I_
:read: CURR:CC?;
:readmath: trim(replace(value,"R",""))
:write: CURR:CC #;[300];
:tip: Set CC mode current value
Amps 0 40
:updatemodechange:
--- End quote ---
Shows a 300ms [300] delay after setting a new current value, you can try increase that value and see if it helps
When looking for communication issues using debug mode may help show it, but be aware that debug mode may slow down the communication and this by itself can fix the issue (The code is written so debug in itself do not slow down the code by any significant amount, but the increased workload on the computer may).
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version