Software Bug?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • BetaMax
    Registered User
    • Jun 2002
    • 187

    #1

    Software Bug?

    Running the 2.4 version on my new X-Mag I got about 2 weeks ago and only used the marker 2 times and already have over 500k shots on it?

    Not that it matters. Also, I do not seem to have burst mode option on my marker either like on my 1.37 emag marker. The 1,3,6 shot burst.
    Wherever you go, there I am.
    My Webpage: http://betamax.xwarzone.com
  • ChucktheMAGician
    Back at it
    • Oct 2002
    • 1855

    #2
    My counter shot up like that after I adjusted the trigger wrong I got it fixed but the count stayed high! Does your board have the jumper installed? That would keep you from having 3 and 6 round burst, hopefully you still have 1 round burst
    Feedback from: AO,PBN

    Comment

    • Halliday
      Level 10
      • Oct 2000
      • 1655

      #3
      Just let the battery die and your counter will be back down :)


      Super Moderator at Pbreview.com

      Comment

      • rpm07
        BLACKCELL powered by AGD
        • Oct 2001
        • 931

        #4
        2.4 does not have shot burst mode.

        Comment

        • Tobe2be
          Posts: 1,000,000,000
          • Feb 2003
          • 1324

          #5
          my battery dies twice on me and the TS hansst cone anywhere. i bought my emag with barely over 23k shots and just in trigger adjustment i put another 15k. i want my TS to go down
          68/45k Flatline for sale
          Misc Parts for sale
          <--click for feedback FULL!

          Comment

          • Miscue
            Super Moderator

            • Oct 2000
            • 7105

            #6
            The problem is, that it is not too difficult for the EEPROM to become corrupt... particularly when battery is low. The microcontroller may have enough power to operate, but not enough power to correctly write to the EEPROM... which can lead to corruption. Also, low power can result in the microcontroller writing to the EEPROM even if the software did not intend to... which can also lead to corruption.

            It's not a software bug as much as it is the nature of the microcontroller and EEPROM memory. There are things that can be done to reduce the possibility of this happening, but there isn't really a way to prevent it completely with how the board is set up.

            Comment

            • PyRo
              President Bioloaf inc.
              • Dec 2000
              • 10186

              #7
              Who cares what the shot counter says...

              Comment

              Working...