No sound/stuck on single colour SOLVED

Hi guys,

I recently received a Pach Store saber and I am unable to get ProffieOS working.

I first installed proffieOS as normal and it all worked as intended. I then tried installing a new sound font which did not work so I tried to go back to normal settings. But now when i turn on the saber, it only has one colour and no sound. I am unable to cycle through the various fonts.

I have tried the boot and reset buttons and reinstalled the driver to no avail.

The SD card works fine as i moved it to an identical saber which works as intended.

When i try to reupload Proffie OS i get this;

` c:/users/thomas reed/appdata/local/arduino15/packages/arduino/tools/arm-none-eabi-gcc/4.8.3-2014q1/bin/…/lib/gcc/arm-none-eabi/4.8.3/…/…/…/…/arm-none-eabi/bin/ld.exe: warning: changing start of section .bss by 24 bytes
c:/users/thomas reed/appdata/local/arduino15/packages/arduino/tools/arm-none-eabi-gcc/4.8.3-2014q1/bin/…/lib/gcc/arm-none-eabi/4.8.3/…/…/…/…/arm-none-eabi/bin/ld.exe: warning: changing start of section .bss by 24 bytes
c:/users/thomas reed/appdata/local/arduino15/packages/arduino/tools/arm-none-eabi-gcc/4.8.3-2014q1/bin/…/lib/gcc/arm-none-eabi/4.8.3/…/…/…/…/arm-none-eabi/bin/ld.exe: warning: changing start of section .bss by 24 bytes
Sketch uses 217544 bytes (88%) of program storage space. Maximum is 245760 bytes.
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

Opening DFU capable USB device…
ID 0483:df11
Run-time device DFU version 011a
Claiming USB DFU Interface…
Setting Alternate Setting #0
Determining device status: state = dfuERROR, status = 10
dfuERROR, clearing status
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 2048
DfuSe interface name: "Internal Flash "
Downloading to address = 0x08000000, size = 217552
Download [=========================] 100% 217552 bytes
Download done.
File downloaded successfully
Transitioning to dfuMANIFEST state `

Any help you can offer would be much appreciated :+1:

Also this is what the serial monitor says;

09:54:42.295 → swingseWelcome to ProffieOS, type ‘help’ for more info.
09:54:54.485 → Battery voltage: 0.09
09:55:14.501 → Battery voltage: 0.09
09:55:34.469 → Battery voltage: 0.09
09:55:54.485 → Battery voltage: 0.09
09:59:22.702 → Sdcard found…
09:59:22.702 → blade= 0
09:59:22.702 → WS2811 Blade with 130 leds.
09:59:22.702 → WS2811 Blade with 8 leds.
09:59:22.702 → Simple Blade
09:59:22.702 → Failed to open: presets.ini
09:59:22.702 → Failed to open: presets.tmp
09:59:22.702 → Scanning sound font: TeensySF done
09:59:22.702 → humstart=1890.00
09:59:22.702 → Activating polyphonic font.
09:59:22.702 → version=2.00
09:59:22.702 → swingsensitivity=450.00
09:59:22.702 → maximumhumducking=75.00
09:59:22.749 → swingsharpness=1.50
09:59:22.749 → swingstrengththreshold=20.00
09:59:22.749 → transition1degrees=45.00
09:59:22.749 → transition2degrees=160.00
09:59:22.749 → maxswingvolume=3.00
09:59:22.749 → Activating SmoothSwing V2
09:59:22.749 → Accent Swings NOT Detected:
09:59:22.749 → unit = 0 vol = 0.50, Playing TeensySF/boot.wav
09:59:22.749 → channels: 1 rate: 44100 bits: 16
09:59:22.749 → Welcome to ProffieOS, type ‘help’ for more info.
09:59:23.453 → Amplifier off.
09:59:23.781 → I2C init…
09:59:23.781 → Motion setup … done.
09:59:24.437 → Unmounting SD Card.
09:59:33.761 → Booster off.
09:59:42.435 → Motion disable.
09:59:42.435 → Battery voltage: 0.20
strong text

Everything there that you posted indicates normal, successful upload, so something about how your config is written might be giving you different results than what you expect.

Didn’t the saber come already installed? Can you clarify what you mean by “first installed” and then what you did to add a font, and what is going " back to normal settings"?
When you went to add a font, were you editing a local copy of the config that they sent on the SD card? And then was your return to normal meaning you tried to upload an original, unedited version of that config?

You should paste your edited config here.
Use 3 backticks before and after the paste to format it nicely for reading here in the page.( The backtick/tilde key is to the left of the 1 key)

Thanks for your input Sloppy.

The saber does come installed with a config but only the base LEDs are active. You need to upload a new config that activates the Neo-Pixel functionality and allows that to work correctly. This new config comes on a piece of paper with the blade. When i did this it worked fine initially. But when i copied a new sound font to SD card that’s when the issues started.

And by " back to normal" settings, I deleted the current config and added a config from my other identical saber.

Below is the config im using;

#ifdef CONFIG_TOP
#include "proffieboard_v2_config.h"
#define NUM_BLADES 3
#define NUM_BUTTONS 2
#define VOLUME 1000
const unsigned int maxLedsPerStrip = 144;
#define CLASH_THRESHOLD_G 1.0
#define ENABLE_AUDIO
#define ENABLE_MOTION
#define ENABLE_WS2811
#define ENABLE_SD
#endif

#ifdef CONFIG_PRESETS
Preset presets[] = {
   { "TeensySF", "tracks/venus.wav",
    StyleNormalPtr<CYAN, WHITE, 300, 800>(),
    StyleNormalPtr<CYAN, WHITE, 300, 800>(),
    StyleNormalPtr<WHITE, WHITE, 300, 800>(), "cyan"},
   { "SmthJedi", "tracks/mars.wav",
    StylePtr<InOutSparkTip<EASYBLADE(BLUE, WHITE), 300, 800> >(),
    StylePtr<InOutSparkTip<EASYBLADE(BLUE, WHITE), 300, 800> >(),
    StyleNormalPtr<WHITE, WHITE, 300, 800>(), "blue"},
   { "SmthGrey", "tracks/mercury.wav",
    StyleFirePtr<RED, YELLOW, 0>(),
    StyleFirePtr<RED, YELLOW, 1>(),
    StyleNormalPtr<WHITE, WHITE, 300, 800>(), "fire"},
   { "SmthFuzz", "tracks/uranus.wav",
    StyleNormalPtr<RED, WHITE, 300, 800>(),
    StyleNormalPtr<RED, WHITE, 300, 800>(),
    StyleNormalPtr<WHITE, WHITE, 300, 800>(), "red"},
   { "RgueCmdr", "tracks/venus.wav",
    StyleFirePtr<BLUE, CYAN, 0>(),
    StyleFirePtr<BLUE, CYAN, 1>(),
    StyleNormalPtr<WHITE, WHITE, 300, 800>(), "blue fire"},
   { "TthCrstl", "tracks/mars.wav",
    StylePtr<InOutHelper<EASYBLADE(OnSpark<GREEN>, WHITE), 300, 800> >(),
    StylePtr<InOutHelper<EASYBLADE(OnSpark<GREEN>, WHITE), 300, 800> >(),
    StyleNormalPtr<WHITE, WHITE, 300, 800>(), "green"},
   { "TeensySF", "tracks/mercury.wav",
    StyleNormalPtr<WHITE, RED, 300, 800, RED>(),
    StyleNormalPtr<WHITE, RED, 300, 800, RED>(),
    StyleNormalPtr<WHITE, WHITE, 300, 800>(), "white"},
   { "SmthJedi", "tracks/uranus.wav",
    StyleNormalPtr<AudioFlicker<YELLOW, WHITE>, BLUE, 300, 800>(),
    StyleNormalPtr<AudioFlicker<YELLOW, WHITE>, BLUE, 300, 800>(),
    StyleNormalPtr<WHITE, WHITE, 300, 800>(), "yellow"},
   { "SmthGrey", "tracks/venus.wav",
    StylePtr<InOutSparkTip<EASYBLADE(MAGENTA, WHITE), 300, 800> >(),
    StylePtr<InOutSparkTip<EASYBLADE(MAGENTA, WHITE), 300, 800> >(),
    StyleNormalPtr<WHITE, WHITE, 300, 800>(), "magenta"},
   { "SmthFuzz", "tracks/mars.wav",
    StyleNormalPtr<Gradient<RED, BLUE>, Gradient<CYAN, YELLOW>, 300, 800>(),
    StyleNormalPtr<Gradient<RED, BLUE>, Gradient<CYAN, YELLOW>, 300, 800>(),
    StyleNormalPtr<WHITE, WHITE, 300, 800>(), "gradient"},
   { "RgueCmdr", "tracks/mercury.wav",
    StyleRainbowPtr<300, 800>(),
    StyleRainbowPtr<300, 800>(),
    StyleNormalPtr<WHITE, WHITE, 300, 800>(), "rainbow"},
   { "TthCrstl", "tracks/uranus.wav",
    StyleStrobePtr<WHITE, Rainbow, 15, 300, 800>(),
    StyleStrobePtr<WHITE, Rainbow, 15, 300, 800>(),
    StyleNormalPtr<WHITE, WHITE, 300, 800>(), "strobe"},
   { "TeensySF", "tracks/venus.wav",
    &style_pov,
    StyleNormalPtr<BLACK, BLACK, 300, 800>(),
    StyleNormalPtr<BLACK, BLACK, 300, 800>(), "POV"},
   { "SmthJedi", "tracks/mars.wav",
    &style_charging,
    StyleNormalPtr<BLACK, BLACK, 300, 800>(),
    StyleNormalPtr<BLACK, BLACK, 300, 800>(), "Battery\nLevel"}
};
BladeConfig blades[] = {
 { 0, WS281XBladePtr<130, bladePin, Color8::GRB, PowerPINS<bladePowerPin2, bladePowerPin3> >(),
    WS281XBladePtr<8, blade2Pin, Color8::GRB, PowerPINS<bladePowerPin4, bladePowerPin5> >(),
    SimpleBladePtr<CH1LED, CH2LED, NoLED, NoLED, bladePowerPin5, bladePowerPin6, -1, -1>()
  , CONFIGARRAY(presets) },
};
#endif

#ifdef CONFIG_BUTTONS
Button PowerButton(BUTTON_POWER, powerButtonPin, "pow");
Button AuxButton(BUTTON_AUX, auxPin, "aux");
#endif

so you have 3 blades, what kind of setup do you have. are you using NPXL or a anode RGB ?

I’m using a neopixel set up

the section that reads

 { 0, WS281XBladePtr<130, bladePin, Color8::GRB, PowerPINS<bladePowerPin2, bladePowerPin3> >(),
    WS281XBladePtr<8, blade2Pin, Color8::GRB, PowerPINS<bladePowerPin4, bladePowerPin5> >(),
    SimpleBladePtr<CH1LED, CH2LED, NoLED, NoLED, bladePowerPin5, bladePowerPin6, -1, -1>()
  , CONFIGARRAY(presets) },

the first line is your main blade for the neopixel, based on this it looks like you have a short blade (either 26 to 30 inches in length)

the second line looks like there are 8 neopixels. chances are there is a cool graphic or some type of lighting on the inside of the hilt when your blade is turned on without the blade (please confirm this).

that last line is what is confusing that line means that you are using a simple led (usually 5mm led looks abit like this

image

can you confirm this in your hilt.
I would also like to get clarification on the Points that NoSloppy stated above as well. the installation of the drivers can be found here.

this is the inventor of Proffieboards tutorial on how to install on a windows pc. however if you have a mac it is plug and play.

please watch the whole thing through and if you have any questions after watching this then feel free to ask. the instructions are windows specific, so if you are running on a MacOS feel free to ask.

P.S. welcome to the group and remember, the only dumb question is the one not asked.

1 Like

Thanks afro :smiley:

I can confirm that there is light at the base of the hilt and the leds are flat rather than bulbs.

The light and effects such as clash work fine the problem is not having any sound or the ability to cycle the colours of fonts.

Before it went wrong the hilt would give a crackle sound effect when the battery was inserted or the board was plugged into the PC. This no longer happens.

If i switch the SD card to another identical saber i have it works fine.

1 Like

remove all the .ini files that are not in font folders on sd card. Your saber is programmed with save state. Those .ini files interfere when you reprogram and add fonts.

2 Likes

this is normal, it’s nothing to worry about. what’s happening is that the usb has a small charge but isn’t powerful enough to give the speaker enough charge to sound better so it crackles.

I knew that was normal, i’m more worried that it doesnt do it all now haha.

And i went through the vid you sent and all my drivers are installed correctly

1 Like

remove all the .ini files that are not in font folders on sd card. Your saber is programmed with save state. Those .ini files interfere when you reprogram and add fonts.

I gave that a try and still no luck. Doing same as before unfortunately :frowning:

When you went to add a font, were you editing a local copy of the config that they sent on the SD card? And then was your return to normal meaning you tried to upload an original, unedited version of that config?

I was editing a copy of a config that came with proffie os and renamed it to mysaber_config as per the instructions on the proffie website.

and by return to normal i meant back to the previous config version i put on that worked

Right. So you should edit a copy of the config that comes with the saber. (the one on the paper I suppose).
A defaut OS config won’t be programmed for your specific wiring.
Adding a new font is just changing the first argument in a preset like this:
{ “fontNameHere”, “trackPathAndFileNameHere”,
StylesGoHere}
The CONFIG_TOP section and the blade array at the bottom should remain the same as what they provided…generally speaking.

it only ask me to change the BladeConfig blades section to what it says on the paper. Like i mentioned before this config works in another blade of the same make and did work previously in this blade until i tried to add another font.

Ok so then it sounds like a simple matter of the edit you made to add the font.
Add the font to the SD card, then edit the preset to use it.
It should match the font folder name exactly, case sensitively.
Just match the syntax of the other existing presets except use your new font name instead. That should work fine.

Ok ill try that.

But before i try re add the new font I just checked that all the current config presets match the file names on the SD and they do and it still not working. Still stuck on same colour and no sound

Unfortunatly it still isnt working. Is there anyway to wipe the os comepletly and install a fresh ProffieOS?

SOLVED!

And the culprit was…

A plug had come out of its socket. I thought despite advice from the manufacturer telling me not to do this, i took the board out and check under it and there it was, the loose socket. Plugged it back and all works again.

Thanks for all your help guys and sticking with it its much appreciated :smiley:

changed title for search engines

1 Like

oh that’s great news. well done on finding the culprit. this might be a good time to encourage people to take photos first.