Program that can log from many multimeters.

[Messtechniker]

After having successfully integrated this ADC within Profilab - see fig. ,



TC integration is next.

With this rudimentary definition file



the ADC is found and the channels 0 to 9 are listed. Yay!

Next I'll  probably need your ascii floating point parser
(together with a few hints on how to configure it).

[HKJ]

Next I'll  probably need your ascii floating point parser
(together with a few hints on how to configure it).

http://lygte-info.dk/pic/Projects/TestController/TestController.jar
It is version 2.23 and it may be some time (Usually not more than an hour) before you can download it, please check you got the correct version.

The floating point format uses the letter e, this means you will need 10 of 111e5 on the #rxFormat line where the 111 is replaced with the actual position in the message of the number.

[Messtechniker]

OK. Now running V2.23. But still in trouble 

#rxStart 1                                                                                                     Reading should start with char 1
#rxLength 170                                                                                              Reading should end with char 170
#rxFormat 10e5 20e5 30e5 40e5 50e5 60e5 70e5 80e5 90e5 100e5         Reading extracts char 10 to14 20 to24 etc.

#askValues Values?                                                                                     
Should insert the measured values the 10 bins of "Current values"

What is wrong? All I ever get is the response :
 ;; ADC10: Rx as numbers <No data (timeout?)>
 in the Commands window

In the debug windows I can see this data coming in:

;; COM8: Rx: 31 32 33 39 09 31 2E 30 30 31 56 0D 0A 43 48 31 3A 31 32 33 38 09 30 2E 39 39 36 56 0D 0A 43 48 32 3A 31 32 33 39 09 30 2E 39 38 32 56 0D 0A 43 48 33 3A 31 32 33 33 09 30 2E 39 39 33 56 0D 0A 43 48 34 3A 31 32 34 30 09 30 2E 39 39 39 56 0D 0A 43 48 35 3A 31 32 33 32 09 31 2E 30 30 30 56 0D 0A 43 48 36 3A 31 32 32 33 09 30 2E 39 38 36 56 0D 0A 43 48 37 3A 31 32 33 37 09 31 2E 30 30 31 56 0D 0A 43 48 38 3A 31 32 33 37 09 30 2E 39 39 36 56 0D 0A 43 48 39 3A 31 32 33 38 09 31 2E 30 30 33 56 0D 0A 0D 0A 43 48

[HKJ]

OK. Now running V2.23. But still in trouble 

#rxStart 1                                                                                                     Reading should start with char 1

Reading start at CH0 text:

#rxStart CH0

According to the table you posted first number is a character 10, next number 17 characters later.

[TheDefpom]

I found a small bug in the Siglent SDM3065X device profile, one of the resistance ranges were not correctly specified, it was setup as a 2MOhm range, when it is actually a 1MOhm, I have corrected the issue in the definition file, the updated file is attached.

[Messtechniker]

Got it! ADC10F103C now works with TC.



Definition file enclosed

@HKJ:Thanks formaking this happen.
You may either include this definition file in the mainstream definition file folder
or on your DIY page.

  ADC10F103C.txt (0.75 kB - downloaded 83 times.)

[HKJ]

Got it! ADC10F103C now works with TC.

Definition file enclosed

@HKJ:Thanks formaking this happen.
You may either include this definition file in the mainstream definition file folder
or on your DIY page.

I will include it.

One note about the chart:
Right click and select layout.
The select "Sync" page

Here you can combine all scales, to avoid using all the space on scales. Only caveat is that it messes up auto scaling (auto scaling works only on the master curve), use manual scaling to get around that.

[HKJ]

I found a small bug in the Siglent SDM3065X device profile, one of the resistance ranges were not correctly specified, it was setup as a 2MOhm range, when it is actually a 1MOhm, I have corrected the issue in the definition file, the updated file is attached.

Thanks, I will update the definition in next release.

[Messtechniker]

Got it! ADC10F103C now works with TC.

Definition file enclosed

@HKJ:Thanks formaking this happen.
You may either include this definition file in the mainstream definition file folder
or on your DIY page.

I will include it.

One note about the chart:
Right click and select layout.
The select "Sync" page

Here you can combine all scales, to avoid using all the space on scales. Only caveat is that it messes up auto scaling (auto scaling works only on the master curve), use manual scaling to get around that.

Thanks for the hint. So many channels...

Since this worked quite well, I have a BME 280 sensor (temp., rel. humi and atm. pressure) waiting.
TC integration should be similar. Wait and see....

[Messtechniker]

Now to TC integration of the processor output for the BME 280 sensor:

Here the output:



Why does TC stop at this

;; COM5: Rx: <Ut:524288 Up:524288 Uh:32768> 55 74 3A 35 32 34 32 38 38 20 55 70 3A 35 32 34 32 38 38 20 55 68 3A 33 32 37 36 38
;; (COM5) Did not find any match for: Ut:524288 Up:524288 Uh:32768
;; COM5: Close

before it can go on reading?

[HKJ]

(Attachment Link) Now to TC integration of the processor output for the BME 280 sensor:

Here the output:

Why does TC stop at this

;; COM5: Rx: <Ut:524288 Up:524288 Uh:32768> 55 74 3A 35 32 34 32 38 38 20 55 70 3A 35 32 34 32 38 38 20 55 68 3A 33 32 37 36 38
;; (COM5) Did not find any match for: Ut:524288 Up:524288 Uh:32768
;; COM5: Close

before it can go on reading?

Probably because it is looking to an answer from a *idn? command, that is default behavior.
It do not look like a fixed length output, i.e. the Block driver cannot be used.
If it had required a command to get the output the Ascii driver would have worked.
I do not have a good driver for streaming variable length ascii output, but I can make one in a couple of days.


If it is fixed length, i.e. it add spaces to keep the length constant, it can be done with the Block driver.

Can you post a hexdump of the full output (Not as a image).

[Messtechniker]

Here a hex dump of the BME 280 output:

D A D A is at the end before a new run starts.

55 74 3A 35 32 34 32 38 38 20 55 70 3A 35 32 34 32 38 38 20 55 68 3A 33 32 37 36 38 D A 54 65 6D 70 65 72 61 74 75 72 3A 20 20 20 20 20 20 20 20 32 30 2E 37 34 B0 43 D A 4C 75 66 74 64 72 75 63 6B 20 36 34 62 69 74 3A 20 20 20 36 37 34 2E 39 38 36 68 50 61 D A 4C 75 66 74 64 72 75 63 6B 20 33 32 62 69 74 3A 20 20 20 36 37 35 2E 32 34 68 50 61 D A 4C 75 66 74 66 65 75 63 68 74 69 67 6B 65 69 74 3A 20 20 32 35 2E 39 35 31 25 D A 48 F6 68 65 20 FC 62 65 72 20 4D 65 65 72 3A 20 20 33 32 39 37 2E 37 38 6D D A D A 55 74 3A 35 32 34 32 38 38 20 55 70 3A 35 32 34 32 38 38 20 55 68 3A 33 32 37 36 38 D A 54 65 6D 70 65 72 61 74 75 72 3A 20 20 20 20 20 20 20 20 32 30 2E 37 34 B0 43 D A 4C 75 66 74 64 72 75 63 6B 20 36 34 62 69 74 3A 20 20 20 36 37 34 2E 39 38 36 68 50 61 D A 4C 75 66 74 64 72 75 63 6B 20 33 32 62 69 74 3A 20 20 20 36 37 35 2E 32 34 68 50 61 D A 4C 75 66 74 66 65 75 63 68 74 69 67 6B 65 69 74 3A 20 20 32 35 2E 39 35 31 25 D A 48 F6 68 65 20 FC 62 65 72 20 4D 65 65 72 3A 20 20 33 32 39 37 2E 37 38 6D D A D A 55 74 3A 35 32 34 32 38 38 20 55 70 3A 35 32 34 32 38 38 20 55 68 3A 33 32 37 36 38 D A 54 65 6D 70 65 72 61 74 75 72 3A 20 20 20 20 20 20 20 20 32 30 2E 37 34 B0 43 D A 4C 75 66 74 64 72 75 63 6B 20 36 34 62 69 74 3A 20 20 20 36 37 34 2E 39 38 36 68 50 61 D A 4C 75 66 74 64 72 75 63 6B 20 33 32 62 69 74 3A 20 20 20 36 37 35 2E 32 34 68 50 61 D A 4C 75 66 74 66 65 75 63 68 74 69 67 6B 65 69 74 3A 20 20 32 35 2E 39 35 31 25 D A 48 F6 68 65 20 FC 62 65 72 20 4D 65 65 72 3A 20 20 33 32 39 37 2E 37 38 6D D A D A 55 74 3A 35 32 34 32 38 38 20 55 70 3A 35 32 34 32 38 38 20 55 68 3A 33 32 37 36 38 D A 54 65 6D 70 65 72 61 74 75 72 3A 20 20 20 20 20 20 20 20 32 30 2E 37 34 B0 43 D A 4C 75 66 74 64 72 75 63 6B 20 36 34 62 69 74 3A 20 20 20 36 37 34 2E 39 38 36 68 50 61 D A 4C 75 66 74 64 72 75 63 6B 20 33 32 62 69 74 3A 20 20 20 36 37 35 2E 32 34 68 50 61 D A 4C 75 66 74 66 65 75 63 68 74 69 67 6B 65 69 74 3A 20 20 32 35 2E 39 35 31 25 D A 48 F6 68 65 20 FC 62 65 72 20 4D 65 65 72 3A 20 20 33 32 39 37 2E 37 38 6D D A D A

[Messtechniker]

Definition file Ver 0.2 for ADC10F103C.
Added in "Notes" alternative designations for the ADC10F103C pcb.

[HKJ]

Here a hex dump of the BME 280 output:

Thanks, I will make a new driver, it will take a few days.

[HKJ]

Definition file Ver 0.2 for ADC10F103C.
Added in "Notes" alternative designations for the ADC10F103C pcb.

I will update the definition.

[HKJ]

Here a hex dump of the BME 280 output:

I got something working, but it is not finished:
http://lygte-info.dk/pic/Projects/TestController/TestController.jar

Code: [Select]

#idString BME280
#name BME280
#handle BME280
#port comfixedbaud
#baudrate 9600
#driver asciiblock

#rxStart Ut:
#rxEnd \r\n\r\n
#rxFormat .*?([0-9.E+-]+).*?([0-9.E+-]+).*?([0-9.E+-]+).*?([0-9.E+-]+).*?([0-9.E+-]+).*?([0-9.E+-]+).*?([0-9.E+-]+).*?([0-9.E+-]+).*?([0-9.E+-]+).*?([0-9.E+-]+)

#askValues Values?
#askValuesReadFormat xxxfxfxxfx

#value Temperature °C D2
#value Pressure hPa D3
#value Humidity % D3

The #rxFormat  is a regular expression that returns all numbers, the #askValuesReadFormat then removes most of the numbers.

I will do some more to this driver, but the above definition will work as is (or with minor modifications) in the final version of the driver. You might need to adjust the baudrate, I programmed the hex you posted into a Arduino ProMicro to test with it.

[Messtechniker]

Thanks for looking into this. However in debug (Test Controller V2.23) I still get:

 TC Port Closing message.txt (0.67 kB - downloaded 67 times.)

The errors for ports other than COM3 and COM5 to which one each BME 280 sensor is connected are OK,
since these are  not connected at the moment.

[HKJ]

Thanks for looking into this. However in debug (Test Controller V2.23) I still get:

The errors for ports other than COM3 and COM5 to which one each BME 280 sensor is connected are OK,
since these are  not connected at the moment.

Be sure not to checkmark "Scan serial ports" on "Load devices" page, it is confusing when looking in the log. It is best to only have one device enabled when debugging.

It do not look like you have loaded and selected the driver I posted.

My log look this way:

Code: [Select]

;; 676.97ms jSerialComm version: 2.9.1
;; 779.97ms Start thread for: COM3 - HKJ Test
;; 1389.23ms COM3: Set params: 9600
;; 1985.27ms COM3: Rx: 55 74 3A 35 32 34 32 38 38 20 55 70 3A 35 32 34 32 38 38 20 55 68 3A 33 32 37 36 38 0D 0A 54 65 6D 70 65 72 61 74 75 72 3A 20 20 20 20 20 20 20 20 32 30 2E 37 34 B0 43 0D 0A 4C 75 66 74 64 72 75 63 6B 20 36 34 62 69 74 3A 20 20 20 36 37 34 2E 39 38 36 68 50 61 0D 0A 4C 75 66 74 64 72 75 63 6B 20 33 32 62 69 74 3A 20 20 20 36 37 35 2E 32 34 68 50 61 0D 0A 4C 75 66 74 66 65 75 63 68 74 69 67 6B 65 69 74 3A 20 20 32 35 2E 39 35 31 25 0D 0A 48 F6 68 65 20 FC 62 65 72 20 4D 65 65 72 3A 20 20 33 32 39 37 2E 37 38 6D 0D 0A 0D 0A
;; 5096.99ms COM3: Rx: 55 74 3A 35 32 34 32 38 38 20 55 70 3A 35 32 34 32 38 38 20 55 68 3A 33 32 37 36 38 0D 0A 54 65 6D 70 65 72 61 74 75 72 3A 20 20 20 20 20 20 20 20 32 30 2E 37 34 B0 43 0D 0A 4C 75 66 74 64 72 75 63 6B 20 36 34 62 69 74 3A 20 20 20 36 37 34 2E 39 38 36 68 50 61 0D 0A 4C 75 66 74 64 72 75 63 6B 20 33 32 62 69 74 3A 20 20 20 36 37 35 2E 32 34 68 50 61 0D 0A 4C 75 66 74 66 65 75 63 68 74 69 67 6B 65 69 74 3A 20 20 32 35 2E 39 35 31 25 0D 0A 48 F6 68 65 20 FC 62 65 72 20 4D 65 65 72 3A 20 20 33 32 39 37 2E 37 38 6D 0D 0A 0D 0A
;; 5097.27ms COM3: Rx: 55 74 3A 35 32 34 32 38 38 20 55 70 3A 35 32 34 32 38 38 20 55 68 3A 33 32 37 36 38 0D 0A 54 65 6D 70 65 72 61 74 75 72 3A 20 20 20 20 20 20 20 20 32 30 2E 37 34 B0 43 0D 0A 4C 75 66 74 64 72 75 63 6B 20 36 34 62 69 74 3A 20 20 20 36 37 34 2E 39 38 36 68 50 61 0D 0A 4C 75 66 74 64 72 75 63 6B 20 33 32 62 69 74 3A 20 20 20 36 37 35 2E 32 34 68 50 61 0D 0A 4C 75 66 74 66 65 75 63 68 74 69 67 6B 65 69 74 3A 20 20 32 35 2E 39 35 31 25 0D 0A 48 F6 68 65 20 FC 62 65 72 20 4D 65 65 72 3A 20 20 33 32 39 37 2E 37 38 6D 0D 0A 0D 0A
;; 5097.49ms COM3: Rx: 55 74 3A 35 32 34 32 38 38 20 55 70 3A 35 32 34 32 38 38 20 55 68 3A 33 32 37 36 38 0D 0A 54 65 6D 70 65 72 61 74 75 72 3A 20 20 20 20 20 20 20 20 32 30 2E 37 34 B0 43 0D 0A 4C 75 66 74 64 72 75 63 6B 20 36 34 62 69 74 3A 20 20 20 36 37 34 2E 39 38 36 68 50 61 0D 0A 4C 75 66 74 64 72 75 63 6B 20 33 32 62 69 74 3A 20 20 20 36 37 35 2E 32 34 68 50 61 0D 0A 4C 75 66 74 66 65 75 63 68 74 69 67 6B 65 69 74 3A 20 20 32 35 2E 39 35 31 25 0D 0A 48 F6 68 65 20 FC 62 65 72 20 4D 65 65 72 3A 20 20 33 32 39 37 2E 37 38 6D 0D 0A 0D 0A
;; Found HKJ Test on Arduino Leonardo (COM3)
;; 5997.19ms COM3: Rx: 55 74 3A 35 32 34 32 38 38 20 55 70 3A 35 32 34 32 38 38 20 55 68 3A 33 32 37 36 38 0D 0A 54 65 6D 70 65 72 61 74 75 72 3A 20 20 20 20 20 20 20 20 32 30 2E 37 34 B0 43 0D 0A 4C 75 66 74 64 72 75 63 6B 20 36 34 62 69 74 3A 20 20 20 36 37 34 2E 39 38 36 68 50 61 0D 0A 4C 75 66 74 64 72 75 63 6B 20 33 32 62 69 74 3A 20 20 20 36 37 35 2E 32 34 68 50 61 0D 0A 4C 75 66 74 66 65 75 63 68 74 69 67 6B 65 69 74 3A 20 20 32 35 2E 39 35 31 25 0D 0A 48 F6 68 65 20 FC 62 65 72 20 4D 65 65 72 3A 20 20 33 32 39 37 2E 37 38 6D 0D 0A 0D 0A
;; 7001.15ms COM3: Rx: 55 74 3A 35 32 34 32 38 38 20 55 70 3A 35 32 34 32 38 38 20 55 68 3A 33 32 37 36 38 0D 0A 54 65 6D 70 65 72 61 74 75 72 3A 20 20 20 20 20 20 20 20 32 30 2E 37 34 B0 43 0D 0A 4C 75 66 74 64 72 75 63 6B 20 36 34 62 69 74 3A 20 20 20 36 37 34 2E 39 38 36 68 50 61 0D 0A 4C 75 66 74 64 72 75 63 6B 20 33 32 62 69 74 3A 20 20 20 36 37 35 2E 32 34 68 50 61 0D 0A 4C 75 66 74 66 65 75 63 68 74 69 67 6B 65 69 74 3A 20 20 32 35 2E 39 35 31 25 0D 0A 48 F6 68 65 20 FC 62 65 72 20 4D 65 65 72 3A 20 20 33 32 39 37 2E 37 38 6D 0D 0A 0D 0A

Note: My Arduino (definition) always identifies as "HKJ Test", the Ardiuino sends the data I have programmed into it.
The reason I have a time stamp on my debug lines is because I uses "debugtime=2" instead of just "debug" as command line parameter (See inside .bat file)

[Messtechniker]

I now get in debug:

;; jSerialComm version: 2.9.1
;; Start thread for: COM4 - BME280
;; COM4: Set params: 9600
;; COM4: Tx: <*IDN?.> 2A 49 44 4E 3F 0A
;; COM4: Rx: <Ut:1048575 Up:1048575 Uh:65535> 55 74 3A 31 30 34 38 35 37 35 20 55 70 3A 31 30 34 38 35 37 35 20 55 68 3A 36 35 35 33 35
;; ELTIMA_Virtual_Serial_Port_04 (COM4) Device BME280 do not match: Ut:1048575 Up:1048575 Uh:65535
;; COM4: Close
;; Stopping thread for: COM4 - BME280
;; COM4: Close

The problem in my case seems to be the unasked for IDN? request. I causes the BME 280 to
respond in a way TC cannot handle. Thus TC closes the COM port down. I suspect this automatic IDN?
query needs to be prevented in some way.

[HKJ]

I now get in debug:

The problem in my case seems to be the unasked for IDN? request. I causes the BME 280 to
respond in a way TC cannot handle. Thus TC closes the COM port down. I suspect this automatic IDN?
query needs to be prevented in some way.

Did you update the .jar file?
If you check "Configuration" and "About" it must show V2.24, any previous version do not have the new driver.

[Messtechniker]

Yep. TC with BME 280 nicely logging away now.



Dunno where this A preceding the C comes from.

Anyway. In the next few days I will send you by mail info on the 
BME 280 sensor processing hardware schematic for your DIY page.

Thanks for your effort.

[HKJ]

Dunno where this A preceding the C comes from.

The definition file must be in unicode with a BOM or TestController cannot select the correct character set for it. If you remind me when you send the stuff I can add it.

Anyway. In the next few days I will send you by mail info on the 
BME 280 sensor processing hardware schematic for your DIY page.

I look forward to it.

[Messtechniker]

Two final questions:

#rxFormat .*?([0-9.E+-]+)
Some documentation of this please.


#askValuesReadFormat xxxfxfxxfx
Some documentation of this please.

[HKJ]

#rxFormat .*?([0-9.E+-]+)
Some documentation of this please.

The above pattern is a simple way to extract a number from a string. I am not going to document regular expression, you can see something about it here: https://docs.oracle.com/javase/7/docs/api/java/util/regex/Pattern.html.
There is also a lot of places on the inet where you can test regular expressions https://regex101.com/ https://regexr.com/

The driver as such will be documented when I release the new version, I am working on it now.
The driver will contain a lot more functionality in the release version, this will not affect your definition, but make it more usable in many other cases. The idea is to make it the driver for multiline answers and for variable length ascii blocks.

#askValuesReadFormat xxxfxfxxfx
Some documentation of this please.

This is not a new function and is documented here: https://lygte-info.dk/project/TestControllerConfigDevice%20UK.html#Fixing_format_and_other_issues

[HKJ]

V2.25 is up
A new driver, new devices, a new popup and some small improvements to TC
   Added: Support for #poll in Block driver.
   Added: AsciiBlock driver, it can handle variable length block and multiline answer.
   Added: ADC10F103C a 12 bit 10 channel cheap usb connected ADC module (Thanks WA).
   Fixed: Minor bug in Siglent SDM3065X definition (Thanks TheDefpom)
   Added: Floating point format to Block driver
   Added: Control infoAsk mostly for showing SCPI error messages.
   Added: BK & Itech load support for Von mode (Thanks jmurray)
   Added: deviceWriteBytes() function to send binary data to a SCPI device.
   Changed/added: R&S NGE102, R&S NGE102B, R&S NGE103, R&S NGE103B power supply (Thanks PL)
   Changed: R&S HMC8012 (Thanks PL)
   Changed: Aim TTi TGF4042, Aim TTi TGF4082, Aim TTi TGF4162, Aim TTi TGF4242 (Thanks PL)
   Changed: Definition of R&S HMO1022 now uses same definition as some other R&S scopes (Thanks WA)
   Added: Auto Adjust popup to find or adjust a output until a input reach a specific value.

The drivers from PL is very advanced, they use the "Other" menu to add a couple of uploads/downloads.

The popup AutoAdjust can be used to search for a setting.


It uses a binary search and it is about as fast as doing it manually when you have a analog control to adjust.

In the above example TC is adjusting current to find a specific voltage.


The AsciiBlock driver is for answers where length and placement of values may vary a bit, it uses regular expressions to find the values.