Who can flash 4.01 on an Emag?

[Miscue]

So something in the 8-bit microprocessor wasn't able to handle the load that the firmware was running it... Hmmm... I guess I may have to study the three pdf's and break back into my former geek status... I guess AGD wouldn't necessarily be liable, but the persons responsible for the modification of the firmware. I guess I will have to wait until I can get my own eMag or xMag to play further...

This is complete nonsense.

[Miscue]

Kinda skewed logic,
Who else is liable really? Maybe the company that makes the loader that feeds the gun paint or the comapny that supplies the gun with air? How would installing a board not make AGD liable yet someone who creates there own software, inturn, makes AGD liable.

AGD has used the safety issue to skirt the issue in the past. If it was that big of an issue Pride wouldn't be using it would they?



If that were true then how come there isnt a problem with the morlock or pred'ed e/xmags?

No offense to Miscue, but I think this was his first big programming project. brians a great guy, I meet him a txball, but I am not sure if he was most qualified to write the code. Whether this is true or not, the biggest issue I see is that AGD farmed out 3.2, then 'scue (another out of house guy), wrote somemore code. Sounds like we need someone familiar with the HES switch to write a more comptent code, again if that is even the issue.

We will see as more e's are pred'ed out.

-gt

You are not qualified to make judgements about my qualifications.

"More competent code." I cannot express how much this pisses me off. You are trashing my work that you know nothing about.

[Muzikman]

'que is as qualified to write code for an emag as a microsoft programmer is to write windows. Actually, probably more so.

[Miscue]

'que is as qualified to write code for an emag as a microsoft programmer is to write windows. Actually, probably more so.

I don't think I like that parallel at all! But thanks.

[GT]

You are not qualified to make judgements about my qualifications.

"More competent code." I cannot express how much this pisses me off. You are trashing my work that you know nothing about.

Dont take it that because that is not what I meant. I also think I am more than comptent to make comments about "your work." as I use a 3.2 emag often. If you havnt noticed so have others. Maybe I can drive a point that I dont want to make. If the largest complaint about the emag is its software, who's fault is that? I know you make some great software, 4.X, so the blame isnt yours rather AGD's reluctance to release it.

I have also read posts, that you posted, that working on the emag software was what intrested you in programming. What that tells me is the emag was one of the first pb related software projects you have worked on.

Lets go back to the issue at hand before people get their pride stepped on.

[Muzikman]

Dont take it that because that is not what I meant. I also think I am more than comptent to make comments about "your work." as I use a 3.2 emag often. If you havnt noticed so have others. Maybe I can drive a point that I dont want to make. If the largest complaint about the emag is its software, who's fault is that? I know you make some great software, 4.X, so the blame isnt yours rather AGD's reluctance to release it.

I have also read posts, that you posted, that working on the emag software was what intrested you in programming. What that tells me is the emag was one of the first pb related software projects you have worked on.

Lets go back to the issue at hand before people get their pride stepped on.

Umm...If I am not mistaken it was the other way around. He knew ASM and decided to try to write code for the gun to give hims something to do in his spare time. I could be wrong, but he did graduate in a Comp Sci degree.

[GT]

Umm...If I am not mistaken it was the other way around. He knew ASM and decided to try to write code for the gun to give hims something to do in his spare time. I could be wrong, but he did graduate in a Comp Sci degree.

this is going to turn into a miscue v gt thing which was not my intent. If there are any glaring issues that need to be resolved then the PM button should be used. Although this little bit of info you provided is kinda strange....

[Muzikman]

Well, you basically said publicly that Miscue has no clue what he is doing and should not be writing code for an emag (or any other software for that matter). I have no problems with you, but if you make statements like that, then you need to be rebutted. If this is not what you ment by what you said, maybe you should change your words as that is what it comes off as saying.

[Miscue]

Umm...If I am not mistaken it was the other way around. He knew ASM and decided to try to write code for the gun to give hims something to do in his spare time. I could be wrong, but he did graduate in a Comp Sci degree.

Correct. I learned almost nothing about programming from working on this - it truly is a trivial program in my opinion. The only thing remotely novel about it, is what it does in the amount of space.

Getting my CS degree took something I enjoyed, and made me hate it. I had nearly forgotten that I used to like doing it. The EMag software was the first "fun" software that I had made in a long time. That's what sparked the new interest that I mentioned.

[JRingold]

No Research

This is complete nonsense.

Yeah, I agree.

Here's my question; everyone says "we want 4.x". But really does anyone really know what that means? I guess my question is, what do you the user feel is "wrong" with 3.2? Or is it just that you know there is a non-released 4.x something out there so you want it?

[RRfireblade]

Yeah, I agree.

Here's my question; everyone says "we want 4.x". But really does anyone really know what that means? I guess my question is, what do you the user feel is "wrong" with 3.2? Or is it just that you know there is a non-released 4.x something out there so you want it?

IMO, there is absolutely nothing wrong with 3.2. I can easily take it right to the limits of my ability to pull trigger,just as on any other 'legally' set up marker I own...and I own ALOT of electronic markers. Most of which are very inclined to 'improve' on my ability if not carefully set up.

Any software that would be considered 'faster' than 3.2, has to be either clearly illegal or possibly,as I suspect 4.xx is..and with NO disrespect to Miscue... just over the line. I've seen people who've never broken 15bps in their life on ANY other marker take 4.xx into areas they've only dreamed about. Both in person and in vids posted on the net. It's also apparent to me after analyzing some of those vids myself, that the ROF counter does 'not' represent actual fired shots...what ever that reason may be.Whether or not it has any relation to actual trigger pulls, I have no idea of knowing or any way of verifying so I'll just have to assume probably not.

But...as with everything else...many people want what they can't have. Even if that sometimes means a higher ROF.

[bunker17]

pretty much i think what most people find wrong about 3.2 its that it doesn't have adebounce levels and 3.2 can only do like 20 in the electric mode or something like that. Icould be wrong

[GT]

Well, you basically said publicly that Miscue has no clue what he is doing and should not be writing code for an emag (or any other software for that matter). I have no problems with you, but if you make statements like that, then you need to be rebutted. If this is not what you ment by what you said, maybe you should change your words as that is what it comes off as saying.

If 3.2 is fine then why develop a new version? How many people are happy with thier 3.2? How many people have bought an emag and bought something else because it was faster?

[Muzikman]

First off what does that have to do with what you quoted me on. My feeling is that 3.2 is good enough, but for many of the people out there that need faster to keep up with the Jones, then they will go buy the gun that ramps and shoots 30bps when you pull the trigger 10.

And people do not understand "debounce" they think debounce is ramping, and it is not. Debounce is designed to take away (or allow) trigger bounce.

Debounce != shot buffering

[hitech]

I've used both, 3.2 and 4.x. Both had the bounce issue with the HES. This issue showed up in 3.2 because of shot buffering. It was possibly more pronounced in 4.x because the code was tighter (taking less time between detecting a trigger pull and firing. Maybe not. I have seen either source, so I'm guessing. However, I did converse with Miscue about the code and as a software engineer I am confident that he was very capable. It's pretty simple code, but even simple code can be done poorly.

Muz, yeah, it's amazing how little most people understand about how an electronic marker works. They need to read Bill's article!