Matti Siponen said
Hello,

Input Registers and Holding Registers allow you to perform linear scaling using a multiplier/factor and an offset on values read from devices. These parameters can be configured in Input Register Properties and Holding Register Properties dialogs. More complex mathematical operations such as using values from devices as inputs of sine or cosine functions are not supported.  

Thank you very much!

Input Registers and Holding Registers allow you to perform linear scaling using a multiplier/factor and an offset on values read from devices. These parameters can be configured in Input Register Properties and Holding Register Properties dialogs. More complex mathematical operations such as using values from devices as inputs of sine or cosine functions are not supported.

You can represent the bit in the register as an OPC UA Variable. Clients can subscribe to this Variable with MonitoredItems and react accordingly. But there is no way to generate OPC UA Events based on the bit in Modbus Server.

When creating the Variable that represent the bit, you can choose its Name and Description. You can use those to inform Clients that the Variable represents a bit that in turn represents a machine alarm.

Please I need to know if the Prosys OPC UA Modbus Server handles the alarms of Modbus slave devices.

I have a Modbus slave that displays machine alarms as bits in a register.

Is it possible to map these "Modbus bit alarms" into OPC UA variable nodes / OPC UA events and add further information (alarm name translated into language, description, severity, ...)?

Thanks in advance for your support,
Francesco

I have install it one a fresh VMware, and everythigs is empty (+ is possible)

1) create a new modbus device, and i can create a new holding register

2) I click to digital input

3) i back to holding register to add new one..... it's not possible

I have uninstall old version first.
Install the last one

2 problems appears :

1) the connection Adress
opc.tcp adress is keep from old server to new one : OK
https adress is not validate

2) Modbus Devices
All modbus device previously entered in the old version are here. but no holding register appear ?????
how to change theim if i need for exemple ???

png gratuit

thanks

I'm going to assume you mean the .sh installer due your phrasing of the question.

Sorry for the confusion, but may I ask why you feel it would need internet?
I'm aware are some software where a script would DL the real installer, but this .sh is not like those, it is self-contained (e.g. compare sizes to the .exe).

Thus, you would DL the .sh file (I'm aware, that it wont maybe show up as "save file" automatically, we'll do something about that or maybe we should have tar.gz it etc.), transfer it to the machine and run it there and it should basically work. If not, that would be an error/bug. At least on an Ubuntu VM without any network adapters attached it basically just works.

NOTE! Please note (this also reads on the DL page) that if you are upgarding from a version before 1.4.0, you must run the uninstaller of the older version manually first. When updating from at least 1.4.0 the installers will ask you if you wish to update or install to a different place, then upgrading would handle uninstalling etc. automatically (as one would expect; just that the old installers we had were... not that great).

Modbus Protocol supports reading 2000 bits per Read call. A Real requires 32 bits to store and thus 62 Reals can be fit into an Array of 2000 bits. At the moment, the Modbus Server doesn't support arrays consisting of more than 2000 bits of data.

Could you try processing the array of 100 Reals as either 2 arrays of 50 Reals or 100 scalar Reals in Modbus Server instead?

https://www.socomec.com/files/.....munication

From there i want to know total active power which is in my believe 18476 register.

I can also try with easier registers, if you have any recommendation.

Are you sure you have the correct address?
I am only asking because I know that the Modbus addressing can be quite confusing. We don't use entity numbers in addresses. Which means that address 18476 could mean digital input (entity number 1) address 8476. But if you mean input register address 18476 (a.k.a 318476) then that is fine too.

Have you tried other addresses?
If the other addresses are working but this particular one isn't, then that means that the connection is OK, but the device does not support the address.