Hi Innovv
The technical specifications on https://www.innovv.com/innovv-k2-spec says, that the USB Port on the K2 is for " Charging (DC5V), Data transfer ".
And when I connect the K2 on a computer, it starts up, but there is no data transfer available.
Is this a planned feature? I would love to transfer the videos over USB rather then removing the SD card everytime, because I am worried that the SD slot will wear out one day or another. Using the USB Port I could use a raspberry as a WLAN relay to access the K2 directly from my home pc.
Will do firmware update to make that work.
Can you give a rough estimation when this update will be?
And can you tell me how much current the K2 takes when powered over USB (continuous and peak).
It should take two weeks to have this update.
And it is 800mA, that is the power supply to get the K2 work properly.
Great. Looking forward to this.
I already have plans how to access the SD card via FTP.
Click below link to download the last firmware, Connect USB port to PC to read the video clips.
https://www.dropbox.com/sh/cyxhdlunuw312js/AADvCE23ptpn4X918bPf48p4a?dl=0
Are you sure that the link is correct? That´s a V39 firmware there.
Edit:
Ok...found the new V49 in the support area. Already modified it and will do some Tests tomorrow, before putting it on Dropbox.
Today I tested the data transfer via usb, but sadly it did not work. The K2 is not detected as an usb device at all, neither on my windows 8 tablet nor on my raspberry 3.
Very disappointing.
By the way.
When I connect my tablet to the K2 wlan, I can access the K2 via browser on 192.168.1.254 and have direct access to the files. But the wlan is bloddy slow (1,5MB/sec), so that is no alternative to usb.
Can you please check the USB cable,
1. it has 4 wires, is able to do data transfer.
2. the wires inside of cable should be at least #26, able to transfer 700mA.
We have been testing the data cables purchased on only, the most are failed due to the wires are inside of cable are too thin.
Do you have old android phone data transfer cable? that should be capable.
So I tested mine this morning and my PC (Windows 10) also does not recognise the dvr as a storage device.
All other functions appear normal, it powers up instantly, I can access live camera feeds etc and when I unplug the USB it powers off instantly.
Looking forward to having this feature as well, have a short USB cable that will stay plugged in and easily accessible on the side of the seat (made a cap out of heat shrink to keep it clean).
Frostie, I hope once this is functioning do will add your higher bitrate code mod?
I already did a modified V49 firmware.
Just had a run, testing the modded case, using the V49-15k modified firmware (based on the stock).
No USB access either with the DVR on the bench connected to the PC only or on the bike with ignition on. :(
I just tried using V49 USB firmware (which is no longer on the Innovv website) and my Mojave Mac, and the K2 does not show up in the Finder.
Reuploaded the V49 to dropbox.
To get stable connection and see the video files in SD card, Two cameras (At least one camera) need to be unplugged from DVR.
The reason is usually USB output is Max 5V 500mA, the K2 with two cameras requires 5V 700mA, which makes PC to overloaded and could not see the SD card storage.
I also tried the USB connection while the K2 was powered by the power converter, but without success. And with a usb hub, which can deliver 2A, but again no success.
Are there different hardware revisions of the K2?
And by the way:
Though the usb specifications says 500mA is the maximum current, nearly every computer can handle more than that on usb.
I just checked my new K2 (V0.49) as a USB-drive. With two cameras plugged in -> instant USB connection with my laptop :-)
I got a transferrate of >11MB/sec to my laptop cheers
Kurt
That doesn't seem very fast. So that would take 25 seconds to download a 3 minute video shot at full resolution (270 MB). The WiFi transfer is about that speed.
You get 11MB/sec when downloading the video on Wifi? I only get 1,5MB/sec.
About the 11MB/sec via USB.
The K2 continues recording when powered via usb. That would take a reasonable part of the data rate of the sd card. So I guess the download speed could be higher if the K2 would stop recording then connected via usb.
Neil.
P.S. Frostie I'm still intend to test the higher bitrates, just not had the opportunity so far.
I did some more tests and got some strage behaviours.
First I tested the usb connections using the shortest usb cable I own, which works flawless with my TomTom GPS or other devices. But again the K2 did not show up as usb device. Then I followed Rocks advice and unplugged the rear cam. And that was when the strange things started.
After connecting the K2 to my Raspberry I noticed, that the camera LED was constantly on. Which means the K2 is not recording. I tried to check this using the App, but there was no Wifi, though the Wifi LED was blinking normally.
I connected to my Raspberry and...oh wonder...the K2 showed up as usb device and I was able to access the sd card. I then powered the K2 off and on again, but still the same. No recording, no wifi, but usb access.
Then I plugged in the rear cam und started the K2. It started recording and Wifi was back, but the rear cam was disabled. And of course no usb access (as usual). After checking the cables of the rear cam,
I checked the settings and figured out, that the K2 messed up the resolution settings. Instead of "1080P" there was "nil". Set it back to 1080P, restarted the K2 and everything was fine again.
To summarize it
- Both cams conected => no usb access. Regardless of how the K2 is powered (usb, power converter)
- One cam removed => usb access, but not recording and no wifi. Resolution settings gets messed up.
In my eyes the fact, that the K2 messed up the resolution settings after I removed the rear cam shows that there is still some kind of firmware issue. This assumption is stengthened by the fact, that recording AND wifi stop working when I unplugged the rear cam. The K2 seems to got in some special state when it started up with only one cam connected. And this state made usb access possible.
So in my eyes this is not a power or two-wire-cable issue. Even when using an usb hub with external power supply, which can deliver 1,5A, the usb connection is not working. And it also does not work when the K2 is powered by the power converter.
Again I would like to ask if there are different hardware revisions of the K2. Even small changes could explain why some (currently only one) customers can access the K2 via usb and all others can not.
And please explain why it does not work when the K2 is powered by the power converter. Because at that moment the 500mA limit of usb 2.0 can't be the problem.
Thank you for testing and input.
It should work if two cameras are removed. 4 wires inside of USB cable should be high quality, not to be too thin.
About the questions you have, we will do check accordingly.
But why do we all have to remove at least one camera? As I already mentioned, the problem stays when the K2 is powered by the power converter. So this can´t be a power issue.
And to be honest:
The need to remove the cams to make usb work is ridiculous. Depening on where the K2 is mounted on the bike, it is difficult to pull off the cams and it will sooner or later ruin the seal of the plugs.
I think for now the use of the usb port is way too fiddly (there is already one tiny screw rattling around in my bike innards somewhere) it's easier and faster just to eject the sd card and transfer the files.
For future models where the usb connectivity is improved perhaps there could be a usb lead coming from the dvr rather than a port hidden under a screwed down panel.
Neil.
Yes...actually removing the sd card is the only way to get the video at an acceptable speed. USB isn´t working and wlan is bloddy slow.
Another tester's results:
USB access as follows (when starting from cold boot):
No cameras connected: No USB access (DVR continually reboots)
Front camera connected: USB access
Rear camera connected: No USB access (DVR continually reboots)
Both cameras connected: No USB access
NOTE 1: If I start with only front camera connected with USB access and then plug in the rear camera without powering down the DVR, the USB access remains.
NOTE 2: When I plug DVR into USB port on my computer monitor, I can see the drive, but not access the WiFi (INNOVV network doesn't appear as list of choices). But if I plug DVR into an iPhone charger USB plugged into wall, the WiFi network is again visible and I can connect. So apparently my computer does not have the juice required for the DVR wifi to power up.
Very interesting results. Escpecially that USB is only working if the rear cam is removed, not the front cam. Thanks for that. But could you please do one more test?
Could you please do what you mentioned in NOTE 1 and then check, if the rear cam is really working after you plugged it in? For example by checking the live view.
http://192.168.1.254:8192
And if yes, start recording and check via USB if videos for both cams are saved?
http://192.168.1.254/?custom=1&cmd=2001&par=1 => starts recording
I have a suspicion what may going on here. And if I am right, the rear cam should not work while usb access.
Frostie,
Before I can complete this follow-on test I’ll need to figure out a way to get DVR WiFi to reliably work when plugged into computer; otherwise, I won’t be able to check the camera video. I’m having difficulty getting Wi-Fi network to appear unless plugged into wall charger or power converter, which means no USB connection. I’ll try a few other cables and USB ports. Any other suggestions?
HarleyFool
Frostie,
I just tried again with DVR plugged in to USB port on my Windows 10 computer. I can only see the INNOVV wifi network when I have both cameras plugged in. In that config, both cameras are working. When I unplug either front or rear camera, I cannot see wifi network. USB connectivity same as reported above, e.g. only seems to work when front camera connected and rear camera removed.
HarleyFool
You could try powering the K2 by the power converter and then, when it is up and running, connect it to your pc.
Maybe I will have time today to test this.
I did some more tests today.
First off all, to prevent any power issues, I connected the K2 power converter to an external power supply and set it to 12,5V.
As a site note:
I noticed that the K2 takes 230mA at 12,5V while running.
Converted to 5V this is 575mA. That's less than the 700mA Rock stated. And I would suppose that nearly any computer can deliver 575mA via USB.
Ok...back to the tests I did.
With both cams connected, I powered the K2 and waited till is has started, then connected my Raspberry. Results: Wifi on, no usb access (we all still know this)
With rear cam unplugged, I powered the K2 and waited till it has started, then connected my Raspberry. Results: Wifi on, no usb access. That was a little bit surprisingly. If this is a power or simply a ressource issue, usb should work now.
With rear cam unplugged, I powered the K2, but connected my Raspberry imediately before the K2 started up. Results: No Wifi, usb access.
During all tests I monitored port 3333 on the K2 in the hope I could see some kind of status or error message. But because wifi always switched off when usb was available, I could not see anything.
I also did a wlan scan to see if there is some kind of maintenance wlan, as I found some other ip addresses within the firmware, but unfortunately there is nothing.
During the tests where wifi was available, the K2 did not report anything on port 3333 (except normal status reports like "recording stop" or "power off")
So I plugged in the rear cam, started the K2, and (again) the rear cam was offline. Within the App the resolution settings switched to <nil>.
Because of this, I compared the settings of the K2 with and without rear cam
(https://192.168.1.254/?custom=1&cmd=3014) and noticed, that there are some settings missing when the rear cam is not connected. These settings are...
<Status>0</Status>
<Cmd>3040</Cmd>
<Status>0</Status>
<Cmd>3041</Cmd>
<Status>1</Status>
<Cmd>3042</Cmd>
<Status>0</Status>
<Cmd>3043</Cmd>
<Status>0</Status>
<Cmd>3039</Cmd>
<Status>0</Status>
<Cmd>8003</Cmd>
<Status>0</Status>
<Cmd>8005</Cmd>
<Status>0</Status>
<Cmd>8006</Cmd>
<Status>0</Status>
<Cmd>8007</Cmd>
<Status>0</Status>
<Cmd>8009</Cmd>
<Status>0</Status>
I haven't figured out yet what these settings are good for. They are not listed within the Novatek wifi command guide.
Another thing I am wondering about is the name of the usb storage device I see, when usb access is available.
[ 992.340956] usb 1-1.1.2: Product: DEMO1
[ 992.340964] usb 1-1.1.2: Manufacturer: NOVATEK
[ 992.340974] usb 1-1.1.2: SerialNumber: 966110000000100
[ 992.344204] usb-storage 1-1.1.2:1.0: USB Mass Storage device detected
[ 992.347835] scsi host0: usb-storage 1-1.1.2:1.0
[ 992.412724] usbcore: registered new interface driver uas
[ 993.444776] scsi 0:0:0:0: Direct-Access NOVATEKN vt-DSC PQ: 0 ANSI: 5
[ 993.449837] sd 0:0:0:0: [sda] 249737216 512-byte logical blocks: (128 GB/119 GiB)
[ 993.454008] sd 0:0:0:0: [sda] Write Protect is off
[ 993.454027] sd 0:0:0:0: [sda] Mode Sense: 2b 00 00 08
[ 993.454383] sd 0:0:0:0: [sda] Write cache: disabled, read cache: disabled, doesn't support DPO or FUA
Why is the storage device named "DEMO1"? I mean, if I would create a product named K2 and this product offers an usb storage device, I would name the device K2 or something like that. And not DEMO1.
To summarize all this. USB does only work if...
the rear cam is not connected
the usb connection is made before the K2 has started up.
It does not matter how the K2 is powered or what kind of cable you are using (as long as it has four wires).
All this leads me to the following suppositions, why usb is only working under the mentioned conditions.
There is a hardware restriction. The rear cam and the usb port shares the same hardware ressources in some ways, which makes it impossible for them functioning at the same time. However, there are many dual dashcams on the market, using the NT96663. I have not found any posting about problems accessing the dashcam via usb. Of course I have not checked every forum in the net, but I guess that these kind of errors would stick out when doing some google search. So this supposition is very unlikely.
There is a firmware issue or restriction. For some reason the usb device and any other device (webserver, rear cam) shares the same software ressources (file handler, uart, etc). Or (in my eyes more likely) the usb feature is implemented badly. The fact that the usb storage device is named "DEMO1" looks like someone copy-pasted some kind of example code. Another fact is, that the K2 only switches to usb storage mode when the computer is connected before the boot process of the K2 has finished. I know that the firmware offers events like "onUSBconnect", but obviously they are not used. It seems that the K2 simply checks on boot whether or not usb is connected and if yes, it switches to some kind of storage mode, but without initializing all the rest (cam, wifi, webserver, etc.) And why the hell does the K2 messes the resolution settings if I remove the rear cam? There is no need for this.
Sorry Rock, but whoever told you that this is a power or cable issue, is wrong. It is a hardware or (most likely) a firmware issue. Your developer(s) should move back at the drawing board.
We will do further check what wrong indeed, and keep you updated.
Edit
Removed my posting, as the steps mentioned there were based on wrong conclussions.
During my tests changed the 128GB sd card to a small 2GB sd card. This led to my assumption, that the steps I wrote here could enable usb, But in fact, usb is working out-of-the-box, if the sd card is small enough (see below).
As a funny update.
I don't know what I've done, but now USB works all the time if the Raspi is connected before starting the K2. This definitively not happend when I started my tests. Already did a system reset and re-flashed the V49 firmware, but USB is still working. I will try to figure out why.
Edit:
Flashed the V39 and then the V49 to really erase all settings. After that, USB isn't working anymore.
As we all know. Now I will do all the tests I did today so see, which settings made USB working.
Edit2:
So far I discovered that it has something to do with the size of the sd card. I did my tests with a small 2GB sd card. With this card I got usb working simply by connecting the Raspi prior startup. Using a 128GB card, usb does not work. I switched the cards during my tests to flash the firmware. Because of that, I did some tests with the 128GB card and some with the 2GB card. And so sometimes usb worked and sometime it did not work. This led to my assumption that I "accidentally" changed some settings which are responsible for that. But in fact it is only the size of the card.
Will do more tests tomorrow.
Tested different sd cards
2 GB => USB works without removing rear cam
4 GB => USB works without removing rear cam
32 GB => USB does not work. Need to remove rear cam
128 GB => USB does not work. Need to remove rear cam
Unfortunately I don't have a 8 GB card for the test. The reason I would love to test this are the free disk space and the bytes necessary to save this.
4 GB => 3995133952 bytes. In Hex this is EE 20 E8 00 and requires 4 bytes to save.
8 GB => 7990267904 bytes. In Hex this is 01 DC 41 D0 00 and requres 5 bytes to save.
Would be interesting so see if this is the limit for usb to work out-of-the-box.
Edit
The mentioned partition size is wrong. See my posting on next site. The actual limit is 32 GB.
I was able to nail down the limit by increasing/decreasing the partition size in the sd card.
The limit is 24467 MiB (23,89 GB). That's the larges possible partition size where usb works without removing the rear cam. In the K2 this is a free disk space of 25649086464 Byte.
If I increase the partition to 24468 MiB, usb does not work anymore.
Well..this is interesting, but I can't see a connection between this maximum size and the fact that we have to remove the rear cam if the parition is greater than that limit.
Well...seems that it is your developers part to figure out what's going on here. Because this is clearly an firmware issue.
That is good findings, that we even did not figure out.
To be honest, our guys do not have such rich knowledge and experience on those, still needs times to get problem fixed.
Great detective work on this, Frostie- Sorry I'm not qualified to add constructive input!
Checking today for updates, I found a new firmware 0.49 (??) without the USBREAD in the name, with filedate 31/05/2019.
At the moment on my K2 is the 0.49-USBREAD with filedate 06/05/2019 installed.
Anybody knows the difference?
There is also a new App-Version 1.3.0., did anyone used it successfull on a Samsung J5?
I did a sha256 check and there is no difference between those two files.