Request: DIAG_PILOT_SETS_F and DIAG_STATE_F

[GoogleCodeExporter]

What steps will reproduce the problem?
1. How could I use the RF Online, for example, as I can interpret the commands 
return DIAG_PILOT_SETS_F and DIAG_STATE_F

Original issue reported on code.google.com by fap...@gmail.com on 2 Jul 2013 at 9:26

[GoogleCodeExporter]

What?

I'm assuming you mean how would you send those commands? I guess the best way 
currently would be to script it with something like

qc = CommandFactory.GetCommand(Qcdm.Cmd.DIAG_STATE_F)
cdmaTerm.Q.Add(qc)
cdmaTerm.Q.Run()

then you could see the result in the log tab... I could probably parse it out 
if you have the 'struct' or the meaning of the bytes--it's not something I've 
ever needed though... (I'm assuming this is like the data you find on the 
"monitor" tab of cdmaworkshop)

Original comment by chromableedstudios on 2 Jul 2013 at 10:03

[GoogleCodeExporter]

Original comment by chromableedstudios on 2 Jul 2013 at 10:04

• Changed title: Request: DIAG_PILOT_SETS_F and DIAG_STATE_F
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

I did the test and I get the following result,

DIAG_STATE_F / new CRC1
TX:
3F 0C 39 7E

RX:
3F 8E 00 00 22 1E 7E

Now I want to know how I can decode this part, is there a manual for this.

Original comment by fap...@gmail.com on 2 Jul 2013 at 11:21

[GoogleCodeExporter]

generally speaking this part is the data "8E 00 00"

If you don't mind my asking what do you need the state information for? I don't 
really know what this is used for (I've never used it in cdma flashing/basic 
provisioning anyway).. I assume this info is like what they use when field 
testing a device?

manual? not sure... if you have qpst/qxdm theres a good chance something in 
there defines it, otherwise it would be necessary to find it in libqcdm or some 
qualcomm sources, or perhaps to simply reverse engineer it. 

Original comment by chromableedstudios on 2 Jul 2013 at 11:51