Proxmark3 community

b_osi

Contributor

From: Hamburg

Registered: 2018-05-01

Posts: 8

Email

[solved] [RDV4] How often is the rdv4 allowed to crash/stop working?

or: is my proxmark broken?

The effect on mine since the beginning was that it sometimes gets hot at the bottom, and crashes frequently.
In the beginning I thought, ok, it's new, there may be some issues in the software, but even after months / several updates it is not constant working.
Strangest effect was now when I added the bt add-on: first time attaching to computer by cable the whole thing got very hot.
Then running on battery, it could ran just a second, before all leds went dark...

So I had the idea: heat = high current and stumbled upon an um34c to get an idea what current I get...

Without bt add-on and without a standalone mode:
80mA when idle

1. hw tune does not always succeed
   sometimes works, sometimes ends with:
   300mA / 450mA and LED a+b stay on
   not able to react to any command anymore:

   [usb] pm3 --> hw tune
   [=] Measuring antenna characteristics, please wait...
   ....[!] Communicating with Proxmark3 device failed
   ....
   [!] No response from Proxmark3. Aborting...
   [=] Running in OFFLINE mode. Use "hw connect" to reconnect

   need to unstick from usb and stick again

   when it works i get:

   [+] LF antenna: 71.66 V - 125.00 kHz
   [+] LF antenna: 38.81 V - 134.00 kHz
   [+] LF optimal: 71.66 V - 125.00 kHz
   [+] LF antenna is OK
   
   [+] HF antenna: 43.76 V - 13.56 MHz
   [+] HF antenna is OK
   
   [+] Displaying LF tuning graph. Divisor 89 is 134khz, 95 is 125khz.

2. Sometimes when just plugging in, some led still is on and does not show up as serial device on computer
   high pitching sound and getting hot quite fast
   current 300mA
   or 200mA without 'sound'
   Thats why i disabled standalone mode, to not interfere with code by just plugging in - but that does not fix it, it sometimes does not come up completely when plugging in.

   
   

3. hf search
   Sometimes 300mA ... not stoppable by button press...LED D stays on

   
   

   [usb] pm3 --> hf 15 info u - without any card
   [!] iso15693 card select failed
   300mA - not responding to further commands

   
   

   [usb] pm3 --> hf 15 info *
   [!] No tag found
   end in 300mA and no reaction

   
   

   [usb] pm3 --> hw reset
   [=] Proxmark3 has been reset.
   does not work, current stays at 300mA

Hardware, apple powerbook
connected to powerbook usb-c with Apple USB-C Digital AV Multiport Adapter
also used different adapter, same effects

[usb] pm3 --> hw version

 [ Proxmark3 RFID instrument ]


 [ CLIENT ]
  client: RRG/Iceman
  compiled with Clang/LLVM 4.2.1 Compatible Apple LLVM 10.0.0 (clang-1000.11.45.5)

 [ PROXMARK RDV4 ]
  external flash:                  present
  smartcard reader:                present

 [ PROXMARK RDV4 Extras ]
  FPC USART for BT add-on support: present

 [ ARM ]
 bootrom: RRG/Iceman/master/45dc0fbc-dirty-unclean 2019-06-25 21:05:31
      os: RRG/Iceman/master/db572df9-dirty-unclean 2019-07-05 17:24:28

 [ FPGA ]
 LF image built for 2s30vq100 on 2019/ 4/18 at  9:35:32
 HF image built for 2s30vq100 on 2018/ 9/ 3 at 21:40:23

 [ Hardware ]
  --= uC: AT91SAM7S512 Rev B
  --= Embedded Processor: ARM7TDMI
  --= Nonvolatile Program Memory Size: 512K bytes, Used: 254522 bytes (49%) Free: 269766 bytes (51%)
  --= Second Nonvolatile Program Memory Size: None
  --= Internal SRAM Size: 64K bytes
  --= Architecture Identifier: AT91SAM7Sxx Series
  --= Nonvolatile Program Memory Type: Embedded Flash Memory

[usb] pm3 --> hw status
#db# Memory
#db#   BIGBUF_SIZE.............40000
#db#   Available memory........40000
#db# Tracing
#db#   tracing ................1
#db#   traceLen ...............0
#db# Currently loaded FPGA image
#db#   mode.................... HF image built for 2s30vq100 on 2018/ 9/ 3 at 21:40:23
#db# Flash memory
#db#   Baudrate................24 MHz
#db#   Init....................OK
#db#   Memory size.............2 mbits / 256 kb
#db#   Unique ID...............0xD567A882A7598226
#db# Smart card module (ISO 7816)
#db#   version.................v2.06
#db# LF Sampling config
#db#   [q] divisor.............95 ( 125 kHz )
#db#   [b] bps.................8
#db#   [d] decimation..........1
#db#   [a] averaging...........Yes
#db#   [t] trigger threshold...0
#db# LF T55XX config
#db#   [a] startgap............29*8 (232)
#db#   [b] writegap............17*8 (136)
#db#   [c] write_0.............15*8 (120)
#db#   [d] write_1.............47*8 (376)
#db#   [e] readgap.............15*8 (120)
#db# Transfer Speed
#db#   Sending packets to client...
#db#   Time elapsed............500ms
#db#   Bytes transferred.......297984
#db#   Transfer Speed PM3 -> Client = 595968 bytes/s
#db# Various
#db#   DBGLEVEL................1
#db#   ToSendMax...............-1
#db#   ToSendBit...............0
#db#   ToSend BUFFERSIZE.......2308
#db# Installed StandAlone Mode
#db#    No standalone mode present
#db# Flash memory dictionary loaded

Last edited by b_osi (2019-08-26 12:43:30)

iceman

Administrator

Registered: 2013-04-25

Posts: 9,468

Website

Re: [solved] [RDV4] How often is the rdv4 allowed to crash/stop working?

That sounds like a faulty device to me.  If you were a backer on KS,  email dennis.   Otherwise contact your retailer.

b_osi

Contributor

From: Hamburg

Registered: 2018-05-01

Posts: 8

Email

Re: [solved] [RDV4] How often is the rdv4 allowed to crash/stop working?

Ok, I got a replacement - completely new feeling ;-)

Some measurement from an ok working device:
idle 90mA
hf tune 100-200mA
hf search up to 300mA
lf search up to 200mA
going back to idle level after every command

blueshark loading with 300mA

iceman

Administrator

Registered: 2013-04-25

Posts: 9,468

Website

Re: [solved] [RDV4] How often is the rdv4 allowed to crash/stop working?

Good to hear!