Communication KO

Discussion about Gate Builder and variables database creation.
Isakovic
Posts: 10
Joined: Tue Jun 14, 2016 10:01 am

Communication KO

Postby Isakovic » Mon Apr 03, 2017 8:32 am

Hello,

When does communication status go KO?

I use Modbus TCP for communication. When PLC is disconnected from network read errors accumulate and then after some time status goes KO. During this time other gates are not updated, because of timeout I suppose.
Before using gates in code I always put if(BitNot(IsDeviceCommunicationKo(2, 2))) but this doesn't work because status doesn't go KO.

User avatar
admin
Site Admin
Posts: 306
Joined: Tue Nov 17, 2009 1:18 pm

Re: Communication KO

Postby admin » Mon Apr 03, 2017 8:40 am

Dear Sir,
for online gate status use "GetNumGateCommunicationStatus(,)", "GetDigGateCommunicationStatus(,)", and so on.

Device status go KO if all device gates are unreadable for 3 attempts.

Best regards

Isakovic
Posts: 10
Joined: Tue Jun 14, 2016 10:01 am

Re: Communication KO

Postby Isakovic » Mon Apr 03, 2017 10:45 am

Thanks for the quick answer. I'll try reducing timeout to get it to KO faster.


Return to “Tags - Gate Builder”

Who is online

Users browsing this forum: No registered users and 1 guest