Access to spectrum data

I would like to get the command data from the spectrum radio for use in my script. Is this something that can be accessed.

I want to read the joystick positions on the transmitter and use them in my program.

try getvalue(_K, n) where n is the channel number

Where did you find this information. I see nothing in the documentation. Do you have additional information for spectrum perimeters that I can read in this envirnment?

I get \"_k is not a valid named constant\" from the compiler.

the query ?K is what you would use from the console to read the spektrum radio data. Test this first.

To read a operating parameter from microbasic you need to use the getvalue() function and replace the ? with _. So _K.

But you may have to do this while the controller is attached to the PC. This is because _K is a relatively new addition and that it may not be in the off-line command dictionary.

When the controller is attached, whenever you click on the Scripting tab, the controller dumps the latest list of commands implemented in the firmware.

It works from the console using the ?_K
I am not sure what the numbers represent.

This is the code I tried to compile.


print(\"spectrum data 1 \", getvalue(_K, 1), \"\\n\")
print(\"spectrum data 2 \", getvalue(_K, 2), \"\\n\")

these are the errors
1 \'_K\' is not a valid named constant
2 \'_K\' is not a valid named constant

Strange that it wouldnt work.

Try getvalue(33,1) and getvalue(33,2)

To help us troublshoot:

Go to console tab
Clear Log
Go to Scripting tab
Go back to console tab
Copy log

Then paste the log here on in a file and send.

Not sure exactly what you want.
I cleared the con log.
put
getvalue(33,1)
getvalue(33,2)

in the script compiled and copied the output

# C
|~
|~=FL:0:6
|~=CAD:1:0
|~=OVL:2:2
|~=THLD:4:0
|~=MXMD:5:0
|~=PWMF:6:2
|~=CPRI:7:0
|~=RWD:8:2
|~=PMS:10:0
|~=ACS:11:0
|~=AMS:12:0
|~=CLIN:13:0
|~=DFC:14:3
|~=DINL:16:6
|~=DOA:17:0
|~=DOL:18:6
|~=AMOD:19:0
|~=AMIN:20:2
|~=ACTR:22:2
|~=ADB:23:0
|~=ALIN:24:1
|~=AINA:25:0
|~=AMINA:26:0
|~=APOL:28:0
|~=PMOD:29:0
|~=PMIN:30:2
|~=PMAX:31:2
|~=PCTR:32:2
|~=PLIN:34:1
|~=PINA:35:0
|~=PMINA:36:0
|~=PMAXA:37:0
|~=PPOL:38:0
|~=MXPF:40:0
|~=MXPR:41:0
|~=ALIM:42:2
|~=ATRIG:43:2
|~=ATGA:44:0
|~=KP:46:0
|~=KI:47:0
|~=KD:48:0
|~=PIDM:49:0
|~=ICAP:50:0
|~=MDEC:52:5
|~=MVEL:53:5
|~=MXRPM:54:2
|~=MXTRN:55:5
|~=CLERD:56:0
|~=BLSTD:58:0
|~=BLFB:59:0
|~=BHOME:60:5
|~=BLL:61:5
|~=BHL:62:5
|~=BHLA:64:0
|~=SXC:65:0
|~=SXM:66:0
|~=ZAIC:67:3
|~=ZPAO:68:3
|~=TELS:70:7
|~=BRUN:71:0
|~=EMOD:72:0
|~=EPPR:73:2
|~=ELL:74:5
|~=ELLA:76:0
|~=EHLA:77:0
|~=KPC1:78:0
|~=KPC2:79:0
|~=KIC1:80:0
|~=KDC1:82:0
|~=KDC2:83:0
|~=EHOME:84:5
|~=SKUSE:85:0
|~=SKMIN:86:2
|~=SKCTR:88:2
|~=SKDB:89:0
|~=SKLIN:90:1
|!
|!=G:0
|!=P:2
|!=S:3
|!=C:4
|!=CB:5
|!=VAR:6
|!=DC:8
|!=DS:9
|!=D1:10
|!=D0:11
|!=R:12
|!=EX:14
|!=MG:15
|!=MS:16
|!=NX:17
|!=GP:18
|!=RC:20
|?
|?=A:0:3
|?=M:1:3
|?=P:2:3
|?=C:4:5
|?=CB:5:5
|?=VAR:6:5
|?=SR:7:3
|?=CR:8:5
|?=BS:10:3
|?=BSR:11:3
|?=BA:12:3
|?=V:13:2
|?=D:14:4
|?=AI:16:3
|?=PI:17:2
|?=T:18:1
|?=F:19:5
|?=FS:20:0
|?=AD:22:2
|?=DO:23:0
|?=E:24:5
|?=CIS:25:5
|?=CIA:26:5
|?=TM:28:0
|?=LK:29:0
|?=FID:30:7
|?=TRN:31:7
|?=TST:32:5
|?=CP:34:0
# C
#

When I put the
getvalue(33,1)
I get
No sub routine named \'getvalue\' that takes \'2\' arguments

The console dump shows that not all the codes are correctly captured. This is a bug when used with USB for which we have a fix for.

However, getvalue(33,1) should not give an error. It works fine here. You should install and use the latest roborun.

Code tested:
print(getvalue(33,1))