when you get up to lab10 you will notice
expAdd ("gMotorVars.Vd", getQValue(24));
expAdd ("gMotorVars.Vq", getQValue(24));
expAdd ("gMotorVars.Vs", getQValue(24));
expAdd ("gMotorVars.VdcBus_kV", getQValue(24));
expAdd ("gMotorVars.Id_A", getQValue(24));
expAdd ("gMotorVars.Iq_A", getQValue(24));
expAdd ("gMotorVars.Is_A", getQValue(24));
in these labs we are only "getting" these values in the background task, which is good enough for viewing in CCS watch window. If you want them every cycle you have to add the _get function into the ISR....but then you have to do something with them...you can see proj_lab5f for an example of how the DLOG functions are used for this sort of thing to buffer up data.
Yes, agree that doing things by hand can only go so far. To test torque or speed controllers you should give step inputs and plot response to tune for best over/under shoot and settling time. This can be done using the graph functions.
Internally we have some projects set-up to do this testing, but it hasn't been added to MotorWare quite yet....
