Difference between revisions of "Idrive X2 Notes"

From Idrive
Jump to navigation Jump to search
Line 1: Line 1:
 
==X2 Notes==
 
==X2 Notes==
  
===Beta Notes===
+
===Issues to resolve (bugs)from Beta testing===
  
From: Florin Pasol [mailto:florin@idriveglobal.com]
+
Plastics
Sent: Monday, December 22, 2014 1:23 AM
 
To: mark@idriveglobal.com
 
Cc: radu@idrive.pro; cornel@idriveglobal.com
 
Subject: RE: X2 Beta plan for customer locations
 
  
Hi Mark,
+
::*LED Lens filter issue, final case
  
We sent today the package for beta by Fedex(tracking no, 806147095240) containing the following:
+
WiFi
-          10 X2s, fully assembled, ready to go;
 
-          20 Driver IDs, ready to go;
 
-          X2 boards, wifi modules, antennas, cables so you can build another 6 cameras using the case samples.
 
  
All the cameras/boards are labeled with the proper S/N, programmed and configured using the following:
+
::* 5g configuration and fail over testing
-          IP Address:  192.168.240.x/16, Base station: 192.168.0.9;
 
-          Wi-Fi: the firmware will try to connect to SSID “bwifi” for 2.4Ghz and “bwifi5g”, WPA-2, pass: “idrive##”, for 5Ghz; depending of the availability of these networks the firmware will use as first priority 5Ghz. In this case will connect directly to “bwifi” slice there will be no 5Ghz APs;
 
  
Please let me know if you have any questions and concerns.
+
::* Will not connect to hidden SSID
  
Subject: X2 Beta plan for customer locations
+
===Beta Notes===
From: "Mark Findley" <mark@idriveglobal.com>
 
Date: Wed, December 17, 2014 8:28 pm
 
To: <support@idriveglobal.com>
 
 
Hi All,
 
 
X2 Beta Plan
 
 
Curt has identified 4 existing customers for participation in the X2 Beta program. They have been selected based on willingness to actively participate as well as for the vehicle types in their fleet.
 
X2 events require Control Center 3.0 in order to be viewed however it is impractical to upgrade the existing base station at the customer site as it would be disruptive to their existing operations.
 
 
 
Here is the plan I am recommending:
 
 
We will ship the customer a beta base station with 3.0 installed on it and 2 small hubs with cables. The Beta system can be installed alongside their existing base station with a Hub for the idrive wireless network and a hub for the internet connection so both connections can be shared and all that the customer will be need to supply is power. The Beta base station will have a different IP address and will share the existing Idrive Wireless network. The Beta X2 cameras will have this IP address in their configuration. No new WiFi to install, less for the customer to do, quicker path to obtaining results, less equipment.
 
 
Base Station Configuration (Small profile Dells purchased as Download Points):
 
Idrive Control Center 3.0
 
Base Station 192.168.0.9
 
Netmask 255.255.0.0
 
 
X2 Beta Cameras
 
IP Address 192.168.163.x (or something way out of range from the X1s)
 
Netmask 255.255.0.0
 
Idrive Server 192.168.0.9
 
WiFi - 2.4 GHz, G only (so as not to interfere with existing X1 devices) SSID bwifi
 
 
This will be the least inconvenient for the customers and will get us feedback about CC3.0 and the X2 more quickly. We can work on the 5.8Ghz (802.11an) separately.
 
 
Comments?
 
  
 +
IP for Beta Base Station is 192.168.0.9
  
 +
Cameras IP Address:  192.168.240.x/16
  
===Process notes===
+
Wi-Fi: the firmware will try to connect to SSID “bwifi” for 2.4Ghz and “bwifi5g”, WPA-2, pass: “idrive##”, for 5Ghz; depending of the availability of these networks the firmware will use as first priority 5Ghz. In this case will connect directly to “bwifi” slice there will be no 5Ghz APs;
From: Florin Pasol [mailto:florin@idriveglobal.com]
 
Sent: Monday, December 15, 2014 9:14 AM
 
To: mark@idriveglobal.com
 
Cc: radu@idriveglobal.com; cornel@idriveglobal.com
 
Subject: RE: Factory Tool 3.0 - Process docs
 
  
Hi Mark,
+
Beta Customers - Clark Pest, Gulfmark, Parsec, Storer
  
Here are my comments:
+
===Serial Numbers===
  
1.       regarding the X2 Process flow
+
breakdown of X2 serial numbers fields so that we can get information about the device by knowing the serial number.
 +
 +
^02^582^11^00001^
 +
 +
^02^ manufacturer location
  
:a.      both SD cards needs to be installed before “Main board initial programming”
+
:* 01 = EMLinQ,
  
:b.      for Secondary testing, we will use X6 programmer and the same process.
+
:* 02= Comet
  
2.      Serial numbers
+
:* 03 =?
 
+
:a.      Agree with your version and can be implemented starting with X2.
+
^582^ (58 is ASCII HEX for X + 2)= X2
 
 
3.      Comments from the movies
 
 
 
:a.      There is no need of 2 USB ports on computer, the programmer provides a hub for this and only one USB cable is used.
 
 
   
 
   
:b.      The SD cards could be formatted EXT4 during configuration OR NOT, this option is available under settings . However, this is a quick format, it will take less than 1min for 64GB card. Usually 64GB cards are coming formatted ExFAT which is not supported by Linux so at least in this case we need this option but I will suggest to use EXT4 for all storage cards(8GB-64Gb) is more safe – FAT can be easily corrupt. Also there is an open source Windows driver for ext3/4 that can be used to read these cards: http://www.ext2fsd.com/
+
^11^ Board revision level Rev 1.1
 
 
:c.      Show console - this can be disabled under settings.
 
 
 
:d.      02705xxxxxx – we will correct this.
 
 
 
4.      Driver ID
 
 
 
:a.      These are programmed one by one(30 seconds each) and also needs to be tested after final assemble – factory tool will be used for that and a custom USB to RS232 adapter provided by us. These devices will have an unique S/N  same as X1 or X2 which are used on shipping.  
 
 
   
 
   
:b.      No, the keys are not mated with Driver Id’s, any key can be used for one driver, they are unique.
+
^00001^ individual serial number
 
 
:c.      These are added one by one under shipping, based on quote – same process used now for X1.
 
 
 
5.      Fully Assembled X2
 
  
:a.      One of the accelerometer is triggering the events and the other one is tested by the Firmware - is used only to collect data.
 
  
:b.      For the accessory ports we will build a small test board that is connected on “Main board initial programming/Testing stage 1” and the Firmware will take care of the tests.
 
  
 
===Features===
 
===Features===

Revision as of 17:17, 15 January 2015

X2 Notes

Issues to resolve (bugs)from Beta testing

Plastics

  • LED Lens filter issue, final case

WiFi

  • 5g configuration and fail over testing
  • Will not connect to hidden SSID

Beta Notes

IP for Beta Base Station is 192.168.0.9

Cameras IP Address: 192.168.240.x/16

Wi-Fi: the firmware will try to connect to SSID “bwifi” for 2.4Ghz and “bwifi5g”, WPA-2, pass: “idrive##”, for 5Ghz; depending of the availability of these networks the firmware will use as first priority 5Ghz. In this case will connect directly to “bwifi” slice there will be no 5Ghz APs;

Beta Customers - Clark Pest, Gulfmark, Parsec, Storer

Serial Numbers

breakdown of X2 serial numbers fields so that we can get information about the device by knowing the serial number.

^02^582^11^00001^

^02^ manufacturer location

  • 01 = EMLinQ,
  • 02= Comet
  • 03 =?

^582^ (58 is ASCII HEX for X + 2)= X2

^11^ Board revision level Rev 1.1

^00001^ individual serial number


Features

Hi Mark,

Here is a list of X2 features available for Beta:

- HD image quality, 30 fps front camera / 15 fps rear camera;

- Better image quality, ultra wide angle - glass lenses front;

- Proprietary event files based on H264 video compression;

- Better nigh time events – more sensitive image sensors and new style IR LEDs providing more light;

- WIFI 802.11 b/g/n dual band, 2.4Ghz & 5Ghz – 10 times faster than X1

- 8 GB storage;

- Driver ID

Features we are working on:

- Continuous recording;

- Event type detection;

- GPS tracking - 3G module integration;