Hexing PLC meter read in problems

sdg.marinusvz
2018-01-10 10:00

This post has been transcribed from an email

Could you please assist us with the following meters that are not communicating for Raslouw - therefore no ?transactions? are being deducted from the ledger.

RM - ERF 532

RM - ERF 499

RM - ERF 407

RM - ERF 456

RM - ERF 514

sdg.marinusvz
2018-01-10 10:00

What does the problem meter list say?

sdg.marinusvz
2018-01-10 10:01

Its says

'partial read'
'communication error'
'plc error'

sdg.marinusvz
2018-01-10 10:02

Ok.

What are the meter serial numbers?

sdg.marinusvz
2018-01-10 10:02

See below:

RM - ERF 532 - 14274569368

RM - ERF 499 - 14274566505

RM - ERF 407 - 14274566737

RM - ERF 456 - 14274565028

RM - ERF 514 - 14271403439

sdg.marinusvz
2018-01-10 10:04

I see 14274569368 never called in?

ever?

And the rest also.

If at all possible, to avoid this kind of situation, I urge you to read in all meters a first time before the installing technician leaves site. It looks like the PLC reception between the Concentrator and the Meters is just not good enough. Are you sure they are added on the correct Concentrator?

14274569350 is an interesting case.

It seems somehow the index inside the concentrator that we programmed for ...9350 has been taken by ...5028?

Has this concentrator perhaps been connected to a different server?

Or possibly someone updated the Multi-Drop id on the Meter Details screen it was changed by the communications class?

Anyway, to force pnpscada to re-program the meter into the concentrator at a new index, set the Multi-Drop id on the Meter Details screen to 1. Since the indexes in the Concentrator is from 2 upwards, when we detect an index < 2, we recalculate a new index and program it into the concentrator when we try to read a meter.

sdg.marinusvz
2018-01-10 10:05

I?ve set the Multi drop ID to 1 and it seems to have worked.

Thank you !

Please log in to post a comment