Hello @hayaoki7
We are working to remove the busses data type loaded in the workspace that you have attached in the picture. Hopefully, this will be added in the next release.
1: I tried to generate code for the PMSM model. It takes longer than the S32K14. Will this code generation time be improved in the release version?
The S32K3 Toolbox is way different than the S32K1. First, we have introduced the usage of an external configuration tool, so instead of having configuration blocks, like in K1 ewe now let our customers use either EB Tresos or S32CT to generate the configuration files. And this comes with a huge advantage: our customers have access to all the settings for the MCU: pins, clocks, peripherals. The second difference is that the K1 generates code on top of NXP S32SDK while the K3 generates code on top of the NXP RTD. So there are some more files there. This explains why the code generation time alongside the building process time got increased. Of course, the code is not generated every time for the external configuration tool, but only when the project has been changed.
2: Release of a compatible model of MCSPTE1AK344
Of course, our plan is to support this MCSPTE1AK344 board, but I cannot provide a timeframe yet. The actual PMSM model delivered with the current release uses the S32K3X4EVB-Q257 + GD3000 so I guess that for the hardware connection, you have to check the pinout compatibility and most likely the motor type.
3: Does it support MCB?
I see no reason why the MathWorks' Motor Control Toolbox shall not be compatible with our toolbox, so I think you can use both. Let us know if you encounter any issues.
4: Is there a plan to support R2021B with the release version of S32K3_MBD?
You can already install our toolbox in R2021b. I've tried some models in R2021b and they work just fine.
Hope this helps,
Marius