X-Mags not taking 3.2...

[Miscue]

Originally posted by Steelrat
Okay, so what is the solution?

A capacitor, a fix to whatever the source of the problem is, or a debounce time that exceeds the solenoid dwell time I believe... if my theory is correct - I don't know. What would be nice is if someone verified what the problem is... I don't have the tools to do it.

My board works like a champ at 1ms debounce... it's strange that others have such problems.

[felony]

Originally posted by Steelrat
Okay, so what is the solution?

the million dollar question...

[Miscue]

Originally posted by Potatoboy


I personally flashed about 6 at SEAO with no luck, good batteries checked under load, and SHBF at 100.

No kidding eh? 100?

How about my stuff? DataPimp said mine went in like a champ... hurm.

[felony]

i have also shot mine at 100ms on SHBF.. still got the same effect as @ 4ms..


Little bit confused..

dan

[Steelrat]

This is the kind of thing that might discourage a person from getting an xmag, unless its solved quickly. Would this be something that would be fixed free of charge, if a solution is found?

[Miscue]

Originally posted by Steelrat
This is the kind of thing that might discourage a person from getting an xmag, unless its solved quickly. Would this be something that would be fixed free of charge, if a solution is found?

Rumor has is that my code is behaving better... and so far it seems to be running like a champ.

I have no way to verify this, beyond heresay... but it makes me feel good. Hehe. What would be nice is if someone with a 'noisy' board had mine put on for comparison... if it works, there's your fix - obviously an oversight in 3.2 code. If same behavior, then it's same hardware issue.

[Steelrat]

I hope it works. Its just that 3.2 is supposed to be the software that transforms the Xmag, and yet there is a chance it will nuke your board. Thats a crappy choice to have to make.

[MantisMag]

well there's no damage done. and you can always flash it back right?

[pito189]

Originally posted by Steelrat
I hope it works. Its just that 3.2 is supposed to be the software that transforms the Xmag, and yet there is a chance it will nuke your board. Thats a crappy choice to have to make.

No it didn't "nuke" my board, Tater found that it didn't work, and just flashed me back to 2.4.

Hopefully this problem will get worked out. :)

[Sir_Brass]

Originally posted by Miscue
Edit: I'll double-check the code. I just thought of a possible issue.

Mission accomplished . Glad I could help by saying SOMETHING that made you stumble across the problem :).

[cgrieves]

I had the "noisy" HES symptoms where the gun would fire fully auto. For me the solution was an easy one- I simply reversed the HE sensor (carefully bending the wires the other way) and reversed the trigger magnet. That completely solved it- easy to do so probably worth a try.

It seems like the problem could be inconsistent hysteresis with some sensors.

[cledford]

Originally posted by felony

zero control, like trying to stop a beamer in the snow :0

HA-HA!!!! Dan, this is a classic quote! I hate ours, it is the most impratical car in the world - especially during the winter!

-Calvin

[cledford]

Originally posted by Miscue


Rumor has is that my code is behaving better... and so far it seems to be running like a champ.

I have no way to verify this, beyond heresay... but it makes me feel good. Hehe. What would be nice is if someone with a 'noisy' board had mine put on for comparison... if it works, there's your fix - obviously an oversight in 3.2 code. If same behavior, then it's same hardware issue.

Hoover can do mine - I can drop by the shop on Friday if you both are cool with it. He can see the continuous bounce (without air) that is the same from 4 to 100ms. I then can show him the constant double tapping at 20ms with air and paint. We can flash it and try it out.

-Calvin

[felony]

I liked that quote too..

But anyway, I have never shot an emag beefore, so i do not know how they are supposed to feel. w/o air the trigger feels fine, but when I gas it up, it just seems to bounce all over town...

LMK if you guys get a good solution to this..

thanks
dan

[JEDI]

What is the primary function for the v3.2? Or in other words what was it made to do/fix? Is more bounce an inherant side effect that was known from the begining? I'm completely outta the loop so fill me in (with as little "Day-babble" as possable).

Aside from these odd occurances, is it doing what its supposed to?