AO: We are back from the dead... again! After an 18 day outage, we are finally alive and well. Who knew how complicated updating software/databases from 2008 would be. I still have alot of tweaks to make, but my main goal was getting everything patched and updated to 2026.
Vbulletin 6 has changed alot since 2008 so we will have a ton of new features to dig into.
Luckily I have no plans after work tonight and tomorrow night so I will have plenty of time to get them all shipped by Wednesday. I didn't expect them until wednesday so I'll get BETA 1.6 emailed out to everyone by Friday, which should be before you actually recieve the programmers.
I ordered 50 and I have 36 still available so if you want one get it now because I will be posting them on ebay by the end of the week.
I was working on BETA 1.6 again this weekend and I've added the one thing that was holding me back from an official release...
BETA 1.6 now checks the values read in from the EEPROM and if they are out of normal range (AKA corrupted) it will automaticly reset them to a default value. At the moment I have it so that each value is checked individually and reset individually, I was thinking about it on the way to work this morning and I don't think that is the best approach because there is no way to tell if something has been reset other than flipping through the menu's and trying to remember what you had it set to. I'm going to change it so that if one value is reset they all get resetincluding the display brightness... that way if your values get reset you will be able to tell because your display will be on the dimmest setting. I know if you are actually using the dimmest brightness setting that you wouldn't be able to tell but I don't think most people will use that.
What do you guys think? Is that a good way of doing it?
I thought of doing that but I can't get any of my three X-Mags to corrupt data when I try. So for now I am just going to rely on resetting the values to defaults. If any of my BETA testers or future users complain about having a corruption problem I will change the code to add a miltibuffer read/write to the EEPROM. Otherwise I'll leave it how I have it since what I have takes less code space.
Luckily I have no plans after work tonight and tomorrow night so I will have plenty of time to get them all shipped by Wednesday. I didn't expect them until wednesday so I'll get BETA 1.6 emailed out to everyone by Friday, which should be before you actually recieve the programmers.
I ordered 50 and I have 36 still available so if you want one get it now because I will be posting them on ebay by the end of the week.
Dammit! I just knocked my Guiness over in joy.
Okay, not really, but I'm thrilled! Thanks again for all your hard work.
man im speechless....and guess what board my halo has....hmm i wonder how fast this cheetah board really is..should we find out?? heheeh one things for sure..as for my warp halo set up?? this is gonna be gun....
I can't wait, me and the boys are heading out to castle conquest at EMR, in a few weeks and I am gonna love to see the looks on people's faces when my emag is ripping'em up!!!! Thanks again Lorne, you ARE THE MAN !!!!
Will you be sending an updated xmod to all your current testers too?
For now keep using BETA 1.5 and as soon as I fix the low battery message I will release BETA 1.6. Don't worry it will be soon I'm sure it's a small problem I just have to stop making programmers long enough to find it.
Alright guys, I've finally finished making all your cables and packaging everything up. I'm sorry it all didn't ship on Wednesday like I said. I slightly underestimated how long it would take me to make everything. It will be shipped tomorrow morning.
Just to let you know, I personally tested each and every programmer and flash cable by flashing BETA 1.6 to my gun before I packaged them up, so I can garuntee you that unless they get smashed in the mail they all work.
I've also fixed the low battery message not appearing when it was supposed to and that means that BETA 1.6 is ready for release. Once I modify the manual I will email everyone the Flash and new manual. Tomorrow and Saturday I will work like mad to get the manual modified to include the instructions for how to use the ICProg to Flash your guns. It is much different from the other two programmers and also about 300% faster. The IcProg takes only 7sec to erase, program, and verify the chip as opposed to the AVRISP and STK500 which both take about 21sec.
Here's another interesting fact... I have yet to actually fire a gun with my own software with either paint or air. I have been quite broke lately and everything I've made so far has been invested into tools that will help me make the software better. That and I had to buy 2 new mainboards because I managed to fry 2 of them... Sparks and smoke... Not good. Don't worry though you're in no danger of that just don't use a variable DC power supply to power your gun while you're trying to flash it. For testing it works great though. Also Don't connect your battery backwards either I also managed to Fry my ACE board doing that. If anyone else did do that and their ACE board is not working I did manage to fix mine by replacing the transistor. I ordered 10 of them from digikey. The way to tell if it's the transistor that's bad is to smell it. If it smells like burnt electronics I can most likely fix it. Long story short I plan on going to play this Sunday and I am excited to see what I can do.
Comment