AM2432: Feature Codes: Technical and licensing for EtherCAT Support

Part Number: AM2432
Other Parts Discussed in Thread: AMIC110,

Hello, I'm trying to figure out the landscape of the features and licensing models for using this processor on an EtherCAT project.  I have spent a lot of time trying to figure it all out. 

My current EtherCAT-enabled design is on an AMIC110, and is based on the Beckhoff SSC.  This new design will use the AM2432.  I have both technical and licensing questions on the EtherCAT supported on each Feature code.

My understanding is that the "F" code supports the TI integrated stack, while the "E" version supports third-party stacks, like the Beckhoff SSC.  The "D" code does not support any EtherCAT implementations.

For the "E" version, I must get the SSC stack from the ETG, and compile it myself.  This is what I currently have for the AMIC110 application.  So with minimal (!) work this should compile and run on this version.

For the "F" version, the TI stack is embedded somehow, and I would interact with it via an API.  Does the "F" version also support the Beckhoff SSC stack?

Now, on to licensing.  Please confirm my understanding. 

If I use the Beckhoff SSC code, I get a license for that code from ETG, correct?

If I use the TI embedded stack, I get the license for the stack by purchasing the processor with the "F" code, correct?

Finally, Is there a technical advantage of using the TI stack over the Beckhoff stack?  Is it smaller or faster?  Is the code to interact with it cleaner or easier in some way?

Thanks!

John Ford

 

  • Hello John Ford,

    My understanding is that the "F" code supports the TI integrated stack, while the "E" version supports third-party stacks, like the Beckhoff SSC.  The "D" code does not support any EtherCAT implementations.

    Yes. Correct.

    For the "F" version, the TI stack is embedded somehow, and I would interact with it via an API.  Does the "F" version also support the Beckhoff SSC stack?

    Yes. The 'F' part also supports Beckhoff SSC stack. Please refer AM243x INDUSTRIAL COMMUNICATIONS SDK: EtherCAT SubDevice Beckhoff SSC Demo.

    If I use the Beckhoff SSC code, I get a license for that code from ETG, correct?

    If I use the TI embedded stack, I get the license for the stack by purchasing the processor with the "F" code, correct?

    The Beckhoff SSC source code can be accessed if you are a valid ETG member. The TI EtherCAT stack examples available in Industrial Communications SDK are time limited. For non-time limited version, you need to acquire the Beckhoff SSC source code and recompile the library. Please find the details here: EtherCAT SubDevice: Beckhoff SSC. For more licensing options please contact your regional TI sales team.

    Hence, in both cases, you need to get a license from Beckhoff or ETG.

    Finally, Is there a technical advantage of using the TI stack over the Beckhoff stack?  Is it smaller or faster?  Is the code to interact with it cleaner or easier in some way?

    TI stack is built on top of Beckhoff SSC stack and adding features for easy to use. TI EtherCAT SubDevice can support up to 50us DC cycle time. Please refer EtherCAT SubDevice: Introduction

    Kind Regards,

  • Thanks.  I was under the impression that the TI stack was independent of the Beckhoff SSC.

    John