Program that can log from many multimeters.

[Messtechniker]

Correction for R&SHMC8043.txt

Remove line
:enable: Output_3.Overload.Turn_off
since Output 3 currently cannot be switched ON and OFF via the popup.

Now the definition for output 3 corresponds to the definitions for output 1 and 2 resp 1/2.

[HKJ]

Correction for R&SHMC8043.txt

Remove line
:enable: Output_3.Overload.Turn_off
since Output 3 currently cannot be switched ON and OFF via the popup.

Now the definition for output 3 corresponds to the definitions for output 1 and 2 resp 1/2.

Thanks, this will be fixed in the next release.

[joxelito]

SystemCommands.txt versions issue: one of 14Kb, one of 46Kb !!

While using the help function for reading system commands information, some times for example  "#STOPSCRIPT" shows this command, sometimes not.
I have found that there are 2 versions of SystemCommands.txt , one of 14Kb, one of 46Kb

After deleting the file and restarting the program, some times the 46Kb version is downloaded, but sometimes (the majority) the 14kb one is downloaded
I have the last version of test controller

[HKJ]

SystemCommands.txt versions issue: one of 14Kb, one of 46Kb !!

While using the help function for reading system commands information, some times for example  "#STOPSCRIPT" shows this command, sometimes not.
I have found that there are 2 versions of SystemCommands.txt , one of 14Kb, one of 46Kb

After deleting the file and restarting the program, some times the 46Kb version is downloaded, but sometimes (the majority) the 14kb one is downloaded
I have the last version of test controller

I suspect you only get the first part of the file and I do not detect correctly that there was a fail during download.
This is probably related to the faster timeout I added recently.
I will take a look on it.

[PushUp]

I have played a bit with my Brymen vs. Linux and this is what I have got so far:





TestController does find it, but it does not appear under "Current values"...

Code: [Select]

;; Found Brymen BM867s on HIDv0820p0001
#DEBUG BM867 +modeComm +valueComm +otherComm +commHex
;; BM867: Tx <VALUE?> 56 41 4C 55 45 3F
;; BM867: Rx <-∞> 2D 3F
;; BM867: Rx as numbers <-Infinity>
;; BM867: Tx <VALUE?> 56 41 4C 55 45 3F
;; BM867: Rx <-∞> 2D 3F
;; BM867: Rx as numbers <-Infinity>
;; BM867: Tx <VALUE?> 56 41 4C 55 45 3F
;; BM867: Rx <-∞> 2D 3F
;; BM867: Rx as numbers <-Infinity>
;; BM867: Tx <VALUE?> 56 41 4C 55 45 3F
;; BM867: Rx <-∞> 2D 3F
;; BM867: Rx as numbers <-Infinity>
;; BM867: Tx <VALUE?> 56 41 4C 55 45 3F
;; BM867: Rx <-∞> 2D 3F
;; BM867: Rx as numbers <-Infinity>
;; BM867: Tx <VALUE?> 56 41 4C 55 45 3F
;; BM867: Rx <-∞> 2D 3F
;; BM867: Rx as numbers <-Infinity>
;; BM867: Tx <VALUE?> 56 41 4C 55 45 3F
;; BM867: Rx <-∞> 2D 3F
;; BM867: Rx as numbers <-Infinity>
;; BM867: Tx <VALUE?> 56 41 4C 55 45 3F
;; BM867: Rx <-∞> 2D 3F
;; BM867: Rx as numbers <-Infinity>
;; BM867: Tx <VALUE?> 56 41 4C 55 45 3F
;; BM867: Rx <-∞> 2D 3F
;; BM867: Rx as numbers <-Infinity>
;; BM867: Tx <VALUE?> 56 41 4C 55 45 3F
;; BM867: Rx <-∞> 2D 3F
;; BM867: Rx as numbers <-Infinity>
;; BM867: Tx <VALUE?> 56 41 4C 55 45 3F
;; BM867: Rx <-∞> 2D 3F
;; BM867: Rx as numbers <-Infinity>
;; BM867: Tx <VALUE?> 56 41 4C 55 45 3F
;; BM867: Rx <-∞> 2D 3F
;; BM867: Rx as numbers <-Infinity>
;; BM867: Tx <VALUE?> 56 41 4C 55 45 3F
;; BM867: Rx <-∞> 2D 3F
;; BM867: Rx as numbers <-Infinity>
;; BM867: Tx <VALUE?> 56 41 4C 55 45 3F
;; BM867: Rx <-∞> 2D 3F
;; BM867: Rx as numbers <-Infinity>
;; BM867: Tx <VALUE?> 56 41 4C 55 45 3F
;; BM867: Rx <-∞> 2D 3F
;; BM867: Rx as numbers <-Infinity>
;; BM867: Tx <VALUE?> 56 41 4C 55 45 3F
;; BM867: Rx <-∞> 2D 3F
;; BM867: Rx as numbers <-Infinity>
;; BM867: Tx <VALUE?> 56 41 4C 55 45 3F
;; BM867: Rx <-∞> 2D 3F
;; BM867: Rx as numbers <-Infinity>
;; BM867: Tx <VALUE?> 56 41 4C 55 45 3F
;; BM867: Rx <-∞> 2D 3F

Cheers!

[HKJ]

I have played a bit with my Brymen vs. Linux and this is what I have got so far:

I only support HID interfaces on windows at the current time.

[HKJ]

V1.97 is up
It is a couple of new devices, some bugfixes and a few addition to the internal stuff.
   Fixed: Downloading of files sometimes gave incomplete files.
   Modified: binConvString added swap and termination parameters.
   Fixed: binConvString codepage specification did not work
   Added: Function msToDate()/dateToms()/msToDateGMT()/dateTomsGMT()/tzOffset(), can be used to convert date/time information.
   Added: Modbus/ascii protocol and holdingS? for reading signed 16 bit value
   Fixed: R&S HMC4043 Channel 3 was disabled (Thanks Messtechniker)
   Added: Metrix MTX3292 (Thanks to a user)
   Added: Siglent SPD3303X power supplies (Thanks C.J.S.)
   Fixed: Interface names in Owon ODP6033
   Added: Ruoshui LCR meters (Thanks TheDefpom & C.J.S.)
   Fixed: #modeFromValue did not handle multiple commands

[PushUp]

I have played a bit with my Brymen vs. Linux and this is what I have got so far:

I only support HID interfaces on windows at the current time.

Yes, I know.

However, over a year ago I couldn't manage that a Brymen with its USBHID was detected by TestController using Linux:

https://www.eevblog.com/forum/testgear/program-that-can-log-from-many-multimeters/msg3019724/?PHPSESSID=e8ja7i0ragru6auspt39agp3m1#msg3019724

..., but now it works. Therefore I thought you "only" need to implement the missing "definitions" and it could be a step forward, trying to use a cheap Brymen with an even cheaper Pi with Linux?

As Brymen works with SmuView under Linux, there is probably only a "piece" missing?

It is only a question, as I am not able to judge the required deal of work! 


Cheers and thanx for version 1.97! 

[HKJ]

Yes, I know.

However, over a year ago I couldn't manage that a Brymen with its USBHID was detected by TestController using Linux:

https://www.eevblog.com/forum/testgear/program-that-can-log-from-many-multimeters/msg3019724/?PHPSESSID=e8ja7i0ragru6auspt39agp3m1#msg3019724

..., but now it works. Therefore I thought you "only" need to implement the missing "definitions" and it could be a step forward, trying to use a cheap Brymen with an even cheaper Pi with Linux?

As Brymen works with SmuView under Linux, there is probably only a "piece" missing?

It is only a question, as I am not able to judge the required deal of work! 

A long time ago I implemented different solutions for Windows and Linux, but the HID library did not work on my RasberryPi (With std. OS), that is the only stand-alone Linux computer I have at the moment, i.e. I could not test and debug it.
It may be a simple fix, but I am not expecting to look at it before I have a way to test/debug, I also need a new look on the Windows part.

[HKJ]

V1.98 is up
This is mostly a bugfix to the modbus protocol that I damaged in the last version, but it also add a new multimeter.
   Added: Info control supports :format: tag
   Fixed: Modbus/ascii disabled the other modbus protocoles.
   Added: Metrix MTX3281, Metrix MTX3282 multimeters (Thanks tgotic)
   Fixed: holdingS? modbus protocol for signed 16 bit value

[Messtechniker]

RE.: Windows HID equipment definitions

I also need a new look on the Windows part.

I'm sure there is quite some interest in this area.
Since I have a Voltcraft VC 940 (UT71E) I could
help with testing once the framework is up and
running. Writing a definition for HID equipment
is unfortunately beyond my abilities.
Doing the initial definition for the HMC 8043
was already stretching it a bit for me.
50 years of experience, but my learning ability
is gradually going downhill.

[HKJ]

I could help with testing once the framework is up and running.

It will probably be some time yet, before I get around to do it.

[PaWill68]

There is an error in the RidenRD60xx file.
It is not possible to set the current to more than 1A. If you choose 1A, then in fact the current is set to 10A.

[Pukker]

There is an error in the RidenRD60xx file.
It is not possible to set the current to more than 1A. If you choose 1A, then in fact the current is set to 10A.

Yes, that is true.

Look in devicefile RidenRD60xx.txt and replace

#metadef
#author MikeLud
#idString Riden,Riden RD6012
#name Riden RD6012
#handle RD6012

#replacetext RD60xx 60121
#replaceText MaxCurrent 12.000
#replaceText MaxOCP 12.100
#replaceText CurrentScaleFactor 1000

with

#metadef
#author MikeLud
#idString Riden,Riden RD6012
#name Riden RD6012
#handle RD6012

#replacetext RD60xx 60121
#replaceText MaxCurrent 12.000
#replaceText MaxOCP 12.100
#replaceText CurrentScaleFactor 100

The CurrentScaleFactor 1000 has to be 100.

Works fine with my RD6012.

Attached my RidenRD60xx.txt file.

[HKJ]

There is an error in the RidenRD60xx file.
It is not possible to set the current to more than 1A. If you choose 1A, then in fact the current is set to 10A.

Yes, that is true.

Look in devicefile RidenRD60xx.txt and replace

This will be fixed in the next release.
I only have definitions for RD6006 & RD6012, if anybody makes definitions for other models I am very interested in getting them.
Note: A definition is probably not more than the 10 lines Pukker has posted, just with other values.

[palmerr23]

Thanks for this really useful software.

I'm working on an instrument definition file for the OWON BT35-41 series multimeters and may attempt my OWON XDS3014 CRO after that (as the manufacturer's Windows app for it is truly woeful!)

All going well, except I can't see a way to get the available commands to display in the help window on the Commands tab. It works for all the virtual instruments, but not

I've found the help file folder \documents\TestController\Settings but it only seems to have help files for the Virtual instruments. I'm using version 1.98 on Win 10-64 bit.

[palmerr23]

I have a FY6900-40M

The following needs to be added to the FeelElecFY6x00-xxM.txt definition file around line 132.

Thanks

Code: [Select]

#metadef
#idString FeelElec,FeelElec FY6900-40M

#name FeelElec FY6900-40M
#handle FY6900

#replacetext FY6x00-xxM FY6900-40M
#replaceText MaxFrequency 40M
#replaceText MaxVpp 24
#replaceText MinOffset -12
#replaceText MaxOffset 12
#replaceText >CAL >12000
#sections WAVE2

[palmerr23]

Thanks for this really useful software.

I'm working on an instrument definition file for the OWON BT35-41 series multimeters and may attempt my OWON XDS3014 CRO after that (as the manufacturer's Windows app for it is truly woeful!)

All going well, except I can't see a way to get the available commands to display in the help window on the Commands tab. It works for all the virtual instruments, but not

I've found the help file folder \documents\TestController\Settings but it only seems to have help files for the Virtual instruments. I'm using version 1.98 on Win 10-64 bit.

I think I've solved my own problem #scpCmd tags in the definition file seem to provide the help/

[palmerr23]

Quote
Thanks for this really useful software.

I'm working on an instrument definition file for the OWON BT35-41 series multimeters and may attempt my OWON XDS3014 CRO after that (as the manufacturer's Windows app for it is truly woeful!)

All going well, except I can't see a way to get the available commands to display in the help window on the Commands tab. It works for all the virtual instruments, but not

I've found the help file folder \documents\TestController\Settings but it only seems to have help files for the Virtual instruments. I'm using version 1.98 on Win 10-64 bit.

I think I've solved my own problem #scpCmd tags in the definition file seem to provide the help/

That answer is wrong! The #help tag does the trick.

[HKJ]

I have a FY6900-40M

The following needs to be added to the FeelElecFY6x00-xxM.txt definition file around line 132.

Thanks, this will be included in next release

[HKJ]

That answer is wrong! The #help tag does the trick.

If the help file name match the device name the #help tag is not needed.

[Karlis]

Hi, realy nice tool, thank's.

But I have a problem with East Tester ET3240, maybe I need somewhere to change something, but can't figure it out.
All works, but in TestController measured values is displayed and logged without taking in to account multiplier.
As example if ET3240 measures 18.05mV on PC it is displayed as 18.05V.
Can You help me?

[HKJ]

Hi, realy nice tool, thank's.

But I have a problem with East Tester ET3240, maybe I need somewhere to change something, but can't figure it out.
All works, but in TestController measured values is displayed and logged without taking in to account multiplier.
As example if ET3240 measures 18.05mV on PC it is displayed as 18.05V.
Can You help me?

I do not have time to look at it today, but you can try opening the "East Tester ET3240.txt"  file and add:

#askValuesReadFormat s

after the "#askValues read?" line

Please report back if it works or not.

[Karlis]

Adding
#askValuesReadFormat s
din't help.

[HKJ]

Adding
#askValuesReadFormat s
din't help.

Ok, I will dig out the meter tomorrow (Usually it is not on my bench) and look at it.