Menu
What's new

Lorex LNB8005B-C and Dahua firmware (Solved with instructions)

R

Ross Cullen

n3wb
Joined
Jan 5, 2019
Messages
13
Reaction score
1
Location
Ireland
This has been really helpful. Thank you to all for your contributions.

I managed to flash a FLIR P143E4 4MP Outdoor Network Dome Camera successfully...

but my Lorex LNB3163B cameras (2016) make no attempt to initiate a TFTP connection on 192.168.1.108 (monitored using configured TFTP server, Ping and Wireshark). I tested the Flir camera that worked initially and I can see that ping. Would be interested if anyone had any thoughts/suggestions or has been able to flash this particular camera model. Thanks
 
P

pozzello

Known around here
Joined
Oct 7, 2015
Messages
2,270
Reaction score
1,117
seems some of Lorex's newer oferrings may no longer be Dahua-OEM'd. or they had Dahua disable the tftp at startup for them, specifically to prevent such self-service. One would probably need to access the serial port to find out more...
 
R

Ross Cullen

n3wb
Joined
Jan 5, 2019
Messages
13
Reaction score
1
Location
Ireland
pozzello said:
seems some of Lorex's newer oferrings may no longer be Dahua-OEM'd. or they had Dahua disable the tftp at startup for them, specifically to prevent such self-service. One would probably need to access the serial port to find out more...
Click to expand...
Thanks will give that a try. Ironically the FLIR was a newer camera than the Lorex! Unfortunetely I can't come across an old firmware to attempt a downgrade. Thanks anyways, appreciate the response :)
 
R

Ross Cullen

n3wb
Joined
Jan 5, 2019
Messages
13
Reaction score
1
Location
Ireland
Ross Cullen said:
Thanks will give that a try. Ironically the FLIR was a newer camera than the Lorex! Unfortunetely I can't come across an old firmware to attempt a downgrade. Thanks anyways, appreciate the response :)
Click to expand...
@pozzello Took your advise and managed to flash it via TFTP and serial connection using the command line. Have the equivalent Dahua firmware installed but finding that every time I set any resolution, it reverts to 720P and 1FPS. Have one a fresh firmware installed as well using the firmware upgrade option in the UI. Would appreciate any suggestions anyone may have :-D
 
P

pozzello

Known around here
Joined
Oct 7, 2015
Messages
2,270
Reaction score
1,117
Please specify which unit you flashed with which FW. Did you do a factory reset after the 'upgrade'? If not, try that to see if it fixes your 'config not-sticking' issue.

hopefully, there's a factory FW available for your unit in case it just doesn't work well on the Dahua FW and you need to revert. I generally don't muck around or recommend anyone else to without this option...
 
Last edited:
R

Ross Cullen

n3wb
Joined
Jan 5, 2019
Messages
13
Reaction score
1
Location
Ireland
pozzello said:
Please specify which unit you flashed with which FW. Did you do a factory reset after the 'upgrade'? If not, try that to see if it fixes your 'config not-sticking' issue.

hopefully, there's a factory FW available for your unit in case it just doesn't work well on the Dahua FW and you need to revert. I generally don't muck around or recommend anyone else to without this option...
Click to expand...
Thanks @pozzello appreciate the help :thumb:
Original firmware was:
LOREX_IPC-HFW1XXX-Alps_Eng_NP_V2.420.LR00.3.R.20160105.bin
firmware used was:
dh_ipc-hfw1xxx-alps_eng_p_v2.622.0000000.31.r.171229.bin
I have a Lorex LNB3163B
I'm assuming the Dahua equivilent is
Dahua IPC-HFW1320S

I did a reset in the GUI after upgrading the firmware but no joy. I remember because it went through the wizard for auto update etc. Thanks again. R
 
P

pozzello

Known around here
Joined
Oct 7, 2015
Messages
2,270
Reaction score
1,117
check.img from LOREX_IPC-HFW1XXX-Alps_Eng_NP_V2.420.LR00.3.R.20160105.bin has:

pozzello@sfo-lp82w:~$ strings check.img.lorex
strings: 'check.img.lorex': No such file
pozzello@sfo-lp82w:~$ strings check.img.lorex
check
"DefaultLanguage" : "English",
"DefaultVideoStandard" : "NTSC",
"SupportLanguages" : "English",
"hwid" : [
"IPC-HDW1020S-V2:01:02:05:49:1C:00:01:00:00:00:00:190:00:00:00:00:00:00:00:00:40",
"IPC-HFW1025B-V2:01:02:05:49:1C:00:01:00:00:00:00:190:00:00:00:00:00:00:00:00:40",
"IPC-HDW1120S-V2:01:02:05:38:1C:00:01:00:00:00:00:190:00:00:00:00:00:00:00:00:40",
"IPC-HDW1220S-V2:01:02:05:3D:1C:00:01:00:00:00:00:190:00:00:00:00:00:00:00:00:80",
"IPC-HDW1220S-V2:01:02:06:1F:1C:00:01:00:00:00:00:190:00:00:00:00:00:00:00:00:40",
"IPC-HFW1225B-V2:01:02:05:1F:1C:00:01:00:00:00:00:190:00:00:00:00:00:00:00:00:40",
"IPC-HDW1320S-V2:01:02:05:1F:1C:00:01:00:00:00:00:190:00:00:00:00:00:00:00:00:80",
"IPC-HDBW1325R-V2:01:02:05:1F:1C:00:01:00:00:00:00:258:00:00:00:00:00:00:00:00:80"
]


while the one from that Dahua FW has:

pozzello@sfo-lp82w:~$ strings check.img
check
"DefaultLanguage" : "English",
"DefaultVideoStandard" : "PAL",
"SupportLanguages" : "English",
"hwid" : [
"IPC-HFW1220B-V2:01:02:02:4F:1C:00:01:00:00:00:00:258:00:00:00:00:00:00:00:00:80",
"IPC-HFW1220S-V2:01:02:02:4F:1C:00:01:00:00:00:00:258:00:00:00:00:00:00:00:00:80",
"IPC-HDBW1220R-V2:01:02:05:55:1C:00:01:00:00:00:00:258:00:00:00:00:00:01:00:00:80",
"IPC-HFW1220M-V2:01:02:02:58:1C:00:01:00:00:00:00:258:00:00:00:00:00:00:00:00:80",
"IPC-HDBW1220R-S-V2:01:02:05:58:1C:00:01:00:00:00:04:258:00:00:00:00:00:00:00:00:80",
"IPC-HDBW1220R-S2:01:02:05:65:1C:00:01:00:00:00:00:258:00:00:00:00:00:00:00:00:80",
"IPC-HDBW1220R-S-S2:01:02:05:65:1C:00:01:00:00:00:04:258:00:00:00:00:00:00:00:00:80",
"IPC-HFW1220M-AS-S2:01:02:02:51:1C:00:01:0E:01:01:04:258:08:03:00:00:00:00:00:00:80",
"IPC-HFW1220M-S-S2:01:02:02:51:1C:00:01:00:00:00:04:258:00:03:00:00:00:00:00:00:80",
"IPC-HDW1320S-V2:01:02:05:1F:1C:00:01:00:00:00:00:190:00:00:00:00:00:00:00:00:80",
"IPC-HDBW1325R-S-V2:01:02:05:1F:1C:00:01:00:00:00:04:258:00:00:00:00:00:00:00:00:80",
"IPC-HDBW1325R-V2:01:02:05:1F:1C:00:01:00:00:00:00:258:00:00:00:00:00:00:00:00:80",
"IPC-HDBW1320R-S-V2:01:02:05:61:1C:00:01:00:00:00:04:258:00:00:00:00:00:00:00:00:80",
"IPC-HDBW1320R-V2:01:02:05:61:1C:00:01:00:00:00:00:258:00:00:00:00:00:00:00:00:80",
"IPC-HFW1320M-AS:01:02:02:19:1C:00:01:0E:01:01:04:258:08:00:00:00:00:01:00:00:80"
]

while IPC-HDW1320S-V2 is listed in both, are you sure that matches the HWID of your Lorex/Flir ?

what does URL "http://<cam-ip>/cgi-bin/magicBox.cgi?action=getSystemInfo" return in any browser?

Also, the Dahua FW defaults to PAL, while the Lorex/Flir defaults to NTSC, which may be related to the resolution settings. If there's a GUI setting for NTSC/PAL (typically in the 'image' config page, try toggling that and see if the behavior remains...
 
R

Ross Cullen

n3wb
Joined
Jan 5, 2019
Messages
13
Reaction score
1
Location
Ireland
pozzello said:
check.img from LOREX_IPC-HFW1XXX-Alps_Eng_NP_V2.420.LR00.3.R.20160105.bin has:

pozzello@sfo-lp82w:~$ strings check.img.lorex
strings: 'check.img.lorex': No such file
pozzello@sfo-lp82w:~$ strings check.img.lorex
check
"DefaultLanguage" : "English",
"DefaultVideoStandard" : "NTSC",
"SupportLanguages" : "English",
"hwid" : [
"IPC-HDW1020S-V2:01:02:05:49:1C:00:01:00:00:00:00:190:00:00:00:00:00:00:00:00:40",
"IPC-HFW1025B-V2:01:02:05:49:1C:00:01:00:00:00:00:190:00:00:00:00:00:00:00:00:40",
"IPC-HDW1120S-V2:01:02:05:38:1C:00:01:00:00:00:00:190:00:00:00:00:00:00:00:00:40",
"IPC-HDW1220S-V2:01:02:05:3D:1C:00:01:00:00:00:00:190:00:00:00:00:00:00:00:00:80",
"IPC-HDW1220S-V2:01:02:06:1F:1C:00:01:00:00:00:00:190:00:00:00:00:00:00:00:00:40",
"IPC-HFW1225B-V2:01:02:05:1F:1C:00:01:00:00:00:00:190:00:00:00:00:00:00:00:00:40",
"IPC-HDW1320S-V2:01:02:05:1F:1C:00:01:00:00:00:00:190:00:00:00:00:00:00:00:00:80",
"IPC-HDBW1325R-V2:01:02:05:1F:1C:00:01:00:00:00:00:258:00:00:00:00:00:00:00:00:80"
]


while the one from that Dahua FW has:

pozzello@sfo-lp82w:~$ strings check.img
check
"DefaultLanguage" : "English",
"DefaultVideoStandard" : "PAL",
"SupportLanguages" : "English",
"hwid" : [
"IPC-HFW1220B-V2:01:02:02:4F:1C:00:01:00:00:00:00:258:00:00:00:00:00:00:00:00:80",
"IPC-HFW1220S-V2:01:02:02:4F:1C:00:01:00:00:00:00:258:00:00:00:00:00:00:00:00:80",
"IPC-HDBW1220R-V2:01:02:05:55:1C:00:01:00:00:00:00:258:00:00:00:00:00:01:00:00:80",
"IPC-HFW1220M-V2:01:02:02:58:1C:00:01:00:00:00:00:258:00:00:00:00:00:00:00:00:80",
"IPC-HDBW1220R-S-V2:01:02:05:58:1C:00:01:00:00:00:04:258:00:00:00:00:00:00:00:00:80",
"IPC-HDBW1220R-S2:01:02:05:65:1C:00:01:00:00:00:00:258:00:00:00:00:00:00:00:00:80",
"IPC-HDBW1220R-S-S2:01:02:05:65:1C:00:01:00:00:00:04:258:00:00:00:00:00:00:00:00:80",
"IPC-HFW1220M-AS-S2:01:02:02:51:1C:00:01:0E:01:01:04:258:08:03:00:00:00:00:00:00:80",
"IPC-HFW1220M-S-S2:01:02:02:51:1C:00:01:00:00:00:04:258:00:03:00:00:00:00:00:00:80",
"IPC-HDW1320S-V2:01:02:05:1F:1C:00:01:00:00:00:00:190:00:00:00:00:00:00:00:00:80",
"IPC-HDBW1325R-S-V2:01:02:05:1F:1C:00:01:00:00:00:04:258:00:00:00:00:00:00:00:00:80",
"IPC-HDBW1325R-V2:01:02:05:1F:1C:00:01:00:00:00:00:258:00:00:00:00:00:00:00:00:80",
"IPC-HDBW1320R-S-V2:01:02:05:61:1C:00:01:00:00:00:04:258:00:00:00:00:00:00:00:00:80",
"IPC-HDBW1320R-V2:01:02:05:61:1C:00:01:00:00:00:00:258:00:00:00:00:00:00:00:00:80",
"IPC-HFW1320M-AS:01:02:02:19:1C:00:01:0E:01:01:04:258:08:00:00:00:00:01:00:00:80"
]

while IPC-HDW1320S-V2 is listed in both, are you sure that matches the HWID of your Lorex/Flir ?

what does URL "http://<cam-ip>/cgi-bin/magicBox.cgi?action=getSystemInfo" return in any browser?

Also, the Dahua FW defaults to PAL, while the Lorex/Flir defaults to NTSC, which may be related to the resolution settings. If there's a GUI setting for NTSC/PAL (typically in the 'image' config page, try toggling that and see if the behavior remains...
Click to expand...
Thanks @pozzello ... here is the output from the URL you suggested above:

appAutoStart=true
deviceType=IPC-HFW1320S
hardwareVersion=1.00
processor=DH6000
serialNumber=ND031709003847
updateSerial=IPC-HDW1320S-V2
updateSerialCloudUpgrade=IPC-HDW1320S-V2:01:02:05:1F:1C:00:01:00:00:00:00:190:00:00:00:00:00:00:00:00:80

OK...I think I've spotted the issue (I think). The "DeviceType" listed above from the output is IPC-HFW1320S (bullet camera) which is the nearest Dahua equivalent I can match it to (although the Lorex/FLIR camera can do 25fps @3MP while the Dahua is listed as only being able to do 20fps @3MP). The firmware applied however appears to be PC-HDW1320S (dome).

Tried looking for a firmware with IPC-HFW1320S listed but don't seem to be able to find one. Any suggestions greatly appreciated as ever :)
 
P

pozzello

Known around here
Joined
Oct 7, 2015
Messages
2,270
Reaction score
1,117
pretty sure it's the updateSerial that determines FW compatibility, and that seems to match, IPC-HDW1320S-V2

It could be Lorex had them enable the higher framerate support in exchange for disabling other cpu-intensive features (like IVS, etc...) There has to be tradeoff, with the limited resources available...

how about the NTSC vs PAL settings?
 
R

Ross Cullen

n3wb
Joined
Jan 5, 2019
Messages
13
Reaction score
1
Location
Ireland
pozzello said:
pretty sure it's the updateSerial that determines FW compatibility, and that seems to match, IPC-HDW1320S-V2

It could be Lorex had them enable the higher framerate support in exchange for disabling other cpu-intensive features (like IVS, etc...) There has to be tradeoff, with the limited resources available...

how about the NTSC vs PAL settings?
Click to expand...
Gotcha... that would make sense. Main reason for changeover is the Lorex firmware wouldn't work on synology surveillance station (but the Dahua would... minus the current resolution/fps issues)!

Would you believe, I can only select PAL (no NTSC on the dropdown for some reason?)
 
P

pozzello

Known around here
Joined
Oct 7, 2015
Messages
2,270
Reaction score
1,117
@Ross Cullen, i think that may be the problem. you previously had configured resolutions in the NTSC space, but the new GUI doesn't know anything about them (as it's PAL only), so thigns are out of sync.

When you did a config reset after fw update, did you do a full 'factory default' or only the partial 'default' reset? if not already, please try 'factory default'. yes, it's more of a pain, but may do a more complete job of converting to PAL-only settings.

An alternative would be to find a version of the FW for that HWID that also supports NTSC...
 
R

Ross Cullen

n3wb
Joined
Jan 5, 2019
Messages
13
Reaction score
1
Location
Ireland
pozzello said:
@Ross Cullen, i think that may be the problem. you previously had configured resolutions in the NTSC space, but the new GUI doesn't know anything about them (as it's PAL only), so thigns are out of sync.

When you did a config reset after fw update, did you do a full 'factory default' or only the partial 'default' reset? if not already, please try 'factory default'. yes, it's more of a pain, but may do a more complete job of converting to PAL-only settings.

An alternative would be to find a version of the FW for that HWID that also supports NTSC...
Click to expand...
Thanks @pozzello ... did another "Factory Default" there (had to change password, accept license etc) but still no NTSC option :-( Also did one from the command line via serial.

Will keep searching for alternative firmware... Thanks again ;)
 
P

pozzello

Known around here
Joined
Oct 7, 2015
Messages
2,270
Reaction score
1,117
i wasn't suggesting it would add NTSC option (that's apparently just not in the FW you loaded), just that the PAL settings might now work as you set them. it sounded like your resolution settings were not previously 'sticking', PAL vs NTSC is not really a problem in the digital domain, just a slightly different set of options
 
R

Ross Cullen

n3wb
Joined
Jan 5, 2019
Messages
13
Reaction score
1
Location
Ireland
pozzello said:
i wasn't suggesting it would add NTSC option (that's apparently just not in the FW you loaded), just that the PAL settings might now work as you set them. it sounded like your resolution settings were not previously 'sticking', PAL vs NTSC is not really a problem in the digital domain, just a slightly different set of options
Click to expand...
I understand what you mean and I agree on the PAL/NTSC thing. I agree, somethings just not 'sticking'. I thought i'd made a breakthrough by changing the values in "System->General" so it would help things stick... and although it seemed to be longer (caus it does stick for a good few seconds). its eventually reverted to 720P and 1FPS. Anyhoo, I've had enough for one night! Thanks again for your help @pozzello
 
R

Ross Cullen

n3wb
Joined
Jan 5, 2019
Messages
13
Reaction score
1
Location
Ireland
Finally a breakthrough @pozzello ... so I had been using firmware 2.420 of the FLIR/Lorex for my LNB3163B. I had tried upgrading to 2.622 before using FLIR_IPC-HFW1XXX-Alps_Eng_NP_V2.622.00FL000.12.R.180628.bin but it had failed. Fundamentally (when I really thought about it), all that was important to me was upgrading ONVIF (current 2.420 was ONVIF 2.4.2) so it would work with Synology Surveillance Station.

So I tried using the firmware mentioned using TFTP in combination with serial.... and voila... the firmware works extremely well (login screen now branded FLIR instead of Lorex, in line with the merger of companies at that time). I now have ONVIF v16.12 and its finally working stable with Synology Surveillance Station.

A big thanks @pozzello for all your advise and encouragement, I would have probably given up without your help. Sincere and heartfelt thanks! :)
 
P

pozzello

Known around here
Joined
Oct 7, 2015
Messages
2,270
Reaction score
1,117
so you ended up using the updated Flir fw? glad you found something that works after a meandering trip down the garden lane... :)
 
R

Ross Cullen

n3wb
Joined
Jan 5, 2019
Messages
13
Reaction score
1
Location
Ireland
pozzello said:
so you ended up using the updated Flir fw? glad you found something that works after a meandering trip down the garden lane... :)
Click to expand...
This firmware in question wouldn't work through the web UI upgrade tool so I doubt it was ever intended for the LNB3163B. My cameras are now listed as PB133E. Thanksfully wasn't all in vein because I still needed to use serial and TFTP to install it. Plenty of head scratching over the past few days but the satisfaction was worth it! Thanks again @pozzello
 
P

pozzello

Known around here
Joined
Oct 7, 2015
Messages
2,270
Reaction score
1,117
the PB133e fw here: DahuaWiki does have IPC-HDW1320S-V2 in the check file, so it does make sense that it works for that cam. i think you were unable to load it from the web GUI as you had already loaded the Dahua fw... it most likely would have loaded fine in the web UI from the original (earlier) Flir fw...
 
R

Ross Cullen

n3wb
Joined
Jan 5, 2019
Messages
13
Reaction score
1
Location
Ireland
pozzello said:
the PB133e fw here: DahuaWiki does have IPC-HDW1320S-V2 in the check file, so it does make sense that it works for that cam. i think you were unable to load it from the web GUI as you had already loaded the Dahua fw... it most likely would have loaded fine in the web UI from the original (earlier) Flir fw...
Click to expand...
Had tried upgrading with a fresh Lorex (now FLIR) camera as well that I had and the firmware had failed on that too. Its odd. I'll double check on the final camera just in case. Tks
Edit: The IPC-HDW1320S-V2 you've referenced is a dome camera (the cameras I have are bullet camera and most closely represent IPC-HFW1320S... not sure that makes a difference). The most important thing I guess is that its working (thank goodness & thanks to your help!)
 
P

pozzello

Known around here
Joined
Oct 7, 2015
Messages
2,270
Reaction score
1,117
yes, i get it. hdw vs hfw. but your cam, tho in a bullet format (hfw) presents HWID with HDW, so that's the firmware that should (and apparently does) work. OK, nuf said. cheers!
 
You must log in or register to reply here.
Top