Pull request #129: correcting typos, rename string id to stream id in GUI (and...

Pull request #129: correcting typos, rename string id to stream id in GUI (and consisten in user manual)

Merge in VECTO/vecto-dev from VECTO/mq_vecto-dev:feature/VECTO-1477-update-user-manual to develop

* commit '04fa286e':
  correcting typos, rename string id to stream id in GUI (and consisten in user manual)

Documentation/User Manual/1-user-interface/0_start.md

@@ -21,7 +21,7 @@ In case you do not have execute permissions, please ask your system administrato
 
 If the ExecutionMode is set to `install` (this is also possible when running VECTO from an arbitrary directory), VECTO does not write its configuration files and log files to the application directory but to the directories `%APPDATA%` and `%LOCALAPPDATA%` (usually `C:\Users\<username>\AppData\Roaming` and `C:\Users\<username>\AppData\Local`).
 
-**Important:** If VECO is run from a directory without write permissions it is necessary that you copy the generic VECTO models distributed with VECTO to a location where you have write permissions or set the output path to a directory with write permissions (see the [Options in the main window](#main-form)).
+**Important:** If VECTO is run from a directory without write permissions it is necessary that you copy the generic VECTO models distributed with VECTO to a location where you have write permissions or set the output path to a directory with write permissions (see the [Options in the main window](#main-form)).
 
 
 User Manual

Documentation/User Manual/1-user-interface/B_mainform.md

@@ -84,7 +84,7 @@ Validate Data
 :    Enables or disables internal checks if the model parameters are within a reasonable range. When simulating a new vehicle model it is good to have this option enabled. If the model parameters are from certified components or the model data has only been modified slightly this check may be disabled. The VECTO simulation will abort anyways if there is an error in the model parameters. Enabling this option increases the simulation time by a few seconds.
 
 Output values in vmod at beginning and end of simulation iterval
-:    By defaul VECTO writes the simulation results at the middle of every simulation interval. If this option is enabled, the .vmod file will contain two entries for every simulation interval, one at the beginning and one at the end of the simulation interval. Enabling this option may be helpful for analysing the trace of certain signals but can not be used for quantitative analyses of the fuel consumption, average power losses, etc. The generated modal result file has the suffix '_sim'. The picture below shows the difference in the output (top: conventional, bottom: if this option is checked)
+:    By default VECTO writes the simulation results at the middle of every simulation interval. If this option is enabled, the .vmod file will contain two entries for every simulation interval, one at the beginning and one at the end of the simulation interval. Enabling this option may be helpful for analysing the trace of certain signals but can not be used for quantitative analyses of the fuel consumption, average power losses, etc. The generated modal result file has the suffix '_sim'. The picture below shows the difference in the output (top: conventional, bottom: if this option is checked)
 
 ![Regular VECTO .vmod output (top) vs. beginning and end of simulation interval (bottom)](pics/VECTO_vmod_vgl.png)
 

Documentation/User Manual/1-user-interface/D1_VECTO-Job-Editor.md

@@ -63,7 +63,7 @@ The list contains the pre-defined auxiliaries where the concrete technology for
 
 <div class="engineering">
 Auxiliaries
-:	In Engineerin Mode the auxiliary power demand can be defined in three ways. 
+:	In Engineering Mode the auxiliary power demand can be defined in three ways. 
 
 The first option is to define the power demand directly in the driving cycle in the column "Padd" (see [Driving Cycles](#driving-cycles-.vdri). This allows to vary the auxiliary load over distance (or time, for time-based driving cycles).
 

Documentation/User Manual/1-user-interface/F_VEH-Editor.md

@@ -6,7 +6,7 @@
 
 The [Vehicle File (.vveh)](#vehicle-file-.vveh) defines the main vehicle/chassis parameters like axles including [RRC](#vehicle-rolling-resistance-coefficient)s, air resistance and masses.
 
-The Vehicle Editor contains up to 6 tabs, depending on the powertrain architecture and simulation mode, to edit all vehicle-related parameters. The 'General' tab allows to input mass, loading, air resistance, vehicle axles, etc. The 'Powertrain' tab allows to define the retarder, an optional angle drive. The third tab is dedicated to all electric components in case of hybrid electric and battery electric vehicles. In the fourth tab the torque limitations for the combustion engine, the electric motor and the whole vehicle can be specified. The fifth tab allows to enable or disable certain advanced driver assistant systems to be considered in the vehicle. The last tab is dedicated to PTOs, either as a basic component or to simulate municipal vehicles such as refuse trucks or road speepers with dedicated PTO activation either during driving or during standstill. 
+The Vehicle Editor contains up to 6 tabs, depending on the powertrain architecture and simulation mode, to edit all vehicle-related parameters. The 'General' tab allows to input mass, loading, air resistance, vehicle axles, etc. The 'Powertrain' tab allows to define the retarder, an optional angle drive. The third tab is dedicated to all electric components in case of hybrid electric and battery electric vehicles. In the fourth tab the torque limitations for the combustion engine, the electric motor and the whole vehicle can be specified. The fifth tab allows to enable or disable certain advanced driver assistant systems to be considered in the vehicle. The last tab is dedicated to PTOs, either as a basic component or to simulate municipal vehicles such as refuse trucks or road sweepers with dedicated PTO activation either during driving or during standstill. 
 
 ###Relative File Paths
 
@@ -168,7 +168,7 @@ The *Loss map EM ADC* can be used to consider the losses of a transmission step
 
 In case of a P2.5 configuration (the electric motor is connected to an internal shaft of the tranmission) the transmission ratio for every single gear of the transmission has to be specified in the list to the right of the electric motor parameters.
 
-For the electric energy storage multiple battery packs can be configured either in series or in parallel and the initial state of charge of the whole battery system can be defined.  For every entry of a battery pack the number of packs (count) in series and a string identifier need to be specified. Battery packs on the same string are connected in series (e.g., two different battery packs on string nuber 1 are in series) while all strings are then connected in parallel (see [Battery Model](#foo) for details). This is only supported for batteries and **not** for SuperCaps.
+For the electric energy storage multiple battery packs can be configured either in series or in parallel and the initial state of charge of the whole battery system can be defined.  For every entry of a battery pack the number of packs (count) in series and a stream identifier need to be specified. Battery packs on the same stream are connected in series (e.g., two different battery packs on stream number 1 are in series) while all streams are then connected in parallel (see [Battery Model](#foo) for details). This is only supported for batteries and **not** for SuperCaps.
 
 **Double-click** an entry to edit.
 
@@ -176,7 +176,7 @@ For the electric energy storage multiple battery packs can be configured either
 : ![addcycle](pics/plus-circle-icon.png) Add REESS (.vbat)
 : ![remcycle](pics/minus-circle-icon.png) Remove the selected REESS from the list
 
-In the REESS Dialog the battery file itself and how it is connected to the electric system (i.e, the string identifier and number of packs used) can be modified.
+In the REESS Dialog the battery file itself and how it is connected to the electric system (i.e, the stream identifier and number of packs used) can be modified.
 
 ![](pics/BatteryPackDialog.png)
 
@@ -192,7 +192,7 @@ In case that the gearbox' maximum torque is lower than the engine's maximum torq
 
 Next, the maximum available torque for the electric machine can be reduced at the vehicle level, both for propulsion and recuperation. The input file is the same as the maximum drive and maximum recuperation curve (see [Electric Motor Max Torque File](#electric-motor-max-torque-file-.vemp))
 
-Last, the overall propulsion of the vehicle (i.e., electric motor plus combusion engine) can be limited. The "Propulsion Torque Limit" curve limits the maximum effective torque at the gearbox input shaft over the input speed. This curve is added to the combustion engine's maximum torque curve (only positive values are allowed!). For details on the file format see [Vehicle Boosting Limits](#vehcle-boosing-limits-.vemp). The propulsion torque limit has to be provided from 0 rpm to the maximum speed of the combustion engine. In case of P3 or P4 configuration, the torque at the gearbox input shaft is calculated assuming that the electric motor does not contribute to propelling the vehicle, considering the increased losses in the transmission components inbetween. For P2.5 powertrain configurations no special calculations are necessary as this architecture is internally anyhow modelled as P2 architecture.
+Last, the overall propulsion of the vehicle (i.e., electric motor plus combustion engine) can be limited. The "Propulsion Torque Limit" curve limits the maximum effective torque at the gearbox input shaft over the input speed. This curve is added to the combustion engine's maximum torque curve (only positive values are allowed!). For details on the file format see [Vehicle Boosting Limits](#vehcle-boosing-limits-.vemp). The propulsion torque limit has to be provided from 0 rpm to the maximum speed of the combustion engine. In case of P3 or P4 configuration, the torque at the gearbox input shaft is calculated assuming that the electric motor does not contribute to propelling the vehicle, considering the increased losses in the transmission components inbetween. For P2.5 powertrain configurations no special calculations are necessary as this architecture is internally anyhow modelled as P2 architecture.
 
 ##Vehicle Editor -- ADAS Tab
 

Documentation/User Manual/1-user-interface/G_ENG-Editor.md

@@ -72,7 +72,7 @@ If the engine is operated in dual-fuel mode, enabling the checkbox "Dual Fuel En
 
 ![](pics/EngineForm_WHR.png)
 
-In case the engine is equipped with a waste heat recovery system (WHR) the WHR type can be selected in the lower right part of the window. For WHR systems that generate mechanlical power that is directly delivered to the engine's crankshaft no further input is required - the WHR shall be considered in the fuel consumption map already. 
+In case the engine is equipped with a waste heat recovery system (WHR) the WHR type can be selected in the lower right part of the window. For WHR systems that generate mechanical power that is directly delivered to the engine's crankshaft no further input is required - the WHR shall be considered in the fuel consumption map already. 
 
 For WHR systems with electrical power output the generated electrical power needs to be provided in the [Fuel Consumption Map](#fuel-consumption-map-.vmap) of the primary fuel. 
 

Documentation/User Manual/1-user-interface/H_GBX-Editor.md

@@ -90,7 +90,7 @@ Torque reserve
 :   The minimal torque reserve which has to be provided after a gearshift. Only used for MT transmissions.
 
 Minimum time between gearshifts
-:   Defines the time interval between two consecutive gearshifts. Has to be greater than 0. This time interval is ingored if the engine speed gets too high or too low.
+:   Defines the time interval between two consecutive gearshifts. Has to be greater than 0. This time interval is ignored if the engine speed gets too high or too low.
 
 ####Shift Strategy Parameters
 

Documentation/User Manual/1-user-interface/L_ElectricMotor.md

@@ -47,7 +47,7 @@ Max. Drive and Max. Generation Torque Curve
 :   Torque over engine speed the electric motor can apply on its output shaft. (see [Electric Motor Max Torque File (.vemp)](#electric-motor-max-torque-file-.vemp)). The max drive and max generation torque have to be provided for two different voltage levels.
 
 Electric Power Consumption Map
-:   Defines the electric power that is required to provide a certain mechanical power (torque and angular speed) at the motor's shaft. This map is used to calculate the electric power demand. The electric power consumption map shall cover a torque range exceeding the max. drive and max. generation torque and shall cover the speed range from 0 up to the maximum speed. (see [Electric Motor Map (.vemo)](#electric-motor-map-.vemo)). The power map has to be provided for two different volatge levels.
+:   Defines the electric power that is required to provide a certain mechanical power (torque and angular speed) at the motor's shaft. This map is used to calculate the electric power demand. The electric power consumption map shall cover a torque range exceeding the max. drive and max. generation torque and shall cover the speed range from 0 up to the maximum speed. (see [Electric Motor Map (.vemo)](#electric-motor-map-.vemo)). The power map has to be provided for two different voltage levels.
 
 Voltage Level Low/High
 :    Applicable voltage level for the electric power consumption map and max drive/generation torque curve

Documentation/User Manual/2-calculation-modes/verification-test.md

 ##Verification Test Mode
 
-The purpose of the verification test is to simulate a vehicle defined in declaration mode on a measured real-driving cycle. This simulation mode uses its own [cyle format](#verification-test-cycle), requiring mainly vehicle speed, wheel speed, wheel torque, engine-fan speed, and engine speed. VECTO then calculates the appropriate gear and simulates the cycle. Auxiliary power is according to the technologies defined in the vehicle. However, the engine fan auxiliary is ignored and the power demand for the engine fan is calcuated based on the engine-fan speed. The power demand for the other auxiliaries depends on the vehicle's actual speed. The fuel consumption is calculated using the engine speed from the driving cycle and the torque demand as given in the cycle, adding the losses of all powertrain components.
+The purpose of the verification test is to simulate a vehicle defined in declaration mode on a measured real-driving cycle. This simulation mode uses its own [cycle format](#verification-test-cycle), requiring mainly vehicle speed, wheel speed, wheel torque, engine-fan speed, and engine speed. VECTO then calculates the appropriate gear and simulates the cycle. Auxiliary power is according to the technologies defined in the vehicle. However, the engine fan auxiliary is ignored and the power demand for the engine fan is calcuated based on the engine-fan speed. The power demand for the other auxiliaries depends on the vehicle's actual speed. The fuel consumption is calculated using the engine speed from the driving cycle and the torque demand as given in the cycle, adding the losses of all powertrain components.
 
 <div class="engineering">
 ###Requirements
@@ -21,7 +21,7 @@ The purpose of the verification test is to simulate a vehicle defined in declara
 
 -   One or more checked job files in the Job List
 -   Each job must include a vehicle in declaration mode (XML)
--   Each job must include the manufacturer report (XML) of the vehicle as generated for the vehicle delcaration
+-   Each job must include the manufacturer report (XML) of the vehicle as generated for the vehicle declaration
 -   Each job file must include exactly one driving cycle (in case multiple driving cycles are provided, only the first cycle is simulated!)
 
 ###Results
@@ -37,7 +37,7 @@ The purpose of the verification test is to simulate a vehicle defined in declara
    * The cycle is provided in 2Hz
    * The ratio of wheel speeds (left/right) should be lower than 1.4 for wheel speeds above 0.1rpm
    * The absolute difference of wheel speeds (left/right) should be lower than 1rpm for wheel speeds below 0.1rpm
-   * The torque ratio (left/right) should be lower than 3 and the absoulte difference should be lower than 200Nm.
+   * The torque ratio (left/right) should be lower than 3 and the absolute difference should be lower than 200Nm.
    * The fan speed shall be between 20 and 4000rpm, unless the vehicle is equipped with an electric fan
    * The fuel consumption within a window off 10min should be between 180 and 600 g/kWh_(PWheel_pos)
 

Documentation/User Manual/3-simulation-models/BusAuxiliaries.md

@@ -13,7 +13,7 @@ The power demand for the engine cooling fan depends on the selected technology o
 
 ###Steering Pump
 
-The power demand of the steering pump can either be electrical or mechanical. The actual demand depends on the selected technolgy, vehicle dimensions and number of steered axles.
+The power demand of the steering pump can either be electrical or mechanical. The actual demand depends on the selected technology, vehicle dimensions and number of steered axles.
 
 ###Pneumatic System
 

Documentation/User Manual/3-simulation-models/Engine_WHTC.md

@@ -28,7 +28,7 @@ with the correction factor CF~urb~, CF~rur~, CF~mot~ coming from the [Engine](#e
 
 In order to balance the trade-off between emissions and fuel consumption during cold and hot starting conditions an additional balancing factor $CF_{C/H}$ is determined from the overall specific fuel consumption over the cold start and hot start WHTC test. Additional correction factors considered are regarding the net calorific value of the fuel ($CF_{NCV}$) and exhaust after-treatment systems ($CF_{RegPer}$). This values are part of the output from the engine component tool.
 
-$NCV_{stdEngine}$: Net calorific value as defined as refernce value for engine testing (Pt. 5.3.3.1 of Annex V), see [Fuel properties](#fuel-properties)
+$NCV_{stdEngine}$: Net calorific value as defined as reference value for engine testing (Pt. 5.3.3.1 of Annex V), see [Fuel properties](#fuel-properties)
 
 $NCV_{stdVECTO}$: Net calorific value defined as reference value for vehicle CO2 certification, see [Fuel properties](#fuel-properties)
 

Documentation/User Manual/3-simulation-models/TC.md

@@ -37,7 +37,7 @@ The torque converter characteristics must also be defined for speed ratios  grea
 <div class="declaration">
 In declaration mode, the torque converter for drag points is automatically appended by VECTO. Input data with a speed ratio &geq; 1 are skipped.
 
-For Power Split transmissions, where the torque converter characteristics already contains the gearbox losses and transmission ratio, the generic drag points are adapted according to the following equations:
+For Power Split transmissions, where the torque converter characteristics already includes the gearbox losses and transmission ratio, the generic drag points are adapted according to the following equations:
 
 $\nu_{PS} = \nu / ratio_i$
 

VECTO/GUI/REESSPackDialog.Designer.vb

@@ -59,19 +59,21 @@ Partial Class REESSPackDialog
         Me.TableLayoutPanel1.ColumnStyles.Add(New System.Windows.Forms.ColumnStyle(System.Windows.Forms.SizeType.Percent, 50!))
         Me.TableLayoutPanel1.Controls.Add(Me.OK_Button, 0, 0)
         Me.TableLayoutPanel1.Controls.Add(Me.Cancel_Button, 1, 0)
-        Me.TableLayoutPanel1.Location = New System.Drawing.Point(421, 108)
+        Me.TableLayoutPanel1.Location = New System.Drawing.Point(632, 166)
+        Me.TableLayoutPanel1.Margin = New System.Windows.Forms.Padding(4, 5, 4, 5)
         Me.TableLayoutPanel1.Name = "TableLayoutPanel1"
         Me.TableLayoutPanel1.RowCount = 1
         Me.TableLayoutPanel1.RowStyles.Add(New System.Windows.Forms.RowStyle(System.Windows.Forms.SizeType.Percent, 50!))
-        Me.TableLayoutPanel1.Size = New System.Drawing.Size(146, 29)
+        Me.TableLayoutPanel1.Size = New System.Drawing.Size(219, 45)
         Me.TableLayoutPanel1.TabIndex = 4
         '
         'OK_Button
         '
         Me.OK_Button.Anchor = System.Windows.Forms.AnchorStyles.None
-        Me.OK_Button.Location = New System.Drawing.Point(3, 3)
+        Me.OK_Button.Location = New System.Drawing.Point(4, 5)
+        Me.OK_Button.Margin = New System.Windows.Forms.Padding(4, 5, 4, 5)
         Me.OK_Button.Name = "OK_Button"
-        Me.OK_Button.Size = New System.Drawing.Size(67, 23)
+        Me.OK_Button.Size = New System.Drawing.Size(100, 35)
         Me.OK_Button.TabIndex = 3
         Me.OK_Button.Text = "OK"
         '
@@ -79,9 +81,10 @@ Partial Class REESSPackDialog
         '
         Me.Cancel_Button.Anchor = System.Windows.Forms.AnchorStyles.None
         Me.Cancel_Button.DialogResult = System.Windows.Forms.DialogResult.Cancel
-        Me.Cancel_Button.Location = New System.Drawing.Point(76, 3)
+        Me.Cancel_Button.Location = New System.Drawing.Point(114, 5)
+        Me.Cancel_Button.Margin = New System.Windows.Forms.Padding(4, 5, 4, 5)
         Me.Cancel_Button.Name = "Cancel_Button"
-        Me.Cancel_Button.Size = New System.Drawing.Size(67, 23)
+        Me.Cancel_Button.Size = New System.Drawing.Size(100, 35)
         Me.Cancel_Button.TabIndex = 4
         Me.Cancel_Button.Text = "Cancel"
         '
@@ -90,16 +93,18 @@ Partial Class REESSPackDialog
         Me.pnREESSPack.Controls.Add(Me.btnOpenBattery)
         Me.pnREESSPack.Controls.Add(Me.btnBrowseBattery)
         Me.pnREESSPack.Controls.Add(Me.tbBattery)
-        Me.pnREESSPack.Location = New System.Drawing.Point(12, 12)
+        Me.pnREESSPack.Location = New System.Drawing.Point(18, 18)
+        Me.pnREESSPack.Margin = New System.Windows.Forms.Padding(4, 5, 4, 5)
         Me.pnREESSPack.Name = "pnREESSPack"
-        Me.pnREESSPack.Size = New System.Drawing.Size(553, 27)
+        Me.pnREESSPack.Size = New System.Drawing.Size(830, 42)
         Me.pnREESSPack.TabIndex = 0
         '
         'btnOpenBattery
         '
-        Me.btnOpenBattery.Location = New System.Drawing.Point(4, 3)
+        Me.btnOpenBattery.Location = New System.Drawing.Point(6, 5)
+        Me.btnOpenBattery.Margin = New System.Windows.Forms.Padding(4, 5, 4, 5)
         Me.btnOpenBattery.Name = "btnOpenBattery"
-        Me.btnOpenBattery.Size = New System.Drawing.Size(94, 21)
+        Me.btnOpenBattery.Size = New System.Drawing.Size(141, 32)
         Me.btnOpenBattery.TabIndex = 0
         Me.btnOpenBattery.TabStop = false
         Me.btnOpenBattery.Text = "REESS Pack"
@@ -109,9 +114,10 @@ Partial Class REESSPackDialog
         '
         Me.btnBrowseBattery.Anchor = CType((System.Windows.Forms.AnchorStyles.Top Or System.Windows.Forms.AnchorStyles.Right),System.Windows.Forms.AnchorStyles)
         Me.btnBrowseBattery.Image = CType(resources.GetObject("btnBrowseBattery.Image"),System.Drawing.Image)
-        Me.btnBrowseBattery.Location = New System.Drawing.Point(527, 2)
+        Me.btnBrowseBattery.Location = New System.Drawing.Point(790, 3)
+        Me.btnBrowseBattery.Margin = New System.Windows.Forms.Padding(4, 5, 4, 5)
         Me.btnBrowseBattery.Name = "btnBrowseBattery"
-        Me.btnBrowseBattery.Size = New System.Drawing.Size(24, 24)
+        Me.btnBrowseBattery.Size = New System.Drawing.Size(36, 37)
         Me.btnBrowseBattery.TabIndex = 1
         Me.btnBrowseBattery.UseVisualStyleBackColor = true
         '
@@ -119,50 +125,55 @@ Partial Class REESSPackDialog
         '
         Me.tbBattery.Anchor = CType(((System.Windows.Forms.AnchorStyles.Top Or System.Windows.Forms.AnchorStyles.Left)  _
             Or System.Windows.Forms.AnchorStyles.Right),System.Windows.Forms.AnchorStyles)
-        Me.tbBattery.Location = New System.Drawing.Point(104, 4)
+        Me.tbBattery.Location = New System.Drawing.Point(156, 6)
+        Me.tbBattery.Margin = New System.Windows.Forms.Padding(4, 5, 4, 5)
         Me.tbBattery.Name = "tbBattery"
-        Me.tbBattery.Size = New System.Drawing.Size(417, 20)
+        Me.tbBattery.Size = New System.Drawing.Size(624, 26)
         Me.tbBattery.TabIndex = 0
         '
         'tbBatteryPackCnt
         '
-        Me.tbBatteryPackCnt.Location = New System.Drawing.Point(214, 45)
+        Me.tbBatteryPackCnt.Location = New System.Drawing.Point(321, 69)
+        Me.tbBatteryPackCnt.Margin = New System.Windows.Forms.Padding(4, 5, 4, 5)
         Me.tbBatteryPackCnt.Name = "tbBatteryPackCnt"
-        Me.tbBatteryPackCnt.Size = New System.Drawing.Size(59, 20)
+        Me.tbBatteryPackCnt.Size = New System.Drawing.Size(86, 26)
         Me.tbBatteryPackCnt.TabIndex = 1
         '
         'lblBatteryPackCnt
         '
         Me.lblBatteryPackCnt.AutoSize = true
-        Me.lblBatteryPackCnt.Location = New System.Drawing.Point(17, 48)
+        Me.lblBatteryPackCnt.Location = New System.Drawing.Point(26, 74)
+        Me.lblBatteryPackCnt.Margin = New System.Windows.Forms.Padding(4, 0, 4, 0)
         Me.lblBatteryPackCnt.Name = "lblBatteryPackCnt"
-        Me.lblBatteryPackCnt.Size = New System.Drawing.Size(124, 13)
+        Me.lblBatteryPackCnt.Size = New System.Drawing.Size(183, 20)
         Me.lblBatteryPackCnt.TabIndex = 25
         Me.lblBatteryPackCnt.Text = "Number of RESS Packs:"
         '
         'tbStreamId
         '
-        Me.tbStreamId.Location = New System.Drawing.Point(214, 71)
+        Me.tbStreamId.Location = New System.Drawing.Point(321, 109)
+        Me.tbStreamId.Margin = New System.Windows.Forms.Padding(4, 5, 4, 5)
         Me.tbStreamId.Name = "tbStreamId"
-        Me.tbStreamId.Size = New System.Drawing.Size(59, 20)
+        Me.tbStreamId.Size = New System.Drawing.Size(86, 26)
         Me.tbStreamId.TabIndex = 2
         '
         'lblStreamId
         '
         Me.lblStreamId.AutoSize = true
-        Me.lblStreamId.Location = New System.Drawing.Point(17, 74)
+        Me.lblStreamId.Location = New System.Drawing.Point(26, 114)
+        Me.lblStreamId.Margin = New System.Windows.Forms.Padding(4, 0, 4, 0)
         Me.lblStreamId.Name = "lblStreamId"
-        Me.lblStreamId.Size = New System.Drawing.Size(44, 13)
+        Me.lblStreamId.Size = New System.Drawing.Size(74, 20)
         Me.lblStreamId.TabIndex = 27
-        Me.lblStreamId.Text = "String #"
+        Me.lblStreamId.Text = "Stream #"
         '
         'REESSPackDialog
         '
         Me.AcceptButton = Me.OK_Button
-        Me.AutoScaleDimensions = New System.Drawing.SizeF(6!, 13!)
+        Me.AutoScaleDimensions = New System.Drawing.SizeF(9!, 20!)
         Me.AutoScaleMode = System.Windows.Forms.AutoScaleMode.Font
         Me.CancelButton = Me.Cancel_Button
-        Me.ClientSize = New System.Drawing.Size(579, 149)
+        Me.ClientSize = New System.Drawing.Size(868, 229)
         Me.Controls.Add(Me.tbStreamId)
         Me.Controls.Add(Me.lblStreamId)
         Me.Controls.Add(Me.tbBatteryPackCnt)
@@ -170,6 +181,7 @@ Partial Class REESSPackDialog
         Me.Controls.Add(Me.pnREESSPack)
         Me.Controls.Add(Me.TableLayoutPanel1)
         Me.FormBorderStyle = System.Windows.Forms.FormBorderStyle.FixedToolWindow
+        Me.Margin = New System.Windows.Forms.Padding(4, 5, 4, 5)
         Me.MaximizeBox = false
         Me.MinimizeBox = false
         Me.Name = "REESSPackDialog"