Idrive - User contributions [en]

X3 Firmware Changelog

2021-01-11T11:21:27Z

Alexandra:

==Version 40.9==

'''Bug'''
*[FX-439] - When connecting to wi-fi, connection gets stucked
*[FX-440] - Sometimes, updater app fails to install properly
*[FX-441] - Old updater app version is not compatible with newer fw version (40.8 fw version)
*[FX-442] - Occasionally, Updater app may not install firmware on the first try

==Version 40.8==

'''Bug'''
*[FX-390] - From time to time, camera uses swap memory, which may affect flash memory
*[FX-415] - When changing the network operator, the internet connection gets stucked
*[FX-416] - Incorrect camera status on GPS tracker
*[FX-433] - When inside camera is disabled, thumbnail should not merge both videos

'''Story'''
*[FX-352] - Firmware implementation of accelerometer shock triggering algorithm 1
*[FX-355] - Merge git updater code with master branch and begin testing
*[FX-365] - Fine tunning and preparing ML ACC for Alpha tests
*[FX-411] - Implement Power off event in Sleep Mode and in Transfer
*[FX-412] - Create a mechanism to upgrade Neural Networks via OTA
*[FX-413] - Implement buzzer for Shock and Speed events
*[FX-418] - Convert Seatbelt detection from HOG SVM to CNN
*[FX-427] - Closing IR leds after all triggers are closed
*[FX-428] - Modify features output network version to be available in Constructor
*[FX-429] - Reorganize S3 components to accept custom regions (Europe, Asia etc)
*[FX-431] - Investigate possible issue when camera doesn't restarts after 24 hours
*[FX-434] - Add JSON output parameter for GPS heading (Cartrack requirment)
*[FX-435] - Parametrize setting for deleting more than 7 days data

==Version 40.7==

'''Bug'''
*[FX-393] - Buzzer setting unavailable on 40.5 FW version
*[FX-397] - Camera doesn't start in Sleep Mode at IGN ON - IGN OFF - IGN ON sequence (FW versions affected 40.4, 40.5; solved in 40.6 )

'''Story'''
*[FX-400] - Improve algorithm in order to verify if events are uploaded on server and verify their size
*[FX-401] - Add 640x360 resolution for cellular events
*[FX-402] - Invert accelerometer axis using camera serial number

==Version 40.5==

'''Story'''
*[FX-391] - All Possible accident events will upload via cellular data.
*[FX-392] - Remove CR list from log file

==Version 40.4==

'''Bug'''
* [FX-373] - Events -> Speed events don't have FR thumbnail attached, even though previous events for that route have thumbnail

'''Story'''
* [FX-341] - Save image for distraction events
* [FX-361] - Implement new Idrive event format (containing all metadata) in JSON
* [FX-363] - Implementing Smart trigger event limitation
* [FX-364] - Converting trigger output parameters to new format
* [FX-367] - Implement new event websocket package
* [FX-377] - Hide driver name from FR thumbnail (GDPR rules)
* [FX-378] - Make preview size (cellular events) adjustable in order to reduce data traffic
* [FX-380] - Remove FR log update in order to reduce data traffic on FR module
* [FX-382] - Deep sleep at Ignition OFF - Instant wake up at Ignition ON
* [FX-384] - Skip Wi-Fi transfer for cell only clients
* [FX-385] - Create a mechanism to reboot camera after 24 hours if it is in Ign ON
* [FX-386] - Turn off display in light sleep mode
* [FX-389] - Implement Safe Mode (with E005 error code) on cellular upload in case camera has no vehicle assigned

==Version 40.3==

'''Bug'''

*[FX-376] - GPS position packages are added on route while speed is 0
*[FX-357] - Video keyframes issue - video streams in mp4 files start with 2 P-frames (non-keyframes) followed by the Keyframe
*[FX-358] - AI camera cannot load the settings from internal memory (E002)
*[FX-369] - Camera doesn't connect to mobile network while SIM is not active

'''Story'''

*[FX-375] - Improve seat belt HOG SVM algorithm for right side drivers
*[FX-353] - Implementing AI trigger's confidence output parameters
*[FX-356] - Extend Bluetooth protocol in order to add camera IP (mandatory for communication with iPhone)
*[FX-360] - Create a mechanism to store critical parameters (ex. serial no) to AOSP properties in case of E002 error

==Version 40.1==

'''Bug'''

*[FX-331] - Fix temperature issue in log file when temperature is lower than 10 degrees
*[FX-337] - Max speed may have wrong value for cellular events
*[FX-339] - Invalid gps coordinates are not uploaded for cellular events. This behavior may create confusion in event speed chart (Iris platform)
*[FX-344] - DAD events are not triggered when Speed is interogated more than one time per second
*[FX-346] - Possible DaD issues when driver is on the right side
*[FX-347] - In some rare cases Ignition On does not reboot the camera when camera is in sleep mode

'''Story'''

*[FX-292] - Add support for camera API scalability - provides a second URL to alternate server connections
*[FX-332] - Improve MySqlWrapper class (API client for connecting to MySql database) in order to allow a number of retries (6 by default) in case of errors
*[FX-333] - Improve Face Recognition process in order to reduce the number of connections on the Face Recognition server
*[FX-335] - Adjust bit rate in continuous recording / original events to have the same values like X2
*[FX-336] - Add timestamps in previews in order to reduce file size (from 700 Kb to 500 Kb); increase the preview bitrate from 500Kb to 700Kb (the preview size will be 700 kb again)
*[FX-338] - Implement error code E004 when video acquisition is freezing from some reason. Camera will reboot after few seconds.
*[FX-340] - Improve Face Recognition algorithm in order to validate a recognition below a safety threshold if the same person has been validated in the past for several times (based on a decay score function)
*[FX-342] - Integrate preview length, preview file size and impact second and pass them to NODE server during the upload of cellular events
*[FX-343] - Adjust GPS class to trigger DAD events when there is no signal for a while
*[FX-345] - Add a cache mechanism for network type (2G, 3G, 4G), signal strength (1, 2, 3, 4) and operator (carrier) when gsm is initialized in Ignition ON. Cache is used during wifi transfer with Factory Tool

==Version 40.0==

'''Bug'''

*[FX-93] - Firmware crash after 8h 35 min --> JNI ERROR (app bug): local reference table overflow (max=512)
*[FX-103] - Fix H264 Header from Encoder (amcvidenc-omxqcomvideoencoderavc)
*[FX-107] - Memory leak when streaming enabled and big latency
*[FX-109] - Dlib library performance issues
*[FX-120] - Droping frames on outside camera when SDW is running
*[FX-129] - Fix datetime in GPS file (the same date for all gps coordinates)
*[FX-130] - DAD is not closing properly on ignition off
*[FX-140] - Video preview out of sync
*[FX-148] - Event additional pictures are not uploaded while internet connection becomes unavailable
*[FX-150] - Adjust H264 circular buffer keyframe issue
*[FX-151] - Android camera2 is dropping frames
*[FX-167] - Camera issue - H264 header fix for Android 9
*[FX-171] - Accelerometer not found - I2C Little kernel issue
*[FX-173] - Cellular issues on new Android
*[FX-174] - Wi-Fi hotspot and WPA 2 issue on Android 9
*[FX-175] - GPS issues on new Android
*[FX-177] - SD card free up space logic fail
*[FX-179] - X3-OV2685 Board - GStreamer pipeline fail
*[FX-185] - AWS library issue -> S3 doesn't work with Android 9
*[FX-186] - FR library not working on Android 9
*[FX-187] - Bluetooth BLE crash in certain condition on one camera
*[FX-188] - Not enough IR light
*[FX-190] - Skipping frames on AHC SRC pipeline
*[FX-193] - Preview upload fail deletes files
*[FX-196] - DAD thumbnail not uploading
*[FX-197] - Don't write any _exit in code
*[FX-198] - Events are either created empty, or will have space partially alocated
*[FX-199] - The fps is lowered because of AI DAD library
*[FX-200] - AOSP doesn't update 3G signal strength
*[FX-202] - Live Speed Events and Live Request Events are not triggered in certain conditions
*[FX-204] - Preview clip is out of sync
*[FX-208] - DAD doesn't trigger properly
*[FX-209] - Preview clip has low quality in certain conditions
*[FX-214] - Facial Recognition process is not closing at ignition off
*[FX-216] - Video and Audio aren't properly muxed
*[FX-217] - Streaming to IRA has incorrect colors
*[FX-218] - X3 is crashing on bluetooth connection
*[FX-219] - Covered camera code is not optimized
*[FX-220] - False-positive results on covered camera
*[FX-221] - Preview created by IRA is not uploaded correctly
*[FX-222] - LTIWebsocketManager should work like on X2 device
*[FX-225] - On continuous recording from time to time old frames reappear
*[FX-231] - Wifi is sending incorrect signal strength on wifi connect
*[FX-233] - Creating a new event deletes all files from the device
*[FX-234] - Reconnecting to wifi while transferring enters an infinite loop
*[FX-240] - OTA full update won't be downloaded
*[FX-244] - USB isn't seen by FW from time to time
*[FX-245] - Updating AOSP with USB stick may break the device
*[FX-250] - Sometime SD Card is not mounted - the mount procedure should be excuted in a loop
*[FX-253] - Some of the cameras cannot connect to cellular
*[FX-256] - Outside image has red hallow
*[FX-269] - Cont Recording Requests are not working properly
*[FX-273] - Yellow wire triggers on rising edge and needs to trigger on falling edge
*[FX-275] - Image sensor improvements - IR
*[FX-276] - There are 5 sec gaps between two continuous recordings file segments
*[FX-286] - When inside camera is disabled, the preview collect is unstable for live requests
*[FX-298] - Preview video contains wrong frames at the end
*[FX-309] - Camera may stuck when checking the internet connection
*[FX-313] - Camera may stuck in ignition off procedure
*[FX-315] - Data send config interval doesn't allow 30 sec
*[FX-316] - Fix circular buffer issue for CR
*[FX-322] - At ignition on, camera doesn't reboot, but remains in connecting to wi-fi

'''Story'''

*[FX-3] - Create the concept of X3 Display module (messages, icons) - Engineering version
*[FX-4] - Test 3G/4G modem for Android
*[FX-6] - Preliminary evaluation for X3 android
*[FX-8] - Generate proprietary event files
*[FX-9] - Add opencv support on Andriod platform
*[FX-10] - X3 proof of concept on SC60/Android - WIFI + Bluetooth evaluation
*[FX-11] - X3 proof of concept on SC60/Android - video acquisition + encoding over GStreamer
*[FX-12] - X3 proof of concept on SC60/Android - GPS data acquisition + processing
*[FX-13] - X3 proof of concept on SC60/Android - Accelerometer data acquisition + processing
*[FX-14] - X3 proof of concept on SC60/Android - images / video acquisition
*[FX-15] - X3 proof of concept on SC60/Android - Preliminary OS evaluation
*[FX-16] - X3 Install Android OS on our SC60 boards
*[FX-17] - Create android development setup and evaluate existing code migration
*[FX-18] - Migrate GStreamer video code
*[FX-19] - Study GStreamer CMake porting
*[FX-20] - Verify dual camera acquisition for new GStreamer library
*[FX-21] - Proof of concept for audio acquisition in GStreamer
*[FX-22] - Android Driver integration for OV2680
*[FX-23] - Porting the X2 IAQ library to X3
*[FX-25] - H264 issue on circular buffer extraction
*[FX-26] - Adapt FFMPEG code to new version for Android
*[FX-27] - Android changes to support OV2680
*[FX-29] - Migrate Imedia to FastCV lib
*[FX-30] - Git Lab edit firmware test
*[FX-31] - Migrate preview mechanism to Android FW
*[FX-32] - Create module to control WIFI on Android
*[FX-33] - Implement changes for second camera support
*[FX-34] - Live streaming camera for lens focusing / image quality evalutation
*[FX-35] - Test X3 GPS data acquisition using a custom board
*[FX-36] - Bluetooth test
*[FX-37] - Study AOSP security permissions
*[FX-38] - Event Trigger ( periodic, speed, continuous recording) on X3
*[FX-39] - Create accelerometer driver
*[FX-40] - Porting System lib
*[FX-41] - Implement Shock events
*[FX-42] - Migrate Img_utils
*[FX-43] - Porting Devicelib
*[FX-44] - Implement Face Recognition
*[FX-46] - Porting Utils lib
*[FX-47] - Porting Cellular Communication lib
*[FX-48] - Porting Wi-Fi Module
*[FX-49] - Develop Display Module I
*[FX-64] - Porting Idatabase library
*[FX-66] - Create a small app to test X3 display and IR controller
*[FX-68] - Adapt MP3 encoder for GStreamer pipeline
*[FX-69] - Implement basic transfer solution via USB stick
*[FX-70] - Implement GPS Trigger and change the system data
*[FX-71] - Import Neurotec Libraries for Facial Recognition feature
*[FX-73] - Adapt GStreamer pipeline to extract RAW frames
*[FX-74] - Implement Event Preview mechanism
*[FX-75] - Integrate JPEG library to IMG-utils
*[FX-76] - Integrate NV12 to Gray scale conversion method
*[FX-77] - Integrate GPIO driver in Firmware
*[FX-78] - Migrate 30.8 X2 fixes
*[FX-80] - Create the APIs for manipulating RAW frames once they are extracted from GStreamer pipeline
*[FX-81] - Possible Memory Leak in JNI
*[FX-85] - Check G-force conversion from byte to double
*[FX-87] - Porting transfer module
*[FX-90] - Porting and optimizing Covered camera on GPU
*[FX-94] - Implement type X3 (/mnt/SDcard)
*[FX-95] - Set proper bitrate to preview event
*[FX-97] - Change thumbstone mechanism (save to SD card, transfer protocol, delete all thumbstone files)
*[FX-99] - Porting existing DAD I
*[FX-102] - Update Factory Tools to accept X3 Product
*[FX-106] - Create build scripts for all Computer Vision/ML libraries
*[FX-108] - Create icons for X3 display
*[FX-110] - Update the display module for the new icons
*[FX-112] - Implement API client for MySql / DynamoDB using HTTP requests
*[FX-113] - Fix lock buffer issue in GStreamer
*[FX-114] - Integrate QSML library
*[FX-115] - Implement API client for S3 storage
*[FX-118] - Implementing SDW to X3
*[FX-121] - Implement event trigger messages on display
*[FX-124] - Implement a mechanism in order to upload camera log using cellular
*[FX-125] - Study RFCOMM Bluetooth on X3
*[FX-127] - Study GATT Bluetooth on X3
*[FX-128] - Study wi-fi hotspot on X3
*[FX-131] - Install Android 9 on SC600
*[FX-134] - Integrate GATT Bluetooth
*[FX-135] - Preliminary test for Android 9 -> camera driver for image sensor
*[FX-136] - Force Android 9 to use UTC date
*[FX-137] - Create method to turn on/off IR leds
*[FX-138] - Adjust image sensor parameters for better night vision/image quality
*[FX-139] - Adjust Android parameters for better sound quality
*[FX-141] - Implement wi-fi hotspot for X3
*[FX-143] - Preliminary test for Android 9 - I2C4, sound, H264 encoding
*[FX-144] - Integrate CNN classes in FW
*[FX-145] - Create classes for DAD based on new CNN
*[FX-146] - Create trigger for new DAD algorithm
*[FX-147] - Implement Seat Belt event
*[FX-152] - Adapt Android 9 for our custom boards
*[FX-153] - Adapt web socket communication to operate over wi-fi
*[FX-154] - Add CPU usage in camera log
*[FX-156] - Implement BLE protocol
*[FX-157] - Adjust Facial Recognition algorithm to trigger detection based on a speed threshold
*[FX-160] - Improve camera video image quality
*[FX-161] - Study batch factory programming for X3
*[FX-162] - Create technical documentation for X3 product - marketing purposes
*[FX-163] - Study Android chromatics library
*[FX-164] - Turn the display on in Lk
*[FX-165] - Test audio on Android 9
*[FX-176] - Tune OV2685 image parameters
*[FX-180] - Camera solutions for OV2685 driver- HAL incompatibility
*[FX-191] - Implement power failure condition
*[FX-194] - X3 library management
*[FX-195] - Implement Factory Application
*[FX-203] - Update Display Info
*[FX-207] - X3 must start wih 1970
*[FX-210] - Implement USB stick update in ignition on and transfer events in ignition off
*[FX-212] - Detach preview from events process
*[FX-213] - Upload preview even if SD card is not present
*[FX-215] - Add de-bounce for wired trigger
*[FX-224] - Verify preview upload at ignition off phase
*[FX-230] - Strip down G-streamer libraries
*[FX-236] - Long-time stress testing app for X3
*[FX-241] - Test USB update
*[FX-242] - Test Wifi reconnection
*[FX-246] - Manage RAM Disk at FW start (delete all existing files)
*[FX-247] - Implement display notification for update app
*[FX-248] - Implement ScanDisk procedure at ignition phase
*[FX-249] - Strip down OpenCV library
*[FX-251] - Add new error code on display if settings.db is missing
*[FX-254] - Document existing changes in GIT commits
*[FX-255] - Update SNPE to 1.31 for performance improvements
*[FX-258] - Refactoring Wi-Fi module
*[FX-259] - Improving FR detection algorithm (inserting Face Template in all events triggered in that session)
*[FX-264] - Research updating Firmware files with GIT
*[FX-265] - Implement updating Firmware files with GIT
*[FX-268] - Adjust BIAS for microphone sensitivity
*[FX-271] - Implement buzzer module for DAD
*[FX-272] - Display an error code in case GPS is missing
*[FX-280] - Install and configure AI beta cameras
*[FX-281] - Preliminary temperature tests for AI
*[FX-293] - Full temperature tests with features active SDW + DAD + FR
*[FX-294] - Format SD card code
*[FX-295] - Investigate auto update for X3 updater
*[FX-296] - Create versioning in neural networks for easy updates in the future
*[FX-297] - Implement Format SD card code in Factory tool
*[FX-299] - Testing and programming 7 AI cameras with Factory tool
*[FX-301] - Add a mechanism to trigger modem scan
*[FX-302] - Create a mechanism for updating the updater app in Firmware
*[FX-303] - Upgrade Factory Application
*[FX-305] - Factory tool installation manual
*[FX-306] - Modify default settings according to Al's suggestions (see attached)
*[FX-308] - Control auto exposure and auto gain from FW for camera calibration
*[FX-318] - Investigate SD card errors on some cameras

X3 Firmware Changelog

2021-01-11T11:20:24Z

Alexandra:

==Version 40.8==

'''Bug'''
*[FX-390] - From time to time, camera uses swap memory, which may affect flash memory
*[FX-415] - When changing the network operator, the internet connection gets stucked
*[FX-416] - Incorrect camera status on GPS tracker
*[FX-433] - When inside camera is disabled, thumbnail should not merge both videos

'''Story'''
*[FX-352] - Firmware implementation of accelerometer shock triggering algorithm 1
*[FX-355] - Merge git updater code with master branch and begin testing
*[FX-365] - Fine tunning and preparing ML ACC for Alpha tests
*[FX-411] - Implement Power off event in Sleep Mode and in Transfer
*[FX-412] - Create a mechanism to upgrade Neural Networks via OTA
*[FX-413] - Implement buzzer for Shock and Speed events
*[FX-418] - Convert Seatbelt detection from HOG SVM to CNN
*[FX-427] - Closing IR leds after all triggers are closed
*[FX-428] - Modify features output network version to be available in Constructor
*[FX-429] - Reorganize S3 components to accept custom regions (Europe, Asia etc)
*[FX-431] - Investigate possible issue when camera doesn't restarts after 24 hours
*[FX-434] - Add JSON output parameter for GPS heading (Cartrack requirment)
*[FX-435] - Parametrize setting for deleting more than 7 days data

==Version 40.7==

'''Bug'''
*[FX-393] - Buzzer setting unavailable on 40.5 FW version
*[FX-397] - Camera doesn't start in Sleep Mode at IGN ON - IGN OFF - IGN ON sequence (FW versions affected 40.4, 40.5; solved in 40.6 )

'''Story'''
*[FX-400] - Improve algorithm in order to verify if events are uploaded on server and verify their size
*[FX-401] - Add 640x360 resolution for cellular events
*[FX-402] - Invert accelerometer axis using camera serial number

==Version 40.5==

'''Story'''
*[FX-391] - All Possible accident events will upload via cellular data.
*[FX-392] - Remove CR list from log file

==Version 40.4==

'''Bug'''
* [FX-373] - Events -> Speed events don't have FR thumbnail attached, even though previous events for that route have thumbnail

'''Story'''
* [FX-341] - Save image for distraction events
* [FX-361] - Implement new Idrive event format (containing all metadata) in JSON
* [FX-363] - Implementing Smart trigger event limitation
* [FX-364] - Converting trigger output parameters to new format
* [FX-367] - Implement new event websocket package
* [FX-377] - Hide driver name from FR thumbnail (GDPR rules)
* [FX-378] - Make preview size (cellular events) adjustable in order to reduce data traffic
* [FX-380] - Remove FR log update in order to reduce data traffic on FR module
* [FX-382] - Deep sleep at Ignition OFF - Instant wake up at Ignition ON
* [FX-384] - Skip Wi-Fi transfer for cell only clients
* [FX-385] - Create a mechanism to reboot camera after 24 hours if it is in Ign ON
* [FX-386] - Turn off display in light sleep mode
* [FX-389] - Implement Safe Mode (with E005 error code) on cellular upload in case camera has no vehicle assigned

==Version 40.3==

'''Bug'''

*[FX-376] - GPS position packages are added on route while speed is 0
*[FX-357] - Video keyframes issue - video streams in mp4 files start with 2 P-frames (non-keyframes) followed by the Keyframe
*[FX-358] - AI camera cannot load the settings from internal memory (E002)
*[FX-369] - Camera doesn't connect to mobile network while SIM is not active

'''Story'''

*[FX-375] - Improve seat belt HOG SVM algorithm for right side drivers
*[FX-353] - Implementing AI trigger's confidence output parameters
*[FX-356] - Extend Bluetooth protocol in order to add camera IP (mandatory for communication with iPhone)
*[FX-360] - Create a mechanism to store critical parameters (ex. serial no) to AOSP properties in case of E002 error

==Version 40.1==

'''Bug'''

*[FX-331] - Fix temperature issue in log file when temperature is lower than 10 degrees
*[FX-337] - Max speed may have wrong value for cellular events
*[FX-339] - Invalid gps coordinates are not uploaded for cellular events. This behavior may create confusion in event speed chart (Iris platform)
*[FX-344] - DAD events are not triggered when Speed is interogated more than one time per second
*[FX-346] - Possible DaD issues when driver is on the right side
*[FX-347] - In some rare cases Ignition On does not reboot the camera when camera is in sleep mode

'''Story'''

*[FX-292] - Add support for camera API scalability - provides a second URL to alternate server connections
*[FX-332] - Improve MySqlWrapper class (API client for connecting to MySql database) in order to allow a number of retries (6 by default) in case of errors
*[FX-333] - Improve Face Recognition process in order to reduce the number of connections on the Face Recognition server
*[FX-335] - Adjust bit rate in continuous recording / original events to have the same values like X2
*[FX-336] - Add timestamps in previews in order to reduce file size (from 700 Kb to 500 Kb); increase the preview bitrate from 500Kb to 700Kb (the preview size will be 700 kb again)
*[FX-338] - Implement error code E004 when video acquisition is freezing from some reason. Camera will reboot after few seconds.
*[FX-340] - Improve Face Recognition algorithm in order to validate a recognition below a safety threshold if the same person has been validated in the past for several times (based on a decay score function)
*[FX-342] - Integrate preview length, preview file size and impact second and pass them to NODE server during the upload of cellular events
*[FX-343] - Adjust GPS class to trigger DAD events when there is no signal for a while
*[FX-345] - Add a cache mechanism for network type (2G, 3G, 4G), signal strength (1, 2, 3, 4) and operator (carrier) when gsm is initialized in Ignition ON. Cache is used during wifi transfer with Factory Tool

==Version 40.0==

'''Bug'''

*[FX-93] - Firmware crash after 8h 35 min --> JNI ERROR (app bug): local reference table overflow (max=512)
*[FX-103] - Fix H264 Header from Encoder (amcvidenc-omxqcomvideoencoderavc)
*[FX-107] - Memory leak when streaming enabled and big latency
*[FX-109] - Dlib library performance issues
*[FX-120] - Droping frames on outside camera when SDW is running
*[FX-129] - Fix datetime in GPS file (the same date for all gps coordinates)
*[FX-130] - DAD is not closing properly on ignition off
*[FX-140] - Video preview out of sync
*[FX-148] - Event additional pictures are not uploaded while internet connection becomes unavailable
*[FX-150] - Adjust H264 circular buffer keyframe issue
*[FX-151] - Android camera2 is dropping frames
*[FX-167] - Camera issue - H264 header fix for Android 9
*[FX-171] - Accelerometer not found - I2C Little kernel issue
*[FX-173] - Cellular issues on new Android
*[FX-174] - Wi-Fi hotspot and WPA 2 issue on Android 9
*[FX-175] - GPS issues on new Android
*[FX-177] - SD card free up space logic fail
*[FX-179] - X3-OV2685 Board - GStreamer pipeline fail
*[FX-185] - AWS library issue -> S3 doesn't work with Android 9
*[FX-186] - FR library not working on Android 9
*[FX-187] - Bluetooth BLE crash in certain condition on one camera
*[FX-188] - Not enough IR light
*[FX-190] - Skipping frames on AHC SRC pipeline
*[FX-193] - Preview upload fail deletes files
*[FX-196] - DAD thumbnail not uploading
*[FX-197] - Don't write any _exit in code
*[FX-198] - Events are either created empty, or will have space partially alocated
*[FX-199] - The fps is lowered because of AI DAD library
*[FX-200] - AOSP doesn't update 3G signal strength
*[FX-202] - Live Speed Events and Live Request Events are not triggered in certain conditions
*[FX-204] - Preview clip is out of sync
*[FX-208] - DAD doesn't trigger properly
*[FX-209] - Preview clip has low quality in certain conditions
*[FX-214] - Facial Recognition process is not closing at ignition off
*[FX-216] - Video and Audio aren't properly muxed
*[FX-217] - Streaming to IRA has incorrect colors
*[FX-218] - X3 is crashing on bluetooth connection
*[FX-219] - Covered camera code is not optimized
*[FX-220] - False-positive results on covered camera
*[FX-221] - Preview created by IRA is not uploaded correctly
*[FX-222] - LTIWebsocketManager should work like on X2 device
*[FX-225] - On continuous recording from time to time old frames reappear
*[FX-231] - Wifi is sending incorrect signal strength on wifi connect
*[FX-233] - Creating a new event deletes all files from the device
*[FX-234] - Reconnecting to wifi while transferring enters an infinite loop
*[FX-240] - OTA full update won't be downloaded
*[FX-244] - USB isn't seen by FW from time to time
*[FX-245] - Updating AOSP with USB stick may break the device
*[FX-250] - Sometime SD Card is not mounted - the mount procedure should be excuted in a loop
*[FX-253] - Some of the cameras cannot connect to cellular
*[FX-256] - Outside image has red hallow
*[FX-269] - Cont Recording Requests are not working properly
*[FX-273] - Yellow wire triggers on rising edge and needs to trigger on falling edge
*[FX-275] - Image sensor improvements - IR
*[FX-276] - There are 5 sec gaps between two continuous recordings file segments
*[FX-286] - When inside camera is disabled, the preview collect is unstable for live requests
*[FX-298] - Preview video contains wrong frames at the end
*[FX-309] - Camera may stuck when checking the internet connection
*[FX-313] - Camera may stuck in ignition off procedure
*[FX-315] - Data send config interval doesn't allow 30 sec
*[FX-316] - Fix circular buffer issue for CR
*[FX-322] - At ignition on, camera doesn't reboot, but remains in connecting to wi-fi

'''Story'''

*[FX-3] - Create the concept of X3 Display module (messages, icons) - Engineering version
*[FX-4] - Test 3G/4G modem for Android
*[FX-6] - Preliminary evaluation for X3 android
*[FX-8] - Generate proprietary event files
*[FX-9] - Add opencv support on Andriod platform
*[FX-10] - X3 proof of concept on SC60/Android - WIFI + Bluetooth evaluation
*[FX-11] - X3 proof of concept on SC60/Android - video acquisition + encoding over GStreamer
*[FX-12] - X3 proof of concept on SC60/Android - GPS data acquisition + processing
*[FX-13] - X3 proof of concept on SC60/Android - Accelerometer data acquisition + processing
*[FX-14] - X3 proof of concept on SC60/Android - images / video acquisition
*[FX-15] - X3 proof of concept on SC60/Android - Preliminary OS evaluation
*[FX-16] - X3 Install Android OS on our SC60 boards
*[FX-17] - Create android development setup and evaluate existing code migration
*[FX-18] - Migrate GStreamer video code
*[FX-19] - Study GStreamer CMake porting
*[FX-20] - Verify dual camera acquisition for new GStreamer library
*[FX-21] - Proof of concept for audio acquisition in GStreamer
*[FX-22] - Android Driver integration for OV2680
*[FX-23] - Porting the X2 IAQ library to X3
*[FX-25] - H264 issue on circular buffer extraction
*[FX-26] - Adapt FFMPEG code to new version for Android
*[FX-27] - Android changes to support OV2680
*[FX-29] - Migrate Imedia to FastCV lib
*[FX-30] - Git Lab edit firmware test
*[FX-31] - Migrate preview mechanism to Android FW
*[FX-32] - Create module to control WIFI on Android
*[FX-33] - Implement changes for second camera support
*[FX-34] - Live streaming camera for lens focusing / image quality evalutation
*[FX-35] - Test X3 GPS data acquisition using a custom board
*[FX-36] - Bluetooth test
*[FX-37] - Study AOSP security permissions
*[FX-38] - Event Trigger ( periodic, speed, continuous recording) on X3
*[FX-39] - Create accelerometer driver
*[FX-40] - Porting System lib
*[FX-41] - Implement Shock events
*[FX-42] - Migrate Img_utils
*[FX-43] - Porting Devicelib
*[FX-44] - Implement Face Recognition
*[FX-46] - Porting Utils lib
*[FX-47] - Porting Cellular Communication lib
*[FX-48] - Porting Wi-Fi Module
*[FX-49] - Develop Display Module I
*[FX-64] - Porting Idatabase library
*[FX-66] - Create a small app to test X3 display and IR controller
*[FX-68] - Adapt MP3 encoder for GStreamer pipeline
*[FX-69] - Implement basic transfer solution via USB stick
*[FX-70] - Implement GPS Trigger and change the system data
*[FX-71] - Import Neurotec Libraries for Facial Recognition feature
*[FX-73] - Adapt GStreamer pipeline to extract RAW frames
*[FX-74] - Implement Event Preview mechanism
*[FX-75] - Integrate JPEG library to IMG-utils
*[FX-76] - Integrate NV12 to Gray scale conversion method
*[FX-77] - Integrate GPIO driver in Firmware
*[FX-78] - Migrate 30.8 X2 fixes
*[FX-80] - Create the APIs for manipulating RAW frames once they are extracted from GStreamer pipeline
*[FX-81] - Possible Memory Leak in JNI
*[FX-85] - Check G-force conversion from byte to double
*[FX-87] - Porting transfer module
*[FX-90] - Porting and optimizing Covered camera on GPU
*[FX-94] - Implement type X3 (/mnt/SDcard)
*[FX-95] - Set proper bitrate to preview event
*[FX-97] - Change thumbstone mechanism (save to SD card, transfer protocol, delete all thumbstone files)
*[FX-99] - Porting existing DAD I
*[FX-102] - Update Factory Tools to accept X3 Product
*[FX-106] - Create build scripts for all Computer Vision/ML libraries
*[FX-108] - Create icons for X3 display
*[FX-110] - Update the display module for the new icons
*[FX-112] - Implement API client for MySql / DynamoDB using HTTP requests
*[FX-113] - Fix lock buffer issue in GStreamer
*[FX-114] - Integrate QSML library
*[FX-115] - Implement API client for S3 storage
*[FX-118] - Implementing SDW to X3
*[FX-121] - Implement event trigger messages on display
*[FX-124] - Implement a mechanism in order to upload camera log using cellular
*[FX-125] - Study RFCOMM Bluetooth on X3
*[FX-127] - Study GATT Bluetooth on X3
*[FX-128] - Study wi-fi hotspot on X3
*[FX-131] - Install Android 9 on SC600
*[FX-134] - Integrate GATT Bluetooth
*[FX-135] - Preliminary test for Android 9 -> camera driver for image sensor
*[FX-136] - Force Android 9 to use UTC date
*[FX-137] - Create method to turn on/off IR leds
*[FX-138] - Adjust image sensor parameters for better night vision/image quality
*[FX-139] - Adjust Android parameters for better sound quality
*[FX-141] - Implement wi-fi hotspot for X3
*[FX-143] - Preliminary test for Android 9 - I2C4, sound, H264 encoding
*[FX-144] - Integrate CNN classes in FW
*[FX-145] - Create classes for DAD based on new CNN
*[FX-146] - Create trigger for new DAD algorithm
*[FX-147] - Implement Seat Belt event
*[FX-152] - Adapt Android 9 for our custom boards
*[FX-153] - Adapt web socket communication to operate over wi-fi
*[FX-154] - Add CPU usage in camera log
*[FX-156] - Implement BLE protocol
*[FX-157] - Adjust Facial Recognition algorithm to trigger detection based on a speed threshold
*[FX-160] - Improve camera video image quality
*[FX-161] - Study batch factory programming for X3
*[FX-162] - Create technical documentation for X3 product - marketing purposes
*[FX-163] - Study Android chromatics library
*[FX-164] - Turn the display on in Lk
*[FX-165] - Test audio on Android 9
*[FX-176] - Tune OV2685 image parameters
*[FX-180] - Camera solutions for OV2685 driver- HAL incompatibility
*[FX-191] - Implement power failure condition
*[FX-194] - X3 library management
*[FX-195] - Implement Factory Application
*[FX-203] - Update Display Info
*[FX-207] - X3 must start wih 1970
*[FX-210] - Implement USB stick update in ignition on and transfer events in ignition off
*[FX-212] - Detach preview from events process
*[FX-213] - Upload preview even if SD card is not present
*[FX-215] - Add de-bounce for wired trigger
*[FX-224] - Verify preview upload at ignition off phase
*[FX-230] - Strip down G-streamer libraries
*[FX-236] - Long-time stress testing app for X3
*[FX-241] - Test USB update
*[FX-242] - Test Wifi reconnection
*[FX-246] - Manage RAM Disk at FW start (delete all existing files)
*[FX-247] - Implement display notification for update app
*[FX-248] - Implement ScanDisk procedure at ignition phase
*[FX-249] - Strip down OpenCV library
*[FX-251] - Add new error code on display if settings.db is missing
*[FX-254] - Document existing changes in GIT commits
*[FX-255] - Update SNPE to 1.31 for performance improvements
*[FX-258] - Refactoring Wi-Fi module
*[FX-259] - Improving FR detection algorithm (inserting Face Template in all events triggered in that session)
*[FX-264] - Research updating Firmware files with GIT
*[FX-265] - Implement updating Firmware files with GIT
*[FX-268] - Adjust BIAS for microphone sensitivity
*[FX-271] - Implement buzzer module for DAD
*[FX-272] - Display an error code in case GPS is missing
*[FX-280] - Install and configure AI beta cameras
*[FX-281] - Preliminary temperature tests for AI
*[FX-293] - Full temperature tests with features active SDW + DAD + FR
*[FX-294] - Format SD card code
*[FX-295] - Investigate auto update for X3 updater
*[FX-296] - Create versioning in neural networks for easy updates in the future
*[FX-297] - Implement Format SD card code in Factory tool
*[FX-299] - Testing and programming 7 AI cameras with Factory tool
*[FX-301] - Add a mechanism to trigger modem scan
*[FX-302] - Create a mechanism for updating the updater app in Firmware
*[FX-303] - Upgrade Factory Application
*[FX-305] - Factory tool installation manual
*[FX-306] - Modify default settings according to Al's suggestions (see attached)
*[FX-308] - Control auto exposure and auto gain from FW for camera calibration
*[FX-318] - Investigate SD card errors on some cameras

X3 Firmware Changelog

2020-10-23T11:40:43Z

Alexandra:

==Version 40.7==

'''Bug'''
*[FX-393] - Buzzer setting unavailable on 40.5 FW version
*[FX-397] - Camera doesn't start in Sleep Mode at IGN ON - IGN OFF - IGN ON sequence (FW versions affected 40.4, 40.5; solved in 40.6 )

'''Story'''
*[FX-400] - Improve algorithm in order to verify if events are uploaded on server and verify their size
*[FX-401] - Add 640x360 resolution for cellular events
*[FX-402] - Invert accelerometer axis using camera serial number

==Version 40.5==

'''Story'''
*[FX-391] - All Possible accident events will upload via cellular data.
*[FX-392] - Remove CR list from log file

==Version 40.4==

'''Bug'''
* [FX-373] - Events -> Speed events don't have FR thumbnail attached, even though previous events for that route have thumbnail

'''Story'''
* [FX-341] - Save image for distraction events
* [FX-361] - Implement new Idrive event format (containing all metadata) in JSON
* [FX-363] - Implementing Smart trigger event limitation
* [FX-364] - Converting trigger output parameters to new format
* [FX-367] - Implement new event websocket package
* [FX-377] - Hide driver name from FR thumbnail (GDPR rules)
* [FX-378] - Make preview size (cellular events) adjustable in order to reduce data traffic
* [FX-380] - Remove FR log update in order to reduce data traffic on FR module
* [FX-382] - Deep sleep at Ignition OFF - Instant wake up at Ignition ON
* [FX-384] - Skip Wi-Fi transfer for cell only clients
* [FX-385] - Create a mechanism to reboot camera after 24 hours if it is in Ign ON
* [FX-386] - Turn off display in light sleep mode
* [FX-389] - Implement Safe Mode (with E005 error code) on cellular upload in case camera has no vehicle assigned

==Version 40.3==

'''Bug'''

*[FX-376] - GPS position packages are added on route while speed is 0
*[FX-357] - Video keyframes issue - video streams in mp4 files start with 2 P-frames (non-keyframes) followed by the Keyframe
*[FX-358] - AI camera cannot load the settings from internal memory (E002)
*[FX-369] - Camera doesn't connect to mobile network while SIM is not active

'''Story'''

*[FX-375] - Improve seat belt HOG SVM algorithm for right side drivers
*[FX-353] - Implementing AI trigger's confidence output parameters
*[FX-356] - Extend Bluetooth protocol in order to add camera IP (mandatory for communication with iPhone)
*[FX-360] - Create a mechanism to store critical parameters (ex. serial no) to AOSP properties in case of E002 error

==Version 40.1==

'''Bug'''

*[FX-331] - Fix temperature issue in log file when temperature is lower than 10 degrees
*[FX-337] - Max speed may have wrong value for cellular events
*[FX-339] - Invalid gps coordinates are not uploaded for cellular events. This behavior may create confusion in event speed chart (Iris platform)
*[FX-344] - DAD events are not triggered when Speed is interogated more than one time per second
*[FX-346] - Possible DaD issues when driver is on the right side
*[FX-347] - In some rare cases Ignition On does not reboot the camera when camera is in sleep mode

'''Story'''

*[FX-292] - Add support for camera API scalability - provides a second URL to alternate server connections
*[FX-332] - Improve MySqlWrapper class (API client for connecting to MySql database) in order to allow a number of retries (6 by default) in case of errors
*[FX-333] - Improve Face Recognition process in order to reduce the number of connections on the Face Recognition server
*[FX-335] - Adjust bit rate in continuous recording / original events to have the same values like X2
*[FX-336] - Add timestamps in previews in order to reduce file size (from 700 Kb to 500 Kb); increase the preview bitrate from 500Kb to 700Kb (the preview size will be 700 kb again)
*[FX-338] - Implement error code E004 when video acquisition is freezing from some reason. Camera will reboot after few seconds.
*[FX-340] - Improve Face Recognition algorithm in order to validate a recognition below a safety threshold if the same person has been validated in the past for several times (based on a decay score function)
*[FX-342] - Integrate preview length, preview file size and impact second and pass them to NODE server during the upload of cellular events
*[FX-343] - Adjust GPS class to trigger DAD events when there is no signal for a while
*[FX-345] - Add a cache mechanism for network type (2G, 3G, 4G), signal strength (1, 2, 3, 4) and operator (carrier) when gsm is initialized in Ignition ON. Cache is used during wifi transfer with Factory Tool

==Version 40.0==

'''Bug'''

*[FX-93] - Firmware crash after 8h 35 min --> JNI ERROR (app bug): local reference table overflow (max=512)
*[FX-103] - Fix H264 Header from Encoder (amcvidenc-omxqcomvideoencoderavc)
*[FX-107] - Memory leak when streaming enabled and big latency
*[FX-109] - Dlib library performance issues
*[FX-120] - Droping frames on outside camera when SDW is running
*[FX-129] - Fix datetime in GPS file (the same date for all gps coordinates)
*[FX-130] - DAD is not closing properly on ignition off
*[FX-140] - Video preview out of sync
*[FX-148] - Event additional pictures are not uploaded while internet connection becomes unavailable
*[FX-150] - Adjust H264 circular buffer keyframe issue
*[FX-151] - Android camera2 is dropping frames
*[FX-167] - Camera issue - H264 header fix for Android 9
*[FX-171] - Accelerometer not found - I2C Little kernel issue
*[FX-173] - Cellular issues on new Android
*[FX-174] - Wi-Fi hotspot and WPA 2 issue on Android 9
*[FX-175] - GPS issues on new Android
*[FX-177] - SD card free up space logic fail
*[FX-179] - X3-OV2685 Board - GStreamer pipeline fail
*[FX-185] - AWS library issue -> S3 doesn't work with Android 9
*[FX-186] - FR library not working on Android 9
*[FX-187] - Bluetooth BLE crash in certain condition on one camera
*[FX-188] - Not enough IR light
*[FX-190] - Skipping frames on AHC SRC pipeline
*[FX-193] - Preview upload fail deletes files
*[FX-196] - DAD thumbnail not uploading
*[FX-197] - Don't write any _exit in code
*[FX-198] - Events are either created empty, or will have space partially alocated
*[FX-199] - The fps is lowered because of AI DAD library
*[FX-200] - AOSP doesn't update 3G signal strength
*[FX-202] - Live Speed Events and Live Request Events are not triggered in certain conditions
*[FX-204] - Preview clip is out of sync
*[FX-208] - DAD doesn't trigger properly
*[FX-209] - Preview clip has low quality in certain conditions
*[FX-214] - Facial Recognition process is not closing at ignition off
*[FX-216] - Video and Audio aren't properly muxed
*[FX-217] - Streaming to IRA has incorrect colors
*[FX-218] - X3 is crashing on bluetooth connection
*[FX-219] - Covered camera code is not optimized
*[FX-220] - False-positive results on covered camera
*[FX-221] - Preview created by IRA is not uploaded correctly
*[FX-222] - LTIWebsocketManager should work like on X2 device
*[FX-225] - On continuous recording from time to time old frames reappear
*[FX-231] - Wifi is sending incorrect signal strength on wifi connect
*[FX-233] - Creating a new event deletes all files from the device
*[FX-234] - Reconnecting to wifi while transferring enters an infinite loop
*[FX-240] - OTA full update won't be downloaded
*[FX-244] - USB isn't seen by FW from time to time
*[FX-245] - Updating AOSP with USB stick may break the device
*[FX-250] - Sometime SD Card is not mounted - the mount procedure should be excuted in a loop
*[FX-253] - Some of the cameras cannot connect to cellular
*[FX-256] - Outside image has red hallow
*[FX-269] - Cont Recording Requests are not working properly
*[FX-273] - Yellow wire triggers on rising edge and needs to trigger on falling edge
*[FX-275] - Image sensor improvements - IR
*[FX-276] - There are 5 sec gaps between two continuous recordings file segments
*[FX-286] - When inside camera is disabled, the preview collect is unstable for live requests
*[FX-298] - Preview video contains wrong frames at the end
*[FX-309] - Camera may stuck when checking the internet connection
*[FX-313] - Camera may stuck in ignition off procedure
*[FX-315] - Data send config interval doesn't allow 30 sec
*[FX-316] - Fix circular buffer issue for CR
*[FX-322] - At ignition on, camera doesn't reboot, but remains in connecting to wi-fi

'''Story'''

*[FX-3] - Create the concept of X3 Display module (messages, icons) - Engineering version
*[FX-4] - Test 3G/4G modem for Android
*[FX-6] - Preliminary evaluation for X3 android
*[FX-8] - Generate proprietary event files
*[FX-9] - Add opencv support on Andriod platform
*[FX-10] - X3 proof of concept on SC60/Android - WIFI + Bluetooth evaluation
*[FX-11] - X3 proof of concept on SC60/Android - video acquisition + encoding over GStreamer
*[FX-12] - X3 proof of concept on SC60/Android - GPS data acquisition + processing
*[FX-13] - X3 proof of concept on SC60/Android - Accelerometer data acquisition + processing
*[FX-14] - X3 proof of concept on SC60/Android - images / video acquisition
*[FX-15] - X3 proof of concept on SC60/Android - Preliminary OS evaluation
*[FX-16] - X3 Install Android OS on our SC60 boards
*[FX-17] - Create android development setup and evaluate existing code migration
*[FX-18] - Migrate GStreamer video code
*[FX-19] - Study GStreamer CMake porting
*[FX-20] - Verify dual camera acquisition for new GStreamer library
*[FX-21] - Proof of concept for audio acquisition in GStreamer
*[FX-22] - Android Driver integration for OV2680
*[FX-23] - Porting the X2 IAQ library to X3
*[FX-25] - H264 issue on circular buffer extraction
*[FX-26] - Adapt FFMPEG code to new version for Android
*[FX-27] - Android changes to support OV2680
*[FX-29] - Migrate Imedia to FastCV lib
*[FX-30] - Git Lab edit firmware test
*[FX-31] - Migrate preview mechanism to Android FW
*[FX-32] - Create module to control WIFI on Android
*[FX-33] - Implement changes for second camera support
*[FX-34] - Live streaming camera for lens focusing / image quality evalutation
*[FX-35] - Test X3 GPS data acquisition using a custom board
*[FX-36] - Bluetooth test
*[FX-37] - Study AOSP security permissions
*[FX-38] - Event Trigger ( periodic, speed, continuous recording) on X3
*[FX-39] - Create accelerometer driver
*[FX-40] - Porting System lib
*[FX-41] - Implement Shock events
*[FX-42] - Migrate Img_utils
*[FX-43] - Porting Devicelib
*[FX-44] - Implement Face Recognition
*[FX-46] - Porting Utils lib
*[FX-47] - Porting Cellular Communication lib
*[FX-48] - Porting Wi-Fi Module
*[FX-49] - Develop Display Module I
*[FX-64] - Porting Idatabase library
*[FX-66] - Create a small app to test X3 display and IR controller
*[FX-68] - Adapt MP3 encoder for GStreamer pipeline
*[FX-69] - Implement basic transfer solution via USB stick
*[FX-70] - Implement GPS Trigger and change the system data
*[FX-71] - Import Neurotec Libraries for Facial Recognition feature
*[FX-73] - Adapt GStreamer pipeline to extract RAW frames
*[FX-74] - Implement Event Preview mechanism
*[FX-75] - Integrate JPEG library to IMG-utils
*[FX-76] - Integrate NV12 to Gray scale conversion method
*[FX-77] - Integrate GPIO driver in Firmware
*[FX-78] - Migrate 30.8 X2 fixes
*[FX-80] - Create the APIs for manipulating RAW frames once they are extracted from GStreamer pipeline
*[FX-81] - Possible Memory Leak in JNI
*[FX-85] - Check G-force conversion from byte to double
*[FX-87] - Porting transfer module
*[FX-90] - Porting and optimizing Covered camera on GPU
*[FX-94] - Implement type X3 (/mnt/SDcard)
*[FX-95] - Set proper bitrate to preview event
*[FX-97] - Change thumbstone mechanism (save to SD card, transfer protocol, delete all thumbstone files)
*[FX-99] - Porting existing DAD I
*[FX-102] - Update Factory Tools to accept X3 Product
*[FX-106] - Create build scripts for all Computer Vision/ML libraries
*[FX-108] - Create icons for X3 display
*[FX-110] - Update the display module for the new icons
*[FX-112] - Implement API client for MySql / DynamoDB using HTTP requests
*[FX-113] - Fix lock buffer issue in GStreamer
*[FX-114] - Integrate QSML library
*[FX-115] - Implement API client for S3 storage
*[FX-118] - Implementing SDW to X3
*[FX-121] - Implement event trigger messages on display
*[FX-124] - Implement a mechanism in order to upload camera log using cellular
*[FX-125] - Study RFCOMM Bluetooth on X3
*[FX-127] - Study GATT Bluetooth on X3
*[FX-128] - Study wi-fi hotspot on X3
*[FX-131] - Install Android 9 on SC600
*[FX-134] - Integrate GATT Bluetooth
*[FX-135] - Preliminary test for Android 9 -> camera driver for image sensor
*[FX-136] - Force Android 9 to use UTC date
*[FX-137] - Create method to turn on/off IR leds
*[FX-138] - Adjust image sensor parameters for better night vision/image quality
*[FX-139] - Adjust Android parameters for better sound quality
*[FX-141] - Implement wi-fi hotspot for X3
*[FX-143] - Preliminary test for Android 9 - I2C4, sound, H264 encoding
*[FX-144] - Integrate CNN classes in FW
*[FX-145] - Create classes for DAD based on new CNN
*[FX-146] - Create trigger for new DAD algorithm
*[FX-147] - Implement Seat Belt event
*[FX-152] - Adapt Android 9 for our custom boards
*[FX-153] - Adapt web socket communication to operate over wi-fi
*[FX-154] - Add CPU usage in camera log
*[FX-156] - Implement BLE protocol
*[FX-157] - Adjust Facial Recognition algorithm to trigger detection based on a speed threshold
*[FX-160] - Improve camera video image quality
*[FX-161] - Study batch factory programming for X3
*[FX-162] - Create technical documentation for X3 product - marketing purposes
*[FX-163] - Study Android chromatics library
*[FX-164] - Turn the display on in Lk
*[FX-165] - Test audio on Android 9
*[FX-176] - Tune OV2685 image parameters
*[FX-180] - Camera solutions for OV2685 driver- HAL incompatibility
*[FX-191] - Implement power failure condition
*[FX-194] - X3 library management
*[FX-195] - Implement Factory Application
*[FX-203] - Update Display Info
*[FX-207] - X3 must start wih 1970
*[FX-210] - Implement USB stick update in ignition on and transfer events in ignition off
*[FX-212] - Detach preview from events process
*[FX-213] - Upload preview even if SD card is not present
*[FX-215] - Add de-bounce for wired trigger
*[FX-224] - Verify preview upload at ignition off phase
*[FX-230] - Strip down G-streamer libraries
*[FX-236] - Long-time stress testing app for X3
*[FX-241] - Test USB update
*[FX-242] - Test Wifi reconnection
*[FX-246] - Manage RAM Disk at FW start (delete all existing files)
*[FX-247] - Implement display notification for update app
*[FX-248] - Implement ScanDisk procedure at ignition phase
*[FX-249] - Strip down OpenCV library
*[FX-251] - Add new error code on display if settings.db is missing
*[FX-254] - Document existing changes in GIT commits
*[FX-255] - Update SNPE to 1.31 for performance improvements
*[FX-258] - Refactoring Wi-Fi module
*[FX-259] - Improving FR detection algorithm (inserting Face Template in all events triggered in that session)
*[FX-264] - Research updating Firmware files with GIT
*[FX-265] - Implement updating Firmware files with GIT
*[FX-268] - Adjust BIAS for microphone sensitivity
*[FX-271] - Implement buzzer module for DAD
*[FX-272] - Display an error code in case GPS is missing
*[FX-280] - Install and configure AI beta cameras
*[FX-281] - Preliminary temperature tests for AI
*[FX-293] - Full temperature tests with features active SDW + DAD + FR
*[FX-294] - Format SD card code
*[FX-295] - Investigate auto update for X3 updater
*[FX-296] - Create versioning in neural networks for easy updates in the future
*[FX-297] - Implement Format SD card code in Factory tool
*[FX-299] - Testing and programming 7 AI cameras with Factory tool
*[FX-301] - Add a mechanism to trigger modem scan
*[FX-302] - Create a mechanism for updating the updater app in Firmware
*[FX-303] - Upgrade Factory Application
*[FX-305] - Factory tool installation manual
*[FX-306] - Modify default settings according to Al's suggestions (see attached)
*[FX-308] - Control auto exposure and auto gain from FW for camera calibration
*[FX-318] - Investigate SD card errors on some cameras

X3 Firmware Changelog

2020-08-25T07:56:11Z

Alexandra:

==Version 40.5==

'''Story'''
*[FX-391] - All Possible accident events will upload via cellular data.
*[FX-392] - Remove CR list from log file

==Version 40.4==

'''Bug'''
* [FX-373] - Events -> Speed events don't have FR thumbnail attached, even though previous events for that route have thumbnail

'''Story'''
* [FX-341] - Save image for distraction events
* [FX-361] - Implement new Idrive event format (containing all metadata) in JSON
* [FX-363] - Implementing Smart trigger event limitation
* [FX-364] - Converting trigger output parameters to new format
* [FX-367] - Implement new event websocket package
* [FX-377] - Hide driver name from FR thumbnail (GDPR rules)
* [FX-378] - Make preview size (cellular events) adjustable in order to reduce data traffic
* [FX-380] - Remove FR log update in order to reduce data traffic on FR module
* [FX-382] - Deep sleep at Ignition OFF - Instant wake up at Ignition ON
* [FX-384] - Skip Wi-Fi transfer for cell only clients
* [FX-385] - Create a mechanism to reboot camera after 24 hours if it is in Ign ON
* [FX-386] - Turn off display in light sleep mode
* [FX-389] - Implement Safe Mode (with E005 error code) on cellular upload in case camera has no vehicle assigned

==Version 40.3==

'''Bug'''

*[FX-376] - GPS position packages are added on route while speed is 0
*[FX-357] - Video keyframes issue - video streams in mp4 files start with 2 P-frames (non-keyframes) followed by the Keyframe
*[FX-358] - AI camera cannot load the settings from internal memory (E002)
*[FX-369] - Camera doesn't connect to mobile network while SIM is not active

'''Story'''

*[FX-375] - Improve seat belt HOG SVM algorithm for right side drivers
*[FX-353] - Implementing AI trigger's confidence output parameters
*[FX-356] - Extend Bluetooth protocol in order to add camera IP (mandatory for communication with iPhone)
*[FX-360] - Create a mechanism to store critical parameters (ex. serial no) to AOSP properties in case of E002 error

==Version 40.1==

'''Bug'''

*[FX-331] - Fix temperature issue in log file when temperature is lower than 10 degrees
*[FX-337] - Max speed may have wrong value for cellular events
*[FX-339] - Invalid gps coordinates are not uploaded for cellular events. This behavior may create confusion in event speed chart (Iris platform)
*[FX-344] - DAD events are not triggered when Speed is interogated more than one time per second
*[FX-346] - Possible DaD issues when driver is on the right side
*[FX-347] - In some rare cases Ignition On does not reboot the camera when camera is in sleep mode

'''Story'''

*[FX-292] - Add support for camera API scalability - provides a second URL to alternate server connections
*[FX-332] - Improve MySqlWrapper class (API client for connecting to MySql database) in order to allow a number of retries (6 by default) in case of errors
*[FX-333] - Improve Face Recognition process in order to reduce the number of connections on the Face Recognition server
*[FX-335] - Adjust bit rate in continuous recording / original events to have the same values like X2
*[FX-336] - Add timestamps in previews in order to reduce file size (from 700 Kb to 500 Kb); increase the preview bitrate from 500Kb to 700Kb (the preview size will be 700 kb again)
*[FX-338] - Implement error code E004 when video acquisition is freezing from some reason. Camera will reboot after few seconds.
*[FX-340] - Improve Face Recognition algorithm in order to validate a recognition below a safety threshold if the same person has been validated in the past for several times (based on a decay score function)
*[FX-342] - Integrate preview length, preview file size and impact second and pass them to NODE server during the upload of cellular events
*[FX-343] - Adjust GPS class to trigger DAD events when there is no signal for a while
*[FX-345] - Add a cache mechanism for network type (2G, 3G, 4G), signal strength (1, 2, 3, 4) and operator (carrier) when gsm is initialized in Ignition ON. Cache is used during wifi transfer with Factory Tool

==Version 40.0==

'''Bug'''

*[FX-93] - Firmware crash after 8h 35 min --> JNI ERROR (app bug): local reference table overflow (max=512)
*[FX-103] - Fix H264 Header from Encoder (amcvidenc-omxqcomvideoencoderavc)
*[FX-107] - Memory leak when streaming enabled and big latency
*[FX-109] - Dlib library performance issues
*[FX-120] - Droping frames on outside camera when SDW is running
*[FX-129] - Fix datetime in GPS file (the same date for all gps coordinates)
*[FX-130] - DAD is not closing properly on ignition off
*[FX-140] - Video preview out of sync
*[FX-148] - Event additional pictures are not uploaded while internet connection becomes unavailable
*[FX-150] - Adjust H264 circular buffer keyframe issue
*[FX-151] - Android camera2 is dropping frames
*[FX-167] - Camera issue - H264 header fix for Android 9
*[FX-171] - Accelerometer not found - I2C Little kernel issue
*[FX-173] - Cellular issues on new Android
*[FX-174] - Wi-Fi hotspot and WPA 2 issue on Android 9
*[FX-175] - GPS issues on new Android
*[FX-177] - SD card free up space logic fail
*[FX-179] - X3-OV2685 Board - GStreamer pipeline fail
*[FX-185] - AWS library issue -> S3 doesn't work with Android 9
*[FX-186] - FR library not working on Android 9
*[FX-187] - Bluetooth BLE crash in certain condition on one camera
*[FX-188] - Not enough IR light
*[FX-190] - Skipping frames on AHC SRC pipeline
*[FX-193] - Preview upload fail deletes files
*[FX-196] - DAD thumbnail not uploading
*[FX-197] - Don't write any _exit in code
*[FX-198] - Events are either created empty, or will have space partially alocated
*[FX-199] - The fps is lowered because of AI DAD library
*[FX-200] - AOSP doesn't update 3G signal strength
*[FX-202] - Live Speed Events and Live Request Events are not triggered in certain conditions
*[FX-204] - Preview clip is out of sync
*[FX-208] - DAD doesn't trigger properly
*[FX-209] - Preview clip has low quality in certain conditions
*[FX-214] - Facial Recognition process is not closing at ignition off
*[FX-216] - Video and Audio aren't properly muxed
*[FX-217] - Streaming to IRA has incorrect colors
*[FX-218] - X3 is crashing on bluetooth connection
*[FX-219] - Covered camera code is not optimized
*[FX-220] - False-positive results on covered camera
*[FX-221] - Preview created by IRA is not uploaded correctly
*[FX-222] - LTIWebsocketManager should work like on X2 device
*[FX-225] - On continuous recording from time to time old frames reappear
*[FX-231] - Wifi is sending incorrect signal strength on wifi connect
*[FX-233] - Creating a new event deletes all files from the device
*[FX-234] - Reconnecting to wifi while transferring enters an infinite loop
*[FX-240] - OTA full update won't be downloaded
*[FX-244] - USB isn't seen by FW from time to time
*[FX-245] - Updating AOSP with USB stick may break the device
*[FX-250] - Sometime SD Card is not mounted - the mount procedure should be excuted in a loop
*[FX-253] - Some of the cameras cannot connect to cellular
*[FX-256] - Outside image has red hallow
*[FX-269] - Cont Recording Requests are not working properly
*[FX-273] - Yellow wire triggers on rising edge and needs to trigger on falling edge
*[FX-275] - Image sensor improvements - IR
*[FX-276] - There are 5 sec gaps between two continuous recordings file segments
*[FX-286] - When inside camera is disabled, the preview collect is unstable for live requests
*[FX-298] - Preview video contains wrong frames at the end
*[FX-309] - Camera may stuck when checking the internet connection
*[FX-313] - Camera may stuck in ignition off procedure
*[FX-315] - Data send config interval doesn't allow 30 sec
*[FX-316] - Fix circular buffer issue for CR
*[FX-322] - At ignition on, camera doesn't reboot, but remains in connecting to wi-fi

'''Story'''

*[FX-3] - Create the concept of X3 Display module (messages, icons) - Engineering version
*[FX-4] - Test 3G/4G modem for Android
*[FX-6] - Preliminary evaluation for X3 android
*[FX-8] - Generate proprietary event files
*[FX-9] - Add opencv support on Andriod platform
*[FX-10] - X3 proof of concept on SC60/Android - WIFI + Bluetooth evaluation
*[FX-11] - X3 proof of concept on SC60/Android - video acquisition + encoding over GStreamer
*[FX-12] - X3 proof of concept on SC60/Android - GPS data acquisition + processing
*[FX-13] - X3 proof of concept on SC60/Android - Accelerometer data acquisition + processing
*[FX-14] - X3 proof of concept on SC60/Android - images / video acquisition
*[FX-15] - X3 proof of concept on SC60/Android - Preliminary OS evaluation
*[FX-16] - X3 Install Android OS on our SC60 boards
*[FX-17] - Create android development setup and evaluate existing code migration
*[FX-18] - Migrate GStreamer video code
*[FX-19] - Study GStreamer CMake porting
*[FX-20] - Verify dual camera acquisition for new GStreamer library
*[FX-21] - Proof of concept for audio acquisition in GStreamer
*[FX-22] - Android Driver integration for OV2680
*[FX-23] - Porting the X2 IAQ library to X3
*[FX-25] - H264 issue on circular buffer extraction
*[FX-26] - Adapt FFMPEG code to new version for Android
*[FX-27] - Android changes to support OV2680
*[FX-29] - Migrate Imedia to FastCV lib
*[FX-30] - Git Lab edit firmware test
*[FX-31] - Migrate preview mechanism to Android FW
*[FX-32] - Create module to control WIFI on Android
*[FX-33] - Implement changes for second camera support
*[FX-34] - Live streaming camera for lens focusing / image quality evalutation
*[FX-35] - Test X3 GPS data acquisition using a custom board
*[FX-36] - Bluetooth test
*[FX-37] - Study AOSP security permissions
*[FX-38] - Event Trigger ( periodic, speed, continuous recording) on X3
*[FX-39] - Create accelerometer driver
*[FX-40] - Porting System lib
*[FX-41] - Implement Shock events
*[FX-42] - Migrate Img_utils
*[FX-43] - Porting Devicelib
*[FX-44] - Implement Face Recognition
*[FX-46] - Porting Utils lib
*[FX-47] - Porting Cellular Communication lib
*[FX-48] - Porting Wi-Fi Module
*[FX-49] - Develop Display Module I
*[FX-64] - Porting Idatabase library
*[FX-66] - Create a small app to test X3 display and IR controller
*[FX-68] - Adapt MP3 encoder for GStreamer pipeline
*[FX-69] - Implement basic transfer solution via USB stick
*[FX-70] - Implement GPS Trigger and change the system data
*[FX-71] - Import Neurotec Libraries for Facial Recognition feature
*[FX-73] - Adapt GStreamer pipeline to extract RAW frames
*[FX-74] - Implement Event Preview mechanism
*[FX-75] - Integrate JPEG library to IMG-utils
*[FX-76] - Integrate NV12 to Gray scale conversion method
*[FX-77] - Integrate GPIO driver in Firmware
*[FX-78] - Migrate 30.8 X2 fixes
*[FX-80] - Create the APIs for manipulating RAW frames once they are extracted from GStreamer pipeline
*[FX-81] - Possible Memory Leak in JNI
*[FX-85] - Check G-force conversion from byte to double
*[FX-87] - Porting transfer module
*[FX-90] - Porting and optimizing Covered camera on GPU
*[FX-94] - Implement type X3 (/mnt/SDcard)
*[FX-95] - Set proper bitrate to preview event
*[FX-97] - Change thumbstone mechanism (save to SD card, transfer protocol, delete all thumbstone files)
*[FX-99] - Porting existing DAD I
*[FX-102] - Update Factory Tools to accept X3 Product
*[FX-106] - Create build scripts for all Computer Vision/ML libraries
*[FX-108] - Create icons for X3 display
*[FX-110] - Update the display module for the new icons
*[FX-112] - Implement API client for MySql / DynamoDB using HTTP requests
*[FX-113] - Fix lock buffer issue in GStreamer
*[FX-114] - Integrate QSML library
*[FX-115] - Implement API client for S3 storage
*[FX-118] - Implementing SDW to X3
*[FX-121] - Implement event trigger messages on display
*[FX-124] - Implement a mechanism in order to upload camera log using cellular
*[FX-125] - Study RFCOMM Bluetooth on X3
*[FX-127] - Study GATT Bluetooth on X3
*[FX-128] - Study wi-fi hotspot on X3
*[FX-131] - Install Android 9 on SC600
*[FX-134] - Integrate GATT Bluetooth
*[FX-135] - Preliminary test for Android 9 -> camera driver for image sensor
*[FX-136] - Force Android 9 to use UTC date
*[FX-137] - Create method to turn on/off IR leds
*[FX-138] - Adjust image sensor parameters for better night vision/image quality
*[FX-139] - Adjust Android parameters for better sound quality
*[FX-141] - Implement wi-fi hotspot for X3
*[FX-143] - Preliminary test for Android 9 - I2C4, sound, H264 encoding
*[FX-144] - Integrate CNN classes in FW
*[FX-145] - Create classes for DAD based on new CNN
*[FX-146] - Create trigger for new DAD algorithm
*[FX-147] - Implement Seat Belt event
*[FX-152] - Adapt Android 9 for our custom boards
*[FX-153] - Adapt web socket communication to operate over wi-fi
*[FX-154] - Add CPU usage in camera log
*[FX-156] - Implement BLE protocol
*[FX-157] - Adjust Facial Recognition algorithm to trigger detection based on a speed threshold
*[FX-160] - Improve camera video image quality
*[FX-161] - Study batch factory programming for X3
*[FX-162] - Create technical documentation for X3 product - marketing purposes
*[FX-163] - Study Android chromatics library
*[FX-164] - Turn the display on in Lk
*[FX-165] - Test audio on Android 9
*[FX-176] - Tune OV2685 image parameters
*[FX-180] - Camera solutions for OV2685 driver- HAL incompatibility
*[FX-191] - Implement power failure condition
*[FX-194] - X3 library management
*[FX-195] - Implement Factory Application
*[FX-203] - Update Display Info
*[FX-207] - X3 must start wih 1970
*[FX-210] - Implement USB stick update in ignition on and transfer events in ignition off
*[FX-212] - Detach preview from events process
*[FX-213] - Upload preview even if SD card is not present
*[FX-215] - Add de-bounce for wired trigger
*[FX-224] - Verify preview upload at ignition off phase
*[FX-230] - Strip down G-streamer libraries
*[FX-236] - Long-time stress testing app for X3
*[FX-241] - Test USB update
*[FX-242] - Test Wifi reconnection
*[FX-246] - Manage RAM Disk at FW start (delete all existing files)
*[FX-247] - Implement display notification for update app
*[FX-248] - Implement ScanDisk procedure at ignition phase
*[FX-249] - Strip down OpenCV library
*[FX-251] - Add new error code on display if settings.db is missing
*[FX-254] - Document existing changes in GIT commits
*[FX-255] - Update SNPE to 1.31 for performance improvements
*[FX-258] - Refactoring Wi-Fi module
*[FX-259] - Improving FR detection algorithm (inserting Face Template in all events triggered in that session)
*[FX-264] - Research updating Firmware files with GIT
*[FX-265] - Implement updating Firmware files with GIT
*[FX-268] - Adjust BIAS for microphone sensitivity
*[FX-271] - Implement buzzer module for DAD
*[FX-272] - Display an error code in case GPS is missing
*[FX-280] - Install and configure AI beta cameras
*[FX-281] - Preliminary temperature tests for AI
*[FX-293] - Full temperature tests with features active SDW + DAD + FR
*[FX-294] - Format SD card code
*[FX-295] - Investigate auto update for X3 updater
*[FX-296] - Create versioning in neural networks for easy updates in the future
*[FX-297] - Implement Format SD card code in Factory tool
*[FX-299] - Testing and programming 7 AI cameras with Factory tool
*[FX-301] - Add a mechanism to trigger modem scan
*[FX-302] - Create a mechanism for updating the updater app in Firmware
*[FX-303] - Upgrade Factory Application
*[FX-305] - Factory tool installation manual
*[FX-306] - Modify default settings according to Al's suggestions (see attached)
*[FX-308] - Control auto exposure and auto gain from FW for camera calibration
*[FX-318] - Investigate SD card errors on some cameras

X3 Firmware Changelog

2020-08-24T10:11:17Z

Alexandra:

==Version 40.5==

'''Story'''
*[FX-391] - All Possible accident events will upload via cellular data.

==Version 40.4==

'''Bug'''
* [FX-373] - Events -> Speed events don't have FR thumbnail attached, even though previous events for that route have thumbnail

'''Story'''
* [FX-341] - Save image for distraction events
* [FX-361] - Implement new Idrive event format (containing all metadata) in JSON
* [FX-363] - Implementing Smart trigger event limitation
* [FX-364] - Converting trigger output parameters to new format
* [FX-367] - Implement new event websocket package
* [FX-377] - Hide driver name from FR thumbnail (GDPR rules)
* [FX-378] - Make preview size (cellular events) adjustable in order to reduce data traffic
* [FX-380] - Remove FR log update in order to reduce data traffic on FR module
* [FX-382] - Deep sleep at Ignition OFF - Instant wake up at Ignition ON
* [FX-384] - Skip Wi-Fi transfer for cell only clients
* [FX-385] - Create a mechanism to reboot camera after 24 hours if it is in Ign ON
* [FX-386] - Turn off display in light sleep mode
* [FX-389] - Implement Safe Mode (with E005 error code) on cellular upload in case camera has no vehicle assigned

==Version 40.3==

'''Bug'''

*[FX-376] - GPS position packages are added on route while speed is 0
*[FX-357] - Video keyframes issue - video streams in mp4 files start with 2 P-frames (non-keyframes) followed by the Keyframe
*[FX-358] - AI camera cannot load the settings from internal memory (E002)
*[FX-369] - Camera doesn't connect to mobile network while SIM is not active

'''Story'''

*[FX-375] - Improve seat belt HOG SVM algorithm for right side drivers
*[FX-353] - Implementing AI trigger's confidence output parameters
*[FX-356] - Extend Bluetooth protocol in order to add camera IP (mandatory for communication with iPhone)
*[FX-360] - Create a mechanism to store critical parameters (ex. serial no) to AOSP properties in case of E002 error

==Version 40.1==

'''Bug'''

*[FX-331] - Fix temperature issue in log file when temperature is lower than 10 degrees
*[FX-337] - Max speed may have wrong value for cellular events
*[FX-339] - Invalid gps coordinates are not uploaded for cellular events. This behavior may create confusion in event speed chart (Iris platform)
*[FX-344] - DAD events are not triggered when Speed is interogated more than one time per second
*[FX-346] - Possible DaD issues when driver is on the right side
*[FX-347] - In some rare cases Ignition On does not reboot the camera when camera is in sleep mode

'''Story'''

*[FX-292] - Add support for camera API scalability - provides a second URL to alternate server connections
*[FX-332] - Improve MySqlWrapper class (API client for connecting to MySql database) in order to allow a number of retries (6 by default) in case of errors
*[FX-333] - Improve Face Recognition process in order to reduce the number of connections on the Face Recognition server
*[FX-335] - Adjust bit rate in continuous recording / original events to have the same values like X2
*[FX-336] - Add timestamps in previews in order to reduce file size (from 700 Kb to 500 Kb); increase the preview bitrate from 500Kb to 700Kb (the preview size will be 700 kb again)
*[FX-338] - Implement error code E004 when video acquisition is freezing from some reason. Camera will reboot after few seconds.
*[FX-340] - Improve Face Recognition algorithm in order to validate a recognition below a safety threshold if the same person has been validated in the past for several times (based on a decay score function)
*[FX-342] - Integrate preview length, preview file size and impact second and pass them to NODE server during the upload of cellular events
*[FX-343] - Adjust GPS class to trigger DAD events when there is no signal for a while
*[FX-345] - Add a cache mechanism for network type (2G, 3G, 4G), signal strength (1, 2, 3, 4) and operator (carrier) when gsm is initialized in Ignition ON. Cache is used during wifi transfer with Factory Tool

==Version 40.0==

'''Bug'''

*[FX-93] - Firmware crash after 8h 35 min --> JNI ERROR (app bug): local reference table overflow (max=512)
*[FX-103] - Fix H264 Header from Encoder (amcvidenc-omxqcomvideoencoderavc)
*[FX-107] - Memory leak when streaming enabled and big latency
*[FX-109] - Dlib library performance issues
*[FX-120] - Droping frames on outside camera when SDW is running
*[FX-129] - Fix datetime in GPS file (the same date for all gps coordinates)
*[FX-130] - DAD is not closing properly on ignition off
*[FX-140] - Video preview out of sync
*[FX-148] - Event additional pictures are not uploaded while internet connection becomes unavailable
*[FX-150] - Adjust H264 circular buffer keyframe issue
*[FX-151] - Android camera2 is dropping frames
*[FX-167] - Camera issue - H264 header fix for Android 9
*[FX-171] - Accelerometer not found - I2C Little kernel issue
*[FX-173] - Cellular issues on new Android
*[FX-174] - Wi-Fi hotspot and WPA 2 issue on Android 9
*[FX-175] - GPS issues on new Android
*[FX-177] - SD card free up space logic fail
*[FX-179] - X3-OV2685 Board - GStreamer pipeline fail
*[FX-185] - AWS library issue -> S3 doesn't work with Android 9
*[FX-186] - FR library not working on Android 9
*[FX-187] - Bluetooth BLE crash in certain condition on one camera
*[FX-188] - Not enough IR light
*[FX-190] - Skipping frames on AHC SRC pipeline
*[FX-193] - Preview upload fail deletes files
*[FX-196] - DAD thumbnail not uploading
*[FX-197] - Don't write any _exit in code
*[FX-198] - Events are either created empty, or will have space partially alocated
*[FX-199] - The fps is lowered because of AI DAD library
*[FX-200] - AOSP doesn't update 3G signal strength
*[FX-202] - Live Speed Events and Live Request Events are not triggered in certain conditions
*[FX-204] - Preview clip is out of sync
*[FX-208] - DAD doesn't trigger properly
*[FX-209] - Preview clip has low quality in certain conditions
*[FX-214] - Facial Recognition process is not closing at ignition off
*[FX-216] - Video and Audio aren't properly muxed
*[FX-217] - Streaming to IRA has incorrect colors
*[FX-218] - X3 is crashing on bluetooth connection
*[FX-219] - Covered camera code is not optimized
*[FX-220] - False-positive results on covered camera
*[FX-221] - Preview created by IRA is not uploaded correctly
*[FX-222] - LTIWebsocketManager should work like on X2 device
*[FX-225] - On continuous recording from time to time old frames reappear
*[FX-231] - Wifi is sending incorrect signal strength on wifi connect
*[FX-233] - Creating a new event deletes all files from the device
*[FX-234] - Reconnecting to wifi while transferring enters an infinite loop
*[FX-240] - OTA full update won't be downloaded
*[FX-244] - USB isn't seen by FW from time to time
*[FX-245] - Updating AOSP with USB stick may break the device
*[FX-250] - Sometime SD Card is not mounted - the mount procedure should be excuted in a loop
*[FX-253] - Some of the cameras cannot connect to cellular
*[FX-256] - Outside image has red hallow
*[FX-269] - Cont Recording Requests are not working properly
*[FX-273] - Yellow wire triggers on rising edge and needs to trigger on falling edge
*[FX-275] - Image sensor improvements - IR
*[FX-276] - There are 5 sec gaps between two continuous recordings file segments
*[FX-286] - When inside camera is disabled, the preview collect is unstable for live requests
*[FX-298] - Preview video contains wrong frames at the end
*[FX-309] - Camera may stuck when checking the internet connection
*[FX-313] - Camera may stuck in ignition off procedure
*[FX-315] - Data send config interval doesn't allow 30 sec
*[FX-316] - Fix circular buffer issue for CR
*[FX-322] - At ignition on, camera doesn't reboot, but remains in connecting to wi-fi

'''Story'''

*[FX-3] - Create the concept of X3 Display module (messages, icons) - Engineering version
*[FX-4] - Test 3G/4G modem for Android
*[FX-6] - Preliminary evaluation for X3 android
*[FX-8] - Generate proprietary event files
*[FX-9] - Add opencv support on Andriod platform
*[FX-10] - X3 proof of concept on SC60/Android - WIFI + Bluetooth evaluation
*[FX-11] - X3 proof of concept on SC60/Android - video acquisition + encoding over GStreamer
*[FX-12] - X3 proof of concept on SC60/Android - GPS data acquisition + processing
*[FX-13] - X3 proof of concept on SC60/Android - Accelerometer data acquisition + processing
*[FX-14] - X3 proof of concept on SC60/Android - images / video acquisition
*[FX-15] - X3 proof of concept on SC60/Android - Preliminary OS evaluation
*[FX-16] - X3 Install Android OS on our SC60 boards
*[FX-17] - Create android development setup and evaluate existing code migration
*[FX-18] - Migrate GStreamer video code
*[FX-19] - Study GStreamer CMake porting
*[FX-20] - Verify dual camera acquisition for new GStreamer library
*[FX-21] - Proof of concept for audio acquisition in GStreamer
*[FX-22] - Android Driver integration for OV2680
*[FX-23] - Porting the X2 IAQ library to X3
*[FX-25] - H264 issue on circular buffer extraction
*[FX-26] - Adapt FFMPEG code to new version for Android
*[FX-27] - Android changes to support OV2680
*[FX-29] - Migrate Imedia to FastCV lib
*[FX-30] - Git Lab edit firmware test
*[FX-31] - Migrate preview mechanism to Android FW
*[FX-32] - Create module to control WIFI on Android
*[FX-33] - Implement changes for second camera support
*[FX-34] - Live streaming camera for lens focusing / image quality evalutation
*[FX-35] - Test X3 GPS data acquisition using a custom board
*[FX-36] - Bluetooth test
*[FX-37] - Study AOSP security permissions
*[FX-38] - Event Trigger ( periodic, speed, continuous recording) on X3
*[FX-39] - Create accelerometer driver
*[FX-40] - Porting System lib
*[FX-41] - Implement Shock events
*[FX-42] - Migrate Img_utils
*[FX-43] - Porting Devicelib
*[FX-44] - Implement Face Recognition
*[FX-46] - Porting Utils lib
*[FX-47] - Porting Cellular Communication lib
*[FX-48] - Porting Wi-Fi Module
*[FX-49] - Develop Display Module I
*[FX-64] - Porting Idatabase library
*[FX-66] - Create a small app to test X3 display and IR controller
*[FX-68] - Adapt MP3 encoder for GStreamer pipeline
*[FX-69] - Implement basic transfer solution via USB stick
*[FX-70] - Implement GPS Trigger and change the system data
*[FX-71] - Import Neurotec Libraries for Facial Recognition feature
*[FX-73] - Adapt GStreamer pipeline to extract RAW frames
*[FX-74] - Implement Event Preview mechanism
*[FX-75] - Integrate JPEG library to IMG-utils
*[FX-76] - Integrate NV12 to Gray scale conversion method
*[FX-77] - Integrate GPIO driver in Firmware
*[FX-78] - Migrate 30.8 X2 fixes
*[FX-80] - Create the APIs for manipulating RAW frames once they are extracted from GStreamer pipeline
*[FX-81] - Possible Memory Leak in JNI
*[FX-85] - Check G-force conversion from byte to double
*[FX-87] - Porting transfer module
*[FX-90] - Porting and optimizing Covered camera on GPU
*[FX-94] - Implement type X3 (/mnt/SDcard)
*[FX-95] - Set proper bitrate to preview event
*[FX-97] - Change thumbstone mechanism (save to SD card, transfer protocol, delete all thumbstone files)
*[FX-99] - Porting existing DAD I
*[FX-102] - Update Factory Tools to accept X3 Product
*[FX-106] - Create build scripts for all Computer Vision/ML libraries
*[FX-108] - Create icons for X3 display
*[FX-110] - Update the display module for the new icons
*[FX-112] - Implement API client for MySql / DynamoDB using HTTP requests
*[FX-113] - Fix lock buffer issue in GStreamer
*[FX-114] - Integrate QSML library
*[FX-115] - Implement API client for S3 storage
*[FX-118] - Implementing SDW to X3
*[FX-121] - Implement event trigger messages on display
*[FX-124] - Implement a mechanism in order to upload camera log using cellular
*[FX-125] - Study RFCOMM Bluetooth on X3
*[FX-127] - Study GATT Bluetooth on X3
*[FX-128] - Study wi-fi hotspot on X3
*[FX-131] - Install Android 9 on SC600
*[FX-134] - Integrate GATT Bluetooth
*[FX-135] - Preliminary test for Android 9 -> camera driver for image sensor
*[FX-136] - Force Android 9 to use UTC date
*[FX-137] - Create method to turn on/off IR leds
*[FX-138] - Adjust image sensor parameters for better night vision/image quality
*[FX-139] - Adjust Android parameters for better sound quality
*[FX-141] - Implement wi-fi hotspot for X3
*[FX-143] - Preliminary test for Android 9 - I2C4, sound, H264 encoding
*[FX-144] - Integrate CNN classes in FW
*[FX-145] - Create classes for DAD based on new CNN
*[FX-146] - Create trigger for new DAD algorithm
*[FX-147] - Implement Seat Belt event
*[FX-152] - Adapt Android 9 for our custom boards
*[FX-153] - Adapt web socket communication to operate over wi-fi
*[FX-154] - Add CPU usage in camera log
*[FX-156] - Implement BLE protocol
*[FX-157] - Adjust Facial Recognition algorithm to trigger detection based on a speed threshold
*[FX-160] - Improve camera video image quality
*[FX-161] - Study batch factory programming for X3
*[FX-162] - Create technical documentation for X3 product - marketing purposes
*[FX-163] - Study Android chromatics library
*[FX-164] - Turn the display on in Lk
*[FX-165] - Test audio on Android 9
*[FX-176] - Tune OV2685 image parameters
*[FX-180] - Camera solutions for OV2685 driver- HAL incompatibility
*[FX-191] - Implement power failure condition
*[FX-194] - X3 library management
*[FX-195] - Implement Factory Application
*[FX-203] - Update Display Info
*[FX-207] - X3 must start wih 1970
*[FX-210] - Implement USB stick update in ignition on and transfer events in ignition off
*[FX-212] - Detach preview from events process
*[FX-213] - Upload preview even if SD card is not present
*[FX-215] - Add de-bounce for wired trigger
*[FX-224] - Verify preview upload at ignition off phase
*[FX-230] - Strip down G-streamer libraries
*[FX-236] - Long-time stress testing app for X3
*[FX-241] - Test USB update
*[FX-242] - Test Wifi reconnection
*[FX-246] - Manage RAM Disk at FW start (delete all existing files)
*[FX-247] - Implement display notification for update app
*[FX-248] - Implement ScanDisk procedure at ignition phase
*[FX-249] - Strip down OpenCV library
*[FX-251] - Add new error code on display if settings.db is missing
*[FX-254] - Document existing changes in GIT commits
*[FX-255] - Update SNPE to 1.31 for performance improvements
*[FX-258] - Refactoring Wi-Fi module
*[FX-259] - Improving FR detection algorithm (inserting Face Template in all events triggered in that session)
*[FX-264] - Research updating Firmware files with GIT
*[FX-265] - Implement updating Firmware files with GIT
*[FX-268] - Adjust BIAS for microphone sensitivity
*[FX-271] - Implement buzzer module for DAD
*[FX-272] - Display an error code in case GPS is missing
*[FX-280] - Install and configure AI beta cameras
*[FX-281] - Preliminary temperature tests for AI
*[FX-293] - Full temperature tests with features active SDW + DAD + FR
*[FX-294] - Format SD card code
*[FX-295] - Investigate auto update for X3 updater
*[FX-296] - Create versioning in neural networks for easy updates in the future
*[FX-297] - Implement Format SD card code in Factory tool
*[FX-299] - Testing and programming 7 AI cameras with Factory tool
*[FX-301] - Add a mechanism to trigger modem scan
*[FX-302] - Create a mechanism for updating the updater app in Firmware
*[FX-303] - Upgrade Factory Application
*[FX-305] - Factory tool installation manual
*[FX-306] - Modify default settings according to Al's suggestions (see attached)
*[FX-308] - Control auto exposure and auto gain from FW for camera calibration
*[FX-318] - Investigate SD card errors on some cameras

Adaptive Event Limitation

2020-08-18T06:00:35Z

Alexandra:

This mechanism, available from the 40.4 Firmware release, limits the number of events uploaded via cellular on the cloud. All the events are still being stored to the SD card and if necessary, they can be retrieved via the mobile application (Android/IOS).

Event types which are limited are:

:*Shocks
:*Distraction/Drowsiness
:*Safe Distance Warning

The number of events for each type of trigger is dynamically adjusted during a route, using a function which depends on the distance traveled. This limitation is made per driving session (ignition on – ignition off cycle). When a new session begins, the algorithm will be restarted allowing the default 3 maximum events per trigger type and keep increasing the limit with the distance driven.

In a future release we will consider implementing this for a specified time (24 hours for example) instead of per ignition cycle for more hard and precise limitation (for the cases where there are a lot of ignition on-ignition off in a short period of time). For this we will need to store all the events numbers and driven miles across all the routes in that period of time in a local camera database.

The current methodology purpose is to get rid of data traffic for companies which are having excessive number of events (RMS, SSA, etc.). We are waiting to see and analyze the data traffic results of this method combined with the reduction in size of events to decide the future approach of the event limitation.

[[File:Annotation 2020-08-18 072525.png|750px]]

This 1st degree function is:

℮ = 3.2 + ∆ * 0.0297

Where:

:*℮ is the number of events uploads available (per trigger)
:*∆ is the route distance since the beginning of the route.

Practically, when you first start the route you have 3 events of each type available for upload, and on every 33 miles the limit increase with 1 event for each trigger. This function stops at 7 maximum events (per trigger) on a session no matter how much you will continue to drive.

'''Example:'''

If the driver has driven 100 miles, and made 3 shocks and 2 SDW’s until now the remaining upload number will be:

::#SHOCKS: 3 (available from the start) + 3 (driven 100 miles and each 33 miles you get another event you can upload) = 6. You already made 3 so you can upload 3 more max
::#SDW: 3 (available from the start) + 3 (driven 100 miles and each 33 miles you get another event you can upload) = 6. You already made 2 so you can upload 4 more max
::#All other triggers: 3 (available from the start) + 3 (driven 100 miles and each 33 miles you get another event you can upload) = 6 upload max

'''Adjustable parameters'''

If necessary, for a client, we can modify the formula, on a specifically trigger (or all) to allow more or less uploaded events or change the hard limit. For this, please contact engineering

File:Annotation 2020-08-18 072525.png

2020-08-18T05:57:18Z

Alexandra:

Adaptive Event Limitation

2020-08-18T05:56:49Z

Alexandra:

Adaptive Event Limitation

2020-08-18T05:55:56Z

Alexandra: Created page with " This mechanism, available from the 40.4 Firmware release, limits the number of events uploaded via cellular on the cloud. All the events are still being stored to the SD card..."

Main Page

2020-08-18T05:51:01Z

Alexandra: /* IDRIVE ROMANIA */

[[File:Wiki.jpg]]

==CUSTOMER GUIDES==

<table><tr>
<td valign="top">
{| class="wikitable"
!style="width: 270px;"|Idrive Useful Links
|-
|rowspan="2"|
[http://admincenter.idriveglobal.com Idrive Admin Center]

[[Idrive Downloads]]

[http://wiki.idriveglobal.com Idrive Customer Wiki - wiki.idriveglobal.com]

[http://www.idriveglobal.com Idrive Web Site]

[http://itunes.apple.com/us/app/idrive-global-center/id498507809?ls=1&mt=8 Idrive App Apple Store]

[https://www.facebook.com/idriveGlobal/ Idrive on Facebook]

[http://twitter.com/idriveX1 Idrive on twitter]

[http://www.teamviewer.com Team Viewer]

[http://get.adobe.com/reader Adobe Reader]

[http://videolan.org Video Lan FLV player]

[https://www.freedom2manage.com Pod Systems SIM Management]

[https://go.trackvia.com TRACKVIA (Questti Installation Info]

|}

{| class="wikitable"
!style="width: 270px;"|Idrive Support
|-
|rowspan="2"|

[[File:settings2.png|center|70px]]

----

[http://wiki.idriveglobal.com/index.php?title=How_To_Open_a_Support_Ticket How To Open a Support Ticket]

[http://wiki.idriveglobal.com/index.php?title=Contact_Idrive_Support Contact Idrive Support]

[http://wiki.idriveglobal.com/index.php?title=Contact_Idrive_Support About RMA (Client)]

[[Idrive Base Station HDD Full]]

[[Idrive Control Center 2.0 Internal Admin User’s Guide]]

[[RMA Processing Policy and Procedures]]

[[Media:New_RMA_Shipping_Form.zip|New RMA Shipping Form]]

|}

</td>

<td valign="top">

{| class="wikitable"
!style="width: 270px;"|Software Customer Guides

|-
|rowspan="2"|
[[File:Smart-icon.png|center|70px]]

----

'''Software'''

----

[[Idrive Control Center 3.0 User’s Guide]]

[[iris User's Manual]]

[http://wiki.idriveglobal.com/index.php?title=Idrive_Global_Center_app_for_iPhone_and_iPad Idrive Global Center app for iPhone and iPad]

----

'''Base Station / Terminal'''

----

[[Mobile Base Station Installation Guide]]

[[idrive Micro Base Station Download Point Installation Guide]]

[http://wiki.idriveglobal.com/index.php?title=X1_%E2%80%A2_Base_Station_%E2%80%A2_Hardware_and_Software idrive Client FAQ]

----

'''Installation'''

----

[http://wiki.idriveglobal.com/index.php?title=Wired_Panic_Button_Installation_Guide Wired Panic Button Kit Installation Guide]

[http://wiki.idriveglobal.com/index.php?title=IR_LED_Illuminator_Kit_Installation_Guide IR LED Illuminator Kit Installation Guide]

----

'''Client Maintenance'''

----

[[Idrive Client weekly X Camera and D4 Maintenance]]

[[Best Practices Base Station, Access Point, and Remote Access]]

|}
</td>

<td valign="top">
{| class="wikitable"
!style="width: 270px;"|Hardware Customer Guides
|-
|rowspan="2"|

[[File:settings2.png|center|70px]]

----

'''AI'''

----
[[Idrive AI (Artificial Intelligence) Installation and Operation Guide]] ('''Left and Right driver images combined''')

[[AI Power Cable Protector Installation Guide]]

[[PowerUp2 Installation and Operation and Specifications Guide]]

----

'''AI - Espanol'''

----

[[Idrive AI (Inteligencia Artificial) Guía de Instalación y Operación - Español]] ('''Imágenes izquierda y derecha combinadas''')

[[AI Power Cable Protector Installation Guide - Español]]

[[PowerUp2 Guía de Instalación, Operación y Especificaciones - Español]]

----

'''X2'''

----

[[Idrive X2V2 Installation and Operation Guide]]

[[Media:Idrive_X2V2_Installation_and_Operation_Guide_left_side_mount_v2.pdf |Idrive X2V2 Installation and Operation Guide - Left side mount for EMEA]]

[[Idrive X2 GSM or 3G Module Installation and operation guide]]

[[Idrive X2 Continuous Recording (CR) and Extended Video (settings and requests guide)]]

[[media:Idrive X2V2 Cable Lock Bracket.pdf| X2V2 Cable Lock Bracket PDF]]

[[Idrive GPS Tracker]]

[[Facial Recognition]]

----

'''X1'''

----

[http://wiki.idriveglobal.com/index.php?title=Idrive_X1_Installation_and_Operation_Guide Idrive X1 Installation and Operation Guide]

----

'''D4'''

----

[http://wiki.idriveglobal.com/index.php?title=Idrive_D4_Installation_and_Configuration_Guide idrive D4 Installation and Configuration Guide]

[http://wiki.idriveglobal.com/index.php?title=Idrive_Viewpro_User_Guide idrive Viewpro User Guide]

----

'''D4M 5/2019'''

----

[[Idrive D4M Installation and Configuration Guide]]

[[Idrive D4M H-Player; Client Video Player Software Client Manual]]

----

'''D8'''

----

[[Idrive D8 HDD Reader and Software]]

|}

</td>
</tr>
</table>

<table><tr>

==INTERNAL GUIDES==

===SOFTWARE===

<td valign="top">

{| class="wikitable"
!style="width: 270px;"|Idrive Internal Customer Guides
|-
|rowspan="2"|

[[File:Smart-icon.png|center|70px]]

----

'''Base Station / Software'''

----

[[Idrive Terminal Information and Policies]]

[[Idrive Control Center "Idrive Settings"]]

[[Idrive Support - Base Station first connection checklist]]

[[idrive "New Client" 2 hour Software Training procedure and guideline]]

[["New Client" Cellular Download; No Base Station; iris setup and training]]

----

'''X2 Information'''

----

[[Read X2 files from Storage SD Card]]

[[X2 Advanced Features]]

[[X2 Surge Ratings and voltages]]

[[X2 GSM Module Notes]]

[[Device Warranty Processes]]

[[USB Config Files]]

[[X2V2 WiFi channel properties]]

----

'''D8 Information'''

----

[[BNSF D8 device and alert management]]

[[D8 repair and reprocessing]]

----

'''Cellular Information'''

----

[[PodGroup (PodSystems) Information]]

[[Idrive X2 GSM Processes]]

|}

</td>

<td valign="top">
{| class="wikitable"
!style="width: 270px;"|Features Documentation
|-
|rowspan="2"|

[[File:Sites-icon.png|center|60px]]

----
'''Software'''
----
[[Standard Reports]]

[[Clustering/FR Assignment Interface]]

[[Global Notifications]]

[[Fleet Manager]]

----
'''Advanced Development'''
----
[[Safe Distance Warning]]

[[Drowsiness and Distraction]]

[[Coaching Reports]]

[[Monetize Reports]]

|}
{| class="wikitable"
!style="width: 270px;"|Idrive releases
|-
|rowspan="2"|

[[File:IdriveX1_small_tech_specs1.jpg|center|120px]]

----
[[Admin Center Changelog]]

[[Control Center Changelog]]

[[IRIS Changelog]]

[[X2 Firmware Releases | X2 Firmware Changelog ]]

[[NODE Changelog]]

[[API Changelog]]

[[IRA Changelog]]

[[X3 Firmware Changelog]]

[[AOSP Changelog]]
|}

</td>

<td valign="top">

{| class="wikitable"
!style="width: 270px;"|Idrive Admin Center
|-
|rowspan="2"|

[[File:wikiac.jpg|center]]

----

[[Idrive AdminCenter Specs]]

[[Outlook Tickets Plugin Specs]]

[[Idrive 2.0 Admin Center Changelog]]

|}

{| class="wikitable"
!style="width: 270px;"|Idrive Control Center
|-
|rowspan="2"|

[[File:wikicc.jpg|center]]

----

[[Idrive 2.0 Control Center Changelog | Idrive 2.0 Control Center Changelog]]

|}
{| class="wikitable"
!style="width: 270px;"|Idrive Factory Tool
|-
|rowspan="2"|

[[File:wikifc.jpg|center]]

----

[[Idrive Factory Tool 2.0 Specs]]

|}
</td>

<td valign="top">
{| class="wikitable"
!style="width: 245px;"|Wifi Related
|-
|rowspan="2"|

[[File:mikrotik.jpg|center|160px]]

----

[[RB Groove Configuration]]

[[Media:Winbox.zip|WinBox (MikroTik Router Software)]]

[[MicroTIK VPN Solution]]

[[Transfer Point Documentation]]

[[Wireless Bridge Documentation]]

[[Netwatch Script Reboots MikroTik]]

[[Vonets VAR11N WiFi Router programming guide (Access Point for Idrive Mobile Base Station)]]

|}
</td>
</tr>
</table>

<table>
<tr>

===HARDWARE===

<td valign="top">
{| class="wikitable"
!style="width: 270px;"|Stonkam D8

|-
|rowspan="2"|

[[File:Sites-icon.png|center|60px]]

[[Stonkam D8 Contact & Notes - What is it?]]

[[Stonkam D8 Initial Configuration and Setup]]

[[Stonkam D8 Configuration Checklist]]

[[Stonkam D8 Installation Guide]]

[[Idrive D8 DVR Installation Guide]]

[[Stonkam D8 End User Guide]]

|}

<td valign="top">

{| class="wikitable"
!style="width: 270px;"| EZ Storage D4
|-
|rowspan="2"|

[[File:IdriveX4_small_tech_specs.jpg|center|150px]]

----

[[D4 Initial Configuration and Setup]]

*''updated firmware and EZ config Nov 2014 adding Backing Cam trigger full screen''

[[D4 DVR_CoreBoard replacement (NAND-NOR_Flash Conversion) ]]

[[media:D4_install_monitor_to_security_box.pdf | D4 install monitor to security box]]

[[media:Train_Inverter_D4_power.pdf‎ | Locomotive inverter and relay schematic for D4 installation ignition and powering ]]

*'''D4M 5/2019 items'''

[[New D4M (4/17/19) Initial Configuration and Setup]]

|}
</td>
<td valign="top">
{| class="wikitable"
!style="width: 270px;"|Idrive Base Station
|-
|rowspan="2"|

[[File:base-station-idrive.jpg|center|160px]]

----

[[Idrive Base Station General Requirements]]

[[Base Station Configuration Guide ]]

[[Media:Base_Station_Checklist_121318.zip|Base Station Checklist (Current as of 12/13/18)]]

[[Base Station Connectivity Information ]]

[[Base Station Upgrade Hard Drives ]]

[[Idrive Base Station 2TB upgrade procedure]]

[[Micro Base Station Download Point Configuration Guide]]

|}
</td>

<td valign="top">
{| class="wikitable"
!style="width: 270px;"|Idrive X2
|-
|rowspan="2"|

[[File:IdriveX1_small_tech_specs1.jpg|center|120px]]

----
[[Driver ID Specs]]

[[ Linux | Linux Freescale 3.0.35_4.1.0]]

[[Idrive X2 Specs]]

[[Idrive X2 Notes]]

|}

</td>

<td valign="top">

{| class="wikitable"
!style="width: 270px;"|Video Splitter
|-
|rowspan="2"|

[[Video Splitter Assembly]]

|}

{| class="wikitable"
!style="width: 270px;"|Camera Boost Converter
|-
|rowspan="2"|

[[Boost Converter Assembly]]

|}

{| class="wikitable"
!style="width: 270px;"|Harsh Environment Cable Kit
|-
|rowspan="2"|

[[Harsh Environment Cable Kit]]

|}

</td>
</tr>
</table>

<table><tr>
<td valign="top">
</td>

==MANUFACTURING==

<td valign="top">
{| class="wikitable"
!style="width: 270px;"|Idrive Manufacturing
|-
|rowspan="2"|

[[File:manuficon.jpg|center|100px]]

----

'''AI'''

----

[[Manufacturing:AI Device Manufacturing and Programming Process | AI Device Manufacturing and Programming Process]]

[[Manufacturing:AI Programmer Setup Wiring| AI Programmer Setup Wiring]]

----

'''X2'''

----

[[Manufacturing:X2 Device Manufacturing and Programming Process | X2 Device Manufacturing and Programming Process]]

[[Manufacturing:X2V2 Device Manufacturing and Programming Process | X2V2 Device Manufacturing and Programming Process]]

[[Manufacturing:X2 Programming Station Documentation | X2 Programming Station Documentation]]

[[Manufacturing:Factory Tool Documentation | Factory Tool Documentation]]

[[Manufacturing:X2 Ubuntu Configuration for MicroSD programming| X2 Ubuntu Configuration for MicroSD programming]]

[[Manufacturing: SDShark use for MicroSD programming | WireShark use for MicroSD programming]]

----

'''X1'''

----

[[Manufacturing:X1 V7 Series Device Manufacturing and Programming Process | X1 V7 Series Device Manufacturing and Programming Process]]

[[X1 V7 Series Device Manufacturing and Programming Admin Documentation]]

|}
</td>
<td valign="top">
{| class="wikitable"
!style="width: 270px;"|AI RMA Documentation
|-
|rowspan="2"|

[[File:Sites-icon.png|center|60px]]

----
'''AI RMA'''
----
[[AI RMA Documentation:AI AI RMA and Programming Process | AI RMA and Programming Process]]

[[AI RMA Documentation:AI AI Assembly Process | AI Assembly Process]]

[[AI RMA Documentation:AI AI Camera Error Codes | AI Camera Error Codes]]

[[AI RMA Documentation:AI Event Types | Event Types]]

[[AI RMA Documentation:AI AI Power Loss Events | AI Power Loss Events]]

[[AI RMA Documentation:AI AI Power Connector Reflow/Repair | AI Power Connector Reflow/Repair]]

[[AI RMA Documentation:AI AI Lens Replacement and Focus| AI Lens Replacement and Focus]]

[[AI RMA Documentation:AI AI Factory Tool Configuration | AI Factory Tool Configuration]]

[[AI RMA Documentation:AI File Recovery with Android Studio | File Recovery with Android Studio]]

|}

</td>
</tr>
</table>

<table><tr>

==INTERNAL PROCESSES==

<td valign="top">
{| class="wikitable"
!style="width: 270px;"|Idrive Internal Process Guides
|-
|rowspan="2"|

[[File:Sites-icon.png|center|60px]]

----

[[Idrive Shipping Receiving Process]]

[[Harmonized Codes Information for Imports]]

[[Idrive Order Handling Process ]]

[[Idrive Customer Exception Process ]]

[[Idrive Parts Ordering Process]]

[[New Client Implementation Schedule ]]

|}

</td>

<td valign="top">
{| class="wikitable"
!style="width: 270px;"|Idrive Internal Technical Support Guides
|-
|rowspan="2"|

[[File:Support.JPG|center|60px]]

----

'''Fix SQL Error''' in Server 2016, 2014, or 2008 -
:[[Could not find the Database Engine startup handle]]

:[[Fix; Export from CC fails to see mapped Network drive from Windows 10]]

:[[Fix; APIPA address on Idrive Wireless NIC in Registry]]

|}

</td>

<td valign="top">

{| class="wikitable"
!style="width: 270px;"|Using Wiki
|-
|rowspan="2"|

[[File:mediawiki.jpg|center|86px]]

----

Consult the [//meta.wikimedia.org/wiki/Help:Contents User's Guide] for information

on using the wiki software.

Getting started
----
* [//www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]
* [//www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]

|}
</td>

</tr>
</table>

<table>
<tr>

==IDRIVE ROMANIA==

<td valign="top">
{| class="wikitable"
!style="width: 270px;"|Idrive Romania
|-
|rowspan="2"|

[[File:ro.jpg|center|60px]]

----

[[Idrive Hardware Development]]

[[Idrive Software Development]]

[[Regulament de Ordine Interioara]]

Laborator

Utile

|}

<td valign="top">
{| class="wikitable"
!style="width: 270px;"|Idrive Romania
|-
|rowspan="2"|

[[File:ro.jpg|center|60px]]
[[File:Support.JPG|top|right|60px]]

----

'''AI FEATURES and SETTINGS'''

[[Shock Event / G-Force]]

[[SDW - Safe Distance Warning]]

[[FR - Face Recognition]]

[[DaD - Distracted and Drowsy]]

[[Cellular Upload]]

[[Covered Camera]]

[[Seat Belt Event]]

[[Adaptive Event Limitation]]

|}

----

Copyright © 2020 Idrive. All rights reserved.

DaD - Distracted and Drowsy

2020-07-24T13:19:41Z

Alexandra:

Idrive™ inside camera AI is processing images directly the on-device without any cloud connectivity or additional hardware add-ons.

Idrive™ inside camera AI is running at 4 FPS and at 2 FPS if Outside Camera AI features are activated.
:- This is done by using the optimum speed/accuracy state of the art Convolution Neural Network (CNN) architectures.

Our high accuracy of 96% during the day and 91% during the night condition is obtained using a huge number of training data that idrive stored during 10 years we were present in the market.

Beside the quantity, a very important factor is diversity;
:*our algorithm training data represents diversity in vehicle types
:*luminosity conditions
:*camera positioning in the vehicle
:*road type
:*and weather condition.

'''Distracted and Drowsy (DaD) triggers an event called “Fatigue/Distracted”'''

The event is uploaded to the idrive cloud via cellular data by default.

The DaD algorithm searches for the driver in a specific position set by the "driving side" parameter
::- (IRIS->Fleet Manager-> Vehicles)
::- Left driving side is considered the default, for any other driving position please adjust this parameter accordingly.

[[File:Driving_side.png]]

'''A DaD trigger is made when the driver is distracted more than 35% of the time in the last 6 seconds'''

A distracted position is considered when the driver is looking down
:*The driver is allowed to look lateral, in the mirrors or behind when backing without considering it as a distracted behavior

'''In order to trigger a DaD event, the vehicle must have at least 5 km/h (3.1 mph)
'''

'''EXCEPTIONS'''

In the areas without GPS signal like parking lots, passages, some unique areas where we cannot estimate the car speed...
::- if there is no GPS signal more than 90% of the time during the last minute we do not take in consideration the speed again until you have a GPS signal restored
::- so will trigger a DaD event every time the driver will look down more than 25% of the last 6 seconds.

Upon client demands we can adjust the settings so during times of no GPS signal, the camera will no trigger a DaD event
::- useful for clients which spend a lot of time in the covered parking garages without GPS signal and do not want DaD triggers during those times
::::- Please address engineering when this is the case to make the change

Other parameters that can be adjusted by engineering upon client/ Idrive Support request are:
*The default 6 seconds analyze time
*The default 25% time needed to stay distracted in order to give a DaD trigger
*Minimum speed (default: 5 km/h (3.1 miles) that a driver should have to trigger a DaD event
*A confidence threshold which is evaluating when the driver is distracted or not (in case of too many or too few DaD events)

'''NOTE:''' Please inform engineering if a client has too many false DaD events and also if no DaD are triggered when it should supposed to.

'''Technical recommendation'''

'''For improved accuracy mount the camera closest to the drivers face on both horizontal and vertical axis'''

<br/><br/>

X3 Firmware Changelog

2020-06-26T06:04:38Z

Alexandra:

==Version 40.3==

'''Bug'''

*[FX-376] - GPS position packages are added on route while speed is 0
*[FX-357] - Video keyframes issue - video streams in mp4 files start with 2 P-frames (non-keyframes) followed by the Keyframe
*[FX-358] - AI camera cannot load the settings from internal memory (E002)
*[FX-369] - Camera doesn't connect to mobile network while SIM is not active

'''Story'''

*[FX-375] - Improve seat belt HOG SVM algorithm for right side drivers
*[FX-353] - Implementing AI trigger's confidence output parameters
*[FX-356] - Extend Bluetooth protocol in order to add camera IP (mandatory for communication with iPhone)
*[FX-360] - Create a mechanism to store critical parameters (ex. serial no) to AOSP properties in case of E002 error

==Version 40.1==

'''Bug'''

*[FX-331] - Fix temperature issue in log file when temperature is lower than 10 degrees
*[FX-337] - Max speed may have wrong value for cellular events
*[FX-339] - Invalid gps coordinates are not uploaded for cellular events. This behavior may create confusion in event speed chart (Iris platform)
*[FX-344] - DAD events are not triggered when Speed is interogated more than one time per second
*[FX-346] - Possible DaD issues when driver is on the right side
*[FX-347] - In some rare cases Ignition On does not reboot the camera when camera is in sleep mode

'''Story'''

*[FX-292] - Add support for camera API scalability - provides a second URL to alternate server connections
*[FX-332] - Improve MySqlWrapper class (API client for connecting to MySql database) in order to allow a number of retries (6 by default) in case of errors
*[FX-333] - Improve Face Recognition process in order to reduce the number of connections on the Face Recognition server
*[FX-335] - Adjust bit rate in continuous recording / original events to have the same values like X2
*[FX-336] - Add timestamps in previews in order to reduce file size (from 700 Kb to 500 Kb); increase the preview bitrate from 500Kb to 700Kb (the preview size will be 700 kb again)
*[FX-338] - Implement error code E004 when video acquisition is freezing from some reason. Camera will reboot after few seconds.
*[FX-340] - Improve Face Recognition algorithm in order to validate a recognition below a safety threshold if the same person has been validated in the past for several times (based on a decay score function)
*[FX-342] - Integrate preview length, preview file size and impact second and pass them to NODE server during the upload of cellular events
*[FX-343] - Adjust GPS class to trigger DAD events when there is no signal for a while
*[FX-345] - Add a cache mechanism for network type (2G, 3G, 4G), signal strength (1, 2, 3, 4) and operator (carrier) when gsm is initialized in Ignition ON. Cache is used during wifi transfer with Factory Tool

==Version 40.0==

'''Bug'''

*[FX-93] - Firmware crash after 8h 35 min --> JNI ERROR (app bug): local reference table overflow (max=512)
*[FX-103] - Fix H264 Header from Encoder (amcvidenc-omxqcomvideoencoderavc)
*[FX-107] - Memory leak when streaming enabled and big latency
*[FX-109] - Dlib library performance issues
*[FX-120] - Droping frames on outside camera when SDW is running
*[FX-129] - Fix datetime in GPS file (the same date for all gps coordinates)
*[FX-130] - DAD is not closing properly on ignition off
*[FX-140] - Video preview out of sync
*[FX-148] - Event additional pictures are not uploaded while internet connection becomes unavailable
*[FX-150] - Adjust H264 circular buffer keyframe issue
*[FX-151] - Android camera2 is dropping frames
*[FX-167] - Camera issue - H264 header fix for Android 9
*[FX-171] - Accelerometer not found - I2C Little kernel issue
*[FX-173] - Cellular issues on new Android
*[FX-174] - Wi-Fi hotspot and WPA 2 issue on Android 9
*[FX-175] - GPS issues on new Android
*[FX-177] - SD card free up space logic fail
*[FX-179] - X3-OV2685 Board - GStreamer pipeline fail
*[FX-185] - AWS library issue -> S3 doesn't work with Android 9
*[FX-186] - FR library not working on Android 9
*[FX-187] - Bluetooth BLE crash in certain condition on one camera
*[FX-188] - Not enough IR light
*[FX-190] - Skipping frames on AHC SRC pipeline
*[FX-193] - Preview upload fail deletes files
*[FX-196] - DAD thumbnail not uploading
*[FX-197] - Don't write any _exit in code
*[FX-198] - Events are either created empty, or will have space partially alocated
*[FX-199] - The fps is lowered because of AI DAD library
*[FX-200] - AOSP doesn't update 3G signal strength
*[FX-202] - Live Speed Events and Live Request Events are not triggered in certain conditions
*[FX-204] - Preview clip is out of sync
*[FX-208] - DAD doesn't trigger properly
*[FX-209] - Preview clip has low quality in certain conditions
*[FX-214] - Facial Recognition process is not closing at ignition off
*[FX-216] - Video and Audio aren't properly muxed
*[FX-217] - Streaming to IRA has incorrect colors
*[FX-218] - X3 is crashing on bluetooth connection
*[FX-219] - Covered camera code is not optimized
*[FX-220] - False-positive results on covered camera
*[FX-221] - Preview created by IRA is not uploaded correctly
*[FX-222] - LTIWebsocketManager should work like on X2 device
*[FX-225] - On continuous recording from time to time old frames reappear
*[FX-231] - Wifi is sending incorrect signal strength on wifi connect
*[FX-233] - Creating a new event deletes all files from the device
*[FX-234] - Reconnecting to wifi while transferring enters an infinite loop
*[FX-240] - OTA full update won't be downloaded
*[FX-244] - USB isn't seen by FW from time to time
*[FX-245] - Updating AOSP with USB stick may break the device
*[FX-250] - Sometime SD Card is not mounted - the mount procedure should be excuted in a loop
*[FX-253] - Some of the cameras cannot connect to cellular
*[FX-256] - Outside image has red hallow
*[FX-269] - Cont Recording Requests are not working properly
*[FX-273] - Yellow wire triggers on rising edge and needs to trigger on falling edge
*[FX-275] - Image sensor improvements - IR
*[FX-276] - There are 5 sec gaps between two continuous recordings file segments
*[FX-286] - When inside camera is disabled, the preview collect is unstable for live requests
*[FX-298] - Preview video contains wrong frames at the end
*[FX-309] - Camera may stuck when checking the internet connection
*[FX-313] - Camera may stuck in ignition off procedure
*[FX-315] - Data send config interval doesn't allow 30 sec
*[FX-316] - Fix circular buffer issue for CR
*[FX-322] - At ignition on, camera doesn't reboot, but remains in connecting to wi-fi

'''Story'''

*[FX-3] - Create the concept of X3 Display module (messages, icons) - Engineering version
*[FX-4] - Test 3G/4G modem for Android
*[FX-6] - Preliminary evaluation for X3 android
*[FX-8] - Generate proprietary event files
*[FX-9] - Add opencv support on Andriod platform
*[FX-10] - X3 proof of concept on SC60/Android - WIFI + Bluetooth evaluation
*[FX-11] - X3 proof of concept on SC60/Android - video acquisition + encoding over GStreamer
*[FX-12] - X3 proof of concept on SC60/Android - GPS data acquisition + processing
*[FX-13] - X3 proof of concept on SC60/Android - Accelerometer data acquisition + processing
*[FX-14] - X3 proof of concept on SC60/Android - images / video acquisition
*[FX-15] - X3 proof of concept on SC60/Android - Preliminary OS evaluation
*[FX-16] - X3 Install Android OS on our SC60 boards
*[FX-17] - Create android development setup and evaluate existing code migration
*[FX-18] - Migrate GStreamer video code
*[FX-19] - Study GStreamer CMake porting
*[FX-20] - Verify dual camera acquisition for new GStreamer library
*[FX-21] - Proof of concept for audio acquisition in GStreamer
*[FX-22] - Android Driver integration for OV2680
*[FX-23] - Porting the X2 IAQ library to X3
*[FX-25] - H264 issue on circular buffer extraction
*[FX-26] - Adapt FFMPEG code to new version for Android
*[FX-27] - Android changes to support OV2680
*[FX-29] - Migrate Imedia to FastCV lib
*[FX-30] - Git Lab edit firmware test
*[FX-31] - Migrate preview mechanism to Android FW
*[FX-32] - Create module to control WIFI on Android
*[FX-33] - Implement changes for second camera support
*[FX-34] - Live streaming camera for lens focusing / image quality evalutation
*[FX-35] - Test X3 GPS data acquisition using a custom board
*[FX-36] - Bluetooth test
*[FX-37] - Study AOSP security permissions
*[FX-38] - Event Trigger ( periodic, speed, continuous recording) on X3
*[FX-39] - Create accelerometer driver
*[FX-40] - Porting System lib
*[FX-41] - Implement Shock events
*[FX-42] - Migrate Img_utils
*[FX-43] - Porting Devicelib
*[FX-44] - Implement Face Recognition
*[FX-46] - Porting Utils lib
*[FX-47] - Porting Cellular Communication lib
*[FX-48] - Porting Wi-Fi Module
*[FX-49] - Develop Display Module I
*[FX-64] - Porting Idatabase library
*[FX-66] - Create a small app to test X3 display and IR controller
*[FX-68] - Adapt MP3 encoder for GStreamer pipeline
*[FX-69] - Implement basic transfer solution via USB stick
*[FX-70] - Implement GPS Trigger and change the system data
*[FX-71] - Import Neurotec Libraries for Facial Recognition feature
*[FX-73] - Adapt GStreamer pipeline to extract RAW frames
*[FX-74] - Implement Event Preview mechanism
*[FX-75] - Integrate JPEG library to IMG-utils
*[FX-76] - Integrate NV12 to Gray scale conversion method
*[FX-77] - Integrate GPIO driver in Firmware
*[FX-78] - Migrate 30.8 X2 fixes
*[FX-80] - Create the APIs for manipulating RAW frames once they are extracted from GStreamer pipeline
*[FX-81] - Possible Memory Leak in JNI
*[FX-85] - Check G-force conversion from byte to double
*[FX-87] - Porting transfer module
*[FX-90] - Porting and optimizing Covered camera on GPU
*[FX-94] - Implement type X3 (/mnt/SDcard)
*[FX-95] - Set proper bitrate to preview event
*[FX-97] - Change thumbstone mechanism (save to SD card, transfer protocol, delete all thumbstone files)
*[FX-99] - Porting existing DAD I
*[FX-102] - Update Factory Tools to accept X3 Product
*[FX-106] - Create build scripts for all Computer Vision/ML libraries
*[FX-108] - Create icons for X3 display
*[FX-110] - Update the display module for the new icons
*[FX-112] - Implement API client for MySql / DynamoDB using HTTP requests
*[FX-113] - Fix lock buffer issue in GStreamer
*[FX-114] - Integrate QSML library
*[FX-115] - Implement API client for S3 storage
*[FX-118] - Implementing SDW to X3
*[FX-121] - Implement event trigger messages on display
*[FX-124] - Implement a mechanism in order to upload camera log using cellular
*[FX-125] - Study RFCOMM Bluetooth on X3
*[FX-127] - Study GATT Bluetooth on X3
*[FX-128] - Study wi-fi hotspot on X3
*[FX-131] - Install Android 9 on SC600
*[FX-134] - Integrate GATT Bluetooth
*[FX-135] - Preliminary test for Android 9 -> camera driver for image sensor
*[FX-136] - Force Android 9 to use UTC date
*[FX-137] - Create method to turn on/off IR leds
*[FX-138] - Adjust image sensor parameters for better night vision/image quality
*[FX-139] - Adjust Android parameters for better sound quality
*[FX-141] - Implement wi-fi hotspot for X3
*[FX-143] - Preliminary test for Android 9 - I2C4, sound, H264 encoding
*[FX-144] - Integrate CNN classes in FW
*[FX-145] - Create classes for DAD based on new CNN
*[FX-146] - Create trigger for new DAD algorithm
*[FX-147] - Implement Seat Belt event
*[FX-152] - Adapt Android 9 for our custom boards
*[FX-153] - Adapt web socket communication to operate over wi-fi
*[FX-154] - Add CPU usage in camera log
*[FX-156] - Implement BLE protocol
*[FX-157] - Adjust Facial Recognition algorithm to trigger detection based on a speed threshold
*[FX-160] - Improve camera video image quality
*[FX-161] - Study batch factory programming for X3
*[FX-162] - Create technical documentation for X3 product - marketing purposes
*[FX-163] - Study Android chromatics library
*[FX-164] - Turn the display on in Lk
*[FX-165] - Test audio on Android 9
*[FX-176] - Tune OV2685 image parameters
*[FX-180] - Camera solutions for OV2685 driver- HAL incompatibility
*[FX-191] - Implement power failure condition
*[FX-194] - X3 library management
*[FX-195] - Implement Factory Application
*[FX-203] - Update Display Info
*[FX-207] - X3 must start wih 1970
*[FX-210] - Implement USB stick update in ignition on and transfer events in ignition off
*[FX-212] - Detach preview from events process
*[FX-213] - Upload preview even if SD card is not present
*[FX-215] - Add de-bounce for wired trigger
*[FX-224] - Verify preview upload at ignition off phase
*[FX-230] - Strip down G-streamer libraries
*[FX-236] - Long-time stress testing app for X3
*[FX-241] - Test USB update
*[FX-242] - Test Wifi reconnection
*[FX-246] - Manage RAM Disk at FW start (delete all existing files)
*[FX-247] - Implement display notification for update app
*[FX-248] - Implement ScanDisk procedure at ignition phase
*[FX-249] - Strip down OpenCV library
*[FX-251] - Add new error code on display if settings.db is missing
*[FX-254] - Document existing changes in GIT commits
*[FX-255] - Update SNPE to 1.31 for performance improvements
*[FX-258] - Refactoring Wi-Fi module
*[FX-259] - Improving FR detection algorithm (inserting Face Template in all events triggered in that session)
*[FX-264] - Research updating Firmware files with GIT
*[FX-265] - Implement updating Firmware files with GIT
*[FX-268] - Adjust BIAS for microphone sensitivity
*[FX-271] - Implement buzzer module for DAD
*[FX-272] - Display an error code in case GPS is missing
*[FX-280] - Install and configure AI beta cameras
*[FX-281] - Preliminary temperature tests for AI
*[FX-293] - Full temperature tests with features active SDW + DAD + FR
*[FX-294] - Format SD card code
*[FX-295] - Investigate auto update for X3 updater
*[FX-296] - Create versioning in neural networks for easy updates in the future
*[FX-297] - Implement Format SD card code in Factory tool
*[FX-299] - Testing and programming 7 AI cameras with Factory tool
*[FX-301] - Add a mechanism to trigger modem scan
*[FX-302] - Create a mechanism for updating the updater app in Firmware
*[FX-303] - Upgrade Factory Application
*[FX-305] - Factory tool installation manual
*[FX-306] - Modify default settings according to Al's suggestions (see attached)
*[FX-308] - Control auto exposure and auto gain from FW for camera calibration
*[FX-318] - Investigate SD card errors on some cameras

X3 Firmware Changelog

2020-06-24T13:06:53Z

Alexandra:

==Version 40.3==

'''Bug'''

*[FX-376] - GPS position packages are added on route while speed is 0

'''Story'''

*[FX-375] - Improve seat belt HOG SVM algorithm for right side drivers

==Version 40.1==

'''Bug'''

*[FX-331] - Fix temperature issue in log file when temperature is lower than 10 degrees
*[FX-337] - Max speed may have wrong value for cellular events
*[FX-339] - Invalid gps coordinates are not uploaded for cellular events. This behavior may create confusion in event speed chart (Iris platform)
*[FX-344] - DAD events are not triggered when Speed is interogated more than one time per second
*[FX-346] - Possible DaD issues when driver is on the right side
*[FX-347] - In some rare cases Ignition On does not reboot the camera when camera is in sleep mode

'''Story'''

*[FX-292] - Add support for camera API scalability - provides a second URL to alternate server connections
*[FX-332] - Improve MySqlWrapper class (API client for connecting to MySql database) in order to allow a number of retries (6 by default) in case of errors
*[FX-333] - Improve Face Recognition process in order to reduce the number of connections on the Face Recognition server
*[FX-335] - Adjust bit rate in continuous recording / original events to have the same values like X2
*[FX-336] - Add timestamps in previews in order to reduce file size (from 700 Kb to 500 Kb); increase the preview bitrate from 500Kb to 700Kb (the preview size will be 700 kb again)
*[FX-338] - Implement error code E004 when video acquisition is freezing from some reason. Camera will reboot after few seconds.
*[FX-340] - Improve Face Recognition algorithm in order to validate a recognition below a safety threshold if the same person has been validated in the past for several times (based on a decay score function)
*[FX-342] - Integrate preview length, preview file size and impact second and pass them to NODE server during the upload of cellular events
*[FX-343] - Adjust GPS class to trigger DAD events when there is no signal for a while
*[FX-345] - Add a cache mechanism for network type (2G, 3G, 4G), signal strength (1, 2, 3, 4) and operator (carrier) when gsm is initialized in Ignition ON. Cache is used during wifi transfer with Factory Tool

==Version 40.0==

'''Bug'''

*[FX-93] - Firmware crash after 8h 35 min --> JNI ERROR (app bug): local reference table overflow (max=512)
*[FX-103] - Fix H264 Header from Encoder (amcvidenc-omxqcomvideoencoderavc)
*[FX-107] - Memory leak when streaming enabled and big latency
*[FX-109] - Dlib library performance issues
*[FX-120] - Droping frames on outside camera when SDW is running
*[FX-129] - Fix datetime in GPS file (the same date for all gps coordinates)
*[FX-130] - DAD is not closing properly on ignition off
*[FX-140] - Video preview out of sync
*[FX-148] - Event additional pictures are not uploaded while internet connection becomes unavailable
*[FX-150] - Adjust H264 circular buffer keyframe issue
*[FX-151] - Android camera2 is dropping frames
*[FX-167] - Camera issue - H264 header fix for Android 9
*[FX-171] - Accelerometer not found - I2C Little kernel issue
*[FX-173] - Cellular issues on new Android
*[FX-174] - Wi-Fi hotspot and WPA 2 issue on Android 9
*[FX-175] - GPS issues on new Android
*[FX-177] - SD card free up space logic fail
*[FX-179] - X3-OV2685 Board - GStreamer pipeline fail
*[FX-185] - AWS library issue -> S3 doesn't work with Android 9
*[FX-186] - FR library not working on Android 9
*[FX-187] - Bluetooth BLE crash in certain condition on one camera
*[FX-188] - Not enough IR light
*[FX-190] - Skipping frames on AHC SRC pipeline
*[FX-193] - Preview upload fail deletes files
*[FX-196] - DAD thumbnail not uploading
*[FX-197] - Don't write any _exit in code
*[FX-198] - Events are either created empty, or will have space partially alocated
*[FX-199] - The fps is lowered because of AI DAD library
*[FX-200] - AOSP doesn't update 3G signal strength
*[FX-202] - Live Speed Events and Live Request Events are not triggered in certain conditions
*[FX-204] - Preview clip is out of sync
*[FX-208] - DAD doesn't trigger properly
*[FX-209] - Preview clip has low quality in certain conditions
*[FX-214] - Facial Recognition process is not closing at ignition off
*[FX-216] - Video and Audio aren't properly muxed
*[FX-217] - Streaming to IRA has incorrect colors
*[FX-218] - X3 is crashing on bluetooth connection
*[FX-219] - Covered camera code is not optimized
*[FX-220] - False-positive results on covered camera
*[FX-221] - Preview created by IRA is not uploaded correctly
*[FX-222] - LTIWebsocketManager should work like on X2 device
*[FX-225] - On continuous recording from time to time old frames reappear
*[FX-231] - Wifi is sending incorrect signal strength on wifi connect
*[FX-233] - Creating a new event deletes all files from the device
*[FX-234] - Reconnecting to wifi while transferring enters an infinite loop
*[FX-240] - OTA full update won't be downloaded
*[FX-244] - USB isn't seen by FW from time to time
*[FX-245] - Updating AOSP with USB stick may break the device
*[FX-250] - Sometime SD Card is not mounted - the mount procedure should be excuted in a loop
*[FX-253] - Some of the cameras cannot connect to cellular
*[FX-256] - Outside image has red hallow
*[FX-269] - Cont Recording Requests are not working properly
*[FX-273] - Yellow wire triggers on rising edge and needs to trigger on falling edge
*[FX-275] - Image sensor improvements - IR
*[FX-276] - There are 5 sec gaps between two continuous recordings file segments
*[FX-286] - When inside camera is disabled, the preview collect is unstable for live requests
*[FX-298] - Preview video contains wrong frames at the end
*[FX-309] - Camera may stuck when checking the internet connection
*[FX-313] - Camera may stuck in ignition off procedure
*[FX-315] - Data send config interval doesn't allow 30 sec
*[FX-316] - Fix circular buffer issue for CR
*[FX-322] - At ignition on, camera doesn't reboot, but remains in connecting to wi-fi

'''Story'''

*[FX-3] - Create the concept of X3 Display module (messages, icons) - Engineering version
*[FX-4] - Test 3G/4G modem for Android
*[FX-6] - Preliminary evaluation for X3 android
*[FX-8] - Generate proprietary event files
*[FX-9] - Add opencv support on Andriod platform
*[FX-10] - X3 proof of concept on SC60/Android - WIFI + Bluetooth evaluation
*[FX-11] - X3 proof of concept on SC60/Android - video acquisition + encoding over GStreamer
*[FX-12] - X3 proof of concept on SC60/Android - GPS data acquisition + processing
*[FX-13] - X3 proof of concept on SC60/Android - Accelerometer data acquisition + processing
*[FX-14] - X3 proof of concept on SC60/Android - images / video acquisition
*[FX-15] - X3 proof of concept on SC60/Android - Preliminary OS evaluation
*[FX-16] - X3 Install Android OS on our SC60 boards
*[FX-17] - Create android development setup and evaluate existing code migration
*[FX-18] - Migrate GStreamer video code
*[FX-19] - Study GStreamer CMake porting
*[FX-20] - Verify dual camera acquisition for new GStreamer library
*[FX-21] - Proof of concept for audio acquisition in GStreamer
*[FX-22] - Android Driver integration for OV2680
*[FX-23] - Porting the X2 IAQ library to X3
*[FX-25] - H264 issue on circular buffer extraction
*[FX-26] - Adapt FFMPEG code to new version for Android
*[FX-27] - Android changes to support OV2680
*[FX-29] - Migrate Imedia to FastCV lib
*[FX-30] - Git Lab edit firmware test
*[FX-31] - Migrate preview mechanism to Android FW
*[FX-32] - Create module to control WIFI on Android
*[FX-33] - Implement changes for second camera support
*[FX-34] - Live streaming camera for lens focusing / image quality evalutation
*[FX-35] - Test X3 GPS data acquisition using a custom board
*[FX-36] - Bluetooth test
*[FX-37] - Study AOSP security permissions
*[FX-38] - Event Trigger ( periodic, speed, continuous recording) on X3
*[FX-39] - Create accelerometer driver
*[FX-40] - Porting System lib
*[FX-41] - Implement Shock events
*[FX-42] - Migrate Img_utils
*[FX-43] - Porting Devicelib
*[FX-44] - Implement Face Recognition
*[FX-46] - Porting Utils lib
*[FX-47] - Porting Cellular Communication lib
*[FX-48] - Porting Wi-Fi Module
*[FX-49] - Develop Display Module I
*[FX-64] - Porting Idatabase library
*[FX-66] - Create a small app to test X3 display and IR controller
*[FX-68] - Adapt MP3 encoder for GStreamer pipeline
*[FX-69] - Implement basic transfer solution via USB stick
*[FX-70] - Implement GPS Trigger and change the system data
*[FX-71] - Import Neurotec Libraries for Facial Recognition feature
*[FX-73] - Adapt GStreamer pipeline to extract RAW frames
*[FX-74] - Implement Event Preview mechanism
*[FX-75] - Integrate JPEG library to IMG-utils
*[FX-76] - Integrate NV12 to Gray scale conversion method
*[FX-77] - Integrate GPIO driver in Firmware
*[FX-78] - Migrate 30.8 X2 fixes
*[FX-80] - Create the APIs for manipulating RAW frames once they are extracted from GStreamer pipeline
*[FX-81] - Possible Memory Leak in JNI
*[FX-85] - Check G-force conversion from byte to double
*[FX-87] - Porting transfer module
*[FX-90] - Porting and optimizing Covered camera on GPU
*[FX-94] - Implement type X3 (/mnt/SDcard)
*[FX-95] - Set proper bitrate to preview event
*[FX-97] - Change thumbstone mechanism (save to SD card, transfer protocol, delete all thumbstone files)
*[FX-99] - Porting existing DAD I
*[FX-102] - Update Factory Tools to accept X3 Product
*[FX-106] - Create build scripts for all Computer Vision/ML libraries
*[FX-108] - Create icons for X3 display
*[FX-110] - Update the display module for the new icons
*[FX-112] - Implement API client for MySql / DynamoDB using HTTP requests
*[FX-113] - Fix lock buffer issue in GStreamer
*[FX-114] - Integrate QSML library
*[FX-115] - Implement API client for S3 storage
*[FX-118] - Implementing SDW to X3
*[FX-121] - Implement event trigger messages on display
*[FX-124] - Implement a mechanism in order to upload camera log using cellular
*[FX-125] - Study RFCOMM Bluetooth on X3
*[FX-127] - Study GATT Bluetooth on X3
*[FX-128] - Study wi-fi hotspot on X3
*[FX-131] - Install Android 9 on SC600
*[FX-134] - Integrate GATT Bluetooth
*[FX-135] - Preliminary test for Android 9 -> camera driver for image sensor
*[FX-136] - Force Android 9 to use UTC date
*[FX-137] - Create method to turn on/off IR leds
*[FX-138] - Adjust image sensor parameters for better night vision/image quality
*[FX-139] - Adjust Android parameters for better sound quality
*[FX-141] - Implement wi-fi hotspot for X3
*[FX-143] - Preliminary test for Android 9 - I2C4, sound, H264 encoding
*[FX-144] - Integrate CNN classes in FW
*[FX-145] - Create classes for DAD based on new CNN
*[FX-146] - Create trigger for new DAD algorithm
*[FX-147] - Implement Seat Belt event
*[FX-152] - Adapt Android 9 for our custom boards
*[FX-153] - Adapt web socket communication to operate over wi-fi
*[FX-154] - Add CPU usage in camera log
*[FX-156] - Implement BLE protocol
*[FX-157] - Adjust Facial Recognition algorithm to trigger detection based on a speed threshold
*[FX-160] - Improve camera video image quality
*[FX-161] - Study batch factory programming for X3
*[FX-162] - Create technical documentation for X3 product - marketing purposes
*[FX-163] - Study Android chromatics library
*[FX-164] - Turn the display on in Lk
*[FX-165] - Test audio on Android 9
*[FX-176] - Tune OV2685 image parameters
*[FX-180] - Camera solutions for OV2685 driver- HAL incompatibility
*[FX-191] - Implement power failure condition
*[FX-194] - X3 library management
*[FX-195] - Implement Factory Application
*[FX-203] - Update Display Info
*[FX-207] - X3 must start wih 1970
*[FX-210] - Implement USB stick update in ignition on and transfer events in ignition off
*[FX-212] - Detach preview from events process
*[FX-213] - Upload preview even if SD card is not present
*[FX-215] - Add de-bounce for wired trigger
*[FX-224] - Verify preview upload at ignition off phase
*[FX-230] - Strip down G-streamer libraries
*[FX-236] - Long-time stress testing app for X3
*[FX-241] - Test USB update
*[FX-242] - Test Wifi reconnection
*[FX-246] - Manage RAM Disk at FW start (delete all existing files)
*[FX-247] - Implement display notification for update app
*[FX-248] - Implement ScanDisk procedure at ignition phase
*[FX-249] - Strip down OpenCV library
*[FX-251] - Add new error code on display if settings.db is missing
*[FX-254] - Document existing changes in GIT commits
*[FX-255] - Update SNPE to 1.31 for performance improvements
*[FX-258] - Refactoring Wi-Fi module
*[FX-259] - Improving FR detection algorithm (inserting Face Template in all events triggered in that session)
*[FX-264] - Research updating Firmware files with GIT
*[FX-265] - Implement updating Firmware files with GIT
*[FX-268] - Adjust BIAS for microphone sensitivity
*[FX-271] - Implement buzzer module for DAD
*[FX-272] - Display an error code in case GPS is missing
*[FX-280] - Install and configure AI beta cameras
*[FX-281] - Preliminary temperature tests for AI
*[FX-293] - Full temperature tests with features active SDW + DAD + FR
*[FX-294] - Format SD card code
*[FX-295] - Investigate auto update for X3 updater
*[FX-296] - Create versioning in neural networks for easy updates in the future
*[FX-297] - Implement Format SD card code in Factory tool
*[FX-299] - Testing and programming 7 AI cameras with Factory tool
*[FX-301] - Add a mechanism to trigger modem scan
*[FX-302] - Create a mechanism for updating the updater app in Firmware
*[FX-303] - Upgrade Factory Application
*[FX-305] - Factory tool installation manual
*[FX-306] - Modify default settings according to Al's suggestions (see attached)
*[FX-308] - Control auto exposure and auto gain from FW for camera calibration
*[FX-318] - Investigate SD card errors on some cameras

Manufacturing:AI Device Manufacturing and Programming Process

2020-05-18T07:36:12Z

Alexandra:

=AI Device Manufacturing and Programming=

==INITIAL ASSEMBLY AI BOARD==

[[File:driver-road.png]]

1. Attach the S/N label on the dedicated area of the “Road side” of the Main Board.

[[File:label.png]]

2. Insert (by pressing) the Micro SIM into the SIM / SD socket on the Road Side of the Main Board.

[[File:sim.png]]

3. Insert (by pressing) the 32GB Micro SD card into the SIM / SD socket on the Road Side of the Main Board.

[[File:card.png]]

4. Mount (by the adhesive tape present on the back) the two Gaskets on the destinated area of both “Road” and “Driver “sides of the board.

[[File:gasket.png]]

[[File:gasket1.png]]

5. Mount the two Lens Holders (by screwing) on both sides of the board.

[[File:lensholder.png]]

Screwing is made from the behind of each lens holder, through the dedicated holes with a torque of 0,2 Nm.

[[File:bolt.png]]

6. Insert the proper lens (by screwing) in the correct side of the Main board, into the Lens Holders.

[[File:lens.png]]

After programming and focus, lenses are glued.

7. Advance the Top Level AI Main Board PCB assembly to the AI Programming Station

==AUTOMATIC INSTALL AND CONFIGURATION (VIA FACTORY TOOL)==

Notes: The Automatic install performs the following:

•installs the AOSP and the Firmware, gets device configuration from the Idrive AdminCenter (IP address, serial number etc.);

•tests triggering on the yellow, blue and green wires;

•provides lens focus mode so both lenses can be focused and glued.

!For this step, DO NOT use Developer Mode!

1. Click on the Factory - New Devices - Auto button

[[File:aa.png]]

2. Scan using the bar code scanner the Bar Code label present on the Main board and press Enter.

[[File:b.png]]

If no bar code scanner is available, manually type the serial number from the bar code label into the serial number input field.

3. Click on the Auto Install button and the Automatic Install window will open.

[[File:c.png]]

If the SN have already been introduced (device has already passed through one or more programming steps), a warning message will be displayed asking if you want to Continue or not. Continue if you want to reprogram the device, cancel if you introduced once more the SN by mistake.

4. In the Automatic Install window, Click on Start Installation button.

[[File:d.png]]

Installation and Configuration process steps:

1. Install AOSP

2. Install Firmware

3. Device Configuration

AI camera successfully installed and configured when all three buttons are GREEN.

[[File:c1.png]]

If all the steps are successfully completed, the program will enter into Lens Focus mode.

If any of these steps fails, the program will stop and give an error. Common errors are:

-Missing or corrupt storage SD card

-Serial cable not connected or incorrect polarity

-USB NIC or Internet connection missing

-I/O ports tester board missing

-Any assembly or incorrect component error

! In case any of the 3 steps fail (button will be red instead of green), there are two options (corrective actions):

1.Repeat the entire process by clicking on Start installation button in the Automatic Install window and the AOSP installation, Firmware installation and Device Configuration will be redone automatically.

2.Repeat manually only that specific step that failed:

a) Click on Factory - New Devices – Manual;

[[File:c2.png]]

b) Scan barcode

c) Depending on the step that failed, click either on Install Aosp button -> Start installation, either on Install Firmware buttonStart installation, either on Device Config – AC Sync – Lens Focus button -> Start configuration.

[[File:e.png]]

In case that the first step failed (Install Aosp), recommended would be to repeat automatically the process by clicking on Start installation button in the Automatic Install window.

===Lens Focus===

1. Select "Inside Camera" Tab and Focus the “Driver side” Lens (“Driver side” is the side containing the Processor).

[[File:f.png]]

The focal length for the inside camera should be ~1.5 meters

2. Select "Outside camera" tab and Focus the “Road side” Lens (“Road side” is the side containing the Power Connector).

[[File:g.png]]

Focus using the provided Idrive Focus Chart. Distance to chart can be 3,6,9 feet but the farther the better.

Optional: Use zoom mode (Show zoom button) to ensure accurate focus.

In Both Cameras tab, you can visualize both “Driver side” and “Road side” cameras on the screen (the screen will be splitted in two).

3. If images are focused and clear (the outside test text is accurate and readable), click on the "Lens Focus OK" button and the focus mode will close.

[[File:h.png]]

If one of the images or both images are not clear, or if the Streaming is not loading (“Loading…Please wait!” message is displayed), click on the "Lens Focus Not OK" and the factory tool will exit focus mode, so corrective actions can be taken.

! Corrective actions: Repeat manually the 3rd step: Factory - New Devices – Manual -> Scan barcode -> Device Config – AC Sync – Lens Focus -> Start Configuration

4. Once focused, fix each lens with a drop of super glue. Test the lenses after several minutes to ensure they have taken the glue and cannot be moved (it means the glue is dried).

5. Remove the device from the test fixture (programmer fixture).

6. Advance the device to Final Assembly step.

==FINAL ASSEMBLY AI CAMERA==

1. Remove (by screwing) the screw nut from power supply connector on the Main board and set it aside.

[[File:1.jpg|290px|]]

2. Connect speaker wire (red and black wire) into the J250 socket on the “Road” side of the Main Board.

[[File:2.png]]

3. Assembly Main board with the “Driver” side up into the inferior case by gently pressing on Main board and by pulling the edges of the case.

[[File:3.png]]

4. Tightens the screw nut removed in step 1 on the power supply connector (torque 0.2 Nm).

[[File:4.jpg]]

5. Connect the wires into the sockets on “Driver” side of the Main board:

[[File:5.png]]

a.Connect 4G antenna – insert wire 1 in J6 socket on Main board;

[[File:5.1.png]]

b.Connect GPS antenna – insert wire 2 in J7 socket on Main board;

[[File:5.2.png]]

c.Connect Wi-Fi antenna – insert wire 3 in J5 socket on Main Board.

[[File:5.3.png]]

6. Mount the Display module into the dedicated socket.

[[File:6.png]]

Remove the plastic protection foil from the display.

7. Mount by screwing the superior case (use torque 0.3 Nm).

[[File:7.png]]

8. Advance assembled AI cam to Final test process.

==FINAL TEST (VIA FACTORY TOOL)==

1. Open Factory Tool -> Factory - New devices – Auto -> Event Test – Transfer and Play (event test window will open – see at point 7)

[[File:poza1.png]]

[[File:poza2.png]]

2. Connect 5 assembled AI cameras to Switch boxes power supplies (Power and Ignition are OFF).

[[File:poza3.jpg|500px|]]

3. Switch Power and Ignition ON -> AI cameras will start to boot (Idrive logo will be displayed).

[[File:poza4.jpg|400px|]]

[[File:poza5.png]]

In this phase, AI cameras connect to GPS and to network (2G/3G/4G). The operator must pay attention to the cameras screens to assure that connections are available, and that all the icons are displayed and there is no error code – See picture below.

[[File:poza6.png]]

4. Trigger a SHOCK event by pulling (shaking) each AI camera backward and forward (once or twice)-> Message SHOCK will be displayed on the screen, moment when the camera starts recording the event.

[[File:poza7.jpg|400px|]]

5. After triggering and recording the SHOCK event (display gets back to normal), Switch Ignition OFF for AI cameras.

In this phase, AI cameras connect to Wi-Fi and start transferring. A text with IGNITION OFF followed by CLOSING TRIGGERS, by CONNECTING WIFI and by TRANSFERING along with specific icons, will be displayed on the screen.

[[File:poza8.png]]

6. In the event test window, click on Play for each of the AI camera in the Play events area -> the record of the SHOCK event will be played.

[[File:poza9.png]]

Verify the focus of both lenses (image clarity). If the image is clear, lens focus was done properly. If not, the camera must be put aside. Check also if GPS route was recorded.

7. If lens focus OK and GPS route recorded -> Click on Label Printed – Print and print 2 labels. Close the window.

[[File:poza10.png]]

[[File:poza11.png|900px|]]

There will be displayed 2 messages: one for label print confirmation and one for beep confirmation.

If label was not printed, click NO and try again to reprint the label. Camera starts to beep only if label printed was confirmed. Once label print and beep confirmed, serial number text row turnes green. If there is no beep, it means that the camera has a problem with the speaker.

8. Camera will shut down automatically (SHUTTING DOWN message will be displayed) -> Switch Power OFF and Unplug the camera.

[[File:poza12.jpg]]

9. Apply one label on the bottom of the AI camera and one on the right side of the Final box.

[[File:poza13.jpg|500px|]]

[[File:poza14.jpg|500px|]]

10. Put the AI camera into the Final box.

[[File:poza15.jpg|600px|]]

ISSUES:

*AI camera doesn’t boot (display is off): verify power circular connector if it’s properly soldered to the board.

If yes, AI camera has a problem with the display -> display needs to be replaced

If it’s not, manually redo the soldering of the connector.

*AI camera appear with red text in the event test window, click on View in the View Transfer Log and see what error occurred.

[[File:poza16.png]]

First, redo the final test (without another shock trigger). If camera didn’t pass second time either, try solutions below:

*Network error

verify if the 4G antenna connector is OK and properly inserted (visual inspection).

verify if the cable is properly soldered to the antenna.

If both above OK -> replace SIM card.

If one or both above are NOK, replace connector/replace cable/manually redo the soldering.

*GPS error

verify if the GPS antenna connector is OK and properly inserted (visual inspection)

verify if the cable is properly soldered to the antenna.

*Infinite loop = HW problem which requires a close HW verification.

*Lens focus NOK -> Disassemble the AI camera and replace entire gasket + lens holders + lens assembly.

*AI camera doesn’t beep = speaker problems -> verify if speaker connector is OK and if it’s properly inserted (visual inspection).

==Radu Notes==

The AI programmer is mandatory only one time when the board comes from China with the default chinese AOSP. Once the AOSP is overwritten with our AOSP, the programmer becomes optional.

You need a micro usb cable in order to connect camera to a computer usb port, a power source for AI camera and a computer with Windows 10 (preferable).

<br>

==Factory Tool Installation==

===Install Factory Tool===

Download and install the latest Factory Tool from Admin Center

<br>

===Firmware===

Firmware folder is auto-populated by the Factory Tool installer and should have the following structure:

- firmware.apk represents the current firmware version (40.0.55)

- updater.apk is a background application taking care about firmware and aosp upgrades / firmware crashes / background staffs. The current version is 1.0

- idrive_root is the place where we keep different files (neural networks, settings, etc)

- firmware.apk should be replaced every time when a new stable firmware is released. For example, if you have a new update.apk file, you can rename this file and copy it over firmware.apk. You have also to copy the same file over idrive_root/recovery.apk file

- The same mechanism should be used if we will upgrade updater.apk. That apk should also be copied over idrive_root/recovery_updater_app.apk.

- Any file from idrive_root folder is replaceable. In the future we can add / remove / replace any file from idrive_root

<br>

===Install the Android OS===

Download and install the latest AOSP from Admin Center

Unzip the ASOP archive

Copy the files to C:\Program Files (x86)\Idrive\Factory Tool 2.0\FactoryToolsAI\Aosp

Every time when a new AOSP is released, the files from Aosp folder should be replaced with the new files.

<br>

==FT Configuration==

Select Idrive Development > Settings (password > idrive2#dev)

<br>

====Disable Passwords ( if applicable)====

Click on Passwords tab and disable

<br>

====Config and Install====

Uncheck "Programmer enabled for AI devices"

[[File:ft_conf_install1.png|500px|]]

The Factory Tool is documented, but I don't have the documentation now 🙂 (Alexandra will send you all documents tomorrow morning)

However the process is very similar with X2. There are AI settings in Idrive Development->Settings->Config and Install (see below)

(DO NOT CHANGE the "sleep seconds" fields for AI devices only).

<br>

====Factory Tool Print Settings (Santa Barbara)====

[[File:GK420t_ft_print1.png|350px|]] [[File:GK420t_ft_print2.png|350px|]]

[[File:GK420t_ft_print3.png|500px|]]

<br>

<br>

==Idrive AI Labels Windows Configuration==

===Add the Printer===

Settings > printers

Add printer>

\\idr-x2-prog-1\Zdesigner GK420t

Click on printer and Manage > Printing preferences
Options> Darkness 25, Width 1.5" Height .5"

[[File:gk420t_settings1.png|500px|]]

<br>

=== GK420T Printer Configuration (Santa Barbara) ===

Install Zebra Setup Utilities (Not needed for Factory Tool)

[[File:zebra_pref1.jpg|300px|]] [[File:zebra_pref2.jpg|300px|]]

<br>

===Label supplies for GK420T printer in RMA area===

https://www.zpsstore.com/ShoppingCart.asp

https://www.barcodesinc.com

https://www.bradyid.com/en-us/family/cps-3053222 (In use in RMA Area)

Zebra Part #: 10011693

Label Size (WxH): 1.5" x 0.50"

Labels Per Roll: 9,420

Rolls Per Case: 4

Core Size: 3"

Outside Diameter: 8"Zebra Z-Ultimate 10011693

* NO perforation between label

Thermal Ribbon:

Zebra 5095 Performance Ribbon

https://www.barcodesinc.com/search.htm?search=05095GS06407&v=1

<br>

Manufacturing:AI Device Manufacturing and Programming Process

2020-05-18T07:27:36Z

Alexandra:

=AI Device Manufacturing and Programming=

==INITIAL ASSEMBLY AI BOARD==

[[File:driver-road.png]]

*Attach the S/N label on the dedicated area of the “Road side” of the Main Board.

[[File:label.png]]

*Insert (by pressing) the Micro SIM into the SIM / SD socket on the Road Side of the Main Board.

[[File:sim.png]]

*Insert (by pressing) the 32GB Micro SD card into the SIM / SD socket on the Road Side of the Main Board.

[[File:card.png]]

*Mount (by the adhesive tape present on the back) the two Gaskets on the destinated area of both “Road” and “Driver “sides of the board.

[[File:gasket.png]]

[[File:gasket1.png]]

*Mount the two Lens Holders (by screwing) on both sides of the board.

[[File:lensholder.png]]

Screwing is made from the behind of each lens holder, through the dedicated holes with a torque of 0,2 Nm.

[[File:bolt.png]]

*Insert the proper lens (by screwing) in the correct side of the Main board, into the Lens Holders.

[[File:lens.png]]

After programming and focus, lenses are glued.

*Advance the Top Level AI Main Board PCB assembly to the AI Programming Station

==AUTOMATIC INSTALL AND CONFIGURATION (VIA FACTORY TOOL)==

Notes: The Automatic install performs the following:

•installs the AOSP and the Firmware, gets device configuration from the Idrive AdminCenter (IP address, serial number etc.);

•tests triggering on the yellow, blue and green wires;

•provides lens focus mode so both lenses can be focused and glued.

!For this step, DO NOT use Developer Mode!

1. Click on the Factory - New Devices - Auto button

[[File:aa.png]]

2. Scan using the bar code scanner the Bar Code label present on the Main board and press Enter.

[[File:b.png]]

If no bar code scanner is available, manually type the serial number from the bar code label into the serial number input field.

3. Click on the Auto Install button and the Automatic Install window will open.

[[File:c.png]]

If the SN have already been introduced (device has already passed through one or more programming steps), a warning message will be displayed asking if you want to Continue or not. Continue if you want to reprogram the device, cancel if you introduced once more the SN by mistake.

4. In the Automatic Install window, Click on Start Installation button.

[[File:d.png]]

Installation and Configuration process steps:

1. Install AOSP

2. Install Firmware

3. Device Configuration

AI camera successfully installed and configured when all three buttons are GREEN.

[[File:c1.png]]

If all the steps are successfully completed, the program will enter into Lens Focus mode.

If any of these steps fails, the program will stop and give an error. Common errors are:

-Missing or corrupt storage SD card

-Serial cable not connected or incorrect polarity

-USB NIC or Internet connection missing

-I/O ports tester board missing

-Any assembly or incorrect component error

! In case any of the 3 steps fail (button will be red instead of green), there are two options (corrective actions):

1.Repeat the entire process by clicking on Start installation button in the Automatic Install window and the AOSP installation, Firmware installation and Device Configuration will be redone automatically.

2.Repeat manually only that specific step that failed:

a) Click on Factory - New Devices – Manual;

[[File:c2.png]]

b) Scan barcode

c) Depending on the step that failed, click either on Install Aosp button -> Start installation, either on Install Firmware buttonStart installation, either on Device Config – AC Sync – Lens Focus button -> Start configuration.

[[File:e.png]]

In case that the first step failed (Install Aosp), recommended would be to repeat automatically the process by clicking on Start installation button in the Automatic Install window.

===Lens Focus===

1. Select "Inside Camera" Tab and Focus the “Driver side” Lens (“Driver side” is the side containing the Processor).

[[File:f.png]]

The focal length for the inside camera should be ~1.5 meters

2. Select "Outside camera" tab and Focus the “Road side” Lens (“Road side” is the side containing the Power Connector).

[[File:g.png]]

Focus using the provided Idrive Focus Chart. Distance to chart can be 3,6,9 feet but the farther the better.

Optional: Use zoom mode (Show zoom button) to ensure accurate focus.

In Both Cameras tab, you can visualize both “Driver side” and “Road side” cameras on the screen (the screen will be splitted in two).

3. If images are focused and clear (the outside test text is accurate and readable), click on the "Lens Focus OK" button and the focus mode will close.

[[File:h.png]]

If one of the images or both images are not clear, or if the Streaming is not loading (“Loading…Please wait!” message is displayed), click on the "Lens Focus Not OK" and the factory tool will exit focus mode, so corrective actions can be taken.

! Corrective actions: Repeat manually the 3rd step: Factory - New Devices – Manual -> Scan barcode -> Device Config – AC Sync – Lens Focus -> Start Configuration

4. Once focused, fix each lens with a drop of super glue. Test the lenses after several minutes to ensure they have taken the glue and cannot be moved (it means the glue is dried).

5. Remove the device from the test fixture (programmer fixture).

6. Advance the device to Final Assembly step.

==FINAL ASSEMBLY AI CAMERA==

*Remove (by screwing) the screw nut from power supply connector on the Main board and set it aside.

[[File:1.jpg|290px|]]

*Connect speaker wire (red and black wire) into the J250 socket on the “Road” side of the Main Board.

[[File:2.png]]

*Assembly Main board with the “Driver” side up into the inferior case by gently pressing on Main board and by pulling the edges of the case.

[[File:3.png]]

*Tightens the screw nut removed in step 1 on the power supply connector (torque 0.2 Nm).

[[File:4.jpg]]

*Connect the wires into the sockets on “Driver” side of the Main board:

[[File:5.png]]

a.Connect 4G antenna – insert wire 1 in J6 socket on Main board;

[[File:5.1.png]]

b.Connect GPS antenna – insert wire 2 in J7 socket on Main board;

[[File:5.2.png]]

c.Connect Wi-Fi antenna – insert wire 3 in J5 socket on Main Board.

[[File:5.3.png]]

*Mount the Display module into the dedicated socket.

[[File:6.png]]

Remove the plastic protection foil from the display.

*Mount by screwing the superior case (use torque 0.3 Nm).

[[File:7.png]]

*Advance assembled AI cam to Final test process.

==FINAL TEST (VIA FACTORY TOOL)==

*Open Factory Tool -> Factory - New devices – Auto -> Event Test – Transfer and Play (event test window will open – see at point 7)

[[File:poza1.png]]

[[File:poza2.png]]

*Connect 5 assembled AI cameras to Switch boxes power supplies (Power and Ignition are OFF).

[[File:poza3.jpg|500px|]]

*Switch Power and Ignition ON -> AI cameras will start to boot (Idrive logo will be displayed).

[[File:poza4.jpg|400px|]]

[[File:poza5.png]]

In this phase, AI cameras connect to GPS and to network (2G/3G/4G). The operator must pay attention to the cameras screens to assure that connections are available, and that all the icons are displayed and there is no error code – See picture below.

[[File:poza6.png]]

*Trigger a SHOCK event by pulling (shaking) each AI camera backward and forward (once or twice)-> Message SHOCK will be displayed on the screen, moment when the camera starts recording the event.

[[File:poza7.jpg|400px|]]

*After triggering and recording the SHOCK event (display gets back to normal), Switch Ignition OFF for AI cameras.

In this phase, AI cameras connect to Wi-Fi and start transferring. A text with IGNITION OFF followed by CLOSING TRIGGERS, by CONNECTING WIFI and by TRANSFERING along with specific icons, will be displayed on the screen.

[[File:poza8.png]]

*In the event test window, click on Play for each of the AI camera in the Play events area -> the record of the SHOCK event will be played.

[[File:poza9.png]]

Verify the focus of both lenses (image clarity). If the image is clear, lens focus was done properly. If not, the camera must be put aside. Check also if GPS route was recorded.

*If lens focus OK and GPS route recorded -> Click on Label Printed – Print and print 2 labels. Close the window.

[[File:poza10.png]]

[[File:poza11.png|900px|]]

There will be displayed 2 messages: one for label print confirmation and one for beep confirmation.

If label was not printed, click NO and try again to reprint the label. Camera starts to beep only if label printed was confirmed. Once label print and beep confirmed, serial number text row turnes green. If there is no beep, it means that the camera has a problem with the speaker.

*Camera will shut down automatically (SHUTTING DOWN message will be displayed) -> Switch Power OFF and Unplug the camera.

[[File:poza12.jpg]]

*Apply one label on the bottom of the AI camera and one on the right side of the Final box.

[[File:poza13.jpg|500px|]]

[[File:poza14.jpg|500px|]]

*Put the AI camera into the Final box.

[[File:poza15.jpg|600px|]]

ISSUES:

*AI camera doesn’t boot (display is off): verify power circular connector if it’s properly soldered to the board.

If yes, AI camera has a problem with the display -> display needs to be replaced

If it’s not, manually redo the soldering of the connector.

*AI camera appear with red text in the event test window, click on View in the View Transfer Log and see what error occurred.

[[File:poza16.png]]

First, redo the final test (without another shock trigger). If camera didn’t pass second time either, try solutions below:

*Network error

verify if the 4G antenna connector is OK and properly inserted (visual inspection).

verify if the cable is properly soldered to the antenna.

If both above OK -> replace SIM card.

If one or both above are NOK, replace connector/replace cable/manually redo the soldering.

*GPS error

verify if the GPS antenna connector is OK and properly inserted (visual inspection)

verify if the cable is properly soldered to the antenna.

*Infinite loop = HW problem which requires a close HW verification.

*Lens focus NOK -> Disassemble the AI camera and replace entire gasket + lens holders + lens assembly.

*AI camera doesn’t beep = speaker problems -> verify if speaker connector is OK and if it’s properly inserted (visual inspection).

==Radu Notes==

The AI programmer is mandatory only one time when the board comes from China with the default chinese AOSP. Once the AOSP is overwritten with our AOSP, the programmer becomes optional.

You need a micro usb cable in order to connect camera to a computer usb port, a power source for AI camera and a computer with Windows 10 (preferable).

<br>

==Factory Tool Installation==

===Install Factory Tool===

Download and install the latest Factory Tool from Admin Center

<br>

===Firmware===

Firmware folder is auto-populated by the Factory Tool installer and should have the following structure:

- firmware.apk represents the current firmware version (40.0.55)

- updater.apk is a background application taking care about firmware and aosp upgrades / firmware crashes / background staffs. The current version is 1.0

- idrive_root is the place where we keep different files (neural networks, settings, etc)

- firmware.apk should be replaced every time when a new stable firmware is released. For example, if you have a new update.apk file, you can rename this file and copy it over firmware.apk. You have also to copy the same file over idrive_root/recovery.apk file

- The same mechanism should be used if we will upgrade updater.apk. That apk should also be copied over idrive_root/recovery_updater_app.apk.

- Any file from idrive_root folder is replaceable. In the future we can add / remove / replace any file from idrive_root

<br>

===Install the Android OS===

Download and install the latest AOSP from Admin Center

Unzip the ASOP archive

Copy the files to C:\Program Files (x86)\Idrive\Factory Tool 2.0\FactoryToolsAI\Aosp

Every time when a new AOSP is released, the files from Aosp folder should be replaced with the new files.

<br>

==FT Configuration==

Select Idrive Development > Settings (password > idrive2#dev)

<br>

====Disable Passwords ( if applicable)====

Click on Passwords tab and disable

<br>

====Config and Install====

Uncheck "Programmer enabled for AI devices"

[[File:ft_conf_install1.png|500px|]]

The Factory Tool is documented, but I don't have the documentation now 🙂 (Alexandra will send you all documents tomorrow morning)

However the process is very similar with X2. There are AI settings in Idrive Development->Settings->Config and Install (see below)

(DO NOT CHANGE the "sleep seconds" fields for AI devices only).

<br>

====Factory Tool Print Settings (Santa Barbara)====

[[File:GK420t_ft_print1.png|350px|]] [[File:GK420t_ft_print2.png|350px|]]

[[File:GK420t_ft_print3.png|500px|]]

<br>

<br>

==Idrive AI Labels Windows Configuration==

===Add the Printer===

Settings > printers

Add printer>

\\idr-x2-prog-1\Zdesigner GK420t

Click on printer and Manage > Printing preferences
Options> Darkness 25, Width 1.5" Height .5"

[[File:gk420t_settings1.png|500px|]]

<br>

=== GK420T Printer Configuration (Santa Barbara) ===

Install Zebra Setup Utilities (Not needed for Factory Tool)

[[File:zebra_pref1.jpg|300px|]] [[File:zebra_pref2.jpg|300px|]]

<br>

===Label supplies for GK420T printer in RMA area===

https://www.zpsstore.com/ShoppingCart.asp

https://www.barcodesinc.com

https://www.bradyid.com/en-us/family/cps-3053222 (In use in RMA Area)

Zebra Part #: 10011693

Label Size (WxH): 1.5" x 0.50"

Labels Per Roll: 9,420

Rolls Per Case: 4

Core Size: 3"

Outside Diameter: 8"Zebra Z-Ultimate 10011693

* NO perforation between label

Thermal Ribbon:

Zebra 5095 Performance Ribbon

https://www.barcodesinc.com/search.htm?search=05095GS06407&v=1

<br>

X2 Firmware Releases

2020-04-09T12:07:59Z

Alexandra:

==Version 32.0==

'''Bug'''

*[FW-529] - Invalid gps coordinates are not uploaded for cellular events. This behavior may create confusion in event speed chart (Iris platform)

'''Story'''

*[FW-528] - Add support for camera API scalability - provides a second URL to alternate server connections
*[FW-530] - Improve Face Recognition process in order to reduce the number of connections on the Face Recognition server
*[FW-531] - Improve Face Recognition algorithm in order to validate a recognition below a safety threshold if the same person has been validated in the past for several times (based on a decay score function)
*[FW-532] - Integrate preview length, preview file size and impact second and pass them to NODE server during the upload of cellular events

==Version 31.9==

'''Bug'''

*[FW-526] - Data send config interval doesn't allow 30 sec
*[FW-527] - Camera may stuck in ignition off procedure

'''Story'''

*[FW-524] - Format SD card code

==Version 31.8==

'''Bug'''

*[FW-521] - There are 5 sec gaps between two continuous recordings file segments

'''Story'''

*[FW-520] - Improve DAD algorithm
*[FW-522] - Set Covered Camera feature disabled as default

==Version 31.6 merged with 31.7==

'''Bug'''

*[FW-515] - Camera fail to acquire GPS signal
*[FW-516] - OTA update procedure may block the camera

'''Story'''

*[FW-517] - Push 31.7 FW version to all devices with HF versions

==Version 31.4 merged with 31.5==

'''Bug'''

*[FW-514] - App crash from time to time on V 31.3

==Version 31.3==

'''Bug'''

*[FW-503] - Continuous recording video broken (possible key frames issue)
*[FW-504] - Ignition off trigger ignored by firmware
*[FW-512] - Possible reboot of camera because of continuous recording failing from time to time
*[FW-513] - Possible reboot of camera because of GPS writing method

Story

*[FW-501] - Driver posture estimator class
*[FW-502] - Create a new filesystem/kernel containing hidraw driver
*[FW-509] - Adapt Facial Recognition algorithm to allow only frontal faces
*[FW-510] - Tunning FR validation template algorithm params
*[FW-511] - Add a method to log all storage files

==Version 31.1==

'''Bug'''

*[FW-496] - Missing GPS packages on circular buffer
*[FW-505] - Continuous recording segments are delayed up to 1 minute
*[FW-506] - Preview event files never uploaded when events are triggered while cellular connection is lost

'''Story'''

*[FW-491] - Implement a mechanism in order to upload camera log using cellular
*[FW-495] - Implement Seat Belt event
*[FW-497] - Proof of concept for buzzer using FT260 chip
*[FW-499] - Implement driver protocol LED chip
*[FW-500] - Implement driver protocol MIC2680 + FT260
*[FW-507] - Adapt image for new type of lenses and case
*[FW-508] - Adjust Facial Recognition algorithm to trigger detection based on a speed threshold

==Verion 31.0==

'''Bug'''

*[FW-492] - Empty gps high-resolution data packages are sent while GPS signal not present

==Version 30.8==

'''Bug'''

*[FW-480] - Application crash after a while only if CR is enabled
*[FW-481] - Date of event sent incorrect while camera has no GPS signal
*[FW-482] - Randomly events are not completely written on SD card

'''Story'''

*[FW-473] - Gain control on X2 camera driver (auto white balance)

==Version 30.7==

'''Story'''

*[FW-475] - Add possibility to trigger multiple camera events per session
*[FW-476] - Eliminate bottom bar with technical info from DAD image

==Version 30.6==

'''Bug fix'''

*[FW-469] - Format SD card issue on Factory Tool proccess
*[FW-470] - Live tracking local database could not be disabled
*[FW-471] - Transfer freezes due to connection lost on Beta uploading firmware
*[FW-472] - Transfer file upload is too slow

==Version 30.5==

'''Bug fix'''

*[FW-442] - Unable to store GSM data to Database when network connection is not present
*[FW-444] - Package error on Events without GPS
*[FW-468] - Triggering more consecutive shock events in some particular cases (RMS->Wylie->Event IDs: 5Y1A44DCACD6, 7Y1A44F2297C, 4Y1A4476788B)

'''Story'''

*[FW-272] - Migrate Driver ID module
*[FW-310] - Create mechanism for FR to use local storage for templates
*[FW-430] - Blur the other faces than driver from the Drowsiness and Distracted behavior picture
*[FW-439] - Implementing covered camera event
*[FW-440] - Add the ability to disable all video triggers
*[FW-443] - Ability to clear FR and GPS local databases via LTI command
*[FW-445] - Face Recognition II implementation (Glasses Detection & Local Templates)
*[FW-449] - Create/test FW build for manufacturing
*[FW-451] - Extend DAD event to write parameters into database

==Version 30.4==

'''Bug fix'''

*[FW-410] - Wrong estimated size of Extended video file when inside camera is disabled
*[FW-418] - Changing the data collection mechanism from acquisition in order to prevent possible app crash (memory issues) when an event / continuous recording is triggered
*[FW-420] - Change the acquisition in circular buffer by using smart pointers (shard_ptr) instead of raw pointers. That should strongly improve the memory management and reduce the memory issues
*[FW-421] - At ignition OFF camera disconnects from node.js server without sending turn off status
*[FW-423] - Application crashes sometime when the device is transferring events via WI-FI
*[FW-429] - The DAD image should be composed from 2 images: the processed image and the black bar with technical information. That should be outside the processed image. See bad example attached
*[FW-431] - Web socket communication is blocked sometimes while and error package is received from server
*[FW-433] - Low audio level on HF for some of the boards
*[FW-434] - Application crashes sometime while a SDW event is in progress

'''Story'''

*[FW-364] - Collect GPS coordinates and speed at 3 seconds interval and send it to server via cell
*[FW-386] - Create a firmware update mechanism for cellular download
*[FW-422] - Upload SDW, FR and DAD event additional images via cellular to S3 storage
*[FW-424] - Ability to disable a particular event type from cellular upload
*[FW-428] - Ability to change the bit-rate when the events are uploaded via cellular in order to improve the video quality

==Version 30.3==

'''Bug fix'''

*[FW-403] - Both cameras (inside / outside) are not synchronizing after a while
*[FW-411] - Sometime camera get stuck to green-green after ignition off

'''Story'''

*[FW-404] - When you request a Live Telematics event and another event is on going, send a status to the node server that the event can not be performed
* Improvements on Drowsiness / distraction event trigger

==Version 30.2==

'''Bug fix'''

*[FW-358] - Card usage error for read-only cards .
*[FW-361] - Unable to mount bad Sd card
*[FW-391] - Wi-Fi connection sometimes cannot be established or it takes a long period of time
*[FW-392] - Requests by date on continuous recording transfer process returns file not found
*[FW-395] - Random FW crashes on different boards - memory issue
*[FW-396] - Update stick did not work properly ( it didn't transfer the settings to the new version)
*[FW-399] - When you create an LT event / Check driver the camera reboots (V 30.1)]

'''Story'''

*[FW-365] - Send all camera settings values to server via cell
*[FW-378] - Extend the cell communication protocol to accept GPS and accelerometer data for events uploads
*[FW-384] - Implement drowsiness and distraction events
*[FW-397] - Integrating buzzer class to X2 FW
*[FW-398] - Create mechanism to upload camera log via cell
*[FW-400] - Add audio on preview (cell download event) file
*[FW-401] - Create a mechanism for cellular download to save events while internet connection is not present
*[FW-402] - Create a mechanism to update camera settings via USB stick

==Version 30.1==

'''Bug fix'''

*[FW-337] - Low sound volume on events
*[FW-347] - Accident prediction mechanism failed to upload video to S3
*[FW-349] - GPS data packages not send to LTI for entire session
*[FW-352] - Sometimes live tracking packages are send again after ignition on
*[FW-356] - Ir leds should be off in Transfer mode
*[FW-357] - Problems on USB transfer
*[FW-359] - Wire events are not triggered in sleep mode

'''Story'''

*[FW-273] - Migrate Maintenance Module
*[FW-318] - Integrate log mechanism
*[FW-345] - Adapt preview mechanism to accept custom video frame rate and length
*[FW-348] - Extend LTI websocket protocol to accept all events type upload
*[FW-350] - Facial recognition optimizations
*[FW-354] - Expanding camera log to cover events section
*[FW-355] - Expand event format (add day/night flag and legal speed)

==Version 30.0==

'''Technical Story'''

*[FW-217] - Setting up a good build environment for firmware development (on Debian Linux)
'''Bug'''
*[FW-154] - Transfer Log Issue
*[FW-333] - Shock event is less sensitive than the previous implementation
*[FW-336] - Application crash
*[FW-346] - Random wire event triggered at the init app phase

'''Epic'''

*[FW-11] - Power-Up system integration
*[FW-195] - USB recovery tool
*[FW-242] - Migrate latest FW version to HF

'''Story'''

*[FW-23] - Integrate new file system and kernel(v 3.10.17) for X2
*[FW-24] - Test all applications and drivers on new filesystem/kernel
*[FW-78] - Implement the face recognition core using Neurotech APIs
*[FW-171] - Filesystem/kernel update using USB stick
*[FW-173] - Create class to generate face templates on the camera using FR API
*[FW-174] - Extend FW communication protocol to accept LTI FR API methods
*[FW-175] - Create a FR templates manager classes using face matching
*[FW-176] - Adapt all FW entities to accept FR Driver ID method
*[FW-177] - Establish Neurotechnology lib licensing method
*[FW-185] - Migrate FW to HF
*[FW-187] - Test the possibility of using G-Streamer for delivering encoded frames
*[FW-208] - Testing NFace verification component
*[FW-209] - Implementing FR communication with LTI Server
*[FW-241] - Re-evaluate FW migration on HF
*[FW-244] - Investigate FFMPEG library frame rate issues
*[FW-245] - Adapt pipeline to accept Gstreamer
*[FW-246] - Re-write event class
*[FW-249] - Port the FR test app code to the FW as a library
*[FW-257] - Migrate websocket communication and GSM management code to libraries
*[FW-261] - Migrate FFMPEG API
*[FW-262] - Idrive Pipeline - Create a class to collect event data from circular buffer
*[FW-263] - Re-write event module (pipeline collect) to accept multiple cameras
*[FW-264] - Migrate Disc Utils
*[FW-265] - Integrate disk utils / files manager to events
*[FW-266] - Migrate Trigger Event module
*[FW-267] - Migrate Configuration Module
*[FW-268] - Migrate Transfer Module
*[FW-269] - Migrate Preview (LT event) Module
*[FW-270] - Migrate GPS - route log
*[FW-271] - Migrate Continuous recording module
*[FW-274] - FR Licencees Management
*[FW-276] - FW light version for demo
*[FW-277] - Extend Pipeline to accept raw frames request
*[FW-278] - Adapt IPU class to accept concurential access
*[FW-279] - Adapt GStreamer wrapper to accept arbitrary data inputs
*[FW-280] - Adapt settings module to accept Face recognition and face matcher license files
*[FW-284] - Create trigger classes for shock, speed, periodic events
*[FW-295] - Patch for serial driver, sound driver, gpio/event and wi fi
*[FW-300] - Fix serial acquisition module to accept 1 second timeout
*[FW-301] - Create an ignition manager class
*[FW-302] - Integrating speed(gps) in SDW
*[FW-303] - Extend LTI protocol to accept SDW calibration
*[FW-304] - Extend LTI protocol to accept accident probability
*[FW-306] - Expand event module
*[FW-308] - Extract detected vehicle image from SDW module
*[FW-309] - Expand GPS module and add FR support
*[FW-311] - Extend ignition manager to accept sleep mode and stop
*[FW-313] - Firmware start up service
*[FW-314] - Migrate update application
*[FW-316] - Integrate preview, session, calibration triggers
*[FW-317] - Save and load sdw parameters from DB
*[FW-322] - Integrate safe mode mechanism while SD card is not accessed
*[FW-323] - Integrate local storage for LTI gps data
*[FW-324] - GPS file corruption
*[FW-325] - USB export events
*[FW-328] - Writing a class for detecting day /night time
*[FW-329] - Tunning sdw parameters for obtaining better fps
*[FW-330] - Create a USB stick update package
*[FW-331] - Create a mechanism to include build nr on fw version

==Version 25.4==

'''Bug'''

*[FW-338] - Alarm trigger operates on signal falling edge, not rising

==Version 25.3==

'''Bug'''

*[FW-255] - Segmentation on Live tracking package
*[FW-294] - Issue on events trigger that cause app to crash
*[FW-298] - G-force value stuck after ingnition on in sleep mode

==Version 25.2==

'''Bug'''

*[FW-145] - Small delay between video and sound
*[FW-293] - Issue on LT protocol that cause app to crash in case multiple ws close calls are received

'''Story'''

*[FW-292] - Add mechanism to disable LTI data local DB storage

==Version 25.1==

'''Bug'''

*[FW-291] - Issue on event, building threads may not exit locking all other triggers

==Version 25.0==

'''Bug'''

*[FW-135] - Transfer error from Sleep mode
*[FW-153] - Sleep Issue after various transfer disconnection
*[FW-290] - Issue on shock events type detection, unknown shock is tarted by CC as valid type.

==Version 24.9==

'''Bug'''

*[FW-237] - Module GSM connects only to 2G
*[FW-238] - WIFI transfer is bypassed, camera goes directly to sleep mode

'''Epic'''

*[FW-13] - Porting HF filesystem/kernel on X2 board
*[FW-160] - Websocket comunication to LTI API

'''Story'''

*[FW-161] - Create a parser class which implements the bidirectional comunication protocol
*[FW-172] - Integrate a websocket client
*[FW-178] - Adapt current classes to the new communication methods
*[FW-186] - Study IoT Amazon platform
*[FW-225] - Extend ws communication to allow remote camera setting
*[FW-226] - Create sqlite warehouse mechanism for data packages sent via ws
*[FW-232] - Rewrite trigger module to allow delays between ignition signals
*[FW-233] - Adapt Driver Id to new websocket communication protocol
*[FW-235] - Create a mechanism to verify the Read only SD Cards and send the a status to CC

'''Sub-task'''

*[FW-70] - Extend wifi protocol to accept kernel update files

==Version 24.8==

'''Story'''

*[FW-234] - Video acquisition failed to stat on inside camera causing the pipeline to remain an init phase

==Version 24.6==

'''Bug'''

*[FW-218] - Continous Recording Setting fail to Start video Aquisition
*[FW-219] - Unable to Unmount SD card Error in Sleep
*[FW-220] - Write operations to sqlite db used to store tracking data decreases significantly SD card lifetime - one of red-green cause

==Version 24.5==

'''Bug'''

*[FW-204] - pppd config file become corrupted while is recreated by te application

'''Story'''

*[FW-205] - Create class to operate bootdevs
*[FW-206] - Create method to write config data to flash
*[FW-210] - Integrate USB stick bootloader update
*[FW-211] - Eliminate any constant writing on OS SD card
*[FW-212] - Improve date/time in management / GPS class
*[FW-213] - Add a fail-safe mechanism on preview upload method

==Version 24.4==

'''Bug'''

*[FW-120] - Events delay Issue .
*[FW-144] - Sleep mode G-Force Issue
*[FW-158] - 2G networks registration cause USB disconnect

'''Story'''

*[FW-157] - Add multiple preferred operators

'''Sub-task'''

*[FW-159] - Add command to disable 2G bands

==Version 24.3==

'''Bug'''

*[FW-121] - Sleep mode led issue
*[FW-122] - Event in Transfer Mode
*[FW-123] - Event Time not accurate
*[FW-124] - Sleep timer doens't trasnfer properly
*[FW-125] - Event prepare time issue
*[FW-126] - Shock in Transfer Issue
*[FW-127] - Driver Id - not Initiating .
*[FW-128] - Transfer issue for events
*[FW-131] - Reboot In sleep after Shock Event
*[FW-132] - Led Issue after Transfer
*[FW-134] - Green wire event length issue
*[FW-136] - Transfer Stick download Issue
*[FW-138] - Extended video issue in sleep mode
*[FW-139] - Size alocated for Events Issue
*[FW-140] - Events out of Sync
*[FW-142] - Ignition Off Trigger Skipped Issue
*[FW-143] - Event Inside Camera Issue
*[FW-149] - Late start for event trigger

'''Story'''

*[FW-4] - Accelerometer alg. events detection
*[FW-14] - Acculitx integration
*[FW-80] - Build firmware framework
*[FW-89] - Redesign the X2 FW
*[FW-105] - Continuous recording reorganize

'''Sub-task'''

*[FW-6] - Accelerometer alg. preliminary QA
*[FW-46] - Study their integration requirements
*[FW-150] - New accelerometer event detection algorithm

==Version 23.0==

'''Bug'''

*[FW-97] - Format command sent by CC fails
*[FW-98] - Transfer process fails camera goes directly to sleep mode
*[FW-99] - Wrong LEDs status in sleep mode
*[FW-100] - Transfer event issue
*[FW-102] - Periodic timer doesn’t work properly.
*[FW-104] - Stick transfer Led Issue
*[FW-109] - Transfer Events Issues on USB Transfer
*[FW-110] - Shock event issue
*[FW-111] - Corrupted name on transfer release

==Version 22.9==

'''Bug'''

*[FW-81] - Aplication sometimes crashes at the initialization phase, camera remains in Red-Green state [1001]
*[FW-85] - Events could be triggered at Ignition on while camera is in sleep mode [1002]
*[FW-94] - Continuous recording delayed while an event is triggered.

'''Story'''

*[FW-86] - Possible counterfeit SD cards on X2 devices [1000]
*[FW-90] - Redesig of the watchdog mechamism
*[FW-91] - Verify and improve factory tools module
*[FW-93] - Create LEDs sequence in case a critical error is thrown followed by camera reboot
*[FW-95] - Harcode threshold time to 20 seconds for speed events

==Version 22.8==

'''Bug'''

*[FW-82] - GPS coordinates conversion throws error [1004]
*[FW-83] - GSM/3G module network registration issue [1003]

==Version 22.7==

'''Sub-task'''

*[FW-87] - Add mechanism to synchronize all acquisition and memory allocation threads

==Version 22.6==

'''Bug'''

*[FW-9] - WiFi protocol issue on files upload method
*[FW-76] - Program fails at the initialization stage
*[FW-77] - Continuous recording mux process cause program failure

'''Story'''

*[FW-1] - Live tracking data package improvements/add coordinates batch
*[FW-44] - Add mechanism to select a specific operator using the modem manual selection
*[FW-45] - Integrate recovery module
*[FW-75] - Preserve tracking session data into SQLite Db in case of unexpected reboots
*[FW-79] - Send reboot command after ignition on is received while camera is in sleep mode

'''Sub-task'''

*[FW-56] - Alter modem communication process in order to allow both modes for operator selection(manual and automatic)

==Version 22.4==

'''Bug'''

*[FW-32] - Events have bigger size than expected (usually 2 minutes)
*[FW-39] - Stat method or open CR files fails on ffmpeg moduls
*[FW-51] - ffmpeg encoding fails after 12-24h of continuous event triggers
*[FW-52] - 3G module is unable to be enumerated on USB port
*[FW-55] - Module AT port become unavailable

'''Story'''

*[FW-16] - Change LED behavior on transfer mode, use different seqance instead of AMBER falsh
*[FW-31] - Health Log(alarm codes)
*[FW-57] - Audio codec driver gain adjust from userspace
*[FW-59] - Correct Video Acquisition Module
*[FW-61] - Add while check with retires on stat method of con rec files
*[FW-62] - Modify open flags for important files (events) to assure data integrity in case of power failure
*[FW-63] - Add check of methods in ffmpeg, video encode and cr modules
*[FW-67] - Increase size of encode circular buffer

'''Sub-task'''

*[FW-49] - Improve FW-modem communication (at AT commands level)
*[FW-50] - Add methods for netowrk scan and operator selection
*[FW-53] - Implement AT command for monitoring the 3G module voltage
*[FW-58] - Investigate audio driver in order to determine if gain level can be controlled
*[FW-66] - Add method to select a specific audio gain based on camera s/n

==Version 22.2==

'''Bug'''

*[FW-2] - Possible problem on CR request
*[FW-28] - WiFi connection is interrupted while CC is trying to inspect the SD Card
*[FW-48] - Abnormal LED behavior on transfer mode

'''Story'''

*[FW-41] - Monitor the processor temperature and frequency on a camera placed in the thermal chamber running only the OS

==Version 22.1==

'''Story'''

*[FW-10] - 3G module AT communication + web client improvments
*[FW-38] - 3G uptime monitoring
*[FW-60] - Critical Log don't write in file Module and Type
*[FW-68] - Add mechanism to update the 3G module firmware using AT commands

'''Sub-task'''

*[FW-20] - Build methods to rewrite the kernel
*[FW-35] - Create a new boot script that allows kernel updates
*[FW-40] - Implement Scan Disk Command

Manufacturing:AI Device Manufacturing and Programming Process

2020-03-25T10:56:57Z

Alexandra:

File:Lens.png

2020-03-25T10:49:34Z

Alexandra:

File:Sim.png

2020-03-25T10:48:33Z

Alexandra:

File:Lensholder.png

2020-03-25T10:48:17Z

Alexandra:

File:Label.png

2020-03-25T10:47:21Z

Alexandra:

File:Gasket1.png

2020-03-25T10:47:01Z

Alexandra:

File:Gasket.png

2020-03-25T10:46:39Z

Alexandra:

File:Card.png

2020-03-25T10:46:21Z

Alexandra:

File:Bolt.png

2020-03-25T10:46:05Z

Alexandra:

File:Driver-road.png

2020-03-25T10:45:42Z

Alexandra:

Manufacturing:AI Programmer Setup Wiring

2020-03-25T10:16:26Z

Alexandra: Created page with "=AI PROGRAMMER SETUP(WIRING)= *Connect Programmer to a 12 V Power Supplier – Power cable connects to the J2 connector on Programmer File:11.png *Connect Programmer t..."

=AI PROGRAMMER SETUP(WIRING)=

*Connect Programmer to a 12 V Power Supplier – Power cable connects to the J2 connector on Programmer

[[File:11.png]]

*Connect Programmer to PC – the cable connects to the J5 connector on Programmer and to the USB slot from USB Hub

[[File:22.png]]

*Connect Serial console cable to Programmer – it connects to the J4 connector on Programmer

[[File:33.png]]

*Insert Main Board into the Programmer holding fixture (secure its position with the plexiglass catcher)

[[File:44.png]]

*Connect Programmer to X3 (AI) Main Board – Power Signal cable connects to the J3 connector on Programmer and to the J1 on Main Board

[[File:55.png]]

*Connect X3 (AI) Main Board to PC – the cable connects to the Micro USB J9 connector on Main Board and to the USB slot from USB Hub.

[[File:66.png]]

USB cables will be connected to PC through a USB Hub (external power supply)

[[File:77.jpg]]

Main Page

2020-03-25T10:15:08Z

Alexandra:

[[File:Wiki.jpg]]

==CUSTOMER GUIDES==

<table><tr>
<td valign="top">
{| class="wikitable"
!style="width: 270px;"|Idrive Useful Links
|-
|rowspan="2"|
[http://admincenter.idriveglobal.com Idrive Admin Center]

[[Idrive Downloads]]

[http://wiki.idriveglobal.com Idrive Customer Wiki - wiki.idriveglobal.com]

[http://www.idriveglobal.com Idrive Web Site]

[http://itunes.apple.com/us/app/idrive-global-center/id498507809?ls=1&mt=8 Idrive App Apple Store]

[https://www.facebook.com/idriveGlobal/ Idrive on Facebook]

[http://twitter.com/idriveX1 Idrive on twitter]

[http://www.teamviewer.com Team Viewer]

[http://get.adobe.com/reader Adobe Reader]

[http://videolan.org Video Lan FLV player]

[https://www.freedom2manage.com Pod Systems SIM Management]

[https://go.trackvia.com TRACKVIA (Questti Installation Info]

|}

{| class="wikitable"
!style="width: 270px;"|Idrive Support
|-
|rowspan="2"|

[[File:settings2.png|center|70px]]

----

[http://wiki.idriveglobal.com/index.php?title=How_To_Open_a_Support_Ticket How To Open a Support Ticket]

[http://wiki.idriveglobal.com/index.php?title=Contact_Idrive_Support Contact Idrive Support]

[http://wiki.idriveglobal.com/index.php?title=Contact_Idrive_Support About RMA (Client)]

[[Idrive Base Station HDD Full]]

[[Idrive Control Center 2.0 Internal Admin User’s Guide]]

[[RMA Processing Policy and Procedures]]

[[Media:New_RMA_Shipping_Form.zip|New RMA Shipping Form]]

|}

</td>

<td valign="top">

{| class="wikitable"
!style="width: 270px;"|Software Customer Guides

|-
|rowspan="2"|
[[File:Smart-icon.png|center|70px]]

----

'''Software'''

----

[[Idrive Control Center 3.0 User’s Guide]]

[[iris User's Manual]]

[http://wiki.idriveglobal.com/index.php?title=Idrive_Global_Center_app_for_iPhone_and_iPad Idrive Global Center app for iPhone and iPad]

----

'''Base Station / Terminal'''

----

[[Mobile Base Station Installation Guide]]

[[idrive Micro Base Station Download Point Installation Guide]]

[http://wiki.idriveglobal.com/index.php?title=X1_%E2%80%A2_Base_Station_%E2%80%A2_Hardware_and_Software idrive Client FAQ]

----

'''Installation'''

----

[http://wiki.idriveglobal.com/index.php?title=Wired_Panic_Button_Installation_Guide Wired Panic Button Kit Installation Guide]

[http://wiki.idriveglobal.com/index.php?title=IR_LED_Illuminator_Kit_Installation_Guide IR LED Illuminator Kit Installation Guide]

----

'''Client Maintenance'''

----

[[Idrive Client weekly X Camera and D4 Maintenance]]

[[Best Practices Base Station, Access Point, and Remote Access]]

|}
</td>

<td valign="top">
{| class="wikitable"
!style="width: 270px;"|Hardware Customer Guides
|-
|rowspan="2"|

[[File:settings2.png|center|70px]]

----

'''AI'''

----
[[Idrive AI (Artificial Intelligence) Installation and Operation Guide]] ('''Left and Right driver images combined''')

[[PowerUp2 Installation and Operation and Specifications Guide]]

----

'''AI - Espanol'''

----

[[Idrive AI (Inteligencia Artificial) Guía de Instalación y Operación - Español]] ('''Imágenes izquierda y derecha combinadas''')

[[PowerUp2 Guía de Instalación, Operación y Especificaciones - Español]]

----

'''X2'''

----

[[Idrive X2V2 Installation and Operation Guide]]

[[Media:Idrive_X2V2_Installation_and_Operation_Guide_left_side_mount_v2.pdf |Idrive X2V2 Installation and Operation Guide - Left side mount for EMEA]]

[[Idrive X2 GSM or 3G Module Installation and operation guide]]

[[Idrive X2 Continuous Recording (CR) and Extended Video (settings and requests guide)]]

[[media:Idrive X2V2 Cable Lock Bracket.pdf| X2V2 Cable Lock Bracket PDF]]

[[Idrive GPS Tracker]]

[[Facial Recognition]]

----

'''X1'''

----

[http://wiki.idriveglobal.com/index.php?title=Idrive_X1_Installation_and_Operation_Guide Idrive X1 Installation and Operation Guide]

----

'''D4'''

----

[http://wiki.idriveglobal.com/index.php?title=Idrive_D4_Installation_and_Configuration_Guide idrive D4 Installation and Configuration Guide]

[http://wiki.idriveglobal.com/index.php?title=Idrive_Viewpro_User_Guide idrive Viewpro User Guide]

----

'''D4M 5/2019'''

----

[[Idrive D4M Installation and Configuration Guide]]

[[Idrive D4M H-Player; Client Video Player Software Client Manual]]

----

'''D8'''

----

[[Idrive D8 HDD Reader and Software]]

|}

</td>
</tr>
</table>

<table><tr>

==INTERNAL GUIDES==

===SOFTWARE===

<td valign="top">

{| class="wikitable"
!style="width: 270px;"|Idrive Internal Customer Guides
|-
|rowspan="2"|

[[File:Smart-icon.png|center|70px]]

----

'''Base Station / Software'''

----

[[Idrive Terminal Information and Policies]]

[[Idrive Control Center "Idrive Settings"]]

[[Idrive Support - Base Station first connection checklist]]

[[idrive "New Client" 2 hour Software Training procedure and guideline]]

[["New Client" Cellular Download; No Base Station; iris setup and training]]

----

'''X2 Information'''

----

[[Read X2 files from Storage SD Card]]

[[X2 Advanced Features]]

[[X2 Surge Ratings and voltages]]

[[X2 GSM Module Notes]]

[[Device Warranty Processes]]

[[USB Config Files]]

[[X2V2 WiFi channel properties]]

----

'''D8 Information'''

----

[[BNSF D8 device and alert management]]

[[D8 repair and reprocessing]]

----

'''Cellular Information'''

----

[[PodGroup (PodSystems) Information]]

[[Idrive X2 GSM Processes]]

|}

</td>

<td valign="top">
{| class="wikitable"
!style="width: 270px;"|Features Documentation
|-
|rowspan="2"|

[[File:Sites-icon.png|center|60px]]

----
'''Software'''
----
[[Standard Reports]]

[[Clustering/FR Assignment Interface]]

[[Global Notifications]]

[[Fleet Manager]]

----
'''Advanced Development'''
----
[[Safe Distance Warning]]

[[Drowsiness and Distraction]]

[[Coaching Reports]]

[[Monetize Reports]]

|}
{| class="wikitable"
!style="width: 270px;"|Idrive releases
|-
|rowspan="2"|

[[File:IdriveX1_small_tech_specs1.jpg|center|120px]]

----
[[Admin Center Changelog]]

[[Control Center Changelog]]

[[IRIS Changelog]]

[[X2 Firmware Releases | X2 Firmware Changelog ]]

[[NODE Changelog]]

[[API Changelog]]

[[IRA Changelog]]

[[X3 Firmware Changelog]]

[[AOSP Changelog]]
|}

</td>

<td valign="top">

{| class="wikitable"
!style="width: 270px;"|Idrive Admin Center
|-
|rowspan="2"|

[[File:wikiac.jpg|center]]

----

[[Idrive AdminCenter Specs]]

[[Outlook Tickets Plugin Specs]]

[[Idrive 2.0 Admin Center Changelog]]

|}

{| class="wikitable"
!style="width: 270px;"|Idrive Control Center
|-
|rowspan="2"|

[[File:wikicc.jpg|center]]

----

[[Idrive 2.0 Control Center Changelog | Idrive 2.0 Control Center Changelog]]

|}
{| class="wikitable"
!style="width: 270px;"|Idrive Factory Tool
|-
|rowspan="2"|

[[File:wikifc.jpg|center]]

----

[[Idrive Factory Tool 2.0 Specs]]

|}
</td>

<td valign="top">
{| class="wikitable"
!style="width: 245px;"|Wifi Related
|-
|rowspan="2"|

[[File:mikrotik.jpg|center|160px]]

----

[[RB Groove Configuration]]

[[Media:Winbox.zip|WinBox (MikroTik Router Software)]]

[[MicroTIK VPN Solution]]

[[Transfer Point Documentation]]

[[Wireless Bridge Documentation]]

[[Netwatch Script Reboots MikroTik]]

[[Vonets VAR11N WiFi Router programming guide (Access Point for Idrive Mobile Base Station)]]

|}
</td>
</tr>
</table>

<table>
<tr>

===HARDWARE===

<td valign="top">
{| class="wikitable"
!style="width: 270px;"|Stonkam D8

|-
|rowspan="2"|

[[File:Sites-icon.png|center|60px]]

[[Stonkam D8 Contact & Notes - What is it?]]

[[Stonkam D8 Initial Configuration and Setup]]

[[Stonkam D8 Configuration Checklist]]

[[Stonkam D8 Installation Guide]]

[[Idrive D8 DVR Installation Guide]]

[[Stonkam D8 End User Guide]]

|}

<td valign="top">

{| class="wikitable"
!style="width: 270px;"| EZ Storage D4
|-
|rowspan="2"|

[[File:IdriveX4_small_tech_specs.jpg|center|150px]]

----

[[D4 Initial Configuration and Setup]]

*''updated firmware and EZ config Nov 2014 adding Backing Cam trigger full screen''

[[D4 DVR_CoreBoard replacement (NAND-NOR_Flash Conversion) ]]

[[media:D4_install_monitor_to_security_box.pdf | D4 install monitor to security box]]

[[media:Train_Inverter_D4_power.pdf‎ | Locomotive inverter and relay schematic for D4 installation ignition and powering ]]

*'''D4M 5/2019 items'''

[[New D4M (4/17/19) Initial Configuration and Setup]]

|}
</td>
<td valign="top">
{| class="wikitable"
!style="width: 270px;"|Idrive Base Station
|-
|rowspan="2"|

[[File:base-station-idrive.jpg|center|160px]]

----

[[Idrive Base Station General Requirements]]

[[Base Station Configuration Guide ]]

[[Media:Base_Station_Checklist_121318.zip|Base Station Checklist (Current as of 12/13/18)]]

[[Base Station Connectivity Information ]]

[[Base Station Upgrade Hard Drives ]]

[[Idrive Base Station 2TB upgrade procedure]]

[[Micro Base Station Download Point Configuration Guide]]

|}
</td>

<td valign="top">
{| class="wikitable"
!style="width: 270px;"|Idrive X2
|-
|rowspan="2"|

[[File:IdriveX1_small_tech_specs1.jpg|center|120px]]

----
[[Driver ID Specs]]

[[ Linux | Linux Freescale 3.0.35_4.1.0]]

[[Idrive X2 Specs]]

[[Idrive X2 Notes]]

|}

</td>

<td valign="top">

{| class="wikitable"
!style="width: 270px;"|Video Splitter
|-
|rowspan="2"|

[[Video Splitter Assembly]]

|}

{| class="wikitable"
!style="width: 270px;"|Camera Boost Converter
|-
|rowspan="2"|

[[Boost Converter Assembly]]

|}

{| class="wikitable"
!style="width: 270px;"|Harsh Environment Cable Kit
|-
|rowspan="2"|

[[Harsh Environment Cable Kit]]

|}

</td>
</tr>
</table>

<table><tr>
<td valign="top">
</td>

==MANUFACTURING==

<td valign="top">
{| class="wikitable"
!style="width: 270px;"|Idrive Manufacturing
|-
|rowspan="2"|

[[File:manuficon.jpg|center|100px]]

----

'''AI'''

----

[[Manufacturing:AI Device Manufacturing and Programming Process | AI Device Manufacturing and Programming Process]]

[[Manufacturing:AI Programmer Setup Wiring| AI Programmer Setup Wiring]]

----

'''X2'''

----

[[Manufacturing:X2 Device Manufacturing and Programming Process | X2 Device Manufacturing and Programming Process]]

[[Manufacturing:X2V2 Device Manufacturing and Programming Process | X2V2 Device Manufacturing and Programming Process]]

[[Manufacturing:X2 Programming Station Documentation | X2 Programming Station Documentation]]

[[Manufacturing:Factory Tool Documentation | Factory Tool Documentation]]

[[Manufacturing:X2 Ubuntu Configuration for MicroSD programming| X2 Ubuntu Configuration for MicroSD programming]]

[[Manufacturing: SDShark use for MicroSD programming | WireShark use for MicroSD programming]]

----

'''X1'''

----

[[Manufacturing:X1 V7 Series Device Manufacturing and Programming Process | X1 V7 Series Device Manufacturing and Programming Process]]

[[X1 V7 Series Device Manufacturing and Programming Admin Documentation]]

|}

</td>
</tr>
</table>

<table>
<tr>

==INTERNAL PROCESSES==

<td valign="top">
{| class="wikitable"
!style="width: 270px;"|Idrive Internal Process Guides
|-
|rowspan="2"|

[[File:Sites-icon.png|center|60px]]

----

[[Idrive Shipping Receiving Process]]

[[Harmonized Codes Information for Imports]]

[[Idrive Order Handling Process ]]

[[Idrive Customer Exception Process ]]

[[Idrive Parts Ordering Process]]

[[New Client Implementation Schedule ]]

|}

</td>

<td valign="top">
{| class="wikitable"
!style="width: 270px;"|Idrive Internal Technical Support Guides
|-
|rowspan="2"|

[[File:Support.JPG|center|60px]]

----

'''Fix SQL Error''' in Server 2016, 2014, or 2008 -
:[[Could not find the Database Engine startup handle]]

:[[Fix; Export from CC fails to see mapped Network drive from Windows 10]]

|}

</td>

<td valign="top">

{| class="wikitable"
!style="width: 270px;"|Using Wiki
|-
|rowspan="2"|

[[File:mediawiki.jpg|center|86px]]

----

Consult the [//meta.wikimedia.org/wiki/Help:Contents User's Guide] for information

on using the wiki software.

Getting started
----
* [//www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]
* [//www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]

|}
</td>

</tr>
</table>

<table>
<tr>

==IDRIVE ROMANIA==

<td valign="top">
{| class="wikitable"
!style="width: 270px;"|Idrive Romania
|-
|rowspan="2"|

[[File:ro.jpg|center|60px]]

----

[[Idrive Hardware Development]]

[[Idrive Software Development]]

[[Regulament de Ordine Interioara]]

Laborator

Utile

|}

</td>

</tr>
</table>

----

Copyright © 2020 Idrive. All rights reserved.

File:66.png

2020-03-25T10:13:45Z

Alexandra:

Manufacturing:AI Programmer Setup

2020-03-25T10:12:27Z

Alexandra:

Manufacturing:AI Programmer Setup

2020-03-25T10:10:23Z

Alexandra: Created page with "=AI PROGRAMMER SETUP(WIRING)= *Connect Programmer to a 12 V Power Supplier – Power cable connects to the J2 connector on Programmer *Connect Programmer to PC – the cable..."

=AI PROGRAMMER SETUP(WIRING)=

*Connect Programmer to a 12 V Power Supplier – Power cable connects to the J2 connector on Programmer

*Connect Programmer to PC – the cable connects to the J5 connector on Programmer and to the USB slot from USB Hub

*Connect Serial console cable to Programmer – it connects to the J4 connector on Programmer

*Insert Main Board into the Programmer holding fixture (secure its position with the plexiglass catcher)

*Connect Programmer to X3 (AI) Main Board – Power Signal cable connects to the J3 connector on Programmer and to the J1 on Main Board

*Connect X3 (AI) Main Board to PC – the cable connects to the Micro USB J9 connector on Main Board and to the USB slot from USB Hub.

USB cables will be connected to PC through a USB Hub (external power supply)

File:77.jpg

2020-03-25T10:09:45Z

Alexandra:

File:55.png

2020-03-25T10:09:01Z

Alexandra:

File:44.png

2020-03-25T10:08:49Z

Alexandra:

File:33.png

2020-03-25T10:08:31Z

Alexandra:

File:22.png

2020-03-25T10:08:18Z

Alexandra:

File:11.png

2020-03-25T10:08:05Z

Alexandra:

Main Page

2020-03-25T10:00:41Z

Alexandra:

[[File:Wiki.jpg]]

==CUSTOMER GUIDES==

<table><tr>
<td valign="top">
{| class="wikitable"
!style="width: 270px;"|Idrive Useful Links
|-
|rowspan="2"|
[http://admincenter.idriveglobal.com Idrive Admin Center]

[[Idrive Downloads]]

[http://wiki.idriveglobal.com Idrive Customer Wiki - wiki.idriveglobal.com]

[http://www.idriveglobal.com Idrive Web Site]

[http://itunes.apple.com/us/app/idrive-global-center/id498507809?ls=1&mt=8 Idrive App Apple Store]

[https://www.facebook.com/idriveGlobal/ Idrive on Facebook]

[http://twitter.com/idriveX1 Idrive on twitter]

[http://www.teamviewer.com Team Viewer]

[http://get.adobe.com/reader Adobe Reader]

[http://videolan.org Video Lan FLV player]

[https://www.freedom2manage.com Pod Systems SIM Management]

[https://go.trackvia.com TRACKVIA (Questti Installation Info]

|}

{| class="wikitable"
!style="width: 270px;"|Idrive Support
|-
|rowspan="2"|

[[File:settings2.png|center|70px]]

----

[http://wiki.idriveglobal.com/index.php?title=How_To_Open_a_Support_Ticket How To Open a Support Ticket]

[http://wiki.idriveglobal.com/index.php?title=Contact_Idrive_Support Contact Idrive Support]

[http://wiki.idriveglobal.com/index.php?title=Contact_Idrive_Support About RMA (Client)]

[[Idrive Base Station HDD Full]]

[[Idrive Control Center 2.0 Internal Admin User’s Guide]]

[[RMA Processing Policy and Procedures]]

[[Media:New_RMA_Shipping_Form.zip|New RMA Shipping Form]]

|}

</td>

<td valign="top">

{| class="wikitable"
!style="width: 270px;"|Software Customer Guides

|-
|rowspan="2"|
[[File:Smart-icon.png|center|70px]]

----

'''Software'''

----

[[Idrive Control Center 3.0 User’s Guide]]

[[iris User's Manual]]

[http://wiki.idriveglobal.com/index.php?title=Idrive_Global_Center_app_for_iPhone_and_iPad Idrive Global Center app for iPhone and iPad]

----

'''Base Station / Terminal'''

----

[[Mobile Base Station Installation Guide]]

[[idrive Micro Base Station Download Point Installation Guide]]

[http://wiki.idriveglobal.com/index.php?title=X1_%E2%80%A2_Base_Station_%E2%80%A2_Hardware_and_Software idrive Client FAQ]

----

'''Installation'''

----

[http://wiki.idriveglobal.com/index.php?title=Wired_Panic_Button_Installation_Guide Wired Panic Button Kit Installation Guide]

[http://wiki.idriveglobal.com/index.php?title=IR_LED_Illuminator_Kit_Installation_Guide IR LED Illuminator Kit Installation Guide]

----

'''Client Maintenance'''

----

[[Idrive Client weekly X Camera and D4 Maintenance]]

[[Best Practices Base Station, Access Point, and Remote Access]]

|}
</td>

<td valign="top">
{| class="wikitable"
!style="width: 270px;"|Hardware Customer Guides
|-
|rowspan="2"|

[[File:settings2.png|center|70px]]

----

'''AI'''

----
[[Idrive AI (Artificial Intelligence) Installation and Operation Guide]] ('''Left and Right driver images combined''')

[[PowerUp2 Installation and Operation and Specifications Guide]]

----

'''AI - Espanol'''

----

[[Idrive AI (Inteligencia Artificial) Guía de Instalación y Operación - Español]] ('''Imágenes izquierda y derecha combinadas''')

[[PowerUp2 Guía de Instalación, Operación y Especificaciones - Español]]

----

'''X2'''

----

[[Idrive X2V2 Installation and Operation Guide]]

[[Media:Idrive_X2V2_Installation_and_Operation_Guide_left_side_mount_v2.pdf |Idrive X2V2 Installation and Operation Guide - Left side mount for EMEA]]

[[Idrive X2 GSM or 3G Module Installation and operation guide]]

[[Idrive X2 Continuous Recording (CR) and Extended Video (settings and requests guide)]]

[[media:Idrive X2V2 Cable Lock Bracket.pdf| X2V2 Cable Lock Bracket PDF]]

[[Idrive GPS Tracker]]

[[Facial Recognition]]

----

'''X1'''

----

[http://wiki.idriveglobal.com/index.php?title=Idrive_X1_Installation_and_Operation_Guide Idrive X1 Installation and Operation Guide]

----

'''D4'''

----

[http://wiki.idriveglobal.com/index.php?title=Idrive_D4_Installation_and_Configuration_Guide idrive D4 Installation and Configuration Guide]

[http://wiki.idriveglobal.com/index.php?title=Idrive_Viewpro_User_Guide idrive Viewpro User Guide]

----

'''D4M 5/2019'''

----

[[Idrive D4M Installation and Configuration Guide]]

[[Idrive D4M H-Player; Client Video Player Software Client Manual]]

----

'''D8'''

----

[[Idrive D8 HDD Reader and Software]]

|}

</td>
</tr>
</table>

<table><tr>

==INTERNAL GUIDES==

===SOFTWARE===

<td valign="top">

{| class="wikitable"
!style="width: 270px;"|Idrive Internal Customer Guides
|-
|rowspan="2"|

[[File:Smart-icon.png|center|70px]]

----

'''Base Station / Software'''

----

[[Idrive Terminal Information and Policies]]

[[Idrive Control Center "Idrive Settings"]]

[[Idrive Support - Base Station first connection checklist]]

[[idrive "New Client" 2 hour Software Training procedure and guideline]]

[["New Client" Cellular Download; No Base Station; iris setup and training]]

----

'''X2 Information'''

----

[[Read X2 files from Storage SD Card]]

[[X2 Advanced Features]]

[[X2 Surge Ratings and voltages]]

[[X2 GSM Module Notes]]

[[Device Warranty Processes]]

[[USB Config Files]]

[[X2V2 WiFi channel properties]]

----

'''D8 Information'''

----

[[BNSF D8 device and alert management]]

[[D8 repair and reprocessing]]

----

'''Cellular Information'''

----

[[PodGroup (PodSystems) Information]]

[[Idrive X2 GSM Processes]]

|}

</td>

<td valign="top">
{| class="wikitable"
!style="width: 270px;"|Features Documentation
|-
|rowspan="2"|

[[File:Sites-icon.png|center|60px]]

----
'''Software'''
----
[[Standard Reports]]

[[Clustering/FR Assignment Interface]]

[[Global Notifications]]

[[Fleet Manager]]

----
'''Advanced Development'''
----
[[Safe Distance Warning]]

[[Drowsiness and Distraction]]

[[Coaching Reports]]

[[Monetize Reports]]

|}
{| class="wikitable"
!style="width: 270px;"|Idrive releases
|-
|rowspan="2"|

[[File:IdriveX1_small_tech_specs1.jpg|center|120px]]

----
[[Admin Center Changelog]]

[[Control Center Changelog]]

[[IRIS Changelog]]

[[X2 Firmware Releases | X2 Firmware Changelog ]]

[[NODE Changelog]]

[[API Changelog]]

[[IRA Changelog]]

[[X3 Firmware Changelog]]

[[AOSP Changelog]]
|}

</td>

<td valign="top">

{| class="wikitable"
!style="width: 270px;"|Idrive Admin Center
|-
|rowspan="2"|

[[File:wikiac.jpg|center]]

----

[[Idrive AdminCenter Specs]]

[[Outlook Tickets Plugin Specs]]

[[Idrive 2.0 Admin Center Changelog]]

|}

{| class="wikitable"
!style="width: 270px;"|Idrive Control Center
|-
|rowspan="2"|

[[File:wikicc.jpg|center]]

----

[[Idrive 2.0 Control Center Changelog | Idrive 2.0 Control Center Changelog]]

|}
{| class="wikitable"
!style="width: 270px;"|Idrive Factory Tool
|-
|rowspan="2"|

[[File:wikifc.jpg|center]]

----

[[Idrive Factory Tool 2.0 Specs]]

|}
</td>

<td valign="top">
{| class="wikitable"
!style="width: 245px;"|Wifi Related
|-
|rowspan="2"|

[[File:mikrotik.jpg|center|160px]]

----

[[RB Groove Configuration]]

[[Media:Winbox.zip|WinBox (MikroTik Router Software)]]

[[MicroTIK VPN Solution]]

[[Transfer Point Documentation]]

[[Wireless Bridge Documentation]]

[[Netwatch Script Reboots MikroTik]]

[[Vonets VAR11N WiFi Router programming guide (Access Point for Idrive Mobile Base Station)]]

|}
</td>
</tr>
</table>

<table>
<tr>

===HARDWARE===

<td valign="top">
{| class="wikitable"
!style="width: 270px;"|Stonkam D8

|-
|rowspan="2"|

[[File:Sites-icon.png|center|60px]]

[[Stonkam D8 Contact & Notes - What is it?]]

[[Stonkam D8 Initial Configuration and Setup]]

[[Stonkam D8 Configuration Checklist]]

[[Stonkam D8 Installation Guide]]

[[Idrive D8 DVR Installation Guide]]

[[Stonkam D8 End User Guide]]

|}

<td valign="top">

{| class="wikitable"
!style="width: 270px;"| EZ Storage D4
|-
|rowspan="2"|

[[File:IdriveX4_small_tech_specs.jpg|center|150px]]

----

[[D4 Initial Configuration and Setup]]

*''updated firmware and EZ config Nov 2014 adding Backing Cam trigger full screen''

[[D4 DVR_CoreBoard replacement (NAND-NOR_Flash Conversion) ]]

[[media:D4_install_monitor_to_security_box.pdf | D4 install monitor to security box]]

[[media:Train_Inverter_D4_power.pdf‎ | Locomotive inverter and relay schematic for D4 installation ignition and powering ]]

*'''D4M 5/2019 items'''

[[New D4M (4/17/19) Initial Configuration and Setup]]

|}
</td>
<td valign="top">
{| class="wikitable"
!style="width: 270px;"|Idrive Base Station
|-
|rowspan="2"|

[[File:base-station-idrive.jpg|center|160px]]

----

[[Idrive Base Station General Requirements]]

[[Base Station Configuration Guide ]]

[[Media:Base_Station_Checklist_121318.zip|Base Station Checklist (Current as of 12/13/18)]]

[[Base Station Connectivity Information ]]

[[Base Station Upgrade Hard Drives ]]

[[Idrive Base Station 2TB upgrade procedure]]

[[Micro Base Station Download Point Configuration Guide]]

|}
</td>

<td valign="top">
{| class="wikitable"
!style="width: 270px;"|Idrive X2
|-
|rowspan="2"|

[[File:IdriveX1_small_tech_specs1.jpg|center|120px]]

----
[[Driver ID Specs]]

[[ Linux | Linux Freescale 3.0.35_4.1.0]]

[[Idrive X2 Specs]]

[[Idrive X2 Notes]]

|}

</td>

<td valign="top">

{| class="wikitable"
!style="width: 270px;"|Video Splitter
|-
|rowspan="2"|

[[Video Splitter Assembly]]

|}

{| class="wikitable"
!style="width: 270px;"|Camera Boost Converter
|-
|rowspan="2"|

[[Boost Converter Assembly]]

|}

{| class="wikitable"
!style="width: 270px;"|Harsh Environment Cable Kit
|-
|rowspan="2"|

[[Harsh Environment Cable Kit]]

|}

</td>
</tr>
</table>

<table><tr>
<td valign="top">
</td>

==MANUFACTURING==

<td valign="top">
{| class="wikitable"
!style="width: 270px;"|Idrive Manufacturing
|-
|rowspan="2"|

[[File:manuficon.jpg|center|100px]]

----

'''AI'''

----

[[Manufacturing:AI Device Manufacturing and Programming Process | AI Device Manufacturing and Programming Process]]

[[Manufacturing:AI Programmer Setup | AI Programmer Setup]]

----

'''X2'''

----

[[Manufacturing:X2 Device Manufacturing and Programming Process | X2 Device Manufacturing and Programming Process]]

[[Manufacturing:X2V2 Device Manufacturing and Programming Process | X2V2 Device Manufacturing and Programming Process]]

[[Manufacturing:X2 Programming Station Documentation | X2 Programming Station Documentation]]

[[Manufacturing:Factory Tool Documentation | Factory Tool Documentation]]

[[Manufacturing:X2 Ubuntu Configuration for MicroSD programming| X2 Ubuntu Configuration for MicroSD programming]]

[[Manufacturing: SDShark use for MicroSD programming | WireShark use for MicroSD programming]]

----

'''X1'''

----

[[Manufacturing:X1 V7 Series Device Manufacturing and Programming Process | X1 V7 Series Device Manufacturing and Programming Process]]

[[X1 V7 Series Device Manufacturing and Programming Admin Documentation]]

|}

</td>
</tr>
</table>

<table>
<tr>

==INTERNAL PROCESSES==

<td valign="top">
{| class="wikitable"
!style="width: 270px;"|Idrive Internal Process Guides
|-
|rowspan="2"|

[[File:Sites-icon.png|center|60px]]

----

[[Idrive Shipping Receiving Process]]

[[Harmonized Codes Information for Imports]]

[[Idrive Order Handling Process ]]

[[Idrive Customer Exception Process ]]

[[Idrive Parts Ordering Process]]

[[New Client Implementation Schedule ]]

|}

</td>

<td valign="top">
{| class="wikitable"
!style="width: 270px;"|Idrive Internal Technical Support Guides
|-
|rowspan="2"|

[[File:Support.JPG|center|60px]]

----

'''Fix SQL Error''' in Server 2016, 2014, or 2008 -
:[[Could not find the Database Engine startup handle]]

:[[Fix; Export from CC fails to see mapped Network drive from Windows 10]]

|}

</td>

<td valign="top">

{| class="wikitable"
!style="width: 270px;"|Using Wiki
|-
|rowspan="2"|

[[File:mediawiki.jpg|center|86px]]

----

Consult the [//meta.wikimedia.org/wiki/Help:Contents User's Guide] for information

on using the wiki software.

Getting started
----
* [//www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]
* [//www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]

|}
</td>

</tr>
</table>

<table>
<tr>

==IDRIVE ROMANIA==

<td valign="top">
{| class="wikitable"
!style="width: 270px;"|Idrive Romania
|-
|rowspan="2"|

[[File:ro.jpg|center|60px]]

----

[[Idrive Hardware Development]]

[[Idrive Software Development]]

[[Regulament de Ordine Interioara]]

Laborator

Utile

|}

</td>

</tr>
</table>

----

Copyright © 2020 Idrive. All rights reserved.

Manufacturing:AI Device Manufacturing and Programming Process

2020-03-24T11:05:26Z

Alexandra:

=AI Device Manufacturing and Programming=

==AUTOMATIC INSTALL AND CONFIGURATION (VIA FACTORY TOOL)==

Notes: The Automatic install performs the following:

•installs the AOSP and the Firmware, gets device configuration from the Idrive AdminCenter (IP address, serial number etc.);

•tests triggering on the yellow, blue and green wires;

•provides lens focus mode so both lenses can be focused and glued.

!For this step, DO NOT use Developer Mode!

1. Click on the Factory - New Devices - Auto button

[[File:aa.png]]

2. Scan using the bar code scanner the Bar Code label present on the Main board and press Enter.

[[File:b.png]]

If no bar code scanner is available, manually type the serial number from the bar code label into the serial number input field.

3. Click on the Auto Install button and the Automatic Install window will open.

[[File:c.png]]

If the SN have already been introduced (device has already passed through one or more programming steps), a warning message will be displayed asking if you want to Continue or not. Continue if you want to reprogram the device, cancel if you introduced once more the SN by mistake.

4. In the Automatic Install window, Click on Start Installation button.

[[File:d.png]]

Installation and Configuration process steps:

1. Install AOSP

2. Install Firmware

3. Device Configuration

AI camera successfully installed and configured when all three buttons are GREEN.

[[File:c1.png]]

If all the steps are successfully completed, the program will enter into Lens Focus mode.

If any of these steps fails, the program will stop and give an error. Common errors are:

-Missing or corrupt storage SD card

-Serial cable not connected or incorrect polarity

-USB NIC or Internet connection missing

-I/O ports tester board missing

-Any assembly or incorrect component error

! In case any of the 3 steps fail (button will be red instead of green), there are two options (corrective actions):

1.Repeat the entire process by clicking on Start installation button in the Automatic Install window and the AOSP installation, Firmware installation and Device Configuration will be redone automatically.

2.Repeat manually only that specific step that failed:

a) Click on Factory - New Devices – Manual;

[[File:c2.png]]

b) Scan barcode

c) Depending on the step that failed, click either on Install Aosp button -> Start installation, either on Install Firmware buttonStart installation, either on Device Config – AC Sync – Lens Focus button -> Start configuration.

[[File:e.png]]

In case that the first step failed (Install Aosp), recommended would be to repeat automatically the process by clicking on Start installation button in the Automatic Install window.

===Lens Focus===

1. Select "Inside Camera" Tab and Focus the “Driver side” Lens (“Driver side” is the side containing the Processor).

[[File:f.png]]

The focal length for the inside camera should be ~1.5 meters

2. Select "Outside camera" tab and Focus the “Road side” Lens (“Road side” is the side containing the Power Connector).

[[File:g.png]]

Focus using the provided Idrive Focus Chart. Distance to chart can be 3,6,9 feet but the farther the better.

Optional: Use zoom mode (Show zoom button) to ensure accurate focus.

In Both Cameras tab, you can visualize both “Driver side” and “Road side” cameras on the screen (the screen will be splitted in two).

3. If images are focused and clear (the outside test text is accurate and readable), click on the "Lens Focus OK" button and the focus mode will close.

[[File:h.png]]

If one of the images or both images are not clear, or if the Streaming is not loading (“Loading…Please wait!” message is displayed), click on the "Lens Focus Not OK" and the factory tool will exit focus mode, so corrective actions can be taken.

! Corrective actions: Repeat manually the 3rd step: Factory - New Devices – Manual -> Scan barcode -> Device Config – AC Sync – Lens Focus -> Start Configuration

4. Once focused, fix each lens with a drop of super glue. Test the lenses after several minutes to ensure they have taken the glue and cannot be moved (it means the glue is dried).

5. Remove the device from the test fixture (programmer fixture).

6. Advance the device to Final Assembly step.

==FINAL ASSEMBLY AI CAMERA==

*Remove (by screwing) the screw nut from power supply connector on the Main board and set it aside.

[[File:1.jpg|290px|]]

*Connect speaker wire (red and black wire) into the J250 socket on the “Road” side of the Main Board.

[[File:2.png]]

*Assembly Main board with the “Driver” side up into the inferior case by gently pressing on Main board and by pulling the edges of the case.

[[File:3.png]]

*Tightens the screw nut removed in step 1 on the power supply connector (torque 0.2 Nm).

[[File:4.jpg]]

*Connect the wires into the sockets on “Driver” side of the Main board:

[[File:5.png]]

a.Connect 4G antenna – insert wire 1 in J6 socket on Main board;

[[File:5.1.png]]

b.Connect GPS antenna – insert wire 2 in J7 socket on Main board;

[[File:5.2.png]]

c.Connect Wi-Fi antenna – insert wire 3 in J5 socket on Main Board.

[[File:5.3.png]]

*Mount the Display module into the dedicated socket.

[[File:6.png]]

Remove the plastic protection foil from the display.

*Mount by screwing the superior case (use torque 0.3 Nm).

[[File:7.png]]

*Advance assembled AI cam to Final test process.

==FINAL TEST (VIA FACTORY TOOL)==

*Open Factory Tool -> Factory - New devices – Auto -> Event Test – Transfer and Play (event test window will open – see at point 7)

[[File:poza1.png]]

[[File:poza2.png]]

*Connect 5 assembled AI cameras to Switch boxes power supplies (Power and Ignition are OFF).

[[File:poza3.jpg|500px|]]

*Switch Power and Ignition ON -> AI cameras will start to boot (Idrive logo will be displayed).

[[File:poza4.jpg|400px|]]

[[File:poza5.png]]

In this phase, AI cameras connect to GPS and to network (2G/3G/4G). The operator must pay attention to the cameras screens to assure that connections are available, and that all the icons are displayed and there is no error code – See picture below.

[[File:poza6.png]]

*Trigger a SHOCK event by pulling (shaking) each AI camera backward and forward (once or twice)-> Message SHOCK will be displayed on the screen, moment when the camera starts recording the event.

[[File:poza7.jpg|400px|]]

*After triggering and recording the SHOCK event (display gets back to normal), Switch Ignition OFF for AI cameras.

In this phase, AI cameras connect to Wi-Fi and start transferring. A text with IGNITION OFF followed by CLOSING TRIGGERS, by CONNECTING WIFI and by TRANSFERING along with specific icons, will be displayed on the screen.

[[File:poza8.png]]

*In the event test window, click on Play for each of the AI camera in the Play events area -> the record of the SHOCK event will be played.

[[File:poza9.png]]

Verify the focus of both lenses (image clarity). If the image is clear, lens focus was done properly. If not, the camera must be put aside. Check also if GPS route was recorded.

*If lens focus OK and GPS route recorded -> Click on Label Printed – Print and print 2 labels. Close the window.

[[File:poza10.png]]

[[File:poza11.png|900px|]]

There will be displayed 2 messages: one for label print confirmation and one for beep confirmation.

If label was not printed, click NO and try again to reprint the label. Camera starts to beep only if label printed was confirmed. Once label print and beep confirmed, serial number text row turnes green. If there is no beep, it means that the camera has a problem with the speaker.

*Camera will shut down automatically (SHUTTING DOWN message will be displayed) -> Switch Power OFF and Unplug the camera.

[[File:poza12.jpg]]

*Apply one label on the bottom of the AI camera and one on the right side of the Final box.

[[File:poza13.jpg|500px|]]

[[File:poza14.jpg|500px|]]

*Put the AI camera into the Final box.

[[File:poza15.jpg|600px|]]

ISSUES:

*AI camera doesn’t boot (display is off): verify power circular connector if it’s properly soldered to the board.

If yes, AI camera has a problem with the display -> display needs to be replaced

If it’s not, manually redo the soldering of the connector.

*AI camera appear with red text in the event test window, click on View in the View Transfer Log and see what error occurred.

[[File:poza16.png]]

First, redo the final test (without another shock trigger). If camera didn’t pass second time either, try solutions below:

*Network error

verify if the 4G antenna connector is OK and properly inserted (visual inspection).

verify if the cable is properly soldered to the antenna.

If both above OK -> replace SIM card.

If one or both above are NOK, replace connector/replace cable/manually redo the soldering.

*GPS error

verify if the GPS antenna connector is OK and properly inserted (visual inspection)

verify if the cable is properly soldered to the antenna.

*Infinite loop = HW problem which requires a close HW verification.

*Lens focus NOK -> Disassemble the AI camera and replace entire gasket + lens holders + lens assembly.

*AI camera doesn’t beep = speaker problems -> verify if speaker connector is OK and if it’s properly inserted (visual inspection).

==Radu Notes==

The AI programmer is mandatory only one time when the board comes from China with the default chinese AOSP. Once the AOSP is overwritten with our AOSP, the programmer becomes optional.

You need a micro usb cable in order to connect camera to a computer usb port, a power source for AI camera and a computer with Windows 10 (preferable).

<br>

==Factory Tool Installation==

===Install Factory Tool===

Download and install the latest Factory Tool from Admin Center

<br>

===Firmware===

Firmware folder is auto-populated by the Factory Tool installer and should have the following structure:

- firmware.apk represents the current firmware version (40.0.55)

- updater.apk is a background application taking care about firmware and aosp upgrades / firmware crashes / background staffs. The current version is 1.0

- idrive_root is the place where we keep different files (neural networks, settings, etc)

- firmware.apk should be replaced every time when a new stable firmware is released. For example, if you have a new update.apk file, you can rename this file and copy it over firmware.apk. You have also to copy the same file over idrive_root/recovery.apk file

- The same mechanism should be used if we will upgrade updater.apk. That apk should also be copied over idrive_root/recovery_updater_app.apk.

- Any file from idrive_root folder is replaceable. In the future we can add / remove / replace any file from idrive_root

<br>

===Install the Android OS===

Download and install the latest AOSP from Admin Center

Unzip the ASOP archive

Copy the files to C:\Program Files (x86)\Idrive\Factory Tool 2.0\FactoryToolsAI\Aosp

Every time when a new AOSP is released, the files from Aosp folder should be replaced with the new files.

<br>

==FT Configuration==

Select Idrive Development > Settings (password > idrive2#dev)

<br>

====Disable Passwords ( if applicable)====

Click on Passwords tab and disable

<br>

====Config and Install====

Uncheck "Programmer enabled for AI devices"

[[File:ft_conf_install1.png|500px|]]

The Factory Tool is documented, but I don't have the documentation now 🙂 (Alexandra will send you all documents tomorrow morning)

However the process is very similar with X2. There are AI settings in Idrive Development->Settings->Config and Install (see below)

(DO NOT CHANGE the "sleep seconds" fields for AI devices only).

<br>

====Factory Tool Print Settings (Santa Barbara)====

[[File:GK420t_ft_print1.png|350px|]] [[File:GK420t_ft_print2.png|350px|]]

[[File:GK420t_ft_print3.png|500px|]]

<br>

<br>

==Idrive AI Labels Windows Configuration==

===Add the Printer===

Settings > printers

Add printer>

\\idr-x2-prog-1\Zdesigner GK420t

Click on printer and Manage > Printing preferences
Options> Darkness 25, Width 1.5" Height .5"

[[File:gk420t_settings1.png|500px|]]

<br>

=== GK420T Printer Configuration (Santa Barbara) ===

Install Zebra Setup Utilities (Not needed for Factory Tool)

[[File:zebra_pref1.jpg|300px|]] [[File:zebra_pref2.jpg|300px|]]

<br>

===Label supplies for GK420T printer in RMA area===

https://www.zpsstore.com/ShoppingCart.asp

https://www.barcodesinc.com

https://www.bradyid.com/en-us/family/cps-3053222 (In use in RMA Area)

Zebra Part #: 10011693

Label Size (WxH): 1.5" x 0.50"

Labels Per Roll: 9,420

Rolls Per Case: 4

Core Size: 3"

Outside Diameter: 8"Zebra Z-Ultimate 10011693

* NO perforation between label

Thermal Ribbon:

Zebra 5095 Performance Ribbon

https://www.barcodesinc.com/search.htm?search=05095GS06407&v=1

<br>

Manufacturing:AI Device Manufacturing and Programming Process

2020-03-24T11:01:03Z

Alexandra:

=AI Device Manufacturing and Programming=

==AUTOMATIC INSTALL AND CONFIGURATION (VIA FACTORY TOOL)==

Notes: The Automatic install performs the following:

•installs the AOSP and the Firmware, gets device configuration from the Idrive AdminCenter (IP address, serial number etc.);

•tests triggering on the yellow, blue and green wires;

•provides lens focus mode so both lenses can be focused and glued.

!For this step, DO NOT use Developer Mode!

1. Click on the Factory - New Devices - Auto button

[[File:aa.png]]

2. Scan using the bar code scanner the Bar Code label present on the Main board and press Enter.

[[File:b.png]]

If no bar code scanner is available, manually type the serial number from the bar code label into the serial number input field.

3. Click on the Auto Install button and the Automatic Install window will open.

[[File:c.png]]

If the SN have already been introduced (device has already passed through one or more programming steps), a warning message will be displayed asking if you want to Continue or not. Continue if you want to reprogram the device, cancel if you introduced once more the SN by mistake.

4. In the Automatic Install window, Click on Start Installation button.

[[File:d.png]]

Installation and Configuration process steps:

1. Install AOSP

2. Install Firmware

3. Device Configuration

AI camera successfully installed and configured when all three buttons are GREEN.

[[File:c1.png]]

If all the steps are successfully completed, the program will enter into Lens Focus mode.

If any of these steps fails, the program will stop and give an error. Common errors are:

-Missing or corrupt storage SD card

-Serial cable not connected or incorrect polarity

-USB NIC or Internet connection missing

-I/O ports tester board missing

-Any assembly or incorrect component error

! In case any of the 3 steps fail (button will be red instead of green), there are two options (corrective actions):

1.Repeat the entire process by clicking on Start installation button in the Automatic Install window and the AOSP installation, Firmware installation and Device Configuration will be redone automatically.

2.Repeat manually only that specific step that failed:

a) Click on Factory - New Devices – Manual;

[[File:c2.png]]

b) Scan barcode

c) Depending on the step that failed, click either on Install Aosp button -> Start installation, either on Install Firmware buttonStart installation, either on Device Config – AC Sync – Lens Focus button -> Start configuration.

[[File:e.png]]

In case that the first step failed (Install Aosp), recommended would be to repeat automatically the process by clicking on Start installation button in the Automatic Install window.

=Lens Focus=

1. Select "Inside Camera" Tab and Focus the “Driver side” Lens (“Driver side” is the side containing the Processor).

[[File:f.png]]

The focal length for the inside camera should be ~1.5 meters

2. Select "Outside camera" tab and Focus the “Road side” Lens (“Road side” is the side containing the Power Connector).

[[File:g.png]]

Focus using the provided Idrive Focus Chart. Distance to chart can be 3,6,9 feet but the farther the better.

Optional: Use zoom mode (Show zoom button) to ensure accurate focus.

In Both Cameras tab, you can visualize both “Driver side” and “Road side” cameras on the screen (the screen will be splitted in two).

3. If images are focused and clear (the outside test text is accurate and readable), click on the "Lens Focus OK" button and the focus mode will close.

[[File:h.png]]

If one of the images or both images are not clear, or if the Streaming is not loading (“Loading…Please wait!” message is displayed), click on the "Lens Focus Not OK" and the factory tool will exit focus mode, so corrective actions can be taken.

! Corrective actions: Repeat manually the 3rd step: Factory - New Devices – Manual -> Scan barcode -> Device Config – AC Sync – Lens Focus -> Start Configuration

4. Once focused, fix each lens with a drop of super glue. Test the lenses after several minutes to ensure they have taken the glue and cannot be moved (it means the glue is dried).

5. Remove the device from the test fixture (programmer fixture).

6. Advance the device to Final Assembly step.

==FINAL ASSEMBLY AI CAMERA==

*Remove (by screwing) the screw nut from power supply connector on the Main board and set it aside.

[[File:1.jpg|290px|]]

*Connect speaker wire (red and black wire) into the J250 socket on the “Road” side of the Main Board.

[[File:2.png]]

*Assembly Main board with the “Driver” side up into the inferior case by gently pressing on Main board and by pulling the edges of the case.

[[File:3.png]]

*Tightens the screw nut removed in step 1 on the power supply connector (torque 0.2 Nm).

[[File:4.jpg]]

*Connect the wires into the sockets on “Driver” side of the Main board:

[[File:5.png]]

a.Connect 4G antenna – insert wire 1 in J6 socket on Main board;

[[File:5.1.png]]

b.Connect GPS antenna – insert wire 2 in J7 socket on Main board;

[[File:5.2.png]]

c.Connect Wi-Fi antenna – insert wire 3 in J5 socket on Main Board.

[[File:5.3.png]]

*Mount the Display module into the dedicated socket.

[[File:6.png]]

Remove the plastic protection foil from the display.

*Mount by screwing the superior case (use torque 0.3 Nm).

[[File:7.png]]

*Advance assembled AI cam to Final test process.

==FINAL TEST (VIA FACTORY TOOL)==

*Open Factory Tool -> Factory - New devices – Auto -> Event Test – Transfer and Play (event test window will open – see at point 7)

[[File:poza1.png]]

[[File:poza2.png]]

*Connect 5 assembled AI cameras to Switch boxes power supplies (Power and Ignition are OFF).

[[File:poza3.jpg|500px|]]

*Switch Power and Ignition ON -> AI cameras will start to boot (Idrive logo will be displayed).

[[File:poza4.jpg|400px|]]

[[File:poza5.png]]

In this phase, AI cameras connect to GPS and to network (2G/3G/4G). The operator must pay attention to the cameras screens to assure that connections are available, and that all the icons are displayed and there is no error code – See picture below.

[[File:poza6.png]]

*Trigger a SHOCK event by pulling (shaking) each AI camera backward and forward (once or twice)-> Message SHOCK will be displayed on the screen, moment when the camera starts recording the event.

[[File:poza7.jpg|400px|]]

*After triggering and recording the SHOCK event (display gets back to normal), Switch Ignition OFF for AI cameras.

In this phase, AI cameras connect to Wi-Fi and start transferring. A text with IGNITION OFF followed by CLOSING TRIGGERS, by CONNECTING WIFI and by TRANSFERING along with specific icons, will be displayed on the screen.

[[File:poza8.png]]

*In the event test window, click on Play for each of the AI camera in the Play events area -> the record of the SHOCK event will be played.

[[File:poza9.png]]

Verify the focus of both lenses (image clarity). If the image is clear, lens focus was done properly. If not, the camera must be put aside. Check also if GPS route was recorded.

*If lens focus OK and GPS route recorded -> Click on Label Printed – Print and print 2 labels. Close the window.

[[File:poza10.png]]

[[File:poza11.png|900px|]]

There will be displayed 2 messages: one for label print confirmation and one for beep confirmation.

If label was not printed, click NO and try again to reprint the label. Camera starts to beep only if label printed was confirmed. Once label print and beep confirmed, serial number text row turnes green. If there is no beep, it means that the camera has a problem with the speaker.

*Camera will shut down automatically (SHUTTING DOWN message will be displayed) -> Switch Power OFF and Unplug the camera.

[[File:poza12.jpg]]

*Apply one label on the bottom of the AI camera and one on the right side of the Final box.

[[File:poza13.jpg|500px|]]

[[File:poza14.jpg|500px|]]

*Put the AI camera into the Final box.

[[File:poza15.jpg|600px|]]

ISSUES:

*AI camera doesn’t boot (display is off): verify power circular connector if it’s properly soldered to the board.

If yes, AI camera has a problem with the display -> display needs to be replaced

If it’s not, manually redo the soldering of the connector.

*AI camera appear with red text in the event test window, click on View in the View Transfer Log and see what error occurred.

[[File:poza16.png]]

First, redo the final test (without another shock trigger). If camera didn’t pass second time either, try solutions below:

*Network error

verify if the 4G antenna connector is OK and properly inserted (visual inspection).

verify if the cable is properly soldered to the antenna.

If both above OK -> replace SIM card.

If one or both above are NOK, replace connector/replace cable/manually redo the soldering.

*GPS error

verify if the GPS antenna connector is OK and properly inserted (visual inspection)

verify if the cable is properly soldered to the antenna.

*Infinite loop = HW problem which requires a close HW verification.

*Lens focus NOK -> Disassemble the AI camera and replace entire gasket + lens holders + lens assembly.

*AI camera doesn’t beep = speaker problems -> verify if speaker connector is OK and if it’s properly inserted (visual inspection).

==Radu Notes==

The AI programmer is mandatory only one time when the board comes from China with the default chinese AOSP. Once the AOSP is overwritten with our AOSP, the programmer becomes optional.

You need a micro usb cable in order to connect camera to a computer usb port, a power source for AI camera and a computer with Windows 10 (preferable).

<br>

==Factory Tool Installation==

===Install Factory Tool===

Download and install the latest Factory Tool from Admin Center

<br>

===Firmware===

Firmware folder is auto-populated by the Factory Tool installer and should have the following structure:

- firmware.apk represents the current firmware version (40.0.55)

- updater.apk is a background application taking care about firmware and aosp upgrades / firmware crashes / background staffs. The current version is 1.0

- idrive_root is the place where we keep different files (neural networks, settings, etc)

- firmware.apk should be replaced every time when a new stable firmware is released. For example, if you have a new update.apk file, you can rename this file and copy it over firmware.apk. You have also to copy the same file over idrive_root/recovery.apk file

- The same mechanism should be used if we will upgrade updater.apk. That apk should also be copied over idrive_root/recovery_updater_app.apk.

- Any file from idrive_root folder is replaceable. In the future we can add / remove / replace any file from idrive_root

<br>

===Install the Android OS===

Download and install the latest AOSP from Admin Center

Unzip the ASOP archive

Copy the files to C:\Program Files (x86)\Idrive\Factory Tool 2.0\FactoryToolsAI\Aosp

Every time when a new AOSP is released, the files from Aosp folder should be replaced with the new files.

<br>

==FT Configuration==

Select Idrive Development > Settings (password > idrive2#dev)

<br>

====Disable Passwords ( if applicable)====

Click on Passwords tab and disable

<br>

====Config and Install====

Uncheck "Programmer enabled for AI devices"

[[File:ft_conf_install1.png|500px|]]

The Factory Tool is documented, but I don't have the documentation now 🙂 (Alexandra will send you all documents tomorrow morning)

However the process is very similar with X2. There are AI settings in Idrive Development->Settings->Config and Install (see below)

(DO NOT CHANGE the "sleep seconds" fields for AI devices only).

<br>

====Factory Tool Print Settings (Santa Barbara)====

[[File:GK420t_ft_print1.png|350px|]] [[File:GK420t_ft_print2.png|350px|]]

[[File:GK420t_ft_print3.png|500px|]]

<br>

<br>

==Idrive AI Labels Windows Configuration==

===Add the Printer===

Settings > printers

Add printer>

\\idr-x2-prog-1\Zdesigner GK420t

Click on printer and Manage > Printing preferences
Options> Darkness 25, Width 1.5" Height .5"

[[File:gk420t_settings1.png|500px|]]

<br>

=== GK420T Printer Configuration (Santa Barbara) ===

Install Zebra Setup Utilities (Not needed for Factory Tool)

[[File:zebra_pref1.jpg|300px|]] [[File:zebra_pref2.jpg|300px|]]

<br>

===Label supplies for GK420T printer in RMA area===

https://www.zpsstore.com/ShoppingCart.asp

https://www.barcodesinc.com

https://www.bradyid.com/en-us/family/cps-3053222 (In use in RMA Area)

Zebra Part #: 10011693

Label Size (WxH): 1.5" x 0.50"

Labels Per Roll: 9,420

Rolls Per Case: 4

Core Size: 3"

Outside Diameter: 8"Zebra Z-Ultimate 10011693

* NO perforation between label

Thermal Ribbon:

Zebra 5095 Performance Ribbon

https://www.barcodesinc.com/search.htm?search=05095GS06407&v=1

<br>

Manufacturing:AI Device Manufacturing and Programming Process

2020-03-24T10:59:17Z

Alexandra:

=AI Device Manufacturing and Programming=

==AUTOMATIC INSTALL AND CONFIGURATION (VIA FACTORY TOOL)==

Notes: The Automatic install performs the following:

•installs the AOSP and the Firmware, gets device configuration from the Idrive AdminCenter (IP address, serial number etc.);

•tests triggering on the yellow, blue and green wires;

•provides lens focus mode so both lenses can be focused and glued.

!For this step, DO NOT use Developer Mode!

1. Click on the Factory - New Devices - Auto button

[[File:aa.png]]

2. Scan using the bar code scanner the Bar Code label present on the Main board and press Enter.

[[File:b.png]]

If no bar code scanner is available, manually type the serial number from the bar code label into the serial number input field.

3. Click on the Auto Install button and the Automatic Install window will open.

[[File:c.png]]

If the SN have already been introduced (device has already passed through one or more programming steps), a warning message will be displayed asking if you want to Continue or not. Continue if you want to reprogram the device, cancel if you introduced once more the SN by mistake.

4. In the Automatic Install window, Click on Start Installation button.

[[File:d.png]]

Installation and Configuration process steps:

1. Install AOSP
2. Install Firmware
3. Device Configuration

AI camera successfully installed and configured when all three buttons are GREEN.

[[File:c1.png]]

If all the steps are successfully completed, the program will enter into Lens Focus mode.

If any of these steps fails, the program will stop and give an error. Common errors are:

Missing or corrupt storage SD card

Serial cable not connected or incorrect polarity

USB NIC or Internet connection missing

I/O ports tester board missing

Any assembly or incorrect component error

! In case any of the 3 steps fail (button will be red instead of green), there are two options (corrective actions):

1.Repeat the entire process by clicking on Start installation button in the Automatic Install window and the AOSP installation, Firmware installation and Device Configuration will be redone automatically.

2.Repeat manually only that specific step that failed:

a) Click on Factory - New Devices – Manual;

[[File:c2.png]]

b) Scan barcode

c) Depending on the step that failed, click either on Install Aosp button -> Start installation, either on Install Firmware buttonStart installation, either on Device Config – AC Sync – Lens Focus button -> Start configuration.

[[File:e.png]]

In case that the first step failed (Install Aosp), recommended would be to repeat automatically the process by clicking on Start installation button in the Automatic Install window.

=Lens Focus=

1. Select "Inside Camera" Tab and Focus the “Driver side” Lens (“Driver side” is the side containing the Processor).

[[File:f.png]]

The focal length for the inside camera should be ~1.5 meters

2. Select "Outside camera" tab and Focus the “Road side” Lens (“Road side” is the side containing the Power Connector).

[[File:g.png]]

Focus using the provided Idrive Focus Chart. Distance to chart can be 3,6,9 feet but the farther the better.

Optional: Use zoom mode (Show zoom button) to ensure accurate focus.

In Both Cameras tab, you can visualize both “Driver side” and “Road side” cameras on the screen (the screen will be splitted in two).

3. If images are focused and clear (the outside test text is accurate and readable), click on the "Lens Focus OK" button and the focus mode will close.

[[File:h.png]]

If one of the images or both images are not clear, or if the Streaming is not loading (“Loading…Please wait!” message is displayed), click on the "Lens Focus Not OK" and the factory tool will exit focus mode, so corrective actions can be taken.

! Corrective actions: Repeat manually the 3rd step: Factory - New Devices – Manual -> Scan barcode -> Device Config – AC Sync – Lens Focus -> Start Configuration

4. Once focused, fix each lens with a drop of super glue. Test the lenses after several minutes to ensure they have taken the glue and cannot be moved (it means the glue is dried).

5. Remove the device from the test fixture (programmer fixture).

6. Advance the device to Final Assembly step.

==FINAL ASSEMBLY AI CAMERA==

*Remove (by screwing) the screw nut from power supply connector on the Main board and set it aside.

[[File:1.jpg|290px|]]

*Connect speaker wire (red and black wire) into the J250 socket on the “Road” side of the Main Board.

[[File:2.png]]

*Assembly Main board with the “Driver” side up into the inferior case by gently pressing on Main board and by pulling the edges of the case.

[[File:3.png]]

*Tightens the screw nut removed in step 1 on the power supply connector (torque 0.2 Nm).

[[File:4.jpg]]

*Connect the wires into the sockets on “Driver” side of the Main board:

[[File:5.png]]

a.Connect 4G antenna – insert wire 1 in J6 socket on Main board;

[[File:5.1.png]]

b.Connect GPS antenna – insert wire 2 in J7 socket on Main board;

[[File:5.2.png]]

c.Connect Wi-Fi antenna – insert wire 3 in J5 socket on Main Board.

[[File:5.3.png]]

*Mount the Display module into the dedicated socket.

[[File:6.png]]

Remove the plastic protection foil from the display.

*Mount by screwing the superior case (use torque 0.3 Nm).

[[File:7.png]]

*Advance assembled AI cam to Final test process.

==FINAL TEST (VIA FACTORY TOOL)==

*Open Factory Tool -> Factory - New devices – Auto -> Event Test – Transfer and Play (event test window will open – see at point 7)

[[File:poza1.png]]

[[File:poza2.png]]

*Connect 5 assembled AI cameras to Switch boxes power supplies (Power and Ignition are OFF).

[[File:poza3.jpg|500px|]]

*Switch Power and Ignition ON -> AI cameras will start to boot (Idrive logo will be displayed).

[[File:poza4.jpg|400px|]]

[[File:poza5.png]]

In this phase, AI cameras connect to GPS and to network (2G/3G/4G). The operator must pay attention to the cameras screens to assure that connections are available, and that all the icons are displayed and there is no error code – See picture below.

[[File:poza6.png]]

*Trigger a SHOCK event by pulling (shaking) each AI camera backward and forward (once or twice)-> Message SHOCK will be displayed on the screen, moment when the camera starts recording the event.

[[File:poza7.jpg|400px|]]

*After triggering and recording the SHOCK event (display gets back to normal), Switch Ignition OFF for AI cameras.

In this phase, AI cameras connect to Wi-Fi and start transferring. A text with IGNITION OFF followed by CLOSING TRIGGERS, by CONNECTING WIFI and by TRANSFERING along with specific icons, will be displayed on the screen.

[[File:poza8.png]]

*In the event test window, click on Play for each of the AI camera in the Play events area -> the record of the SHOCK event will be played.

[[File:poza9.png]]

Verify the focus of both lenses (image clarity). If the image is clear, lens focus was done properly. If not, the camera must be put aside. Check also if GPS route was recorded.

*If lens focus OK and GPS route recorded -> Click on Label Printed – Print and print 2 labels. Close the window.

[[File:poza10.png]]

[[File:poza11.png|900px|]]

There will be displayed 2 messages: one for label print confirmation and one for beep confirmation.

If label was not printed, click NO and try again to reprint the label. Camera starts to beep only if label printed was confirmed. Once label print and beep confirmed, serial number text row turnes green. If there is no beep, it means that the camera has a problem with the speaker.

*Camera will shut down automatically (SHUTTING DOWN message will be displayed) -> Switch Power OFF and Unplug the camera.

[[File:poza12.jpg]]

*Apply one label on the bottom of the AI camera and one on the right side of the Final box.

[[File:poza13.jpg|500px|]]

[[File:poza14.jpg|500px|]]

*Put the AI camera into the Final box.

[[File:poza15.jpg|600px|]]

ISSUES:

*AI camera doesn’t boot (display is off): verify power circular connector if it’s properly soldered to the board.

If yes, AI camera has a problem with the display -> display needs to be replaced

If it’s not, manually redo the soldering of the connector.

*AI camera appear with red text in the event test window, click on View in the View Transfer Log and see what error occurred.

[[File:poza16.png]]

First, redo the final test (without another shock trigger). If camera didn’t pass second time either, try solutions below:

*Network error

verify if the 4G antenna connector is OK and properly inserted (visual inspection).

verify if the cable is properly soldered to the antenna.

If both above OK -> replace SIM card.

If one or both above are NOK, replace connector/replace cable/manually redo the soldering.

*GPS error

verify if the GPS antenna connector is OK and properly inserted (visual inspection)

verify if the cable is properly soldered to the antenna.

*Infinite loop = HW problem which requires a close HW verification.

*Lens focus NOK -> Disassemble the AI camera and replace entire gasket + lens holders + lens assembly.

*AI camera doesn’t beep = speaker problems -> verify if speaker connector is OK and if it’s properly inserted (visual inspection).

==Radu Notes==

The AI programmer is mandatory only one time when the board comes from China with the default chinese AOSP. Once the AOSP is overwritten with our AOSP, the programmer becomes optional.

You need a micro usb cable in order to connect camera to a computer usb port, a power source for AI camera and a computer with Windows 10 (preferable).

<br>

==Factory Tool Installation==

===Install Factory Tool===

Download and install the latest Factory Tool from Admin Center

<br>

===Firmware===

Firmware folder is auto-populated by the Factory Tool installer and should have the following structure:

- firmware.apk represents the current firmware version (40.0.55)

- updater.apk is a background application taking care about firmware and aosp upgrades / firmware crashes / background staffs. The current version is 1.0

- idrive_root is the place where we keep different files (neural networks, settings, etc)

- firmware.apk should be replaced every time when a new stable firmware is released. For example, if you have a new update.apk file, you can rename this file and copy it over firmware.apk. You have also to copy the same file over idrive_root/recovery.apk file

- The same mechanism should be used if we will upgrade updater.apk. That apk should also be copied over idrive_root/recovery_updater_app.apk.

- Any file from idrive_root folder is replaceable. In the future we can add / remove / replace any file from idrive_root

<br>

===Install the Android OS===

Download and install the latest AOSP from Admin Center

Unzip the ASOP archive

Copy the files to C:\Program Files (x86)\Idrive\Factory Tool 2.0\FactoryToolsAI\Aosp

Every time when a new AOSP is released, the files from Aosp folder should be replaced with the new files.

<br>

==FT Configuration==

Select Idrive Development > Settings (password > idrive2#dev)

<br>

====Disable Passwords ( if applicable)====

Click on Passwords tab and disable

<br>

====Config and Install====

Uncheck "Programmer enabled for AI devices"

[[File:ft_conf_install1.png|500px|]]

The Factory Tool is documented, but I don't have the documentation now 🙂 (Alexandra will send you all documents tomorrow morning)

However the process is very similar with X2. There are AI settings in Idrive Development->Settings->Config and Install (see below)

(DO NOT CHANGE the "sleep seconds" fields for AI devices only).

<br>

====Factory Tool Print Settings (Santa Barbara)====

[[File:GK420t_ft_print1.png|350px|]] [[File:GK420t_ft_print2.png|350px|]]

[[File:GK420t_ft_print3.png|500px|]]

<br>

<br>

==Idrive AI Labels Windows Configuration==

===Add the Printer===

Settings > printers

Add printer>

\\idr-x2-prog-1\Zdesigner GK420t

Click on printer and Manage > Printing preferences
Options> Darkness 25, Width 1.5" Height .5"

[[File:gk420t_settings1.png|500px|]]

<br>

=== GK420T Printer Configuration (Santa Barbara) ===

Install Zebra Setup Utilities (Not needed for Factory Tool)

[[File:zebra_pref1.jpg|300px|]] [[File:zebra_pref2.jpg|300px|]]

<br>

===Label supplies for GK420T printer in RMA area===

https://www.zpsstore.com/ShoppingCart.asp

https://www.barcodesinc.com

https://www.bradyid.com/en-us/family/cps-3053222 (In use in RMA Area)

Zebra Part #: 10011693

Label Size (WxH): 1.5" x 0.50"

Labels Per Roll: 9,420

Rolls Per Case: 4

Core Size: 3"

Outside Diameter: 8"Zebra Z-Ultimate 10011693

* NO perforation between label

Thermal Ribbon:

Zebra 5095 Performance Ribbon

https://www.barcodesinc.com/search.htm?search=05095GS06407&v=1

<br>

Manufacturing:AI Device Manufacturing and Programming Process

2020-03-24T10:56:33Z

Alexandra:

=AI Device Manufacturing and Programming=

==AUTOMATIC INSTALL AND CONFIGURATION (VIA FACTORY TOOL)==

Notes: The Automatic install performs the following:

•installs the AOSP and the Firmware, gets device configuration from the Idrive AdminCenter (IP address, serial number etc.);

•tests triggering on the yellow, blue and green wires;

•provides lens focus mode so both lenses can be focused and glued.

!For this step, DO NOT use Developer Mode!

1. Click on the Factory - New Devices - Auto button

[[File:aa.png]]

2. Scan using the bar code scanner the Bar Code label present on the Main board and press Enter.

[[File:b.png]]

If no bar code scanner is available, manually type the serial number from the bar code label into the serial number input field.

3. Click on the Auto Install button and the Automatic Install window will open.

[[File:c.png]]

If the SN have already been introduced (device has already passed through one or more programming steps), a warning message will be displayed asking if you want to Continue or not. Continue if you want to reprogram the device, cancel if you introduced once more the SN by mistake.

4. In the Automatic Install window, Click on Start Installation button.

[[File:d.png]]

Installation and Configuration process steps:

1.Install AOSP
2.Install Firmware
3.Device Configuration

AI camera successfully installed and configured when all three buttons are GREEN.

[[File:c1.png]]

If all the steps are successfully completed, the program will enter into Lens Focus mode.

If any of these steps fails, the program will stop and give an error. Common errors are:

Missing or corrupt storage SD card
Serial cable not connected or incorrect polarity
USB NIC or Internet connection missing
I/O ports tester board missing
Any assembly or incorrect component error

! In case any of the 3 steps fail (button will be red instead of green), there are two options (corrective actions):

1.Repeat the entire process by clicking on Start installation button in the Automatic Install window and the AOSP installation, Firmware installation and Device Configuration will be redone automatically.

2.Repeat manually only that specific step that failed:

a) Click on Factory - New Devices – Manual;

[[File:c2.png]]

b) Scan barcode

c) Depending on the step that failed, click either on Install Aosp button -> Start installation, either on Install Firmware buttonStart installation, either on Device Config – AC Sync – Lens Focus button -> Start configuration.

[[File:e.png]]

In case that the first step failed (Install Aosp), recommended would be to repeat automatically the process by clicking on Start installation button in the Automatic Install window.

=Lens Focus=

1. Select "Inside Camera" Tab and Focus the “Driver side” Lens (“Driver side” is the side containing the Processor).

[[File:f.png]]

The focal length for the inside camera should be ~1.5 meters

2. Select "Outside camera" tab and Focus the “Road side” Lens (“Road side” is the side containing the Power Connector).

[[File:g.png]]

Focus using the provided Idrive Focus Chart. Distance to chart can be 3,6,9 feet but the farther the better.

Optional: Use zoom mode (Show zoom button) to ensure accurate focus.

In Both Cameras tab, you can visualize both “Driver side” and “Road side” cameras on the screen (the screen will be splitted in two).

3. If images are focused and clear (the outside test text is accurate and readable), click on the "Lens Focus OK" button and the focus mode will close.

[[File:h.png]]

If one of the images or both images are not clear, or if the Streaming is not loading (“Loading…Please wait!” message is displayed), click on the "Lens Focus Not OK" and the factory tool will exit focus mode, so corrective actions can be taken.

! Corrective actions: Repeat manually the 3rd step: Factory - New Devices – Manual -> Scan barcode -> Device Config – AC Sync – Lens Focus -> Start Configuration

4. Once focused, fix each lens with a drop of super glue. Test the lenses after several minutes to ensure they have taken the glue and cannot be moved (it means the glue is dried).

5. Remove the device from the test fixture (programmer fixture).

6. Advance the device to Final Assembly step.

==FINAL ASSEMBLY AI CAMERA==

*Remove (by screwing) the screw nut from power supply connector on the Main board and set it aside.

[[File:1.jpg|290px|]]

*Connect speaker wire (red and black wire) into the J250 socket on the “Road” side of the Main Board.

[[File:2.png]]

*Assembly Main board with the “Driver” side up into the inferior case by gently pressing on Main board and by pulling the edges of the case.

[[File:3.png]]

*Tightens the screw nut removed in step 1 on the power supply connector (torque 0.2 Nm).

[[File:4.jpg]]

*Connect the wires into the sockets on “Driver” side of the Main board:

[[File:5.png]]

a.Connect 4G antenna – insert wire 1 in J6 socket on Main board;

[[File:5.1.png]]

b.Connect GPS antenna – insert wire 2 in J7 socket on Main board;

[[File:5.2.png]]

c.Connect Wi-Fi antenna – insert wire 3 in J5 socket on Main Board.

[[File:5.3.png]]

*Mount the Display module into the dedicated socket.

[[File:6.png]]

Remove the plastic protection foil from the display.

*Mount by screwing the superior case (use torque 0.3 Nm).

[[File:7.png]]

*Advance assembled AI cam to Final test process.

==FINAL TEST (VIA FACTORY TOOL)==

*Open Factory Tool -> Factory - New devices – Auto -> Event Test – Transfer and Play (event test window will open – see at point 7)

[[File:poza1.png]]

[[File:poza2.png]]

*Connect 5 assembled AI cameras to Switch boxes power supplies (Power and Ignition are OFF).

[[File:poza3.jpg|500px|]]

*Switch Power and Ignition ON -> AI cameras will start to boot (Idrive logo will be displayed).

[[File:poza4.jpg|400px|]]

[[File:poza5.png]]

In this phase, AI cameras connect to GPS and to network (2G/3G/4G). The operator must pay attention to the cameras screens to assure that connections are available, and that all the icons are displayed and there is no error code – See picture below.

[[File:poza6.png]]

*Trigger a SHOCK event by pulling (shaking) each AI camera backward and forward (once or twice)-> Message SHOCK will be displayed on the screen, moment when the camera starts recording the event.

[[File:poza7.jpg|400px|]]

*After triggering and recording the SHOCK event (display gets back to normal), Switch Ignition OFF for AI cameras.

In this phase, AI cameras connect to Wi-Fi and start transferring. A text with IGNITION OFF followed by CLOSING TRIGGERS, by CONNECTING WIFI and by TRANSFERING along with specific icons, will be displayed on the screen.

[[File:poza8.png]]

*In the event test window, click on Play for each of the AI camera in the Play events area -> the record of the SHOCK event will be played.

[[File:poza9.png]]

Verify the focus of both lenses (image clarity). If the image is clear, lens focus was done properly. If not, the camera must be put aside. Check also if GPS route was recorded.

*If lens focus OK and GPS route recorded -> Click on Label Printed – Print and print 2 labels. Close the window.

[[File:poza10.png]]

[[File:poza11.png|900px|]]

There will be displayed 2 messages: one for label print confirmation and one for beep confirmation.

If label was not printed, click NO and try again to reprint the label. Camera starts to beep only if label printed was confirmed. Once label print and beep confirmed, serial number text row turnes green. If there is no beep, it means that the camera has a problem with the speaker.

*Camera will shut down automatically (SHUTTING DOWN message will be displayed) -> Switch Power OFF and Unplug the camera.

[[File:poza12.jpg]]

*Apply one label on the bottom of the AI camera and one on the right side of the Final box.

[[File:poza13.jpg|500px|]]

[[File:poza14.jpg|500px|]]

*Put the AI camera into the Final box.

[[File:poza15.jpg|600px|]]

ISSUES:

*AI camera doesn’t boot (display is off): verify power circular connector if it’s properly soldered to the board.

If yes, AI camera has a problem with the display -> display needs to be replaced

If it’s not, manually redo the soldering of the connector.

*AI camera appear with red text in the event test window, click on View in the View Transfer Log and see what error occurred.

[[File:poza16.png]]

First, redo the final test (without another shock trigger). If camera didn’t pass second time either, try solutions below:

*Network error

verify if the 4G antenna connector is OK and properly inserted (visual inspection).

verify if the cable is properly soldered to the antenna.

If both above OK -> replace SIM card.

If one or both above are NOK, replace connector/replace cable/manually redo the soldering.

*GPS error

verify if the GPS antenna connector is OK and properly inserted (visual inspection)

verify if the cable is properly soldered to the antenna.

*Infinite loop = HW problem which requires a close HW verification.

*Lens focus NOK -> Disassemble the AI camera and replace entire gasket + lens holders + lens assembly.

*AI camera doesn’t beep = speaker problems -> verify if speaker connector is OK and if it’s properly inserted (visual inspection).

==Radu Notes==

The AI programmer is mandatory only one time when the board comes from China with the default chinese AOSP. Once the AOSP is overwritten with our AOSP, the programmer becomes optional.

You need a micro usb cable in order to connect camera to a computer usb port, a power source for AI camera and a computer with Windows 10 (preferable).

<br>

==Factory Tool Installation==

===Install Factory Tool===

Download and install the latest Factory Tool from Admin Center

<br>

===Firmware===

Firmware folder is auto-populated by the Factory Tool installer and should have the following structure:

- firmware.apk represents the current firmware version (40.0.55)

- updater.apk is a background application taking care about firmware and aosp upgrades / firmware crashes / background staffs. The current version is 1.0

- idrive_root is the place where we keep different files (neural networks, settings, etc)

- firmware.apk should be replaced every time when a new stable firmware is released. For example, if you have a new update.apk file, you can rename this file and copy it over firmware.apk. You have also to copy the same file over idrive_root/recovery.apk file

- The same mechanism should be used if we will upgrade updater.apk. That apk should also be copied over idrive_root/recovery_updater_app.apk.

- Any file from idrive_root folder is replaceable. In the future we can add / remove / replace any file from idrive_root

<br>

===Install the Android OS===

Download and install the latest AOSP from Admin Center

Unzip the ASOP archive

Copy the files to C:\Program Files (x86)\Idrive\Factory Tool 2.0\FactoryToolsAI\Aosp

Every time when a new AOSP is released, the files from Aosp folder should be replaced with the new files.

<br>

==FT Configuration==

Select Idrive Development > Settings (password > idrive2#dev)

<br>

====Disable Passwords ( if applicable)====

Click on Passwords tab and disable

<br>

====Config and Install====

Uncheck "Programmer enabled for AI devices"

[[File:ft_conf_install1.png|500px|]]

The Factory Tool is documented, but I don't have the documentation now 🙂 (Alexandra will send you all documents tomorrow morning)

However the process is very similar with X2. There are AI settings in Idrive Development->Settings->Config and Install (see below)

(DO NOT CHANGE the "sleep seconds" fields for AI devices only).

<br>

====Factory Tool Print Settings (Santa Barbara)====

[[File:GK420t_ft_print1.png|350px|]] [[File:GK420t_ft_print2.png|350px|]]

[[File:GK420t_ft_print3.png|500px|]]

<br>

<br>

==Idrive AI Labels Windows Configuration==

===Add the Printer===

Settings > printers

Add printer>

\\idr-x2-prog-1\Zdesigner GK420t

Click on printer and Manage > Printing preferences
Options> Darkness 25, Width 1.5" Height .5"

[[File:gk420t_settings1.png|500px|]]

<br>

=== GK420T Printer Configuration (Santa Barbara) ===

Install Zebra Setup Utilities (Not needed for Factory Tool)

[[File:zebra_pref1.jpg|300px|]] [[File:zebra_pref2.jpg|300px|]]

<br>

===Label supplies for GK420T printer in RMA area===

https://www.zpsstore.com/ShoppingCart.asp

https://www.barcodesinc.com

https://www.bradyid.com/en-us/family/cps-3053222 (In use in RMA Area)

Zebra Part #: 10011693

Label Size (WxH): 1.5" x 0.50"

Labels Per Roll: 9,420

Rolls Per Case: 4

Core Size: 3"

Outside Diameter: 8"Zebra Z-Ultimate 10011693

* NO perforation between label

Thermal Ribbon:

Zebra 5095 Performance Ribbon

https://www.barcodesinc.com/search.htm?search=05095GS06407&v=1

<br>

Manufacturing:AI Device Manufacturing and Programming Process

2020-03-24T10:55:03Z

Alexandra:

=AI Device Manufacturing and Programming=

==AUTOMATIC INSTALL AND CONFIGURATION (VIA FACTORY TOOL)==

Notes: The Automatic install performs the following:

•installs the AOSP and the Firmware, gets device configuration from the Idrive AdminCenter (IP address, serial number etc.);

•tests triggering on the yellow, blue and green wires;

•provides lens focus mode so both lenses can be focused and glued.

!For this step, DO NOT use Developer Mode!

1. Click on the Factory - New Devices - Auto button

[[File:aa.png]]

2. Scan using the bar code scanner the Bar Code label present on the Main board and press Enter.

[[File:b.png]]

If no bar code scanner is available, manually type the serial number from the bar code label into the serial number input field.

3. Click on the Auto Install button and the Automatic Install window will open.

[[File:c.png]]

If the SN have already been introduced (device has already passed through one or more programming steps), a warning message will be displayed asking if you want to Continue or not. Continue if you want to reprogram the device, cancel if you introduced once more the SN by mistake.

4. In the Automatic Install window, Click on Start Installation button.

[[File:d.png]]

Installation and Configuration process steps:

1.Install AOSP
2.Install Firmware
3.Device Configuration

AI camera successfully installed and configured when all three buttons are GREEN.

[[File:c1.png]]

If all the steps are successfully completed, the program will enter into Lens Focus mode.

If any of these steps fails, the program will stop and give an error. Common errors are:

Missing or corrupt storage SD card
Serial cable not connected or incorrect polarity
USB NIC or Internet connection missing
I/O ports tester board missing
Any assembly or incorrect component error

! In case any of the 3 steps fail (button will be red instead of green), there are two options (corrective actions):

1.Repeat the entire process by clicking on Start installation button in the Automatic Install window and the AOSP installation, Firmware installation and Device Configuration will be redone automatically.

2.Repeat manually only that specific step that failed:

a) Click on Factory - New Devices – Manual;

[[File:c2.png]]

b) Scan barcode

c) Depending on the step that failed, click either on Install Aosp button -> Start installation, either on Install Firmware buttonStart installation, either on Device Config – AC Sync – Lens Focus button -> Start configuration.

In case that the first step failed (Install Aosp), recommended would be to repeat automatically the process by clicking on Start installation button in the Automatic Install window.

[[File:e.png]]

=Lens Focus=

1. Select "Inside Camera" Tab and Focus the “Driver side” Lens (“Driver side” is the side containing the Processor).

[[File:f.png]]

The focal length for the inside camera should be ~1.5 meters

2. Select "Outside camera" tab and Focus the “Road side” Lens (“Road side” is the side containing the Power Connector).

[[File:g.png]]

Focus using the provided Idrive Focus Chart. Distance to chart can be 3,6,9 feet but the farther the better.

Optional: Use zoom mode (Show zoom button) to ensure accurate focus.

In Both Cameras tab, you can visualize both “Driver side” and “Road side” cameras on the screen (the screen will be splitted in two).

3. If images are focused and clear (the outside test text is accurate and readable), click on the "Lens Focus OK" button and the focus mode will close.

[[File:h.png]]

If one of the images or both images are not clear, or if the Streaming is not loading (“Loading…Please wait!” message is displayed), click on the "Lens Focus Not OK" and the factory tool will exit focus mode, so corrective actions can be taken.

! Corrective actions: Repeat manually the 3rd step: Factory - New Devices – Manual -> Scan barcode -> Device Config – AC Sync – Lens Focus -> Start Configuration

4. Once focused, fix each lens with a drop of super glue. Test the lenses after several minutes to ensure they have taken the glue and cannot be moved (it means the glue is dried).

5. Remove the device from the test fixture (programmer fixture).

6. Advance the device to Final Assembly step.

==FINAL ASSEMBLY AI CAMERA==

*Remove (by screwing) the screw nut from power supply connector on the Main board and set it aside.

[[File:1.jpg|290px|]]

*Connect speaker wire (red and black wire) into the J250 socket on the “Road” side of the Main Board.

[[File:2.png]]

*Assembly Main board with the “Driver” side up into the inferior case by gently pressing on Main board and by pulling the edges of the case.

[[File:3.png]]

*Tightens the screw nut removed in step 1 on the power supply connector (torque 0.2 Nm).

[[File:4.jpg]]

*Connect the wires into the sockets on “Driver” side of the Main board:

[[File:5.png]]

a.Connect 4G antenna – insert wire 1 in J6 socket on Main board;

[[File:5.1.png]]

b.Connect GPS antenna – insert wire 2 in J7 socket on Main board;

[[File:5.2.png]]

c.Connect Wi-Fi antenna – insert wire 3 in J5 socket on Main Board.

[[File:5.3.png]]

*Mount the Display module into the dedicated socket.

[[File:6.png]]

Remove the plastic protection foil from the display.

*Mount by screwing the superior case (use torque 0.3 Nm).

[[File:7.png]]

*Advance assembled AI cam to Final test process.

==FINAL TEST (VIA FACTORY TOOL)==

*Open Factory Tool -> Factory - New devices – Auto -> Event Test – Transfer and Play (event test window will open – see at point 7)

[[File:poza1.png]]

[[File:poza2.png]]

*Connect 5 assembled AI cameras to Switch boxes power supplies (Power and Ignition are OFF).

[[File:poza3.jpg|500px|]]

*Switch Power and Ignition ON -> AI cameras will start to boot (Idrive logo will be displayed).

[[File:poza4.jpg|400px|]]

[[File:poza5.png]]

In this phase, AI cameras connect to GPS and to network (2G/3G/4G). The operator must pay attention to the cameras screens to assure that connections are available, and that all the icons are displayed and there is no error code – See picture below.

[[File:poza6.png]]

*Trigger a SHOCK event by pulling (shaking) each AI camera backward and forward (once or twice)-> Message SHOCK will be displayed on the screen, moment when the camera starts recording the event.

[[File:poza7.jpg|400px|]]

*After triggering and recording the SHOCK event (display gets back to normal), Switch Ignition OFF for AI cameras.

In this phase, AI cameras connect to Wi-Fi and start transferring. A text with IGNITION OFF followed by CLOSING TRIGGERS, by CONNECTING WIFI and by TRANSFERING along with specific icons, will be displayed on the screen.

[[File:poza8.png]]

*In the event test window, click on Play for each of the AI camera in the Play events area -> the record of the SHOCK event will be played.

[[File:poza9.png]]

Verify the focus of both lenses (image clarity). If the image is clear, lens focus was done properly. If not, the camera must be put aside. Check also if GPS route was recorded.

*If lens focus OK and GPS route recorded -> Click on Label Printed – Print and print 2 labels. Close the window.

[[File:poza10.png]]

[[File:poza11.png|900px|]]

There will be displayed 2 messages: one for label print confirmation and one for beep confirmation.

If label was not printed, click NO and try again to reprint the label. Camera starts to beep only if label printed was confirmed. Once label print and beep confirmed, serial number text row turnes green. If there is no beep, it means that the camera has a problem with the speaker.

*Camera will shut down automatically (SHUTTING DOWN message will be displayed) -> Switch Power OFF and Unplug the camera.

[[File:poza12.jpg]]

*Apply one label on the bottom of the AI camera and one on the right side of the Final box.

[[File:poza13.jpg|500px|]]

[[File:poza14.jpg|500px|]]

*Put the AI camera into the Final box.

[[File:poza15.jpg|600px|]]

ISSUES:

*AI camera doesn’t boot (display is off): verify power circular connector if it’s properly soldered to the board.

If yes, AI camera has a problem with the display -> display needs to be replaced

If it’s not, manually redo the soldering of the connector.

*AI camera appear with red text in the event test window, click on View in the View Transfer Log and see what error occurred.

[[File:poza16.png]]

First, redo the final test (without another shock trigger). If camera didn’t pass second time either, try solutions below:

*Network error

verify if the 4G antenna connector is OK and properly inserted (visual inspection).

verify if the cable is properly soldered to the antenna.

If both above OK -> replace SIM card.

If one or both above are NOK, replace connector/replace cable/manually redo the soldering.

*GPS error

verify if the GPS antenna connector is OK and properly inserted (visual inspection)

verify if the cable is properly soldered to the antenna.

*Infinite loop = HW problem which requires a close HW verification.

*Lens focus NOK -> Disassemble the AI camera and replace entire gasket + lens holders + lens assembly.

*AI camera doesn’t beep = speaker problems -> verify if speaker connector is OK and if it’s properly inserted (visual inspection).

==Radu Notes==

The AI programmer is mandatory only one time when the board comes from China with the default chinese AOSP. Once the AOSP is overwritten with our AOSP, the programmer becomes optional.

You need a micro usb cable in order to connect camera to a computer usb port, a power source for AI camera and a computer with Windows 10 (preferable).

<br>

==Factory Tool Installation==

===Install Factory Tool===

Download and install the latest Factory Tool from Admin Center

<br>

===Firmware===

Firmware folder is auto-populated by the Factory Tool installer and should have the following structure:

- firmware.apk represents the current firmware version (40.0.55)

- updater.apk is a background application taking care about firmware and aosp upgrades / firmware crashes / background staffs. The current version is 1.0

- idrive_root is the place where we keep different files (neural networks, settings, etc)

- firmware.apk should be replaced every time when a new stable firmware is released. For example, if you have a new update.apk file, you can rename this file and copy it over firmware.apk. You have also to copy the same file over idrive_root/recovery.apk file

- The same mechanism should be used if we will upgrade updater.apk. That apk should also be copied over idrive_root/recovery_updater_app.apk.

- Any file from idrive_root folder is replaceable. In the future we can add / remove / replace any file from idrive_root

<br>

===Install the Android OS===

Download and install the latest AOSP from Admin Center

Unzip the ASOP archive

Copy the files to C:\Program Files (x86)\Idrive\Factory Tool 2.0\FactoryToolsAI\Aosp

Every time when a new AOSP is released, the files from Aosp folder should be replaced with the new files.

<br>

==FT Configuration==

Select Idrive Development > Settings (password > idrive2#dev)

<br>

====Disable Passwords ( if applicable)====

Click on Passwords tab and disable

<br>

====Config and Install====

Uncheck "Programmer enabled for AI devices"

[[File:ft_conf_install1.png|500px|]]

The Factory Tool is documented, but I don't have the documentation now 🙂 (Alexandra will send you all documents tomorrow morning)

However the process is very similar with X2. There are AI settings in Idrive Development->Settings->Config and Install (see below)

(DO NOT CHANGE the "sleep seconds" fields for AI devices only).

<br>

====Factory Tool Print Settings (Santa Barbara)====

[[File:GK420t_ft_print1.png|350px|]] [[File:GK420t_ft_print2.png|350px|]]

[[File:GK420t_ft_print3.png|500px|]]

<br>

<br>

==Idrive AI Labels Windows Configuration==

===Add the Printer===

Settings > printers

Add printer>

\\idr-x2-prog-1\Zdesigner GK420t

Click on printer and Manage > Printing preferences
Options> Darkness 25, Width 1.5" Height .5"

[[File:gk420t_settings1.png|500px|]]

<br>

=== GK420T Printer Configuration (Santa Barbara) ===

Install Zebra Setup Utilities (Not needed for Factory Tool)

[[File:zebra_pref1.jpg|300px|]] [[File:zebra_pref2.jpg|300px|]]

<br>

===Label supplies for GK420T printer in RMA area===

https://www.zpsstore.com/ShoppingCart.asp

https://www.barcodesinc.com

https://www.bradyid.com/en-us/family/cps-3053222 (In use in RMA Area)

Zebra Part #: 10011693

Label Size (WxH): 1.5" x 0.50"

Labels Per Roll: 9,420

Rolls Per Case: 4

Core Size: 3"

Outside Diameter: 8"Zebra Z-Ultimate 10011693

* NO perforation between label

Thermal Ribbon:

Zebra 5095 Performance Ribbon

https://www.barcodesinc.com/search.htm?search=05095GS06407&v=1

<br>

File:Aa.png

2020-03-24T10:46:09Z

Alexandra:

File:H.png

2020-03-24T10:44:37Z

Alexandra:

File:G.png

2020-03-24T10:44:24Z

Alexandra:

File:F.png

2020-03-24T10:44:13Z

Alexandra:

File:E.png

2020-03-24T10:44:02Z

Alexandra:

File:D.png

2020-03-24T10:43:48Z

Alexandra:

File:C2.png

2020-03-24T10:43:36Z

Alexandra: