Auto tracking ptz ip camera and MINI PTZ IP Camera Update file

Code: 
[filecnt]
cnt=11
[file0]
name=ipnc.tgz
path=/home
version=12_0.0.0.0
md5sum=48b77bc5d887c3184e3ca4d73c423e85
model=XXXXXX
[file1]
name=S90ipnc
path=/etc/init.d
version=12_0.0.0.0
md5sum=b11c6be2922c5a37060e859f6b31372e
model=XXXXXX
[file2]
name=fsck.vfat
path=/sbin
version=12_0.0.0.0
md5sum=7cb8bd01fa05972701d903ec1dc3582f
model=XXXXXX
[file3]
name=mkfs.vfat
path=/sbin
version=12_0.0.0.0
md5sum=b9fae743a801887b10c152260ec8d7f3
model=XXXXXX
[file4]
name=exfat.ko
path=/lib/modules/3.10.73/extra
version=12_0.0.0.0
md5sum=4dd2da528abed7d8f87c36dcbd6562b5
model=XXXXXX
[file5]
name=M342_MiniPtz.bin
path=/home
version=12_0.0.0.0
md5sum=7a87cd4c61b7c43c8ce9e76ee2b5178b
model=XXXXXX
[file6]
name=ar0230.ko
path=/lib/modules/3.10.73/extra
version=12_0.0.0.0
md5sum=8e7eaee122af67b22cc460b0fd1a034b
model=XXXXXX
[file7]
name=M342_ZoomCam.bin
path=/home
version=12_0.0.0.0
md5sum=32dfc8f3c34be7d9737613909f3f6604
model=XXXXXX
[file8]
name=STM32F030F4_MiniPtz.bin
path=/home
version=12_0.0.0.0
md5sum=4368187d474d3a391c800b1d0db8455e
model=XXXXXX
[file9]
name=STM32F030F4_PtContrl.bin
path=/home
version=12_0.0.0.0
md5sum=478efb81497b6c38c6e09e3d6ccc0fa0
model=XXXXXX
[file10]
name=web.tgz
path=/home
version=12_0.0.0.0
md5sum=0553411cbf78f1a9388a6f59f3a67d6c
model=XXXXXX

*edit*
Is there a release note for this firmware?
What models, with what sensors, is it built for?
There does appear to be a lot of risk applying Huisun firmware as it doesn't check the models properly and can result in a bricked camera.
 
@YUNCHCCTV Thanks for the extra info about the changes in that firmware.
I can see that there are improvements in how the SD card is handled, better (non-Busybox) support for the vFAT file system.
And I can see that the file supports a wide range of sensors, and that both imx122 and imx322 are supported.
I think I'll try the update tonight.

I have added a pseudo SD card to the camera via an NFS share, but although the camera sees it OK, formats it OK, and files from the camera can be saved to it OK, it doesn't save image captures or videos, so maybe this new firmware will fix that.
 
Last edited by a moderator:
I have added a pseudo SD card to the camera via an NFS share, but although the camera sees it OK, formats it OK, and files from the camera can be saved to it OK, it doesn't save image captures or videos, so maybe this new firmware will fix that.
Click to expand...
Wow!
And it did. I'm now seeing capture files and video being stored on a remote vfat image file accessed as an NFS share on a NAS.
As a proof of concept it looks interesting.
I have no idea yet if it will be reliable or even usable.
But it's interesting ...

For the Linux techies amongst us -
Mount a NAS NFS share to camera /tmp
Code: 
mount -t nfs -o nolock 192.168.1.201:/cctv1 /tmp
This share holds a 4GB (or bigger) file1.img created with a Linux box (could be the camera, but would take too long with the 100Mbps LAN connection) using
Code: 
dd if=/dev/zero of=/NAS_NFS_share/file1.img bs=1MiB count=4k

Then in the camera
Code: 
mkfs.vfat /tmp/file1.img
Create a loop device (no others in use)
Code: 
losetup /dev/loop0 /tmp/file1.img
Link it to the device name of the SD card
Code: 
ln -s /dev/loop0 /dev/mmcblk0
And just for good measure, mount this where a real one would normally be, though the camera seems to do this automatically anyway when it sees /dev/mmcblk0 appear
Code: 
mount /dev/mmcblk0 /ipnc/sd

Then in the camera web GUI, under Storage | Storage Management the pseudo card should appear.
Select it and format it and it should change to 'Available'

Code: 
#
#
# losetup -a
/dev/loop0: 0 /tmp/file1.img
# mount
rootfs on / type rootfs (rw)
/dev/root on / type jffs2 (rw,sync,relatime)
devtmpfs on /dev type devtmpfs (rw,relatime,size=61740k,nr_inodes=15435,mode=755)
proc on /proc type proc (rw,relatime)
tmpfs on /tmp type tmpfs (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw,relatime)
tmpfs on /run type tmpfs (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
192.168.1.201:/cctv1 on /tmp type nfs (rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,nolock,proto=tcp,port=2049,timeo=70,retrans=3,sec=sys,local_lock=all,addr=192.168.1.201)
none on /ipnc type tmpfs (rw,relatime)
none on /ipnc/snapshot type tmpfs (rw,relatime,size=4096k)
none on /ipnc/log type tmpfs (rw,relatime,size=2048k)
none on /ipnc/ringbuf type tmpfs (rw,relatime,size=5120k)
/dev/mmcblk0 on /ipnc/sd type exfat (rw,noatime,nodiratime,fmask=0022,dmask=0022,iocharset=utf8,namecase=0,errors=remount-ro)
#
#
# ls -al /ipnc/sd
total 584800
drwxr-xr-x    2 root     root         32768 Jul 27 04:03 .
drwxrwxrwt   11 root     root           680 Jul 27 03:44 ..
-rwxr-xr-x    1 root     root     130665137 Jul 27 03:52 000001.h264
-rwxr-xr-x    1 root     root        673700 Jul 27 03:49 000001.jpg
-rwxr-xr-x    1 root     root     130706301 Jul 27 03:55 000002.h264
-rwxr-xr-x    1 root     root        673707 Jul 27 03:49 000002.jpg
-rwxr-xr-x    1 root     root     130604151 Jul 27 03:59 000003.h264
-rwxr-xr-x    1 root     root        673716 Jul 27 03:49 000003.jpg
-rwxr-xr-x    1 root     root     130636502 Jul 27 04:02 000004.h264
-rwxr-xr-x    1 root     root        673557 Jul 27 03:50 000004.jpg
-rwxr-xr-x    1 root     root      45096378 Jul 27 04:03 000005.h264
-rwxr-xr-x    1 root     root        673146 Jul 27 03:50 000005.jpg
-rwxr-xr-x    1 root     root        673909 Jul 27 03:50 000006.jpg
-rwxr-xr-x    1 root     root        673158 Jul 27 03:51 000007.jpg
-rwxr-xr-x    1 root     root        673385 Jul 27 03:51 000008.jpg
-rwxr-xr-x    1 root     root        673724 Jul 27 03:51 000009.jpg
-rwxr-xr-x    1 root     root        673769 Jul 27 03:52 000010.jpg
-rwxr-xr-x    1 root     root        673926 Jul 27 03:52 000011.jpg
-rwxr-xr-x    1 root     root        673685 Jul 27 03:52 000012.jpg
-rwxr-xr-x    1 root     root        673923 Jul 27 03:53 000013.jpg
-rwxr-xr-x    1 root     root        674075 Jul 27 03:53 000014.jpg
-rwxr-xr-x    1 root     root        676678 Jul 27 03:53 000015.jpg
-rwxr-xr-x    1 root     root        676541 Jul 27 03:54 000016.jpg
-rwxr-xr-x    1 root     root        676757 Jul 27 03:54 000017.jpg
-rwxr-xr-x    1 root     root        676398 Jul 27 03:54 000018.jpg
-rwxr-xr-x    1 root     root        676450 Jul 27 03:55 000019.jpg
-rwxr-xr-x    1 root     root        676160 Jul 27 03:55 000020.jpg
-rwxr-xr-x    1 root     root        675965 Jul 27 03:55 000021.jpg
-rwxr-xr-x    1 root     root        675383 Jul 27 03:56 000022.jpg
-rwxr-xr-x    1 root     root        675212 Jul 27 03:56 000023.jpg
-rwxr-xr-x    1 root     root        674699 Jul 27 03:56 000024.jpg
-rwxr-xr-x    1 root     root        675111 Jul 27 03:57 000025.jpg
-rwxr-xr-x    1 root     root        674741 Jul 27 03:57 000026.jpg
-rwxr-xr-x    1 root     root        674046 Jul 27 03:57 000027.jpg
-rwxr-xr-x    1 root     root        674019 Jul 27 03:58 000028.jpg
-rwxr-xr-x    1 root     root        673707 Jul 27 03:58 000029.jpg
-rwxr-xr-x    1 root     root        675558 Jul 27 03:58 000030.jpg
-rwxr-xr-x    1 root     root        674775 Jul 27 03:59 000031.jpg
-rwxr-xr-x    1 root     root        674760 Jul 27 03:59 000032.jpg
-rwxr-xr-x    1 root     root        673541 Jul 27 03:59 000033.jpg
-rwxr-xr-x    1 root     root        673249 Jul 27 04:00 000034.jpg
-rwxr-xr-x    1 root     root        672659 Jul 27 04:00 000035.jpg
-rwxr-xr-x    1 root     root        672019 Jul 27 04:00 000036.jpg
-rwxr-xr-x    1 root     root        671516 Jul 27 04:01 000037.jpg
-rwxr-xr-x    1 root     root        671206 Jul 27 04:01 000038.jpg
-rwxr-xr-x    1 root     root        670770 Jul 27 04:01 000039.jpg
-rwxr-xr-x    1 root     root        669891 Jul 27 04:02 000040.jpg
-rwxr-xr-x    1 root     root        669686 Jul 27 04:02 000041.jpg
-rwxr-xr-x    1 root     root        669245 Jul 27 04:02 000042.jpg
-rwxr-xr-x    1 root     root        668829 Jul 27 04:03 000043.jpg
-rwxr-xr-x    1 root     root        668265 Jul 27 04:03 000044.jpg
-rwxr-xr-x    1 root     root        667448 Jul 27 04:03 000045.jpg
-rwxr-xr-x    1 root     root          3072 Jul 27 04:03 logs.db
-rwxr-xr-x    1 root     root         10240 Jul 27 04:03 records.db
-rwxr-xr-x    1 root     root             0 Jul 27 04:03 records.db-journal
#
 
  • Like
Reactions: ilrider78, vasycara and EyePeeKamz
Unfortunately, the firmware file appears to be passworded therefore it won't extract. Does anyone know the password?
 
A word of caution here on updating with the firmware in this thread.
A forum member used the firmware posted at the start of this thread to update a Mini PTZ V2 and it bricked.
Apparently dead, no LAN response, no movement.
Using the slightly cumbersome method of forum PMs, which the member managed to follow pretty well for the needed serial console commands, the camera has been recovered and appears to be working normally again.
It does seem that the Huisun firmware update process has a finite failure rate.
I believe @klasipca was speculating that the bricking problems may have been related to the use of an alternate sensor, but I think that link was not proven.

I know there are others that have bricked Mini PTZ (V2 and V1) after firmware updates.
It might be interesting to hear about these, and maybe set up some how-to's to fix them.

By the way - fixing this specific Mini PTZ V2 was in fact pretty straightforward as the Amboot bootloader didn't have the problematic hardware reset when changing the kernel boot command that @pozzello 's camera had when I unbricked it. https://www.ipcamtalk.com/showthread.php/12454-Unbricking-the-Mini-PTZ-V2
 
Last edited by a moderator:
  • Like
Reactions: bob2701, Q™ and vasycara
With help, I was able to get to the file, however reading the cautions and etc...think I'll leave it alone. Would be nice if they would simply put the firmware updates in a specific place like all the rest of the hardware manufacturers. Still a newbie here so I can't respond to PM's quite yet due to the rules but the advice was greatly appreciated. My issues revolve with the YC-HD785R-20X and my desire to fix the auto-tracking issues. Jumps around way too much and many times in the wrong direction.
 
  • Like
Reactions: alastairstevenson
I tried to update Huisun Mini PTZ V2 and it bricked with new version . Mini PTZ V2 died after reboot..Nothing in ping anything in telnet. Nothing in SADP. I thought it was completely dead..am accessed in UART, and saw that activity was, so it was not completely dead.
With the help of Mr. Alastairstevenson and I thank you on this way, after several conversations we managed to start Mini PTZ V2.
ip mini cam back to life and everything is ok.
Many thanks to Mr. Alastairstevenson for help.
 
Last edited by a moderator:
@dgrant
Unfortunately, the firmware file appears to be passworded therefore it won't extract. Does anyone know the password?
Click to expand...
Just to clear up any misconception - the camera firmware update doesn't need you to extract any files from the firmware distribution - it handles the password-protected ZIP file directly.
The extraction password is only needed if the contents are of interest.
 
Last edited by a moderator:
hi, i have upgrade my camera imporx imp hc7286 k20x with firmware and it's all ok, lot of thanks at Mr. Alastairstevenson and @YUNCHCCTV.
On the other hand I have no more the icon of auto tracking in Web plugin

(Exactly icon of auto tracking was replaced by that of the auto-scan)
Have you one idea ?
 
Last edited by a moderator:
Don't have one of these but a big shout-out to @YUNCHCCTV on this.

We get lots of spammers or resellers on here offering no or little value. Yunch resells Huisun and then offers these updates for all to use even those who haven't bought from them. If Yunch keeps this up and helps out with people's issues on here then I will be buying my next PTZ from them.
 
Last edited by a moderator:
  • Like
Reactions: alastairstevenson
I'll buy one from 'ol Yunchie too when the v3 is released.
 
  • Like
Reactions: user503
Yep - we cloned your bricked Mini PTZ V2 with a copy of the entire app firmware from what was originally (!) @pozzello 's camera to unbrick it, which was itself cloned from his other Mini PTZ V2 to unbrick that. Clones r'Us.
That firmware includes the camera hardware definitions and options that would have been written during manufacture.
And it has '0' for audio and alarm.
So - if you are careful, you should be able to change the hardware definitions of your camera using the altered config_hw.ini file that I sent you via PM.
It's just a text file.
 
Last edited by a moderator:
  • Like
Reactions: vasycara
Thank you, I will come back with the result.
 
Last edited by a moderator:
Hi,

Then last return, after several test and diverse exchange of firmware, I put back last time the last one firmware, and miracle the tab of auto-tracking is reappeared.

On the other hand I have one concerns, with the autofocus:

When I select on 6M or infinity the image is fuzzy

Further to the test under ipcdebugger, which moreover is not to end normally.

have you an solution ?

lot of thanks
 
You must log in or register to reply here.
Top Bottom