| Line 25: |
Line 25: |
| | If camera is disconnected and later reconnected, a device will detect it by periodic camera ping packet. Once camera is detected, the device will reissue the reconfiguration procedure. | | If camera is disconnected and later reconnected, a device will detect it by periodic camera ping packet. Once camera is detected, the device will reissue the reconfiguration procedure. |
| | <br> | | <br> |
| − | ==DualCam update procedure==
| |
| − |
| |
| − | '''NOTE: This update procedure is for the DualCam which has 1.9.3 firmware version, if you already have DualCam firmware version 2.2.1, 2.2.2 or 2.2.3 skip to step 10.'''
| |
| − |
| |
| − | '''Firmware download for FMX125 and DualCam:'''
| |
| − |
| |
| − | Link: https://drive.teltonika.lt/d/e5c4b09a60b74fa5b6a0/
| |
| − |
| |
| − | Password: 3RpOAf96
| |
| − |
| |
| − |
| |
| − | '''DualCam firmware video update'''
| |
| − |
| |
| − | <youtube>https://www.youtube.com/watch?v=pqOHLWi29bE&ab_channel=TeltonikaTelematics</youtube><br><br>
| |
| − |
| |
| − | Before the update, FMx125 has to be updated first. The latest camera firmware requires 03.27.13.Rev.362 or newer firmware. After FMx125 update, update of the camera can start:
| |
| − |
| |
| − | 1 Connect the camera to the FMx125. Power up, wait for the configuration finish (about 30 seconds after power up).
| |
| − |
| |
| − | 2 Ensure, that power supply at all times has stable 14V and not less that 2.5A output. If update is performed with the camera, that is installed in the vehicle, it is strongly recommended to have the engine running for stable alternator power supply.
| |
| − |
| |
| − | 3 Make sure that the camera works and responds (for example, try getting an image or try sending “camgetver” and check whether for both front and rear camera firmware versions are returned).
| |
| − |
| |
| − | 4 Format the SD cards of both cameras using SMS command "'''camget_sdformat:<cam id>'''". Cam id is the same as in “'''camreq'''”: 1 - Front Camera, 2 - Rear Camera. For example:
| |
| − |
| |
| − | '''camget_sdformat:1'''
| |
| − |
| |
| − | '''camget_sdformat:2'''
| |
| − |
| |
| − | Our device will return success if the format goes well. The result returned of a successful SD card format:
| |
| − | Camera front/rear SD Card format success
| |
| − |
| |
| − | 5 After the cards are formatted, power off everything, disconnect the camera from FMx125 and take out the SD cards. If disconnecting FMx125 from the DualCam is not possible, disable external UART mode from the configuration:
| |
| − |
| |
| − | [[File:UART_MODE.jpg|alt=|frameless]]
| |
| − |
| |
| − | 6 After taking out SD cards, write the firmware file of V2.2.0 to the root of both (front/rear) SD cards. Do not rename the firmware file, it has to be as it is, "JPEG_IPC_APP".
| |
| − |
| |
| − | 7 Put the cards back in, power the camera on. Do not reconnect the camera to the FMx125 or configure RS232 mode back yet.
| |
| − |
| |
| − | 8 '''Wait 60-90s for 2.2.0 version (for 2.2.3 version wait 120s).''' You should hear a click from the rear camera after the update succeeds. That click sound indicates restart of the rear camera which happens after successful firmware update.
| |
| − |
| |
| − | 9 Even if you don't hear the clicking sound, reconnect the camera to the FMx125 (or reconfigure RS232 mode back to DualCam) after few minutes anyway and send SMS “camgetver” command to check the versions.
| |
| − |
| |
| − | At this point the command should return “Front/Rear camera camgetver failed.” If it does, it does not mean a problem, because V2.2.0 is a transitional firmware and it does not return version. Therefore, if the camera was returning V1.9.3/1.9.2 or other 1.9.X version, this means it has updated to the V2.2.0 successfully and update procedure can continue.
| |
| − |
| |
| − | 10 Format SD cards again as it is in step 4 and disconnect from the camera the FMx125. After that go with step 11.
| |
| − |
| |
| − | 11 Take the cards out and write the firmware files of V2.2.1 V2.2.2 and V2.2.3 to the root of both SD cards. The file name is“ALL221_IPC_BIN”, “ALL222_IPC_BIN” and “ALL223_IPC_BIN”. Again, do not rename it. '''(You must write 3 files to the SD card)'''
| |
| − |
| |
| − | 12 Repeat steps 7, and 8. After that go with step 13.
| |
| − |
| |
| − | '''Note: Only for 2.2.3 version wait 120 second'''
| |
| − |
| |
| − | 13 Now, if all went successfully, return to the '''“camgetver”''' should return this:
| |
| − | Front camera V2.2.3. Rear camera V2.2.3.
| |
| − |
| |
| − | If it does, that means the camera is updated to V2.2.3 successfully.
| |
| − |
| |
| − | 14 After the update, it would be advisable to format SD cards again.
| |
| − |
| |
| − | ===Potential issues and solutions===
| |
| − |
| |
| − | Update is pretty straightforward most of the time. However, sometimes the update does not trigger. In case it doesn’t and the camera does not update, check whether it is really disconnected from FMx125 device. If it is, do not power off the camera at first. Keep it powered on and take out and put back in both SD cards. After this, wait 60-90s again and check the firmware version using “camgetver”.
| |
| − |
| |
| − | If it still is not updated, disconnect from FMx125, power the camera off for at least 20 seconds and power it back on. Wait for a few minutes and then re-insert the cards again. Reconnect and check the firmware version using “camgetver”.
| |
| − |
| |
| − | Can also note that if just one camera updates, only front or only rear, all mentioned solutions and steps could be done to only camera.
| |
| − |
| |
| − | Reminder, that the rear camera is with IR LEDs and light sensor and the front one is without them.
| |
| − |
| |
| | ==Troubleshoot== | | ==Troubleshoot== |
| | | | |
