how long you press the reset button and is your camera also give some cliking sound once in like a minute
Dahua ptz camera reset dh-sd50225-hni forgot password
- Thread starter Rory040
- Start date
how long you press the reset button and is your camera also give some cliking sound once in like a minute
camera is acessible through 3777...
The clicking is ithink it tries to combine color or b/w picture ....
i figured it out that i flashed the correct firmware 2.63 but later i flashed mcu file
General_SD59XXX-HN-MAIN_MCU_V2.300.0000000.10.R.170926 which has 30 kb and it is causing the problem...
my camera turns on when i cover the lens (because it respond on the light - causing the clicking sound (like it is switching between the day and night)..after covered lens camera boots fine... http 192.168.1.108...
i pushed reset buton for 1 min....
i Think this is the problem ....
i figured that i need to flash main mcu---beacuse this file is related to same camera starlight 2mp 25xzoom but bnc model ......
the new firmware 2.8 doesnt have inside components of mcu1.bin and mcu-x.bin ....i have flashed with this sd59xxxxhmain-mcu (in the screen shoot you can see the diference between two files)
i need to install the mcu1.bin and mcu-x.bin and put them in similar file like sd59xxxx-hmain-mcu (this file flashed within windows web gui without problem)...
can somebody help me with this ...
put this files from firmware 2.60 to this smallbin sd59xxxx-hmain-mcu file so i can flash it
the link for 2,60 firmware
the link for sd59xxxx-hmain-mcu file
Attachments
It seem that my problem with my camera is related to wron FIRMWARE FOR PTZ OR MCU ...
Which I read and followed on this forum...
ipcamtalk.com
Now when i flashed the camera with this MCU
The color mode is restored but the camera is spining when i move it more than two times...
This is all due to wrong MCU that was posted in the thread ...Mine camera would be working now if it wasn`t for that ...You have to flash two files...
Now what ...What is the wright MCU file I have them both in the FIRMWARE which is LOWER version that i have ???
now what i have to downgrade the camera so the firmware in the package could install the mc1.img nad mc-x.img in them..
Here are the firmwares signed...
Which I read and followed on this forum...
SD59225U-HNI latest new firmware.
Hi Guys Dahua released the newer firmware for the ptz 5 series. You can install on these cams. SD59430U-HNI SD59225U-HNI SD59230U-HNI SD52C225U-HNI SD52C230U-HNI SD50225U-HNI SD50230U-HNI PAL and NTSC is the main firmware for the camera(Download what your country use),PTZ function one is for...
Now when i flashed the camera with this MCU
The color mode is restored but the camera is spining when i move it more than two times...
This is all due to wrong MCU that was posted in the thread ...Mine camera would be working now if it wasn`t for that ...You have to flash two files...
Now what ...What is the wright MCU file I have them both in the FIRMWARE which is LOWER version that i have ???
now what i have to downgrade the camera so the firmware in the package could install the mc1.img nad mc-x.img in them..
Here are the firmwares signed...
Rory install one of these firwmware if you see the cam in config tool....
I have also downgraded on 2.422 then web gui was scrabled ( i preformed reset of one minute holding the reset button)
then i upgraded to version 2.60
if you want to you can go higher to 2.80 (on this version the bootloader updates to 2019)
When i was downgrade-ing from 2.8 version to 2.442 in boot loader(was 2019)
i needed to flash the bootloader to version of the firmware
do not update bootloader if you do not have to
link to firmwares
drive.google.com
I have also downgraded on 2.422 then web gui was scrabled ( i preformed reset of one minute holding the reset button)
then i upgraded to version 2.60
if you want to you can go higher to 2.80 (on this version the bootloader updates to 2019)
When i was downgrade-ing from 2.8 version to 2.442 in boot loader(was 2019)
i needed to flash the bootloader to version of the firmware
do not update bootloader if you do not have to
link to firmwares
Firmware - Google Drive
drive.google.com
Attachments
30kb bon is the ptz firmware or main mcu
You need to flash the 25 mb version file or something...
Ptz firmware is not so important it controls the ptz movement...
Try flashing with version 2.600
I have flashed firmware by serial connwction,
Got i to the bootloader through putty,
Flashed firmware 2.42 over 2.80 that was on camera
I got error like canot write bootlog...
After that my camera was going i to boot loop.
Again i made conection over serial by putty...
Flashed the bootloader and then the rest of the comands... (bootloader is file name dhboot.img)
When my camera started into gui interface by internet explorer...
The letters were scrumbled, so i flashed with firmware 2.60 (upgraded the software)
And it was fine...
Try upgrading software by config tool if you can see the camera on the network...
I conected rx from usb to tx on camera
And tx on usb to rx on camera
Gnd to gnd on camera
And 3.3 usb to 3.3v on camera
Remeber the big files od 25 mb or so are the main firmware files needed to upgrade the camera or reflash it, the small files are the ones to update or reflash the main control unit or the PTZ controls ....
when you flash the camera with the firmware 2.80 it is reviewed in the upgrade tab - software version 2.80
web version changes to new one
onvif version changes to new one
and the ptz software remains the same if you didnt flash it or here is the newest mcu or PTZ software version file that ANDY (from this forum) gave me
when you flash the camera with the firmware 2.80 it is reviewed in the upgrade tab - software version 2.80
web version changes to new one
onvif version changes to new one
and the ptz software remains the same if you didnt flash it or here is the newest mcu or PTZ software version file that ANDY (from this forum) gave me
Try updateing little by version 2.60
then 2.63 and 2.80 if you don`t like it....
you can always flash the main mcu file over any version of the main software is it 2.42, 2.60, 2.63 or 2.80..
I just had a problem that i flashed with the main mcu version of 59xxx camera version beacuse it is not my model of camera (my model is same as yours (dh-sd50255u-hni)
type if you had any problems
yes but before i did see the camera and i flashed before the 30 kb file and after that i did flash the 2.40 version and it was successfully flashed but now the only thing i can do i ping the camera.
port 3800 is not open any more even same as pussty port is also closed
port 3800 is not open any more even same as pussty port is also closed
It is like that on some camera that you have to connect rx (recive conection) to tx (transmit connection) and tx(transmit) to rx(recive)..
I tried to rx to rx and ty to tx i didnt recive any info by putty...
There is also a thrrad on this forum that says that you can flash dahua cams by 3 ways
1. Normal from config tool of web browser via GUI ( graphic user interface)
2. Conecting camera to tx, rx,gnd, vcc 3.3
Serial to ttl usb adapter
(THIS WAY YOU CAN CHANGE THE
Ip adress on camera where the camera looks for server that holds firmware files(your computer)
Default is 192.168.1.1 if your conputer adress is 192.168.1.4 (you change ip adress of server on camera 192.168.1.4)
This way you can type printenv see the information on camera.
Execute some comands that are predifined in camera like
Dc=
Dr=
Dw=
You see them when you type printenv
Run dc
Run dr
Run dw
Execute that programs...
3. Way is by scipt were this comands are entered on txt file.
You set your network adapter acording to instruction on that thread and execute those bat files
Commands.bat
Console.bat
server.bat
Camera boots up and looks for ip server (that is your computer set to ip adress 192.168.1.1 and another ip adress 192.168.254.254) if there is a upgrade(some numbers).txt
Looks for upgrade and runs commands that are set in comands.txt file
(By this way you dont need usb to ttl adapter...because you dont nees to type comands to upgrade - downgrade firmware manually (by typeing comands)
The script does this for you, and protocol on camera (when camera boots up, it looks up for upgrade file)
The main thing is that you can see your camera on network.
I was having a problem that i could not ping my camera of see it on network...
That was a problem because i could not upgrade my camera any way ...because transmition of firmware is done by network cable....
Not usb to tll adapter ( it is only a tool to see camera parameters and manually input or set comands)
I tried to rx to rx and ty to tx i didnt recive any info by putty...
There is also a thrrad on this forum that says that you can flash dahua cams by 3 ways
1. Normal from config tool of web browser via GUI ( graphic user interface)
2. Conecting camera to tx, rx,gnd, vcc 3.3
Serial to ttl usb adapter
(THIS WAY YOU CAN CHANGE THE
Ip adress on camera where the camera looks for server that holds firmware files(your computer)
Default is 192.168.1.1 if your conputer adress is 192.168.1.4 (you change ip adress of server on camera 192.168.1.4)
This way you can type printenv see the information on camera.
Execute some comands that are predifined in camera like
Dc=
Dr=
Dw=
You see them when you type printenv
Run dc
Run dr
Run dw
Execute that programs...
3. Way is by scipt were this comands are entered on txt file.
You set your network adapter acording to instruction on that thread and execute those bat files
Commands.bat
Console.bat
server.bat
Camera boots up and looks for ip server (that is your computer set to ip adress 192.168.1.1 and another ip adress 192.168.254.254) if there is a upgrade(some numbers).txt
Looks for upgrade and runs commands that are set in comands.txt file
(By this way you dont need usb to ttl adapter...because you dont nees to type comands to upgrade - downgrade firmware manually (by typeing comands)
The script does this for you, and protocol on camera (when camera boots up, it looks up for upgrade file)
The main thing is that you can see your camera on network.
I was having a problem that i could not ping my camera of see it on network...
That was a problem because i could not upgrade my camera any way ...because transmition of firmware is done by network cable....
Not usb to tll adapter ( it is only a tool to see camera parameters and manually input or set comands)
When you enter the camera through serial by usb adapter
There you can manually flash firmware by executing commands
Run dc
Run dw...etc...
But if you reset enveromental table meaning you setting of the camera as i did by mistacke...
Why? Because i tought it woukd bringmy network up and i would be able to flash the firmware....
My camera latter had only ip adress mac adress (which wasnt the one from the camera sticker on the box)
My s/n was the sam as the mac adress and my camwra was not named dh-sd50255u-hni but ca20225u
There you can manually flash firmware by executing commands
Run dc
Run dw...etc...
But if you reset enveromental table meaning you setting of the camera as i did by mistacke...
Why? Because i tought it woukd bringmy network up and i would be able to flash the firmware....
My camera latter had only ip adress mac adress (which wasnt the one from the camera sticker on the box)
My s/n was the sam as the mac adress and my camwra was not named dh-sd50255u-hni but ca20225u
"CA-HZ2025U:01:03:04:4A:17:14:01:0A:01:01:04:258:00:00:00:04:00:01:00:00:400" -------->this is my ID
mac adress on sticker of the camera
3c:ef:8c:e5:08:ce
s/n on the sticker of the camera
2J00122PAM0xxxxx on camera MCU-modul
Serial number on smartpss to connect p2p
2K00215PAxxxxxx
(mine printenv)
printenv
bootargs=mem=256M console=ttyS0,115200 root=/dev/mtdblock7 rootfstype=squashfs
bootcmd=kload 0x82000000; bootm 0x82000000
bootdelay=1
baudrate=115200
ethaddr=00:12:34:56:78:9A
ipaddr=192.168.1.108
serverip=192.168.1.1
gatewayip=192.168.1.1
netmask=255.255.255.0
bootfile="uImage"
wifiaddr=00:12:34:56:78:91 (this is the same on all devices or some)
mp_autotest=0
ID=000000000000000000
da=tftp 0x82000000 dhboot.bin.img; flwrite;nand protect off;tftp dhboot-min.bin.img;flwrite
dr=tftp 0x82000000 romfs-x.squashfs.img; flwrite
dk=tftp 0x82000000 kernel.img; flwrite
du=tftp 0x82000000 user-x.squashfs.img; flwrite
dw=tftp 0x82000000 web-x.squashfs.img; flwrite
dp=tftp 0x82000000 partition-x.cramfs.img;flwrite
dc=tftp 0x82000000 custom-x.squashfs.img; flwrite
up=tftp 0x82000000 update.img; flwrite
tk=tftp 0x82000000 uImage; bootm
dh_keyboard=1
appauto=1
sysbackup=1
loglevel=4
pd=tftp 0x82000000 pd-x.squashfs.img; flwrite
HWID=CA-HZ2025U:01:03:04:4A:17:14:01:0A:01:01:04:258:00:00:00:04:00:01:00:00:400 (the id I entered manually)
ethact=gmac
stdin=serial
stdout=serial
stderr=serial
ver=U-Boot 2010.06-svn7012 (Aug 27 2019 - 17:12:23)
Environment size: 1070/131068 bytes
Someone else printenv)
bootdelay=1
baudrate=115200
ipaddr=192.168.1.108
serverip=192.168.1.1
gatewayip=192.168.1.1
netmask=255.255.255.0
bootfile="uImage"
wifiaddr=00:12:34:56:78:91
da=tftp 0x82000000 dhboot.bin.img; flwrite;tftp dhboot-min.bin.img;flwrite
dr=tftp 0x82000000 romfs-x.squashfs.img; flwrite
dk=tftp 0x82000000 kernel.img; flwrite
du=tftp 0x82000000 user-x.squashfs.img; flwrite
dw=tftp 0x82000000 web-x.squashfs.img; flwrite
dp=tftp 0x82000000 partition-x.cramfs.img;flwrite
dc=tftp 0x82000000 custom-x.squashfs.img; flwrite
up=tftp 0x82000000 update.img; flwrite
tk=tftp 0x82000000 uImage; bootm
dh_keyboard=1
loglevel=4
pd=tftp 0x82000000 pd-x.squashfs.img; flwrite
ethact=gmac
BSN=3E0616FPAX03953 (Serial number of the camera)
HWID=IPC-HDW4431C:01:02:05:23:1A:00:01:0A:01:00:00:258:00:00:00:00:00:01:00:00:100
devalias=IPC-HDW4431C-A-V2 (device alias - name of the camera as it is showned on dahua gui)
ID=3F024CBPAA01072 (ID of the camera in system settings - near the clock setting --- you can change that manually from gui)
ethaddr=E0:50:8B:B2:A6:24 (MAC adress of camera)
filesize=27E040
fileaddr=82000000
appauto=1
bootargs=mem=87M console=ttyS0,115200 root=/dev/mtdblock7 rootfstype=squashfs
stdin=serial
stdout=serial
stderr=serial
verify=n
ver=U-Boot 2010.06-svn3638 (Feb 28 2017 - 04:38:07)
Environment size: 1115/131068 bytes
set devalias (YOU CAN PUT THE NAME OF THE CAMERA AS IT IS SHOWNED ON THE SYSTEM DISLAY)
set BSN (SERIAL NUMBER OF THE CAMERA)
set ID (NAME OF THE CAMERA BY THE TIME SETTINGS IN DAHUA GUI - CAN BE CHANGED FROM GUI - I PUT THE SAME AS THE SERIAL NUMBER OF THE CAMERA)
mac (NEW MAC ADRESS)
hwid (DEVICE HARDWARE ID - NEEDED TO INSTALL CORRECT FIRMWARE ON THE DEVICE)
mac adress on sticker of the camera
3c:ef:8c:e5:08:ce
s/n on the sticker of the camera
2J00122PAM0xxxxx on camera MCU-modul
Serial number on smartpss to connect p2p
2K00215PAxxxxxx
(mine printenv)
printenv
bootargs=mem=256M console=ttyS0,115200 root=/dev/mtdblock7 rootfstype=squashfs
bootcmd=kload 0x82000000; bootm 0x82000000
bootdelay=1
baudrate=115200
ethaddr=00:12:34:56:78:9A
ipaddr=192.168.1.108
serverip=192.168.1.1
gatewayip=192.168.1.1
netmask=255.255.255.0
bootfile="uImage"
wifiaddr=00:12:34:56:78:91 (this is the same on all devices or some)
mp_autotest=0
ID=000000000000000000
da=tftp 0x82000000 dhboot.bin.img; flwrite;nand protect off;tftp dhboot-min.bin.img;flwrite
dr=tftp 0x82000000 romfs-x.squashfs.img; flwrite
dk=tftp 0x82000000 kernel.img; flwrite
du=tftp 0x82000000 user-x.squashfs.img; flwrite
dw=tftp 0x82000000 web-x.squashfs.img; flwrite
dp=tftp 0x82000000 partition-x.cramfs.img;flwrite
dc=tftp 0x82000000 custom-x.squashfs.img; flwrite
up=tftp 0x82000000 update.img; flwrite
tk=tftp 0x82000000 uImage; bootm
dh_keyboard=1
appauto=1
sysbackup=1
loglevel=4
pd=tftp 0x82000000 pd-x.squashfs.img; flwrite
HWID=CA-HZ2025U:01:03:04:4A:17:14:01:0A:01:01:04:258:00:00:00:04:00:01:00:00:400 (the id I entered manually)
ethact=gmac
stdin=serial
stdout=serial
stderr=serial
ver=U-Boot 2010.06-svn7012 (Aug 27 2019 - 17:12:23)
Environment size: 1070/131068 bytes
Someone else printenv)
bootcmd=kload 0x82000000; bootm 0x82000000
bootdelay=1
baudrate=115200
ipaddr=192.168.1.108
serverip=192.168.1.1
gatewayip=192.168.1.1
netmask=255.255.255.0
bootfile="uImage"
wifiaddr=00:12:34:56:78:91
da=tftp 0x82000000 dhboot.bin.img; flwrite;tftp dhboot-min.bin.img;flwrite
dr=tftp 0x82000000 romfs-x.squashfs.img; flwrite
dk=tftp 0x82000000 kernel.img; flwrite
du=tftp 0x82000000 user-x.squashfs.img; flwrite
dw=tftp 0x82000000 web-x.squashfs.img; flwrite
dp=tftp 0x82000000 partition-x.cramfs.img;flwrite
dc=tftp 0x82000000 custom-x.squashfs.img; flwrite
up=tftp 0x82000000 update.img; flwrite
tk=tftp 0x82000000 uImage; bootm
dh_keyboard=1
loglevel=4
pd=tftp 0x82000000 pd-x.squashfs.img; flwrite
ethact=gmac
BSN=3E0616FPAX03953 (Serial number of the camera)
HWID=IPC-HDW4431C:01:02:05:23:1A:00:01:0A:01:00:00:258:00:00:00:00:00:01:00:00:100
devalias=IPC-HDW4431C-A-V2 (device alias - name of the camera as it is showned on dahua gui)
ID=3F024CBPAA01072 (ID of the camera in system settings - near the clock setting --- you can change that manually from gui)
ethaddr=E0:50:8B:B2:A6:24 (MAC adress of camera)
filesize=27E040
fileaddr=82000000
appauto=1
bootargs=mem=87M console=ttyS0,115200 root=/dev/mtdblock7 rootfstype=squashfs
stdin=serial
stdout=serial
stderr=serial
verify=n
ver=U-Boot 2010.06-svn3638 (Feb 28 2017 - 04:38:07)
Environment size: 1115/131068 bytes
set devalias (YOU CAN PUT THE NAME OF THE CAMERA AS IT IS SHOWNED ON THE SYSTEM DISLAY)
set BSN (SERIAL NUMBER OF THE CAMERA)
set ID (NAME OF THE CAMERA BY THE TIME SETTINGS IN DAHUA GUI - CAN BE CHANGED FROM GUI - I PUT THE SAME AS THE SERIAL NUMBER OF THE CAMERA)
mac (NEW MAC ADRESS)
hwid (DEVICE HARDWARE ID - NEEDED TO INSTALL CORRECT FIRMWARE ON THE DEVICE)