• State Resolved
  • Locked Locked
  • Replies 12 replies
  • Subscribers 82 subscribers
  • Views 2255 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Not able to connect TMDSDC3359 board with L+G E450 meter

Vamsi Marri
Prodigy 115 points

Hello,

I am trying to connect TMDSDC3359 Data Concentrator (with G3 firmware in CENELEC A band) with a landis + gyr E450 G3 meter. But I am not able to establish a connection between them. At least I am not able to debug the connection.

Earlier I tried to connect the TMDSPLCKITV4-CEN service node with TMDSDC3359 Data Concentrator and everything was working. But I don't have much luck with the Landis + gyr meters.

May I know what parameters should I change in order to establish the connection?

Is there a way to debug the connection between them? I am currently using g3_evt_mon_AM335X binary file to monitor the events. But it is not giving any output. In one of the documents (TI_plcSUITE_g3_dc_mgmt_intf_msg) it is mentioned that "separate Sniffer Build Provided" for debugging purpose. But I have only found g3_evt_mon_AM335X binary file for this purpose.

Thanks in advance.

Best regards,
Vamsi.

  • 0
    TI__Genius 10345 points

    hi Vamsi ,

    When you say the meter is not connecting , are you saying so because you don't see any activity on the event monitor ?

    with the same connections and using the TI meter PLCv4 kit you do see event on event monitor ?

    You can use the g3_mgmt_cli_AM335x to check the neighbor table as well as the route table to see if any node has joint and got routes .

    Are the connections from DC to the meter appropriate ?

    is this a 3 phase meter ? can we check with only phase B and neutral connections between DC and meter as in PLCv4 kit case ?

    We don't provide the Sniffer Build with the package .

    Regards.

  • 0 in reply to MEGHANA MANAVAZHI
    Prodigy 115 points

    Hi Meghana,

    Thanks for the reply.

    Yes, I don't see any activity in the event monitor and I also checked with the g3_mgmt_cli_AM335x binary. I also don't see any trace of a new node.

    Yes, with the same connections I was able to see events in the event monitor with TI meter PLCv4 kit and I was able to ping the other device.

    Yes, the connections are appropriate because similar connections are working with the TI meter PLCv4 kit.

    The Meter is a 3 phase meter and we were able to connect to a L+G DC with 3 phases.

    Since the PLCv4 kit is only having single phase, I have tried connecting with different phases by changing the connections and jumpers. It was working fine with that kit but not with the L+G DC.

    May I know which sniffer tool do you provide for the debug purposes? I have also seen in the documentation that the promiscuous mode can not be enabled.

    Thanks,
    Vamsi.

  • 0 in reply to Vamsi Marri
    TI__Genius 10345 points

    hi Vamsi,

    We dont provide sniffer tool. you can use sniffer from any other vendor that support G3 .

    "The Meter is a 3 phase meter and we were able to connect to a L+G DC with 3 phases." can you check with only phase B connection of the meter as in the PLCv4 kit ?

    "Since the PLCv4 kit is only having single phase, I have tried connecting with different phases by changing the connections and jumpers. It was working fine with that kit but not with the L+G DC." does that mean that the PLCv4 kit with the L&G DC is not working ? Have you tried with single phase connections here as well for now ?

    in this case you can use the Zero config GUI on the SN side to check the packets being received and sent by the SN .

    Regards .

  • 0 in reply to MEGHANA MANAVAZHI
    Prodigy 115 points

    Hi Meghana,

    Thanks for the reply.

    I have tested a L&G meter and a L&G DC with single phase and the connection is working fine.

    I have also tried connecting PLCv4 kit with the L&G DC. This is not working. Please check the below image for the error message when I try to connect to the DC.

    I am not aware of such sniffer tools. Could you please suggest one.

    Thanks,
    Vamsi.

  • 0 in reply to Vamsi Marri
    TI__Genius 10345 points

    hi Vamsi ,

    The error that you see is 0x50c0 which is for ADP_STAT_AUTH_FLR. This happens if the authenticator cannot authenticate the peer (unacceptable Responses to one or more Requests),
    then after unsuccessful completion of the EAP method in progress.

    Is the psksvr_AM335x running in the DC ?

    Are the keys like the psk key (PIB adpPSK 0x1F ) set the same for both DC and SN ? The join would be declined in such case ...

    use send raw data in SN side .( key is 0x3C 00 FF FF 0F 00 00 00 00 00 00 00 00 00 00 00)

    0x0D 80 1C 00 C2 44 5C D1 1F 00     0x00 00 00 00 10 00 3C 00 FF FF
        0x0F 00 00 00 00 00 00 00 00 00     0x00 00

    Use pskeuilist to set key at DC for the SN

    details of the same on how to create the pskeuilist etc given in 1.1     Default example PSK Server of TI G3 DC Interface Guide.

     

    Regards.

  • 0 in reply to MEGHANA MANAVAZHI
    Prodigy 115 points

    Hi Meghana,

    Thanks for the reply. It took some time for me to get the right PSK. Now I have tried the pskeuilist (white list) and I am able to successfully attach the L+G E450 meter with the TMDSDC3359 board.

    Now I am having another problem . The Meter is getting a short address (0x1) from the DC but when I try to use the ping or udpIPv6App_AM335X I am not getting any response from the meter. Here is the output I am getting:

    ./udpIPv6App_AM335X -l 32 -s 0x1 -u 61616
scopeId : 3
opened socket , ipv6Fd - 3
Sending packet (32 bytes) to <fe80::7455:00ff:fe00:0001 :: 61616>
Waiting for packets ....
No response from service node !!

    Here is the output from g3_evt_mon_AM335X:

    --------------------------------------------------------------------------
    Event Nr: 9
    Time: Thu Jun 23 16:13:15 2016
    Event type: G3_EVT_TYPE_TMP_SENT
    Sent TMR response to Addr(0x0001), LQI (0x70) TxMod(0x3), ToneMap(0x0000003f)
    --------------------------------------------------------------------------
    --------------------------------------------------------------------------
    Event Nr: 10
    Time: Thu Jun 23 16:13:15 2016
    Event type: G3_EVT_TYPE_MAC_RECEIVE_PACKET
    G3 MAC RX Packet MCS(0x00) DIF-COH(0x00) SrcAddr(0x0001) LQI(0x70) Phase(0x00) Tonemap(0x0000003f
    --------------------------------------------------------------------------
    --------------------------------------------------------------------------
    Event Nr: 11
    Time: Thu Jun 23 16:13:51 2016
    Event type: G3_EVT_DATA_CONFIRM
    G3 Data confirm Status(0x5088) msdu-handle(0x00) destAddr(0x01)
    --------------------------------------------------------------------------

    When I try ping, I am not getting any reply and I also don't see any event from the g3_evt_mon_AM335X

    ping fe80::7455:ff:fe00:1
PING fe80::7455:ff:fe00:1 (fe80::7455:ff:fe00:1): 56 data bytes

    I didn't have any problem when I use PLCV4 kit with the DC. I could run both the applications. May I know what could be the problem.

    Thanks once again for your support.

    Best regards,
    Vamsi.

  • 0 in reply to Vamsi Marri
    TI__Genius 10345 points

    hi Vamsi ,

    the 0x5088 error you are getting in DC log is for ADP_STAT_ROUTE_ERROR.

    which could mean that the DC does not have a proper route to the node or the SN does not know the route to DC ?

    can you check the route table in the DC using the g3_mgmt_cli and see if the SN is part of the DC route table ?

    Also check on SN side using intermediate GUI ?

    Regards .

  • 0 in reply to MEGHANA MANAVAZHI
    Prodigy 115 points

    Hi Meghana,

    Thanks for the reply.

    Here is the output I am getting with the g3_mgmt_cli_AM335X and g3_evt_mon_AM335X. I won't be able to debug from the SN side because it is a L+G meter. Now I have a route to the SN. Even then I am not able to communicate.

    >> get-mac-node-info
PAN ID = 0x7455
Short Addr      Extended Addr
-----------------------------------
0x0002          bd77:14ff:ff93:0f00
0x0000          ffee:ddcc:bbaa:9988
-----------------------------------

>> get-route-table

>> discover-route -da 0x2
Request sent ..

>> get-route-table
Route Table:
Dest<0x0002> / NextHop<0002> / Age<1440 min> / Cost<11> /hopCnt (1) weakLink (0)

>> get-neighbor-table
Neighbor Table Entry:
------------------------------------------------------------------------------------------------------
addr   TxMod Gain  Res  LQI  ToneMap    MpTime TblTime Phase RxLQI TxCoeff              DiffCoh  LongCp
------------------------------------------------------------------------------------------------------
0x0002 0x00  0x00  0x00 0x00 0x00000000 0x00   0xfe    0x00  0x70  0x00:00:00:00:00:00  0x00     0x00

    UDP application

    root@beaglebone:/usr/bin/G3# ./udpIPv6App_AM335X -l 100 -s 0x2
scopeId : 3
opened socket , ipv6Fd - 3
Sending packet (100 bytes) to <fe80::7455:00ff:fe00:0002 :: 61617>
Waiting for packets ....
No response from service node !!

root@beaglebone:/usr/bin/G3# ./udpIPv6App_AM335X -l 100 -s 0x2 -u 61616
scopeId : 3
opened socket , ipv6Fd - 3
Sending packet (100 bytes) to <fe80::7455:00ff:fe00:0002 :: 61616>
Waiting for packets ....
No response from service node !!

    Output from the g3_evt_mon_AM335X

    --------------------------------------------------------------------------
Event Nr: 1
Time: Fri Jun 24 17:54:23 2016
Event type: G3_EVT_TYPE_TMP_SENT
Sent TMR response to Addr(0x0002), LQI (0x70) TxMod(0x3), ToneMap(0x0000003f)
--------------------------------------------------------------------------
--------------------------------------------------------------------------
Event Nr: 2
Time: Fri Jun 24 17:54:23 2016
Event type: G3_EVT_TYPE_MAC_RECEIVE_PACKET
G3 MAC RX Packet MCS(0x00) DIF-COH(0x00) SrcAddr(0x0002) LQI(0x70) Phase(0x00) Tonemap(0x0000003f
--------------------------------------------------------------------------
--------------------------------------------------------------------------
Event Nr: 3
Time: Fri Jun 24 17:54:23 2016
Event type: G3_EVT_TYPE_ROUTE_UPDATE
R-REPLY dst(0x0002) NextHop(0x0002) Metric(0xf) RC(0x0b) HC(0x1) WL(0x00)
--------------------------------------------------------------------------
--------------------------------------------------------------------------
Event Nr: 4
Time: Fri Jun 24 17:54:23 2016
Event type: G3_EVT_TYPE_ROUTE_DISC_RESP
Route discover result:
<0x00> - SUCCESS
--------------------------------------------------------------------------
--------------------------------------------------------------------------
Event Nr: 5
Time: Fri Jun 24 17:56:31 2016
Event type: G3_EVT_DATA_CONFIRM
G3 Data confirm Status(0x00) msdu-handle(0x00) destAddr(0x02)
--------------------------------------------------------------------------
--------------------------------------------------------------------------
Event Nr: 6
Time: Fri Jun 24 17:56:59 2016
Event type: G3_EVT_DATA_CONFIRM
G3 Data confirm Status(0x00) msdu-handle(0x00) destAddr(0x02)
--------------------------------------------------------------------------

    Thanks,

    Vamsi.

  • 0 in reply to Vamsi Marri
    TI__Genius 10345 points
    hi Vamsi ,


    From the event log the DC has sent out the packet to the SN .
    "No response from service node !!" means that the DC has not got anything from the SN .

    Now there are 3 ways to this either try using a ping instead of ./udpIPv6App_AM335X

    test using ping6 -I tun0 FE80::7455:00FF:FE00:0002 -c 1 -s 1

    Or check at the SN end to see if the SN has received the ping or not .

    or Can you get me the blacklist table (0x1E) in case the ping did not complete onto the line ( i doubt this option is not the case )?

    Regards.
  • 0 in reply to MEGHANA MANAVAZHI
    Prodigy 115 points
    Hi Meghana,

    Thanks for the reply.

    Now the ping is working. There are multiple problems. First there is a routing problem and then ADP minimum level security setting. Now I have adjusted these and I am able to communicate with the meter successfully.

    But I am still not able to communicate via udpIPv6App_AM335X application. Any idea?

    Thanks once again for your help.

    Best regards,
    Vamsi.
  • 0 in reply to Vamsi Marri
    TI__Genius 10345 points

    hi Vamsi ,

    the thing would be to check at the meter end if the packet is really being received .

    Also is the meter replying to the DC message ...?

    This i say as the tables at DC end seem good so the thing could only be the meter not knowing the route .

    but again if the ping at the setup works even the udpIPv6App should...

    i retried here with the below commands : ( the udpIPv6App is same as your udpIPv6App_AM335X)

    root@am335x-evm:~/PLC/G3_DC#  ./udpIPv6App -l 32 -s 0x1 -t 10
    scopeId : 12
    opened socket , ipv6Fd - 3
    Sending packet (32 bytes) to <fe80::7455:00ff:fe00:0001 :: 61617>
    Waiting for packets ....
    No response from service node !!

    This is got as there was no such node in my tables ...


    root@am335x-evm:~/PLC/G3_DC#  ./udpIPv6App -l 32 -s 0x2 -t 10
    scopeId : 12
    opened socket , ipv6Fd - 3
    Sending packet (32 bytes) to <fe80::7455:00ff:fe00:0002 :: 61617>
    Waiting for packets ....
    Sent packet length <32 bytes>, received packet length <32 bytes>
    Checking pattern ...... matches !!
    Round trip time (in millisecs) - 390

    This command works well .

    Regards .

  • 0 in reply to MEGHANA MANAVAZHI
    Prodigy 115 points

    Hi Meghana,

    Thanks again for trying out the UDP application.

    As I told you earlier, we don't have a means to check the communication at the Meter side.

    It is also very strange to me that ping is working very well but not the UDP application. I know the destination port is open and the meter is accepting connections. I will see what I can do about that.


    Best regards,
    Vamsi.