EDIT:
Please ignore the following post. The V0.64 seems to work as intended. See my last posting for the reason why I had the described issue.
Innovv released the new V0.64 firmware, which allows to switch off wifi automatically after some minutes. I will report about this feature in a different thread.
During my tests of this new feature, I discovered a behaviour, which may render the new firmware useless.
When doing tests with my spare K2, it is connected to an external power supply. Means the yellow and the read cable are connected to 12V and I use the button on top of the K2 to start it up or shut it down. Going this way, the new V0.64 firmware works as intended.
But if I simulate the normal operation in a motorbike and connect/disconnect the yellow cable to start/stop the K2, it automatically shut down some seconds after startup.
I checked the logs and found this.
[35mMode {MOVIE} Open end Auto channel choose ch:1 [31mERR:ICF_FC_TimerTrigProc() trigger interval shorter than process time!! 1 [0mgNHC_filetype = 4! normal pathid=0,=A:\INNOVV_K2\VIDEO\20200110_121443_FP.MP4 [32m thm=0xa6005c80 0x1462 [0m[0] name=A:\INNOVV_K2\VIDEO\20200110_121443_FP.MP4 [31mERR:TM_End() Exceed max TM array! [0m[31mAP ready, total period = 4128093 us [0m[37mCHK: 1618, UIMenuWndWiFiMobileLinkOK_OnCustom1[0m gbGsensorTrig :0 RecType_2p: 3 Set Crash!!! send lock file msg 00 Gsensor Power On Rec:0 usbPlug:1 Gsensor Power On Rec:1 usbPlug:1 send locate failed 02 [37mCHK: 289, Save_MenuInfo[0m kick[f0] gNHC_filetype = 4! normal pathid=1,=A:\INNOVV_K2\VIDEO\20200110_121445_RP.MP4 [1] name=A:\INNOVV_K2\VIDEO\20200110_121445_RP.MP4 [1]Queue: 5 kick[f1] [0]Queue: 5 [0]stillBlock = 4 Gsensor Power On Rec:2 usbPlug:1 Gsensor Power On Rec:3 usbPlug:1 Gsensor Power On Rec:4 usbPlug:1 Gsensor Power On Rec:5 usbPlug:1 Gsensor Power On Rec:6 usbPlug:1 Gsensor Power On Rec:7 usbPlug:1 Gsensor Power On Rec:8 usbPlug:1 Gsensor Power On Rec:9 usbPlug:1 Gsensor Power On Rec:10 usbPlug:1 Gsensor Power On Rec:11 usbPlug:1 Gsensor Power On Rec:12 usbPlug:1 Gsensor Power On Rec:13 usbPlug:1 Gsensor Power On Rec:14 usbPlug:1 Gsensor Power On Rec:15 usbPlug:1 Gsensor Power On Rec:16 usbPlug:1 Gsensor Power On Rec:17 usbPlug:1 Gsensor Power On Rec:18 usbPlug:1 Gsensor Power On Rec:19 usbPlug:1 Gsensor Power On Rec:20 usbPlug:1 [35mOn Shutdown begin
Noted the "Set Crash" in the Logs? I saw the same entries and behaviour when the K2 wakes up in parking mode to start recording after a shock has been registered.
Of course in my case, parking mode is disabled. I even disabled the G-Sensor and this is a normal startup. But for some reason, the K2 switches to some kind of "parking mode bootup". Consequently, the videos recorded during the short power up time are stored in the park folder and not in the video folder.
This behaviour happens with default settings (right after flashing the firmware) and with altered settings, where I disabled G-Sensor, switched parking mode on and off again to make sure the K2 got it. But without success.
I would love to verify this on my installed K2, but my motorbike is currently in my dealers garage for maintenance. But maybe someone else is able (and willing) to test the V0.64 firmware and verify this. Just install the firmware, shut down the K2 and then start it the normal way and see if it stays on.
Dear Frostie
I just did a short test of the V0.64 in my motorbike (from 13:35-13:43):
--> K2 behaves in my hands completely normal.
here some screenshots of the configuration and the moviedocs
Here is in the app the parameter for WIFI-time:
Hmmm...did you reboot your K2 after the flashing process?
After flashing, my K2 works normal. But after first reboot, the mentioned issue occurs.
Yes - I did reboot K2 (I installed firmware 2 days ago)
Ok. I was able to nail it down. It is my USBUart I use to get shell access to the K2. Of course it is always connected to the K2 when doing tests to see the log. For some reasons this seems to confuse the K2 since V0.64 during bootup. Maybe because I use the ground from USB.
If I disconnect the USBUart, everything works as intended and the K2 keeps running.
Thanks
So when you turn off the g-sensor again, will the video still be saved to the park folder?
Yes. Regardless of what settings I make, the V64 starts into this "parking mode bootup", records some seconds and shuts down. But as this only happens when my USBUart is connected, it is nothing you or any other user has to worry about. It is strange, but not your fault.
I've reported to our engineer, he will do a test later.
I wonder if this issue could be related to a problem I've been having? Ever since I installed the K2 last July, I've not gone more than a few weeks without the K2 starting to shut itself off for no apparent reason. It's not consistent, and I'll get normal operation at times, but then the K2 will shut itself off shortly after I start the engine and head out. I've stopped (with engine running) and tried to force it back on using the physical button - same result, it powers up briefly, then shuts itself off.
I've checked and re-checked absolutely everything: ground and other power connections, battery condition, motorcycle charging system output, etc. I even got a new motorcycle battery a few weeks ago, because the old one was no longer holding much of a charge (but, that still shouldn't have made the K2 shut down while the engine was running!). I am keeping the bike on a battery tender to ensure the battery is in absolute tip-top condition.
I've swapped DVR's once since last July, and I'm on my third power supply. My vendor keeps giving me replacements, but I'm really tired of having to swap the power supplies.
I've been on firmware 0.57 the whole time. Maybe I should try 0.64 to see whether anything screwy happens. Is there any way to see an error log without a USB logging device like you're using? If I could at least have some idea why the K2's software thinks it needs to shut down when there is 14.5V present, that would be hugely useful.
I’m sorry to hear that .. I would like to ask you some questions at first.
How long does your DVR turn itself off after use?
And the video recording during normal use is normal?
Does your converter have an LED working indicator?
The blue LED was illuminated when the K2 would shut down for no reason. Really strange.
I haven't had the problem since I got another new power supply, a few weeks ago, but I haven't been riding very much. I'll let you know if it still happens.
Could you please move all postings regarding
As far as I know....no. The K2 only gives some kind of status report on Port 3333/tcp, which can be used by e.g. telnet. If you, for example, stop recording, the K2 will report status "2", which means "Recording stopped". (see Novatek Wifi Command Guide). But that is nothing which would help you.
When this happens, where are the videos stored? "Video" or "Parked"? Are the videos ok or corrupted?
If the videos are corrupted, I guess the K2 crashed or (more likely) the power converter failed and the K2 simply switched off. You said, that you already got three new power supplies. As it is very unlikely that you got three faulty power supplies, I would guess that there is something killing it. Maybe some voltage peak.
I don't know whether the K2 power supply has an integrated peak protection or not. But maybe you would like to invest some Euro/Dollar in a voltage-peak-killer to test if it helps.
I don't know whether my vendor has sent the malfunctioning power supplies back to Innovv for analysis. I'm asking.
It's good to confirm that I'm having an actual hardware problem. I didn't think your increased-bitrate firmwares could possibly cause the problem I've had, but it's useful to rule things out. I'm about to flash my K2 with the official 0.64 firmware. If that goes well for the next few weeks or so I'll probably install the increased-bitrate version of 0.64.
Well...I am not sure whether it's a hardware problem or not. Maybe the K2 shuts down due to a power issue. Maybe it simply crashed due to a software issue. Though I would not expect the increased bitrate would cause any problems, I cannot guarantee it. Especially as I never tested the modified V0.64 for more than some minutes. So you are right that it is a good idea to install the original V0.64 to sort this out.
Unfortunately, I can't get the factory 0.64 firmware to install.
Nothing happens. I've tried everything I can think of.
Details here: https://www.innovv.com/forum/innovv-k2/k2-won-t-install-new-firmware-what-am-i-doing-wrong