3.2 software w/ shot buffering

[DiRTyBuNNy]

Originally posted by BTAutoMag
(i was being sarcastic)

I wasn't talking about you specifically...i know it's not your fault..I was just shouting up at Mt. Olympus..

[BTAutoMag]

lol i never noticed


AGD = Zeus

[Evil1]

3.2 software

Sorry for being a pest w/ this whole 3.2 thing. I didn't realize it was the 3rd time. Thank you for the info though.

[rikkter]

iuno if its just me or what and it being i woke up 15 minutes ago, but i read this whole thread and i sware its like 3 combined threads. so many off topic/weird posts lol.

[DiRTyBuNNy]

it's ok...people just haven't recognized the fact that making your X-Mag go full auto isn't a bug...it's an undocumented feature..Microsoft does that all the time..

[Dayspring]

It's a bug that's happened 3 times. Let it go DB...

[Evil1]

3.2 software

I don't get it. What about an X-mag going full auto? And what about Microsoft? I am not to smart when it comes to computer talk. The one I'm on is less than a week old and its the first one I've ever owned.

[Dayspring]

DB had an issue with his gun. The 3.2 software will act funky in some Emag/Xmags due to the HES picking up electronic "noise." Hence the full auto. Changing out the HES, putting a capacitor inline or changing back to 2.4 software would solve all those problems.

[Evil1]

3.2software

What is the max bps on the 2.4 and 3.2? Which one is better?

[Dayspring]

20bps for both.

3.2 if you don't have any issues with bounce. It has shot buffering which will increase the ROF.

It also has a nifty trigger test mode to help you set up the magnets- tells you when the HES sees the magnet and when it doesn't.

[Tobe2be]

ok i picked up my x mag yesterday and i really didnt see any diffrence when i played around with the shot buffer. What exactly does the shot buffer do. i think i can handle big terms and whatnot.

[Dayspring]

The way I understand it---

For example, a complete firing cycle takes 50ms. That's from trigger pull all the way to relocking the sear and regassing the air chamber.

With anything before 3.2- if you pulled the trigger during that 50ms, the gun would ignore the shot.

With 3.x (includes Q 1.x), you can set the time between the first shot and the next opportunity for you to pull the trigger.

The lower the setting on the gun, the shorter the time frame between firing and the gun looking for another pull. The higher the setting, the longer the gun will wait to accept a new trigger pull.

i.e. a shot buffer setting of 4 will wait 4ms after the first trigger pull and then look for another pull.

i.e. a shot buffer setting of 100 will wait 100ms after the first trigger pull and then look for another pull.

Make sense?

[MantisMag]

a few additions to dayspring's explanation:

For example, a complete firing cycle takes 50ms. That's from trigger pull all the way to relocking the sear and regassing the air chamber.

50ms is the time between shots at 20 bps. 1 second divide by 20 shots gives you 50ms per shot cycle.

With anything before 3.2- if you pulled the trigger during that 50ms, the gun would ignore the shot.

With 3.x (includes Q 1.x), you can set the time between the first shot and the next opportunity for you to pull the trigger.

The lower the setting on the gun, the shorter the time frame between firing and the gun looking for another pull. The higher the setting, the longer the gun will wait to accept a new trigger pull.

i.e. a shot buffer setting of 4 will wait 4ms after the first trigger pull and then look for another pull.

i.e. a shot buffer setting of 100 will wait 100ms after the first trigger pull and then look for another pull.

we'll use the 4ms example. let's say you happen to pause right at the point of detection. you get off two pulls with only 2ms between them. that second shot gets ignored. now let's say you do a very fast double tap and get one 10ms after the first. that's after the buffer setting but before your max rof cap. that gets saved to the buffer. the marker waits the remaining 40ms (50ms between shots. you've already waited 10ms since the last shot fired) and then fires.

i do have two questions though. how many shots can be buffered at once? it'd be interesting if you had a long queue of shots buffered and the xmag kept firing for a significant time after you stopped pulling.

how does the software measure the time for the buffer delay? is it when a shot is fired or the last recorded pull? for example how would it deal with this situation. let's say the buffer delay is set to 20ms. the max rof is set to 20bps. you pull once every 30ms. you pull once it fires. you pull the second time it gets buffered. at 50ms from the first pull it fires the buffered shot. at 60ms you pull again. that's only 10ms after the shot fired. less than the 20ms buffer delay. but it's 30ms since the last time you pulled the trigger. what does it do?

[AGD]

Sorry but I dont read every thread every day. I someone wants an answer from me start a new thread with "question for AGD" so I will see it.

All the xmags get 3-500 shots on them in testing. If they need to be taken apart and tweeked, they get another 3-500. Guns go out with all kinds of numbers on the shot counter. Some times the counter glitches and you get really stupid numbers.

My main tech guy is on vacation this week. I went out to check the 3.2 problem myself and we dont have any guns here with 3.2 in them. Next I went to program one up to 3.2 and the programer is on its way to texas for the scenario game.

So basically this whole thing is on hold until the end of next week when the programer comes back from the field and I get back in the office.

We have a next generation software in the works that blows 3.2 away. Most likely I am going to recall 3.2 and wait for the next version. I will let you know by the end of the day.

AGD

[TheTramp]

I just got an RA# to send my E-Mag in for the 3.2.

If it's going to be a while (more than a month) for the "next generation" to come out I'd rather just get the 3.2 now and get the new one when it is available.

It'll be 4-5 months before I've got to worry about tourny legality so if my E-Mag turns out to be one of the few that doesn't work well with 3.2 I wont have a problem.