Deviating a JoySway
- mwm
- Topic Author
- Offline
Got nothing. One channel at 1 the entire time, the others all at 0.
However, it seemed to stop the capture early whenever it got a signal: either when I powered on, or when I turned on the Rx. Reliably. This makes me think that I've got a connection issue. Possibly what I have as "Ground" isn't? Or one of the two grounds isn't - I connected up both of the things I think are the proper corners.
If that seems likely, could you repost the diagram, with indications as to the board orientation? I.e. - assuming I'm looking at the side that's away from the main PCB, which column of pins is the one close to an edge?
Do not ask me questions via PM. Ask in the forums, where I'll answer if I can.
My remotely piloted vehicle ("drone") is a yacht.
Please Log in or Create an account to join the conversation.
- victzh
- Offline
- Posts: 1386
Please Log in or Create an account to join the conversation.
- Deal57
- Offline
- Posts: 857
Deviation Devo7e 3way switch mod, A7105, NRF24L01
Devo6s 2x2 switch mod, trim mod, haptic, multimodule, A7105, NRF24L01, CC2500
Devo12e 4-in-1 with voice mod -- it speaks!!
Please Log in or Create an account to join the conversation.
- mwm
- Topic Author
- Offline
16MHz capture. Probes 0-5 on the five inside pins, so that 1, 2 and 3 should be SDIO, SCK and SCS. Pins 0 & 4 don't seem to have a signal, except for going up on poweron, but I didn't do a full search. If you need a capture with more pins on it, let me know.
One odd thing: the Rx has a "bind" button. The Tx doesn't. Just hit bind on the Tx, the led flashes, and it reconnects.
Do not ask me questions via PM. Ask in the forums, where I'll answer if I can.
My remotely piloted vehicle ("drone") is a yacht.
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Offline
- Posts: 4402
Please Log in or Create an account to join the conversation.
- mwm
- Topic Author
- Offline
drive.google.com/open?id=0B72nhihrc01MUU...VtODM2U1E&authuser=0
Do not ask me questions via PM. Ask in the forums, where I'll answer if I can.
My remotely piloted vehicle ("drone") is a yacht.
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Offline
- Posts: 4402
Please Log in or Create an account to join the conversation.
- mwm
- Topic Author
- Offline
Just to check, CSN should be obvious in the power on capture, right? If not, then is there a single capture I can use?
I had probes on channels 0-4. My cursory indication of the data is that channels 0 & 4 had no useful data on them. Is this correct?
Thanks!
Do not ask me questions via PM. Ask in the forums, where I'll answer if I can.
My remotely piloted vehicle ("drone") is a yacht.
Please Log in or Create an account to join the conversation.
- victzh
- Offline
- Posts: 1386
How did you solve the connection without soldering problem?
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Offline
- Posts: 4402
Please Log in or Create an account to join the conversation.
- mwm
- Topic Author
- Offline
If you haven't checked it, the powerup csv file is probably the most reliable, as it was done first.
I unplugged the module, wire-wrapped all 8 pins, and then clipped onto those. I'm going to work on the idea the the clips may have had intermittent contact, and try a couple of workarounds for that. I'll also double-check that the wire wraps lines are on the pins I think they are on. I'll try some other pin hookups until I find the pattern that PB mentioned. I do have one question about that, though: is the "it" that goes high again after sck(?) toggles 8 times sck or csn?
Do not ask me questions via PM. Ask in the forums, where I'll answer if I can.
My remotely piloted vehicle ("drone") is a yacht.
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Offline
- Posts: 4402
MOSI will look somewhat random. If you are lucky it will only transition while CSN is low, but that depends on if the bus is shared. It should always transition while SCK is low though, and should only transition when SCK is also transitioning.
MISO will look similar to MOSI, but will change less frequenctly
SCK will be very regular. You will see it toggle in bursts of either 4, 8 or some multiple of 8 pulses at a time with long spans where it doesn't transition.
CSN will go low before SCK starts to transition and stay low through a set of SCK pulses and then CSN will go high again. If the SPI bus is shared, but may also see SCK toggle while CSN is high.
We specifically are only interested in reading the values of MOSI and MISO each time the SCK transitions while CSN is low. All other data will be ignored, as it isn't relevant to the trasnceiver.
Please Log in or Create an account to join the conversation.
- mwm
- Topic Author
- Offline
This is the Tx power on, and the second one is the Rx power on and connect. Let me know if these look right, and I'll get the other needful things.
Do not ask me questions via PM. Ask in the forums, where I'll answer if I can.
My remotely piloted vehicle ("drone") is a yacht.
Please Log in or Create an account to join the conversation.
- mwm
- Topic Author
- Offline
Do not ask me questions via PM. Ask in the forums, where I'll answer if I can.
My remotely piloted vehicle ("drone") is a yacht.
Please Log in or Create an account to join the conversation.
- victzh
- Offline
- Posts: 1386
Please Log in or Create an account to join the conversation.
- mwm
- Topic Author
- Offline
Note that BINDING IS INITIATED AT THE RX, not the TX.
On names: Joysway is a product line from the company Ripmax. The receivers and transmitters are shared across other lines. The protocol is FHSS. Yes, it's Futaba's FHSS, but it's from a third party, and binding has been reported as being hit or miss.
Do not ask me questions via PM. Ask in the forums, where I'll answer if I can.
My remotely piloted vehicle ("drone") is a yacht.
Please Log in or Create an account to join the conversation.
- victzh
- Offline
- Posts: 1386
Please Log in or Create an account to join the conversation.
- mwm
- Topic Author
- Offline
As for the chips, those are just tools for translating for digital signals to RF signals. Whether or not they can talk a given protocol will depend on the chip features. All the stuff I see here reverse engineers the digital signals, which means you have to have the same chip. Given the right equipment (which I don't have), I'm sure someone with the appropriate skills (again, which I don't have) could reverse engineer things at the RF level, and then tell you whether or not the A7105 could do what Futaba is making the CC2500 do.
Please don't let this sideline slow down the work on the protocol. I now have a couple of models I'd like to sail with this.
Do not ask me questions via PM. Ask in the forums, where I'll answer if I can.
My remotely piloted vehicle ("drone") is a yacht.
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Offline
- Posts: 4402
You can run:
utils/spi/rawcsv_to_spi.pl -mosi 2 -miso 2 -clk 3 -enable 4 -sample 0 tx-poweron.csv > tx-poweron.spi
utils/spi/format_spi.pl -tx a7105 bind.spi
You can easily see the initialization code in tx-poweron.csv using this
You can also see the channel pattern:
0.121050 = STROBE_STANDBY a0 => a0
0.121078 > PLL_I 0f 30 e0 => 30
0.126057 > FIFO_DATA 05 ff f8 2d ca a0 00 5b 86 64 64 c6 66 64 64 aa d5 d0 => ff
0.127101 = STROBE_STANDBY a0 => a0
0.127131 > PLL_I 0f 30 e0 => 30
0.132108 > FIFO_DATA 05 ff f8 2d ca a0 00 5b 86 64 64 c6 66 64 64 aa d5 d0 => ff
0.133153 = STROBE_STANDBY a0 => a0
0.133181 > PLL_I 0f 30 e0 => 30
0.138158 > FIFO_DATA 05 ff f8 2d ca a0 00 5b 86 64 64 c6 66 64 64 aa d5 d0 => ff
0.139203 = STROBE_STANDBY a0 => a0
0.139234 > PLL_I 0f 31 e0 => 31
0.144209 > FIFO_DATA 05 ff f8 2d ca a0 00 5b 86 64 64 c6 66 64 64 aa d5 d0 => ff
0.145253 = STROBE_STANDBY a0 => a0
0.145281 > PLL_I 0f 30 e0 => 30
0.150260 > FIFO_DATA 05 ff f8 2d ca a0 00 5b 86 64 64 c6 66 64 64 aa d5 d0 => ff
0.151305 = STROBE_STANDBY a0 => a0
0.151335 > PLL_I 0f 32 e0 => 32
0.156311 > FIFO_DATA 05 ff f8 2d ca a0 00 5b 86 64 64 c6 66 64 64 aa d5 d0 => ff
0.157356 = STROBE_STANDBY a0 => a0
Data packet size is 17bytes.
I looked at aileron.csv, and see that byte 7 is the aileron data with values from 1eh to aah (mid-point is 5bh). Byte 16 seems to be a checksum. Very occasionally, I see a 'ddh' in the 1st byte (otherwise it is 'ffh') I wonder if this is used by the Rx for binding.
That is all for now.
Please Log in or Create an account to join the conversation.
- mwm
- Topic Author
- Offline
Ripmax seems to be a lot like WLToys. Except they also sell some FTR aircraft under the Joysway label. These are what have "hit or miss" binding with Futaba Tx's. They also use component-based electronics, so you can get standalone Rx's as well as Tx's, at least for some of their craft. However, you are expected to either buy a Tx/Rx Pair, or a Tx designed for your craft. Beyond that, compatibility isn't guaranteed.
So victzh is right - this is just Frequency Hopping Spread Spectrum, and not Futaba's protocol.
I have verified that this Tx works with the Rx in their two smallest yachts, the Orion and the Caribbean. The Rx used in the Orion is also used in their most popular yacht, the Dragon Force, as well as the recent Explorer yacht and the Force 2 and Binary catamarans. It is not used in the older Focus, which is their largest yacht, and I don't believe they are compatible. However, the Focus appears to be out of production.
Do not ask me questions via PM. Ask in the forums, where I'll answer if I can.
My remotely piloted vehicle ("drone") is a yacht.
Please Log in or Create an account to join the conversation.
- Home
- Forum
- Development
- Protocol Development
- Deviating a JoySway