I don't see what's wrong here.

[MikeR]

How do i fix this.  all have the same IP right?
See atached.
Thanks!

[ADC Product Engineer]

Do-more uses the concept of "devices" as a in-between driver for it's hardware.   

If you use one "device" (com handler) for all of your slaves, if one slave gets an error then you hang your communications to all of your slaves waiting on the bad one to respond.  This is and always has been an issue until Do-more came along.

With Do-more you can make multiple "devices" (com handlers) for one IP address.  Use each "device" for each slave.  This way if one hangs up, the rest keep on chugging because they are not all using the same com handler (device).

[franji1]

How do i fix this.  all have the same IP right?
See atached.
Thanks!

It appears you are using a hard IP address for one of the Modbus instructions, then use a variavle D0 for all the others.  If these are all the same slave, i.e D0, once set, is not changing berween instructions, you can definitely ignore thse.  Just right click on the Program Check rule and select Ignore in Rung, or even Ignore in Project if this is going to be utilized with the same IP address in all other new MxX instructions.

If, however these are different IP addresses, i.e. They are all different slaves, then ADC Product Engineer's post should be considered.

[MikeR]

Thank you. They all are the same IP. I was too tired to understand that there were a bunch that i hadn't changed and that all of the instructions were not showing in that list.   

Thanks again
Mike

[franji1]

It appears there are 11 of them total.  One is hard (192.168.27.72), the remaining 10 are D0.   Are you really using D0 as an IP Address (e.g. an HMI entry)?

If they all were the same static IP Address (192.168.27.72) you would NOT receive any Program Check messages.  But because 10 of them are D0, that means you want them to be dynamic (not static), hence the Program Check messages.