Recent content by sina55555

I upgraded my NVR608-32-4KS2 in my office to v4 and i didn't factory reset before or after that & there is no problem.because last version of firmware is 2018build but all of 2016builds get in trouble....so, my question is why! older NVR get some problem for upgrading?

if you can get a high resolution picture with more details, there is no good reason to buy doorbell or video intercom. a high 5MP or 8MP dome camera or high resolution pin hole cameras can give you better picture and maybe it has microphone or audio in/out....

as you said this is a VTO. it means Video Intercom Outdoor, Not Camera! you can't get it instead of Doorbell camera or IP camera and on fisheye lens of doorbell cameras & video intercoms implicates that in this situations not require high resolution camera. just angel of sight is important not...

when a video intercom connects to a calling system there is no need to get a chime relay or button for bell because in sip protocol you can get more of this. but in standalone access controllers like ASI1212D i saw a bell wire and a button for it.

there are some new villa door stations that i prefer them, because they have more features and compatible with IP video intercoms. VTO1301R-W VTO2301R-P VTO2311R-WP

i Upgraded my NVR608-4KS2 from v3build 2015 to NVR6XX-4KS2_MultiLang_V4.001.0000001.1.R.200812 but don't upgraded to the latest version( NVR6XX-4KS2_MultiLang_V4.002.0000000.0.R.210727) and there are some problems after upgrading...for example don't restored from factory default and not...

the firmware structure of access controllers is sth like intercoms of dahua. and the stm chip is the MCU microcontroller for controlling modules of board

hi i have some dahua ARC2008c-g alarm controllers i got arc config in toolbox app but it doesn't appear in arc config and not discovered. i have ping to ip address of that(default:192.168.1.108) but i don't know how to manage it over network or monitor it if someone have the latest firmware of...

yes. this modkit tool can not make new crc check and also hwid is important... but i don't understand that this data signature is on whole of firmware or just one specific partition like pd-x.squashfs...

yes! incorrect cable connector can makes it not work correctly...

i don't think so that this problem is about poe injector because the main issue is on poe switch and when i tested this model with poe switch DH-PFS3006-4ET-60 by default configuration it works and ok with ethernet switch

so your vto's board is corrupt. because i used this model and there is no issue with this for poe and ethernet link

make sure your poe injector adapter works well(try other device with this injector) after that if it's ok, try vto with a small poe switch for example 4port poe switch(ex, DH-PFS3006-4ET-60 )

THANKS and how about backing up a device from shell?... for example backing up firmware or configuration....

access to ssh is not efficient when there is no way to shell :(