AM2434: What is difference between Eval and Prod package of Industrial Communications SDK and Motor Control SDK ?

Hideaki Matsumoto said:

What is difference between Eval and Prod package ?

Even though all stack libraries except ethercat_subdevice_bkhf_ssc.am243x_evm.r5f.ti-arm-clang.release.lib and ethercat_subdevice_bkhf_ssc.am243x_lp.r5f.ti-arm-clang.release.lib (built using Beckhoff SSC and with time limited eval version and can be found in ind_comms_sdk\source\industrial_comms\ethercat_slave\stack\lib ) are production version, due the presence of these two libraries - we can NOT keep production license in installer package (though that was always the original intent). So, we created Prod package to grant production license to our customers cleanly. Eval license will continue to exist which might integrate 3P eval demos like FSoE stack for eg:- in future

Hideaki Matsumoto said:

Same software? Or any limitation on Eval software ?

Yes, the software is same. No limitation on Eval software, actually if someone wants to evaluate EtheCAT funtionality without downloading Beckhoff SSC stack, this package is the option. Other functions remain identical.

Hideaki Matsumoto said:

Is it possible to use Production package at the evaluation targeting Production in the future ?

Yes - of course

Hideaki Matsumoto said:

Is it possible to use Evaluation package for the production if they would sign on additional licenses for production ?

Lets discuss this point offline, I want to understand the background

Hideaki Matsumoto said:

They have to change the SDK from Eval to Prod after evaluation ?

This is up to them. As mentioned above this is more of clickwrap license and packaging constraint on TI side than anything to do with licensing.