Protocol Stacks

FDR wrote: I have a CB100, which is 2401 compatible, so I can test it too.
But I have to figure out how to compile for the tx and make a dfu from that...
I hasn't implemented the encoding in my dfu tool yet.

The encoding is part of utils/dfu.py. Even without knowing much python, it should not be too hard to figure out. Or you could just install python in mingw, then you could build there. I would not recommend trying to fly the firmware yet though. The todo list is still quite long.

wuselfuzz wrote: First tests:

- Binding to an rx2801 worked, but an attached servo jittered like hell.
- Binding to an rx2435 (rx2401 series) didn't work.

Can't find the free DSM2 receiver and currently can't test with a 2601 series receiver, that one is still in my 4G6.

Yeah, I plugged my rx2801 in today and saw the same thing. build_data_pkt2801() is really messed up. I don't know what I was thinking, but I got the 2MSBs compeletely wrong. I'll be working on it tonight.

Not surprising since I've never tested it before. The devo stuff still works fine though.

wuselfuzz wrote: Hehe, my only devo receiver is the one in the V100D08, I don't feel like breaking a brand new heli yet.

Found the DSM2 in my MiniMag, but I have to go to bed soon and visit my parents tomorrow.

I got the Rx-2801 working now
Unfortunately, I realized I don't have any connectors small enough to power my Rx2609. I need to get some regular-to-mini plug adapters so I can use my servos and battery with my 2609.

My RX2609 s working now too (in both WK2601 and WK2801 mode)

I soldered some leads onto the board, so I could power it and it worked right away.
I found out that Walkera hooked up the micro-jst servo connectors backwards to how Hobby King sells them, so I also needed to reverse those.

I don't have anything that speaks the WK2401 protocol, so I can't test that one, but I'm encouraged that the WK2801 and 2601 protocols are working

Congrats!
I see you two are working hard!
What can I help? I have a 4ch CB100 to try the WK-2401 protocol...

FDR wrote: Congrats!
I see you two are working hard!
What can I help? I have a 4ch CB100 to try the WK-2401 protocol...

Well, you can try loading the firmware onto your tx and see if it'll bind with your cb100. I would take the blades off 1st in case it actually works and ends up starting at full throttle.

I have no idea how to build the firmware on Windows, but here is the latest copy:


To use:
install it with the Walkera DfuSe tool.

power down and power up holding the 'Ent' key
your PC should detect it as an unformatted drive.
format the drive with default settings
copy the contents of the 'filesystem' folder to the new drive (not the folder itself though. you want tx.ini, models, media, etc in the root of the Tx drive)
power down and power the Tx back up. it should now work just like the emulator. Select WK2401 as the protocol, power off again, plug in your CB100 and power back on the Tx.

I thin wuselfuzz also has some WK2401 gear, so you could possibly wait for him too.

Deviation will not overwrite your models (if everything is working properly..I'd probably run the backup just in case) so you can go back to the Devo firmware by reflashing the firmware and library.

PhracturedBlue wrote: I have no idea how to build the firmware on Windows, but here is the latest copy:

Where here?
Is that supposed to be an attachment? It won't allow .dfu file nor larger than 1MB, so please zip it...

FDR wrote:

PhracturedBlue wrote: I have no idea how to build the firmware on Windows, but here is the latest copy:

Where here?
Is that supposed to be an attachment? It won't allow .dfu file nor larger than 1MB, so please zip it...

I did zip it. This forum is very annoying about not telling you when it doesn't accept an attachment.

Try it again.

I confirm that: it doesn't bind.

I should give more detail:

I think it binded once, but I'm not certain, because I forgot, that I left my WK2402 turned on... (However it shouldn't bind after the first 10 seconds...)
The thing is: it was unreliable. For example once I set up the model data, but on the next turning on for binding, it was not correct (the mixers were resetted to none state).

It seems, that my sticks are quite off: they would need calibration. The receiver might not bind if throttle is not zero (or -100% in this case).

There were other minor issues too: it didn't turn off, when I was not on the main screen.
The trim page's trim step values were hard to change: single clicks were unreliable...

It is bedtime now, but tomorrow I will try to play with it a little longer...

I made some changes that may help with the WK2401. The state of the sticks will not affect binding, so the fact that calibration is off won't matter at all.

Were you using a stylus tp play with the spinbox? I cannot reliably change spinboxes without one. It is likely you'll need to calibrate your screen as well as your sticks. I'll add a page for that.

Here's a new build. It may fix the wk2401. If it still doesn't bind, I'll provide a 'replay' build which just plays back some logs I have to see if that works.

The new build also has a (crude) calibration screen for touch and stick.

It didn't help, it still doesn't bind...

Try this one.
Also, in model1.ini add this in the radio section:
fixed_id=487193

(also try both WK2401 and WK2601 modes)

This is exactly the binding code that I see in the logs I got. If this doesn't bind it implies the initialization or timing is wrong.

Bed time here....I'll take it up in the morning

wuselfuzz wrote: I just ordered a logic analyzer. \o/

dangerousprototypes.com/open-logic-sniffer/

That looks like a nice bit of kit. I'll be interested in how far 16kB goes as far as number of samples (you need to sample the SPI bus at 8MHZ to get reliable data). I generally like to look at logs that are 10-30 seconds long, and I doubt you'll be able to use such long logs with that. It shouldn't matter too much though, it just means you can't look at the whole log in one shot.

I spent some time double checking my code against the sample logs I got from renatopub. I don't see anything else wrong, so if it still doesn't work with the last build and fixed-id, I'm stumped. In that case, I guess I'll dump my logs and make sure what I see on the emulator is what I see from the Tx.