Program that can log/control many multimeters and other devices.

[flash2b]

I need to convert a string into a multiple 16bit values

Lets say my string is "abcde" the output should be 0x6162 0x6364 0x6500, how do I do that ?

It is like the reverse version of holdingBytes?

I have no luck with with <<8 and substring...

It is called packing ascii into 16bit big-endian order with zero-padding. 

[HKJ]

I need to convert a string into a multiple 16bit values

Lets say my string is "abcde" the output should be 0x6162 0x6364 0x6500, how do I do that ?

It is like the reverse version of holdingBytes?

I have no luck with with <<8 and substring...

It is called packing ascii into 16bit big-endian order with zero-padding.

You need to cast to bytes, but it looks like I am missing a substring function for bytes.
I.e. first use substring to get two chars, then cast it to bytes, then cast the bytes to int

A question: Can I use substring for this or do I need to make a subbyte function? It is easy to check the datatype in substring and modify the behavior if a byte array is used as argument, but it is not completely logical.

[flash2b]

I have tried that but I get Java exceptions

Code: [Select]

C1= int(bytes(substring( value ,0,1)))
C2= int(bytes(substring( value ,1,2)))
C3= (C1<<8)+C2
My input is a string and can have any length. However I only need to decode a portion of it that since the device has only place for 6 16bit packed value that I need to write with Modbus function 10.

[HKJ]

I have tried that but I get Java exceptions

Code: [Select]

C1= int(bytes(substring( value ,0,1)))
C2= int(bytes(substring( value ,1,2)))
C3= (C1<<8)+C2
My input is a string and can have any length. However I only need to decode a portion of it that since the device has only place for 6 16bit packed value that I need to write with Modbus function 10.

It would be more useful if you include the exception.

[flash2b]

I got it working now

Code: [Select]

#scpiCmd writeDisplayText #pgm#
C1= int(bytes(substring( value ,0,1)))
C2= int(bytes(substring( value ,1,2)))
C3= int(bytes(substring( value ,2,3)))
C4= int(bytes(substring( value ,3,4)))
C5= int(bytes(substring( value ,4,5)))
C6= int(bytes(substring( value ,5,6)))
deviceWrite(handle,"holding 0x17 2");
deviceWrite(handle,"holding 0x05 "+ ((C1<<8)+C2) + " " + ((C3<<8)+C4) + " " + ((C5<<8)+C6) )
I have trouble to understand if I can have an expression in a function or that only variables. It is now both.

Can I do the above without the extra variables C1..C6 ?

[HKJ]

I got it working now

Code: [Select]

#scpiCmd writeDisplayText #pgm#
C1= int(bytes(substring( value ,0,1)))
C2= int(bytes(substring( value ,1,2)))
C3= int(bytes(substring( value ,2,3)))
C4= int(bytes(substring( value ,3,4)))
C5= int(bytes(substring( value ,4,5)))
C6= int(bytes(substring( value ,5,6)))
deviceWrite(handle,"holding 0x17 2");
deviceWrite(handle,"holding 0x05 "+ ((C1<<8)+C2) + " " + ((C3<<8)+C4) + " " + ((C5<<8)+C6) )
I have trouble to understand if I can have an expression in a function or that only variables. It is now both.

Can I do the above without the extra variables C1..C6 ?

You may get away with:

Code: [Select]

for i=1 to (length(value)+1)/2 do
deviceWrite(handle+":"+i*2,"holding 0x05 "+ int(bytes(substring( value ,i*2,i*2+2))));
endfor

I have not tested the code, i.e. it probably has a lot of errors, but the idea is valid.

[flash2b]

length is not a function, Java says. (Function not found length)

it should be for i=0 I guess.

[HKJ]

length is not a function, Java says. (Function not found length)

it should be for i=0 I guess.

Sorry, it is strlen() or size()

[flash2b]

It is strlen().

Well also the holding register needs to count up and it now produces little endian 

I will fiddle with it, what I posted with the variables works for me but there is always ways to improve.

[HKJ]

Well also the holding register needs to count up and it now produces little endian 

I added it to the handle, that was wrong, you have to add it to the address.

I will fiddle with it, what I posted with the variables works for me but there is always ways to improve.

There is often multiple ways to solve a issue with the programming language. I try to make it as flexible as possible.

[flash2b]

Well also the holding register needs to count up and it now produces little endian 

I added it to the handle, that was wrong, you have to add it to the address.

Yes I caught that, but it needs to be written one time, so 1 holding with multiple values not multiple holding with 1 (16bit) value.

Reading it back I can do with holdingBytes? so that is easy.

[HKJ]

Yes I caught that, but it needs to be written one time, so 1 holding with multiple values not multiple holding with 1 (16bit) value.

Reading it back I can do with holdingBytes? so that is easy.

I am not sure if you can collect the values in a string and use that as a parameter, but you can make a string with the full command and execute it (executeString()).

[HKJ]

I have uploaded a new test version, it support shared modbus.
It works the same was as GPIB and is configured in the same popup.

To use it a definition must have: "#port comfixedbaud modbus" or something similar, always specify com port first and modbus second!


This means I have been into the GPIB code and I do not have a GPIB setup at the current time, could somebody please verify it still works.


And a warning: Using multiple devices on the same modbus interface will reduce the maximum logging rate. TC has to fit all the communication onto the same wire, this means parallel reading do not work for these devices.

[flash2b]

I added parameter: Modbus Z Serial COM10 9600 to the submenu

My device is on Address: Z:1

But it does not see it, or connect to it.

My defintion has: #port comfixedbaud modbus

What do I need to do additional ?

[HKJ]

I added parameter: Modbus Z Serial COM10 9600 to the submenu

My device is on Address: Z:1

But it does not see it, or connect to it.

My defintion has: #port comfixedbaud modbus

What do I need to do additional ?

Select modbus for the device, i.e. click on the "Type" for the device and select modbus, instead of serial.
Put Z:1 in the address field.

[flash2b]

we were typing at the same time.

I needed to set Type to Modbus ...... !! and it connects ! 

I am so happy with this feature, thank you HKJ will start testing with multiple devices on the same modbus.

 

[flash2b]

Is the update on https://lygte-info.dk/project/TestControllerInterfaceDefinitions%20UK.html not published yet ?

There is a little typo: #interfaceType thermomenter thermomenter:2 thermomenter:3 thermomenter:4 , should be 4 times: thermometer which then also can be updated with it together.

[HKJ]

Is the update on https://lygte-info.dk/project/TestControllerInterfaceDefinitions%20UK.html not published yet ?

Most of the time I first publish the updated documentation when I release the official version of TC.

There is a little typo: #interfaceType thermomenter thermomenter:2 thermomenter:3 thermomenter:4 , should be 4 times: thermometer which then also can be updated with it together.

Oops, fixed.

[flash2b]

That's what I thought.

There is a slight delay when TC connects to the new shared modbus interface when it shows: "Modbus interface created for shared communication" but other than that I works as before. I need to change some slaveIDs on my modbus devices and will then be able to string them together on the same port of my modbus interface. Some have dip switches while most I need to configure them with a command.

[HKJ]

There is a slight delay when TC connections to the new shared modbus interface when it shows: "Modbus interface created for shared communication" but other than that I works as before. I need to change some slaveIDs on my modbus devices and will then be able to string them together on the same port of my modbus interface. Some have dip switches while most I need to configure them with a command.

I do not know about a delay with one device, but with more devices there will be a delay.
I used a command to change address of device 1, then connected next device and did the same, before wiring them all to the same bus.
In my test setup I am running with 3 NT18B07

[dreamer]

Thank you, I will try!

[flash2b]

I tried the new shared modbus function and it works !



The NT48A08 is now on address: 002 on the same RS485 port via COM5 to USB. My temperature reading script outputting the value on the DM18C04 still works, so test passed !

(Again) extremely happy !

[HKJ]

I tried the new shared modbus function and it works !

The NT48A08 is now on address: 002 on the same RS485 port via COM5 to USB. My temperature reading script outputting the value on the DM18C04 still works, so test passed !

And did you put the display on the same bus?

You serial numbers are not really good, they are the same for multiple devices and that confuses TC in some cases (It will still work, but they will change name each time you restart, if you have multiple devices with the same name)

[flash2b]

Yes they are on the same bus: Port1

My Modbus devices generally do not supply a serial number via a register nor do they have a printed serial# on the device themself (Ebyte does put a serial on the device as a sticker). So I generally set the serial in the definition (with some comments) and that is no problem if there is only one device. I have seen TC change the handle with a suffix when there were 2 devices with the same serial# and the same handles attached.

What is a better way to have a serial# when the device does not offer it over a interface command ?

[HKJ]

Yes they are on the same bus: Port1

My Modbus devices generally do not supply a serial number via a register nor do they have a printed serial# on the device themself (Ebyte does put a serial on the device as a sticker). So I generally set the serial in the definition (with some comments) and that is no problem if there is only one device. I have seen TC change the handle with a suffix when there were 2 devices with the same serial# attached.

What is a better way to have a serial# when the device does not offer it over a interface command ?

Leave it empty, if people what to add their own it is fine.
TC will base the _999 number on serial port, inet or modbus address if no serial number is found, this usually mean the number stays the same.