X2 Firmware Releases

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