Hi Dojo,
I’m writing a protocol and now I have the following problem. When I do a set on one column it should also do automatically a second set before on another column for the same row.
A B C D E
1 2 3 4 5
6 7 8 9 10
For example this table above you choose parameter 2 for the set but before must be parameter 4 set to a specific value.
Is there something I can do easily in the write parameter? I have two solutions in my mind, either do a copy of the table and than use a QAction to do the specific sets. Or just da QAction for the first set, but here I’m not sure if the snmp set is already done, before I can set the second column.
Hi Stefan,
To set one parameter before another in the same row, you’ll indeed need to handle this within a QAction.
Here’s how you can approach it:
- Triggering the QAction: Set up the QAction to be triggered with
row=trueto capture the table key (instance) for the row in question. - Setting the Initial Parameter: First, perform the set on the initial SNMP column. I recommend checking out this guide for details on executing SNMP sets in tables: Here.
Note: Although the value will be immediately set in the table, this doesn’t automatically trigger a “get” to confirm the set value on the device. If you want to confirm that the set was applied on the device, you’ll need to manually initiate a repoll after setting.
- Setting the Target Parameter: After the first set, perform the main set on your target parameter (e.g., on parameter 2) within the same QAction.
- Adding Wait Logic (If Necessary): If you need a delay between sets or want to confirm the first set succeeded before moving on, consider adding a wait mechanism or a check to confirm that the value is updated on the device before proceeding with the main set.
I hope this helps! Let me know if you need further clarification.
Thanks José, worked perfectly!