New Wiiceiver code!! testers wanted

ecycler said:

Yes, thank you, Dexter. You are definitely the eboard virtual god of sorts. I will give it a go and look forward to swapping the C and Z button functionality. For some reason I have a similar issue to whitepony where it is just really hard for me to control the joystick and hold the c button simultaneously, but the z is no problem. I will flash the newest updates from github after swapping those buttons in the code when I get back home in a few weeks.

Click to expand...

wldmki said:

I’ve just downloaded the zip from github, failed compilation for the Wiiceiver_2_0

Click to expand...

Mevel said:

Added some Lines in your Code. In particular the UI Setup. Nothing fancy!

The Acc. values are now printed to the Terminal too, like the values for Throttle and Brake.

Click to expand...

// NOTE: the value # flashed is +1, can't flash "0" times :/
int ui_getValue(byte blinks, byte valueAddy, byte defaultValue, byte maxValue) {
  int newValue = readSetting(valueAddy, defaultValue);
  Serial.print(F("getting value #"));
  Serial.print(blinks);
  Serial.println("; use stick up/down to change, C to save");
  flash(green, blinks);
  delay(1000);
  flash(green, newValue+1);
  Serial.print("Value: ");
  Serial.println(newValue+1);
  do {
    chuck.update();
    if (chuck.Y > 0.5) {
      newValue ++;   
      if (newValue > maxValue) {
        newValue = 0;
      }
      Serial.print("Value: "); 
      Serial.println(newValue+1);
      flash(green, newValue+1);
      delay(20);
      chuck.update();
    } else if (chuck.Y < -0.5) {
      newValue --;
      if (newValue < 0) {
        newValue = maxValue;
      }
      Serial.print("Value: "); 
      Serial.println(newValue+1);
      flash(green, newValue+1);
      delay(20);
      chuck.update();
    }
    delay(20);
  } while (!chuck.C);
  Serial.print(F("Saving value #"));
  Serial.print(blinks);
  Serial.print(F(" as "));
  Serial.println(newValue+1);
  EEPROM.update(valueAddy, newValue);
  green.high();
  flash(red, blinks);
  red.high();
  delay(1000);
  return newValue;
} // int ui_getValue(byte blinks, byte defaultValue)

razad7@gmail.com said:

Hey,
I've been using the new code with my Arduino Nano and Nyko Kama.
I've been loving the code but i have a few question, or comments?
1. Sometimes when i use C+Z i.e raw mode, and I'm at a stop light or something i accidentally get into calibration mode and recalibrate the acceleration, which is less to my liking. I though about maybe if you made the entrance into calibration mode with C+Z + full left (or right) on the stick would maybe solve this problem (since nobody uses left to right that i know of).
2. Calibrating with Arduino, I think maybe because the lights on the arduino are different then the WiiCiever I am having a difficult calibrating some of the features on the remote.. like drag brake and minimum speed forward. - Is there anyone who has calibrated with arduino and knows how to do this correctly?
3. Are you using the sensors inside the nunchuck? maybe could be used for acceleration/brake sensitivity (helping people not getting thrown off the board and stuff)
Thanks for the hard work, it's awesome!
Z

Click to expand...

austindavid said:

The acceleration profile would not change the calibration point; it only changes the rate of change for acceleration or braking. I'll review the code later this weekend to double-check, but the calibration should be clean. Once you set a value for the drag brake, that's what your ESC will get when you press/hold Z.

It can be tricky to choose that value though, and the braking might feel stronger at higher RPM. Try going into the setup again and bringing that value down a little (use C to scroll through the setup options, then bump the stick up a few times to reduce that level) and see if it's better for you. On my boards I can actually hear the sound difference in the motor for when the brakes start. I generally can't actually feel the resistance, but the motor sounds different enough that I can find exactly the point where the brakes kick in. Set at that level, holding Z applies just a tiny bit of braking pressure, and I can use the stick to increase it. Or just use the stick for brakes, whichever.

Now the other thing: that's crazy. I assume you're on the most recent code 2.0 beta3, which was updated about 6 weeks ago?

In the code there's only one way to get the ESC up to full throttle instantly -- C+Z at the same time. When I'm testing I look at that transition brakes -> throttle, or throttle->brakes, very closely. It's a sensitive time for the rider sa your acceleration totally changes, and that's when you've got the hardest time balancing. I also test that standing on the board, for the same reasons. I've never seen the issue you describe.

The ESC could get confused about your calibration level, and if thatt happens ... all bets are off. I don't have one of those 12S ESCs handy so I can't really speak to the performance, but I haven't heard anything bad about it. I should be receiving one soon though.

In the meantime, could you flip your board over, keep the wiiceiver + LEDs where you can see it, and try to reproduce the problem? I'd love to know what the wiiceiver thinks is happening when the ESC goes bananas. I've seen this on specific ESCs, particularly after using brakes for a while. Going from brakes -> neutral, the ESC decides "braking is the new neutral", and when the stick goes up (to neutral) the ESC decides to accelerate. It's terrible, but also hard to reproduce. The Flier ESCs have a setting about auto-calibrating neutral, you generally want that OFF, wiiceiver handles that for you.

I will also ping torqueboards offline and see if I can find a way to sync the throttle range on the ESC (which is independent of wiiceiver setup), that might smooth things out a bunch, and keep it from getting confused.

Click to expand...