The Portal Administrator View - Revision history

Jonas: /* Upload a Vehicle Import File */

2025-09-02T12:59:24Z

Upload a Vehicle Import File

← Older revision		Revision as of 12:59, 2 September 2025
Line 269:		Line 269:
	The header is a bit special:		The header is a bit special:
	a set of columns are treated specially,		a set of columns are treated specially,
	and the rest are added to the resulting ~~car~~ as labels.		and the rest are added to the resulting vehicle as labels.
	The special column headers are listed below,		The special column headers are listed below,
	but are also the same fields you find in the [[#Add Vehicle Dialog\|Add Vehicle dialog]].		but are also the same fields you find in the [[#Add Vehicle Dialog\|Add Vehicle dialog]].
Line 277:		Line 277:
	As mentioned,		As mentioned,
	remaining columns are interpreted as labels		remaining columns are interpreted as labels
	and are added to all imported ~~cars~~.		and are added to all imported vehicles.
	New labels are created as valued labels,		New labels are created as valued labels,
	and are given an empty value for rows with empty data.		and are given an empty value for rows with empty data.
	If there is data present,		If there is data present,
	it will be saved as the value of the label for the corresponding ~~car~~.		it will be saved as the value of the label for the corresponding vehicles.
	If the label already exists		If the label already exists
	but is not a valued label,		but is not a valued label,

Mika.ivarsson: Minor tweaks of /* Upload a Vehicle Import File */

2025-08-28T07:27:17Z

Minor tweaks of Upload a Vehicle Import File

← Older revision		Revision as of 07:27, 28 August 2025
Line 288:		Line 288:
	Special header values:		Special header values:
	; VIN		; VIN
	: ~~VI Number~~ specifying what car the row refers to. '''Required'''.		: VIN specifying what car the row refers to. '''Required'''.
	; regNr		; regNr
	: License plate number.		: License plate number.
	; description		; description
	~~: Text description.~~
	; project		; project
	~~: TODO~~
	; protoNumber		; protoNumber
	~~: TODO~~
	; tsu		; tsu
	~~: TODO~~
	; series		; series
	~~: TODO~~
	; profile		; profile
	: Name of [[Vehicle Profiles\|Vehicle Profile]]		: Name of [[Vehicle Profiles\|Vehicle Profile]]
	; diagnostics		; diagnostics
	: Name of [[Vehicle Profiles#Manage Description files\|Diagnostics DB]] file		: Name of [[Vehicle Profiles#Manage Description files\|Diagnostics DB]] file
			Full header for copying: ''VIN,regNr,description,project,protoNumber,tsu,series,profile,diagnostics''

	=== Show or export SIM card ID ===		=== Show or export SIM card ID ===

Mika.ivarsson: Update vehicle import section

2025-08-25T15:09:22Z

Update vehicle import section

@@ Line 260: / Line 260: @@
 ===Upload a Vehicle Import File===
-There are seven attributes currently. When uploading the file you have a choice of modifying existing vehicles in the portal. If you do not check this box and there are vehicles that already exist, the import will fail.
+Using ''Upload Vehicle Import File'',
 === Show or export SIM card ID ===

Robin.karhu: /* Fetch PINs */

2025-06-13T09:01:16Z

Fetch PINs

← Older revision		Revision as of 09:01, 13 June 2025
Line 636:		Line 636:

	==== Fetch PINs ====		==== Fetch PINs ====
	For portals with VCF enabled there will be a button '''Fetch PINs''' that will connect with PIE to fetch any available PINs for the resources in the group. These PINs can then be applied to the VCF configurations of the group. Read more about VCF [[Vehicle Communication Forwarder\|here]] and about ~~fetching~~ PINs ~~from PIE~~ [[I/O configurations#Apply uploaded PINs\|here]].		For portals with VCF enabled there will be a button '''Fetch PINs''' that will connect with PIE to fetch any available PINs for the resources in the group. These PINs can then be applied to the VCF configurations of the group. Read more about VCF [[Vehicle Communication Forwarder\|here]] and about applying the fetched PINs [[I/O configurations#Apply uploaded PINs\|here]].

	====Manipulating Resources in a Resource Group====		====Manipulating Resources in a Resource Group====

Robin.karhu: /* Fetch PINs */

2025-06-13T09:00:47Z

Fetch PINs

← Older revision		Revision as of 09:00, 13 June 2025
Line 636:		Line 636:

	==== Fetch PINs ====		==== Fetch PINs ====
	For portals with VCF enabled there will be a button '''Fetch PINs''' that will connect with PIE to fetch any available PINs for the resources in the group. These PINs can then be applied to the VCF configurations of the group. Read more about VCF [[Vehicle Communication Forwarder\|here]].		For portals with VCF enabled there will be a button '''Fetch PINs''' that will connect with PIE to fetch any available PINs for the resources in the group. These PINs can then be applied to the VCF configurations of the group. Read more about VCF [[Vehicle Communication Forwarder\|here]] and about fetching PINs from PIE [[I/O configurations#Apply uploaded PINs\|here]].

	====Manipulating Resources in a Resource Group====		====Manipulating Resources in a Resource Group====

Robin.karhu: /* The Resource Groups Tab */

2025-06-13T08:52:00Z

The Resource Groups Tab

← Older revision		Revision as of 08:52, 13 June 2025
Line 634:		Line 634:
	==== Approved Assignments ====		==== Approved Assignments ====
	You can require that assignments must have been reviewed and approved before they can be applied to a resource group by checking the box "Require Approved Assignments". If an assignment does not meet these criteria, the assignment will not be applied to the resource group. Read more about the assignment review process [[Review assignment process\|here]].		You can require that assignments must have been reviewed and approved before they can be applied to a resource group by checking the box "Require Approved Assignments". If an assignment does not meet these criteria, the assignment will not be applied to the resource group. Read more about the assignment review process [[Review assignment process\|here]].

			==== Fetch PINs ====
			For portals with VCF enabled there will be a button '''Fetch PINs''' that will connect with PIE to fetch any available PINs for the resources in the group. These PINs can then be applied to the VCF configurations of the group. Read more about VCF [[Vehicle Communication Forwarder\|here]].

	====Manipulating Resources in a Resource Group====		====Manipulating Resources in a Resource Group====

Henrik.Moller: /* Configure the Vinreader Module */

2025-06-12T06:31:49Z

Configure the Vinreader Module

← Older revision		Revision as of 06:31, 12 June 2025
Line 570:		Line 570:

	=== Configure the Vinreader Module ===		=== Configure the Vinreader Module ===
	[[File:~~Screenshot from 2022-04-22 08-59-33~~.png\|alt=Settings for the Vinreader module\|thumb\|250x250px\|Settings for the Vinreader module]]		[[File:SettingForTheVinReaderModule.png\|alt=Settings for the Vinreader module\|thumb\|250x250px\|Settings for the Vinreader module]]
	The method of reading a vehicle's VIN (Vehicle Identification Number) can be set to '''SPA29''', '''OBD2''', '''SPA11, BP, TEA2+, UDS, DoIP''' ''', SOVD''' or '''FIXED'''. The preferred setting for this is OBD2, whereby a standardized OBD-II diagnostic service is used to read out the VIN. SPA29 and SPA11 refers to using CAN diagnostic requests using either 29 bit or 11 bit SPA addressing respectively. The CAN channel (on the WCU) is selected in 'Default CAN channel'.		The method of reading a vehicle's VIN (Vehicle Identification Number) can be set to '''SPA29''', '''OBD2''', '''SPA11, BP, TEA2+, UDS, DoIP''' ''', SOVD''' or '''FIXED'''. The preferred setting for this is OBD2, whereby a standardized OBD-II diagnostic service is used to read out the VIN. SPA29 and SPA11 refers to using CAN diagnostic requests using either 29 bit or 11 bit SPA addressing respectively. The CAN channel (on the WCU) is selected in 'Default CAN channel'.

Henrik.Moller: /* Configure the Vinreader Module */

2025-06-12T06:29:37Z

Configure the Vinreader Module

← Older revision		Revision as of 06:29, 12 June 2025
Line 589:		Line 589:

	The standard range for custom values is between <code>0x0E80</code> and <code>0x0FFF</code>, but users may also enter a value outside this range if needed.		The standard range for custom values is between <code>0x0E80</code> and <code>0x0FFF</code>, but users may also enter a value outside this range if needed.

			'''Note:''' For the ''Tester Address'' field to appear in this module, the vehicle's VIN must be set to '''SPA29'''.

	==The Administration Tab==		==The Administration Tab==

Henrik.Moller: /* Configure the Vinreader Module */

2025-06-12T06:27:51Z

Configure the Vinreader Module

@@ Line 462: / Line 462: @@
 [[File:Screenshot from 2021-10-19 10-17-38.png|none|thumb|Settings for the IDC module]]
 From version 2.68.0 another option also exists where the file output format can be set.
 ===Configure the IPEmotion RT Module===
@@ Line 502: / Line 510: @@
 From version 2.88.0 it is possible to select the MDF4 format when logging frames.
 ===Configure the SmartEye Module===
@@ Line 565: / Line 581: @@
 There are currently two ways of identifying a vehicle, either by reading the VIN or the chassis number. The selection is shown in Illustration 'Vehicle ID method type' to the right. When using 'Chassis NO' as identification type you must select which valued label to use for this mechanism. If no such label has been selected, you will see the the text 'No label selected in backend' to the right of the selected type, see Illustration 'No identifying label selected' on the right. To select which label to use, head over to the [[Labels#Administer labels|label administration tab]] to make the selection.
 ==The Administration Tab==

Henrik.Moller: /* Configure the Vinreader Module */

2025-06-12T06:17:49Z

Configure the Vinreader Module

← Older revision		Revision as of 06:17, 12 June 2025
Line 555:		Line 555:
	=== Configure the Vinreader Module ===		=== Configure the Vinreader Module ===
	[[File:Screenshot from 2022-04-22 08-59-33.png\|alt=Settings for the Vinreader module\|thumb\|250x250px\|Settings for the Vinreader module]]		[[File:Screenshot from 2022-04-22 08-59-33.png\|alt=Settings for the Vinreader module\|thumb\|250x250px\|Settings for the Vinreader module]]
	The method of reading a vehicle's VIN (Vehicle Identification Number) can be set to '''SPA29''', '''OBD2''', '''SPA11, BP, TEA2+, UDS, DoIP''' or '''FIXED'''. The preferred setting for this is OBD2, whereby a standardized OBD-II diagnostic service is used to read out the VIN. SPA29 and SPA11 refers to using CAN diagnostic requests using either 29 bit or 11 bit SPA addressing respectively. The CAN channel (on the WCU) is selected in 'Default CAN channel'.		The method of reading a vehicle's VIN (Vehicle Identification Number) can be set to '''SPA29''', '''OBD2''', '''SPA11, BP, TEA2+, UDS, DoIP''' ''', SOVD''' or '''FIXED'''. The preferred setting for this is OBD2, whereby a standardized OBD-II diagnostic service is used to read out the VIN. SPA29 and SPA11 refers to using CAN diagnostic requests using either 29 bit or 11 bit SPA addressing respectively. The CAN channel (on the WCU) is selected in 'Default CAN channel'.

	When the setting FIXED is used, the VIN will not be read out from the vehicle using a diagnostic service, but rather a preset value entered in the item named 'Fixed VIN' is used.		When the setting FIXED is used, the VIN will not be read out from the vehicle using a diagnostic service, but rather a preset value entered in the item named 'Fixed VIN' is used.