You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<p>The control bus structure utilises expandable connectors to provide a flexible bus concept. This approach makes it easy to add new signals to the control bus so that data can be passed around the model. The control bus structure implemented is heirarchical so that signals are easily located. The approach adopted is that physical measurements taken from, for example, the transmission are placed on a sub-bus called <b>transmissionBus</b>. Signals output from control blocks, for example the transmission controller, are placed on a sub-bus called <b>transmissionControlBus</b>.</p>
@@ -72,7 +73,8 @@ Parameters that represent initial values for simulation experiments are denoted
72
73
<p>Wheels are identified by numbers from front left towards rear right. Those are, typically, used as indices in parameter or variable names. E.g., for a four-wheel car the front left wheel is \"1\", front right is \"2\", rear left \"3\", and rear right \"4\".</p>
<p>For example: when the accelerator pedal position = 1, the driver is accelerating as fast as possible; when the clutch pedal position = 1, the driver has pressed the clutch pedal and the clutch is actually disengaged.</p>
class Version_1_2_2 "Version 1.2.2 (Jun. 21, 2014)"
433
+
class Version_1_2_2 "Version 1.2.2 (Jun. 30, 2014)"
425
434
extends Modelica.Icons.ReleaseNotes;
426
435
427
436
annotation (Documentation(info="<html>
@@ -603,30 +612,6 @@ on the library.
603
612
</html>"));
604
613
end ReleaseNotes;
605
614
606
-
class Acknowledgements "Acknowledgements"
607
-
extends Modelica.Icons.Information;
608
-
609
-
annotation (Documentation(info="<html>
610
-
<p>A number of automotive library developers and consultants have co-operated to develop this release of the VehicleInterfaces Library. The developers can all be contacted by emailing <a href=\"mailto:[email protected]\">[email protected]</a>. The developers are:</p>
611
-
<ul>
612
-
<li>Arsenal Research: Franz Pirker, Anton Haumer, Christian Kral</li>
<li>DLR Oberpfaffenhofen: Martin Otter, Christian Schweiger, Jakub Tobolar</li>
616
-
<li>DLR Stuttgart: Peter Treffinger, Marcus Baur, Jörg Ungethüm</li>
617
-
<li>Modelon AB: Johan Andreasson, Magnus Gäfvert</li>
618
-
<li>Ricardo UK Ltd: Mark Ingram, Peter Harman</li>
619
-
</ul>
620
-
<p>This library has been developed from work on the original Modelica VMA (<a href=\"http://www.modelica.org/events/Conference2003/papers/h32_vehicle_Tiller.pdf\">Paper from the Modelica Conference 2003</a>) developed by Michael Tiller et al and published by Ford Motor Company.</p>
621
-
<p>Additional ideas from intermediate work by members of DLR Oberpfaffenhofen and Modelon has also been incorporated. The above partners agreed to develop these ideas in to a new library and adopt this set of interface definitions.</p>
622
-
<p>The implementation of the VehicleInterfaces library was led by Claytex Services Limited under contract to Dassault Systèmes AB</p>
<p>This library is maintained by the Modelica Association. Further development takes place on <a href=\"https://github.com/modelica/VehicleInterfaces\">https://github.com/modelica/VehicleInterfaces</a> where users can also report issues and/or supply pull-requests.</p>
666
+
<h5>History</h5>
667
+
<p>A number of automotive library developers and consultants have co-operated to develop the VehicleInterfaces Library. The developers were:</p>
668
+
<ul>
669
+
<li>Arsenal Research: Franz Pirker, Anton Haumer, Christian Kral</li>
<li>DLR Oberpfaffenhofen: Martin Otter, Christian Schweiger, Jakub Tobolar</li>
673
+
<li>DLR Stuttgart: Peter Treffinger, Marcus Baur, Jörg Ungethüm</li>
674
+
<li>Modelon AB: Johan Andreasson, Magnus Gäfvert</li>
675
+
<li>Ricardo UK Ltd: Mark Ingram, Peter Harman</li>
676
+
</ul>
677
+
<p>This library has been developed from work on the original Modelica VMA (<a href=\"http://www.modelica.org/events/Conference2003/papers/h32_vehicle_Tiller.pdf\">Paper from the Modelica Conference 2003</a>) developed by Michael Tiller et al and published by Ford Motor Company.</p>
678
+
<p>Additional ideas from intermediate work by members of DLR Oberpfaffenhofen and Modelon has also been incorporated. The above partners agreed to develop these ideas in to a new library and adopt this set of interface definitions.</p>
679
+
<p>The implementation of the VehicleInterfaces library was led by Claytex Services Limited under contract to Dassault Systèmes AB</p>
<p>The VehicleInterfaces Modelica library provides standard interface definitions for automotive subsystems and vehicle models. These are designed to promote compatibility between the various automotive libraries and provide a flexible, powerful structure for vehicle modelling. The main focus of the library is on defining the interfaces for the individual subsystems and a number of vehicle model examples are included to demonstrate how they might be used.</p>
<p>For an automotive library to be compatible with other libraries based on this set of interface definitions they should extend the interface definition from within this library and following the naming convention for the control signal bus and driver interaction bus if used. </p>
678
694
<p>This library also contains a proposal for a naming convention covering the whole model library and the developers of this library would recommend that this convention is followed by other developers to ensure a consistent naming convention across the whole set of automotive models.</p>
679
-
680
-
<p>The library has been developed as a co-operation between a number of vendors who are currently developing automotive libraries. The developers can be contacted by emailing <a href=\"mailto://[email protected]\">[email protected]</a>, please see <a href=\"Modelica://VehicleInterfaces.UsersGuide.Acknowledgements\">here</a> for a list of the people involved in the development of this library.</p>
695
+
<p>
696
+
The complete documentation of the VehicleInterfaces library in PDF format
697
+
is available as <a href=\"modelica://VehicleInterfaces/Resources/Documentation/VehicleInterfaces.pdf\">VehicleInterfaces.pdf</a>
<p>For an automotive library to be compatible with other libraries based on this set of interface definitions they should extend the interface definition from within this library and following the naming convention for the signal bus. </p>
34
34
<p>This library also contains a proposal for a naming convention covering the whole model library and the developers of this library would recommend that this convention is followed by other developers to ensure a consistent naming convention across the whole set of automotive models.</p>
35
-
36
35
<p>
37
-
The complete documentation of the VehicleInterfaces library in pdf format
36
+
The complete documentation of the VehicleInterfaces library in PDF format
38
37
is available as <a href=\"modelica://VehicleInterfaces/Resources/Documentation/VehicleInterfaces.pdf\">VehicleInterfaces.pdf</a>
39
38
</p>
40
-
41
-
<p>The library has been developed as a co-operation between a number of vendors who are currently developing automotive libraries. The developers can be contacted by emailing <a href=\"mailto://[email protected]\">[email protected]</a>, please see <a href=\"Modelica://VehicleInterfaces.UsersGuide.Acknowledgements\">acknowledgements</a> for a list of the people involved in the development of this library.</p>
39
+
<p>The library has been developed as a co-operation between a number of vendors who are currently developing automotive libraries. Please see <a href=\"modelica://VehicleInterfaces.UsersGuide.Contact\">the contact information</a> on how to give feedback and for a list of the people involved in the development of this library.</p>
0 commit comments