Review-I'll be the guinea pig for the new SD59225U-HNI PTZ.

That may have the best shot at fixing it - I'll give it a try tomorrow...

I TFTP'd in DH_SD-Eos_EngSpnFrn_N_Stream3_V2.420.0001.0.R.20161220 with cfgRestore and oddly enough, it didn't get rid of the Life Stats, although it did reset them...

NAND: Check nand flash controller v610. found
Special NAND id table Version 1.36
Nand ID: 0x92 0xF1 0x80 0x95 0x40 0x7F 0x7F 0x7F
NAND_ECC_NONE selected by board driver. This is not recommended !!
128 MiB
partition file version 2
rootfstype squashfs root /dev/mtdblock7
In: serial
Out: serial
Err: serial
TEXT_BASE:81000000
Net: PHY found at 1
ETH0: PHY(phyaddr=-1, rmii) link UP: DUPLEX=FULL : SPEED=100M
MAC: E0-50-8B-26-74-DF
Using gmac device
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending through gateway 192.168.1.1Download Filename 'upgrade_info_7db780a713a4.txt'.Download to address: 0x84000000
Downloading: *
done
Bytes transferred = 213 (d5 hex)
config erased.
backup erased.
ETH0: PHY(phyaddr=-1, rmii) link UP: DUPLEX=FULL : SPEED=100M
MAC: E0-50-8B-26-74-DF
Using gmac device
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending through gateway 192.168.1.1Download Filename 'romfs-x.squashfs.img'.Download to address: 0x82000000
Downloading: *
done
Bytes transferred = 909376 (de040 hex)
Erasing update flag partition.

## Checking Image at 82000000 ...
Legacy image found
Image Name: romfs
Image Type: ARM Linux Standalone Program (gzip compressed)
Data Size: 909312 Bytes = 888 KiB
Load Address: 01200000
Entry Point: 01a00000
Verifying Checksum ... OK
Programing start at: 0x01200000
write : 100%
done
ETH0: PHY(phyaddr=-1, rmii) link UP: DUPLEX=FULL : SPEED=100M
MAC: E0-50-8B-26-74-DF
Using gmac device
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending through gateway 192.168.1.1Download Filename 'kernel.img'.Download to address: 0x82000000
Downloading: *
done
Bytes transferred = 2229712 (2205d0 hex)
Erasing update flag partition.

## Checking Image at 82000000 ...
Legacy image found
Image Name: kernel
Image Type: ARM Linux Firmware (uncompressed)
Data Size: 2229648 Bytes = 2.1 MiB
Load Address: 00d00000
Entry Point: 01200000
Verifying Checksum ... OK
Programing start at: 0x00d00000
write : 100%
done
ETH0: PHY(phyaddr=-1, rmii) link UP: DUPLEX=FULL : SPEED=100M
MAC: E0-50-8B-26-74-DF
Using gmac device
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending through gateway 192.168.1.1Download Filename 'user-x.squashfs.img'.Download to address: 0x82000000
Downloading: *
done
Bytes transferred = 14282816 (d9f040 hex)
Erasing update flag partition.

## Checking Image at 82000000 ...
Legacy image found
Image Name: user
Image Type: ARM Linux Standalone Program (gzip compressed)
Data Size: 14282752 Bytes = 13.6 MiB
Load Address: 02200000
Entry Point: 03a80000
Verifying Checksum ... OK
Programing start at: 0x02200000
write : 100%
done
ETH0: PHY(phyaddr=-1, rmii) link UP: DUPLEX=FULL : SPEED=100M
MAC: E0-50-8B-26-74-DF
Using gmac device
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending through gateway 192.168.1.1Download Filename 'web-x.squashfs.img'.Download to address: 0x82000000
Downloading: *
done
Bytes transferred = 5816384 (58c040 hex)
Erasing update flag partition.

## Checking Image at 82000000 ...
Legacy image found
Image Name: web
Image Type: ARM Linux Standalone Program (gzip compressed)
Data Size: 5816320 Bytes = 5.5 MiB
Load Address: 01a00000
Entry Point: 02200000
Verifying Checksum ... OK
Programing start at: 0x01a00000
write : 100%
done
ETH0: PHY(phyaddr=-1, rmii) link UP: DUPLEX=FULL : SPEED=100M
MAC: E0-50-8B-26-74-DF
Using gmac device
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending through gateway 192.168.1.1Download Filename 'partition-x.cramfs.img'.Download to address: 0x82000000
Downloading: *
done
Bytes transferred = 4160 (1040 hex)
Erasing update flag partition.

## Checking Image at 82000000 ...
Legacy image found
Image Name: partition
Image Type: ARM Linux Standalone Program (gzip compressed)
Data Size: 4096 Bytes = 4 KiB
Load Address: 00500000
Entry Point: 00600000
Verifying Checksum ... OK
Programing start at: 0x00500000
write : 100%
done
ETH0: PHY(phyaddr=-1, rmii) link UP: DUPLEX=FULL : SPEED=100M
MAC: E0-50-8B-26-74-DF
Using gmac device
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending through gateway 192.168.1.1Download Filename 'custom-x.squashfs.img'.Download to address: 0x82000000
Downloading: *
done
Bytes transferred = 106560 (1a040 hex)
Erasing update flag partition.

## Checking Image at 82000000 ...
Legacy image found
Image Name: custom
Image Type: ARM Linux Standalone Program (gzip compressed)
Data Size: 106496 Bytes = 104 KiB
Load Address: 00600000
Entry Point: 00980000
Verifying Checksum ... OK
Programing start at: 0x00600000
write : 100%
done
ETH0: PHY(phyaddr=-1, rmii) link UP: DUPLEX=FULL : SPEED=100M
MAC: E0-50-8B-26-74-DF
Using gmac device
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending through gateway 192.168.1.1Download Filename 'pd-x.squashfs.img'.Download to address: 0x82000000
Downloading: *
done
Bytes transferred = 49216 (c040 hex)
Erasing update flag partition.

## Checking Image at 82000000 ...
Legacy image found
Image Name: pd
Image Type: ARM Linux Standalone Program (gzip compressed)
Data Size: 49152 Bytes = 48 KiB
Load Address: 00980000
Entry Point: 00d00000
Verifying Checksum ... OK
Programing start at: 0x00980000
write : 100%
done
ETH0: PHY(phyaddr=-1, rmii) link UP: DUPLEX=FULL : SPEED=100M
MAC: E0-50-8B-26-74-DF
Using gmac device
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending through gateway 192.168.1.1Download Filename '.FLASHING_DONE_STOP_TFTP_NOW'.Download to address: 0x82000000
Downloading: *
done
partition file version 2
rootfstype squashfs root /dev/mtdblock7
fail to load bootargsParameters.txt
fail to load bootargsParameters.txt file
get bootargs info failed
cmdLine mem=256M console=ttyS0,115200 root=/dev/mtdblock7 rootfstype=squashfs
ETH0: PHY(phyaddr=-1, rmii) link UP: DUPLEX=FULL : SPEED=100M
MAC: E0-50-8B-26-74-DF
 
Any suggestion how to best set up the target area and target filters (min and max sizes) in my scene? Is there any guideline for best detection in IVS?

View attachment 18413


Change the arrow to up/down. (Start drawing from the other direction to change the movement direction.)
Make it a bit more square sized.

Set to appears or crosses.

Set the min size to a bit bigger then the bricks.
Max, a bit bigger then a car up close.

Go for a walk/quick drive and test or wait for a car to pass. :)
Rinse and repeat your adjustments until it behaves roughly how you want it to, eg ignore a cat but follow a person.

Make sure the green movement box is tracking people/things as they move, if it doesn't appear, adjust the contrast a bit more, you want the camera to already know stuff is moving by the time the object crosses into the trigger point. (Sometimes you have to restart the camera for it to properly take affect).

And LOL, say a few of you guys playing with my toy SD29 today. haha
 
Last edited:
  • Like
Reactions: Frank van der Heide
Change the arrow to up/down. (Start drawing from the other direction to change the movement direction.)
Make it a bit more square sized.

Set to appears or crosses.

Set the min size to a bit bigger then the bricks.
Max, a bit bigger then a car up close.

Go for a walk/quick drive and test or wait for a car to pass. :)
Rinse and repeat your adjustments until it behaves roughly how you want it to, eg ignore a cat but follow a person.

Make sure the green movement box is tracking people/things as they move, if it doesn't appear, adjust the contrast a bit more, you want the camera to already know stuff is moving by the time the object crosses into the trigger point.

And LOL, say a few of you guys playing with my toy SD29 today. haha

Thanks, I will follow your suggestions. Never figured that the way you draw the box defines the movement direction. That's an eye opener. I will test it and give my feedback here. Thanks again.

And yeah, I'm one who looked at your setup on your PTZ. Hehehe, curiosity kills the cat ;-)
 
Last edited:
Thanks, I will follow your suggestions. Never figured that the way you draw the box defines the movement direction. That's an eye opener for me. I will test it and give my feedback here. Thanks again.

And yeah, I'm one who looked at your setup on your PTZ. Hehehe, curiosity kills the cat ;-)

Haha thats my baby test one, the login is limited but lets you play with the PTZ settings etc.
She is there until I bring my SD59 back from work. :)

Camera is free to fiddle with right now, seems like you logged in at the same time as someone in Cali.
 
  • Like
Reactions: Frank van der Heide
The plugs are 34.925mm (inside) (1 3/8 inch) - Dahua has detailed drawings on all of their mounts if you search for it - I think the back of the corner mount was 35mm...
 
@beingaware Can we get these back with the images blacked out if the camera owner is really that bent about it?? I just got mine yesterday and was going to reference what you changed as a testing point.

Screen Shot 2017-05-17 at 7.50.34 pm.png Screen Shot 2017-05-17 at 8.13.20 pm.png Screen Shot 2017-05-17 at 7.50.21 pm.png Screen Shot 2017-05-17 at 7.50.04 pm.png Screen Shot 2017-05-17 at 7.49.56 pm.png Screen Shot 2017-05-17 at 7.49.50 pm.png

The two different IR settings are dependant on your max usage range.
I personally would keep it turned down but you'll need to balance it to give AF and AutoTracking the best chance.

Re max focal limit, you can leave that unlimited unless your max target range is less then 200m, in which case turning on the limit will speed up AF seek rate.
 
View attachment 18432 View attachment 18433 View attachment 18434 View attachment 18435 View attachment 18436 View attachment 18437

The two different IR settings are dependant on your max usage range.
I personally would keep it turned down but you'll need to balance it to give AF and AutoTracking the best chance.

Re max focal limit, you can leave that unlimited unless your max target range is less then 200m, in which case turning on the limit will speed up AF seek rate.

Why did you set the bitrate to 4096 Kbps? Doesn't 8192 Kbps give more detail? I have only 3 cams on my Gigabit switch, so speed should not be an issue. Or does maxing out the bitrate affect AF or tracking in a negative way?
 
Last edited:
What size screws are you guys using to secure the mounting arm to wood? Will be mounting to 8x8" dock post
 
What size screws are you guys using to secure the mounting arm to wood? Will be mounting to 8x8" dock post

As big as will fit and the best quality you can get your hands on. Even better if they are cap screws with security heads. Don't skimp on the hardware. :winktongue:
 
Why did you set the bitrate to 4096 Kbps? Doesn't 8192 Kbps give more detail? I have only 3 cams on my Gigabit switch, so speed should not be an issue. Or does maxing out the bitrate affect AF or tracking in a negative way?

Was to help stop lag while I was assisting that camera Remotely, their upload to me was struggling.

I have mine set to 6mbps usually.
 
what happened to
Agree with everyone all on all counts. We will persevere.

My install was interrupted by my crazy neighbor, for whom these cameras are being installed for.

@Solar Deity, what happened to you? I was hoping for some help after your last message about assisting to help setup IVS and Autotracking. Your previous explanation was really helpfull, so i was actually hoping for more ;-)

Care to share your settings/guide?
 
Last edited:
Reseating my camera module didn't help anything - The optics in the module are all internal - The front of the camera is nothing more than a "window" so even if it were off somehow, it probably wouldn't make a difference. I did it anyway, and no luck.

It's also dropping packets, so there is more going on with this mystery cam than just hidden menu settings and focus problems...