Yobo wireless Nunchuck, not responding

[SouthernAtHeart]

Hi, you said this worked for you with a Yobo wireless nunchuck, so I'm hoping to get it working. So far it's not communicating with the adapter. I'm using an UNO, as seen in the photo. I changed the line in the file ArduinoNunchuck.cpp to: //#define CPU_FREQ 8000000L

define CPU_FREQ 16000000L

The LEDS on the Yobo and the Yobo adapter blink like they're synced, but I get no output data. I'm using 4.7K pull-ups, (I tried it without pull-ups, too), and 3.3V from the UNO.

Any ideas?

[SouthernAtHeart]

[ca0abinary]

Are SDA and SCL on pins A4 and A5 for your board? In my sketch the default SDA / SCL are used instead of other analog pins like are used in some examples. Also, you may not need to use the pullup resistors on the uno. I hope you are successful! The Yobo adapter was a little tricky to get working consistently so you might need to play around with some of the timings.

[SouthernAtHeart]

Ok. It is working. But like you said it's a bit touchy on syncing. If it doesn't startup just right it won't ever sync. I'm working on making a replacement board to go in the Yobo that has an NRF24L01+ transceiver in it. Then it will easily talk to a remote arduino unit without connection/sync issues.

[RyshBot]

Hi, First thanks a lot for your code.

Im having the same trouble as Southern. I'm using the same hardward except for the adapter. I cut an extension wire and plug it directly to the uno. I'm sure I got the good identifacation on my wire. But on the serial monitor I got a bunch of 2 like this ..... init chuck...2222222222

Do you think you may help me ?

thx RB

[ca0abinary]

@RyshBot Are you using an Arduino at 16MHz or 8MHz? Here's a list of things I'd check (you may have already done this, it's just my personal list):

• Check clock speed, in the code from this repo it's set to 8MHz which is only standard for 3.3v arduinos
• Check your resistors (if you're using a 16MHz 5v part you likely don't need them)
• Reset a few times, this nunchuck is not standard and sometimes it doesn't work correctly. Wish I had some time to nail it down with an oscilloscope.

[RyshBot]

thx for the fast answer!! I'm using an uno R3 so I'm pretty sure the clock speed is 16MHz First, I have changed the line

define CPU_FREQ 8000000L to #define CPU_FREQ 16000000L

After, I tried with an without resistances nothing worked Then I tried to reset a few time.Maybe I did not tried enough time.

I will try to use the defaul SDA/SCL Also when you says "you might need to play around with some of the timings.". What did you mean? Can you explain? During week, I don't have time to work on the project so I will read your comment and try thing you may suggest on friday night

Thanks again I hope to make it work next weekend

[ca0abinary]

you might need to play around with some of the timings

That quote mainly refers to the CPU_FREQ and delay(500) lines of code.

Sorry to hear it's not working well for you, using the default SDA/SCL is likely the solution to your issue since the code isn't written to use software SPI because that never worked for me personally.

[RyshBot]

ok so once I connect to default SDA/SCL I should play around with delay(500) and CPU_FREQ. Which kind of value should I try ? Tell me if i'm wrong. delay(200) will try to initiate the chuck faster. Playing with CPU_FREQ will do something that I can't understand yet. Should I drop it ?

The value 2 means it didn't not sync what about value 4 ?

I'm sure of my wiring because wired chuck with any code found is working good. Using a bigger baudrate would change anything ?

This is reminding me that cheap things isn't alway worth but I will make it work