PB V3.7 beta test thread

The board went in tonight.

5 Likes

Ooooh that’s sweet.

Well, running on bench untouched, I just had a couple of force ghost events. More OS based I think than board, but reporting nonetheless.


16:11:17.253 -> Playing testfont2/swingl01.wav
16:11:17.253 -> channels: 1 rate: 44100 bits: 16
16:11:17.857 -> Playing testfont2/swingh01.wav
16:11:17.857 -> channels: 1 rate: 44100 bits: 16
16:11:18.208 -> EVENT: Push ON millis=1666007
16:11:18.208 -> unit = 1 vol = 0.50, Playing testfont2/force01.wav
16:11:18.242 -> channels: 1 rate: 44100 bits: 16
16:11:18.242 -> EVENT: Push ON millis=1666019
16:11:18.242 -> EVENT: Push ON millis=1666028
16:11:18.277 -> EVENT: Push ON millis=1666044
16:11:18.413 -> EVENT: Push ON millis=1666184
16:11:18.413 -> EVENT: Push ON millis=1666191
16:11:18.413 -> EVENT: Push ON millis=1666199
16:11:18.446 -> EVENT: Push ON millis=1666209
16:11:18.479 -> EVENT: Push ON millis=1666242
16:11:18.479 -> EVENT: Push ON millis=1666251
16:11:18.479 -> EVENT: Push ON millis=1666256
16:11:19.007 -> Playing testfont2/swingl01.wav
16:11:19.007 -> channels: 1 rate: 44100 bits: 16
16:11:19.805 -> Playing testfont2/swingh01.wav
16:11:19.805 -> channels: 1 rate: 44100 bits: 16

1 Like

But the push detection code is in your prop file, isn’t it?

Indeed. I’m just saying the saber is sitting idle humming and I didn’t touch it. Seemed similar to the random motion events when SWING_ON was occuring.

I think swing on is less of an issue in V6 because we have more smoothing inside the swing_speed function.

For push detection, I would have to read how that works to figure out what the solution is.

No Sloppy now has company!!!

4 Likes

Anyone else finding battery level inaccurate? I have a fully charged 4.1v battery in, reports as 4.0 volts on Proffieboard v1.5.
V3 board reports 3.26v

With USB connected or without USB connected?
While on or while off?

USB connected blade off 3.25v
USB connected blade on 3.25v
USB disconnected blade off 3.25v
USB disconnected blade on - unknown (spoken only in off state)

Green light shows Saw pattern while USB connected and 2 second bright blink also indicating charging

That is weird, it’s basically saying the same thing no matter what.

Serial monitor reports same value as spoken (expected)

Just flashed identical compile to v1.5 board and 4.09v reported.

I found a potential problem here:

Does it work better if you change that line to:

#if VERSION_MAJOR == 5 || VERSION_MAJOR == 6

?

Unfortunately no, and to add to this, It still reports 3.25 volts with the battery removed.

oh wait hold on. premature post

Ok now it’s saying ~4.16 volts…with or without the battery while USB connected…

Might be better, assuming it’s charging.

Copy that. So it’s reading the USB voltage as incoming battery. That makes sense. Ok cool, thanks!
Maybe I should unwire this non-working Bluetooth and hook up the TTL-> USB instead.