2 Replies Latest reply on Jun 14, 2018 11:33 AM by Chris Hamner

    Bug in .NET SDK with "Tag event" option?

    Josko Bacic

      Hello!

      We use FX7500 along with C# .NET SDK but even when we use your compiled genuine .exe from SDK suite and when checking this option "Tag event" after some minute of scanning, Actv and Pwr bulbs go DIMMED-green and connection with RFID reader is lost (see screenshot).

      Sometimes we get some "Reader ExceptionEvent Reset NGE due to error type (2)" message also with disconnection event immediately afterwards!

       

      It looks like when it comes to some 1000-2000 "tag-seen events", your exe just breaks down?

      Is there some workaround on this , is this bug or?

      Regards...

       

      ADDITION: I tried with PowerSession app as well and same thing happens after some minute of reading: see the 2nd screenshot..

        • Re: Bug in .NET SDK with "Tag event" option?
          Josko Bacic

          It is fixed.  bad (too weak) power supply was to blame.

            • Re: Bug in .NET SDK with "Tag event" option?
              Chris Hamner

              This issue also happens with inadequate power from a PoE port as well.

               

              Scenario:

              FX7500 on PoE port with 12000 mW limitation.  When an RFID tag inventory was started the FX7500 stopped communicating completely (via ICMP PING / ARP, etc).

               

              FX7500 on P4 (restricted to 12000 mW)

              • Sitting idle is OK because it draws only 7200 mW
              • Running RFID inventory is NOT OK because it runs at 17000mW or higher

               

              FX7500 on P3 (restrictedto 22000 mW)

              • Sitting idle is OK
              • Running RFID inventory is OK (doesn't surpass the 22000 mW restriction)

               

               

              FX7500 running RFID tag inventory (with one antenna) - this was within the Port 3 power restriction, but surpassed the Port 4 power restriction

              snap002-crackle# show peth-port

               

               

                  Port Name     En.  AT En. Status Class Pow.(mW) Cur.(mA) Limit(mW) Prio

              --------------- ----- ------ ------ ----- -------- -------- --------- ----

              P1 External1     Up    Up     Off       0        0        0     30000  Low

              P2 External2     Up    Up     Off       0        0        0     30000  Low

              P3 FX7500        Up    Up     On        4    17700      332     22000 Crit.

              P4 Camera        Up    Up     Off       0        0        0     12000 Crit.

              P5 Spare         Up    Up     Off       0        0        0     15000 High

              P6 AP            Up    Up     Off       0        0        0     22000 Crit.

              P7 LASC          Up    Up     Off       0        0        0      6000 Crit.

               

               

              FX7500 sitting idle (not running inventory) - this was within the Port 4 power restrictions on the port so all was running well

              snap002-crackle# show peth-port

               

               

                  Port Name     En.  AT En. Status Class Pow.(mW) Cur.(mA) Limit(mW) Prio

              --------------- ----- ------ ------ ----- -------- -------- --------- ----

              P1 External1     Up    Up     Off       0        0        0     30000  Low

              P2 External2     Up    Up     Off       0        0        0     30000  Low

              P3 FX7500        Up    Up     On        4     7200      137     22000 Crit.

              P4 Camera        Up    Up     Off       0        0        0     12000 Crit.

              P5 Spare         Up    Up     Off       0        0        0     15000 High

              P6 AP            Up    Up     Off       0        0        0     22000 Crit.

              P7 LASC          Up    Up     Off       0        0        0      6000 Crit.