DSM2 Reports

Description in an earlier link of vlad_vy


00184 * Three values for the transmitter information byte have been seen thus far
00185 *
00186 * 0x01 From a Spektrum DX7eu which transmits a single frame containing all
00187 * channel data every 22ms with 10bit resolution.
00188 *
00189 * 0x02 From a Spektrum DM9 module which transmits two frames to carry the
00190 * data for all channels 11ms apart with 10bit resolution.
00191 *
00192 * 0x12 From a Spektrum DX7se which transmits two frames to carry the
00193 * data for all channels 11ms apart with 11bit resolution.
00194 *
00195 * 0x12 From a JR X9503 which transmits two frames to carry the
00196 * data for all channels 11ms apart with 11bit resolution.
00197 *
00198 * 0x01 From a Spektrum DX7 which transmits a single frame containing all
00199 * channel data every 22ms with 10bit resolution.
00200 *
00201 * 0x12 From a JR DSX12 which transmits two frames to carry the
00202 * data for all channels 11ms apart with 11bit resolution.
00203 *
00204 * 0x1 From a Spektru DX5e which transmits a single frame containing all
00205 * channel data every 22ms with 10bit resolution.
00206 *
00207 * 0x01 From a Spektrum DX6i which transmits a single frame containing all
00208 * channel data every 22ms with 10bit resolution.
00209 *
00210 * Currently the assumption is that the data has the form :
00211 *
00212 * [0 0 0 R 0 0 N1 N0]
00213 *
00214 * where :
00215 *
00216 * 0 means a '0' bit
00217 * R: 0 for 10 bit resolution 1 for 11 bit resolution channel data
00218 * N1 to N0 is the number of frames required to receive all channel
00219 * data.
00220 *
00221 * Channels can have either 10bit or 11bit resolution. Data from a tranmitter
00222 * with 10 bit resolution has the form:
00223 *
00224 * [F 0 C3 C2 C1 C0 D9 D8 D7 D6 D5 D4 D3 D2 D1 D0]
00225 *
00226 * Data from a tranmitter with 11 bit resolution has the form
00227 *
00228 * [F C3 C2 C1 C0 D10 D9 D8 D7 D6 D5 D4 D3 D2 D1 D0]
00229 *
00230 * where :
00231 *
00232 * 0 means a '0' bit
00233 * F: Normally 0 but set to 1 for the first channel of the 2nd frame if a
00234 * second frame is transmitted.
00235 *
00236 * C3 to C0 is the channel number, 4 bit, matching the numbers allocated in
00237 * the transmitter.
00238 *
00239 * D9 to D0 is the channel data (10 bit) 0xaa..0x200..0x356 for
00240 * 100% transmitter-travel
00241 *
00242 *
00243 * D10 to D0 is the channel data (11 bit) 0x154..0x400..0x6AC for
00244 * 100% transmitter-travel

Well, I just bound my ar7200bx and sitting on the desk I didn't see anything jittery etc. But of course, it's an FBL unit sitting on a table so it's not going to show you if a channel is a little jittery.

I had the TX in 6 channel mode. I didn't want to try anything higher at first.
My setup was really basic. All simple mixes with lowered scale (low rates) and of course throttle hold.

It would spool up ok, and hover very stable for a minute or so, then it would roll or pitch on its own... throttle hold works!

It's almost as if it was "stuck" for a moment but I didn't give it a chance see if it would "unstick" on it's own. I just dropped it down as soon as it started doing it.

Another weird thing, once when it did it's little glitch, the throttle stick was at about 40% but the motor shut down. As soon as I moved the stick down the motor started back up, again as if the throttle was stuck.

Again, that was with the TX set to 6 channel mode and the ar7200bx bound with a fixed ID.

I wish I could give you better info, like a log or something, but I don't have any analyzers or the know how to use them for that matter...

Oh well... back to the mcpx and nano, which were flying perfectly the other day. I'll try them again tonight and see if anything changed. I DID upgrade to the latest experimental firmware today. (Yesterday I was on fc31fd71caa8 and installed 87729ce290cb this afternoon).

Might be my imagination, but it seemed the nano had a small glitch as well. Throttle dropped of for a fraction of a second. But other than that it was pretty good. Sorry, I know my report is not very scientific.

just want to ask this to be safe...is it ok to fly with the dsm protocal? i didn't update to the experimental release i am still running the 1.1.2 ...i built my tri-copter last week and did a short maiden flight but didn't go to far with it..it has the 6ch orange dsm rx with the sat port on it...i just want to make sure its safe to fly with it and not be nervous about it loosing control and flying off or hitting something...it seems rock solid with no glitches or brownouts as long as i turn on the rx first..i did check what would happen if it looses signal by holding the tri and powering it up and turning off my tx and all it does it cut the throttle to zero...so if it happens to loose signal it shouldn't fly off into the clouds...lol

I flew another pack through the nano and it seemed fine. If you feel that your quad isn't going to hurt anyone then go for it. This hobby is all about risk management.

I'm willing to risk my nano crashing but not my 300x. But i could crash my 300x with any tx for any number of reasons. personally the biggest I'll go for now is my 250. I'm going to try it with an orange and a spectrum. Just not the beaxstx.

with 1.1.2 and DEVO8S i had no problems (in a range of 300 Meters)

Tested with Protocol DSM2:
T-Rex 250/3GX FBL, T-Rex 450/Microbeast FBL, Blade 130x/FBL,
Blade McpX/FBL

Tested with Protocol DEVO:
Walkera Master CP.

cheers
Graziano

Yeah, I was doing some reading and my 300x issues may have been vibration related. I'll switch out the TX tonight and test...

Got that weird effect again tonight on my mcpx this time. I flew 3 packs through my V120, devo protocol, no problems at all. Felt very responsive to the sticks with no delay feeling at all.

Flew the mcpx and it felt like every now and then there was a delayed input. Seemed to happen on ELEV. I bound it to my er9x radio and didn't seem to have the issue. The two don't have exactly the same settings for D/R but pretty close and I always use very little expo if any.

Again, I wish I could offer more a technical explanation, but that's just how it felt.

To end on a plus, the V120D02v2 is an awesome little heli! And I had no issues with deviation at all. (momentarily the v2 voltage showed 8.1v... but other than that, control is fine)

Cheers!