PTZ1A225U-IRA-N 2MP 25x Starlight

Is anyone else using a microSD in this camera?

I have one in mine and it's been working flawlessly for weeks, but the last two days I've had an issue where the stream to BI works perfectly but the web interface isn't available on the camera until it's rebooted by disabling & re-enabling the switch port.

I'm on firmware 2.622.0000000.5.R.E4.2512.9A.NR, Build Date: 2017-12-28

The video stream works fine to Blue Iris and the camera responds to pings, but the web interface is unavailable.

I've enabled syslog so I can see events off camera and I've noticed that the camera throws a Disk Error followed by a removal and add event.upload_2018-7-23_20-19-46.png

There are a few options I guess:
  1. The microSD isn't liking something - it's a brand new Samsung Evo+ 128GB card direct from Amazon which tested fine in h2testw.
  2. The microSD is faulty - usually they toggle entirely read only or just become unreadable in this circumstance though.
  3. It's a bug in this firmware version.
  4. It's temperature related and something is crashing.
  5. It's a camera HW fault.
I've formatted the card and enabled SSH to try and give more of an idea for troubleshooting.

I've had the temperature display turned off but will turn it back on in case that gives any hints as to what is going on.
 
OK the web interface has gone again today and I noticed the 59225 on the latest firmware also showed the same problem.

As mentioned before I enabled ssh and I was still able to connect via ssh when the http interface is not responding and some sample output is below in the hopes it may be of some use for the Dahua engineers - it suggests that there are no network errors and that it does have a microSD.

Code: 
#gethwid



[OSA-APP] OSA Build on Dec 28 2017 at 17:23:19.
[OSA-APP] SVN NUM: 11764.

[libpdi] libpdi.so Build on Dec 28 2017 at 17:28:27.
[libpdi] SVN NUM: 44149.
[libpdi] PDI product has 1 configs!!!
[libpdi] PDI product Init OK!
[libpdi] PDI hwid Get OK!
[libpdi] PDI run in gethwid
[libpdi] WARN  : TwoEyesCom Dev not exists,status = -1
[libpdi] partionNum=15
[libpdi] Get fpga upgrade cfg failed, use default
18:48:52|[pdc] The cmd 3221510146 is invalid
[libpdi] Get flash total size failed.
18:48:52|[pdc] The cmd 3221510149 is invalid
[libpdi] Get bootsupportswitchpart failed.
[libpdi] Support backup partition !!!
[libpdi]  Flashtype = 0x4,patSize = 0x100000,rwSize = 0x800,ersSize = 0x20000
[libpdi] gFlashCtrlObj.isSupportSwitchPart:0
[libpdi] gFlashCtrlObj.bootFromBack:0
[libpdi] gFlashCtrlObj.bootVersion:2
[libpdi] WARN  : Heat Dev not exists,status = -1
[libpdi] WARN  : Device has no crypt chip!
[libpdi] phyaddr= 0x8fffe000, memLen= 0x2000
18:48:52|[pdc] Both of Chief and Backup File CRC check OK!
 [libpdi] CreatePartionTab:hwid fd=13
Fail to get env hwidEx!
[libpdi] can't find commLen cfg
[libpdi] PDI run in gethwid
[libpdi] PDI_eventInit Wrapper OK!!!
[libpdi] run with no coprocessor!


[Systools]: Build on Dec 28 2017 at 17:29:02.
[Systools]:SVN NUM: 36048.
the usage: gethwid type!
       productGetName        = 0
       HWID_VERSION            = 1
       CATEGORY            = 2
       SUB_CATEGORY            = 3
       FVIDEO_CHIP            = 4
       DSP_CHIP            = 5
       BVIDEO_CHIP            = 6
       VIDEO_CHANNEL            = 7
       ANALOG_AUDIO_MODE        = 8
       AUDIO_IN_CHANNEL        = 9
       AUDIO_OUT_CHANNEL        = 10
       STORE_INTERFACE            = 11
       CPU_COUNT            = 12
       ALARM_MODE            = 13
       WIRELESS_INTERFACE        = 14
       HD_ENCODE            = 15
       VD_INTERFACE            = 16
       NET_INTERFACE            = 17
       INTE_ANALYSE            = 18
       HD_VERSION            = 19
       VIDEO_STAND            = 20
       HAS_SD_CARD            = 21
       PHY_MEMSIZE            = 22
system error
#diagnose 1



          CPU0      
 35:   22913842       GIC  timer
 39:          0       GIC  RTC Alarm
 42:     694720       GIC  uart-pl011
 52:    1300913       GIC  hi_mci
 53:          0       GIC  ehci_hcd:usb1
 57:   28515950       GIC  gmac0
 65:          0       GIC  VOU Interrupt
 66:          0       GIC  mipi int
 67:   22911610       GIC  ISP, VIU
 68:    5727684       GIC  VPSS0
 69:          1       GIC  tde_osr_isr
 70:    8037580       GIC  VGS0
 71:   11455494       GIC  AIO Interrupt
 72:    3436372       GIC  VEDU_0
 73:          0       GIC  JPEGU_0
 75:          0       GIC  HEVCU_0
 76:          0       GIC  VDA
 77:          0       GIC  IVE
 79:          0       GIC  Gpio_irq:Group0
 80:          0       GIC  Gpio_irq:Group1
 81:          0       GIC  Gpio_irq:Group2
 82:        371       GIC  Gpio_irq:Group3
 83:          0       GIC  Gpio_irq:Group4
 84:          0       GIC  Gpio_irq:Group5
 85:          0       GIC  Gpio_irq:Group6
 86:          0       GIC  Gpio_irq:Group7
 87:          0       GIC  Gpio_irq:Group8
Err:          0
#diagnose 2

MemTotal:         254124 kB
MemFree:          142452 kB
Buffers:            3360 kB
Cached:            24236 kB
SwapCached:            0 kB
Active:            49556 kB
Inactive:          23880 kB
Active(anon):      45984 kB
Inactive(anon):     4776 kB
Active(file):       3572 kB
Inactive(file):    19104 kB
Unevictable:           0 kB
Mlocked:               0 kB
SwapTotal:             0 kB
SwapFree:              0 kB
Dirty:                 0 kB
Writeback:             0 kB
AnonPages:         45860 kB
Mapped:            20952 kB
Shmem:              4920 kB
Slab:              19476 kB
SReclaimable:      13364 kB
SUnreclaim:         6112 kB
KernelStack:        1408 kB
PageTables:          972 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:      127060 kB
Committed_AS:    1229132 kB
VmallocTotal:     761856 kB
VmallocUsed:      340256 kB
VmallocChunk:     350012 kB
#diagnose 3

Character devices:
  1 mem
  4 /dev/vc/0
  4 tty
  5 /dev/tty
  5 /dev/console
  5 /dev/ptmx
  5 threads
  7 vcs
 10 misc
 13 input
 21 sg
 29 fb
 77 ivf
 89 i2c
 90 mtd
108 ppp
128 ptm
136 pts
180 usb
189 usb_device
204 ttyAMA
218 himedia
233 len_drv
234 senDev
235 pdcMem
236 pdcRecord
237 pdcSramFile
238 pdcMisc
239 pdcIris
240 pdcAdc
241 pdcWdt
242 pdcSmartIR
243 pdcRtc
244 pdcIRCut
245 pdcHwid
246 pdcPartion
247 binder
248 binderNS
249 binderSR
250 logDev
251 ubi2
252 ubi1
253 ubi0
254 bsg

Block devices:
259 blkext
  8 sd
 31 mtdblock
 65 sd
 66 sd
 67 sd
 68 sd
 69 sd
 70 sd
 71 sd
128 sd
129 sd
130 sd
131 sd
132 sd
133 sd
134 sd
135 sd
179 mmc
#diagnose 4

Inter-|   Receive                                                |  Transmit
 face |bytes    packets errs drop fifo frame compressed multicast|bytes    packets errs drop fifo colls carrier compressed
   lo:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
  sit0:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
  eth0: 3167691280 64718312    0 132990    0     0          0         0 2557680728 8095092    0    0    0     0       0          0

#diagnose 5

229155.29 139591.81
#diagnose 6

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.0.55    0.0.0.0         UG    0      0        0 eth0
192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0

#gethwid 21



[OSA-APP] OSA Build on Dec 28 2017 at 17:23:19.
[OSA-APP] SVN NUM: 11764.

[libpdi] libpdi.so Build on Dec 28 2017 at 17:28:27.
[libpdi] SVN NUM: 44149.
[libpdi] PDI product has 1 configs!!!
[libpdi] PDI product Init OK!
[libpdi] PDI hwid Get OK!
[libpdi] PDI run in gethwid
[libpdi] WARN  : TwoEyesCom Dev not exists,status = -1
[libpdi] partionNum=15
[libpdi] Get fpga upgrade cfg failed, use default
18:55:38|[pdc] The cmd 3221510146 is invalid
[libpdi] Get flash total size failed.
18:55:38|[pdc] The cmd 3221510149 is invalid
[libpdi] Get bootsupportswitchpart failed.
[libpdi] Support backup partition !!!
[libpdi]  Flashtype = 0x4,patSize = 0x100000,rwSize = 0x800,ersSize = 0x20000
[libpdi] gFlashCtrlObj.isSupportSwitchPart:0
[libpdi] gFlashCtrlObj.bootFromBack:0
[libpdi] gFlashCtrlObj.bootVersion:2
[libpdi] WARN  : Heat Dev not exists,status = -1
[libpdi] WARN  : Device has no crypt chip!
[libpdi] phyaddr= 0x8fffe000, memLen= 0x2000
18:55:38|[pdc] Both of Chief and Backup File CRC check OK!
 [libpdi] CreatePartionTab:hwid fd=13
Fail to get env hwidEx!
[libpdi] can't find commLen cfg
[libpdi] PDI run in gethwid
[libpdi] PDI_eventInit Wrapper OK!!!
[libpdi] run with no coprocessor!


[Systools]: Build on Dec 28 2017 at 17:29:02.
[Systools]:SVN NUM: 36048.

18:55:38|[libpdi] >-------getSystemInfo------->
Fail to get env dvname!
Fail to get env devOEM!
Fail to get env authcode!
18:55:38|[libpdi] Get authcode error
18:55:38|[libpdi]  deviceType:         PTZ1A225U-IRA-N
18:55:38|[libpdi]  processorType:      23
18:55:38|[libpdi]  hardwareVersion:    1.00
18:55:38|[libpdi]  appAutoStart:       1
18:55:38|[libpdi]  serialNumber:       4C0743FPAJ1644A
18:55:38|[libpdi]  deviceClass:        SD
18:55:39|[libpdi]  noPtz:              0
18:55:39|[libpdi]  noSdCard:           0
18:55:39|[libpdi]  noRTC:              0
18:55:39|[libpdi]  bandWidth:          80
18:55:39|[libpdi] <-------getSystemInfo-------<
                hasSdcard == 1
 
When running the getDateInfo command it seems the camera is set a month in advance (ie it says it's 26 August 2018) - it's configured to use NTP and the video stream itself shows the correct date.

From further reading it sounds like the gateDateInfo command returning the wrong date is pretty standard - weird though.
 
Last edited:
Yeah I thought the getDateInfo bug was funny when I found it. I guess someone forgot how arrays are indexed.

Is there anything else hitting your cameras on your network?
If you're on the same LAN as most dahua cameras you can crash the webserver and/or knock out the video feed with malformed http requests
 
  • Like
Reactions: reverend
There's nothing out of the ordinary - syslog shows the only web logins and logouts as from my Chromebook and ONVIF from Blue Iris and in terms of other noise a quick Wireshark doesn't show anything dodgy.

I've got a feeling this one is due to the microSD causing something with the December firmware - it's a genuine Samsung Evo Plus 128GB card from Amazon which tested fine in h2testw.

I just toggled POE+ to restart the camera and it showed the card as being full but only showed around 12 hours of video (usually there's more than 24 hours on a card that size).

The older EOS firmwares used to apply to the 59225 and this camera so there's a chance this would work with the newer June 18 firmware Andy posted but I'll wait for confirmation from Dahua.

Temperature wise the camera showed 24c when the video stopped - it peaked at 45c yesterday looking at the off camera motion clips stored over in Blue Iris so it's not like it should have been a heat issue causing it to barf.

I've formatted the card again and gone back to the November 17 firmware to see how that goes.
 
OK it's still losing the web interface on the November 17 firmware.

I took a gamble as as the older main firmwares (NOT the PTZ MCU) for this camera were the same as the 59225 I installed the June 2018 firmware for the 59225 and it's upgraded fine with all functionality intact. Again just to clarify just the main PAL firmware was used - not the PTZ MCU as they are different.

I've also enabled debug logging on the switch now (just in case that reports any weird errors just before the camera web interface goes non responsive).

I've got to admit I am starting to wonder if it's the camera not liking the Samsung Evo+ 128GB card - for now to test a theory I've reformatted the card and disabled constant recording for now and will see if the web interface stays up longer and if any more disk errors are logged.
 
You keep saying that you suspect the sd card, but you're only focusing on the firmware versions. Why not take out the sd card and see what that does? If that solves the problem maybe try another sd card..
 
Kameraad said:
You keep saying that you suspect the sd card, but you're only focusing on the firmware versions. Why not take out the sd card and see what that does? If that solves the problem maybe try another sd card..
Click to expand...
Unfortunately it's 14m up and I've got a dodgy shoulder at the moment so just trying everything else I can first :)
 
Would you guys recommend this over the SD59230U-HNI?

Pricing aside, is one better then the other?

Thanks!
 
ssean said:
Would you guys recommend this over the SD59230U-HNI?

Pricing aside, is one better then the other?

Thanks!
Click to expand...
It depends what you want out of it really - if you need it to be able to look straight down then the SD59230U-HNI or another zoom variant of that is best, whereas if you want the ability to look straight up at the night sky this would be better.
 
After using the PTZ1A225U-IRA-N for a while would you recommend this model? I like the mounting style, I am thinking of mounting it under the eave of my house hanging down and I'm not thrilled with the foot long pendant mounting hardware or the huge corner bracket used for the other models like the SD59230U-HNI. Thanks.
 
looney2ns said:
Are you still happy with this cam @Parley ?
Click to expand...

@looney2ns - I am very happy with how mine works. Even the auto tracking works pretty well in my environment. I don't use the internal IR, but instead have a couple of IR lights positioned to light up the immediate areas it covers. One thing I like is I could position it up looking at the sky, to catch some of the Perseid meteor shower. In color mode it worked well, with other exposure settings adjusted accordingly.
 
  • Like
Reactions: EMPIRETECANDY and looney2ns
Hi guys,

Just got my camera and have a couple of questions. I have set to use auto tracking. It works but after tracking something, the camera would point to the sky and then go back trying to track. Second what is the best exposure setting to still have the camera display color videos ?

Thanks
 
Also, anyone successfully updated to the latest 2018 firmware yet ? if so which version ?

Thanks!
 
You must log in or register to reply here.
Top Bottom