DDPai Mola N3

@ADD150N DDPai models do not have motion detect in parking mode. They record 1fps time lapse, or G-sensor event based for up to 30 seconds and then goes back to sleep.

@kogabe The power supply interface does not have the usual USB data link. It's only used for power and communicating with GPS bracket. It's also pretty amazing you have a USB-C tip small and long enough to plug it in. I tried but I didn't have a suitable cable tip.
So this is false then, I cant see any reason to chose ddpai for my next dashcams, removed the snapshot buttons, the mini 5 cant take a large micro sd card, and the app is STILL beyond rubbish, not once did my cameras work as dual cameras in the app after setting up. i need decent dashcams that can do person detection, snapshot, cheers.
 

Attachments

  • hello ding ding.PNG
    hello ding ding.PNG
    375.6 KB · Views: 30
Hello friends, somewhere in the app is the remaining recording time informed for each set resolution? thanks.
 
Last edited:
mine always get "bad network message" downloading video was so slow and i cant replay recorded video. anyone got the same problem? how to fix it?
 
If a dashcam in my car was telling me when the light is green, i am pretty sure in a short while i would take that as a insult to my intelligence and get furious.
How anyone can think this might be a good aid for a human i dont know, cuz if you can not detect the light being on ( colorblind ) or actually see the green color, well you should not be driving a car.

The skies look very Danish, but i am sure its still a lot warmer out there, daytime here are 10 - 12 degrees ATM, and night time sub zero are not far away.
Someone with color blindness knows the toplight burning is red and the bottom one is green... :facepalm:
 
@Elcrying No, there's no such button on the Mola N3. The best you could do is tap the camera and trigger it to record. In medium sensitivity, it's pretty easy to trigger it. Going over washboard strips triggers it in medium on my car with lowered + stiffened springs and "sports" absorbers, so I had to set mine to low sensitivity.

@Cesarblu Yes, when you change resolution in the app, there's an indication of how much recording time your current memory card gives you. Depending on firmware, you have 1600p, 1440p, or 1080p options. I remember the recording time between 1600p and 1440p isn't that much different. Maybe 10-15 mins on a 32GB card.
 
[USER = 72252] @Elcrying [/ USER] Não, esse botão não existe no Mola N3. O melhor que você pode fazer é tocar na câmera e acioná-la para gravar. Em sensibilidade média, é muito fácil acioná-lo. Passar por cima das tiras de tábua de lavar o aciona no meio no meu carro com molas rebaixadas + enrijecidas e amortecedores "esportivos", então tive que ajustar o meu para baixa sensibilidade.

[USER = 71426] @Cesarblu [/ USER] Sim, quando você altera a resolução no aplicativo, há uma indicação de quanto tempo de gravação seu cartão de memória atual oferece. Dependendo do firmware, você tem opções de 1600p, 1440p ou 1080p. Lembro que o tempo de gravação entre 1600p e 1440p não é muito diferente. Talvez 10-15 minutos em um cartão de 32 GB.
Thank you friend.
 
@richx Thanks, i have one more question how long is the clip when you trigger g sensor to save the clip, are there any settings of a emergency clip duration ?
 
@Elcrying I believe the setting for it is 10 seconds, 20 seconds or 30 seconds + snapshot. It holds something like 5 seconds before and X seconds after based on your setting.

@Cesarblu I checked back the app again, it looks like the recording time estimate has disappeared off the latest version :/
 
[USER = 72252] @Elcrying [/ USER] Acredito que a configuração para isso é 10 segundos, 20 segundos ou 30 segundos + instantâneo. Ele mantém algo como 5 segundos antes e X segundos depois, com base em sua configuração.

[USER = 71426] @Cesarblu [/ USER] Verifiquei o aplicativo novamente, parece que a estimativa de tempo de gravação desapareceu da versão mais recente: /
Thank you friend, really don't have any more, I already complained with the support.
 
Probably the GPS is not using USB standard to connect to the cam.
I have opened the GPS housing and looked at its internals. The GPS/microUSB board is linked to the USB-C connector with the 12line flat cable.
DDPAI GPS receivers are usually connected using the UART port. DDPAI has used the VBUS and GND lines appropriately since your Samsung USB-C cable works as expected.
It should be possible to trace the UART RXD/TXD lines using the oscilloscope or a FTDI converter.
If the USB D+ and D- lines are routed between the microUSB and USB-C connectors, then it should be possible to run the usbstorage gadget on mola M3 for accessing the SD card.
 
Hi friends.
Clip broke and DDPAi Official does not provide replacement parts, does anyone know where to buy?
Thanks.
20210325_172101.jpg
 
I got working UVC streaming over USB-C (only 30fps), but not over microUSB on the GPS bracket (no D+/D- connection between them ?).
Accessing the SD card over USB-C should also work with the right software.
Have you ever heard about the 4G bracket for mola ?
I have ordered the Adafruit USB-C breakout board to check the GPS UART lines (SBU1 & SBU2 ?).
 
Trawling around Tmall and found this interesting accessory for the Mola N3. Unfortunately it definitely will not work with the toll collection system of your country (aside from China?). Also I think it doesn't have GPS functionality
This is just an external gadget using the UART (not USB) like GPS, so you can't have both with this hardware setup.
 
The fun can begin. I have managed to connect a multitude of external USB devices to the molaN3 running in USB host mode.
What do you think about external USB HDD connected to mola ? :cool:
Here i log in and load the self-compiled kernel modules:
Code:
$ telnet 193.168.0.1
Trying 193.168.0.1...
Connected to 193.168.0.1.
Escape character is '^]'.

(none) login: root
Password:
Welcome to HiLinux.
None of nfsroot found in cmdline.
~ # modprobe cdc_acm
~ # modprobe ftdi_sio
~ # modprobe pl2303
~ # modprobe usb_storage
~ # lsmod
Module                  Size  Used by    Tainted: P
pl2303                  7386  0
ftdi_sio               29741  0
cdc_acm                15070  0
usb_storage            38382  0
scsi_mod               99857  1 usb_storage
sg_pool                 1733  1 scsi_mod
8189fs               1408388  0
hi_int                  1679  1 [permanent]
hisi_mci               36193  1 8189fs
mmc_block              35372  2
mmc_core               97143  3 8189fs,hisi_mci,mmc_block
hi3559v200_wdt          4574  0
xhci_plat_hcd           5353  0
xhci_hcd               88268  1 xhci_plat_hcd
ehci_hcd               36046  0
hi_userproc            11647  0
hi_gpio                 3344  1
hi3559v200_ive        167498  0
hi3559v200_adc          3127  0
hi3559v200_sys         63246  1 hi3559v200_ive
hi3559v200_base        54215  2 hi3559v200_ive,hi3559v200_sys
hi_osal                55518 14 hi3559v200_wdt,hi3559v200_ive,hi3559v200_adc,hi3559v200_sys,hi3559v200_base
hi_virt_tty             8262  0
hi_ipcm                28878  5 hi_virt_tty

Now i connect an old 2GB USB stick (behind the external 4 port USB hub ;))
Code:
usb 1-1: new high-speed USB device number 3 using xhci-hcd
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
usb 1-1.1: new high-speed USB device number 4 using xhci-hcd
usb-storage 1-1.1:1.0: USB Mass Storage device detected
scsi host0: usb-storage 1-1.1:1.0
scsi 0:0:0:0: Direct-Access     SMI      USB DISK         1100 PQ: 0 ANSI: 4
sd 0:0:0:0: [sda] 3891200 512-byte logical blocks: (1.99 GB/1.86 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
sd 0:0:0:0: [sda] No Caching mode page found
sd 0:0:0:0: [sda] Assuming drive cache: write through
sda: sda1
sd 0:0:0:0: [sda] Attached SCSI removable disk
and mount it on /mnt (SD card is mounted on /app/sd)
Code:
~ # mount /dev/sda1 /mnt/
~ # df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root                 2304      1828       476  79% /
devtmpfs                 20464         4     20460   0% /dev
/dev/mtdblock7            7424      5404      2020  73% /app
/dev/mtdblock8             512       240       272  47% /usrcfg
run                       2048         8      2040   0% /app/var/run
/dev/mmcblk0p1        62343680  34104448  28239232  55% /app/sd
/dev/sda1              1940768   1879948     60820  97% /mnt
 
The USB GPS receivers work too (u-blox and old sirf using CDC-ACM and FTDI/PL2302 USB-serial bridges),
but i have a problem with the cheap USB modems.Their USB storage parts are recognised properly
Code:
USB stick using cdc_ether:

SCSI subsystem initialized
usb-storage 1-1:1.0: USB Mass Storage device detected
scsi host0: usb-storage 1-1:1.0
usbcore: registered new interface driver usb-storage
scsi 0:0:0:0: CD-ROM            HUAWEI   Mass Storage     2.31 PQ: 0 ANSI: 2
scsi 0:0:0:1: Direct-Access     HUAWEI   TF CARD Storage  2.31 PQ: 0 ANSI: 2

USB stick using usbserial:

usb 1-1: new high-speed USB device number 3 using xhci-hcd
usb-storage 1-1:1.0: USB Mass Storage device detected
scsi host0: usb-storage 1-1:1.0
usb-storage 1-1:1.1: USB Mass Storage device detected
scsi host1: usb-storage 1-1:1.1
scsi 1:0:0:0: Direct-Access     HUAWEI   SD Storage       2.31 PQ: 0 ANSI: 2
scsi 0:0:0:0: CD-ROM            HUAWEI   Mass Storage     2.31 PQ: 0 ANSI: 2
but since cdc_ether & usbserial are compiled into the kernel (and not dynamically loaded)
i can not easily debug them (other than decompiling the kernel RAM dump, which is a real PITA).
 
Wow imagine the fun storing into a 1TB SSD via USB ...
 
Wow imagine the fun storing into a 1TB SSD via USB ...
It can be easily done by renaming the DCIM directory, mounting the 1TB SSD on /app/sd/DCIM and moving the DCIM content back.
molaN3 and mini5 use the USB-C connectors, but otherwise are normal USB2.0 quasi-OTG devices.
Unfortunately there is one problem: standard mounting bracket. I did some research on its wiring using a simple multimeter:
the CC1/CC2, SBU1/SBU2 pairs are shorted and the SBU1/SBU2 pair is passed through to microUSB D+ (green cable).
microUSB D- (white cable) is not connected. Now i'm wondering how do they use the hardware kit.
The mini5 hardware kit may have the same UART wiring, but i was dumb enough not to buy it with mini5.
Now it has disappeared from Amazon.
BTW, the same USB2.0 quasi-OTG setup does not work on mini5 out of the box, because DDPAI uses the second USB port for 4G bracket,
but i still have some hope.
 
Last edited:
The problem with huawei 3G modems is well known to the Linux wireless router community (needs usb_modeswitch, which is missing from busybox).
This is the "switched" ID on my linux laptop
Code:
Bus 001 Device 108: ID 12d1:14dc Huawei Technologies Co., Ltd. E33372 LTE/UMTS/GSM HiLink Modem/Networkcard
and this is what mola sees
Code:
Bus 001 Device 005: ID 12d1:1f01
Here is another example:
Code:
Bus 001 Device 106: ID 12d1:1436 Huawei Technologies Co., Ltd. Broadband stick

Bus 001 Device 004: ID 12d1:1446

4G modems usually use the Qualcomm chipset and they need different drivers (qmi_* and rndis_host), and i can't test it (no such device here).
 
TP-Link UE300 Gigabit ethernet USB adapter works out of the box, because the Realtek RTL8152/8153 driver is compiled into the kernel.
Now i can switch off wifi and save power(y)
NFS mount for 'cloud storage' :LOL:
 
Last edited:
I had the DDPAI app on the mobile to be able to configure the DDPAI Mola N3. I have uninstalled it because I could not connect with the camera and when I try to reinstall it I see that the app I had is not available in the Play Store.

I have installed an app called 'Drive for DDpai' which appears but does not allow me to control my DDPAI Mola N3 model. 'Drive for DDpai' I only see that it allows to control the models 'DDPai Mini2' and 'DDPai M6' that I do not have.

Which one should I install or where can I get the apk to install?

Thanks

Not working download from Play Store, but you can dowload from:

https://m.apkpure.com/ddpai/com.cam...7--reiHiqnOjOLVubp1qNlTVHgdlqGgVo69rQzPOC-T2s
 
Last edited:
Back
Top