The Jimi IoT JC261 & JC400 dashcam is a capable 2-Channel (Front + Cabin) dashcam with GPS Tracker functionality
It can be configured to deliver video events to the platform, you can request Live or Historic video as well as use it as a tracking device on the Whitelabel Tracking Platform
There are different models of the JC261 & JC400:
- JC261P - integrated dual channel & ADAS AI (upgraded from JC400P)
- JC261 - integrated front camera and optional external camera with ADAS AI
- JC400D - integrated front camera and optional external camera - uses external DMS sensor
- JC400 - integrated front camera and optional external camera
- JC400P - integrated dual channel
JC261 / JC400
Step 1 - Check the firmware
For the most accurate and up-to-date firmware, please contact Jimi IoT directly
Do not update your firmware without first confirming with Jimi IoT about device compatibilitySend this GPRS/SMS command to your device/sim card:
- VERSION
If your version is out dated or not using our recommended version, you will need to update it.
Firmware updates must be applied sequentially, i.e. you cannot go from 1.4.1 directly to 1.6.3 (you cannot skip 1.6.1)
Update methods
Manual update:
- Copy firmware file to the device SD card as it is (do not unzip the file).
- Insert the SD card into the device and power it on.
- After inserting the USB flash drive, the device will automatically detect the upgrade package and perform the upgrade.
GPRS command
- If device is reporting to the platform, goto asset info / commands and send a custom GPRS command listed above
Send the following SMS commands to your tracker in this EXACT order, and wait for each message to reply before sending the next
- COREKITSW,0 - Set intergration mode
- TIMEZONE,+00:00 - Set the timezone as UTC/GMT 0
- TIMESYNC,gps - Set the time syncronization as GPS mode
- Set your APN, leave blank if user or password is not required:
- APN,<apn>,<apn>,,,,,,<user>,,<password>,,,,# - If your APN uses a user & password
- APN,<apn>,<apn>,,,,,,,,,,,,# - If your apn does not have a user or password
- UPLOAD,http://media.gpsiot.net:23010/upload - Pointing to upload server
- RSERVICE,rtmp://media.gpsiot.net:1936/live - Set video live stream
- SERVER,1,data.gpsiot.net,8928 - Set GPS tracking server
Step 3 - Configure the remaining commands with GPRS
Your device should now be reporting to the platform, if you do not wish to send more SMS commands, you can use the GPRS commands page to send the remaining commands to the tracker (assuming its reporting to the platform).
Goto Asset Info > Commands to and send the following custom commands.
- MILEAGE,ON - Enable odometer and set to 0 or use MILEAGE,ON,86154000 to set to 86,154km
- TIMER,ON,60 - Report rate: send every 60 seconds when Ignition on
- TIMER1,ON,3600 - Report rate: send every 3600 seconds when Ignition off
- ANGLEREP,ON,30 - Report rate: send if there is a 30 degree angle change
- SOSALM,ON,0 - Enable SOS alarm events
- ACCREP,ON - Enable ACC/Ignition status change events.
- UPLOADSW,SOS,ON - Enable SOS video events
- UPLOADSW,CRASH,ON - Enable crash/impact video event
- UPLOADSW,RAPIDACC,ON - Enable harsh acceleration video events
- UPLOADSW,RAPIDDEC,ON -Enable harsh braking video events
- UPLOADSW,RAPIDTURN,ON - Enable harsh cornering video events
- RAPIDDEC,2 - Set the sensitivity level to medium for triggering harsh braking event.
- RAPIDACC,2 - Set the sensitivity level to medium for triggering harsh acceleration event.
- RAPIDTURN,1 - Set the sensitivity level to low for triggering harsh cornering event.
- RAPIDTEST,30,40,70 - Set the threshold to trigger an aggressive driving behavior alert.
- REBOOT - Lastly reboot the device so the settings take affect.
UART Switch/Door Sensor Commands
Using the following command structure:
UART,<A>,<B>,<C>,<D>,<E>,<F>
- A== 0/1/2 - 0 disables the function, 1 takes close as a trigger, and 2 takes open as a trigger
- B== 0/1/2 - The ACC state, where 0 detects in any state, 1 detects only in ACC ON, and 2 detects only in ACC OFF;
- C== ranges from 1-3600 - The detection interval in seconds, between 2 detections to avod many un-necessary event videos
- D== ranges from 1-120 - The speed condition by GPS speed, with 0 being unlimited;
- E == 1/2 - The action after trigger, where 1 equals short video, and 2 equals photo;
- F== 0/1/2 - To broadcast voice after trigger, where 0 means no broadcast (i.e., door sensor detection without voice prompt), 1 is the seatbelt version, and 2 is the door sensor detection version.
our prefered command UART,1,0,60,100,1,0
Troubleshooting
The device will only record video when the vehicle is running.
If you goto Trips and click on the VIDEO icon on the map bubble, you can request historical video.
If you are getting "video cannot be found" errors when requesting historical video, its likely due to a bug with where the firmware is not setting the timezone correctly, and the device cannot find the video on the SD card because the timezone is mismatched.
To confirm if this is an issue:
Send the commands:
- timesync
- timezone
- param
These commands should reply with
- timesync = GPS
- timezone = current:+00:00 set:+00:00
- param = IMEI:864xxxxxxxxxxxxx,GPS Time:60,TIMEZONE:+00:00
The timezone in param command will likely not match the timezone above, therefore you will need to send the RESTORE command to factory reset the device and re-setup the device with SMS commands.