PAC Control Digital Input: Allow Write Capability disabled?

Hey all,

I’m using a Digital Input channel on a GRV-MM1001 module to monitor for a button press, with the intention of reading the Onlatch from an OPC tag and clearing it after read. When trying to do this, I encounter an error (from Python asyncua code):

UA Error writing to tag ns=2;s=Devices/[scar_io]/OptoMMP/Modules/Channels/Start_Button/Onlatch on groov: "The access level does not allow writing to the Node."(BadNotWritable)

However, in the PAC Control edit window for that input, the “Allow Write Capability” checkbox is disabled, so I can’t enable it:

I feel like maybe I’m missing something obvious – can anyone help me out here? How can I read and clear the latch through OPC tags?

Thanks,
Patrick

OPC and Python use the REST interface.
To set that up, you need to use the groov Manage interface.
PAC Control is more for the strategy tags ect.

1 Like

Hey Beno, thanks, I have that set though and I’m still getting the same error:

I thought that whatever was in the PAC Control strategy would take the place of these settings whenever it was uploaded and run – I noticed that a different channel name in the strategy would replace whatever I had set in groov Manage, for example.

Did you restart the data service after saving these changes?

1 Like

I don’t think Channel 2 supports latching, only channel 0 and 1.

Good catch on the second screenshot @philip
You are correct. Only the first 2 channels are ‘smart’.

EDIT: hold up. They only do the counting, I think all channels can do latching

From the toggles in the Public Access, I can see why one would get a different impression - that should probably be fixed to not display those counter and latch options outside of channel 0 and 1.

They didn’t about two years ago when I tried.

Edit, 4 years ago… time flies:

RIO yes, Just the first two.
EPIC MM, no, all of them.

The EPIC CPU has more horsepower and so can do all the digital inputs.

1 Like

Did you restart the data service after saving these changes?

:sweat_smile:
I knew I was missing something. This works now, thank you!!

2 Likes