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.

TCP/IP enabled PLC



Hello,

I am interested in establishing a TCP/IP communication between two host environments connected through the TMDSPLCKIT-V3 PLC kit. Currently, the plc kit only features (virtual) UART communication, but I prefer to use Ethernet connections in both ends instead. I am not started on the development yet, so I seek some advice and guidelines on how to attack this problem in the best way. As I see it, there are three options:

1. Use an additional 'host' microprocessor, which acts as an ethernet to serial converter. For example using the Stellaris S2E board.

Advantage: Direct Ethernet connection from host PC, a lot of possible configurations (different protocols / translators etc. can be implemented). Disadvantage: Uses another, external microprocessor, adds to complexity.

2. Concerto MCU that uses the C2000 DSP part for PLC communication and the M3 part for host tasks, similar to 1) but in the same package. The Concerto MCU also has a devkit with the C2000 devkit socket that fits into the PLC kit - but will I be able to use the PLC libraries directly on a Concerto platform?

Advantage: Same as 1). Disadvantage: Not using the same MCU as the PLC kit, so incompatibilities might arise. Also, Concerto MCUs are not that mature yet.

3. Implement PPP directly on the PLC F28069 DSP, for example using lwIP PPP code.

Advantage: Only one DSP, using the same PLC kit platform. Disadvantage: Not Ethernet, might affect the performance of the PLC functionality, must interface to the PLC libraries which are without source code (makes debugging a hard time).

 

Currently, I'm judging that option 1) is the best. However, if someone knows more about C2000 / Concerto compatiblity, I would appreciate to hear what your thoughts are.

Thanks in advance,

Joachim Johansen

  • Joachim,

    These are all reasonable options.  However, which options are possible will depend on what type of PLC communication you need.  Are you looking to do PRIME, G3, etc or would a TI proprietary implementation be fine as long as the communication was robust?  What kind of data-rates do you expect?  Do you need to be a particular band to meet regulations (ie if you're in Europe you should broadcast in the CENELEC-B band unless your communication will be used by the grid companies).

    My first reaction would be to go with option (1).  With (1) you'll trade a bit of end system cost for a sufficiently shortened development time.  This of course could change depending on your specific requirements.


    Thank you,
    Brett