Jump to content

daled

Members
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral
  1. oleglevsha: Thank you! That tool was able to reset the firmware in the camera even though configtool was unable to do so.
  2. Yes. I realize that the firmware is wrong. The question now it how to get it loaded given the camera's current state which I described in the post.
  3. I have a DH-IPC-HFW4300S which I unwisely attempted to upgrade using the Dahua tool "Firmware Kit for IPCPTZ". The tool reloaded the camera with some image, but not one that works and it left the camera semi-bricked. I can access the camera using Telnet and the camera does respond to port 3800. However, when I try to login using the Dahua ConfigTool, the login fails even though I know the password and can use it (with the standard prefix as described in the first post in this thread) to login via telnet. If I kill and start up /utils/upgraded from the telnet console I get the following when trying to connect from the configtool: # /utils/upgraded [libdvr] libdvr.so Build on May 22 2014 at 14:23:12. [libdvr] SVN NUM: 5830. [libdvr] ...dataBuf[0] 26, dataBuf[1] 4 [libdvr] Real fchip type is 21 [libdvr] WARN (../../src/misc/sys.c|getSystemInfo|430): get authcode error ! [libdvr] info->deviceType:IPC-HFW2200B-V2 [libdvr] devalias:IPC-HFW1200S [libdvr] armrate = 486 [libdvr] @@@@ buf = 1A03212PAU00375 UPGRADED_MSG: Can't Open /mnt/mtd/Config/passwd UPGRADED_MSG: Account not exist! The config tool login attempt fails with the message "Login overtime" which I assume means "login timeout". I think that if could just get logged in from the config tool I might be able to load a working image. I'm unable to modify the i18n files described by cctv_007 earlier in this thread because they are on a ro squashfs filesystem that cannot be modified by mounting it rw. Does anyone have a suggestion for how I can get a connection on port 3800 to try to load a different image?
  4. Did you mean why "don't" you....I wanted to control the cameras from computer software...and did not have an extra CU161.
  5. Ricksi, I'm having the exact same problem with two different CS854 cameras. I followed the 3 step reset/setup directions given to me by Panasonic support and cannot get the cameras to go into Pelco mode either. I can get them to go into Panasonic mode and can talk to them from my computer over the RS485 interface in Panasonic mode using a test program. Did you ever figure out how to get your camera to enter Pelco mode? UPDATE: I escellated a ticket with Panasonic Support. They researched the issue and reported to me that ONLY WV-CS854A or WV-CS854B cameras support Pelco mode. If the camera model number does not have the A or B designation, you will not be able to put it into Pelco mode.
×