topic Re: How to set ReadOnly tag values when in simulation mode. in Kepware

How to set ReadOnly tag values when in simulation mode.

AS_12348596 — Wed, 13 Nov 2024 01:57:20 GMT

Currently I am using the Torque Tool Ethernet driver, in KEPServerEX 6.
The device I am testing for, is a PowerFocus 6000 that is communicating via Revision 2.0 of OpenProtocol.

There are a number of things I need to test and simulate, and this means I need to also set ReadOnly values. This is so that I can bug test my code, and confirm it can retrieve correct values at the correct time. For example, when LTR_NEWDATA is set to 1 by the device, or when LTR_TORQUE_STATUS outputs a NG status value.

The problem is as follows: LTR_TORQUE_STATUS is a ReadOnly tag. So I am under the impression that I cannot manually set the value for testing. This appears to be the same for other TORQUE tags like LTR_TORQUE_VALUE.

I tried to set the data address to something like "901.00001" or "1202.00001", while keeping the tag name the same. My program only looks for tag names. So I was hoping that I could set a different address for testing.

(I understand both 901 and 1202 are intended to be used for variable data, and are therefore, read-only)

I have two primary questions:

#1: Is it possible to set values for Read-Only tags? (For example, when using OPC Quick Client in simulation mode)

Alternatively, #2: Are there any extra addresses that are read and write-able, which I can use in this context? This would be appreciated as a workaround, which would let me write values to the tag names for testing.

An answer to either #1, or #2 would be greatly appreciated!

Thankyou in advance,
Azu

Re: How to set ReadOnly tag values when in simulation mode.

rajskumar — Wed, 13 Nov 2024 12:07:18 GMT

Hello,

You can use “DYNAMIC_JOB_REQUEST” or “ALARM_NEWDATA” or any other tag address option that has write access, as per the driver manual. Hope this helps.

Re: How to set ReadOnly tag values when in simulation mode.

AS_12348596 — Fri, 15 Nov 2024 03:26:24 GMT

Hello raiskumar!

Thank you for the response.

I did end up using addresses like USER_DATA, ID_DOWNLOAD and PSET_PROGRAM_WRITE

(Since I am not connecting to an actual device, this should be fine)

I've managed to finangle it so I have enough values, (Some have the wrong data type, but there are simply not enough write-able values.)

I do wish there was a better solution, but thank you. This will have to work for now.