alastairstevenson
Staff member
Do you think that's significant? Repeatable?
How's the power budget on your PoE switch?
5 MegaGixel 1/1.8" low light destroyer for $90-AVOID LONGSE JUNK
- Thread starter klasipca
- Start date
How's the power budget on your PoE switch?
It's the only POE item on the switch, out of four ports available.
The other two cameras on the switch have separate 12V power supplies.
Cicely e-mailed back later last night, authorizing the return.
Now I'm just waiting on the RA number to put on the package.
I'll pay shipping one way back to them, and they'll pay coming to me.
Both my cameras are now losing the video stream(s) but one more than the other. Really thinking this firmware has issues because they didn't do this before. Need to try and telnet in to look at the logs.
fenderman
Staff member
- Mar 9, 2014
- 36,892
- 21,407
Q™
IPCT Contributor
Ahhhh yes...
3516A_IMX178_W_6.1.44.2
"Improved stability and fix the problems"
Should be labeled "...fix a few of the problems but we'll leave the rest so we have something to do in the future..."
3516A_IMX178_W_6.1.44.2
"Improved stability and fix the problems"
Should be labeled "...fix a few of the problems but we'll leave the rest so we have something to do in the future..."
Are you in the US? How much was the return shipping and what carrier did you use?
I installed that firmware two weeks ago. I thought it might have fixed my problems but after two weeks it just dropped its network connection like it always does after a week or so. Three different firmware updates haven't fixed my problems. I think the hardware is just junk.
Q™
IPCT Contributor
It would actually be quite impossible for @zeoclang to know which defect(s) any firmware update actually resolved, unless zeoclang was privy to the specific defect(s) and/or enhancements which the developer claimed a given firmware update addressed. To explain this in simpler terms, just so you understand, and as we say in America, zeoclang really doesn't know Jack Shit. But hey...that's OK...I don't know Jack Shit about a lot of stuff either. But the apparent difference between me and zeoclang is that I try not to make definitive statements about issues I don't know Jack Shit about.
alastairstevenson
Staff member
That may suggest the problems are not linked to the firmware.
I know it's a one-off anecdotal experience - but over many months I've see zero problems with my S500, no freezes, no reboots, with firmware updated as it's become available.
I installed the 3516A_IMX178_W_6.1.44.2 version about 6 weeks ago.
It may be worth doing some trouble-shooting by monitoring some of the debug interfaces.
These are read-only on telnet ports 401-404 and don't require any logon.
401 is alarm status, and probably not relevant.
402 is network-related and probably is relevant.
Example :
Code:
alastair@PC-I5 ~ $ telnet 192.168.254.16 402
Trying 192.168.254.16...
Connected to 192.168.254.16.
Escape character is '^]'.
[Trace]: eth0 LINK up
Auto_Loop 5753: getaddrinfo start
Auto_Loop 5766: getaddrinfo end
No arp reply received for this address
[Trace]: eth0 LINK up
No arp reply received for this address
[Trace]: eth0 LINK up
No arp reply received for this address
[Trace]: eth0 LINK up
No arp reply received for this address
[AddSchedule] gAlarmSchedules[1].nDuration = 10
Debug Recieved message:3 from 2
[ProcFileMsg1].........FILE_MSG_WRITE
Debug pMsg->shmidx=1
Debug Message process success
Debug File write
DEBUG SemaPhore_Wait-77: Semaphore Wait
DEBUG SemaPhore_Post-96: Semaphore Post
MAC=00:00:1b:06:b2:f3
[Trace]: eth0 LINK up
No arp reply received for this address
[Trace]: eth0 LINK up
No arp reply received for this address
[Trace]: eth0 LINK up
Auto_Loop 5753: getaddrinfo start
Auto_Loop 5766: getaddrinfo end
No arp reply received for this address
[Trace]: eth0 LINK up
No arp reply received for this address
[Trace]: eth0 LINK up
No arp reply received for this address
[Trace]: eth0 LINK up
No arp reply received for this address
[Trace]: eth0 LINK up
No arp reply received for this address
[AddSchedule] gAlarmSchedules[1].nDuration = 10
Debug Recieved message:3 from 2
[ProcFileMsg1].........FILE_MSG_WRITE
Debug pMsg->shmidx=1
Debug Message process success
Debug File write
DEBUG SemaPhore_Wait-77: Semaphore Wait
DEBUG SemaPhore_Post-96: Semaphore Post
MAC=00:00:1b:06:b2:f3
[Trace]: eth0 LINK up
No arp reply received for this address
[AddSchedule] gAlarmSchedules[1].nDuration = 10
Debug Recieved message:3 from 2
[ProcFileMsg1].........FILE_MSG_WRITE
Debug pMsg->shmidx=1
Debug Message process success
Debug File write
DEBUG SemaPhore_Wait-77: Semaphore Wait
DEBUG SemaPhore_Post-96: Semaphore Post
MAC=00:00:1b:06:b2:f3
[Trace]: eth0 LINK up
Auto_Loop 5753: getaddrinfo start
Auto_Loop 5766: getaddrinfo end
No arp reply received for this address
[Trace]: eth0 LINK up
No arp reply received for this address
[Trace]: eth0 LINK up
No arp reply received for this address
[Trace]: eth0 LINK up
No arp reply received for this address
[Trace]: eth0 LINK up
[AddSchedule] gAlarmSchedules[1].nDuration = 10
Debug Recieved message:3 from 2
[ProcFileMsg1].........FILE_MSG_WRITE
Debug pMsg->shmidx=1
Debug Message process success
Debug File write
DEBUG SemaPhore_Wait-77: Semaphore Wait
No arp reply received for this address
DEBUG SemaPhore_Post-96: Semaphore Post
MAC=00:00:1b:06:b2:f3
[Trace]: eth0 LINK up
No arp reply received for this address
[Trace]: eth0 LINK up
Auto_Loop 5753: getaddrinfo start
Auto_Loop 5766: getaddrinfo end
No arp reply received for this address
[Trace]: eth0 LINK up
No arp reply received for this address
[Trace]: eth0 LINK up
No arp reply received for this address
^]close
telnet> close
Connection closed.
alastair@PC-I5 ~ $404 is IP configuration but may be worth listening to.
And with the shell root password, the ifconfig error counts will give an indication of any grumbling network connectivity problems :
Code:
alastair@PC-I5 ~ $
alastair@PC-I5 ~ $ telnet 192.168.254.16
Trying 192.168.254.16...
Connected to 192.168.254.16.
Escape character is '^]'.
(none) login: root
Password:
Welcome to HiLinux.
None of nfsroot found in cmdline.
~ # ifconfig
eth0 Link encap:Ethernet HWaddr 00:00:1B:06:B2:F3
inet addr:192.168.254.16 Bcast:192.168.254.255 Mask:255.255.255.0
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:474172603 errors:0 dropped:24 overruns:0 frame:0
TX packets:252301203 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:789168739 (752.6 MiB) TX bytes:4197502232 (3.9 GiB)
Interrupt:57
~ #Q™
IPCT Contributor
I've too have had similar positive experience with my LRDC60S500 (and LBW90S500) cameras. Although I did have a rebooting issue at one time with one of my LRDC60S500 which -- after getting frustrated pissed off at the manufacturer -- turned out to be a bad POE switch port. I'm not suggesting that your camera is not defective, but your issue sounds as if it may possibly be power or network related. Sorry that I haven't read through all of your posts to this topic, but have you tried hooking an AC adapter to the camera instead of using a POE power source? Have you tried a different network switch? Have you replaced the network cable?
You are making the mistake of reading too much into my comment. I never claimed to know the specifics of what the firmware update addresses. The firmware states it "improved stability and fix the problems" but stability problems are still present on my camera after three updates. That is a factual statement.
@alastairstevenson Thanks for that information I will attempt to take a look at the logs. However, I don't know how successful I will be since my camera often fails to talk to the switch. The PoE port power status light will stay on showing the camera is getting power but the link light is dead. I have tried two switches and multiple network cables.
I should probably do like @VorlonFrog has done and return it but I'm not too keen on paying the return shipping costs.
I should probably do like @VorlonFrog has done and return it but I'm not too keen on paying the return shipping costs.
alastairstevenson
Staff member
Understood. But if you are lucky to might just see a shout before it goes under.
The ifconfig error counts might be interesting - I'll PM you the root password if you feel motivated to check them.
Actually, I've only de-installed and boxed it up this weekend. I've been dealing with a severely nasty cold and a LOT of issues at work. I'll just see what UPS and FedEx ask, first. If they're just plain outrageous/unreasonable, I'll do some deeper research to find an international shipper.
EDIT: Holy crap, FedEx wants more than $100 to ship a 6x6x6 box weighing less than two pounds!! That's insane in this day and age. UPS wants a little over $100 as well. Finally, DHL only wants about $75.
Last edited:
nayr
IPCT Contributor
Cheap shipping is only available FROM china; thats pretty much normal for shipping too china.. insane? given how little they import from us vs how much we import from them it seems about right considering.
Dont ever plan on returning anything to china; if they dont have a USA distributor you can return it too (extremely rare but it does happen) then you might as well throw it in the trash before ever attempting a warranty claim.
Dont ever plan on returning anything to china; if they dont have a USA distributor you can return it too (extremely rare but it does happen) then you might as well throw it in the trash before ever attempting a warranty claim.
Q™
IPCT Contributor
It cost me about $90 to ship it back, but it only required three days to arrive back with Cicely at Longse. They quickly returned what appears to be the same camera shell, but I'm willing to bet it has new guts inside. It arrived with the original 5.1.51.3-160113 firmware, which I quickly upgraded to the latest HeroSpeed release, for ease of operation. (That older Windows 8 style Metro interface is so ridiculously clunky and AOL-ish.) Anyway, it's re-configured, re-installed, and working well with Blue Iris, for the time being. I'll definitely let you know if it starts acting up again. I'm not willing to ship it back to China a second time, honestly. If I had to part with it Q, I'd want at least $50.
I've tried this on both of mine and on every port (except default telnet) I get an endless loop of:
[Trace]: eth0 LINK up
No arp reply received for this address
This is when they are both up and functioning "normally"
alastairstevenson
Staff member