Carman Scan Lite Diagnostic Tester
Alibaba.com offers 37 carman scan 1 products. About 62% of these are diagnostic tools, 35% are scanners. A wide variety of carman scan 1 options are available to you, such as engine analyzer, code reader. There are 34 carman scan 1 suppliers, mainly located in Asia. Jan 1, 2018 - Spatial multicriteria decision analysis. Spatial rough set. Spatial extension of fuzzy set theory. Ontologies for spatial analysis. Urban modeling.
The Carman Scan Lite is a high quality, premium brand, hand held, Asian vehicle diagnostic scan tester with the addition of European, American and Australian software.
Specification
- Compact hand held tester 256Mb built in memory
- LCD backlight 320 x 240 resolution 40 columns x 12 lines
- OBD-11, KWP-2000, SAE-J1587 Compatibility
- Canbus ready
- Internal battery .2hrs
Features
- Pictorial & text diagnostic socket location
- Large range and depth of software Korea, Asian, European, USA & Australian.
- Menu vehicle selection, auto ECU scan, General search
Scan Functions
- EMS, Airbag, ABS, Body control, Dashboard, Chassis, Comfort, Immobiliser, Diesel, etc
- Self diagnosis, fault code read, store and clear
- Live data display, digital, graphic, min & max & store
- Actuator test and activation
- Flight record
- Service light reset, warning light reset, Coding and adaptation
Software
- Near OE software for Hyundai / Kia
- Near OE level on Asian applications
- Additional software, European, USA, Australian
- Update via internet
- No time out software
- No software “catch up” charges
- 64bit Windows 7 & 8 PC Compatible
Software Pricing
(New purchases of this tester come with 24 months free software)
12 months Software | £ 395.00 |
24 months Software | £ 705.00 |
Existing owners of the Carman Scan Lite can update their software by visiting our Carman Scan Software Page.
Kit Contents
- Hand held Scan tester
- High quality metal carrying case
- Operating Manual
- Accessory leads, AC/DC power cable, upload lead, Cigar cable
Optional Items
Asian Cable Kit
Includes pre-OBD connection cables for all Asian applications, including:
- Hyundai / Mitsubishi Cable (12 pin)
- Kia / mazda Adapter (6 + 1 pin)
- Kia Adapter (20 pin blue)
- Daewoo / GM Adapter (12 pin)
- Ssangyong Adapter (14 pin)
- Ssangyong Adapter (20 pin)
- Toyota / Lexus Adapter (17 pin R)
- Toyota / Lexus Adapter (17 pin C)
- Samsung / Nissan Adapter (14 pin)
- Mitsubishi Cable (12 pin + 16 pin)
- Honda Adapter (3 pin)
- Honda Adapter (5 pin)
- Mazda C Adapter (17 pin)
- Subaru Adapter (9 pin)
P/No. : cscablekita
Multi-Gateway Cable
The latest Carman Scan Software (Version 980 onwards) contains new functionality that requires a new cable.
This new Multi-Gateway cable is required for communication on the following systems:
High Speed CAN
- Honda
- Volvo
Low Speed CAN
- Honda
Single Wire CAN
- GM/Opel/Holden
- Daewoo/Suzuki
- PSA
115k High Speed Serial
- BMW / Mini (04-07)
P/No. : nexmul
Question
What does (Sel: ) mean in Oracle's explain plan?
Answer
When reviewing an Oracle tkprof file or autotrace output from SQL*Plus, one might notice the string (Sel: <value>) after the operation DOMAIN INDEX.
The Sel: <value> represents the selectivity the optimizer was provided by the st_domain_stats type. This number is derived from the input envelope, the given operator and an execution plan chosen when the statement was parsed.
The following example demonstrates the output one would see using SQL*Plus and autotrace:
The value .162684 represents the selectivity calculated by the st_domain_stats type based upon the input envelope from the st_envintersects operator. The optimizer uses selectivity to represent the fraction of rows which are returned by the statement. The number of rows returned by the statement, 290 in above case, is the cardinality for the statement or predicate. Cardinality is simply calculated by multiplying the number of rows in the table by the selectivity -
178,321 parcels * (.162684/100) = 290 rows (rounded).
The selectivity value is also input used by the optimizer to calculate the cost of using an index compared to performing a full table scan. If a high selectivity is derived, then its very possible the cost of using the index is greater then the cost of performing the full table scan.
Potentially one might see other <values> for selectivity -
(Sel: Default - No Stats)
(Sel: Default - Undefined)
(Sel: 0)
If (Sel: Default - No stats) is reported it indicates there are no statistics for the spatial index. Once the statistics are captured using ArcCatalog, dbms_stats.gather_table_stats or dbms_stats.gather_index_stats the value for selectivity should then be reported.
If (Sel: Default - Undefined) is reported it may indicate that there was an error generating statistics, or that the operator has been disassociated from the statistical type, such as the st_envintersects operator.
In the above cases, when no statistics are present or are undefined, the optimizer uses default values for selectivity (1 percent) and a default cost (3). When the optimizer's default values are used, the indexes low cost becomes the likely access path. But, potentially the high selectivity (1 percent) may result in a very high cardinality and in turn impact the optimizer in choosing an optimal join plan.
When (Sel: 0) is reported then the selectivity for the layer is 0. This may happen when statistics are gathered prior to any features existing in the layer. Always ensure your statistics accurately represent the true representation of the data.
The selectivity value reported is rounded to the 7th decimal.
The Sel: <value> represents the selectivity the optimizer was provided by the st_domain_stats type. This number is derived from the input envelope, the given operator and an execution plan chosen when the statement was parsed.
The following example demonstrates the output one would see using SQL*Plus and autotrace:
The value .162684 represents the selectivity calculated by the st_domain_stats type based upon the input envelope from the st_envintersects operator. The optimizer uses selectivity to represent the fraction of rows which are returned by the statement. The number of rows returned by the statement, 290 in above case, is the cardinality for the statement or predicate. Cardinality is simply calculated by multiplying the number of rows in the table by the selectivity -
178,321 parcels * (.162684/100) = 290 rows (rounded).
The selectivity value is also input used by the optimizer to calculate the cost of using an index compared to performing a full table scan. If a high selectivity is derived, then its very possible the cost of using the index is greater then the cost of performing the full table scan.
Potentially one might see other <values> for selectivity -
(Sel: Default - No Stats)
(Sel: Default - Undefined)
(Sel: 0)
If (Sel: Default - No stats) is reported it indicates there are no statistics for the spatial index. Once the statistics are captured using ArcCatalog, dbms_stats.gather_table_stats or dbms_stats.gather_index_stats the value for selectivity should then be reported.
If (Sel: Default - Undefined) is reported it may indicate that there was an error generating statistics, or that the operator has been disassociated from the statistical type, such as the st_envintersects operator.
In the above cases, when no statistics are present or are undefined, the optimizer uses default values for selectivity (1 percent) and a default cost (3). When the optimizer's default values are used, the indexes low cost becomes the likely access path. But, potentially the high selectivity (1 percent) may result in a very high cardinality and in turn impact the optimizer in choosing an optimal join plan.
When (Sel: 0) is reported then the selectivity for the layer is 0. This may happen when statistics are gathered prior to any features existing in the layer. Always ensure your statistics accurately represent the true representation of the data.
The selectivity value reported is rounded to the 7th decimal.
Article ID: 000009227
Software: ArcSDE 9.3.1, 9.3, 9.2, 10.2.2, 10.2.1, 10.2, 10.1, 10