#136 PD topography counter with faulty behavior

[Michael Anderegg]

I create a test case for testing the behavior of topography counter check from A.6.7 Table A.5.

I receive a PD with the given values below. The actual topography counter values are set as shown below. The first check is passed concerning case 4:

Actual topography counter	values of the received telegram
etbTopoCnt	opTrnTopoCnt
123	456

For the second test of the receiving PD, I use diffrent values submitted in the PD.subscribe. The second check is not passed, there is no case for this combination. But the PD is delivered successfully

values of the received telegram	values submitted with the subscription
etbTopoCnt	opTrnTopoCn t
123	456

As allready discused in ticket #123 the description of the behavior of the Topography counter in the specification is very bad and leads to misunderstanding. But for my opinion the above described combination should block the PD instead of transmitting.

[Bernd Löhr]

The topo count error is currently silently ignored, it should at least lead to an error callback.