Help identifying Dahua OEM NVR from Speco N8NXP

I will mention the serial port on my Speco did have pins on it unlike val-ipcam's which didn't. The process was still the same though.
Can you advise how you went about connecting the USB to serial converter to your board with pins? I have everything I need except haven't walked through the steps because the little pins are so darn hard to connect without a harness.
 
Can you advise how you went about connecting the USB to serial converter to your board with pins? I have everything I need except haven't walked through the steps because the little pins are so darn hard to connect without a harness.

Preferably you would use a harness, but I didn't have one that fit. I was impatient, so I took a different approach. I updated my earlier post with more details of what I did along with a picture.
 
  • Like
Reactions: mat200
Preferably you would use a harness, but I didn't have one that fit. I was impatient, so I took a different approach. I updated my earlier post with more details of what I did along with a picture.
I wish someone would enlighten us on what type of harness that is so I could get a few and have a solid connection. I'm wary about attempting a flash upgrade with tenuous connections.
 
I wish someone would enlighten us on what type of harness that is so I could get a few and have a solid connection. I'm wary about attempting a flash upgrade with tenuous connections.

Just looking at pictures, it looks a lot like the JST PH 4 pin female connectors. The problem is I can't determine if these are the right size or not just by pictures. There are a lot of them available on Amazon along with AliExpress for fairly cheap. Here's a link to a search on Amazon so you can take a look and research it further.
 
Just looking at pictures, it looks a lot like the JST PH 4 pin female connectors. The problem is I can't determine if these are the right size or not just by pictures. There are a lot of them available on Amazon along with AliExpress for fairly cheap. Here's a link to a search on Amazon so you can take a look and research it further.
So like I mentioned before, I haven’t gotten around to trying this yet on my NVR, but this is the serial adapter I ordered. It includes a ribbon cable with the Individual headers to be able to slip onto the pins, even if it’s not a molded 4-pin header. Unless these pins are some odd size, I think this should suffice.

DSD TECH USB to TTL Serial Converter CP2102 with 4 PIN Dupont Cable Compatible with Windows 7,8,10,Linux,Mac OSX
 
As an Amazon Associate IPCamTalk earns from qualifying purchases.
  • Like
Reactions: mat200
So like I mentioned before, I haven’t gotten around to trying this yet on my NVR, but this is the serial adapter I ordered. It includes a ribbon cable with the Individual headers to be able to slip onto the pins, even if it’s not a molded 4-pin header. Unless these pins are some odd size, I think this should suffice.

DSD TECH USB to TTL Serial Converter CP2102 with 4 PIN Dupont Cable Compatible with Windows 7,8,10,Linux,Mac OSX

The adapter itself should be fine, but those pins won't fit correctly to the motherboard. My adapter is the same brand and came with a similar cable set. The problem is the pins are short and close together making the square plastic cover on those wires too close together. That is why I had to remove the plastic covers. If they make something similar in a smaller size then it would work, but I don't know if they do.
 
As an Amazon Associate IPCamTalk earns from qualifying purchases.
  • Like
Reactions: mat200
The adapter itself should be fine, but those pins won't fit correctly to the motherboard. My adapter is the same brand and came with a similar cable set. The problem is the pins are short and close together making the square plastic cover on those wires too close together. That is why I had to remove the plastic covers. If they make something similar in a smaller size then it would work, but I don't know if they do.

thanks for heads up. I’ll see what I can come up with.
 
  • Like
Reactions: mat200
I know some people were asking about IVS with this NVR and I can verifiy that it does support IVS. I got some Amcrest 5MP cameras that are Dahua IPC-HDW2531T-AS-S2. I flashed them over to Dahua firmware and they support IVS. I enabled IVS in the cameras and in the NVR and I was able to setup tripwires. I now email notifications from the NVR when they are tripped. I still haven't figured out how to get IVS push notifications in the gDMSS app, but the motion push notifications work fine.
 
Thanks for the write up to flash themm I bought the $100 N16NXP version which is the 4416-16p-4ks2 version mainly for the 4 hdd support. I flashed it through its rs232 port to 3.216 and IVS works like a charm with my Dahua 1831 and amcrest flashed to dahua firmware cameras.
 
  • Like
Reactions: mat200 and sstevetx
That’s great news! I actually bought the usb to serial converter but haven’t gotten around to flashing it yet.
Well it's official. I did it. I'm now running the latest Dahua firmware on the Speco branded NVR. Special thanks to sstevetx and val-ipcam for trying this out first and taking a lot of the unknown out. Everything went exactly as described previously. As mentioned before, I tried the method that sstevetx used for hooking up to the pins on the board.

The only thing that was slightly unnerving was the 'du' command. I guess that file isn't included in the 3.216 firmware so it failed to update that file. What this resulted in was Speco branded tiles on the monitor display. Once I updated to the lasted 4.0 firmware, that got updated.
 
Well it's official. I did it. I'm now running the latest Dahua firmware on the Speco branded NVR. Special thanks to sstevetx and val-ipcam for trying this out first and taking a lot of the unknown out. Everything went exactly as described previously. As mentioned before, I tried the method that sstevetx used for hooking up to the pins on the board.

The only thing that was slightly unnerving was the 'du' command. I guess that file isn't included in the 3.216 firmware so it failed to update that file. What this resulted in was Speco branded tiles on the monitor display. Once I updated to the lasted 4.0 firmware, that got updated.

So after messing around with the updated firmware and my cameras, i can't seem to get IVS working. I have IVS set up on one of my cameras, SmartPlan enabled and several tripwires. I turned on the Intelligent option in the recording manager. Not sure if this is just a byproduct of the hardware maybe not natively supporting IVS (even though ALL the options are there)? I do notice in the IVS control options in the NVR, the NVR fails to pull the IVS config from the cameras...which could be why it's not recording.
 
So after messing around with the updated firmware and my cameras, i can't seem to get IVS working. I have IVS set up on one of my cameras, SmartPlan enabled and several tripwires. I turned on the Intelligent option in the recording manager. Not sure if this is just a byproduct of the hardware maybe not natively supporting IVS (even though ALL the options are there)? I do notice in the IVS control options in the NVR, the NVR fails to pull the IVS config from the cameras...which could be why it's not recording.

The IVS is working for me so far with emails being consistently sent with tripwire alerts, alarms showing up in the "Alarm Info" section of the NVR and IVR events showing up under the NVR AI->Smart Search section. Did you turn on SmartPlan on both the NVR and within the Camera itself?

NVR: AI -> Parameters -> Smart Plan
Camera: Setting ->Event -> Smart Plan
 
  • Like
Reactions: mat200
The IVS is working for me so far with emails being consistently sent with tripwire alerts, alarms showing up in the "Alarm Info" section of the NVR and IVR events showing up under the NVR AI->Smart Search section. Did you turn on SmartPlan on both the NVR and within the Camera itself?

NVR: AI -> Parameters -> Smart Plan
Camera: Setting ->Event -> Smart Plan

hmm, interesting. I did turn it on on the camera. On the NVR I consistently get the red “Disconnected” pop up when I click Smart Plan, and when I click IVS I get the red “Failed to acquire config” pop up.
 
hmm, interesting. I did turn it on on the camera. On the NVR I consistently get the red “Disconnected” pop up when I click Smart Plan, and when I click IVS I get the red “Failed to acquire config” pop up.

I wonder if the NVR doesn't believe the camera supports IVS? I get the same type of popup when I try to enable Face Detection in the NVR since the camera doesn't support it. Did you try doing a factory reset on the camera after you did the firmware upgrade on it? I'm new to all this, so that's about all I know at this point. Someone else might be able to jump in and provide some additional help.
 
I wonder if the NVR doesn't believe the camera supports IVS? I get the same type of popup when I try to enable Face Detection in the NVR since the camera doesn't support it. Did you try doing a factory reset on the camera after you did the firmware upgrade on it? I'm new to all this, so that's about all I know at this point. Someone else might be able to jump in and provide some additional help.
That’s what I’m thinking. That or maybe I need to update my camera firmware? I’m running a build from 12/2019 on the cameras, and the NVR I believe is a build from 03/2020.
 
FYI, I worked with the awesome people over on the DigiKey forums to identify the connector on the board. We believe it is a Molex PicoBlade connector. The corresponding male connector for this harness is most likely the WM1722-ND. Corresponding socket crimps would be required to build your own cable. Pre-crimped leads and fully pre-made cables are also available. I'm going to prove this out over the next couple weeks.
 
  • Like
Reactions: mat200 and mcolina1
Good work! Maybe post the details about the connector in this thread for when the listing eventually gets removed?
My response was already to a previous message where I documented the details about the connector.
FYI, I worked with the awesome people over on the DigiKey forums to identify the connector on the board. We believe it is a Molex PicoBlade connector. The corresponding male connector for this harness is most likely the WM1722-ND. Corresponding socket crimps would be required to build your own cable. Pre-crimped leads and fully pre-made cables are also available. I'm going to prove this out over the next couple weeks.
 
  • Like
Reactions: mcolina1