random blaster blocks and force effects help!!

shriker1
Commander

Posts: 173

random blaster blocks and force effects help!! Dec 4, 2019 14:27:35 GMT -5

Quote

Post by shriker1 on Dec 4, 2019 14:27:35 GMT -5

My two Proffieboard V2.2's keep on having random Blaster blocks and power switch presses. i have triple checked everything and nothing seems to be the culprit other then the board or os. i have been trying to find a solution on the facebook forum but i haven't found anything so far.

Possible reasons that didnt come up with anything:

Switches Faulty? - it does it with the switches disconnected as well
Bad Board Wiring? - Resoldered switches and ground multiple times so they dont touch anything else
Bad Recharge Port Wiring? - Pushed and pulled and tugged and resoldered to get a reaction, does absolutely nothing, doesnt trigger anything
Shorting Switch Wires? - To the best of my ability i have checked all concerning wires and nothing comes up as weird.
What Does The Serial Monitor Say? - Every Several seconds there is suddenly triple short power button presses, even up to six or eight presses, all at the EXACT same time, aux button does it less frequently. ill send an example soon.

has this been happening to anyone else? this has only been happening to my new proffie v2.2 boards

i should also mention that during all of the shorts i wasnt even touching it let alone near it, it just does it on its own.

Last Edit: Dec 4, 2019 14:28:54 GMT -5 by shriker1

yodadawa
Commander

Posts: 130

random blaster blocks and force effects help!! Dec 4, 2019 15:14:55 GMT -5 via Tapatalk

Quote

Post by yodadawa on Dec 4, 2019 15:14:55 GMT -5

I have one board with strange behavior too but I need to make more tests.

What kind are the switches?

False clashes can be caused by some bass speakers, chassis design (board close to speaker) and low sensibility parameter. But false blaster blocks it should be a kind of noise in aux. Switch.

shriker1 Commander Posts: 173	random blaster blocks and force effects help!! Dec 4, 2019 15:20:36 GMT -5 Quote Select Post Deselect Post Link to Post Back to Top Post by shriker1 on Dec 4, 2019 15:20:36 GMT -5 they are 12mm Non Illuminated AV switches from KR Sabers. But the random blaster blocks and power switch presses happen even when the the switches are disconnected
	Last Edit: Dec 4, 2019 15:22:05 GMT -5 by shriker1

profezzorn
Armory

May the source be with you.

Posts: 4,312

random blaster blocks and force effects help!! Dec 4, 2019 15:25:53 GMT -5

Quote

Post by profezzorn on Dec 4, 2019 15:25:53 GMT -5

I saw some of this on FB, and it's certainly a weird problem.
The fact that two boards is doing it would seem to indicate some problem with the software or configuration.
Could you post your config file? Maybe some pictures of the wiring?

Signatures are a waste of space.

shriker1 Commander Posts: 173	random blaster blocks and force effects help!! Dec 4, 2019 15:32:05 GMT -5 Quote Select Post Deselect Post Link to Post Back to Top Post by shriker1 on Dec 4, 2019 15:32:05 GMT -5 I'll post it when i get home. i am AFPD (Away From Personal Desktop) at the moment.
	Last Edit: Dec 4, 2019 15:34:14 GMT -5 by shriker1

profezzorn
Armory

May the source be with you.

Posts: 4,312

random blaster blocks and force effects help!! Dec 4, 2019 15:35:17 GMT -5

Quote

Post by profezzorn on Dec 4, 2019 15:35:17 GMT -5

Dec 4, 2019 15:25:53 GMT -5 profezzorn said:

I saw some of this on FB, and it's certainly a weird problem.
The fact that two boards is doing it would seem to indicate some problem with the software or configuration.
Could you post your config file? Maybe some pictures of the wiring?

Btw, getting more than one press from the same button in the same millisecond should be impossible because of debouncing, which has a 10ms timeout.
Going from not pressed to pressed is immediate, but going from pressed to not pressed should take at least 10 ms.
So if you really have 6-8 events from the same button AT THE SAME TIME, there is definitely something wrong with the software.
If they are at least 10ms apart, then the problem might be something else.

Have you tried measuring the voltage between GND and the button pad? Should be 3.3v when button is not pressed and 0v when button is pressed.

Signatures are a waste of space.

shriker1
Commander

Posts: 173

random blaster blocks and force effects help!! Dec 4, 2019 15:44:46 GMT -5 via mobile

Quote

Post by shriker1 on Dec 4, 2019 15:44:46 GMT -5

I pulled my original serial monitor from Facebook which is still consistently happening.

unit = 0 vol = 0.50, Playing Hero/font/font.wav
channels: 1 rate: 44100 bits: 16
EVENT: Aux-Pressed millis=47186
EVENT: Aux-Released millis=47361
EVENT: Aux-Shortclick millis=47361
DISPLAY: Preset: 4
RgueVdrV2
Scanning sound font: RgueVdrV2 done
humstart=1000.00
Activating polyphonic font.
version=2.00
swingsensitivity=300.00
maximumhumducking=75.00
swingsharpness=3.00
swingstrengththreshold=30.00
transition1degrees=60.00
transition2degrees=240.00
maxswingvolume=3.00
Activating SmoothSwing V2
Proffie Font Detected
SmoothSwing pairs: 8
Accent Swings Enabled.
Polyphonic swings: 16
Monophonic swings: 0
Accent Slashes NOT Detected:
Accent Spins NOT Detected:
unit = 0 vol = 0.50, Playing RgueVdrV2/font.wav
channels: 1 rate: 44100 bits: 16
Amplifier off.
EVENT: Power-Pressed millis=49053
EVENT: Power-Released millis=49242
EVENT: Power-Shortclick millis=49242
Ignition.
unit = 0 vol = 0.00, Playing RgueVdrV2/hum01.wav
channels: 1 rate: 44100 bits: 16
unit = 1 vol = 0.50, Playing RgueVdrV2/out01.wav
channels: 1 rate: 44100 bits: 16
unit = 2 vol = 0.50, Playing RgueVdrV2/swingl01.wav
channels: 1 rate: 44100 bits: 16
unit = 3 vol = 0.50, Playing RgueVdrV2/swingh01.wav
channels: 1 rate: 44100 bits: 16
Playing RgueVdrV2/swingh01.wav
channels: 1 rate: 44100 bits: 16
Playing RgueVdrV2/swingl01.wav
channels: 1 rate: 44100 bits: 16
Battery voltage: 3.56
EVENT: Power-Pressed ON millis=61369
EVENT: Power-Released ON millis=61369
EVENT: Power-Shortclick ON millis=61369
EVENT: Power-Pressed ON millis=65663
EVENT: Power-Released ON millis=65663
EVENT: Power-Shortclick ON millis=65664
Playing RgueVdrV2/hum01.wav
channels: 1 rate: 44100 bits: 16
Playing RgueVdrV2/swingh01.wav
channels: 1 rate: 44100 bits: 16
Playing RgueVdrV2/swingl01.wav
channels: 1 rate: 44100 bits: 16
EVENT: Power-Pressed ON millis=72870
EVENT: Power-Held ON millis=73171
EVENT: Power- ON millis=73671
EVENT: Power-HeldLong ON millis=74871
unit = 1 vol = 0.50, Playing RgueVdrV2/in01.wav
channels: 1 rate: 44100 bits: 16
EVENT: Power-Released millis=75337
Amplifier off.
Unmounting SD Card.
Battery voltage: 3.71
Booster off.
Motion disable.
I2C sleeping..
Battery voltage: 3.73
Battery voltage: 3.73
Battery voltage: 3.73
Battery voltage: 3.73
EVENT: Power-Pressed millis=165213
Motion setup ... I2C init..
done.
SWING
EVENT: Swing mods Power millis=165225
SWING
EVENT: Swing mods Power millis=165227
SWING
EVENT: Swing mods Power millis=165228
EVENT: Power-Released millis=165406
EVENT: Power-Shortclick millis=165406
Ignition.
unit = 0 vol = 0.00, Playing RgueVdrV2/hum01.wav
channels: 1 rate: 44100 bits: 16
unit = 1 vol = 0.50, Playing RgueVdrV2/out01.wav
channels: 1 rate: 44100 bits: 16
unit = 2 vol = 0.00, Playing RgueVdrV2/swingl05.wav
channels: 1 rate: 44100 bits: 16
unit = 3 vol = 0.00, Playing RgueVdrV2/swingh05.wav
channels: 1 rate: 44100 bits: 16
Playing RgueVdrV2/swingl05.wav
channels: 1 rate: 44100 bits: 16
Playing RgueVdrV2/swingh05.wav
channels: 1 rate: 44100 bits: 16
Battery voltage: 3.55
EVENT: Aux-Pressed ON millis=185453
EVENT: Aux-Released ON millis=185662
EVENT: Aux-Shortclick ON millis=185662
unit = 1 vol = 0.50, Playing RgueVdrV2/blst09.wav
channels: 1 rate: 44100 bits: 16
Playing RgueVdrV2/hum01.wav
channels: 1 rate: 44100 bits: 16
Playing RgueVdrV2/swingl05.wav
channels: 1 rate: 44100 bits: 16
Playing RgueVdrV2/swingh05.wav
channels: 1 rate: 44100 bits: 16
Battery voltage: 3.54
Playing RgueVdrV2/swingl05.wav
channels: 1 rate: 44100 bits: 16
Playing RgueVdrV2/swingh05.wav
channels: 1 rate: 44100 bits: 16
Playing RgueVdrV2/hum01.wav
channels: 1 rate: 44100 bits: 16
EVENT: Power-Pressed ON millis=206944
EVENT: Power-Released ON millis=206944
EVENT: Power-Shortclick ON millis=206944
EVENT: Power-Pressed ON millis=216894
EVENT: Power-Released ON millis=216894
EVENT: Power-Shortclick ON millis=216895
Battery voltage: 3.53
Playing RgueVdrV2/swingl05.wav
channels: 1 rate: 44100 bits: 16
Playing RgueVdrV2/swingh05.wav
channels: 1 rate: 44100 bits: 16
Playing RgueVdrV2/hum01.wav
channels: 1 rate: 44100 bits: 16
EVENT: Power-Pressed ON millis=227022
EVENT: Power-Released ON millis=227022
EVENT: Power-Shortclick ON millis=227022
EVENT: Power-Pressed ON millis=227329
EVENT: Power-Doubleclick ON millis=227329
unit = 1 vol = 0.50, Playing RgueVdrV2/force2.wav
channels: 1 rate: 44100 bits: 16
EVENT: Power-Released ON millis=227339
Battery voltage: 3.53
Playing RgueVdrV2/swingl05.wav
channels: 1 rate: 44100 bits: 16
Playing RgueVdrV2/swingh05.wav
channels: 1 rate: 44100 bits: 16
Playing RgueVdrV2/hum01.wav
channels: 1 rate: 44100 bits: 16
EVENT: Power-Pressed ON millis=249592
EVENT: Power-Released ON millis=249592
EVENT: Power-Shortclick ON millis=249592
Battery voltage: 3.52
Playing RgueVdrV2/swingl05.wav
channels: 1 rate: 44100 bits: 16
Playing RgueVdrV2/swingh05.wav
channels: 1 rate: 44100 bits: 16
EVENT: Power-Pressed ON millis=267030
EVENT: Power-Released ON millis=267030
EVENT: Power-Shortclick ON millis=267030
Playing RgueVdrV2/hum01.wav
channels: 1 rate: 44100 bits: 16
EVENT: Power-Pressed ON millis=269452
EVENT: Power-Released ON millis=269452
EVENT: Power-Shortclick ON millis=269452
Battery voltage: 3.52
Playing RgueVdrV2/swingl05.wav
channels: 1 rate: 44100 bits: 16
Playing RgueVdrV2/swingh05.wav
channels: 1 rate: 44100 bits: 16
EVENT: Power-Pressed ON millis=280784
EVENT: Power-Released ON millis=280785
EVENT: Power-Shortclick ON millis=280785
EVENT: Power-Pressed ON millis=286299
EVENT: Power-Released ON millis=286299
EVENT: Power-Shortclick ON millis=286299
EVENT: Power-Pressed ON millis=287356
EVENT: Power-Released ON millis=287356
EVENT: Power-Shortclick ON millis=287356
Playing RgueVdrV2/hum01.wav
channels: 1 rate: 44100 bits: 16
EVENT: Power-Pressed ON millis=290743
EVENT: Power-Released ON millis=290743
EVENT: Power-Shortclick ON millis=290744
EVENT: Power-Pressed ON millis=294349
EVENT: Power-Held ON millis=294650
EVENT: Power- ON millis=295150
EVENT: Power-HeldLong ON millis=296350
unit = 1 vol = 0.50, Playing RgueVdrV2/in01.wav
channels: 1 rate: 44100 bits: 16
Amplifier off.

profezzorn Armory May the source be with you. Posts: 4,312	random blaster blocks and force effects help!! Dec 4, 2019 16:20:32 GMT -5 Quote Select Post Deselect Post Link to Post Back to Top Post by profezzorn on Dec 4, 2019 16:20:32 GMT -5 What version of ProffieOS is this?
	Signatures are a waste of space.

shriker1 Commander Posts: 173	random blaster blocks and force effects help!! Dec 4, 2019 16:26:09 GMT -5 Quote Select Post Deselect Post Link to Post Back to Top Post by shriker1 on Dec 4, 2019 16:26:09 GMT -5 Color change Proffie OS 2.6CCF

profezzorn
Armory

May the source be with you.

Posts: 4,312

random blaster blocks and force effects help!! Dec 4, 2019 16:42:38 GMT -5

Quote

Post by profezzorn on Dec 4, 2019 16:42:38 GMT -5

Dec 4, 2019 16:26:09 GMT -5 shriker1 said:

Color change Proffie OS 2.6CCF

2.6CCF has some changes in the button code. It doesn't look like those changes would cause this problem though.
However, I would still suggest trying ProffieOS 2.9 or 3.3 to see if the problems happen there too, just to rule things out.

I'd also like to see the config file.
And, one more question: Have you checked the resistance between the button pads and the nearby LED pads? (Should be nearly infinite, meaning that they are not connected.)

Signatures are a waste of space.

shriker1 Commander Posts: 173	random blaster blocks and force effects help!! Dec 4, 2019 16:56:48 GMT -5 via mobile Quote Select Post Deselect Post Link to Post Back to Top Post by shriker1 on Dec 4, 2019 16:56:48 GMT -5 I have gone back to 2.6 from 3.3 because of this, still has the same problems When I get home I’ll test the connections

profezzorn
Armory

May the source be with you.

Posts: 4,312

random blaster blocks and force effects help!! Dec 4, 2019 17:07:19 GMT -5

Quote

Post by profezzorn on Dec 4, 2019 17:07:19 GMT -5

Dec 4, 2019 16:56:48 GMT -5 shriker1 said:

I have gone back to 2.6 from 3.3 because of this, still has the same problems
When I get home I’ll test the connections

If it also happened on 3.3, that pretty much rules out the changes in the button code.

Signatures are a waste of space.

profezzorn
Armory

May the source be with you.

Posts: 4,312

random blaster blocks and force effects help!! Dec 4, 2019 17:08:45 GMT -5

Quote

Post by profezzorn on Dec 4, 2019 17:08:45 GMT -5

Dec 4, 2019 17:07:19 GMT -5 profezzorn said:

Dec 4, 2019 16:56:48 GMT -5 shriker1 said:

I have gone back to 2.6 from 3.3 because of this, still has the same problems
When I get home I’ll test the connections

If it also happened on 3.3, that pretty much rules out the changes in the button code.

None of this explains how it's possible to have a "RELEASE" event in the same millisecond as the "PRESS" event.
From what I see in the code, that should be impossible.

Signatures are a waste of space.

shriker1
Commander

Posts: 173

random blaster blocks and force effects help!! Dec 4, 2019 18:02:52 GMT -5

Quote

Post by shriker1 on Dec 4, 2019 18:02:52 GMT -5

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

#ifdef CONFIG_PRESETS
Preset presets[] = {
{ "SmthJedi", "tracks/na",
&style_charging, "Battery\nLevel"},

{ "TheBalance", "tracks/StarWars.wav",
StylePtr<InOutHelper<OnSpark<SimpleClash<SimpleClash<AudioFlicker<Cyan,DeepSkyBlue>,White,40,EFFECT_BLAST>,White>,White,200>,40,800>>()},

{ "Hero", "tracks/Anakin.wav",
StylePtr<InOutHelper<OnSpark<SimpleClash<SimpleClash<Lockup<AudioFlicker<Blue,Rgb16<0,3813,65535>>,AudioFlicker<White,Blue>,Blue>,White,40,EFFECT_BLAST>,White>,White,200>,40,800>>()},

{ "RgueVdrV2", "tracks/darthvader.wav",
StylePtr<InOutHelper<OnSpark<SimpleClash<SimpleClash<Lockup<AudioFlicker<Red,Rgb16<45025,0,11>>,AudioFlicker<White,Red>,Red>,White,40,EFFECT_BLAST>,White>,White,200>,40,800>>()},

{ "SvgNght", "tracks/Reignofvengeance.wav",
StylePtr<InOutHelper<OnSpark<SimpleClash<SimpleClash<Lockup<AudioFlicker<Red,Rgb16<22546,0,0>>,AudioFlicker<White,Red>,Red>,White,100,EFFECT_BLAST>,White>,BrownNoiseFlicker<Red,White,50>,600>,40,800>>()},

{ "KrssGrdV3", "tracks/Trailer.wav",
StylePtr<InOutHelper<OnSpark<SimpleClash<SimpleClash<Lockup<AudioFlicker<Red,Black>,AudioFlicker<White,Rgb16<16439,0,0>>,Red>,White,40,EFFECT_BLAST>,White,80>,White,200>,40,800>>()},

{ "LS6V2", "tracks/Finale.wav",
StylePtr<InOutHelper<OnSpark<SimpleClash<SimpleClash<Lockup<AudioFlicker<Green,Rgb16<1662,45025,0>>,AudioFlicker<White,Green>,Green>,White,40,EFFECT_BLAST>,White>,White,200>,40,800>>()},

{ "Menace", "tracks/Rinzler.wav",
StylePtr<InOutHelper<OnSpark<SimpleClash<SimpleClash<Lockup<AudioFlicker<Rgb16<15138,216,64410>,Rgb16<9699,1,48793>>,AudioFlicker<White,Blue>,Rgb16<15138,216,64410>>,White,40,EFFECT_BLAST>,White,80>,White,200>,40,800>>()},

{ "SstrShdws", "tracks/DarkArts.wav",
StylePtr<InOutHelper<OnSpark<SimpleClash<SimpleClash<Lockup<AudioFlicker<DeepPink,Magenta>,AudioFlicker<White,DeepPink>,DeepPink>,White,100,EFFECT_BLAST>,White>,White,600>,40,800>>()},

{ "LukeROTJ", "tracks/LordVader.wav",
StylePtr<InOutHelper<OnSpark<SimpleClash<SimpleClash<Lockup<AudioFlicker<Magenta,HotPink>,AudioFlicker<White,Magenta>,Magenta>,White,40,EFFECT_BLAST>,White>,White,200>,40,800>>()},

{ "SmthFuzz", "tracks/DuelofFates.wav",
StylePtr<InOutHelper<OnSpark<SimpleClash<SimpleClash<Lockup<AudioFlicker<Rgb16<65535,37562,0>,Yellow>,AudioFlicker<White,Rgb16<65535,37562,0>>,Rgb16<65535,37562,0>>,White,40,EFFECT_BLAST>,White,70>,White,200>,40,800>>()},

};
BladeConfig blades[] = {
{ 0, SimpleBladePtr<CreeXPE2RedTemplate<1200>, CreeXPE2GreenTemplate<500>, CreeXPE2BlueTemplate<500>, CreeXPE2WhiteTemplate<500>, bladePowerPin1, bladePowerPin2, bladePowerPin3, bladePowerPin4>(), CONFIGARRAY(presets) },
};
#endif

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

profezzorn
Armory

May the source be with you.

Posts: 4,312

random blaster blocks and force effects help!! Dec 4, 2019 18:36:03 GMT -5

Quote

Post by profezzorn on Dec 4, 2019 18:36:03 GMT -5

I don't see anything wrong with the config file, which means that we are now getting into more esoteric problems.
However, we still need to do some measurements on the button pad to see if we can figure out if something weird is going on electrically.

I also found a potential problem in debounced_button.h which could explain why the button is getting such a quick on/off.
It would only occur if digitialRead() on the pin returns HIGH and another digitialRead() right afterwards return LOW. If that's the case, it would mean that the pin goes high for a VERY short amount of time. (less than a microsecond...)

I wonder if induction could cause that? It seems unlikely, but maybe the wires driving the LEDs, or maybe the speaker could be inducing enough electrical movement in the power wire to make it read as high for a microsecond?
The induction would need to be high enough to overcome the ~40k pull-up though, which seems unlikely. (50uA induced current?)

Last Edit: Dec 4, 2019 18:50:50 GMT -5 by profezzorn

Signatures are a waste of space.

profezzorn
Armory

May the source be with you.

Posts: 4,312

random blaster blocks and force effects help!! Dec 4, 2019 18:52:39 GMT -5

Quote

Post by profezzorn on Dec 4, 2019 18:52:39 GMT -5

Dec 4, 2019 18:36:03 GMT -5 profezzorn said:

I don't see anything wrong with the config file, which means that we are now getting into more esoteric problems.
However, we still need to do some measurements on the button pad to see if we can figure out if something weird is going on electrically.

I also found a potential problem in debounced_button.h which could explain why the button is getting such a quick on/off.
It would only occur if digitialRead() on the pin returns HIGH and another digitialRead() right afterwards return LOW. If that's the case, it would mean that the pin goes high for a VERY short amount of time. (less than a microsecond...)

I wonder if induction could cause that? It seems unlikely, but maybe the wires driving the LEDs, or maybe the speaker could be inducing enough electrical movement in the power wire to make it read as high for a microsecond?
The induction would need to be high enough to overcome the ~40k pull-up though, which seems unlikely. (50uA induced current?)

Some simple tests to test the induction theory:
Does the problem occur if you set the volume in the config file to 5?
Does the problem occur if you you pick a blade style that doesn't turn any LEDs on, like StylePtr<BLACK>() ?

Signatures are a waste of space.

shriker1
Commander

Posts: 173

random blaster blocks and force effects help!! Dec 4, 2019 20:36:01 GMT -5 via mobile

Quote

Post by shriker1 on Dec 4, 2019 20:36:01 GMT -5

Ok I have narrowed down the problem to the led positive wire. It works just fine without it connected to the leds but when it’s soldered to the leds it does all the stuff mentioned. This was after I redid the recharge port

shriker1 Commander Posts: 173	random blaster blocks and force effects help!! Dec 4, 2019 20:52:04 GMT -5 via mobile Quote Select Post Deselect Post Link to Post Back to Top Post by shriker1 on Dec 4, 2019 20:52:04 GMT -5 I then switched out the recharge port for another one but it still does the same thing

shriker1
Commander

Posts: 173

random blaster blocks and force effects help!! Dec 4, 2019 21:38:29 GMT -5 projectno253 likes this

Quote

Post by shriker1 on Dec 4, 2019 21:38:29 GMT -5

alright i found the issue. yall was right, it was a short, though i couldnt for the life of me see it. it was somehow shorting between led 1 and button 1 pad. well i resoldered the button wire to the other side of the board and so far it works, same for button 2. i swear it didnt look like it was shorting AT ALL.

shriker1 Commander Posts: 173	random blaster blocks and force effects help!! Dec 4, 2019 23:20:19 GMT -5 via mobile Quote Select Post Deselect Post Link to Post Back to Top Post by shriker1 on Dec 4, 2019 23:20:19 GMT -5 Scratch that it still happens just less frequently

profezzorn Armory May the source be with you. Posts: 4,312	random blaster blocks and force effects help!! Dec 5, 2019 3:50:24 GMT -5 Quote Select Post Deselect Post Link to Post Back to Top Post by profezzorn on Dec 5, 2019 3:50:24 GMT -5 Dec 4, 2019 23:20:19 GMT -5 shriker1 said: Scratch that it still happens just less frequently Best way to check for shorts is a multimeter.
	Signatures are a waste of space.

shriker1 Commander Posts: 173	random blaster blocks and force effects help!! Dec 5, 2019 17:52:03 GMT -5 via mobile Quote Select Post Deselect Post Link to Post Back to Top Post by shriker1 on Dec 5, 2019 17:52:03 GMT -5 So I’ve checked battery positive to the button 1 pad and it says negative 658 ohms in the 2000k mode, and negative 285 volts in the 2000m mode Does this mean anything to anyone?

profezzorn
Armory

May the source be with you.

Posts: 4,312

random blaster blocks and force effects help!! Dec 5, 2019 18:06:59 GMT -5

Quote

Post by profezzorn on Dec 5, 2019 18:06:59 GMT -5

Dec 5, 2019 17:52:03 GMT -5 shriker1 said:

So I’ve checked battery positive to the button 1 pad and it says negative 658 ohms in the 2000k mode, and negative 285 volts in the 2000m mode

Does this mean anything to anyone?

negative ohms, that's impressive (and impossible)

-0.285 volts between batt+ and the button pad seems reasonable though. The button pad *should* be at 3.3 volt, so that would mean that your battery is at 3.585 volts, which would make sense.
It would be better to measure the voltage between GND and the button pad though.

Signatures are a waste of space.

shriker1 Commander Posts: 173	random blaster blocks and force effects help!! Dec 5, 2019 19:31:38 GMT -5 via mobile Quote Select Post Deselect Post Link to Post Back to Top Post by shriker1 on Dec 5, 2019 19:31:38 GMT -5 I measured 3.16 volt in 20 mode between ground and button pad*
	Last Edit: Dec 5, 2019 19:33:06 GMT -5 by shriker1

profezzorn
Armory

May the source be with you.

Posts: 4,312

random blaster blocks and force effects help!! Dec 5, 2019 20:11:53 GMT -5

Quote

Post by profezzorn on Dec 5, 2019 20:11:53 GMT -5

Dec 5, 2019 19:31:38 GMT -5 shriker1 said:

I measured 3.16 volt in 20 mode between ground and button pad*

That is right on the edge of being weird.
The voltage is supposed to be 3.3 volts. Now, it could be that your multimeter isn't very good or something, but it could also be that something is pulling down the voltage of that button for some reason.

Signatures are a waste of space.

shriker1 Commander Posts: 173	random blaster blocks and force effects help!! Dec 5, 2019 21:03:36 GMT -5 Quote Select Post Deselect Post Link to Post Back to Top Post by shriker1 on Dec 5, 2019 21:03:36 GMT -5 ok so what do i do?

shriker1
Commander

Posts: 173

random blaster blocks and force effects help!! Dec 5, 2019 22:02:54 GMT -5

Quote

Post by shriker1 on Dec 5, 2019 22:02:54 GMT -5

Dec 4, 2019 18:52:39 GMT -5 profezzorn said:

Dec 4, 2019 18:36:03 GMT -5 profezzorn said:

I don't see anything wrong with the config file, which means that we are now getting into more esoteric problems.
However, we still need to do some measurements on the button pad to see if we can figure out if something weird is going on electrically.

I also found a potential problem in debounced_button.h which could explain why the button is getting such a quick on/off.
It would only occur if digitialRead() on the pin returns HIGH and another digitialRead() right afterwards return LOW. If that's the case, it would mean that the pin goes high for a VERY short amount of time. (less than a microsecond...)

I wonder if induction could cause that? It seems unlikely, but maybe the wires driving the LEDs, or maybe the speaker could be inducing enough electrical movement in the power wire to make it read as high for a microsecond?
The induction would need to be high enough to overcome the ~40k pull-up though, which seems unlikely. (50uA induced current?)

Some simple tests to test the induction theory:
Does the problem occur if you set the volume in the config file to 5?
Does the problem occur if you you pick a blade style that doesn't turn any LEDs on, like StylePtr<BLACK>() ?

it still happens even when the volume is turned down to 5,
nothing happens when there is no led's on
i should also point out that it seems to be the worst on red.

Last Edit: Dec 5, 2019 22:30:32 GMT -5 by shriker1

profezzorn
Armory

May the source be with you.

Posts: 4,312

random blaster blocks and force effects help!! Dec 5, 2019 22:50:36 GMT -5

Quote

Post by profezzorn on Dec 5, 2019 22:50:36 GMT -5

That makes it very very likely that there is a short between the RED led pad and the button pad.
Now, the question is how, which can be pretty tricky sometimes.
If you power the board off and set your multimeter to beep mode and measure between the red led and the button pad, does it beep?

Signatures are a waste of space.

shriker1 Commander Posts: 173	random blaster blocks and force effects help!! Dec 5, 2019 23:55:10 GMT -5 Quote Select Post Deselect Post Link to Post Back to Top Post by shriker1 on Dec 5, 2019 23:55:10 GMT -5 it didnt detect any shorts either from red or green to button pad

shriker1 Commander Posts: 173	random blaster blocks and force effects help!! Dec 6, 2019 0:32:15 GMT -5 Quote Select Post Deselect Post Link to Post Back to Top Post by shriker1 on Dec 6, 2019 0:32:15 GMT -5 but it detected a value of 809 from ground to button pad 1 profezzorn
	Last Edit: Dec 6, 2019 0:33:27 GMT -5 by shriker1

random blaster blocks and force effects help!!

Post by shriker1 on Dec 4, 2019 14:27:35 GMT -5

Post by yodadawa on Dec 4, 2019 15:14:55 GMT -5

Post by shriker1 on Dec 4, 2019 15:20:36 GMT -5

Post by profezzorn on Dec 4, 2019 15:25:53 GMT -5

Post by shriker1 on Dec 4, 2019 15:32:05 GMT -5

Post by profezzorn on Dec 4, 2019 15:35:17 GMT -5

Post by shriker1 on Dec 4, 2019 15:44:46 GMT -5

Post by profezzorn on Dec 4, 2019 16:20:32 GMT -5

Post by shriker1 on Dec 4, 2019 16:26:09 GMT -5

Post by profezzorn on Dec 4, 2019 16:42:38 GMT -5

Post by shriker1 on Dec 4, 2019 16:56:48 GMT -5

Post by profezzorn on Dec 4, 2019 17:07:19 GMT -5

Post by profezzorn on Dec 4, 2019 17:08:45 GMT -5

Post by shriker1 on Dec 4, 2019 18:02:52 GMT -5

Post by profezzorn on Dec 4, 2019 18:36:03 GMT -5

Post by profezzorn on Dec 4, 2019 18:52:39 GMT -5

Post by shriker1 on Dec 4, 2019 20:36:01 GMT -5

Post by shriker1 on Dec 4, 2019 20:52:04 GMT -5

Post by shriker1 on Dec 4, 2019 21:38:29 GMT -5

Post by shriker1 on Dec 4, 2019 23:20:19 GMT -5

Post by profezzorn on Dec 5, 2019 3:50:24 GMT -5

Post by shriker1 on Dec 5, 2019 17:52:03 GMT -5

Post by profezzorn on Dec 5, 2019 18:06:59 GMT -5

Post by shriker1 on Dec 5, 2019 19:31:38 GMT -5

Post by profezzorn on Dec 5, 2019 20:11:53 GMT -5

Post by shriker1 on Dec 5, 2019 21:03:36 GMT -5

Post by shriker1 on Dec 5, 2019 22:02:54 GMT -5

Post by profezzorn on Dec 5, 2019 22:50:36 GMT -5

Post by shriker1 on Dec 5, 2019 23:55:10 GMT -5

Post by shriker1 on Dec 6, 2019 0:32:15 GMT -5

Shoutbox