Recall on 4.00 Beta

[billmi]

I hear you. Though I must point out, as clarified in a previous thread, folding paper or aluminum foil hats is just a hobby for me, not a job. :-)

-Bill

[RoadDawg]

Originally posted by jeffremiller
Interesting... I haven't had this problem. But then again, I wear an aluminum foil hat to keep the aliens and the government from reading my thoughts.

I do the samething. Only it's to keep Major League Baseball from knowing my hat size.

[Swede X-mag]

Is AGD working on this issue With the HES/Solenoid?
Or Is It up to us on AO to solve this?

What i pesonaly want is an software that has the the features of the 3.2 but with an lock for the SHBF (debounce setting) So if the 3.2 software works. Couldent some one just add this lock eature and make a 3.3 software.

[USAF-Flyboy with a Mag]

Originally posted by Swede X-mag
Is AGD working on this issue With the HES/Solenoid?
Or Is It up to us on AO to solve this?

What i pesonaly want is an software that has the the features of the 3.2 but with an lock for the SHBF (debounce setting) So if the 3.2 software works. Couldent some one just add this lock eature and make a 3.3 software.

I can't speak for the 3.2, but the 4.0 does have a lock for the debounce.

[SeeK]

I figure it's time again to stimulate the AO neurons:

They produce magnetic shielding material and have a magnetic shielding calculator.

http://www.magnetic-shield.com/products/alloys.html

Of course I'm not sure we can rule out RF interference since an oscillating magnetic field could create an RF field in the wires or board traces.

http://www.astronomynotes.com/light/s2.htm

http://www.trifield.com/magnetic_fields.htm

In case you wondered how many gauss it takes to trigger a Hall Effect sensor:

http://www.du.edu/~etuttle/electron/elect19.htm

Any other thoughts?

[Da1spaz247]

well guys, I would absolutely love to help out here, but I have to admit, this is way above me! Here is my attempt at the problem.

To me, it almost seems like maybe 4.0 just has an error in the programming or something. Maybe a slight mistake when writing the software. Miscue said it is a much "cleaner" version of 3.2 or something, but maybe 3.2 was written complicatedly for a reason? (is complicatedly even a word?)

Is it not something that changing the software couldn't fix? After all, it has to be software related, otherwise no other software would work with the existing hardware.

Please correct me if I am wrong.

[pbzmag]

It's hardware. Some had no problems after the 3.2 upgrade and had no problems, some did. I had 2.4 and was able to produce the full-auto bug. It was slight but was there. Once I changed the solenoid leads, it went away. I had mines upgraded to 4.0 and had no problems.

[USAF-Flyboy with a Mag]

Originally posted by Da1spaz247
well guys, I would absolutely love to help out here, but I have to admit, this is way above me! Here is my attempt at the problem.

To me, it almost seems like maybe 4.0 just has an error in the programming or something. Maybe a slight mistake when writing the software. Miscue said it is a much "cleaner" version of 3.2 or something, but maybe 3.2 was written complicatedly for a reason? (is complicatedly even a word?)

Is it not something that changing the software couldn't fix? After all, it has to be software related, otherwise no other software would work with the existing hardware.

Please correct me if I am wrong.

It is a hardware problem...NOT A SOFTWARE PROBLEM

[Miscue]

Originally posted by Da1spaz247

To me, it almost seems like maybe 4.0 just has an error in the programming or something. Maybe a slight mistake when writing the software.

Nope, the software works as it should.

[Rope a Dope]

Originally posted by Miscue


Nope, the software works as it should.

So why can't I get it?!?!

[miked]

Hey miscue:

I was bored at work the other day and hooked my x-mag up to an oscilliscope. While watching the HES output I triggered it several times to see if I could detect any second induced pulse on the line which would then result in a second firing with the right software. I didn't see anything. I have 2.4 but that shouldn't matter if its a hardware thing. It could be that mine is a very nice gun as far as this condition and will never see the FA issue. Or it could be that I rushed the setup of the scope and wasn't sampling fast enough. if you want I can check other locations on the circuit for issues. can't promise I will have time soon but I can try.

oh and I was wondering if you thought about maybe doing something where you ignore anything from the HES in a small window after the true pulse. not sure how complicated that would be. I would imagine it would take a ton of processing logic to do. my thought here is that basically the hardware problem should occur a regular interval after the trigger. so simply ignore x nanoseconds after the trigger to x + some then resume normal monitoring. fine maybe you wouldn't catch every real trigger but you would get most so long as the window is small. probably just better to find the hardware issue, fix it and be done with it though.

[MantisMag]

if i'm not mistaken that would be debounce.

[OfficerGoat]

Guess what ... I am 90% certian I have it worked out.. At least on my gun :) I need to get some more testing before I open my mouth and look too much like an asshat... but I think there really is light at the end of this tunnel. :)

BTW... I dont think its the HES taking the interfeirence.

[OfficerGoat]

Miscue!!!

BTW .. clean out your inbox!!!!

[gibby]

GO OG GO!!!