On an aside; will changing a payload's values programmattically on-the-fly via the above quoted $PLST_GRP1[1].$PAYLOAD=(n) system variable set mess with the motion planning algorithm that FANUC has running in the background to calculate motor torque, current draw, encoder counts/speed rates/whatever type of PID algorithm they have going on? I always assumed that changing the variable as it's being used could cause corruption of the motion planner.
I was also not really sure about this, as when someone manually changes any value inside the payload schedule page, we get a "Path and Cycletime will change. Set it?" message, not sure it after hitting “Yes” a new calculation was made but dynamically modifying the variables could result on something like what you mention, but maybe not and this is just a warning for just entering the value and it would be the same as modifying the variables directly.
Tests will say