Hi Tim, did you ever find a solution to this? We are up against the same issue a the moment with an Emerson Flow Computer. I can see that the Modbus comms is cycling correctly but there is no data being sent back from the slave. We can successfully see the data in various modbus testing softwares but not in Codesys...
Hi Tim, did you ever find a solution to this? We are up against the same issue a the moment with an Emerson Flow Computer. I can see that the Modbus comms is cycling correctly but there is no data being sent back from the slave. We can successfully see the data in various modbus testing softwares but not in Codesys...
Brilliant thanks, seems counter intuitive to have to have some 'code behind' just to get the selected ID number, but that's working now anyway. Another one for you then... Once an alarm has been selected, is there any way of deselecting it to essentially reset the ID number back to 0? At the moment, once I select an alarm in the window, if that alarm is removed the selection will jump to the next alarm down, and therefore automatically update the ID number.
Was this ever solved? We have a need to display the current Alarm ID in a separate column on the Alarm Vis, as well as populate a tag with the 'selected' alarm ID number. Neither of which seems to work. When we put a tag in the 'Selection --> Variable for the selected alarm ID' variable it does not update the tag on selection, it also doesn't work if we use an Alarm-Info structure tag in the 'Variable for alarm information' variable. It does however update the alarm group number, so we can see that...