DM002 protocol (contains captures)

lani wrote: * Rate modes LOW (default) and HIGH (ch11) are enough, with the plastic controller HIGH was too wild but with Taranis it is just great

Default should be High, at least that's how I've coded it based on your table...

lani wrote: * Difficult to achieve perfect trim with the control ranges at least in the HIGH rate (one click left causes left drift, one click back creates right drift). This might be just a feature of the quad but the analogue knobs in the TX could perhaps be mapped to the trims to achieve best effort. I sort of believe the trim steps have a lot smaller effect to the control than actual control steps.

These small quads always have drift anyway and even depend on the battery voltage so I don't think there is big value...

lani wrote: * Bind on powerup seems not to work when selected from OpenTX. Would there be something i need to tweak in the protocol file or multiprotocol config?

Not sure how you've configured the module... By default the _config.h file comes with bind on channel 16 and waits for a bind before starting the protocol. It's a safety feature to not bind everything around you at the radio powerup or model selection. You can disable this behavior if you want. It's all explained in the _config.h file...

lani wrote: * How does the protocol enumeration get updated to the OpenTX software, do they include directly something from the multiprotocol repo?

For ersky9x it's a file on the SD card. For OpenTX, you have to wait for plaisthos to add it in the code and do a release (that's why you have access to custom while he is doing it). Ask for it on rcgroups: www.rcgroups.com/forums/showthread.php?2...ol-TX-Module/page573

lani wrote: * In the SPI captures, why was there data on the line at moments when the clock pulse was not active?

SPI lines might be used for something else when not talking to the XN297L, like used to get data from the acc/gyro.

Pascal

planger wrote: Default should be High, at least that's how I've coded it based on your table...

Sorry, i just wrote it upside down. You are correct, default is HIGH.

planger wrote: These small quads always have drift anyway and even depend on the battery voltage so I don't think there is big value...

OK, let's not waste time on that then.

planger wrote: Not sure how you've configured the module... By default the _config.h file comes with bind on channel 16 and waits for a bind before starting the protocol. It's a safety feature to not bind everything around you at the radio powerup or model selection. You can disable this behavior if you want. It's all explained in the _config.h file...

User error, yes it binds on CH16. The _config was TLDR

planger wrote: SPI lines might be used for something else when not talking to the XN297L, like used to get data from the acc/gyro.

Acc/gyro on the TX side? Anyway I understand that the data line is used to something else too but that "else" is then not SPI as the clock signal is silent. Wouldn't expect the data line to be shared but the clock line separate?

lani wrote: Acc/gyro on the TX side? Anyway I understand that the data line is used to something else too but that "else" is then not SPI as the clock signal is silent. Wouldn't expect the data line to be shared but the clock line separate?

You are right stupid comment... some controllers avec SPI and I2C sharing some pins but not with the same function... Anyway we don't care.

What we need now is more dumps to figure out TX IDs/RF channels.

Pascal

Installed latest Nightly (2017-03-26). I have a Devo 7e. Testing DM002. Works well but Ail need to be trimmed. When I take-off the quad goes to the right. Performed a stick cal. but no effect. With stock controller I can perform better hovering. I have to find better trimming. Sorry for my English.

Setup search for Devo 7E

Dieter

When I bind this quad with my devo every move of the stick induces annoying pulses in the motors that make it fly very jittery it really makes a weird sound and even had it suddenly oscillate and fall out of the sky! well its fairly controlable with the stock tx and being able to turn off lights is cool!

Well guys (especially goebish !) thank you very much for adding the DM002 protocol !
I've flashed my Devo10 with the last nightly, and just tried it with my fresh arrived DM002, and it works just fine !
I had to add some Expo to throttle (I was oscillating on the Up axis at the beginning , but with expo my medium command was much more adapted to the hovering command and it was easier to get stabilized) and Rudder (to get out of the dead zone of this little quad), I'm able to get very nice sessions with it !
So thanks again , it's still a pleasure to add nice little new birds to my Devo !!!

I like AIO with CF antenna, I placed an order on the DM002 FPV RTF today.

I guess the development of the protocol is complete. If we need anything like more TXIDs, please let me know, I can capture.

Thanks.

I'll do some capture when it arrives. Just shipped out on epacket.

Just received my DM002. The yaw deadband is annoying. I spent some time to configure a complex mixer using minMax, 1-1 and deadband to counter it.

What kind of capture would we need for more ID? Is it just power up? Anything else?

Regards.

Would you have pin out for where to tap for the DM002 stock TX?

The MCU isn't marked. The other chip is a 297. There is one pad marked Data far away from those 2 chips.

OK found it on the web. It's a single pin for data.

Capture is posted on rcgroups:

www.rcgroups.com/forums/showpost.php?p=37997608&postcount=4

It is actually a tar.gz.

I assume the capture is OK. If not, please let me know.

I have flashed your 24721ef onto my devo10. This is the first time via upload jar without switching into windows. Great.

I can bind with and without fixed ID of 2 or something else. I am not sure what to do to test ID though.

Thanks.