DS-2CD2347G1-LU OEM software

xethax

n3wb
Aug 30, 2020
10
1
Netherlands
Goodmorning,

I have 2 Hikvision OEM camera's and my question is how do i update/upgrade these ones. (they are OEM)
The cameras are DS-2CD2347G1-LU and DS-2CD2385FWD-I.

Want to update the Colorvu to V5.6.2. build 200407 so i can use Led events. (led while only go on when there is a detection of motion)
 
I have 2 Hikvision OEM camera's and my question is how do i update/upgrade these ones. (they are OEM)
The cameras are DS-2CD2347G1-LU and DS-2CD2385FWD-I.
The model numbers you have quoted are normal Hikvision ones.
The Hikvision stock firmware for those models is here :

But from what I've seen, none of those firmware versions supports the 'turn on the LEDs on motion event' linkage capability.

There has been one firmware version that does this on the DS-2CD2347G1-LU - see this post :
 
The model numbers you have quoted are normal Hikvision ones.
The Hikvision stock firmware for those models is here :

But from what I've seen, none of those firmware versions supports the 'turn on the LEDs on motion event' linkage capability.

There has been one firmware version that does this on the DS-2CD2347G1-LU - see this post :



The model numbers are: DT347G-U (DS-2CD2347G1-LU) and DT385-I (DS-2CD2385FWD-I)
I tried the original software from the portal but no luck :(

Here a link to the firmware i need: DS-2CD2347G1-L(U) Hikvision 4 MP ColorVu Fixed Turret Network Camera
This firmware includes the trigger on event Led on.
 
This firmware includes the trigger on event Led on.
Yes, I've tested that 5.6.2 firmware on a DS-2CD2347G1-LU ColorVu.
And it does have the capability for a motion event linkage to turn on the LEDs.
Despite all the newer stock versions up to 5.6.5 from here :

oddly not having that capability.

If your OEM camera firmware is rejecting attempts to apply the stock firmware as it's respecting the mismatch of the OEM code, you'd have to try the tftp updater method, which does less validation and might just ignore the OEM code.
But because the firmware filesize is above the 32MB size limit of the Hikvsion tftp updater, you'd need to try Scott Lamb's python clone, here :
 
If your OEM camera firmware is rejecting attempts to apply the stock firmware as it's respecting the mismatch of the OEM code, you'd have to try the tftp updater method, which does less validation and might just ignore the OEM code.
But because the firmware filesize is above the 32MB size limit of the Hikvsion tftp updater, you'd need to try Scott Lamb's python clone, here :
I tried the Scottlamb tftp method but i think i'm doing something wrong.
Wireshark shows me enough traffic but i can't find why its not working.
Tried both ip adresses...
 
I see the UDP probe from the server
No - the UDP probe comes from the camera, usually from source address 192.0.0.64, to the server on destination 192.0.0.128
It can be blocked inbound to the PC if the Windows firewall doesn't have an inbound rule, or isn't temporarily disabled.
 
No - the UDP probe comes from the camera, usually from source address 192.0.0.64, to the server on destination 192.0.0.128
It can be blocked inbound to the PC if the Windows firewall doesn't have an inbound rule, or isn't temporarily disabled.
Turned Windows Firewall off, and still nothing.
 

Attachments

  • dump.jpg
    dump.jpg
    907.8 KB · Views: 7
If you want to take this experiment further - a connection to the serial console will give direct access to the update program.
From what I recall, that model has a serial console connector under the SD card hatch.

That would need a USB to serial TTL convertor, such as a PL2303TA-based one.
A 4-pin 1.5mm JST ZH wired connector.
 
If you want to take this experiment further - a connection to the serial console will give direct access to the update program.
From what I recall, that model has a serial console connector under the SD card hatch.

That would need a USB to serial TTL convertor, such as a PL2303TA-based one.
A 4-pin 1.5mm JST ZH wired connector.
if i had those connectors i would try it.
But i think i wait for a new way to update or something :P
 
only a change in serverip?
Yes. My network at home is 192.168.1.x, so i was able to update without unplugging the camera from the network.

After the update i was unable to access the webinterface, but reboot fixed that..
 
I see that the IP in the camera is fixed at 192.168.1.64.. So maybe this is required.