Is it possible someone can host the HZXM_IPC_HI3518E_50H10L_S38_V4.02.R12.20140926_ALL 升.bin firmware somewhere? I am trying the camera on different firmware levels as I have the following issue:
I have a couple of these cameras in mini bullet style and have them connected Wirelessly and have no end of issues with RTSP streaming when the cameras are connected over WiFi. Doing some digging it appears to be that the cameras are enabled for multicast and reading upon that, multicast can cause no end of issues on WiFi and basically cause your wireless network to bomb out.
ifconfig shows:
Code:
Welcome to Monitor Tech.
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:12:12:75:59:CA
inet addr:192.168.0.33 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:12
eth2 Link encap:Ethernet HWaddr 7C:DD:90:7B:24:42
inet addr:192.168.0.33 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:25 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:154133 (150.5 KiB) TX bytes:10735 (10.4 KiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:5 errors:0 dropped:0 overruns:0 frame:0
TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3772 (3.6 KiB) TX bytes:3772 (3.6 KiB)
running the following commands disables multicast on the interfaces, and can be verified by running ifconfig again:
Code:
# ifconfig eth0 -multicast
# ifconfig eth2 -multicast
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:12:12:75:59:CA
inet addr:192.168.0.33 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:12
eth2 Link encap:Ethernet HWaddr 7C:DD:90:7B:24:42
inet addr:192.168.0.33 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MTU:1500 Metric:1
RX packets:0 errors:0 dropped:91 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:257383 (251.3 KiB) TX bytes:18764 (18.3 KiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:5 errors:0 dropped:0 overruns:0 frame:0
TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3772 (3.6 KiB) TX bytes:3772 (3.6 KiB)
Things then considerably improve and the cameras then do appear to work fine. I'm not a professional with Linux though and these commands arent persistant so have to be entered every time the camera reboots. It appears the file system is read only too by the root user so I dont even know if I can edit one of the config files somewhere and save it back so multicasting is turned off permamently.
The seller even sent me another camera to test with and I have got that plugged in over ethernet and I am going to setup iSpy to record that today during the day and see if that remains stable as I haven't tested that yet.
I may then have to use some PowerLine over Ethernet adapters to connect these to my network instead.
Some other posters have commented about RTSP streams being choppy on their mobiles but working fine on VLC, I have exactly the same experience, the low quality stream works fine but the high quality one isn't - even if setting the bitrate really low - which is dissapointing really.