Just wanted to add some notes about PAM-D testing...
Never say "everything OK" too early, I launched STS-51G scenarios, 3 PAM-D satellites.
There are times, when everything works, and there are times when not everything works.
I loaded launch scenario:
1) one time everything OK
2) second time - SPIN1 OK, SPIN2 OK, but SPIN4 shows RPM value -1, and when pressing RPM+ satellite disappears.
similar on orbit, actually there was
1) one time OK
2) second time SPIN1 OK, but if I remember SPIN2 showed RPM value 15004,
pressing RPM+, satellite disappeared.
Seems quite random thing, SPIN1 always seems OK, but other SPINtables can "malfunction", I noticed, when I saw RPM "0" for appropriate SPIN, that means - it will work.
If RPM is -1, or 15004, or something like that (non zero value) - a failure will be.
P.S. Maybe that's idea - to simulate random malfunction of spintables,
P.S.2 After this post I launch on orbit scenario a couple of times - everything was OK. As I saw RPM values "0" I knew all spin tables will be OK, and it was OK. Hm, really seems random.
So it mostly works, and is not a big issue.
And I launched again several times - everything was OK. So maybe its an Orbiter issue ( I run Orbiter 2016, not BETA) , so after all, nevermind...