the more i think about this, the more complex it gets :-)
Hi @HKJ, you've clearly done a great job supporting such a wide range of hardware!
It is not me alone, I got a lot of help from people here (You can see a list on the About page).Is the project on github? Sorry if its in the thread somewhere.
No.
Also, I was wondering why you didn't build upon Sigrok, say a new UI and/or adding drivers for missing hardware?I wanted the program simple to install and use. The program is in Java and works on multiple platforms with one executable file, you could not do that with Sigrok.
I was hoping to find remote control/logging in a client-server design: backend interfacing with the h/w, say on a R-Pi (which could even be built into test equipment) and the client web / mobile...
I may at some time in the future make it possible to use remote serial ports.
If you want to design your own test equipment, there is documentation on how to interface it to TestController.
maybe a bold question, but would it be possible to add a Manson HCS-3300? I've already found some protocol info on: https://sigrok.org/wiki/Manson_HCS-3xxx_series
I presume that means it isn't open source licenced. You'd get a lot more help from others if it was Open Source rather the proprietary. For instance, what happens if you become too busy with other things in your life to support it, or if it becomes really popular the amount of support, bug fixing etc will become too much of a burden?
Sigrok says it has cross platform build, still, it looks a bit rough at the edges and has plenty of nasty use of macros in the code (just took a quick look), I guess to make it cross platform.
maybe a bold question, but would it be possible to add a Manson HCS-3300? I've already found some protocol info on: https://sigrok.org/wiki/Manson_HCS-3xxx_series
Anybody with a bit of time can add that supply using a ascii driver.
Documentation: https://lygte-info.dk/project/TestControllerConfigDevice2%20UK.html#Non-SCPI_ascii_devices_(Ascii)
Ok, I just had a look into that, but I need more info on the subject to be able to implement this. I've looked at the Ascii Skeleton and a lot of questions. For example, I know the results of a GETD command (VVVVCCCCS\rOK\r) are in mV and mA. There is a definition value Voltage V ... which could handle this, but what does D0..D6 mean?
I do generally maintain my software for a long time and even if I stop maintaining it, it will still continue to work.
Could you cut it in two, and have the device files in git?
Most additions are about that.
Ok, I just had a look into that, but I need more info on the subject to be able to implement this. I've looked at the Ascii Skeleton and a lot of questions. For example, I know the results of a GETD command (VVVVCCCCS\rOK\r) are in mV and mA. There is a definition value Voltage V ... which could handle this, but what does D0..D6 mean?
D0..D6 is 0 to 6 decimal places when showing the value, you will usually use the number that match the display on the device.
To adjust the input values you usually uses a :readmath: function. It is called #askValuesMathFormat for #askValues, but :readmath: nearly everywhere else.
You may also want to look at the SCPI configuration page, it contains a lot of common stuff for all configuration files: https://lygte-info.dk/project/TestControllerConfigDevice%20UK.html
The general idea is to get a connection to the device, then you can try/test commands from the command line.
I'm starting to grasp a vague idea... One practical question. With one ASCII command I get the complete status in one string with numbers. First 4 are V, then 4 for A and then a 0 or 1 for CC or CV.. How would I split this into the different values?
To me it looks you need to use askValues to configure which values to get en use scpiCmd to define how to get those values. But in this case I only need one command to get all the values in one go
Any of you wise testcontrol stars out there who could help to make, or even come with suggestions on how to make the device file?
Is it possible that this program doesn't work with the Brymen BM869S in 500k mode?
I can get it to read and log in 50k mode fine, and about 5 times per second, so according to the screen refresh, but when I switch the meter in 500k mode the readings are very slow, irratic (and if logged, in 50k mode) and it also won't reconnect in 500k mode.
I plan to push for using it at work,
and at the same time looking for a donate / paypal info ?
how about you add a little about, donate-ware info, so if people feel this help their work, save time, add value to their work,
they can express their gratitude by paying a few $ your way
I cant find any such menu in the program ?
1. I first tried #fftView 3 for the third column and the the console complains "failed due to null" but the window pops up anyway. I (now) get that the argument should be the table column name, but since the fft window actually pops up it is confusing to have the error say "failed". I then tried just #fftView with no arguments and the console gives no error message and the window does not pop up. I would think there should be a console error if the window does not pop up. For me it would be more convenient if it did pop up and then I could manipulate it manually to get what I want.
2. How does this fft work? Normally fft code assumes a constant sampling period. But TC sampling period varies. So, does the fft assume constant sample period at the log interval set point?
3. What would the fft do if the logging starts at one log interval and then TC adjusts the log interval slower due to slow responses? In other words what doe this fft do with a Table record with two or more different set points for the log interval?
4. Is there a limit to the number of points in the Table that the fft can be taken for? Related question, does this FFT always use all the points or is it an fft that always truncates the data to the first 2^n points for a binary number of sample points?
4. I suggest adding a button on the Chart view to open the fftView. It is a little awkward to have to go to the console and type in #fftView + arguments. Great for scripts, not so much for user actively working on the data.
Generally you place all the tx/rx commands in scpiCmds and then you use the commands you have defined there in the rest of the definition.
You will also want to add commands to set voltage, current, on/off. Adding interface function can be useful for automatic testing.
1. The device responses with 2 lines first line contains the data (almost always numbers) then a <cr> then "OK". At the moment i use txrx? which seems to ignore the second line, but I'm not sure that's the correct way.
2. On/Off is reversed on the device 0=on 1=off. This works for the buttons on the 'Setup' page, but the red square does not work anymore.
3. Is it possible to calculate for example the Ah and/or Wh in the driver ander report that as Current Values as the device doesn't report those by itself.
1. The device responses with 2 lines first line contains the data (almost always numbers) then a <cr> then "OK". At the moment i use txrx? which seems to ignore the second line, but I'm not sure that's the correct way.Use txrx2? instead
1. The device responses with 2 lines first line contains the data (almost always numbers) then a <cr> then "OK". At the moment i use txrx? which seems to ignore the second line, but I'm not sure that's the correct way.Use txrx2? insteadI tried that, but how to get rid of the <cr>OK ?