• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 83 subscribers
  • Views 819 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.

TMS320F28069: G3 Host Message protocol specification

Marco Cane
Prodigy 40 points

Part Number: TMS320F28069
Other Parts Discussed in Thread: AFE031

good afternoon to every one,

I'm trying to build a small PLC network using the TMS320 + AFE031. I got the development kit and the attached "G3 Host Message protocol specification" but there are a lot of "black holes".

In principle I don't need the full G3 stack, my idea was to just transfer data over the PLC, implementing my own protocol on top of the basic "data transfer messages".

The problem are:

1. it is not clear what the different "device modes" mean, i.e. if one of them can suit my needs.

2. in the DATA_TRANSFER section it states for G3 normal data transfer a standard IPv6 data packet must be used as a payload, while in lower MAC mode it is not clear what the HCT Connection Handle is

Can someone help me in clarify all these points?

thanks in advance

  • 0
    TI__Guru* 82590 points
    Marco,
    Can you clarify which development kit(full order-able Part Number) you have, and I'll try and get this pointed in the right direction.

    Matt
  • 0 in reply to MatthewPate
    Prodigy 40 points

    Hi Matt,

    the development kit should be the TIDM-TMDSPLCKIT-V3. I do not know the exact version because it was given to me by our supplier. They also gave to me the G3_DDK_Package_V7_8_1_6 as reference which contains the version 2.0.31 of the Host Message Protocol Specification.

    What I need to know is if I can avoid to use the IPv6 header + payload structure and just send the raw data into the payload of DATA_TRANSFER requests. By the way it's not clear why the IPv6 header is used, because for example the source address and destination address used by your Intermediate GUI does not refer to the ones specified inside any mask of the tool and I got a test sw by our supplier in which almost all fields of the IPv6 message are blank (like source/destination address and even the whole UDP header).

    Please consider I do not need to be compatible with any one, I need to use the powerline communication and G3 modulation in a "private" network, where the protocol is fully custom.

    Thanks in advance

  • 0 in reply to Marco Cane
    Prodigy 40 points

    Hi,

    one more point; I did not find in any document a clean explanation of what the "device mode" are and how they work. could you please also provide some links to clarify this point?

    thanks again

  • 0 in reply to Marco Cane
    TI__Genius 10345 points

    hi ,

    if you look at Table 2 of the g3_hostmsg.pdf , the device modes are mentioned .

    The Normal Mode : can be used when we want to connect the devices in a network , multi nodes . The host can be another device sending host messages to the modem.

    p2p - can be used when we want only point to point communication and not point to multi point communication.The host can be another device sending host messages to the modem.

    The other 2 modes are used when the device is also running the App EMu application or the host is also on the modem.

    As far as stripping the ipv6 header data , we don't provide the option of removing that as such in the firmware.

    You could look at the raw data in the log of the Zero config gui to get an idea of how to populate the data .

    Regards.

  • 0 in reply to MEGHANA MANAVAZHI
    Prodigy 40 points

    hi,

    thanks for your reply, the problem is that is not clear how to properly setup a full and reliable communication; for example I tried to setup the Normal Mode but, even if the setup ends correctly, the modem is not properly initialized and I always receive an error code not present into the status code table (and the data are not sent).

    At the moment I'm running with the P2P mode, with or without the IPv6 encapsulation, and I'm able to poll several nodes, one by one. The problem I'm facing are multiples:

    1. the communication is really slow, since I have to send a message and wait for the reply (turn around time is more or less 250ms); maybe with the normal mode I would be able to send/receive more messages in a shortest time, like in a ethernet network?

    2. if I turn off one of the module, on power up it takes a very long time (several minutes) before being able to transmit again (even if it is able to receive)

    Could you please explain how to properly setup a full network and if this setup will allow me to poll nodes at a higher speed?

    thanks