firmware 6.08

Rayman.Chan

Well-Known Member
Manufacturer
Joined
Oct 7, 2013
Messages
1,459
Reaction score
994
Location
Shenzhen
Country
China
Dash Cam
mini0806, mini0806S, mini0903/0905, mini0906, mini0808
today we updated the bit rate in 0906 firmware so I can't hold to release it to you guys.

http://www.mini0906.com/firmware/FIRMWARE_20170608.zip

most software bugs we found until now have been sorted in this version.
but some small speck we need to figure out in next:
1, firmware version pop up on the upper row;
2,
3
 
the bit rate chart is:

Resolution..........super perfect...........perfect ............normal
1080+1080..........20M+16M...........14M+12M.........10M+8M
1080+720............20M+10M...........14M+8M..........10M+6M
1080P60.................30M....................24M.................20M
1080P30.................20M....................16M..................12M
720P60...................16M ....................12M..................10M
720P30...................12M.....................8M....................6M
 
On my drive last night i had a feeling i better bring the 0906 with me up in my apartment, seem like i hit that one bang on.

Will update right away.
 
Updated,,,,, i think this is a good excuse to go for a little drive.
 
@Rayman.Chan I just tested the firmware but there are missing video files unfortunately...
Did a drive with two stops and after the second stop (drive berfore second stop: very short distance, only 1:37 duration) it didn't record anything.
I guess it didn't shut down cleanly because of the short driving time, it also didnt show the shutdown screen and just went black, but the last file was still saved.
And now comes the weird part: It did turn on and write a log file but not a single video recording.
I had a look at the log files:

After the first stop, everything was ok:
Corresponding files:
20170608_181038.log (ok)
20170608_181041_0007A.MOV (ok)
20170608_181143_0008A.MOV (ok)

After the second stop:
20170608_181506.log (The date/time of the logfile is correct)
(no video files created)
Weird content of log:
[......]
(INFO: The bold part should be the time, but it shows 08XXXX, which is absolutely wrong.)
Line 1092: UIMovie_SetCustomFileName 2 20170608_081747_0003A uiPathId:0 SerialNum:3 FileNum:2
Line 1095: UIMovie_SetCustomFileName 1 20170608_081747_0003A uiPathId:1 SerialNum:3 FileNum:3 uSetPathCnt:2
Line 1096: UIMovie_SetCustomFileName 2 20170608_081747_0003B uiPathId:1 SerialNum:3 FileNum:3
Line 1167: Txt 11 filepathA = A:\FRONT\20170608_081747_0003A.MOV
Line 1168: Txt 21 filepathB = A:\REAR\20170608_081747_0003B.MOV
Line 1169: A:\FRONT\20170608_081747_0003A.MOV is exist
Line 1171: Txt filepath = A:\GPS\20170608_081747_0003.log
[.....]
a few minutes later (like max. 5 minutes)
[.....]
Line 3783: UIMovie_SetCustomFileName 1 20170608_084048_0026B uiPathId:0 SerialNum:27 FileNum:50 uSetPathCnt:49
Line 3784: UIMovie_SetCustomFileName 2 20170608_084148_0027A uiPathId:0 SerialNum:27 FileNum:50
Line 3787: UIMovie_SetCustomFileName 1 20170608_084148_0027A uiPathId:1 SerialNum:27 FileNum:51 uSetPathCnt:50
Line 3788: UIMovie_SetCustomFileName 2 20170608_084148_0027B uiPathId:1 SerialNum:27 FileNum:51
Line 3859: Txt 11 filepathA = A:\FRONT\20170608_084148_0027A.MOV
Line 3860: Txt 21 filepathB = A:\REAR\20170608_084148_0027B.MOV
Line 3861: A:\FRONT\20170608_084148_0027A.MOV is exist
Line 3863: Txt filepath = A:\GPS\20170608_084148_0027.log
[END OF DRIVE/LOG]

So the filename time increased by almost 30 minutes during 5 minutes of driveing
There is also an error right before it started with the strange time file names in the log that has something to do with timers (Line 1071):
Code:
[0m[31mERR:TM_End() Exceed max TM array!
[0m[31mERR:h264_close() H264Enc don't need to close, 1, 396
[0m
[31mERR:drv_setIstEvent() TIMER losing event [0x00001000]
[0m
[31mERR:drv_setIstEvent() TIMER losing event [0x00001000]
[0m
[31mERR:drv_setIstEvent() TIMER losing event [0x00001000]
[0m
[31mERR:drv_setIstEvent() TIMER losing event [0x00001000]

I've attached the log file
 

Attachments

  • weird_log_timer_losing.txt
    1 MB · Views: 1
I'm guessing that's going to need a reliable memory card - will get mine updated tomorrow!

Does the extra bitrate cause issues for closing the last rear file?

One thing I will say is that the 0906 has handled bad weather very well indeed - here's a clip of 5.27 from tonight when we went to vote!

 
Last edited:
Tested the new 0608 firmware.
:(Found a bug. When you use screen saver, you can't "wake up" by pressing power on/off button. Working fine when screen is on (toggle front, rear, off).
:peeking:Led light is still to dim, Can't see them at all, on a sunny day.
:inpain:Is it possible to build in a shut off delay on 3 sec. If you turn off the car, but leave the power on for radio. The second you start the car again, it shut down.
:singing:Nice shut down chime.
(y)(y)(y) High bit rate.

A request. How do I got the USB cable the are going from the front camera to the rear camera? It have a round connector at the rear end. I got 2 cars and like to be able to make an easy switch between them. I already got a power USB cable in place.

I have modified the camera with a new resistor, so I want to see if I could provoke a temperature shutdown on a nice warm summer day 25C. So I left the car facing the sun, kept the screen on the dash cam and no AC on. I was cooking :cry: so it drip, but got what I want @ 85C it shut down. Camera was hot and I measured the temp to 72C.
It make some funny buss sound before it shut down.

Strait after the shutdown I turn it on "select 15 sec screen off" and turn AC on and drove for 15 min without any shutdown.
Front.
Rear.
 
@Viking The connection cable is not a USB cable, probably some Novatek proprietary one
 
@Viking The connection cable is not a USB cable, probably some Novatek proprietary one
Whatever it's called, I will be pleased if I can get my finger in an extra one.
I was hoping there was a genius, that could guide me to an Ebay site.
If you don't ask you don't get an answer.
 
Would love to have a second one as well. Everytime I'm testing something I have to get into my car since I "hardwired" the rear cam and connection cable....
 
The strength of the LED's cant be fixed in firmware.
 
I have still problem with last file not getting saved.
error.JPG
 
Photo is named as "front 20170608_104504_0001A" and read as "20170608_104504_0002B" is it possible to get the number in front A and B to be the same.
Is it possible to get GPS and time written into Exif data.
 
Photo is named as "front 20170608_104504_0001A" and read as "20170608_104504_0002B" is it possible to get the number in front A and B to be the same.

are you using the latest firmware? it have been updated from 5.27 version.

here is my list just in minutes recording


├ FRONT
│ │ 20170608_113758_0001A.MOV
│ │ 20170608_114026_0002A.MOV
│ │ 20170608_114035_0003A.MOV
│ │ 20170608_115746_0004A.MOV
│ └ 20170608_115914_0005A.MOV
├ Novatek
│ └ LOG
│ │ 20170608_115743.log
│ │ 20170608_115911.log
│ │ 0003_dummy.log
│ │ 0004_dummy.log
│ │ 0005_dummy.log
│ │ 0006_dummy.log
│ │ 0007_dummy.log
│ │ 0008_dummy.log
│ │ 0009_dummy.log
│ │ 0010_dummy.log
│ │ 0011_dummy.log
│ │ 0012_dummy.log
│ │ 0013_dummy.log
│ │ 0014_dummy.log
│ │ 0015_dummy.log
│ │ 0016_dummy.log
│ │ 0017_dummy.log
│ │ 0018_dummy.log
│ │ 0019_dummy.log
│ │ 0020_dummy.log
│ │ 0021_dummy.log
│ │ 0022_dummy.log
│ │ 0023_dummy.log
│ │ 0024_dummy.log
│ │ 0025_dummy.log
│ │ 0026_dummy.log
│ │ 0027_dummy.log
│ │ 0028_dummy.log
│ │ 0029_dummy.log
│ │ 0030_dummy.log
│ │ 0031_dummy.log
│ └ 20170608_113754.log
├ GPS
│ │ 20170608_113758_0001.log
│ │ 20170608_114026_0002.log
│ │ 20170608_114035_0003.log
│ │ 20170608_115746_0004.log
│ └ 20170608_115914_0005.log
└ REAR
. │ 20170608_113758_0001B.MOV
. │ 20170608_114026_0002B.MOV
. │ 20170608_114035_0003B.MOV
. │ 20170608_115746_0004B.MOV
. └ 20170608_115914_0005B.MOV

(i am not sure why DCT auto removed the blank before characters so i have to add dots here)
 
Does the extra bitrate cause issues for closing the last rear file?

that will affect little but not visible.
the power off sequence was: no power -- record 2 seconds - still no power - save files - shut down
new power off sequence is: no power -- save files - waiting 2 seconds - still no power - shut down

so if you only drive a short trip and didn;t recharge the super cap enough, the last files will not be damaged.
but there is also limits, for example if you drive 1 minute the caps are only 88% recharged, you may also lost the ending files!
 
when you post logs use the insert function and select the code option and it won't change the formatting

Thanks Rick
 
Back
Top