ProffieOS v6.3 BETA testing

Afrojedi · November 22, 2021, 9:31pm

Yep I sure do

MTMiller · November 22, 2021, 10:44pm

idle.pbm (50.0 KB)
or maybe
font.pbm (50.0 KB)

profezzorn · November 22, 2021, 10:45pm

What issue?
Is this the hum staying on?
Or the hum not starting?
Or something else that I’ve forgotten?

I don’t have either of these fonts, which makes it harder to reproduce the problem.
Does it matter which font you switch TO? Or just which font you switch FROM?
Can you reproduce it with the font you already sent? (Bal Venos)

Also, since you’re using WebUSB it’s hard to know when you did what. Combined with not knowing exactly what the problem is, it’s really difficult to know what to look for in the serial output.

profezzorn · November 22, 2021, 10:49pm

Can I also see your config file?

MTMiller · November 22, 2021, 10:55pm

when I use the config file from 5.9 in 6.0, the compile give me an error with the…

#ifdef CONFIG_BOTTOM
SSD1306Template<64, uint32_t> display;
#endif

…section you had me insert into my config file a hundred years ago (it seems). Deleting this portion of the config file results in a successful compile, but corruption of the OLED graphics.

The reversal of the trigger and mode buttons is on me. I forgot that I had accidentally wired those buttons in reverse, easily remedied within the config.

MTMiller · November 22, 2021, 10:56pm

blaster_v3-3_config.h (2.2 KB)

NoSloppy · November 22, 2021, 11:00pm

This can happen (if everything else seems to be correct) if the image is not 1bit-per-pixel, monochrome, black and white only image.
Try these known-good files to test:
https://www.dropbox.com/s/q7avh3a38otgqqo/OLEDTest.zip?dl=1

profezzorn · November 22, 2021, 11:03pm

When you go with a standard display setup, images which are 64 pixels wide won’t work.
Also, the configuration in CONFIG_BOTTOM has changed a bit since last time.
You need a display controller now. At minimum, it should look like this:

#ifdef CONFIG_BOTTOM
StandardDisplayController<64, uint32_t> display_controller;
SSD1306Template<64, uint32_t> display(&display_controller);
#endif

For bullet counts, you’ll want something like:

#ifdef CONFIG_BOTTOM
DisplayHelper<64, uint32_t,
  BaseLayerOp<StandardDisplayController>,
  ClearRectangleOp<10, 80, 8, 24>,
  WriteBulletCountOp<10, 20, 5>
> display_controller;
SSD1306Template<64, uint32_t> display(&display_controller);
#endif

MTMiller · November 22, 2021, 11:10pm

They had been working fine under 5.9. I had figured out all that 1 bit, black and white stuff and had been making my own animations. Was unaware of the controller stuff that had been added, so l’ll try that next and report back.

NoSloppy · November 22, 2021, 11:25pm

so this superceeds previous version then? which I have as:

//Support for 128x64 OLED
#ifdef CONFIG_BOTTOM
SSD1306Template<128, uint64_t> display(0x3C);
#endif

or is the latter all that’s needed for standard 128x32 screens?

MTMiller · November 23, 2021, 12:04am

Inserted the bullet count lines into the config, compiled and uploaded to the board successfully, and then it turned the blaster on automatically (as it does) but it only got a half second or so into the boot sound when it abruptly stopped. OLED remains corrupted and a random barrel light turns on. No function from either the trigger or the mode buttons.
Also, the computer now thinks that the USB device is unrecognizable, so I can’t do a serial monitor to see what’s happening. “The last USB device malfunctioned and windows does not recognize it”

Afrojedi · November 23, 2021, 12:21am

The issue that the hum is staying on. As seen in the read out the pstoff is above the hum sound.

profezzorn · November 23, 2021, 1:10am

Are you talking about what’s happening at 20:48:46.007?
Because it looks like there is a stab ignition happening there.
Is that the problem?

profezzorn · November 23, 2021, 1:12am

Could be that the rectangle clear is too big. Try this:

#ifdef CONFIG_BOTTOM
DisplayHelper<64, uint32_t,
  BaseLayerOp<StandardDisplayController>,
  ClearRectangleOp<10, 50, 8, 24>,
  WriteBulletCountOp<10, 20, 5>
> display_controller;
SSD1306Template<64, uint32_t> display(&display_controller);
#endif

MTMiller · November 23, 2021, 1:35am

How do I fix the USB device malfunction problem? Is this a “push the two buttons” situation?

profezzorn · November 23, 2021, 1:45am

Most likely, yes.

Afrojedi · November 23, 2021, 6:05am

I can’t test any more as my usb connector broke. Thanks for your efforts thus far.

MegtoothSith · November 23, 2021, 1:54pm

Fett263:

@MegtoothSith @astromech or others.

I have put together a test version with the Gesture “Spamming” delays removed but we’ll need it beat up pretty good before considering. This removes the 2 second delay on gesture events that were there to prevent users from “spamming” gestures or from doing the movement accidentally in quick succession (particularly twists).
Unfortunately, with the holiday this week my time and access to my saber and computer for testing is going to be very limited so I’d like to get several testers to beat it up. This is applicable to the following, so we need to make sure that if you “spam” these events we don’t get issues or odd behavior, like the saber not turning off or sounds getting stuck or preon/ignition/retraction not working as expected:

Twist On / Off

Thrust On

Stab On

Multi-Phase (needs define enabled)

Gesture Sleep

This is only a test version so you’ll have to pull from my fork, I don’t want to submit to main until it’s thoroughly proven out.

https://github.com/fdarosa2663/ProffieOS/tree/test

I have been gesture spamming with proffieboard 1.5 and 3.7. No issues so far. Tip drag works with aux hold pointing down. Ill try color zoom today.

Fett263 · November 23, 2021, 2:02pm

Thanks, the gesture “spam” delays have been removed on the github version.
There is an issue with ColorZoom in Edit Mode for 1 button, it won’t allow you to revert with a long press currently so I’ll need to fix but it won’t be until next week due to the holiday.

MegtoothSith · November 23, 2021, 2:36pm

yeah Im running your fork.