Test set fails on "issue st 0 1.0" command

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install the standard test set
2. Start both the slave and master
3. Attempt to issue a setpoint from the master

What is the expected output? What do you see instead?
I would expect the value to show up in the slave.  Instead one gets a not 
implemented message.

What version of the product are you using? On what operating system?
TS 0_9_0 on Windows 7

Please provide any additional information below.
Value shows up in the log(I think).  We had a valid master trying to send a 
setpoint - which failed.  We then tried DO_ONLY as the type of setpoint, which 
failed.  We then went back to the default XML files and used the test set 
master, which failed to issue the setpoint. 

Original issue reported on code.google.com by oenon...@yahoo.com on 7 Jul 2010 at 9:40

[GoogleCodeExporter]

It seems we may want to change the defaults for the slave test set. It supports 
all AO types even floating point ones! The Slave test set returns 
"NOT_SUPPORTED" for all controls/setpoints by default, although you may have 
just convinced me that the default should be SUCCESS. To change the response 
type, use the slave's "response" terminal command:

>help response //prints info on this command
>response ALL ALL SUCCESS // any command/setpoint with a valid index will 
return success

Hopefully this is well documented in the testset docx.

The master "auto selects" the type to send based on the type of the value, i.e.:

>issue st 0 1      // causes the master to send a Grp41Var2
>issue st 0 65536  // "" Grp41Var1
>issue st 0 1.0    // Grp41Var3

Original comment by jadamcrain on 7 Jul 2010 at 10:36

[GoogleCodeExporter]

Consider changing default response behavior to CS_SUCCESS.

Original comment by jadamcrain on 7 Jul 2010 at 11:22

• Changed state: WontFix