Recent content by TheDude

Latest version is DH_NVR5XXX-4KS2_MultiLang_V4.002.0000000.6.R.221115 Maybe try updating to that one? https://www.dahuasecurity.com/products/All-Products/Network-Recorders/Pro-Series/NVR5-Series/2HDD/NVR5208/5216/5232-4KS2

I told you in the other thread after you got the NVR flashed to Dahua firmware that the Lorex cameras cannot be cross flashed. Only the NVR can. The cameras use a Lorex signed firmware that will only accept another Lorex specific firmware.

Great to hear you got it to finally work right on the NVR! Now you can use the Dahua web interface and update it to the most current versions of Dahua software. From what I have found, the Lorex branded cameras cannot be flashed to Dahua firmware. They are made by Dahua but have a custom...

Did you follow the instructions here - Lorex Another method - if trying to update using the "run up" command might be to try to update individual parts of the firmware one by one using this method - Lorex I did compare and according to Lorex mine and yours use the same firmware. So one of...

ARP Retry Count and Bad Magic Number are the issues. ARP retry is likely a networking thing. Not sure if it matters but when I did my setenv commands for the IP addresses I used this format which adds what each line is specifically for. setenv serverip 255.255.255.255 setenv ipaddr...

Maybe, and only maybe..... flashing it via a direct TTL connection to the internal circuit board might work. That is a lot more involved though and requires a TTL adapter, manually extracting the firmware, then use a terminal emulator command line to interrupt the boot loader and and manually...

Ah - yeah I think wittaj might be right. I remember reading on some other thread about that a while back that some of the newer firmware might not allow cross flashing without first downgrading to an older firmware. I guess if an older firmware cannot be found or if the device is new enough that...

READ my post at the top of the page, about 5 posts up. I detailed exactly what you want to look for and gave a link to the Dahua firmware page. You found the Amcrest firmware already. When you go to the Dahua firmware link above you can see there is a matching Dahua firmware from January 18 2022.

I cannot say I've seen any performance improvement crossflashing any of mine. I did find additional features (cannot remember specifically what anymore). Also better odds that if there is a bug or security patch needed that Dahua will implement it before downline rebranded ones do. Of course...

To figure this out, you first have to find the Amcrest firmware for the camera. Firmware Upgrade | Amcrest Technologies Then you look at the file name to find the type name which is type number plus a name (both are critical). In this case you find that it is a "Hx25(8)xx Molec" device. The...

I have always gone to the official Dahua Wiki for software/firmware. You can also directly browse the file system by using this link.... that being said, I don't see anything about an SDK there. https://dahuawiki.com/images/Files/

I have no idea if trying to use a TTL serial adapter on a regular serial connection might be workable. TTL is 0v, 3.3v, and 5V signaling while that serial port on the NVR is standard RS232 serial which is 12v signaling. The console is getting something though but no idea what. Maybe trying...

Garbled serial console data is usually caused by an incorrect configuration for the serial communication. I think the NVR's are usually configured for serial at 115,200 8 N 1 but maybe yours is set for a different speed or possibly the pins on the serial port are not configured right. Not really...

One of my SD1A203T PTZ cameras will only work when powered via the 12V power jack now. Will not power up with POE using the NVR5216-4KS2 NVR or with a Texas POE injector.....

Maybe you can catch it with the Config Tool, select its checkbox and re-initialize it or restore the factory defaults using the Config Tool? Might be worth a try. Not sure otherwise other than maybe trying to manually connect its serial port and see what a console session shows and try to update...