ONVIF Problem with Lorex LNE9292B / Dahua IPC-HDW3841T-ZAS-27135

B

brettgavin

n3wb
Jan 9, 2023
9
2
USA
I have some Lorex LNE9292B cameras that I'm trying to attach to Blue Iris.

So far, I have 5 cameras attached (19 more to go) to BI, but 2 out of the 5 aren't able to get video via ONVIF. I get "Cam2: No Signal. Error: 8000274c (Failed to Connect) 0" on a gray thumbnail. The cameras DO work with the Lorex NVR. I've tried defaulting the cameras, but it doesn't help.

Also, these cameras won't respond to ping, but they are accessible via the web interface.

SystemInfo reports:
/cgi-bin/magicBox.cgi?action=getSystemInfo

appAutoStart=true
deviceType=LNE9292B
hardwareVersion=1.00
processor=SSC339
serialNumber=NDmynumber
updateSerial=IPC-HDW3841T-ZAS-27135
updateSerialCloudUpgrade=IPC-HDW3841T-ZAS-27135


Web GUI Information/Version page reports:
Device TypeLNE9292B
System Version00008
buildDate2021-06-30
WEB VersionV3.2.1.913961
ONVIF Version19.06(V2.6.1.887698)
S/N NDmynumber
Algorithm Version2.0.0
Security Baseline VersionV2.1



My questions are:
  1. Is this a known issue? I haven't found anything about this model and ONVIF, yet.
  2. Would the Dahua firmware for the IPC-HDW3841T-ZAS-27135 be a better/more reliable option?
    1. Is this the best place to get the firmware? IPC-HDW3841T-ZAS
      1. What is the difference between NP and PN versions?
    2. Are there any gotchas with the flash process?
      1. Does the firmware installed even allow cross-flashing? I've read about the firmware locking to Lorex branded firmware.

Thanks for reading.
 
Maybe worth checking if ONVIF Device Manager finds the camera, and shows live video.
Give ODM some admin logon credentials, top left of the window.
sourceforge.net

ODM

Download ODM for free. Device Manager for ONVIF-based Network video devices. ODM is a ONVIF protocol implementation of Network Video Client (NVC) to manage Network Video Transmitters (NVT), Network Video Storage (NVS) and Network Video Analytics (NVA) devices. Implements Discovery, Device...
sourceforge.net sourceforge.net
 
Lorex has been preventing flashing firmware from the Dahua equivalent. It may work, or it may brick it.

The NP and PN simply mean PAL or NTSC, but since it is a slider in the firmware, it doesn't really matter.

What we really need is your network topology and a screenshot of what shows up in BI in the popup window when you hit the find/inspect button.
 
alastairstevenson said:
Maybe worth checking if ONVIF Device Manager finds the camera, and shows live video.
Give ODM some admin logon credentials, top left of the window.
sourceforge.net

ODM

Download ODM for free. Device Manager for ONVIF-based Network video devices. ODM is a ONVIF protocol implementation of Network Video Client (NVC) to manage Network Video Transmitters (NVT), Network Video Storage (NVS) and Network Video Analytics (NVA) devices. Implements Discovery, Device...
sourceforge.net sourceforge.net
Click to expand...


ODM is able to see the NVR and all 5 camera channels on the NVR. It is also able to see 3 out of the 5 cameras directly. The other 2 don't show up directly.
 
wittaj said:
Lorex has been preventing flashing firmware from the Dahua equivalent. It may work, or it may brick it.

The NP and PN simply mean PAL or NTSC, but since it is a slider in the firmware, it doesn't really matter.

What we really need is your network topology and a screenshot of what shows up in BI in the popup window when you hit the find/inspect button.
Click to expand...


Topology diagram below:
camera topology.png


Find/Inspect from working camera:
Code: 
Opening 10.0.0.201 port 80...
HTTP Get / request...
OK
ONVIF GetSystemDateAndTime
2023-01-09T21:38:05.000Z
Requesting device information...
Manufacturer: LOREX
Model: LNE9292B
FirmwareVersion: 2.800.00LR002.8.R, Build Date 2021-06-30
GetCapabilities...
Querying services
Has Imaging services: /onvif/imaging_service
Has media services: /onvif/media_service
Has RTP_RTSP_TCP, requesting profiles
profile token MediaProfile00000
profile name MediaProfile_Channel1_MainStream
profile source is 00000
profile source config is 00000
profile token MediaProfile00001
profile name MediaProfile_Channel1_SubStream1
profile source is 00000
profile source config is 00000
profile token MediaProfile00002
profile name MediaProfile_Channel1_SubStream2
profile source is 00000
profile source config is 00000
requesting URI for profile MediaProfile00000
RTSP URI: /cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif
requesting URI for profile MediaProfile00001
RTSP URI: /cam/realmonitor?channel=1&subtype=1&unicast=true&proto=Onvif
requesting URI for profile MediaProfile00002
RTSP URI: /cam/realmonitor?channel=1&subtype=2&unicast=true&proto=Onvif
Has Event services: /onvif/event_service
Has WSPullPointSupport
RelayOutputs: 0
InputConnectors: 0
Has Device IO services: /onvif/deviceIO_service
AudioOutputs: 0
Has PTZ service: /onvif/ptz_service
Done


Find/Inspect from non-working camera:
Code: 
Opening 10.0.0.203 port 80...
HTTP Get / request...
OK
ONVIF GetSystemDateAndTime
2023-01-09T21:39:28.000Z
Requesting device information...
Manufacturer: LOREX
Model: LNE9292B
FirmwareVersion: 2.800.00LR002.8.R, Build Date 2021-06-30
GetCapabilities...
Querying services
Has Imaging services: /onvif/imaging_service
Has media services: /onvif/media_service
Has RTP_RTSP_TCP, requesting profiles
profile token MediaProfile00000
profile name MediaProfile_Channel1_MainStream
profile source is 00000
profile source config is 00000
profile token MediaProfile00001
profile name MediaProfile_Channel1_SubStream1
profile source is 00000
profile source config is 00000
profile token MediaProfile00002
profile name MediaProfile_Channel1_SubStream2
profile source is 00000
profile source config is 00000
requesting URI for profile MediaProfile00000
RTSP URI: /cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif
requesting URI for profile MediaProfile00001
RTSP URI: /cam/realmonitor?channel=1&subtype=1&unicast=true&proto=Onvif
requesting URI for profile MediaProfile00002
RTSP URI: /cam/realmonitor?channel=1&subtype=2&unicast=true&proto=Onvif
Has Event services: /onvif/event_service
Has WSPullPointSupport
RelayOutputs: 0
InputConnectors: 0
Has Device IO services: /onvif/deviceIO_service
AudioOutputs: 0
Has PTZ service: /onvif/ptz_service
Done
 
That is interesting. Nothing quickly sticks out to me as an issue in that find/inspect.

BUT...if you plan to continue using the Lorex NVR, how about letting that feed the cameras into BI?

In BI, you select add camera and put the IP address of the NVR into the IP address location. Put in username and password and hit find/inspect and let BI do its thing.

Then about halfway down is a pull down for Camera number and pick camera 1 and then hit ok. The camera should show up. Then repeat process and add camera and then select copy and copy this camera and then change the number 1 to a 2 and repeat for your cameras. OR depending on your NVR, it may populate all the cameras in the main and substream pulldown boxes and you just select a camera number and then add another camera and select the next pulldown.
 
Here's an interesting detail:

One of the non-working cameras attached to BI has captured 2 frames via ONVIF; one yesterday afternoon and one about 0130 last night. No stream is available, but it seems to have connected at some point. Both cameras still have the failed to connect message.
 
brettgavin said:
I hadn't planned to keep the Lorex NVR, but that's not a bad idea. I'll give it a try and see what happens.
Click to expand...

I added the NVR as a camera source. I am able to see 1 of the 2 non-working cameras. It seems that no matter which channel I select, I am only able to see the 1 camera. Did I miss something I should configure?

In the image below:

Cam7 is Channel 1
Cam 6 is Channel 4
Cam2 is the displayed camera (.203)

1673369713941.png
 
Turn on the substreams for each camera and in BI to rule out it isn't a bottleneck in the network somewhere.

And up the Receive buffer to 40MB on that screen above for each camera.
 
heh. yeah. and super frustrating at the same time.

i'm going to keep adding more cameras, then. hopefully, this was a limited scope problem.


thank you for you assistance with the troubleshooting.
 
  • Like
Reactions: mat200
You must log in or register to reply here.
Top Bottom