Working on blaster prop and my board just decided to start playing hum audibly at about about 71 minutes of being on.
00:32:48.228 -> Ignition.
...............
01:42:12.470 -> Playing testfont2a/hum01.wav
which sounds possibly related to:
I have my testfont running, and it was sitting on the bench when suddenly I got “hhhuuummmmmmmmm”
Serial monitor shows hum playing all along, as well as swingl and swingh…but they are not audible, even though they are present in the font folder (expected when blaster mode)
I do get preon.wav and out.wav at boot/preset change, but not smoothswings or hum…until this hum thing now.
The following updates/additions/fixes for my prop are currently on github if we can get them tested they’ll roll into v6.1:
Track Player
Fixed Loop playback for tracks, added fix for missing /tracks folder in /font or /common. If no tracks other than default is available Track Player will Loop the default track, no other playback options are available. If more than one track in font or common then Track Player will now start with first track found instead of default. This is to prevent repeat play during Rotate if default track was also first track.
Fix Scroll Preset Increment
Increment by 5 fixed for Scroll Preset menu
Added Swing Option Menu to Style Settings Submenu
SWING OPTION was missing from Style Settings menu in v6.0
Release Wav Player for non-Edit Mode menus
wav_player is now released after prompt for non-menu usage
Prevent Hold Button or Long Click Button in Color Editing or Blade Length Editing
Added prevention for a hold or long click when ShowColor style is active, refer to controls for each mode to ensure correct button use
Color Zoom for Color List
Color Zoom added to on-the-fly Color List controls for 1 button and 2 button, changed control for Color List to match ColorWheel Zoom
Button changes to allow for Choreography Mode addition to 1 button
Changed a few controls to enable Choreography Mode for 1 button, refer to top section of prop for updated controls
Add Drag for HOLD_BUTTON_LOCKUP
Added Drag for the Hold Button lockup define while saber is pointing down
Fixed FETT263_DUAL_MODE_SOUND selection for pstoff
pstoff sounds now selected up=odd, down=even (along with preon, out and in sounds)
Added on-the-fly Copy Preset
Added on-the-fly Copy Preset functionality to 1 button and 2 button controls (outside Edit Mode Menu) refer to controls at top of prop, will make a copy of current preset which you can then edit to add additional presets.
OS6 should work fine with TeensySabers, although you don’t get some of the features, like faster neopixels and faster motion readouts. Would be great to test it out and see if there are anything that doesn’t work as it should.
I have a TeensySaberV3 running OS6 with Fernando’s OS6 bladestyles and Edit Mode. Testing now, but all seems well initially!!! How cool is that? This saber is 4 years old, and is now more feature rich than new sabers!!!
PS, Fredrik: I have also tested these on Proffieboard 3.7 and 2.2:
FETT263_SWING_ON_PREON
FETT263_TWIST_ON_PREON
FETT263_STAB_ON
FETT263_STAB_ON_PREON
FETT263_THRUST_ON_PREON
All work to trigger preon audio and blade effects.
I haven’t tried to post an error message before, so I hope this works ok. Basically, with fett263’s newest update, I get an error unless I have FETT263_SAVE_CHOREOGRAPHY defined. I’m planning to use it anyway, just letting you know.
In file included from D:\Users\jdsea\Documents\Proffieboard\OS\6.0\ProffieOS\config\beta_test_config.h:136,
from D:\Users\jdsea\Documents\Proffieboard\OS\6.0\ProffieOS\ProffieOS.ino:558:
D:\Users\jdsea\Documents\Proffieboard\OS\6.0\ProffieOS\props\saber_fett263_buttons.h: In member function 'void SaberFett263Buttons::RestoreGestureState()':
D:\Users\jdsea\Documents\Proffieboard\OS\6.0\ProffieOS\props\saber_fett263_buttons.h:981:9: error: 'saved_choreography' was not declared in this scope
981 | if (saved_choreography.isIntialized()) memset(saved_choreography.clash_rec, 0, sizeof(saved_choreography.clash_rec));
| ^~~~~~~~~~~~~~~~~~
exit status 1
Error compiling for board Proffieboard V2.
This report would have more information with
"Show verbose output during compilation"
option enabled in File -> Preferences.
Thanks, I must have crossed up the functions when I was adding on github, that line belongs in RestoreChoreo() not RestoreGestureState(). I submitted the fix, it should be on github now.
Hey Tom, I have some answers for you.
Thrust has an intentional 2 second delay before another thrust will register.
For the voice prompts, Fredrik only recently updated the zip files for download. There were some fixes made (mbatt saying default being one of them).
So grab a fresh copy and you should be good to go.
I’m lost, there’s been too many hum issues.
Also, when you do commands from webusb, some of the output goes to webusb, so it’s really hard to see what you’re doing, and what the expected result might be. I think previously you added some comments to the serial monitor output? Or was that someone else?
I think we’re going to need to create new threads when we find problems in the beta. I’m finding it very difficult to keep track of multiple issues in the same thread.
