And just in case someone experienced sees this:
The scrips feature a few "bad" workarounds to expose some settings, like overrun detection, com in background, or change some setting like core count, frequency,...
is there a better, official way to do this?
Another issue, while I can change the target ip in simulink, my deployer always uses the ip from the script, so that, wheenever I want to changee the target ip, I need to run the script again