Before commenting read Forum rules
Don't comment the topic if you have a new question.
You can create a new topic selecting correct category from Gurux Forum and then create a new topic selecting "New Topic" from the top left.
Forums
Hi Mikko,
There're some situations which I hope you can help shed some light.
Scenario 1:
Our meter is connected to a serial port of a transparent router/gateway/concentrator device.
This device is connected to a computer that is running a Gurux Director program.
The meter's Device Address is set as 1. The Physical Server Address of the Director is also set as 1.
We can read the data and registers etc of the meter.
No problems here.
Scenario 2:
From Scenario 1 above, we added another meter (RS485 multidrop) with the Device Address as 2.
Now when we are unable to connect to any of the 2 meters.
Scenario 3:
So we tried to troubleshoot by reducing the connection back to Scenario 1.
It works again.
Now we change the Device Address from 1 to 2.
We changed also the Physical Server Address of the Director as 2.
We were unable to connect to the meter, even though it is the same as in Scenario 1, and there is only 1 meter connected.
I've tried to change the following configs, but still could not connect:
a) Protocol using UDP
b) Use Serial port through ethernet
c) Logical Server
d) Physical Server
Were there any configs from Gurux that I missed?
Thank you.
Further information:
Further information:
The attached picture showed the error received in Scenario 3:
Hi,
Hi,
There are some differences in how multidrop is implemented for different meters. You need to change the server address. Don't change anything else.
In first you can try to connect using the serial number. Change meter address type from Default to SerialNumber. Then set serial number of the meter 2. Try to connect.
If it fails, some meters expect that you will add meter 2 to the SAP Assignment table of meter 1. This is more complicated, so start with the serial number.
BR,
Mikko
Thanks for your kind replies.
Thanks for your kind replies.
However, the address type has no selections other than default.
And for the Scenario 3, there's only one meter connected. How, in this case, do we set the SAP Assignment table in another meter?
Hi,
Hi,
It might be that your meter type hasn't ever been read with multidrop. Who is the manufacturer of your meter?
In Scenario 3 you need to add meter #2 logical device name to meter #1 SAP Assignment table. Let's hope that your meter is using a serial number. It's easier because you don't need to configure meter #1.
BR,
Mikko
Hi Mikko,
Hi Mikko,
The meter is a Holley 3 phase AMR meter, and they do support multi drop.
Perhaps you meant Scenario 2 here.
It does has the serial number and will try to find a way to config it in the Director.
Thanks.
Hi Mikko,
Hi Mikko,
I would like to update you on an almost-successful connection, which I tested with the Physical Address settings as 18 (added 16). From the logs, there were a bit of responses but then the meter disconnects.
I hope you can help to decipher the logs below for a solution:
18:26:26
<HDLC len="9" >
<TargetAddress Value="12" />
<SourceAddress Value="10" />
<FrameType Value="93" />
<Snrm>
</Snrm>
</HDLC>
18:26:26
<HDLC len="1D" >
<TargetAddress Value="10" />
<SourceAddress Value="12" />
<FrameType Value="73" />
<PDU>
<Ua>
<MaxInfoTX Value="200" />
<MaxInfoRX Value="200" />
<WindowSizeTX Value="1" />
<WindowSizeRX Value="1" />
</Ua>
</PDU>
</HDLC>
18:26:26
<HDLC len="2A" >
<TargetAddress Value="12" />
<SourceAddress Value="10" />
<FrameType Value="10" />
<PDU>
<AssociationRequest>
<ApplicationContextName Value="LN" />
<InitiateRequest>
<ProposedDlmsVersionNumber Value="06" />
<ProposedConformance>
<ConformanceBit Name="GeneralProtection" />
<ConformanceBit Name="GeneralBlockTransfer" />
<ConformanceBit Name="DeltaValueEncoding" />
<ConformanceBit Name="BlockTransferWithGetOrRead" />
<ConformanceBit Name="BlockTransferWithSetOrWrite" />
<ConformanceBit Name="BlockTransferWithAction" />
<ConformanceBit Name="MultipleReferences" />
<ConformanceBit Name="Access" />
<ConformanceBit Name="Get" />
<ConformanceBit Name="Set" />
<ConformanceBit Name="SelectiveAccess" />
<ConformanceBit Name="Action" />
</ProposedConformance>
<ProposedMaxPduSize Value="FFFF" />
</InitiateRequest>
</AssociationRequest>
</PDU>
</HDLC>
18:26:31
<HDLC len="9" >
<TargetAddress Value="10" />
<SourceAddress Value="12" />
<FrameType Value="1F" />
<DisconnectMode>
</DisconnectMode>
</HDLC>
Thanks.
Hi,
Hi,
The reason can be anything. I believe that your server address is invalid and the connection fails when you try to connect to the meter. Ask the meter vendor for the correct settings.
BR,
Mikko
Dear Mikko,
Dear Mikko,
Noted, will check.
Thanks.