Z 60 Master in house

[kamkar]

And shortly after the mail man arrived undergoing memory card compatibility testing in the window sill, and might i add not doing too well ATM as the 2 tested cards so far only lasted 2 hours or so before they failed.

Mind you i think there is upgraded firmware out there, just not looked into that as i have been doing other things

I have found one personal thing i do not like, there seem not to be any option for recording in larger segments than 1 minute, i am partial to 3 minutes myself.
But this is of course not a flaw, just personal preference.

A bit wet in Denmark ATM so will do static testing for a while before i can get a break in weather to install in car.

Memory cards tested so far:

Samsung PRO ultimate. Black - OK
Sandisk extreme plus. gold / red - not OK
PNY XLR8. white / red - OK
Silicon power Inspire. Yellow / Black - OK
Lexar professional. grey / Black - Not OK
Kingston Canvas Go plus. - black / blue ( GEN 3 ) - OK
Adata high endurance. - black / red - Not OK
PNY PRO Elite - grey / black - Not OK ( would not even format )
Kingston canvas select plus. Black ( GEN 2 ) - Not OK
Trancend Ultra performance - black silver - Not OK
Adata Premier pro. black green - OK
Samsung PRO Plus U3 - blue - Not OK
Samsung EVO Plus - whiter - Not OK ( would not even format )

 

[lufa6977]

I prefer 3-minute video loops also. The cards you are testing, is that in the dashcam or in your computer?

 

[kamkar]

In the camera, i was nervous the camera might be toasting them. but the 2 failed cards are OK just too slow it would seem, though as i recall both did fine on the T800 from 70mai.
This system it would seem, when it fail it run a speed test on the card and leave the result as a TXT on the card. which i kinda like to be honest, no guessing.
the camera say the Sandisk card is 27.956799 MB/s and the Samsaung is 23.579620 MB/s according to the camera.

 

[lufa6977]

Have you ever used this tool?

h2testw

Heat issues tend to intrigue me a bit. In a dashcam, the SDXC card heats up; put the card in my Mac Studio or my Debian box, and at the same write speeds, there is almost no heat.

 

[kamkar]

Yes for over a decade, but it is rare i use it now, if a card fail in a system it fail, usually out of the 15 or so cards i have only a couple or 3 fail, but i have never experienced 2 to fail right off the batt.
I would have put money on these 2 working, they are also some of my newest cards in the collection.

results with the Vantrue S1ProMax.

Trancend Ultra performance - black silver - OK
PNY XLR8. white red - OK
Kingston Canvas Go plus. - black blue ( GEN 3 ) - OK
Sandisk extreme plus. gold red - OK
Lexar professional. grey - Black - OK
PNY PRO Elite - grey black - OK
Adata Premier pro. black green - OK
Adata high endurance. - black red - OK
Kingston canvas select plus. Black ( GEN 2 ) - OK
Samsung PRO ultimate. Black - OK
Samsung PRO Plus U3 - blue - OK
Silicon power Inspire - Yellow Black - OK

results ( limited as i got side tracked ) with the T 800 from 70mai.

70mai own menory card - Black - Of course OK
Lexar professional. grey - Black - OK
Kingston Canvas Go plus. - black blue ( GEN 3 ) - OK
Silicon power Inspire - Yellow Black - OK
Sandisk extreme plus. gold red - OK
PNY XLR8. white red - OK
Samsung PRO ultimate. Black - OK


ATM the PNY XLR8 is in the Z60 and i think it might work, been a couple of hours now. 🤞

 

[mentadent]

Will you be testing the cloud features?

 

[kamkar]

Indeed i will, but not before the system get in the car.

 

[kamkar]

So the PNY XLR8 card seem to have been working, though the APP did display a low speed memory warning.
But the system did not create a txt file with the speed of the card like it would do if it error out on this.

 

[kamkar]

H2testw the sillicon power inspire card.

Test finished without errors.
You can now delete the test files *.h2w or verify them again.
Writing speed: 37.0 MByte/s
Reading speed: 39.0 MByte/s
H2testw v1.4

The dashcam is now running with the Kingston Canvas Go plus. - black / blue ( GEN 3 )

Will have to retry this card and the Lexar card as i think i found a " issue "

 

[kamkar]

Okay i have a bit of strangeness, cards that have failed i can get to work anyhow by just formatting thru the camera, as in navigate on the camera to that menu and then format there VS using the APP as i did first.

Also looking at the memory card, it save logs in a TXT format, and while working and doing its thing it seem to encounter a lot of errors during recording.

Example of one such TXT.

This just a little part of the TXT in one of the files, and from when i was sleeping and so NOT interacting with the system.

[FS_OpenFile][742] lNodeIndex=95, szFileName:20260902103444_040.log, fileroot:/app/sd/DCIM/207log/main
[FS_OpenFile 749] szNewFilePath [/app/sd/DCIM/207log/main/20260902103444_040.log] is [Not Exist]
[FS_OpenFile][778] find filename=19700101013510_T.log
[FSRenameFilePath][2350] lNodeIndex=96
[10:34:44:918 [1;32mINFO[m-]😀DP_FILE_MoveFile[765]:to szDestFile:/app/sd/DCIM/207log/main/20260902103444_040.log
[FS_OpenFile][802] exist free file(19700101013510_T.log), open new file(20260902103444_040.log)
[FS_SetFileLen][1627] file len=512000
[10:34:46:131 [1;32mINFO[m-]😀DP_DIGICAM_CLIENT_StreamCb[2541]😀ev0 Cam[1] [REAR][Normal][SUB] frame size[3952] seq[690700] time[23032318279]
[10:34:46:131 [1;32mINFO[m-]😀DP_DIGICAM_CLIENT_StreamCb[2541]😀ev0 Cam[1] [REAR][Normal][MAIN] frame size[47520] seq[690700] time[23032351612]
[10:34:46:344 [1;32mINFO[m-]😀DP_DupFdSystem[358]:[0;32;32msh 'cat /proc/rkisp* | grep 'Isp' | awk -F'frame:' '{print $2}' | awk -F' ' '{print $1}''
[m[10:34:46:511 [1;32mINFO[m-]😀DP_DupFdSystem[358]:[0;32;32msh 'ls /sys/class/net/'
[m[10:34:47:200 [1;32mINFO[m-]😀DP_DupFdSystem[358]:[0;32;32msh 'ps'
[m[10:34:47:670 [1;32mINFO[m-]😀DP_HAL_WATCHDOG_Feed[141]:[0;32;32mdone !
[m[10:34:48:035 [1;32mINFO[m-]😀DP_DIGICAM_CLIENT_StreamCb[2590]😀ev1 Cam[2] [INTERIOR][Normal][AAC] frame size[768] seq[359800] time[23034141339]
[10:34:48:352 [1;32mINFO[m-]😀DP_DupFdSystem[358]:[0;32;32msh 'cat /proc/rkisp* | grep 'Isp' | awk -F'frame:' '{print $2}' | awk -F' ' '{print $1}''
[m[10:34:48:516 [1;32mINFO[m-]😀DP_DupFdSystem[358]:[0;32;32msh 'ls /sys/class/net/'
[m[10:34:48:796 [1;32mINFO[m-]😀DP_DIGICAM_CLIENT_StreamCb[2541]😀ev1 Cam[2] [INTERIOR][Normal][SUB] frame size[4403] seq[575700] time[23034875799]
[10:34:48:850 [1;32mINFO[m-]😀DP_DIGICAM_CLIENT_StreamCb[2541]😀ev1 Cam[2] [INTERIOR][Normal][MAIN] frame size[68609] seq[575700] time[23034955799]
[10:34:49:464 [1;32mINFO[m-]😀DP_DIGICAM_CLIENT_StreamCb[2541]😀ev0 Cam[1] [REAR][Normal][SUB] frame size[2262] seq[690800] time[23035651612]
[10:34:49:469 [1;32mINFO[m-]😀DP_DIGICAM_CLIENT_StreamCb[2541]😀ev0 Cam[1] [REAR][Normal][MAIN] frame size[64163] seq[690800] time[23035684946]
[10:34:49:990 [1;32mINFO[m-]😀DP_DIGICAM_CLIENT_StreamCb[2590]😀ev0 Cam[1] [REAR][Normal][AAC] frame size[768] seq[359800] time[23036216239]
[10:34:50:359 [1;32mINFO[m-]😀DP_DupFdSystem[358]:[0;32;32msh 'cat /proc/rkisp* | grep 'Isp' | awk -F'frame:' '{print $2}' | awk -F' ' '{print $1}''
[m[10:34:50:520 [1;32mINFO[m-]😀DP_DupFdSystem[358]:[0;32;32msh 'ls /sys/class/net/'
[m[10:34:52:212 [1;32mINFO[m-]😀DP_DupFdSystem[358]:[0;32;32msh 'ps'
[m[10:34:52:365 [1;32mINFO[m-]😀DP_DupFdSystem[358]:[0;32;32msh 'cat /proc/rkisp* | grep 'Isp' | awk -F'frame:' '{print $2}' | awk -F' ' '{print $1}''
[m[10:34:52:524 [1;32mINFO[m-]😀DP_DupFdSystem[358]:[0;32;32msh 'ls /sys/class/net/'
[m[10:34:52:796 [1;32mINFO[m-]😀DP_DIGICAM_CLIENT_StreamCb[2541]😀ev0 Cam[1] [REAR][Normal][MAIN] frame size[51932] seq[690900] time[23039018279]
[10:34:52:797 [1;32mINFO[m-]😀DP_DIGICAM_CLIENT_StreamCb[2541]😀ev0 Cam[1] [REAR][Normal][SUB] frame size[5133] seq[690900] time[23038984946]
[10:34:52:803 [1;32mINFO[m-]😀DP_DIGICAM_CLIENT_StreamCb[2541]😀ev1 Cam[2] [INTERIOR][Normal][SUB] frame size[4066] seq[575800] time[23038875799]
[10:34:52:831 [1;32mINFO[m-]😀DP_DIGICAM_CLIENT_StreamCb[2541]😀ev1 Cam[2] [INTERIOR][Normal][MAIN] frame size[65731] seq[575800] time[23038955799]
[10:34:54:372 [1;32mINFO[m-]😀DP_DupFdSystem[358]:[0;32;32msh 'cat /proc/rkisp* | grep 'Isp' | awk -F'frame:' '{print $2}' | awk -F' ' '{print $1}''
[m[10:34:54:420 [1;32mINFO[m-]😀DP_DIGICAM_CLIENT_StreamCb[2590]😀ev1 Cam[2] [INTERIOR][Normal][AAC] frame size[768] seq[359900] time[23040541344]
[10:34:54:529 [1;32mINFO[m-]😀DP_DupFdSystem[358]:[0;32;32msh 'ls /sys/class/net/'
[m[10:34:55:016 [1;32mINFO[m-]😀DP_HAL_MCU_SendMsg[396]: 55 AA 07 00 00 00 00 07
[10:34:56:125 [1;32mINFO[m-]😀DP_DIGICAM_CLIENT_StreamCb[2541]😀ev0 Cam[1] [REAR][Normal][MAIN] frame size[61143] seq[691000] time[23042351612]
[10:34:56:130 [1;32mINFO[m-]😀DP_DIGICAM_CLIENT_StreamCb[2541]😀ev0 Cam[1] [REAR][Normal][SUB] frame size[8563] seq[691000] time[23042318279]
[10:34:56:378 [1;32mINFO[m-]😀DP_DupFdSystem[358]:[0;32;32msh 'cat /proc/rkisp* | grep 'Isp' | awk -F'frame:' '{print $2}' | awk -F' ' '{print $1}''
[m[10:34:56:384 [1;32mINFO[m-]😀DP_DIGICAM_CLIENT_StreamCb[2590]😀ev0 Cam[1] [REAR][Normal][AAC] frame size[768] seq[359900] time[23042616265]
[10:34:56:533 [1;32mINFO[m-]😀DP_DupFdSystem[358]:[0;32;32msh 'ls /sys/class/net/'
[m[10:34:56:791 [1;32mINFO[m-]😀DP_DIGICAM_CLIENT_StreamCb[2541]😀ev1 Cam[2] [INTERIOR][Normal][SUB] frame size[5182] seq[575900] time[23042875799]
[10:34:56:841 [1;32mINFO[m-]😀DP_DIGICAM_CLIENT_StreamCb[2541]😀ev1 Cam[2] [INTERIOR][Normal][MAIN] frame size[61694] seq[575900] time[23042955799]
[10:34:57:225 [1;32mINFO[m-]😀DP_DupFdSystem[358]:[0;32;32msh 'ps'
[m[10:34:57:391 [1;32mINFO[m-]:GPS_StateCallback[152]:enEvent:2
[10:34:57:392 [1;32mINFO[m-IPCMSG_CTRL]😀DP_IPCMSG_Ctrl_EventProc[222]:EventID:0x12a00000, arg1:0x2, arg2:0, result:0
[10:34:57:392 [1;32mINFO[m-IPCMSG_CTRL]😀DP_IPCMSG_OnEvent[131]:
[10:34:57:392 [1;32mINFO[m-IPCMSG_CTRL]😀DP_IPCMSG_REPORT_SystemStatus[453]:EventID:0x12a00000
[10:34:57:392 [1;32mINFO[m-NetCtrl]😀DP_BLUETOOTH_HandleEvent[99]:recv EventID:0x12a00000
[10:34:57:392 [1;32mINFO[m-NetCtrl]😀VR_OnRemoteEvent[390]:recv EventID:0x12a00000
[10:34:57:392 [1;32mINFO[m-NetCtrl]😛DT_NETCTRL_EventProc[527]:EventID:0x12a00000, arg1:0x2, arg2:0, result:0
[DDP_GPSMNG_CheckPoint][1201] speed(531.090027) time(1788338098) is invalid!
[HI_CGI_BluetoothGetState][3104]: HI_CGI_BluetoothGetState = {"API_StateReport":{"wifi":1,"gps":1,"radar":-1,"rec":1,"recMode":-1,"recTime":0,"bat":-1,"charging":-1,"dis":0,"time":0,"handRecTime":0,"tf":1,"fsensor":1,"rsensor":1}}
[10:34:57:670 [1;32mINFO[m-]😀DP_HAL_WATCHDOG_Feed[141]:[0;32;32mdone !
[m[DDP_GPSMNG_CheckPoint][1201] speed(524.849976) time(1788338099) is invalid!
[10:34:58:384 [1;32mINFO[m-]😀DP_DupFdSystem[358]:[0;32;32msh 'cat /proc/rkisp* | grep 'Isp' | awk -F'frame:' '{print $2}' | awk -F' ' '{print $1}''
[m[10:34:58:537 [1;32mINFO[m-]😀DP_DupFdSystem[358]:[0;32;32msh 'ls /sys/class/net/'


Right now testing the Samsung card again, this time formatted using the buttons on the camera and not APP

 

[lufa6977]

I'd expect no difference in formatting between on-screen and the app. But...I am unfamiliar with DDPAI products. 🤔

The disk tools to format should be the same software regardless of where the 'command to format' originates from. You could format it both ways, then check the SD card on your PC and use diskutil to see whether one method creates unused space before the first partition.

The text file you are looking at looks more like a debug file or crash log, though I don't see any alerts I would expect in a crash log. It does look like they are using Linux in part of the system. Honestly, that log is producing a lot of info, and if that info is just for average, everyday, error-free driving, then it should be turned off, in my view anyway. I understand logging some data for customer troubleshooting, but that is way too much and it consumes too much processor time and disk space.

 

[kamkar]

Yes i also find it pretty strange.
Also inserting card first time, these all used and full of other system footage, well the Z60 dont even ask for a format right away, or that is it have done that one time.

No i was looking at another of those TXT files when i saw " error " this above seem pretty normal, and i suppose in dashcams thing happen beside recording.

The Samsung card is still chugging along, and in the APP i do not see the low speed storage warning above.
It do not take terrible long to fill a 256GB memory card with the 760 or so 1 minute files it is able to hold ( about 25GB memory space seem to be reserved for events.

Also every time putting a card in the reader, my PC want to scan and repair it, but i select just carry on and then i get to see the content just fine.

 

[kamkar]

Okay the Samsung also seem to work anyway.
The system seem to have the latest firmwares ASO, so not like it sneaky have updated itself in the background.
So confused as to why there should be a difference in using APP to format the memory card or the buttons on the camera,,,,,, BTW format the memory card is in the reset camera menu, took me a while to find it.

The sandisk extreme plus is now in the camera.

 

[lufa6977]

.
.
Also every time putting a card in the reader, my PC want to scan and repair it, but i select just carry on and then i get to see the content just fine.

Yes, that is a very annoying Windows habit. I think it usually happens when the SDXC card wasn't properly closed/ejected from the previous device. But I have also had this happen with some SD-to-SDXC adapters, but not others. Issues like fragmented files, files not properly closed, and improper or missing metadata could also cause this.

What is really annoying is that you tell Windows to fix the SDXC card, and then when you put it into the dashcam, the dashcam will sometimes tell you to format the card.

 

[kamkar]

I am using a adapter CUZ the micro port died in my reader, perhaps i should go looking for a new one, some modern SD cards also way outspeed what this old one can do.
For that i do have vacant USB 4 ports on the back of my PC.

But never done so with cards from the S1Pro Max or the T800 system or my Insta 360 ace pro "action" camera.

Static testing here, i just pull the plug out of the wall wart, or should i say wall HUMP, damn thing will give 140 watts on its USB C outlet, but the A one i use i do not know how much, but plenty i am sure.

 

[kamkar]

New card reader in the mail, but have now run out of memory cards to test.
I am currently running the Samsung EVO Plus again, this time just formatted on the PC, which seem to be OK for the system as it just booted and got going recording.
On first try this same card wouldn't even format in the camera.
I might try the same for the other cards that failed.

Needless to say, this system more memory card fussy than others i have tried lately.

 

[lufa6977]

I have a DDPAI N5 Pro with Radar and LTE for testing. I tested the 64GB DDPAI microSDXC card: it wrote 55.36 MB/s error-free and read back 88.68 MB/s error-free.

I am surprised by how much space on the microSDXC is wasted on log files, thumbnails, and duplicate but smaller videos for the front video.

 

[kamkar]

The APP also different, it remind me more of the APP for my friends little CCTV cameras.
Not bad but a little different.
I also have a original DDpai 64 Gb card i will test that in my new card reader when it arrive from Sweden on Monday.
USB 3.2 /10 Gbps so also ready for when dashcams need to upgrade to even faster memory cards, though i still hope they will do another slightly larger storage solution.

 

[lufa6977]

The APP also different, it remind me more of the APP for my friends little CCTV cameras.
Not bad but a little different.
I also have a original DDpai 64 Gb card i will test that in my new card reader when it arrive from Sweden on Monday.
USB 3.2 /10 Gbps so also ready for when dashcams need to upgrade to even faster memory cards, though i still hope they will do another slightly larger storage solution.

Yes, that App is very different. It will take me a while to get used to it. My hypercritical eye for design has already noticed issues with the app's display and the website, such as spelling. Not bad, but common mistakes made by non-English-speaking designers; it is to be expected. So far, the only video has been in my house, but I have liked what I have seen. Next week, my car will be in the shop from Wednesday to probably the week after, so I am thinking about how I want to mount and power this for the next few days. It didn't come with a CLA, but I have plenty of those and cables, so I will probably use a CLA.

 

[kamkar]

I hope it is just the window i film thru during my memory card testing, but the footage from the main camera seem a bit soft.
Also on exposure the main and rear cameras are the same, but the interior camera OMG it is like 2 X brighter at night.

The wire harness also unusual.
I will have to go to new untried levels i think to get that to play ball with my headliner in the new car that contrary to the old car feel much tighter installed.

I have agreed with myself that the sensor housing cover will remain off for a while.

Also have to get car coated for rust protection really soon, so want to delay install to after that is done.
Ill see if i can get up early enough Monday to call seller so he can book a time for me.