openinverter.org wiki - User contributions [en]

https://openinverter.org/wiki/api.php?action=feedcontributions&feedformat=atom&user=Powercontrol openinverter.org wiki - User contributions [en] 2026-04-29T10:23:17Z User contributions MediaWiki 1.43.1 https://openinverter.org/wiki/index.php?title=Content_Management&diff=5779 Content Management 2025-05-11T09:49:32Z

<p>Powercontrol: </p> <hr /> <div>'''DRAFT - DRAFT - DRAFT'''<br /> <br /> the objective of this page is to explain how the content of the wiki page could be structured using Semantic for Mediawiki (SMW) to build a scalable and object-based wiki (for search and relation-building aspects) and still keeping the freedom for authors to create their content. There needs to be a trade-off to be found between freedom and structure.<br /> <br /> === Why Semantic for Mediawiki? ===<br /> SMW allows to have a form-based creation of objects. the form asks the users some key information then create the corresponding page and render the entered information in a consistent way, assign the category accordingly etc.<br /> <br /> Because the page created is based on a template, changing the template modifies the instantiation of the created pages. <br /> <br /> SMW also allows to create dynamic queries inside pages. The content will be modified based on other pages content. this is a powerful manner to make references to other pages without doing manual maintenance of the page. A practical and basic example would be that if the query below was inserted a page creation (a template being called by a form):<br /> <br /> <nowiki>{{#ask:<br /> [[FoundIn.Page::{{PAGENAME}}]]<br /> | format=list<br /> | link=all<br /> }}</nowiki><br /> The page content will update itself to list all other pages that refer to this new page. There are much more granular type of queries to be done (including on categories) which then become really handy.<br /> === General Principles and Naming Convention ===<br /> SMW uses multiple notions. They are key to be used properly for good use.<br /> <br /> ==== Type of Mediawiki Objects and their usage ====<br /> {| class="wikitable"<br /> |+<br /> !Object<br /> !Usage<br /> !Naming Convention<br /> !Example<br /> |-<br /> |'''Page'''<br /> |the core component of the wiki and what readers are consuming. By default, there is no hierarchical structure of pages - and categories are the better way for structuring a wiki<br /> |each Word is start with a capital letter. Spaces and brackets are allowed. mutiple words are recommended to be separated by a space (mediawiki uses underscore instead of %20 for URL)<br /> '''''Title Case'''''<br /> |Nissan Leaf (2010-2017)<br /> |-<br /> |'''Category'''<br /> |the categories are part of the generic Mediawiki structure. its reflects a categorization or labeling of pages. Categories can be nested which are useful to reflect a structure of "component of" and for "is a subtype of". Multiple categories can be assigned to page, hence it can provide multiple view at once. A dedicated section of this page will cover their aspects.<br /> There are cases where it is not obvious whether a property or a category makes more sense. one does not prevent the other, by the way.<br /> |as the wiki already as categories created and they use naming similar to Page, the categories will further be named the same way.<br /> Ideally, categories shall be written in <u>plural form</u> (because it is a grouping of x) <br /> '''''Title Case (in plural)'''''<br /> |Batteries<br /> Connectors<br /> |-<br /> |'''Property'''<br /> |SMW specific - it defines a relation between 2 objects, or assign an attribute to an object. the target (called [[Special:Types]]) can be a list, another page. When defining a property, it would make sense to refer to a specific category of object (for instance, FoundIn would be referring to a Vehicle or a Component), but the type of object we can refer to are Pages, Numbers, Date,... nothing to do with category. <br /> |'''''UpperCamelCase.DestinationObjectType''''' or '''''UpperCamelCase.DestinationAttributeType'''''<br /> |FoundIn.Page<br /> HasWeight.Qantity<br /> |-<br /> |'''Template'''<br /> |SMW specific - defines which properties values shall be defined at the creation of an object. Not all pages must be created using templates, but objects which have relations between themselves are best created using templates.<br /> |the template name shall refer to a corresponding category name in <u>singular</u>, and the template shall enforce that category at page creation.<br /> '''''T/UpperCamelCase.OutputFormat'''''<br /> |T/Connector.Infobox<br /> T/Battery.PlainText<br /> |-<br /> |'''Form'''<br /> |SMW specific - A Form is an helper for the author to create a templated object. The form allows to create a consistent visual structure to pages<br /> |'''''F/UpperCamelCase''''' - the Form refers to a corresponding Template, but the output format will not be referred to in the form name.<br /> A form can also call multiple templates - in such case its name will refer to the first one<br /> |F/Connector<br /> F/Battery<br /> |}<br /> <br /> ==== Hierarchical relationship ====<br /> There are often 2 possibilities for defining relationship between objects, you can go from parent to child, or from child to parent. <br /> <br /> In practical manner, I can define from a DC/DC that it is a component of the vehicle XYZ, or from that vehicle, that it uses the component DC/DC ABC.<br /> <br /> On a pure conventional basis, '''<u>the link will be made from child to parent</u>'''. This is practical as when we describe a component (like a DC/DC), the car it belongs to is quite likely already created as a Page, but the connectors composing the DC/DC less likely so. we would then be blocked in defining the DC/DC because we cannot create the connector (or same with the CAN message it generates). In reality, we will face quite often such situation that the associated object does not exist yet. The convention is not fixing all problems.<br /> <br /> ==== Pages or Categories? ====<br /> Categories helps grouping of similar Pages together. Quite often, we can consider a category (like BMW), but when using Properties, we cannot link them to categories. So, in such case, a Page is required. To avoid meaningless empty Pages, the following minimum information can be added:<br /> <br /> * A dynamic query listing all pages referring to this page, (possibly organized by category)<br /> * A button to call a form to create a component from that page (i.e. a component from BMW).<br /> * the rest of the page must of course be editable for content creator to capture and share their knowledge.<br /> <br /> === Categories ===<br /> At the time of writing, the following category structure exist: (in the absence of CategoryTree extension, doing my best to represent it):<br /> <br /> {| class="wikitable"<br /> ! Level 1 !! Level 2 !! Level 3 !! transferred<br /> |-<br /> | Basics || || ||x<br /> |-<br /> | Parts || Inverter || ||x<br /> |-<br /> | || Motor || || x<br /> |-<br /> | || Battery || || x<br /> |-<br /> | || Charger || Rapid Charging|| x<br /> |-<br /> | || DC/DC || || x<br /> |-<br /> | || HVJB (High Voltage Junction Box) || || x<br /> |-<br /> | || Contactor || || x<br /> |-<br /> | || PCB || || x<br /> |-<br /> | || CAN || || x<br /> |-<br /> | || LIN || || x<br /> |-<br /> | || ISA Shunt || || x<br /> |-<br /> | || Accelerator Pedals and Position Sensors || || x<br /> |-<br /> | || Gearbox || || x<br /> |-<br /> | || Gear Selectors || || x<br /> |-<br /> | || Power Steering || || x<br /> |-<br /> | || Water Pumps || || x<br /> |-<br /> | || Arduino || || x<br /> |-<br /> | || Adapter || || x<br /> |-<br /> |<br /> |Thermal Management<br /> |AC Compressor<br /> |x<br /> |-<br /> | || || Heater Coolant|| x<br /> |-<br /> |<br /> |<br /> |Heater Air<br /> |x<br /> |-<br /> |<br /> |HVAC<br /> |Coolant Fittings<br /> |x<br /> |-<br /> |<br /> |<br /> |Coolant Valve<br /> |x<br /> |-<br /> | || ESP32 || || x<br /> |-<br /> | || ESP8266 || || x<br /> |-<br /> | || ZombieVerter || || x<br /> |-<br /> | || VCU || || x<br /> |-<br /> | OEM Manufacturers || BMW || || x<br /> |-<br /> | || Bosch || || x<br /> |-<br /> | || Chevrolet || || x<br /> |-<br /> | || Ford || || x<br /> |-<br /> | || Honda || || x<br /> |-<br /> | || Hyundai || || x<br /> |-<br /> | || Isabellenhütte || || x<br /> |-<br /> | || Land Rover || || x<br /> |-<br /> | || Lexus || || x<br /> |-<br /> | || Mercedes-Benz || || x<br /> |-<br /> | || MG || || x<br /> |-<br /> | || Mitsubishi || || x<br /> |-<br /> | || Nissan || || x<br /> |-<br /> | || Opel || || x<br /> |-<br /> | || Peugeot || || x<br /> |-<br /> | || Renault || || x<br /> |-<br /> | || Tesla || || x<br /> |-<br /> | || Toyota || || x<br /> |-<br /> | || VAG (Volkswagen Audi Group) || VW || x<br /> |-<br /> | || Vauxhall || || x<br /> |-<br /> | || Volvo || || x<br /> |-<br /> | Charging Systems || ChaDeMo || Chademo with Zombieverter || x<br /> |-<br /> | || CCS || || x<br /> |-<br /> | || Charge Ports || || x<br /> |-<br /> | || Fast Charging || || x<br /> |-<br /> | Conversions || Mechanical || Parts || x<br /> |-<br /> | || OpenInverter Projects || || x<br /> |-<br /> | || OEM Repurposing || || <br /> |-<br /> | || Obsolete || || <br /> |-<br /> | Accessories || || ||x<br /> |-<br /> | Education || || ||<br /> |-<br /> | Request for Review || || ||x<br /> |-<br /> | Troubleshoot || || ||<br /> |-<br /> | Webasto || || ||x<br /> |-<br /> |Legalities<br /> |<br /> |<br /> |x<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |}<br /> <br /> I am proposing to shuffle the categories in the following structure - bold/italic names are to be created<br /> <br /> ==== Manufacturers categories and structure ====<br /> the structure is meant to only identifies the group of brand (as they will likely be sharing components). Therefore, if a brand leaves a group to join another, a distinct brand category must be created.<br /> <br /> Model names (a specific category - see below) is attached to the brand related to its parent group (i.e. Opel Ampera is linked to GM, Opel Moka is linked to Stellantis). this structure gives us the flexibility to manage changing alliances/holdings over time. <br /> <br /> Cars are being sold with different names (Opel/Vauxhall, Renault/Mitsubishi etc), therefore, while the Page Name may refer to a specific brand-model combination, the car model <u>shall not</u> be a category on its own.<br /> <br /> The OEM Manufacturers shall include the groups that are delivering parts to car makers (Bosch, Magnetti Marelli etc)<br /> {| class="wikitable"<br /> |+<br /> !Top level<br /> !Group<br /> !Brand<br /> !Note<br /> |-<br /> |OEM<br /> |'''''BMW Group'''''<br /> |BMW<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Mini'''''<br /> |<br /> |-<br /> |<br /> |'''''General Motors'''''<br /> |Chevrolet<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Opel (<2017)'''''<br /> |the Opel Ampera was still under GM, so it is a completely different affiliation than today<br /> |-<br /> |<br /> |'''''Stellantis'''''<br /> |Opel (2017-)<br /> |the new ones<br /> |-<br /> |<br /> |<br /> |Vauxhall<br /> |<br /> |-<br /> |<br /> |<br /> |Peugeot<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Citroen'''''<br /> |<br /> |-<br /> |<br /> |'''''Toyota Motor Corporation'''''<br /> |Toyota<br /> |<br /> |-<br /> |<br /> |<br /> |Lexus<br /> |<br /> |-<br /> |<br /> |'''''Hyundai Motor Group'''''<br /> |Hyundai<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Kia'''''<br /> |<br /> |-<br /> |<br /> |'''''Renault-Nissan-Mitsubishi Alliance'''''<br /> |Mitsubishi<br /> |<br /> |-<br /> |<br /> |<br /> |Renault<br /> |<br /> |-<br /> |<br /> |<br /> |Nissan<br /> |<br /> |-<br /> |<br /> |'''''Ford Motor Corporation'''''<br /> |Ford<br /> |<br /> |-<br /> |<br /> |'''''Tata Motors'''''<br /> |Land Rover<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Jaguar'''''<br /> |<br /> |-<br /> |<br /> |VAG (Volkswagen Audi Group)<br /> |'''''Volkswagen'''''<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Audi'''''<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Skoda'''''<br /> |<br /> |-<br /> |<br /> |'''''Geely Holding Group'''''<br /> |Volvo<br /> |<br /> |-<br /> |<br /> |'''''SAIC Motor Europe'''''<br /> |MG<br /> |<br /> |-<br /> |<br /> |Honda<br /> |<br /> |<br /> |-<br /> |<br /> |Bosch<br /> |<br /> |<br /> |-<br /> |<br /> |Isabellenhütte<br /> |<br /> |<br /> |-<br /> |<br /> |Mercedes-Benz<br /> |<br /> |<br /> |-<br /> |<br /> |'''''BYD'''''<br /> |<br /> |<br /> |-<br /> |<br /> |Tesla<br /> |<br /> |<br /> |-<br /> |<br /> |Webasto<br /> |<br /> |moved under OEM Manufacturers<br /> |-<br /> |<br /> |'''''TE Connectivity'''''<br /> |<br /> |build connectors (notably for BMW)<br /> |-<br /> |<br /> |'''''Aptiv'''''<br /> |<br /> |build connectors (notably for Nissan) - ex Delphi (ex GM :-) )<br /> |-<br /> |<br /> |'''''Molex'''''<br /> |<br /> |build connectors (notably for Tesla)<br /> |-<br /> |<br /> |'''''Sumitomo'''''<br /> |<br /> |build connectors (notably for Mitsubishi)<br /> |-<br /> |<br /> |'''''Hirose'''''<br /> |<br /> |build connectors (notably for Mitsubishi)<br /> |-<br /> |<br /> |'''''Dilong'''''<br /> |<br /> |build chargers (at the very least)<br /> |-<br /> |<br /> |Eltek<br /> |<br /> |build chargers (at the very least)<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |}<br /> <br /> ==== Parts (Components) ====<br /> {| class="wikitable"<br /> !Top level<br /> !2nd level<br /> !3rd level<br /> !Note<br /> |-<br /> |Parts<br /> |Inverter<br /> |<br /> |<br /> |-<br /> |<br /> |Motor<br /> |<br /> |<br /> |-<br /> |<br /> |Brake Assist<br /> |<br /> |<br /> |-<br /> |<br /> |'''''Battery Packs'''''<br /> |'''''Battery modules'''''<br /> |this is a split of the battery category<br /> |-<br /> |<br /> |<br /> |BMS<br /> |moved under Battery packs<br /> |-<br /> |<br /> |<br /> |Contactor<br /> |where SBOX, VBOX and Isabellenhutte should belong. moved under battery packs<br /> |-<br /> |<br /> |DC/DC<br /> |<br /> |<br /> |-<br /> |<br /> |HVJB (High Voltage Junction Box)<br /> |<br /> |<br /> |-<br /> |<br /> |Accelerator Pedals and Position Sensors<br /> |<br /> |<br /> |-<br /> |<br /> |Gearbox<br /> |<br /> |<br /> |-<br /> |<br /> |Gear Selectors<br /> |<br /> |<br /> |-<br /> |<br /> |Power Steering<br /> |<br /> |<br /> |-<br /> |<br /> |Charging Systems<br /> |ChaDeMo<br /> |<br /> |-<br /> |<br /> |<br /> |CCS<br /> |<br /> |-<br /> |<br /> |<br /> |Charge Ports<br /> |<br /> |-<br /> |<br /> |<br /> |Fast Charging<br /> |moved out of charger and under charging systems<br /> |-<br /> |<br /> |<br /> |Charger<br /> |moved under charging systems<br /> |-<br /> |<br /> |Thermal Management<br /> |AC Compressor<br /> |<br /> |-<br /> |<br /> |<br /> |Heater Coolant<br /> |<br /> |-<br /> |<br /> |<br /> |Heater Air<br /> |<br /> |-<br /> |<br /> |<br /> |Water Pumps<br /> |<br /> |-<br /> |<br /> |<br /> |HVAC<br /> |<br /> |-<br /> |<br /> |<br /> |Coolant Fittings<br /> |<br /> |-<br /> |<br /> |<br /> |Coolant Valve<br /> |<br /> |-<br /> |<br /> |'''''Connectors'''''<br /> |<br /> |<br /> |-<br /> |<br /> |'''''Cables'''''<br /> |<br /> |<br /> |-<br /> |<br /> |'''''Instruments'''''<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |'''''Mechanical Adapters'''''<br /> |CAD<br /> |mechanical and adapter categories to be merged as "mechanical adapters"<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |}<br /> <br /> ==== Software, Electronics and Protocols ====<br /> {| class="wikitable"<br /> !Top level<br /> !2nd level<br /> !3rd level<br /> !Note<br /> |-<br /> |'''Electronics'''<br /> |VCU<br /> |ZombieVerter<br /> |<br /> |-<br /> |<br /> |<br /> |OpenInverter<br /> |<br /> |-<br /> |<br /> |'''''chipsets'''''<br /> |ESP32<br /> |<br /> |-<br /> |<br /> |<br /> |ESP8266<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |PCB<br /> |Arduino<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |Protocols<br /> |CAN<br /> |'''''CANID'''''<br /> |category to define the CAN messages<br /> |-<br /> |<br /> |LIN<br /> |<br /> |<br /> |-<br /> |<br /> |'''''Ethernet'''''<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |}<br /> <br /> ==== Other categories ====<br /> {| class="wikitable"<br /> !Top level<br /> !2nd level<br /> !3rd level<br /> !Note<br /> |-<br /> |Basics<br /> |Tutorials<br /> |<br /> |covers the necessary understanding required before envisaging a conversion project (maybe merge the 2 categories?)<br /> Tutorial to be merged with Tutorials<br /> |-<br /> |<br /> |Resource<br /> |<br /> |merge with Introduction?<br /> |-<br /> |<br /> |FAQ<br /> |<br /> |<br /> |-<br /> |Conversion<br /> |<br /> |<br /> |ongoing and succesful conversion projects (the VCU should be a mandatory sub-category I think)<br /> |-<br /> |Legalities<br /> |<br /> |<br /> |<br /> |}<br /> <br /> ==== Proposed for deletion (category, not content!) ====<br /> {| class="wikitable"<br /> !Name<br /> !Number of Pages<br /> !Reason for request for deletion<br /> |-<br /> |Accessories<br /> |0<br /> |what is mandatory? What is an accessory? better consider they are parts. the category has 0 page so far<br /> |-<br /> |Hardware<br /> |0<br /> |better call it parts - 0 page<br /> |-<br /> |ISA Shunt<br /> |1<br /> |this should not be a category on its own but a page of category "connector"<br /> |-<br /> |Chademo with Zombieverter<br /> |0<br /> |should be part of category chademo<br /> |-<br /> |Request for Review<br /> |1<br /> |this seldom used<br /> |-<br /> |OpenInverter Projects<br /> |<br /> |better have a combination of the "conversion" and the corresponding VCU category?<br /> |-<br /> |Introduction<br /> |<br /> |merge with Resource?<br /> |-<br /> |DEAD<br /> |1<br /> |possibly wrongly created in the first place<br /> |-<br /> |Delta<br /> |1<br /> |<br /> |-<br /> |General Tesla FAQ<br /> |1<br /> |should be a page part of category FAQ, not a category on its own.<br /> |}<br /> <br /> === Templates structure ===<br /> the intent is that for some content that would fit a given category, an associated template and form is being created. Not all pages must be created like that, and it is quite possible that such templated pages must be created when a certain maturity level is being reached. For those selected categories, the associated object and data properties must be identified. It is likely that some will be resused throughout different type of objects (any physical component has dimension and weight for instance).<br /> <br /> I have identified the following categories that are not created yet and which are useful (so as not to mess with any contributors' work at this stage)<br /> <br /> - Parts/Connectors<br /> <br /> - Parts/Cables<br /> <br /> - Protocols/CAN/CANID<br /> <br /> ==== Connectors ====<br /> <br /> ===== Page Name Structure: =====<br /> the name is composed of 4 components <br /> {| class="wikitable"<br /> |+<br /> !<br /> !Mandatory<br /> !Remarks<br /> |-<br /> !Manufacturer<br /> |yes<br /> |<br /> |-<br /> !Family<br /> |yes<br /> |<br /> |-<br /> !Model<br /> |no<br /> |<br /> |-<br /> !header/Plug<br /> |yes<br /> |header: connects to a physical component<br /> <br /> plug: connects to a cable<br /> |}<br /> Manufacturer - family - specific model - header/plug<br /> <br /> * ''Examples:''<br /> ** ''Aptiv - SHIELDPACK HV APEX280 SB - Plug''<br /> <br /> ===== Infobox content: =====<br /> {| class="wikitable"<br /> |+<br /> !PropertyName<br /> !Label (friendly name)<br /> !Associated Object or Data<br /> !single/multiple<br /> !Mandatory/Optional<br /> !Comments<br /> |-<br /> |HasImage.Page<br /> |Image<br /> |Page for in the File: namespace<br /> |single<br /> |Optional<br /> |Multiple images can be used for an object, but having one that serves inot the infobox, which can tell also be used for visual searches (imagine you do not know what type of connector you have, you can look at a visual gallery to find out which one you have and the associated relevant information)<br /> The image display will be constrained in the form for a given size.<br /> |-<br /> |IsProducedBy.Page<br /> |Manufacturer<br /> |Page<br /> |single<br /> |Optional<br /> |Link the component to its manufacturer<br /> |-<br /> |UsedIn.Page<br /> |Used in<br /> |Page<br /> |multiple<br /> |Optional<br /> |allow to link the parent components/vehicles which are using this component<br /> |-<br /> |IsMatedWith.Page<br /> |Mating connector<br /> |Page<br /> |single<br /> |Optional<br /> |When available, define which connector is used to connect to it.<br /> |-<br /> |IsHighVoltage.Boolean<br /> |High Voltage<br /> |Boolean<br /> |single<br /> |Mandatory<br /> |defines if HV or not<br /> |-<br /> |HasInterlock.Boolean<br /> |Interlock Present<br /> |Boolean<br /> |single<br /> |Mandatory<br /> |defines if interlock pins are present or not<br /> |-<br /> |HasColour.Text<br /> |Main colour<br /> |Text<br /> |single<br /> |Mandatory<br /> |describe the most prevalent colour of the connector. it can be useful for narrowing down searches. the list of colour should be constrained to avoid having "Deep sea blue" or "amethist" type of colours...<br /> |-<br /> |HasReference.Text<br /> |References<br /> |Text<br /> |multiple<br /> |optional<br /> |<br /> |-<br /> |HasTerminals.Number<br /> |number of terminals (pins)<br /> |Number<br /> |single<br /> |Mandatory<br /> |number of pins or holes on the connectors, WITHOUT counting the interlock<br /> |-<br /> |HasDatasheet.URL<br /> |Link to Datasheet<br /> |URL<br /> |single<br /> |optional<br /> |<br /> |}<br /> <br /> ===== Main section content =====<br /> <br /> ==== CANID Message ====<br /> {| class="wikitable"<br /> |+<br /> !<br /> !<br /> !<br /> !<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |}</div>

Powercontrol https://openinverter.org/wiki/index.php?title=Content_Management&diff=5778 Content Management 2025-05-11T08:45:58Z

<p>Powercontrol: in the middle of describing the connectors content</p> <hr /> <div>'''DRAFT - DRAFT - DRAFT'''<br /> <br /> the objective of this page is to explain how the content of the wiki page could be structured using Semantic for Mediawiki (SMW) to build a scalable and object-based wiki (for search and relation-building aspects) and still keeping the freedom for authors to create their content. There needs to be a trade-off to be found between freedom and structure.<br /> <br /> === Why Semantic for Mediawiki? ===<br /> SMW allows to have a form-based creation of objects. the form asks the users some key information then create the corresponding page and render the entered information in a consistent way, assign the category accordingly etc.<br /> <br /> Because the page created is based on a template, changing the template modifies the instantiation of the created pages. <br /> <br /> SMW also allows to create dynamic queries inside pages. The content will be modified based on other pages content. this is a powerful manner to make references to other pages without doing manual maintenance of the page. A practical and basic example would be that if the query below was inserted a page creation (a template being called by a form):<br /> <br /> <nowiki>{{#ask:<br /> [[FoundIn.Page::{{PAGENAME}}]]<br /> | format=list<br /> | link=all<br /> }}</nowiki><br /> The page content will update itself to list all other pages that refer to this new page. There are much more granular type of queries to be done (including on categories) which then become really handy.<br /> === General Principles and Naming Convention ===<br /> SMW uses multiple notions. They are key to be used properly for good use.<br /> <br /> ==== Type of Mediawiki Objects and their usage ====<br /> {| class="wikitable"<br /> |+<br /> !Object<br /> !Usage<br /> !Naming Convention<br /> !Example<br /> |-<br /> |'''Page'''<br /> |the core component of the wiki and what readers are consuming. By default, there is no hierarchical structure of pages - and categories are the better way for structuring a wiki<br /> |each Word is start with a capital letter. Spaces and brackets are allowed. mutiple words are recommended to be separated by a space (mediawiki uses underscore instead of %20 for URL)<br /> '''''Title Case'''''<br /> |Nissan Leaf (2010-2017)<br /> |-<br /> |'''Category'''<br /> |the categories are part of the generic Mediawiki structure. its reflects a categorization or labeling of pages. Categories can be nested which are useful to reflect a structure of "component of" and for "is a subtype of". Multiple categories can be assigned to page, hence it can provide multiple view at once. A dedicated section of this page will cover their aspects.<br /> There are cases where it is not obvious whether a property or a category makes more sense. one does not prevent the other, by the way.<br /> |as the wiki already as categories created and they use naming similar to Page, the categories will further be named the same way.<br /> Ideally, categories shall be written in <u>plural form</u> (because it is a grouping of x) <br /> '''''Title Case (in plural)'''''<br /> |Batteries<br /> Connectors<br /> |-<br /> |'''Property'''<br /> |SMW specific - it defines a relation between 2 objects, or assign an attribute to an object. the target (called [[Special:Types]]) can be a list, another page. When defining a property, it would make sense to refer to a specific category of object (for instance, FoundIn would be referring to a Vehicle or a Component), but the type of object we can refer to are Pages, Numbers, Date,... nothing to do with category. <br /> |'''''UpperCamelCase.DestinationObjectType''''' or '''''UpperCamelCase.DestinationAttributeType'''''<br /> |FoundIn.Page<br /> HasWeight.Qantity<br /> |-<br /> |'''Template'''<br /> |SMW specific - defines which properties values shall be defined at the creation of an object. Not all pages must be created using templates, but objects which have relations between themselves are best created using templates.<br /> |the template name shall refer to a corresponding category name in <u>singular</u>, and the template shall enforce that category at page creation.<br /> '''''T/UpperCamelCase.OutputFormat'''''<br /> |T/Connector.Infobox<br /> T/Battery.PlainText<br /> |-<br /> |'''Form'''<br /> |SMW specific - A Form is an helper for the author to create a templated object. The form allows to create a consistent visual structure to pages<br /> |'''''F/UpperCamelCase''''' - the Form refers to a corresponding Template, but the output format will not be referred to in the form name.<br /> A form can also call multiple templates - in such case its name will refer to the first one<br /> |F/Connector<br /> F/Battery<br /> |}<br /> <br /> ==== Hierarchical relationship ====<br /> There are often 2 possibilities for defining relationship between objects, you can go from parent to child, or from child to parent. <br /> <br /> In practical manner, I can define from a DC/DC that it is a component of the vehicle XYZ, or from that vehicle, that it uses the component DC/DC ABC.<br /> <br /> On a pure conventional basis, '''<u>the link will be made from child to parent</u>'''. This is practical as when we describe a component (like a DC/DC), the car it belongs to is quite likely already created as a Page, but the connectors composing the DC/DC less likely so. we would then be blocked in defining the DC/DC because we cannot create the connector (or same with the CAN message it generates). In reality, we will face quite often such situation that the associated object does not exist yet. The convention is not fixing all problems.<br /> <br /> ==== Pages or Categories? ====<br /> Categories helps grouping of similar Pages together. Quite often, we can consider a category (like BMW), but when using Properties, we cannot link them to categories. So, in such case, a Page is required. To avoid meaningless empty Pages, the following minimum information can be added:<br /> <br /> * A dynamic query listing all pages referring to this page, (possibly organized by category)<br /> * A button to call a form to create a component from that page (i.e. a component from BMW).<br /> * the rest of the page must of course be editable for content creator to capture and share their knowledge.<br /> <br /> === Categories ===<br /> At the time of writing, the following category structure exist: (in the absence of CategoryTree extension, doing my best to represent it):<br /> <br /> {| class="wikitable"<br /> ! Level 1 !! Level 2 !! Level 3 !! transferred<br /> |-<br /> | Basics || || ||x<br /> |-<br /> | Parts || Inverter || ||x<br /> |-<br /> | || Motor || || x<br /> |-<br /> | || Battery || || x<br /> |-<br /> | || Charger || Rapid Charging|| x<br /> |-<br /> | || DC/DC || || x<br /> |-<br /> | || HVJB (High Voltage Junction Box) || || x<br /> |-<br /> | || Contactor || || x<br /> |-<br /> | || PCB || || x<br /> |-<br /> | || CAN || || x<br /> |-<br /> | || LIN || || x<br /> |-<br /> | || ISA Shunt || || x<br /> |-<br /> | || Accelerator Pedals and Position Sensors || || x<br /> |-<br /> | || Gearbox || || x<br /> |-<br /> | || Gear Selectors || || x<br /> |-<br /> | || Power Steering || || x<br /> |-<br /> | || Water Pumps || || x<br /> |-<br /> | || Arduino || || x<br /> |-<br /> | || Adapter || || x<br /> |-<br /> |<br /> |Thermal Management<br /> |AC Compressor<br /> |x<br /> |-<br /> | || || Heater Coolant|| x<br /> |-<br /> |<br /> |<br /> |Heater Air<br /> |x<br /> |-<br /> |<br /> |HVAC<br /> |Coolant Fittings<br /> |x<br /> |-<br /> |<br /> |<br /> |Coolant Valve<br /> |x<br /> |-<br /> | || ESP32 || || x<br /> |-<br /> | || ESP8266 || || x<br /> |-<br /> | || ZombieVerter || || x<br /> |-<br /> | || VCU || || x<br /> |-<br /> | OEM Manufacturers || BMW || || x<br /> |-<br /> | || Bosch || || x<br /> |-<br /> | || Chevrolet || || x<br /> |-<br /> | || Ford || || x<br /> |-<br /> | || Honda || || x<br /> |-<br /> | || Hyundai || || x<br /> |-<br /> | || Isabellenhütte || || x<br /> |-<br /> | || Land Rover || || x<br /> |-<br /> | || Lexus || || x<br /> |-<br /> | || Mercedes-Benz || || x<br /> |-<br /> | || MG || || x<br /> |-<br /> | || Mitsubishi || || x<br /> |-<br /> | || Nissan || || x<br /> |-<br /> | || Opel || || x<br /> |-<br /> | || Peugeot || || x<br /> |-<br /> | || Renault || || x<br /> |-<br /> | || Tesla || || x<br /> |-<br /> | || Toyota || || x<br /> |-<br /> | || VAG (Volkswagen Audi Group) || VW || x<br /> |-<br /> | || Vauxhall || || x<br /> |-<br /> | || Volvo || || x<br /> |-<br /> | Charging Systems || ChaDeMo || Chademo with Zombieverter || x<br /> |-<br /> | || CCS || || x<br /> |-<br /> | || Charge Ports || || x<br /> |-<br /> | || Fast Charging || || x<br /> |-<br /> | Conversions || Mechanical || Parts || x<br /> |-<br /> | || OpenInverter Projects || || x<br /> |-<br /> | || OEM Repurposing || || <br /> |-<br /> | || Obsolete || || <br /> |-<br /> | Accessories || || ||x<br /> |-<br /> | Education || || ||<br /> |-<br /> | Request for Review || || ||x<br /> |-<br /> | Troubleshoot || || ||<br /> |-<br /> | Webasto || || ||x<br /> |-<br /> |Legalities<br /> |<br /> |<br /> |x<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |}<br /> <br /> I am proposing to shuffle the categories in the following structure - bold/italic names are to be created<br /> <br /> ==== Manufacturers categories and structure ====<br /> the structure is meant to only identifies the group of brand (as they will likely be sharing components). Therefore, if a brand leaves a group to join another, a distinct brand category must be created.<br /> <br /> Model names (a specific category - see below) is attached to the brand related to its parent group (i.e. Opel Ampera is linked to GM, Opel Moka is linked to Stellantis). this structure gives us the flexibility to manage changing alliances/holdings over time. <br /> <br /> Cars are being sold with different names (Opel/Vauxhall, Renault/Mitsubishi etc), therefore, while the Page Name may refer to a specific brand-model combination, the car model <u>shall not</u> be a category on its own.<br /> <br /> The OEM Manufacturers shall include the groups that are delivering parts to car makers (Bosch, Magnetti Marelli etc)<br /> {| class="wikitable"<br /> |+<br /> !Top level<br /> !Group<br /> !Brand<br /> !Note<br /> |-<br /> |OEM<br /> |'''''BMW Group'''''<br /> |BMW<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Mini'''''<br /> |<br /> |-<br /> |<br /> |'''''General Motors'''''<br /> |Chevrolet<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Opel (<2017)'''''<br /> |the Opel Ampera was still under GM, so it is a completely different affiliation than today<br /> |-<br /> |<br /> |'''''Stellantis'''''<br /> |Opel (2017-)<br /> |the new ones<br /> |-<br /> |<br /> |<br /> |Vauxhall<br /> |<br /> |-<br /> |<br /> |<br /> |Peugeot<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Citroen'''''<br /> |<br /> |-<br /> |<br /> |'''''Toyota Motor Corporation'''''<br /> |Toyota<br /> |<br /> |-<br /> |<br /> |<br /> |Lexus<br /> |<br /> |-<br /> |<br /> |'''''Hyundai Motor Group'''''<br /> |Hyundai<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Kia'''''<br /> |<br /> |-<br /> |<br /> |'''''Renault-Nissan-Mitsubishi Alliance'''''<br /> |Mitsubishi<br /> |<br /> |-<br /> |<br /> |<br /> |Renault<br /> |<br /> |-<br /> |<br /> |<br /> |Nissan<br /> |<br /> |-<br /> |<br /> |'''''Ford Motor Corporation'''''<br /> |Ford<br /> |<br /> |-<br /> |<br /> |'''''Tata Motors'''''<br /> |Land Rover<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Jaguar'''''<br /> |<br /> |-<br /> |<br /> |VAG (Volkswagen Audi Group)<br /> |'''''Volkswagen'''''<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Audi'''''<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Skoda'''''<br /> |<br /> |-<br /> |<br /> |'''''Geely Holding Group'''''<br /> |Volvo<br /> |<br /> |-<br /> |<br /> |'''''SAIC Motor Europe'''''<br /> |MG<br /> |<br /> |-<br /> |<br /> |Honda<br /> |<br /> |<br /> |-<br /> |<br /> |Bosch<br /> |<br /> |<br /> |-<br /> |<br /> |Isabellenhütte<br /> |<br /> |<br /> |-<br /> |<br /> |Mercedes-Benz<br /> |<br /> |<br /> |-<br /> |<br /> |'''''BYD'''''<br /> |<br /> |<br /> |-<br /> |<br /> |Tesla<br /> |<br /> |<br /> |-<br /> |<br /> |Webasto<br /> |<br /> |moved under OEM Manufacturers<br /> |-<br /> |<br /> |'''''TE Connectivity'''''<br /> |<br /> |build connectors (notably for BMW)<br /> |-<br /> |<br /> |'''''Aptiv'''''<br /> |<br /> |build connectors (notably for Nissan) - ex Delphi (ex GM :-) )<br /> |-<br /> |<br /> |'''''Molex'''''<br /> |<br /> |build connectors (notably for Tesla)<br /> |-<br /> |<br /> |'''''Sumitomo'''''<br /> |<br /> |build connectors (notably for Mitsubishi)<br /> |-<br /> |<br /> |'''''Hirose'''''<br /> |<br /> |build connectors (notably for Mitsubishi)<br /> |-<br /> |<br /> |'''''Dilong'''''<br /> |<br /> |build chargers (at the very least)<br /> |-<br /> |<br /> |Eltek<br /> |<br /> |build chargers (at the very least)<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |}<br /> <br /> ==== Parts (Components) ====<br /> {| class="wikitable"<br /> !Top level<br /> !2nd level<br /> !3rd level<br /> !Note<br /> |-<br /> |Parts<br /> |Inverter<br /> |<br /> |<br /> |-<br /> |<br /> |Motor<br /> |<br /> |<br /> |-<br /> |<br /> |Brake Assist<br /> |<br /> |<br /> |-<br /> |<br /> |'''''Battery Packs'''''<br /> |'''''Battery modules'''''<br /> |this is a split of the battery category<br /> |-<br /> |<br /> |<br /> |BMS<br /> |moved under Battery packs<br /> |-<br /> |<br /> |<br /> |Contactor<br /> |where SBOX, VBOX and Isabellenhutte should belong. moved under battery packs<br /> |-<br /> |<br /> |DC/DC<br /> |<br /> |<br /> |-<br /> |<br /> |HVJB (High Voltage Junction Box)<br /> |<br /> |<br /> |-<br /> |<br /> |Accelerator Pedals and Position Sensors<br /> |<br /> |<br /> |-<br /> |<br /> |Gearbox<br /> |<br /> |<br /> |-<br /> |<br /> |Gear Selectors<br /> |<br /> |<br /> |-<br /> |<br /> |Power Steering<br /> |<br /> |<br /> |-<br /> |<br /> |Charging Systems<br /> |ChaDeMo<br /> |<br /> |-<br /> |<br /> |<br /> |CCS<br /> |<br /> |-<br /> |<br /> |<br /> |Charge Ports<br /> |<br /> |-<br /> |<br /> |<br /> |Fast Charging<br /> |moved out of charger and under charging systems<br /> |-<br /> |<br /> |<br /> |Charger<br /> |moved under charging systems<br /> |-<br /> |<br /> |Thermal Management<br /> |AC Compressor<br /> |<br /> |-<br /> |<br /> |<br /> |Heater Coolant<br /> |<br /> |-<br /> |<br /> |<br /> |Heater Air<br /> |<br /> |-<br /> |<br /> |<br /> |Water Pumps<br /> |<br /> |-<br /> |<br /> |<br /> |HVAC<br /> |<br /> |-<br /> |<br /> |<br /> |Coolant Fittings<br /> |<br /> |-<br /> |<br /> |<br /> |Coolant Valve<br /> |<br /> |-<br /> |<br /> |'''''Connectors'''''<br /> |<br /> |<br /> |-<br /> |<br /> |'''''Cables'''''<br /> |<br /> |<br /> |-<br /> |<br /> |'''''Instruments'''''<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |'''''Mechanical Adapters'''''<br /> |CAD<br /> |mechanical and adapter categories to be merged as "mechanical adapters"<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |}<br /> <br /> ==== Software, Electronics and Protocols ====<br /> {| class="wikitable"<br /> !Top level<br /> !2nd level<br /> !3rd level<br /> !Note<br /> |-<br /> |'''Electronics'''<br /> |VCU<br /> |ZombieVerter<br /> |<br /> |-<br /> |<br /> |<br /> |OpenInverter<br /> |<br /> |-<br /> |<br /> |'''''chipsets'''''<br /> |ESP32<br /> |<br /> |-<br /> |<br /> |<br /> |ESP8266<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |PCB<br /> |Arduino<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |Protocols<br /> |CAN<br /> |'''''CANID'''''<br /> |category to define the CAN messages<br /> |-<br /> |<br /> |LIN<br /> |<br /> |<br /> |-<br /> |<br /> |'''''Ethernet'''''<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |}<br /> <br /> ==== Other categories ====<br /> {| class="wikitable"<br /> !Top level<br /> !2nd level<br /> !3rd level<br /> !Note<br /> |-<br /> |Basics<br /> |Tutorials<br /> |<br /> |covers the necessary understanding required before envisaging a conversion project (maybe merge the 2 categories?)<br /> Tutorial to be merged with Tutorials<br /> |-<br /> |<br /> |Resource<br /> |<br /> |merge with Introduction?<br /> |-<br /> |<br /> |FAQ<br /> |<br /> |<br /> |-<br /> |Conversion<br /> |<br /> |<br /> |ongoing and succesful conversion projects (the VCU should be a mandatory sub-category I think)<br /> |-<br /> |Legalities<br /> |<br /> |<br /> |<br /> |}<br /> <br /> ==== Proposed for deletion (category, not content!) ====<br /> {| class="wikitable"<br /> !Name<br /> !Number of Pages<br /> !Reason for request for deletion<br /> |-<br /> |Accessories<br /> |0<br /> |what is mandatory? What is an accessory? better consider they are parts. the category has 0 page so far<br /> |-<br /> |Hardware<br /> |0<br /> |better call it parts - 0 page<br /> |-<br /> |ISA Shunt<br /> |1<br /> |this should not be a category on its own but a page of category "connector"<br /> |-<br /> |Chademo with Zombieverter<br /> |0<br /> |should be part of category chademo<br /> |-<br /> |Request for Review<br /> |1<br /> |this seldom used<br /> |-<br /> |OpenInverter Projects<br /> |<br /> |better have a combination of the "conversion" and the corresponding VCU category?<br /> |-<br /> |Introduction<br /> |<br /> |merge with Resource?<br /> |-<br /> |DEAD<br /> |1<br /> |possibly wrongly created in the first place<br /> |-<br /> |Delta<br /> |1<br /> |<br /> |-<br /> |General Tesla FAQ<br /> |1<br /> |should be a page part of category FAQ, not a category on its own.<br /> |}<br /> <br /> === Templates structure ===<br /> the intent is that for some content that would fit a given category, an associated template and form is being created. Not all pages must be created like that, and it is quite possible that such templated pages must be created when a certain maturity level is being reached. For those selected categories, the associated object and data properties must be identified. It is likely that some will be resused throughout different type of objects (any physical component has dimension and weight for instance).<br /> <br /> I have identified the following categories that are not created yet and which are useful (so as not to mess with any contributors' work at this stage)<br /> <br /> - Parts/Connectors<br /> <br /> - Parts/Cables<br /> <br /> - Protocols/CAN/CANID<br /> <br /> ==== Connectors ====<br /> <br /> ===== Page Name Structure: =====<br /> the name is composed of 4 components <br /> {| class="wikitable"<br /> |+<br /> !<br /> !Mandatory<br /> !Remarks<br /> |-<br /> !Manufacturer<br /> |yes<br /> |<br /> |-<br /> !Family<br /> |yes<br /> |<br /> |-<br /> !Model<br /> |no<br /> |<br /> |-<br /> !header/Plug<br /> |yes<br /> |header: connects to a physical component<br /> <br /> plug: connects to a cable<br /> |}<br /> Manufacturer - family - specific model - header/plug<br /> <br /> * ''Examples:''<br /> ** ''Aptiv - SHIELDPACK HV APEX280 SB - Plug''<br /> <br /> ===== Infobox content: =====<br /> {| class="wikitable"<br /> |+<br /> !PropertyName<br /> !Label (friendly name)<br /> !Associated Object or Data<br /> !single/multiple<br /> !Mandatory/Optional<br /> !Comments<br /> |-<br /> |HasImage.Page<br /> |Image<br /> |Page for in the File: namespace<br /> |single<br /> |Optional<br /> |Multiple images can be used for an object, but having one that serves inot the infobox, which can tell also be used for visual searches (imagine you do not know what type of connector you have, you can look at a visual gallery to find out which one you have and the associated relevant information)<br /> The image display will be constrained in the form for a given size.<br /> |-<br /> |IsProducedBy.Page<br /> |Manufacturer<br /> |Page<br /> |single<br /> |Optional<br /> |Link the component to its manufacturer<br /> |-<br /> |UsedIn.Page<br /> |Used in<br /> |Page<br /> |multiple<br /> |Optional<br /> |allow to link the parent components/vehicles which are using this component<br /> |-<br /> |IsMatedWith.Page<br /> |Mating connector<br /> |Page<br /> |single<br /> |Optional<br /> |When available, define which connector is used to connect to it.<br /> |-<br /> |IsHighVoltage.Boolean<br /> |High Voltage<br /> |Boolean<br /> |single<br /> |Mandatory<br /> |defines if HV or not<br /> |-<br /> |HasInterlock.Boolean<br /> |Interlock Present<br /> |Boolean<br /> |single<br /> |Mandatory<br /> |defines if interlock pins are present or not<br /> |-<br /> |HasColour.Text<br /> |Main colour<br /> |Text<br /> |single<br /> |Mandatory<br /> |describe the most prevalent colour of the connector. it can be useful for narrowing down searches. the list of colour should be constrained to avoid having "Deep sea blue" or "amethist" type of colours...<br /> |-<br /> |HasReference.Text<br /> |References<br /> |Text<br /> |multiple<br /> |optional<br /> |<br /> |-<br /> |HasTerminals.Number<br /> |number of terminals (pins)<br /> |Number<br /> |single<br /> |Mandatory<br /> |number of pins or holes on the connectors, WITHOUT counting the interlock<br /> |-<br /> |HasDatasheet.URL<br /> |Link to Datasheet<br /> |URL<br /> |single<br /> |optional<br /> |<br /> |}<br /> <br /> ==== Main section content ====<br /> <br /> ==== CANID Message ====<br /> {| class="wikitable"<br /> |+<br /> !<br /> !<br /> !<br /> !<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |}</div>

Powercontrol https://openinverter.org/wiki/index.php?title=Content_Management&diff=5777 Content Management 2025-05-11T07:55:33Z

<p>Powercontrol: work ongoing - defining the connectors template</p> <hr /> <div>'''DRAFT - DRAFT - DRAFT'''<br /> <br /> the objective of this page is to explain how the content of the wiki page could be structured using Semantic for Mediawiki (SMW) to build a scalable and object-based wiki (for search and relation-building aspects) and still keeping the freedom for authors to create their content. There needs to be a trade-off to be found between freedom and structure.<br /> <br /> === Why Semantic for Mediawiki? ===<br /> SMW allows to have a form-based creation of objects. the form asks the users some key information then create the corresponding page and render the entered information in a consistent way, assign the category accordingly etc.<br /> <br /> Because the page created is based on a template, changing the template modifies the instantiation of the created pages. <br /> <br /> SMW also allows to create dynamic queries inside pages. The content will be modified based on other pages content. this is a powerful manner to make references to other pages without doing manual maintenance of the page. A practical and basic example would be that if the query below was inserted a page creation (a template being called by a form):<br /> <br /> <nowiki>{{#ask:<br /> [[FoundIn.Page::{{PAGENAME}}]]<br /> | format=list<br /> | link=all<br /> }}</nowiki><br /> The page content will update itself to list all other pages that refer to this new page. There are much more granular type of queries to be done (including on categories) which then become really handy.<br /> === General Principles and Naming Convention ===<br /> SMW uses multiple notions. They are key to be used properly for good use.<br /> {| class="wikitable"<br /> |+<br /> !Object<br /> !Usage<br /> !Naming Convention<br /> !Example<br /> |-<br /> |'''Page'''<br /> |the core component of the wiki and what readers are consuming. By default, there is no hierarchical structure of pages - and categories are the better way for structuring a wiki<br /> |each Word is start with a capital letter. Spaces and brackets are allowed. mutiple words are recommended to be separated by a space (mediawiki uses underscore instead of %20 for URL)<br /> '''''Title Case'''''<br /> |Nissan Leaf (2010-2017)<br /> |-<br /> |'''Category'''<br /> |the categories are part of the generic Mediawiki structure. its reflects a categorization or labeling of pages. Categories can be nested which are useful to reflect a structure of "component of" and for "is a subtype of". Multiple categories can be assigned to page, hence it can provide multiple view at once. A dedicated section of this page will cover their aspects.<br /> There are cases where it is not obvious whether a property or a category makes more sense. one does not prevent the other, by the way.<br /> |as the wiki already as categories created and they use naming similar to Page, the categories will further be named the same way.<br /> Ideally, categories shall be written in <u>plural form</u> (because it is a grouping of x) <br /> '''''Title Case (in plural)'''''<br /> |Batteries<br /> Connectors<br /> |-<br /> |'''Property'''<br /> |SMW specific - it defines a relation between 2 objects, or assign an attribute to an object. the target (called [[Special:Types]]) can be a list, another page. When defining a property, it would make sense to refer to a specific category of object (for instance, FoundIn would be referring to a Vehicle or a Component), but the type of object we can refer to are Pages, Numbers, Date,... nothing to do with category. <br /> |'''''UpperCamelCase.DestinationObjectType''''' or '''''UpperCamelCase.DestinationAttributeType'''''<br /> |FoundIn.Page<br /> HasWeight.Qantity<br /> |-<br /> |'''Template'''<br /> |SMW specific - defines which properties values shall be defined at the creation of an object. Not all pages must be created using templates, but objects which have relations between themselves are best created using templates.<br /> |the template name shall refer to a corresponding category name in <u>singular</u>, and the template shall enforce that category at page creation.<br /> '''''T/UpperCamelCase.OutputFormat'''''<br /> |T/Connector.Infobox<br /> T/Battery.PlainText<br /> |-<br /> |'''Form'''<br /> |SMW specific - A Form is an helper for the author to create a templated object. The form allows to create a consistent visual structure to pages<br /> |'''''F/UpperCamelCase''''' - the Form refers to a corresponding Template, but the output format will not be referred to in the form name.<br /> A form can also call multiple templates - in such case its name will refer to the first one<br /> |F/Connector<br /> F/Battery<br /> |}<br /> <br /> === Hierarchical relationship ===<br /> There are often 2 possibilities for defining relationship between objects, you can go from parent to child, or from child to parent. <br /> <br /> In practical manner, I can define from a DC/DC that it is a component of the vehicle XYZ, or from that vehicle, that it uses the component DC/DC ABC.<br /> <br /> On a pure conventional basis, '''<u>the link will be made from child to parent</u>'''. This is practical as when we describe a component (like a DC/DC), the car it belongs to is quite likely already created as a Page, but the connectors composing the DC/DC less likely so. we would then be blocked in defining the DC/DC because we cannot create the connector (or same with the CAN message it generates). In reality, we will face quite often such situation that the associated object does not exist yet. The convention is not fixing all problems.<br /> <br /> === Categories ===<br /> At the time of writing, the following category structure exist: (in the absence of CategoryTree extension, doing my best to represent it):<br /> <br /> {| class="wikitable"<br /> ! Level 1 !! Level 2 !! Level 3 !! transferred<br /> |-<br /> | Basics || || ||x<br /> |-<br /> | Parts || Inverter || ||x<br /> |-<br /> | || Motor || || x<br /> |-<br /> | || Battery || || x<br /> |-<br /> | || Charger || Rapid Charging|| x<br /> |-<br /> | || DC/DC || || x<br /> |-<br /> | || HVJB (High Voltage Junction Box) || || x<br /> |-<br /> | || Contactor || || x<br /> |-<br /> | || PCB || || x<br /> |-<br /> | || CAN || || x<br /> |-<br /> | || LIN || || x<br /> |-<br /> | || ISA Shunt || || x<br /> |-<br /> | || Accelerator Pedals and Position Sensors || || x<br /> |-<br /> | || Gearbox || || x<br /> |-<br /> | || Gear Selectors || || x<br /> |-<br /> | || Power Steering || || x<br /> |-<br /> | || Water Pumps || || x<br /> |-<br /> | || Arduino || || x<br /> |-<br /> | || Adapter || || x<br /> |-<br /> |<br /> |Thermal Management<br /> |AC Compressor<br /> |x<br /> |-<br /> | || || Heater Coolant|| x<br /> |-<br /> |<br /> |<br /> |Heater Air<br /> |x<br /> |-<br /> |<br /> |HVAC<br /> |Coolant Fittings<br /> |x<br /> |-<br /> |<br /> |<br /> |Coolant Valve<br /> |x<br /> |-<br /> | || ESP32 || || x<br /> |-<br /> | || ESP8266 || || x<br /> |-<br /> | || ZombieVerter || || x<br /> |-<br /> | || VCU || || x<br /> |-<br /> | OEM Manufacturers || BMW || || x<br /> |-<br /> | || Bosch || || x<br /> |-<br /> | || Chevrolet || || x<br /> |-<br /> | || Ford || || x<br /> |-<br /> | || Honda || || x<br /> |-<br /> | || Hyundai || || x<br /> |-<br /> | || Isabellenhütte || || x<br /> |-<br /> | || Land Rover || || x<br /> |-<br /> | || Lexus || || x<br /> |-<br /> | || Mercedes-Benz || || x<br /> |-<br /> | || MG || || x<br /> |-<br /> | || Mitsubishi || || x<br /> |-<br /> | || Nissan || || x<br /> |-<br /> | || Opel || || x<br /> |-<br /> | || Peugeot || || x<br /> |-<br /> | || Renault || || x<br /> |-<br /> | || Tesla || || x<br /> |-<br /> | || Toyota || || x<br /> |-<br /> | || VAG (Volkswagen Audi Group) || VW || x<br /> |-<br /> | || Vauxhall || || x<br /> |-<br /> | || Volvo || || x<br /> |-<br /> | Charging Systems || ChaDeMo || Chademo with Zombieverter || x<br /> |-<br /> | || CCS || || x<br /> |-<br /> | || Charge Ports || || x<br /> |-<br /> | || Fast Charging || || x<br /> |-<br /> | Conversions || Mechanical || Parts || x<br /> |-<br /> | || OpenInverter Projects || || x<br /> |-<br /> | || OEM Repurposing || || <br /> |-<br /> | || Obsolete || || <br /> |-<br /> | Accessories || || ||x<br /> |-<br /> | Education || || ||<br /> |-<br /> | Request for Review || || ||x<br /> |-<br /> | Troubleshoot || || ||<br /> |-<br /> | Webasto || || ||x<br /> |-<br /> |Legalities<br /> |<br /> |<br /> |x<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |}<br /> <br /> <br /> I am proposing to shuffle the categories in such structure - bold/italic names are to be created<br /> <br /> ==== Manufacturers categories and structure ====<br /> the structure is meant to only identifies the group of brand (as they will likely be sharing components). Therefore, if a brand leaves a group to join another, a distinct brand category must be created.<br /> <br /> Model names (a specific category - see below) is attached to the brand related to its parent group (i.e. Opel Ampera is linked to GM, Opel Moka is linked to Stellantis). this structure gives us the flexibility to manage changing alliances/holdings over time. <br /> <br /> Cars are being sold with different names (Opel/Vauxhall, Renault/Mitsubishi etc), therefore, while the Page Name may refer to a specific brand-model combination, the car model <u>shall not</u> be a category on its own.<br /> <br /> The OEM Manufacturers shall include the groups that are delivering parts to car makers (Bosch, Magnetti Marelli etc)<br /> {| class="wikitable"<br /> |+<br /> !Top level<br /> !Group<br /> !Brand<br /> !Note<br /> |-<br /> |OEM Manufacturers<br /> |'''''BMW Group'''''<br /> |BMW<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Mini'''''<br /> |<br /> |-<br /> |<br /> |'''''General Motors'''''<br /> |Chevrolet<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Opel (<2017)'''''<br /> |the Opel Ampera was still under GM, so it is a completely different affiliation than today<br /> |-<br /> |<br /> |'''''Stellantis'''''<br /> |Opel (2017-)<br /> |the new ones<br /> |-<br /> |<br /> |<br /> |Vauxhall<br /> |<br /> |-<br /> |<br /> |<br /> |Peugeot<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Citroen'''''<br /> |<br /> |-<br /> |<br /> |'''''Toyota Motor Corporation'''''<br /> |Toyota<br /> |<br /> |-<br /> |<br /> |<br /> |Lexus<br /> |<br /> |-<br /> |<br /> |'''''Hyundai Motor Group'''''<br /> |Hyundai<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Kia'''''<br /> |<br /> |-<br /> |<br /> |'''''Renault-Nissan-Mitsubishi Alliance'''''<br /> |Mitsubishi<br /> |<br /> |-<br /> |<br /> |<br /> |Renault<br /> |<br /> |-<br /> |<br /> |<br /> |Nissan<br /> |<br /> |-<br /> |<br /> |'''''Ford Motor Corporation'''''<br /> |Ford<br /> |<br /> |-<br /> |<br /> |'''''Tata Motors'''''<br /> |Land Rover<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Jaguar'''''<br /> |<br /> |-<br /> |<br /> |VAG (Volkswagen Audi Group)<br /> |'''''Volkswagen'''''<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Audi'''''<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Skoda'''''<br /> |<br /> |-<br /> |<br /> |'''''Geely Holding Group'''''<br /> |Volvo<br /> |<br /> |-<br /> |<br /> |'''''SAIC Motor Europe'''''<br /> |MG<br /> |<br /> |-<br /> |<br /> |Honda<br /> |<br /> |<br /> |-<br /> |<br /> |Bosch<br /> |<br /> |<br /> |-<br /> |<br /> |Isabellenhütte<br /> |<br /> |<br /> |-<br /> |<br /> |Mercedes-Benz<br /> |<br /> |<br /> |-<br /> |<br /> |'''''BYD'''''<br /> |<br /> |<br /> |-<br /> |<br /> |Tesla<br /> |<br /> |<br /> |-<br /> |<br /> |Webasto<br /> |<br /> |moved under OEM Manufacturers<br /> |-<br /> |<br /> |'''''TE Connectivity'''''<br /> |<br /> |build connectors (notably for BMW)<br /> |-<br /> |<br /> |'''''Aptiv'''''<br /> |<br /> |build connectors (notably for Nissan) - ex Delphi (ex GM :-) )<br /> |-<br /> |<br /> |'''''Molex'''''<br /> |<br /> |build connectors (notably for Tesla)<br /> |-<br /> |<br /> |'''''Sumitomo'''''<br /> |<br /> |build connectors (notably for Mitsubishi)<br /> |-<br /> |<br /> |'''''Hirose'''''<br /> |<br /> |build connectors (notably for Mitsubishi)<br /> |-<br /> |<br /> |'''''Dilong'''''<br /> |<br /> |build chargers (at the very least)<br /> |-<br /> |<br /> |Eltek<br /> |<br /> |build chargers (at the very least)<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |}<br /> <br /> ==== Parts (Components) ====<br /> {| class="wikitable"<br /> !Top level<br /> !2nd level<br /> !3rd level<br /> !Note<br /> |-<br /> |Parts<br /> |Inverter<br /> |<br /> |<br /> |-<br /> |<br /> |Motor<br /> |<br /> |<br /> |-<br /> |<br /> |Brake Assist<br /> |<br /> |<br /> |-<br /> |<br /> |'''''Battery Packs'''''<br /> |'''''Battery modules'''''<br /> |this is a split of the battery cateogy<br /> |-<br /> |<br /> |<br /> |BMS<br /> |moved under Battery packs<br /> |-<br /> |<br /> |<br /> |Contactor<br /> |where SBOX, VBOX and Isabellenhutte should belong. moved under battery packs<br /> |-<br /> |<br /> |DC/DC<br /> |<br /> |<br /> |-<br /> |<br /> |HVJB (High Voltage Junction Box)<br /> |<br /> |<br /> |-<br /> |<br /> |Accelerator Pedals and Position Sensors<br /> |<br /> |<br /> |-<br /> |<br /> |Gearbox<br /> |<br /> |<br /> |-<br /> |<br /> |Gear Selectors<br /> |<br /> |<br /> |-<br /> |<br /> |Power Steering<br /> |<br /> |<br /> |-<br /> |<br /> |Charging Systems<br /> |ChaDeMo<br /> |<br /> |-<br /> |<br /> |<br /> |CCS<br /> |<br /> |-<br /> |<br /> |<br /> |Charge Ports<br /> |<br /> |-<br /> |<br /> |<br /> |Fast Charging<br /> |moved out of charger and under charging systems<br /> |-<br /> |<br /> |<br /> |Charger<br /> |moved under charging systems<br /> |-<br /> |<br /> |Thermal Management<br /> |AC Compressor<br /> |<br /> |-<br /> |<br /> |<br /> |Heater Coolant<br /> |<br /> |-<br /> |<br /> |<br /> |Heater Air<br /> |<br /> |-<br /> |<br /> |<br /> |Water Pumps<br /> |<br /> |-<br /> |<br /> |<br /> |HVAC<br /> |<br /> |-<br /> |<br /> |<br /> |Coolant Fittings<br /> |<br /> |-<br /> |<br /> |<br /> |Coolant Valve<br /> |<br /> |-<br /> |<br /> |'''''Connectors'''''<br /> |<br /> |<br /> |-<br /> |<br /> |'''''Cables'''''<br /> |<br /> |<br /> |-<br /> |<br /> |'''''Instruments'''''<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |'''''Mechanical Adapters'''''<br /> |CAD<br /> |mechanical and adapter categories to be merged as "mechanical adapters"<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |}<br /> <br /> ==== Software, Electronics and Protocols ====<br /> {| class="wikitable"<br /> !Top level<br /> !2nd level<br /> !3rd level<br /> !Note<br /> |-<br /> |'''Electronics'''<br /> |VCU<br /> |ZombieVerter<br /> |<br /> |-<br /> |<br /> |<br /> |OpenInverter<br /> |<br /> |-<br /> |<br /> |'''''chipsets'''''<br /> |ESP32<br /> |<br /> |-<br /> |<br /> |<br /> |ESP8266<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |PCB<br /> |Arduino<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |Protocols<br /> |CAN<br /> |'''''CANID'''''<br /> |category to define the CAN messages<br /> |-<br /> |<br /> |LIN<br /> |<br /> |<br /> |-<br /> |<br /> |'''''Ethernet'''''<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |}<br /> <br /> ==== Other categories ====<br /> {| class="wikitable"<br /> !Top level<br /> !2nd level<br /> !3rd level<br /> !Note<br /> |-<br /> |Basics<br /> |Tutorials<br /> |<br /> |covers the necessary understanding required before envisaging a conversion project (maybe merge the 2 categories?)<br /> Tutorial to be merged with Tutorials<br /> |-<br /> |<br /> |Resource<br /> |<br /> |merge with Introduction?<br /> |-<br /> |<br /> |FAQ<br /> |<br /> |<br /> |-<br /> |Conversion<br /> |<br /> |<br /> |ongoing and succesful conversion projects (the VCU should be a mandatory sub-category I think)<br /> |-<br /> |Legalities<br /> |<br /> |<br /> |<br /> |}<br /> <br /> ==== Proposed for deletion (category, not content!) ====<br /> {| class="wikitable"<br /> !Name<br /> !Number of Pages<br /> !Reason for request for deletion<br /> |-<br /> |Accessories<br /> |0<br /> |what is mandatory? What is an accessory? better consider they are parts. the category has 0 page so far<br /> |-<br /> |Hardware<br /> |0<br /> |better call it parts - 0 page<br /> |-<br /> |ISA Shunt<br /> |1<br /> |this should not be a category on its own but a page of category "connector"<br /> |-<br /> |Chademo with Zombieverter<br /> |0<br /> |should be part of category chademo<br /> |-<br /> |Request for Review<br /> |1<br /> |this seldom used<br /> |-<br /> |OpenInverter Projects<br /> |<br /> |better have a combination of the "conversion" and the corresponding VCU category?<br /> |-<br /> |Introduction<br /> |<br /> |merge with Resource?<br /> |-<br /> |DEAD<br /> |1<br /> |possibly wrongly created in the first place<br /> |-<br /> |Delta<br /> |1<br /> |<br /> |-<br /> |General Tesla FAQ<br /> |1<br /> |should be a page part of category FAQ, not a category on its own.<br /> |}<br /> <br /> === Templates structure ===<br /> the intent is that for some content that would fit a given category, an associated template and form is being created. Not all pages must be created like that, and it is quite possible that such templated pages must be created when a certain maturity level is being reached. For those selected categories, the associated object and data properties must be identified. It is likely that some will be resused throughout different type of objects (any physical component has dimension and weight for instance).<br /> <br /> I have identified the following categories that are not created yet and which are useful (so as not to mess with any contributors' work at this stage)<br /> <br /> - Parts/Connectors<br /> <br /> - Parts/Cables<br /> <br /> - Protocols/CAN/CANID<br /> <br /> ==== Connectors ====<br /> <br /> ===== Page Name Structure: =====<br /> <br /> ===== Infobox content: =====<br /> {| class="wikitable"<br /> |+<br /> !PropertyName<br /> !Label (friendly name)<br /> !Associated Object or Data<br /> !single/multiple<br /> !Mandatory/Optional<br /> !Comments<br /> |-<br /> |HasImage.Page<br /> |Image<br /> |Page for in the File: namespace<br /> |single<br /> |Optional<br /> |Multiple images can be used for an object, but having one that serves inot the infobox, which can tell also be used for visual searches (imagine you do not know what type of connector you have, you can look at a visual gallery to find out which one you have and the associated relevant information)<br /> The image display will be constrained in the form for a given size.<br /> |-<br /> |IsProducedBy.Page<br /> |Manufacturer<br /> |Page<br /> |single<br /> |Optional<br /> |Link the component to its manufacturer<br /> |-<br /> |UsedIn.Page<br /> |Used in<br /> |Page<br /> |multiple<br /> |Optional<br /> |allow to link the parent components/vehicles which are using this component<br /> |-<br /> |IsMatedWith.Page<br /> |Mating connector<br /> |Page<br /> |single<br /> |Optional<br /> |When available, define which connector is used to connect to it.<br /> |-<br /> |IsHighVoltage.Boolean<br /> |High Voltage<br /> |Boolean<br /> |single<br /> |Mandatory<br /> |defines if HV or not<br /> |-<br /> |HasInterlock.Boolean<br /> |Interlock Present<br /> |Boolean<br /> |single<br /> |Mandatory<br /> |defines if interlock pins are present or not<br /> |-<br /> |HasColour.Text<br /> |Main colour<br /> |Text<br /> |single<br /> |Mandatory<br /> |describe the most prevalent colour of the connector. it can be useful for narrowing down searches. the list of colour should be constrained to avoid having "Deep sea blue" or "amethist" type of colours...<br /> |-<br /> |HasReference.Text<br /> |References<br /> |Text<br /> |multiple<br /> |optional<br /> |<br /> |-<br /> |HasTerminals.Number<br /> |number of terminals (pins)<br /> |Number<br /> |single<br /> |Mandatory<br /> |number of pins or holes on the connectors, WITHOUT counting the interlock<br /> |}<br /> <br /> ==== CANID Message ====<br /> {| class="wikitable"<br /> |+<br /> !<br /> !<br /> !<br /> !<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |}</div>

Powercontrol https://openinverter.org/wiki/index.php?title=Content_Management&diff=5776 Content Management 2025-05-10T14:58:33Z

<p>Powercontrol: </p> <hr /> <div>'''DRAFT - DRAFT - DRAFT'''<br /> <br /> the objective of this page is to explain how the content of the wiki page could be structured using Semantic for Mediawiki (SMW) to build a scalable and object-based wiki (for search and relation-building aspects) and still keeping the freedom for authors to create their content. There needs to be a trade-off to be found between freedom and structure.<br /> <br /> === Why Semantic for Mediawiki? ===<br /> SMW allows to have a form-based creation of objects. the form asks the users some key information then create the corresponding page and render the entered information in a consistent way, assign the category accordingly etc.<br /> <br /> Because the page created is based on a template, changing the template modifies the instantiation of the created pages. <br /> <br /> SMW also allows to create dynamic queries inside pages. The content will be modified based on other pages content. this is a powerful manner to make references to other pages without doing manual maintenance of the page. A practical and basic example would be that if the query below was inserted a page creation (a template being called by a form):<br /> <br /> <nowiki>{{#ask:<br /> [[FoundIn.Page::{{PAGENAME}}]]<br /> | format=list<br /> | link=all<br /> }}</nowiki><br /> The page content will update itself to list all other pages that refer to this new page. There are much more granular type of queries to be done (including on categories) which then become really handy.<br /> === General Principles and Naming Convention ===<br /> SMW uses multiple notions. They are key to be used properly for good use.<br /> {| class="wikitable"<br /> |+<br /> !Object<br /> !Usage<br /> !Naming Convention<br /> !Example<br /> |-<br /> |'''Page'''<br /> |the core component of the wiki and what readers are consuming. By default, there is no hierarchical structure of pages - and categories are the better way for structuring a wiki<br /> |each Word is start with a capital letter. Spaces and brackets are allowed. mutiple words are recommended to be separated by a space (mediawiki uses underscore instead of %20 for URL)<br /> '''''Title Case'''''<br /> |Nissan Leaf (2010-2017)<br /> |-<br /> |'''Category'''<br /> |the categories are part of the generic Mediawiki structure. its reflects a categorization or labeling of pages. Categories can be nested which are useful to reflect a structure of "component of" and for "is a subtype of". Multiple categories can be assigned to page, hence it can provide multiple view at once. A dedicated section of this page will cover their aspects.<br /> There are cases where it is not obvious whether a property or a category makes more sense. one does not prevent the other, by the way.<br /> |as the wiki already as categories created and they use naming similar to Page, the categories will further be named the same way.<br /> Ideally, categories shall be written in <u>plural form</u> (because it is a grouping of x) <br /> '''''Title Case (in plural)'''''<br /> |Batteries<br /> Connectors<br /> |-<br /> |'''Property'''<br /> |SMW specific - it defines a relation between 2 objects, or assign an attribute to an object. the target (called [[Special:Types]]) can be a list, another page. When defining a property, it would make sense to refer to a specific category of object (for instance, FoundIn would be referring to a Vehicle or a Component), but the type of object we can refer to are Pages, Numbers, Date,... nothing to do with category. <br /> |'''''UpperCamelCase.DestinationObjectType''''' or '''''UpperCamelCase.DestinationAttributeType'''''<br /> |FoundIn.Page<br /> HasWeight.Qty<br /> |-<br /> |'''Template'''<br /> |SMW specific - defines which properties values shall be defined at the creation of an object. Not all pages must be created using templates, but objects which have relations between themselves are best created using templates.<br /> |the template name shall refer to a corresponding category name in <u>singular</u>, and the template shall enforce that category at page creation.<br /> '''''T/UpperCamelCase.OutputFormat'''''<br /> |T/Connector.Infobox<br /> T/Battery.PlainText<br /> |-<br /> |'''Form'''<br /> |SMW specific - A Form is an helper for the author to create a templated object. The form allows to create a consistent visual structure to pages<br /> |'''''F/UpperCamelCase''''' - the Form refers to a corresponding Template, but the output format will not be referred to in the form name.<br /> A form can also call multiple templates - in such case its name will refer to the first one<br /> |F/Connector<br /> F/Battery<br /> |}<br /> <br /> === Categories ===<br /> At the time of writing, the following category structure exist: (in the absence of CategoryTree extension, doing my best to represent it):<br /> <br /> {| class="wikitable"<br /> ! Level 1 !! Level 2 !! Level 3 !! transferred<br /> |-<br /> | Basics || || ||x<br /> |-<br /> | Parts || Inverter || ||x<br /> |-<br /> | || Motor || || x<br /> |-<br /> | || Battery || || x<br /> |-<br /> | || Charger || Rapid Charging|| x<br /> |-<br /> | || DC/DC || || x<br /> |-<br /> | || HVJB (High Voltage Junction Box) || || x<br /> |-<br /> | || Contactor || || x<br /> |-<br /> | || PCB || || x<br /> |-<br /> | || CAN || || x<br /> |-<br /> | || LIN || || x<br /> |-<br /> | || ISA Shunt || || x<br /> |-<br /> | || Accelerator Pedals and Position Sensors || || x<br /> |-<br /> | || Gearbox || || x<br /> |-<br /> | || Gear Selectors || || x<br /> |-<br /> | || Power Steering || || x<br /> |-<br /> | || Water Pumps || || x<br /> |-<br /> | || Arduino || || x<br /> |-<br /> | || Adapter || || x<br /> |-<br /> |<br /> |Thermal Management<br /> |AC Compressor<br /> |x<br /> |-<br /> | || || Heater Coolant|| x<br /> |-<br /> |<br /> |<br /> |Heater Air<br /> |x<br /> |-<br /> |<br /> |HVAC<br /> |Coolant Fittings<br /> |x<br /> |-<br /> |<br /> |<br /> |Coolant Valve<br /> |x<br /> |-<br /> | || ESP32 || || x<br /> |-<br /> | || ESP8266 || || x<br /> |-<br /> | || ZombieVerter || || x<br /> |-<br /> | || VCU || || x<br /> |-<br /> | OEM Manufacturers || BMW || || x<br /> |-<br /> | || Bosch || || x<br /> |-<br /> | || Chevrolet || || x<br /> |-<br /> | || Ford || || x<br /> |-<br /> | || Honda || || x<br /> |-<br /> | || Hyundai || || x<br /> |-<br /> | || Isabellenhütte || || x<br /> |-<br /> | || Land Rover || || x<br /> |-<br /> | || Lexus || || x<br /> |-<br /> | || Mercedes-Benz || || x<br /> |-<br /> | || MG || || x<br /> |-<br /> | || Mitsubishi || || x<br /> |-<br /> | || Nissan || || x<br /> |-<br /> | || Opel || || x<br /> |-<br /> | || Peugeot || || x<br /> |-<br /> | || Renault || || x<br /> |-<br /> | || Tesla || || x<br /> |-<br /> | || Toyota || || x<br /> |-<br /> | || VAG (Volkswagen Audi Group) || VW || x<br /> |-<br /> | || Vauxhall || || x<br /> |-<br /> | || Volvo || || x<br /> |-<br /> | Charging Systems || ChaDeMo || Chademo with Zombieverter || x<br /> |-<br /> | || CCS || || x<br /> |-<br /> | || Charge Ports || || x<br /> |-<br /> | || Fast Charging || || x<br /> |-<br /> | Conversions || Mechanical || Parts || x<br /> |-<br /> | || OpenInverter Projects || || x<br /> |-<br /> | || OEM Repurposing || || <br /> |-<br /> | || Obsolete || || <br /> |-<br /> | Accessories || || ||x<br /> |-<br /> | Education || || ||<br /> |-<br /> | Request for Review || || ||x<br /> |-<br /> | Troubleshoot || || ||<br /> |-<br /> | Webasto || || ||x<br /> |-<br /> |Legalities<br /> |<br /> |<br /> |x<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |}<br /> <br /> <br /> I am proposing to shuffle the categories in such structure - bold/italic names are to be created<br /> <br /> ==== Manufacturers categories and structure ====<br /> the structure is meant to only identifies the group of brand (as they will likely be sharing components). Therefore, if a brand leaves a group to join another, a distinct brand category must be created.<br /> <br /> Model names (a specific category - see below) is attached to the brand related to its parent group (i.e. Opel Ampera is linked to GM, Opel Moka is linked to Stellantis). this structure gives us the flexibility to manage changing alliances/holdings over time. <br /> <br /> Cars are being sold with different names (Opel/Vauxhall, Renault/Mitsubishi etc), therefore, while the Page Name may refer to a specific brand-model combination, the car model <u>shall not</u> be a category on its own.<br /> <br /> <br /> The OEM Manufacturers shall include the groups that are delivering parts to car makers (Bosch, Magnetti Marelli etc)<br /> {| class="wikitable"<br /> |+<br /> !Top level<br /> !Group<br /> !Brand<br /> !Note<br /> |-<br /> |OEM Manufacturers<br /> |'''''BMW Group'''''<br /> |BMW<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Mini'''''<br /> |<br /> |-<br /> |<br /> |'''''General Motors'''''<br /> |Chevrolet<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Opel (<2017)'''''<br /> |the Opel Ampera was still under GM, so it is a completely different affiliation than today<br /> |-<br /> |<br /> |'''''Stellantis'''''<br /> |Opel (2017-)<br /> |the new ones<br /> |-<br /> |<br /> |<br /> |Vauxhall<br /> |<br /> |-<br /> |<br /> |<br /> |Peugeot<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Citroen'''''<br /> |<br /> |-<br /> |<br /> |'''''Toyota Motor Corporation'''''<br /> |Toyota<br /> |<br /> |-<br /> |<br /> |<br /> |Lexus<br /> |<br /> |-<br /> |<br /> |'''''Hyundai Motor Group'''''<br /> |Hyundai<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Kia'''''<br /> |<br /> |-<br /> |<br /> |'''''Renault-Nissan-Mitsubishi Alliance'''''<br /> |Mitsubishi<br /> |<br /> |-<br /> |<br /> |<br /> |Renault<br /> |<br /> |-<br /> |<br /> |<br /> |Nissan<br /> |<br /> |-<br /> |<br /> |'''''Ford Motor Corporation'''''<br /> |Ford<br /> |<br /> |-<br /> |<br /> |'''''Tata Motors'''''<br /> |Land Rover<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Jaguar'''''<br /> |<br /> |-<br /> |<br /> |VAG (Volkswagen Audi Group)<br /> |'''''Volkswagen'''''<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Audi'''''<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Skoda'''''<br /> |<br /> |-<br /> |<br /> |'''''Geely Holding Group'''''<br /> |Volvo<br /> |<br /> |-<br /> |<br /> |'''''SAIC Motor Europe'''''<br /> |MG<br /> |<br /> |-<br /> |<br /> |Honda<br /> |<br /> |<br /> |-<br /> |<br /> |Bosch<br /> |<br /> |<br /> |-<br /> |<br /> |Isabellenhütte<br /> |<br /> |<br /> |-<br /> |<br /> |Mercedes-Benz<br /> |<br /> |<br /> |-<br /> |<br /> |'''''BYD'''''<br /> |<br /> |<br /> |-<br /> |<br /> |Tesla<br /> |<br /> |<br /> |-<br /> |<br /> |Webasto<br /> |<br /> |moved under OEM Manufacturers<br /> |-<br /> |<br /> |'''''TE Connectivity'''''<br /> |<br /> |build connectors (notably for BMW)<br /> |-<br /> |<br /> |'''''Aptiv'''''<br /> |<br /> |build connectors (notably for Nissan) - ex Delphi (ex GM :-) )<br /> |-<br /> |<br /> |'''''Molex'''''<br /> |<br /> |build connectors (notably for Tesla)<br /> |-<br /> |<br /> |'''''Sumitomo'''''<br /> |<br /> |build connectors (notably for Mitsubishi)<br /> |-<br /> |<br /> |'''''Hirose'''''<br /> |<br /> |build connectors (notably for Mitsubishi)<br /> |-<br /> |<br /> |'''''Dilong'''''<br /> |<br /> |<br /> |-<br /> |<br /> |Eltek<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |}<br /> <br /> ==== Parts (Components) ====<br /> {| class="wikitable"<br /> !Top level<br /> !2nd level<br /> !3rd level<br /> !Note<br /> |-<br /> |Parts<br /> |Inverter<br /> |<br /> |<br /> |-<br /> |<br /> |Motor<br /> |<br /> |<br /> |-<br /> |<br /> |Brake Assist<br /> |<br /> |<br /> |-<br /> |<br /> |'''''Battery Packs'''''<br /> |'''''Battery modules'''''<br /> |this is a split of the battery cateogy<br /> |-<br /> |<br /> |<br /> |BMS<br /> |moved under Battery packs<br /> |-<br /> |<br /> |<br /> |Contactor<br /> |where SBOX, VBOX and Isabellenhutte should belong. moved under battery packs<br /> |-<br /> |<br /> |DC/DC<br /> |<br /> |<br /> |-<br /> |<br /> |HVJB (High Voltage Junction Box)<br /> |<br /> |<br /> |-<br /> |<br /> |Accelerator Pedals and Position Sensors<br /> |<br /> |<br /> |-<br /> |<br /> |Gearbox<br /> |<br /> |<br /> |-<br /> |<br /> |Gear Selectors<br /> |<br /> |<br /> |-<br /> |<br /> |Power Steering<br /> |<br /> |<br /> |-<br /> |<br /> |Charging Systems<br /> |ChaDeMo<br /> |<br /> |-<br /> |<br /> |<br /> |CCS<br /> |<br /> |-<br /> |<br /> |<br /> |Charge Ports<br /> |<br /> |-<br /> |<br /> |<br /> |Fast Charging<br /> |moved out of charger and under charging systems<br /> |-<br /> |<br /> |<br /> |Charger<br /> |moved under charging systems<br /> |-<br /> |<br /> |Thermal Management<br /> |AC Compressor<br /> |<br /> |-<br /> |<br /> |<br /> |Heater Coolant<br /> |<br /> |-<br /> |<br /> |<br /> |Heater Air<br /> |<br /> |-<br /> |<br /> |<br /> |Water Pumps<br /> |<br /> |-<br /> |<br /> |<br /> |HVAC<br /> |<br /> |-<br /> |<br /> |<br /> |Coolant Fittings<br /> |<br /> |-<br /> |<br /> |<br /> |Coolant Valve<br /> |<br /> |-<br /> |<br /> |'''''Connectors'''''<br /> |<br /> |<br /> |-<br /> |<br /> |'''''Cables'''''<br /> |<br /> |<br /> |-<br /> |<br /> |'''''Instruments'''''<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |'''''Mechanical Adapters'''''<br /> |CAD<br /> |mechanical and adapter categories to be merged as "mechanical adapters"<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |}<br /> <br /> ==== Software, Electronics and Protocols ====<br /> {| class="wikitable"<br /> !Top level<br /> !2nd level<br /> !3rd level<br /> !Note<br /> |-<br /> |'''Electronics'''<br /> |VCU<br /> |ZombieVerter<br /> |<br /> |-<br /> |<br /> |<br /> |OpenInverter<br /> |<br /> |-<br /> |<br /> |'''''chipsets'''''<br /> |ESP32<br /> |<br /> |-<br /> |<br /> |<br /> |ESP8266<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |PCB<br /> |Arduino<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |Protocols<br /> |CAN<br /> |'''''CANID'''''<br /> |category to define the CAN messages<br /> |-<br /> |<br /> |LIN<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |}<br /> <br /> ==== Other categories ====<br /> {| class="wikitable"<br /> !Top level<br /> !2nd level<br /> !3rd level<br /> !Note<br /> |-<br /> |Basics<br /> |Tutorials<br /> |<br /> |covers the necessary understanding required before envisaging a conversion project (maybe merge the 2 categories?)<br /> Tutorial to be merged with Tutorials<br /> |-<br /> |<br /> |Resource<br /> |<br /> |merge with Introduction?<br /> |-<br /> |<br /> |FAQ<br /> |<br /> |<br /> |-<br /> |Conversion<br /> |<br /> |<br /> |ongoing and succesful conversion projects (the VCU should be a mandatory sub-category I think)<br /> |-<br /> |Legalities<br /> |<br /> |<br /> |<br /> |}<br /> <br /> ==== Proposed for deletion (category, not content!) ====<br /> {| class="wikitable"<br /> !Name<br /> !Number of Pages<br /> !Reason for request for deletion<br /> |-<br /> |Accessories<br /> |0<br /> |what is mandatory? What is an accessory? better consider they are parts. the category has 0 page so far<br /> |-<br /> |Hardware<br /> |0<br /> |better call it parts - 0 page<br /> |-<br /> |ISA Shunt<br /> |1<br /> |this should not be a category on its own but a page of category "connector"<br /> |-<br /> |Chademo with Zombieverter<br /> |0<br /> |should be part of category chademo<br /> |-<br /> |Request for Review<br /> |1<br /> |this seldom used<br /> |-<br /> |OpenInverter Projects<br /> |<br /> |better have a combination of the "conversion" and the corresponding VCU category?<br /> |-<br /> |Introduction<br /> |<br /> |merge with Resource?<br /> |-<br /> |DEAD<br /> |1<br /> |possibly wrongly created in the first place<br /> |-<br /> |Delta<br /> |1<br /> |<br /> |-<br /> |General Tesla FAQ<br /> |1<br /> |should be a page part of category FAQ, not a category on its own.<br /> |}</div>

Powercontrol https://openinverter.org/wiki/index.php?title=Content_Management&diff=5775 Content Management 2025-05-10T14:54:55Z

<p>Powercontrol: draft done for the category aspect, moving to template and forms description</p> <hr /> <div>'''DRAFT - DRAFT - DRAFT'''<br /> <br /> the objective of this page is to explain how the content of the wiki page could be structured using Semantic for Mediawiki (SMW) to build a scalable and object-based wiki (for search and relation-building aspects) and still keeping the freedom for authors to create their content. There needs to be a trade-off to be found between freedom and structure.<br /> <br /> === Why Semantic for Mediawiki? ===<br /> SMW allows to have a form-based creation of objects. the form asks the users some key information then create the corresponding page and render the entered information in a consistent way, assign the category accordingly etc.<br /> <br /> Because the page created is based on a template, changing the template modifies the instantiation of the created pages. <br /> <br /> SMW also allows to create dynamic queries inside pages. The content will be modified based on other pages content. this is a powerful manner to make references to other pages without doing manual maintenance of the page. A practical and basic example would be that if the query below was inserted a page creation (a template being called by a form):<br /> <br /> <nowiki>{{#ask:<br /> [[FoundIn.Page::{{PAGENAME}}]]<br /> | format=list<br /> | link=all<br /> }}</nowiki><br /> The page content will update itself to list all other pages that refer to this new page. There are much more granular type of queries to be done (including on categories) which then become really handy.<br /> === General Principles and Naming Convention ===<br /> SMW uses multiple notions. They are key to be used properly for good use.<br /> {| class="wikitable"<br /> |+<br /> !Object<br /> !Usage<br /> !Naming Convention<br /> !Example<br /> |-<br /> |'''Page'''<br /> |the core component of the wiki and what readers are consuming. By default, there is no hierarchical structure of pages - and categories are the better way for structuring a wiki<br /> |each Word is start with a capital letter. Spaces and brackets are allowed. mutiple words are recommended to be separated by a space (mediawiki uses underscore instead of %20 for URL)<br /> '''''Title Case'''''<br /> |Nissan Leaf (2010-2017)<br /> |-<br /> |'''Category'''<br /> |the categories are part of the generic Mediawiki structure. its reflects a categorization or labeling of pages. Categories can be nested which are useful to reflect a structure of "component of" and for "is a subtype of". Multiple categories can be assigned to page, hence it can provide multiple view at once. A dedicated section of this page will cover their aspects.<br /> There are cases where it is not obvious whether a property or a category makes more sense. one does not prevent the other, by the way.<br /> |as the wiki already as categories created and they use naming similar to Page, the categories will further be named the same way.<br /> Ideally, categories shall be written in <u>plural form</u> (because it is a grouping of x) <br /> '''''Title Case (in plural)'''''<br /> |Batteries<br /> Connectors<br /> |-<br /> |'''Property'''<br /> |SMW specific - it defines a relation between 2 objects, or assign an attribute to an object. the target (called [[Special:Types]]) can be a list, another page. When defining a property, it would make sense to refer to a specific category of object (for instance, FoundIn would be referring to a Vehicle or a Component), but the type of object we can refer to are Pages, Numbers, Date,... nothing to do with category. <br /> |'''''UpperCamelCase.DestinationObjectType''''' or '''''UpperCamelCase.DestinationAttributeType'''''<br /> |FoundIn.Page<br /> HasWeight.Qty<br /> |-<br /> |'''Template'''<br /> |SMW specific - defines which properties values shall be defined at the creation of an object. Not all pages must be created using templates, but objects which have relations between themselves are best created using templates.<br /> |the template name shall refer to a corresponding category name in <u>singular</u>, and the template shall enforce that category at page creation.<br /> '''''T/UpperCamelCase.OutputFormat'''''<br /> |T/Connector.Infobox<br /> T/Battery.PlainText<br /> |-<br /> |'''Form'''<br /> |SMW specific - A Form is an helper for the author to create a templated object. The form allows to create a consistent visual structure to pages<br /> |'''''F/UpperCamelCase''''' - the Form refers to a corresponding Template, but the output format will not be referred to in the form name.<br /> A form can also call multiple templates - in such case its name will refer to the first one<br /> |F/Connector<br /> F/Battery<br /> |}<br /> <br /> === Categories ===<br /> At the time of writing, the following category structure exist: (in the absence of CategoryTree extension, doing my best to represent it):<br /> <br /> {| class="wikitable"<br /> ! Level 1 !! Level 2 !! Level 3 !! transferred<br /> |-<br /> | Basics || || ||x<br /> |-<br /> | Parts || Inverter || ||x<br /> |-<br /> | || Motor || || x<br /> |-<br /> | || Battery || || x<br /> |-<br /> | || Charger || Rapid Charging|| x<br /> |-<br /> | || DC/DC || || x<br /> |-<br /> | || HVJB (High Voltage Junction Box) || || x<br /> |-<br /> | || Contactor || || x<br /> |-<br /> | || PCB || || x<br /> |-<br /> | || CAN || || x<br /> |-<br /> | || LIN || || x<br /> |-<br /> | || ISA Shunt || || x<br /> |-<br /> | || Accelerator Pedals and Position Sensors || || x<br /> |-<br /> | || Gearbox || || x<br /> |-<br /> | || Gear Selectors || || x<br /> |-<br /> | || Power Steering || || x<br /> |-<br /> | || Water Pumps || || x<br /> |-<br /> | || Arduino || || x<br /> |-<br /> | || Adapter || || x<br /> |-<br /> |<br /> |Thermal Management<br /> |AC Compressor<br /> |x<br /> |-<br /> | || || Heater Coolant|| x<br /> |-<br /> |<br /> |<br /> |Heater Air<br /> |x<br /> |-<br /> |<br /> |HVAC<br /> |Coolant Fittings<br /> |x<br /> |-<br /> |<br /> |<br /> |Coolant Valve<br /> |x<br /> |-<br /> | || ESP32 || || x<br /> |-<br /> | || ESP8266 || || x<br /> |-<br /> | || ZombieVerter || || x<br /> |-<br /> | || VCU || || x<br /> |-<br /> | OEM Manufacturers || BMW || || x<br /> |-<br /> | || Bosch || || x<br /> |-<br /> | || Chevrolet || || x<br /> |-<br /> | || Ford || || x<br /> |-<br /> | || Honda || || x<br /> |-<br /> | || Hyundai || || x<br /> |-<br /> | || Isabellenhütte || || x<br /> |-<br /> | || Land Rover || || x<br /> |-<br /> | || Lexus || || x<br /> |-<br /> | || Mercedes-Benz || || x<br /> |-<br /> | || MG || || x<br /> |-<br /> | || Mitsubishi || || x<br /> |-<br /> | || Nissan || || x<br /> |-<br /> | || Opel || || x<br /> |-<br /> | || Peugeot || || x<br /> |-<br /> | || Renault || || x<br /> |-<br /> | || Tesla || || x<br /> |-<br /> | || Toyota || || x<br /> |-<br /> | || VAG (Volkswagen Audi Group) || VW || x<br /> |-<br /> | || Vauxhall || || x<br /> |-<br /> | || Volvo || || x<br /> |-<br /> | Charging Systems || ChaDeMo || Chademo with Zombieverter || x<br /> |-<br /> | || CCS || || x<br /> |-<br /> | || Charge Ports || || x<br /> |-<br /> | || Fast Charging || || x<br /> |-<br /> | Conversions || Mechanical || Parts || x<br /> |-<br /> | || OpenInverter Projects || || <br /> |-<br /> | || OEM Repurposing || || <br /> |-<br /> | || Obsolete || || <br /> |-<br /> | Accessories || || ||x<br /> |-<br /> | Education || || ||<br /> |-<br /> | Request for Review || || ||x<br /> |-<br /> | Troubleshoot || || ||<br /> |-<br /> | Webasto || || ||x<br /> |-<br /> |Legalities<br /> |<br /> |<br /> |x<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |}<br /> <br /> <br /> I am proposing to shuffle the categories in such structure - bold/italic names are to be created<br /> <br /> ==== Manufacturers categories and structure ====<br /> the structure is meant to only identifies the group of brand (as they will likely be sharing components). Therefore, if a brand leaves a group to join another, a distinct brand category must be created.<br /> <br /> Model names (a specific category - see below) is attached to the brand related to its parent group (i.e. Opel Ampera is linked to GM, Opel Moka is linked to Stellantis). this structure gives us the flexibility to manage changing alliances/holdings over time. <br /> <br /> Cars are being sold with different names (Opel/Vauxhall, Renault/Mitsubishi etc), therefore, while the Page Name may refer to a specific brand-model combination, the car model <u>shall not</u> be a category on its own.<br /> <br /> <br /> The OEM Manufacturers shall include the groups that are delivering parts to car makers (Bosch, Magnetti Marelli etc)<br /> {| class="wikitable"<br /> |+<br /> !Top level<br /> !Group<br /> !Brand<br /> !Note<br /> |-<br /> |OEM Manufacturers<br /> |'''''BMW Group'''''<br /> |BMW<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Mini'''''<br /> |<br /> |-<br /> |<br /> |'''''General Motors'''''<br /> |Chevrolet<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Opel (<2017)'''''<br /> |the Opel Ampera was still under GM, so it is a completely different affiliation than today<br /> |-<br /> |<br /> |'''''Stellantis'''''<br /> |Opel (2017-)<br /> |the new ones<br /> |-<br /> |<br /> |<br /> |Vauxhall<br /> |<br /> |-<br /> |<br /> |<br /> |Peugeot<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Citroen'''''<br /> |<br /> |-<br /> |<br /> |'''''Toyota Motor Corporation'''''<br /> |Toyota<br /> |<br /> |-<br /> |<br /> |<br /> |Lexus<br /> |<br /> |-<br /> |<br /> |'''''Hyundai Motor Group'''''<br /> |Hyundai<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Kia'''''<br /> |<br /> |-<br /> |<br /> |'''''Renault-Nissan-Mitsubishi Alliance'''''<br /> |Mitsubishi<br /> |<br /> |-<br /> |<br /> |<br /> |Renault<br /> |<br /> |-<br /> |<br /> |<br /> |Nissan<br /> |<br /> |-<br /> |<br /> |'''''Ford Motor Corporation'''''<br /> |Ford<br /> |<br /> |-<br /> |<br /> |'''''Tata Motors'''''<br /> |Land Rover<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Jaguar'''''<br /> |<br /> |-<br /> |<br /> |VAG (Volkswagen Audi Group)<br /> |'''''Volkswagen'''''<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Audi'''''<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Skoda'''''<br /> |<br /> |-<br /> |<br /> |'''''Geely Holding Group'''''<br /> |Volvo<br /> |<br /> |-<br /> |<br /> |'''''SAIC Motor Europe'''''<br /> |MG<br /> |<br /> |-<br /> |<br /> |Honda<br /> |<br /> |<br /> |-<br /> |<br /> |Bosch<br /> |<br /> |<br /> |-<br /> |<br /> |Isabellenhütte<br /> |<br /> |<br /> |-<br /> |<br /> |Mercedes-Benz<br /> |<br /> |<br /> |-<br /> |<br /> |'''''BYD'''''<br /> |<br /> |<br /> |-<br /> |<br /> |Tesla<br /> |<br /> |<br /> |-<br /> |<br /> |Webasto<br /> |<br /> |moved under OEM Manufacturers<br /> |-<br /> |<br /> |'''''TE Connectivity'''''<br /> |<br /> |build connectors (notably for BMW)<br /> |-<br /> |<br /> |'''''Aptiv'''''<br /> |<br /> |build connectors (notably for Nissan) - ex Delphi (ex GM :-) )<br /> |-<br /> |<br /> |'''''Molex'''''<br /> |<br /> |build connectors (notably for Tesla)<br /> |-<br /> |<br /> |'''''Sumitomo'''''<br /> |<br /> |build connectors (notably for Mitsubishi)<br /> |-<br /> |<br /> |'''''Hirose'''''<br /> |<br /> |build connectors (notably for Mitsubishi)<br /> |-<br /> |<br /> |'''''Dilong'''''<br /> |<br /> |<br /> |-<br /> |<br /> |Eltek<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |}<br /> <br /> ==== Parts (Components) ====<br /> {| class="wikitable"<br /> !Top level<br /> !2nd level<br /> !3rd level<br /> !Note<br /> |-<br /> |Parts<br /> |Inverter<br /> |<br /> |<br /> |-<br /> |<br /> |Motor<br /> |<br /> |<br /> |-<br /> |<br /> |Brake Assist<br /> |<br /> |<br /> |-<br /> |<br /> |'''''Battery Packs'''''<br /> |'''''Battery modules'''''<br /> |this is a split of the battery cateogy<br /> |-<br /> |<br /> |<br /> |BMS<br /> |moved under Battery packs<br /> |-<br /> |<br /> |<br /> |Contactor<br /> |where SBOX, VBOX and Isabellenhutte should belong. moved under battery packs<br /> |-<br /> |<br /> |DC/DC<br /> |<br /> |<br /> |-<br /> |<br /> |HVJB (High Voltage Junction Box)<br /> |<br /> |<br /> |-<br /> |<br /> |Accelerator Pedals and Position Sensors<br /> |<br /> |<br /> |-<br /> |<br /> |Gearbox<br /> |<br /> |<br /> |-<br /> |<br /> |Gear Selectors<br /> |<br /> |<br /> |-<br /> |<br /> |Power Steering<br /> |<br /> |<br /> |-<br /> |<br /> |Charging Systems<br /> |ChaDeMo<br /> |<br /> |-<br /> |<br /> |<br /> |CCS<br /> |<br /> |-<br /> |<br /> |<br /> |Charge Ports<br /> |<br /> |-<br /> |<br /> |<br /> |Fast Charging<br /> |moved out of charger and under charging systems<br /> |-<br /> |<br /> |<br /> |Charger<br /> |moved under charging systems<br /> |-<br /> |<br /> |Thermal Management<br /> |AC Compressor<br /> |<br /> |-<br /> |<br /> |<br /> |Heater Coolant<br /> |<br /> |-<br /> |<br /> |<br /> |Heater Air<br /> |<br /> |-<br /> |<br /> |<br /> |Water Pumps<br /> |<br /> |-<br /> |<br /> |<br /> |HVAC<br /> |<br /> |-<br /> |<br /> |<br /> |Coolant Fittings<br /> |<br /> |-<br /> |<br /> |<br /> |Coolant Valve<br /> |<br /> |-<br /> |<br /> |'''''Connectors'''''<br /> |<br /> |<br /> |-<br /> |<br /> |'''''Cables'''''<br /> |<br /> |<br /> |-<br /> |<br /> |'''''Instruments'''''<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |'''''Mechanical Adapters'''''<br /> |CAD<br /> |mechanical and adapter categories to be merged as "mechanical adapters"<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |}<br /> <br /> ==== Software, Electronics and Protocols ====<br /> {| class="wikitable"<br /> !Top level<br /> !2nd level<br /> !3rd level<br /> !Note<br /> |-<br /> |'''Electronics'''<br /> |VCU<br /> |ZombieVerter<br /> |<br /> |-<br /> |<br /> |<br /> |OpenInverter<br /> |<br /> |-<br /> |<br /> |'''''chipsets'''''<br /> |ESP32<br /> |<br /> |-<br /> |<br /> |<br /> |ESP8266<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |PCB<br /> |Arduino<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |Protocols<br /> |CAN<br /> |'''''CANID'''''<br /> |category to define the CAN messages<br /> |-<br /> |<br /> |LIN<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |}<br /> <br /> ==== Other categories ====<br /> {| class="wikitable"<br /> !Top level<br /> !2nd level<br /> !3rd level<br /> !Note<br /> |-<br /> |Basics<br /> |Tutorials<br /> |<br /> |covers the necessary understanding required before envisaging a conversion project (maybe merge the 2 categories?)<br /> Tutorial to be merged with Tutorials<br /> |-<br /> |<br /> |Resource<br /> |<br /> |merge with Introduction?<br /> |-<br /> |<br /> |FAQ<br /> |<br /> |<br /> |-<br /> |Conversion<br /> |<br /> |<br /> |ongoing and succesful conversion projects (the VCU should be a mandatory sub-category I think)<br /> |-<br /> |Legalities<br /> |<br /> |<br /> |<br /> |}<br /> <br /> ==== Proposed for deletion (category, not content!) ====<br /> {| class="wikitable"<br /> !Name<br /> !Number of Pages<br /> !Reason for request for deletion<br /> |-<br /> |Accessories<br /> |0<br /> |what is mandatory? What is an accessory? better consider they are parts. the category has 0 page so far<br /> |-<br /> |Hardware<br /> |0<br /> |better call it parts - 0 page<br /> |-<br /> |ISA Shunt<br /> |1<br /> |this should not be a category on its own but a page of category "connector"<br /> |-<br /> |Chademo with Zombieverter<br /> |0<br /> |should be part of category chademo<br /> |-<br /> |Request for Review<br /> |1<br /> |this seldom used<br /> |-<br /> |OpenInverter Projects<br /> |<br /> |better have a combination of the "conversion" and the corresponding VCU category?<br /> |-<br /> |Introduction<br /> |<br /> |merge with Resource?<br /> |-<br /> |DEAD<br /> |1<br /> |possibly wrongly created in the first place<br /> |-<br /> |Delta<br /> |1<br /> |<br /> |-<br /> |General Tesla FAQ<br /> |1<br /> |should be a page part of category FAQ, not a category on its own.<br /> |}</div>

Powercontrol https://openinverter.org/wiki/index.php?title=Content_Management&diff=5774 Content Management 2025-05-10T14:33:14Z

<p>Powercontrol: </p> <hr /> <div>'''DRAFT - DRAFT - DRAFT'''<br /> <br /> the objective of this page is to explain how the content of the wiki page could be structured using Semantic for Mediawiki (SMW) to build a scalable and object-based wiki (for search and relation-building aspects) and still keeping the freedom for authors to create their content. There needs to be a trade-off to be found between freedom and structure.<br /> <br /> === Why Semantic for Mediawiki? ===<br /> SMW allows to have a form-based creation of objects. the form asks the users some key information then create the corresponding page and render the entered information in a consistent way, assign the category accordingly etc.<br /> <br /> Because the page created is based on a template, changing the template modifies the instantiation of the created pages. <br /> <br /> SMW also allows to create dynamic queries inside pages. The content will be modified based on other pages content. this is a powerful manner to make references to other pages without doing manual maintenance of the page. A practical and basic example would be that if the query below was inserted a page creation (a template being called by a form):<br /> <br /> <nowiki>{{#ask:<br /> [[FoundIn.Page::{{PAGENAME}}]]<br /> | format=list<br /> | link=all<br /> }}</nowiki><br /> The page content will update itself to list all other pages that refer to this new page. There are much more granular type of queries to be done (including on categories) which then become really handy.<br /> === General Principles and Naming Convention ===<br /> SMW uses multiple notions. They are key to be used properly for good use.<br /> {| class="wikitable"<br /> |+<br /> !Object<br /> !Usage<br /> !Naming Convention<br /> !Example<br /> |-<br /> |'''Page'''<br /> |the core component of the wiki and what readers are consuming. By default, there is no hierarchical structure of pages - and categories are the better way for structuring a wiki<br /> |each Word is start with a capital letter. Spaces and brackets are allowed. mutiple words are recommended to be separated by a space (mediawiki uses underscore instead of %20 for URL)<br /> '''''Title Case'''''<br /> |Nissan Leaf (2010-2017)<br /> |-<br /> |'''Category'''<br /> |the categories are part of the generic Mediawiki structure. its reflects a categorization or labeling of pages. Categories can be nested which are useful to reflect a structure of "component of" and for "is a subtype of". Multiple categories can be assigned to page, hence it can provide multiple view at once. A dedicated section of this page will cover their aspects.<br /> There are cases where it is not obvious whether a property or a category makes more sense. one does not prevent the other, by the way.<br /> |as the wiki already as categories created and they use naming similar to Page, the categories will further be named the same way.<br /> Ideally, categories shall be written in <u>plural form</u> (because it is a grouping of x) <br /> '''''Title Case (in plural)'''''<br /> |Batteries<br /> Connectors<br /> |-<br /> |'''Property'''<br /> |SMW specific - it defines a relation between 2 objects, or assign an attribute to an object. the target (called [[Special:Types]]) can be a list, another page. When defining a property, it would make sense to refer to a specific category of object (for instance, FoundIn would be referring to a Vehicle or a Component), but the type of object we can refer to are Pages, Numbers, Date,... nothing to do with category. <br /> |'''''UpperCamelCase.DestinationObjectType''''' or '''''UpperCamelCase.DestinationAttributeType'''''<br /> |FoundIn.Page<br /> HasWeight.Qty<br /> |-<br /> |'''Template'''<br /> |SMW specific - defines which properties values shall be defined at the creation of an object. Not all pages must be created using templates, but objects which have relations between themselves are best created using templates.<br /> |the template name shall refer to a corresponding category name in <u>singular</u>, and the template shall enforce that category at page creation.<br /> '''''T/UpperCamelCase.OutputFormat'''''<br /> |T/Connector.Infobox<br /> T/Battery.PlainText<br /> |-<br /> |'''Form'''<br /> |SMW specific - A Form is an helper for the author to create a templated object. The form allows to create a consistent visual structure to pages<br /> |'''''F/UpperCamelCase''''' - the Form refers to a corresponding Template, but the output format will not be referred to in the form name.<br /> A form can also call multiple templates - in such case its name will refer to the first one<br /> |F/Connector<br /> F/Battery<br /> |}<br /> <br /> === Categories ===<br /> At the time of writing, the following category structure exist: (in the absence of CategoryTree extension, doing my best to represent it):<br /> <br /> {| class="wikitable"<br /> ! Level 1 !! Level 2 !! Level 3 !! transferred<br /> |-<br /> | Basics || || ||x<br /> |-<br /> | Parts || Inverter || ||x<br /> |-<br /> | || Motor || || x<br /> |-<br /> | || Battery || || x<br /> |-<br /> | || Charger || Rapid Charging|| x<br /> |-<br /> | || DC/DC || || x<br /> |-<br /> | || HVJB (High Voltage Junction Box) || || x<br /> |-<br /> | || Contactor || || x<br /> |-<br /> | || PCB || || x<br /> |-<br /> | || CAN || || x<br /> |-<br /> | || LIN || || x<br /> |-<br /> | || ISA Shunt || || <br /> |-<br /> | || Accelerator Pedals and Position Sensors || || x<br /> |-<br /> | || Gearbox || || x<br /> |-<br /> | || Gear Selectors || || x<br /> |-<br /> | || Power Steering || || x<br /> |-<br /> | || Water Pumps || || x<br /> |-<br /> | || Arduino || || <br /> |-<br /> | || Adapter || || <br /> |-<br /> |<br /> |Thermal Management<br /> |AC Compressor<br /> |x<br /> |-<br /> | || || Heater Coolant|| x<br /> |-<br /> |<br /> |<br /> |Heater Air<br /> |x<br /> |-<br /> |<br /> |HVAC<br /> |Coolant Fittings<br /> |x<br /> |-<br /> |<br /> |<br /> |Coolant Valve<br /> |x<br /> |-<br /> | || ESP32 || || x<br /> |-<br /> | || ESP8266 || || x<br /> |-<br /> | || ZombieVerter || || x<br /> |-<br /> | || VCU || || x<br /> |-<br /> | OEM Manufacturers || BMW || || x<br /> |-<br /> | || Bosch || || x<br /> |-<br /> | || Chevrolet || || x<br /> |-<br /> | || Ford || || x<br /> |-<br /> | || Honda || || x<br /> |-<br /> | || Hyundai || || x<br /> |-<br /> | || Isabellenhütte || || x<br /> |-<br /> | || Land Rover || || x<br /> |-<br /> | || Lexus || || x<br /> |-<br /> | || Mercedes-Benz || || x<br /> |-<br /> | || MG || || x<br /> |-<br /> | || Mitsubishi || || x<br /> |-<br /> | || Nissan || || x<br /> |-<br /> | || Opel || || x<br /> |-<br /> | || Peugeot || || x<br /> |-<br /> | || Renault || || x<br /> |-<br /> | || Tesla || || x<br /> |-<br /> | || Toyota || || x<br /> |-<br /> | || VAG (Volkswagen Audi Group) || VW || x<br /> |-<br /> | || Vauxhall || || x<br /> |-<br /> | || Volvo || || x<br /> |-<br /> | Charging Systems || ChaDeMo || Chademo with Zombieverter || x<br /> |-<br /> | || CCS || || x<br /> |-<br /> | || Charge Ports || || x<br /> |-<br /> | || || ||<br /> |-<br /> | || Fast Charging || || x<br /> |-<br /> | Conversions || Mechanical || Parts || <br /> |-<br /> | || OpenInverter Projects || || <br /> |-<br /> | || OEM Repurposing || || <br /> |-<br /> | || Obsolete || || <br /> |-<br /> | Accessories || || ||<br /> |-<br /> | Education || || ||<br /> |-<br /> | Errors || || ||<br /> |-<br /> | Fix Links || || ||<br /> |-<br /> | || || ||<br /> |-<br /> | || || ||<br /> |-<br /> | || || ||<br /> |-<br /> | Request for Review || || ||<br /> |-<br /> | Troubleshoot || || ||<br /> |-<br /> | Webasto || || ||x<br /> |}<br /> <br /> <br /> I am proposing to shuffle the categories in such structure - bold/italic names are to be created<br /> <br /> ==== Manufacturers categories and structure ====<br /> the structure is meant to only identifies the group of brand (as they will likely be sharing components). Therefore, if a brand leaves a group to join another, a distinct brand category must be created.<br /> <br /> Model names (a specific category - see below) is attached to the brand related to its parent group (i.e. Opel Ampera is linked to GM, Opel Moka is linked to Stellantis). this structure gives us the flexibility to manage changing alliances/holdings over time. <br /> <br /> Cars are being sold with different names (Opel/Vauxhall, Renault/Mitsubishi etc), therefore, while the Page Name may refer to a specific brand-model combination, the car model <u>shall not</u> be a category on its own.<br /> <br /> <br /> The OEM Manufacturers shall include the groups that are delivering parts to car makers (Bosch, Magnetti Marelli etc)<br /> {| class="wikitable"<br /> |+<br /> !Top level<br /> !Group<br /> !Brand<br /> !Note<br /> |-<br /> |OEM Manufacturers<br /> |'''''BMW Group'''''<br /> |BMW<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Mini'''''<br /> |<br /> |-<br /> |<br /> |'''''General Motors'''''<br /> |Chevrolet<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Opel (<2017)'''''<br /> |the Opel Ampera was still under GM, so it is a completely different affiliation than today<br /> |-<br /> |<br /> |'''''Stellantis'''''<br /> |Opel (2017-)<br /> |the new ones<br /> |-<br /> |<br /> |<br /> |Vauxhall<br /> |<br /> |-<br /> |<br /> |<br /> |Peugeot<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Citroen'''''<br /> |<br /> |-<br /> |<br /> |'''''Toyota Motor Corporation'''''<br /> |Toyota<br /> |<br /> |-<br /> |<br /> |<br /> |Lexus<br /> |<br /> |-<br /> |<br /> |'''''Hyundai Motor Group'''''<br /> |Hyundai<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Kia'''''<br /> |<br /> |-<br /> |<br /> |'''''Renault-Nissan-Mitsubishi Alliance'''''<br /> |Mitsubishi<br /> |<br /> |-<br /> |<br /> |<br /> |Renault<br /> |<br /> |-<br /> |<br /> |<br /> |Nissan<br /> |<br /> |-<br /> |<br /> |'''''Ford Motor Corporation'''''<br /> |Ford<br /> |<br /> |-<br /> |<br /> |'''''Tata Motors'''''<br /> |Land Rover<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Jaguar'''''<br /> |<br /> |-<br /> |<br /> |VAG (Volkswagen Audi Group)<br /> |'''''Volkswagen'''''<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Audi'''''<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Skoda'''''<br /> |<br /> |-<br /> |<br /> |'''''Geely Holding Group'''''<br /> |Volvo<br /> |<br /> |-<br /> |<br /> |'''''SAIC Motor Europe'''''<br /> |MG<br /> |<br /> |-<br /> |<br /> |Honda<br /> |<br /> |<br /> |-<br /> |<br /> |Bosch<br /> |<br /> |<br /> |-<br /> |<br /> |Isabellenhütte<br /> |<br /> |<br /> |-<br /> |<br /> |Mercedes-Benz<br /> |<br /> |<br /> |-<br /> |<br /> |'''''BYD'''''<br /> |<br /> |<br /> |-<br /> |<br /> |Tesla<br /> |<br /> |<br /> |-<br /> |<br /> |Webasto<br /> |<br /> |moved under OEM Manufacturers<br /> |-<br /> |<br /> |'''''TE Connectivity'''''<br /> |<br /> |build connectors (notably for BMW)<br /> |-<br /> |<br /> |'''''Aptiv'''''<br /> |<br /> |build connectors (notably for Nissan) - ex Delphi (ex GM :-) )<br /> |-<br /> |<br /> |'''''Molex'''''<br /> |<br /> |build connectors (notably for Tesla)<br /> |-<br /> |<br /> |'''''Sumitomo'''''<br /> |<br /> |build connectors (notably for Mitsubishi)<br /> |-<br /> |<br /> |'''''Hirose'''''<br /> |<br /> |build connectors (notably for Mitsubishi)<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |}<br /> <br /> ==== Parts (Components) ====<br /> {| class="wikitable"<br /> !Top level<br /> !2nd level<br /> !3rd level<br /> !Note<br /> |-<br /> |Parts<br /> |Inverter<br /> |<br /> |<br /> |-<br /> |<br /> |Motor<br /> |<br /> |<br /> |-<br /> |<br /> |Brake Assist<br /> |<br /> |<br /> |-<br /> |<br /> |'''''Battery Packs'''''<br /> |'''''Battery modules'''''<br /> |this is a split of the battery cateogy<br /> |-<br /> |<br /> |<br /> |BMS<br /> |moved under Battery packs<br /> |-<br /> |<br /> |<br /> |Contactor<br /> |where SBOX, VBOX and Isabellenhutte should belong. moved under battery packs<br /> |-<br /> |<br /> |DC/DC<br /> |<br /> |<br /> |-<br /> |<br /> |HVJB (High Voltage Junction Box)<br /> |<br /> |<br /> |-<br /> |<br /> |Accelerator Pedals and Position Sensors<br /> |<br /> |<br /> |-<br /> |<br /> |Gearbox<br /> |<br /> |<br /> |-<br /> |<br /> |Gear Selectors<br /> |<br /> |<br /> |-<br /> |<br /> |Power Steering<br /> |<br /> |<br /> |-<br /> |<br /> |Charging Systems<br /> |ChaDeMo<br /> |<br /> |-<br /> |<br /> |<br /> |CCS<br /> |<br /> |-<br /> |<br /> |<br /> |Charge Ports<br /> |<br /> |-<br /> |<br /> |<br /> |Fast Charging<br /> |moved out of charger and under charging systems<br /> |-<br /> |<br /> |<br /> |Charger<br /> |moved under charging systems<br /> |-<br /> |<br /> |Thermal Management<br /> |AC Compressor<br /> |<br /> |-<br /> |<br /> |<br /> |Heater Coolant<br /> |<br /> |-<br /> |<br /> |<br /> |Heater Air<br /> |<br /> |-<br /> |<br /> |<br /> |Water Pumps<br /> |<br /> |-<br /> |<br /> |<br /> |HVAC<br /> |<br /> |-<br /> |<br /> |<br /> |Coolant Fittings<br /> |<br /> |-<br /> |<br /> |<br /> |Coolant Valve<br /> |<br /> |-<br /> |<br /> |'''''Connectors'''''<br /> |<br /> |<br /> |-<br /> |<br /> |'''''Cables'''''<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |VCU<br /> |<br /> |-<br /> |<br /> |<br /> |ESP32<br /> |<br /> |-<br /> |<br /> |<br /> |ESP8266<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |}<br /> <br /> ==== Communication, Software and Electronics ====<br /> {| class="wikitable"<br /> !Top level<br /> !2nd level<br /> !3rd level<br /> !Note<br /> |-<br /> |'''Electronics'''<br /> |VCU<br /> |Zombieverter<br /> |<br /> |-<br /> |<br /> |<br /> |Openinverter<br /> |<br /> |-<br /> |<br /> |'''''chipsets'''''<br /> |ESP32<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |ESP8266<br /> |<br /> |-<br /> |<br /> |PCB<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |'''''Communication'''''<br /> |CAN<br /> |'''''CANID'''''<br /> |category to define the CAN messages<br /> |-<br /> |<br /> |LIN<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |}<br /> <br /> ==== Other categories ====<br /> {| class="wikitable"<br /> !Top level<br /> !2nd level<br /> !3rd level<br /> !Note<br /> |-<br /> |Basics<br /> |Tutorials<br /> |<br /> |covers the necessary understanding required before envisaging a conversion project (maybe merge the 2 categories?)<br /> |-<br /> |Conversion<br /> |<br /> |<br /> |ongoing and succesful conversion projects<br /> |}<br /> <br /> ==== Proposed for deletion (category, not content!) ====<br /> {| class="wikitable"<br /> !Name<br /> !Number of Pages<br /> !Reason for request for deletion<br /> |-<br /> |Accessories<br /> |0<br /> |what is mandatory? What is an accessory? better consider they are parts. the category has 0 page so far<br /> |-<br /> |Hardware<br /> |0<br /> |better call it parts - 0 page<br /> |-<br /> |ISA Shunt<br /> |1<br /> |this should not be a category on its own but a page of category "connector"<br /> |}</div>

Powercontrol https://openinverter.org/wiki/index.php?title=Content_Management&diff=5773 Content Management 2025-05-10T14:22:07Z

<p>Powercontrol: ongoing work on categories</p> <hr /> <div>'''DRAFT - DRAFT - DRAFT'''<br /> <br /> the objective of this page is to explain how the content of the wiki page could be structured using Semantic for Mediawiki (SMW) to build a scalable and object-based wiki (for search and relation-building aspects) and still keeping the freedom for authors to create their content. There needs to be a trade-off to be found between freedom and structure.<br /> <br /> === Why Semantic for Mediawiki? ===<br /> SMW allows to have a form-based creation of objects. the form asks the users some key information then create the corresponding page and render the entered information in a consistent way, assign the category accordingly etc.<br /> <br /> Because the page created is based on a template, changing the template modifies the instantiation of the created pages. <br /> <br /> SMW also allows to create dynamic queries inside pages. The content will be modified based on other pages content. this is a powerful manner to make references to other pages without doing manual maintenance of the page. A practical and basic example would be that if the query below was inserted a page creation (a template being called by a form):<br /> <br /> <nowiki>{{#ask:<br /> [[FoundIn.Page::{{PAGENAME}}]]<br /> | format=list<br /> | link=all<br /> }}</nowiki><br /> The page content will update itself to list all other pages that refer to this new page. There are much more granular type of queries to be done (including on categories) which then become really handy.<br /> === General Principles and Naming Convention ===<br /> SMW uses multiple notions. They are key to be used properly for good use.<br /> {| class="wikitable"<br /> |+<br /> !Object<br /> !Usage<br /> !Naming Convention<br /> !Example<br /> |-<br /> |'''Page'''<br /> |the core component of the wiki and what readers are consuming. By default, there is no hierarchical structure of pages - and categories are the better way for structuring a wiki<br /> |each Word is start with a capital letter. Spaces and brackets are allowed. mutiple words are recommended to be separated by a space (mediawiki uses underscore instead of %20 for URL)<br /> '''''Title Case'''''<br /> |Nissan Leaf (2010-2017)<br /> |-<br /> |'''Category'''<br /> |the categories are part of the generic Mediawiki structure. its reflects a categorization or labeling of pages. Categories can be nested which are useful to reflect a structure of "component of" and for "is a subtype of". Multiple categories can be assigned to page, hence it can provide multiple view at once. A dedicated section of this page will cover their aspects.<br /> There are cases where it is not obvious whether a property or a category makes more sense. one does not prevent the other, by the way.<br /> |as the wiki already as categories created and they use naming similar to Page, the categories will further be named the same way.<br /> Ideally, categories shall be written in <u>plural form</u> (because it is a grouping of x) <br /> '''''Title Case (in plural)'''''<br /> |Batteries<br /> Connectors<br /> |-<br /> |'''Property'''<br /> |SMW specific - it defines a relation between 2 objects, or assign an attribute to an object. the target (called [[Special:Types]]) can be a list, another page. When defining a property, it would make sense to refer to a specific category of object (for instance, FoundIn would be referring to a Vehicle or a Component), but the type of object we can refer to are Pages, Numbers, Date,... nothing to do with category. <br /> |'''''UpperCamelCase.DestinationObjectType''''' or '''''UpperCamelCase.DestinationAttributeType'''''<br /> |FoundIn.Page<br /> HasWeight.Qty<br /> |-<br /> |'''Template'''<br /> |SMW specific - defines which properties values shall be defined at the creation of an object. Not all pages must be created using templates, but objects which have relations between themselves are best created using templates.<br /> |the template name shall refer to a corresponding category name in <u>singular</u>, and the template shall enforce that category at page creation.<br /> '''''T/UpperCamelCase.OutputFormat'''''<br /> |T/Connector.Infobox<br /> T/Battery.PlainText<br /> |-<br /> |'''Form'''<br /> |SMW specific - A Form is an helper for the author to create a templated object. The form allows to create a consistent visual structure to pages<br /> |'''''F/UpperCamelCase''''' - the Form refers to a corresponding Template, but the output format will not be referred to in the form name.<br /> A form can also call multiple templates - in such case its name will refer to the first one<br /> |F/Connector<br /> F/Battery<br /> |}<br /> <br /> === Categories ===<br /> At the time of writing, the following category structure exist: (in the absence of CategoryTree extension, doing my best to represent it):<br /> <br /> {| class="wikitable"<br /> ! Level 1 !! Level 2 !! Level 3 !! transferred<br /> |-<br /> | Basics || || ||x<br /> |-<br /> | Parts || Inverter || ||x<br /> |-<br /> | || Motor || || x<br /> |-<br /> | || Battery || || x<br /> |-<br /> | || Charger || Rapid Charging|| x<br /> |-<br /> | || DC/DC || || x<br /> |-<br /> | || HVJB (High Voltage Junction Box) || || x<br /> |-<br /> | || Contactor || || x<br /> |-<br /> | || PCB || || <br /> |-<br /> | || CAN || || <br /> |-<br /> | || LIN || || <br /> |-<br /> | || ISA Shunt || || <br /> |-<br /> | || Accelerator Pedals and Position Sensors || || x<br /> |-<br /> | || Gearbox || || x<br /> |-<br /> | || Gear Selectors || || x<br /> |-<br /> | || Power Steering || || x<br /> |-<br /> | || || || <br /> |-<br /> | || || || <br /> |-<br /> | || || || <br /> |-<br /> | || Water Pumps || || x<br /> |-<br /> | || Arduino || || <br /> |-<br /> | || Adapter || || <br /> |-<br /> |<br /> |Thermal Management<br /> |AC Compressor<br /> |x<br /> |-<br /> | || || Heater Coolant|| x<br /> |-<br /> |<br /> |<br /> |Heater Air<br /> |x<br /> |-<br /> |<br /> |HVAC<br /> |Coolant Fittings<br /> |x<br /> |-<br /> |<br /> |<br /> |Coolant Valve<br /> |x<br /> |-<br /> | || ESP32 || || x<br /> |-<br /> | || ESP8266 || || x<br /> |-<br /> | || ZombieVerter || || x<br /> |-<br /> | || VCU || || x<br /> |-<br /> | OEM Manufacturers || BMW || || x<br /> |-<br /> | || Bosch || || x<br /> |-<br /> | || Chevrolet || || x<br /> |-<br /> | || Ford || || x<br /> |-<br /> | || Honda || || x<br /> |-<br /> | || Hyundai || || x<br /> |-<br /> | || Isabellenhütte || || x<br /> |-<br /> | || Land Rover || || x<br /> |-<br /> | || Lexus || || x<br /> |-<br /> | || Mercedes-Benz || || x<br /> |-<br /> | || MG || || x<br /> |-<br /> | || Mitsubishi || || x<br /> |-<br /> | || Nissan || || x<br /> |-<br /> | || Opel || || x<br /> |-<br /> | || Peugeot || || x<br /> |-<br /> | || Renault || || x<br /> |-<br /> | || Tesla || || x<br /> |-<br /> | || Toyota || || x<br /> |-<br /> | || VAG (Volkswagen Audi Group) || VW || x<br /> |-<br /> | || Vauxhall || || x<br /> |-<br /> | || Volvo || || x<br /> |-<br /> | Charging Systems || ChaDeMo || Chademo with Zombieverter || x<br /> |-<br /> | || CCS || || x<br /> |-<br /> | || Charge Ports || || x<br /> |-<br /> | || || ||<br /> |-<br /> | || Fast Charging || || x<br /> |-<br /> | Conversions || Mechanical || Parts || <br /> |-<br /> | || OpenInverter Projects || || <br /> |-<br /> | || OEM Repurposing || || <br /> |-<br /> | || Obsolete || || <br /> |-<br /> | Accessories || || ||<br /> |-<br /> | Education || || ||<br /> |-<br /> | Errors || || ||<br /> |-<br /> | Fix Links || || ||<br /> |-<br /> | || || ||<br /> |-<br /> | || || ||<br /> |-<br /> | || || ||<br /> |-<br /> | Request for Review || || ||<br /> |-<br /> | Troubleshoot || || ||<br /> |-<br /> | Webasto || || ||x<br /> |}<br /> <br /> <br /> I am proposing to shuffle the categories in such structure - bold/italic names are to be created<br /> <br /> ==== Manufacturers categories and structure ====<br /> the structure is meant to only identifies the group of brand (as they will likely be sharing components). Therefore, if a brand leaves a group to join another, a distinct brand category must be created.<br /> <br /> Model names (a specific category - see below) is attached to the brand related to its parent group (i.e. Opel Ampera is linked to GM, Opel Moka is linked to Stellantis). this structure gives us the flexibility to manage changing alliances/holdings over time. <br /> <br /> Cars are being sold with different names (Opel/Vauxhall, Renault/Mitsubishi etc), therefore, while the Page Name may refer to a specific brand-model combination, the car model <u>shall not</u> be a category on its own.<br /> <br /> <br /> The OEM Manufacturers shall include the groups that are delivering parts to car makers (Bosch, Magnetti Marelli etc)<br /> {| class="wikitable"<br /> |+<br /> !Top level<br /> !Group<br /> !Brand<br /> !Note<br /> |-<br /> |OEM Manufacturers<br /> |'''''BMW Group'''''<br /> |BMW<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Mini'''''<br /> |<br /> |-<br /> |<br /> |'''''General Motors'''''<br /> |Chevrolet<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Opel (<2017)'''''<br /> |the Opel Ampera was still under GM, so it is a completely different affiliation than today<br /> |-<br /> |<br /> |'''''Stellantis'''''<br /> |Opel (2017-)<br /> |<br /> |-<br /> |<br /> |<br /> |Vauxhall<br /> |<br /> |-<br /> |<br /> |<br /> |Peugeot<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Citroen'''''<br /> |<br /> |-<br /> |<br /> |'''''Toyota Motor Corporation'''''<br /> |Toyota<br /> |<br /> |-<br /> |<br /> |<br /> |Lexus<br /> |<br /> |-<br /> |<br /> |'''''Hyundai Motor Group'''''<br /> |Hyundai<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Kia'''''<br /> |<br /> |-<br /> |<br /> |'''''Renault-Nissan-Mitsubishi Alliance'''''<br /> |Mitsubishi<br /> |<br /> |-<br /> |<br /> |<br /> |Renault<br /> |<br /> |-<br /> |<br /> |<br /> |Nissan<br /> |<br /> |-<br /> |<br /> |'''''Ford Motor Corporation'''''<br /> |Ford<br /> |<br /> |-<br /> |<br /> |'''''Tata Motors'''''<br /> |Land Rover<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Jaguar'''''<br /> |<br /> |-<br /> |<br /> |VAG (Volkswagen Audi Group)<br /> |'''''Volkswagen'''''<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Audi'''''<br /> |<br /> |-<br /> |<br /> |<br /> |'''''Skoda'''''<br /> |<br /> |-<br /> |<br /> |'''''Geely Holding Group'''''<br /> |Volvo<br /> |<br /> |-<br /> |<br /> |'''''SAIC Motor Europe'''''<br /> |MG<br /> |<br /> |-<br /> |<br /> |Honda<br /> |<br /> |<br /> |-<br /> |<br /> |Bosch<br /> |<br /> |<br /> |-<br /> |<br /> |Isabellenhütte<br /> |<br /> |<br /> |-<br /> |<br /> |Mercedes-Benz<br /> |<br /> |<br /> |-<br /> |<br /> |'''''BYD'''''<br /> |<br /> |<br /> |-<br /> |<br /> |Tesla<br /> |<br /> |<br /> |-<br /> |<br /> |Webasto<br /> |<br /> |moved under OEM Manufacturers<br /> |-<br /> |<br /> |'''''TE Connectivity'''''<br /> |<br /> |build connectors (notably for BMW)<br /> |-<br /> |<br /> |'''''Aptiv'''''<br /> |<br /> |build connectors (notably for Nissan)<br /> |-<br /> |<br /> |'''''Molex'''''<br /> |<br /> |build connectors (notably for Tesla)<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |}<br /> <br /> ==== Parts (Components) ====<br /> {| class="wikitable"<br /> !Top level<br /> !2nd level<br /> !3rd level<br /> !Note<br /> |-<br /> |Parts<br /> |Inverter<br /> |<br /> |<br /> |-<br /> |<br /> |Motor<br /> |<br /> |<br /> |-<br /> |<br /> |Brake Assist<br /> |<br /> |<br /> |-<br /> |<br /> |'''''Battery Packs'''''<br /> |'''''Battery modules'''''<br /> |this is a split of the battery cateogy<br /> |-<br /> |<br /> |<br /> |BMS<br /> |moved under Battery packs<br /> |-<br /> |<br /> |<br /> |Contactor<br /> |where SBOX, VBOX and Isabellenhutte should belong. moved under battery packs<br /> |-<br /> |<br /> |DC/DC<br /> |<br /> |<br /> |-<br /> |<br /> |HVJB (High Voltage Junction Box)<br /> |<br /> |<br /> |-<br /> |<br /> |Accelerator Pedals and Position Sensors<br /> |<br /> |<br /> |-<br /> |<br /> |Gearbox<br /> |<br /> |<br /> |-<br /> |<br /> |Gear Selectors<br /> |<br /> |<br /> |-<br /> |<br /> |Power Steering<br /> |<br /> |<br /> |-<br /> |<br /> |Charging Systems<br /> |ChaDeMo<br /> |<br /> |-<br /> |<br /> |<br /> |CCS<br /> |<br /> |-<br /> |<br /> |<br /> |Charge Ports<br /> |<br /> |-<br /> |<br /> |<br /> |Fast Charging<br /> |moved out of charger and under charging systems<br /> |-<br /> |<br /> |<br /> |Charger<br /> |moved under charging systems<br /> |-<br /> |<br /> |Thermal Management<br /> |AC Compressor<br /> |<br /> |-<br /> |<br /> |<br /> |Heater Coolant<br /> |<br /> |-<br /> |<br /> |<br /> |Heater Air<br /> |<br /> |-<br /> |<br /> |<br /> |Water Pumps<br /> |<br /> |-<br /> |<br /> |<br /> |HVAC<br /> |<br /> |-<br /> |<br /> |<br /> |Coolant Fittings<br /> |<br /> |-<br /> |<br /> |<br /> |Coolant Valve<br /> |<br /> |-<br /> |<br /> |'''''Connectors'''''<br /> |<br /> |<br /> |-<br /> |<br /> |'''''Cables'''''<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |VCU<br /> |<br /> |-<br /> |<br /> |<br /> |ESP32<br /> |<br /> |-<br /> |<br /> |<br /> |ESP8266<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |}<br /> <br /> ==== Software and Electronics ====<br /> {| class="wikitable"<br /> !Top level<br /> !2nd level<br /> !3rd level<br /> !Note<br /> |-<br /> |'''Electronics'''<br /> |VCU<br /> |Zombieverter<br /> |<br /> |-<br /> |<br /> |<br /> |ESP32<br /> |<br /> |-<br /> |<br /> |<br /> |ESP8266<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |}<br /> <br /> ==== Other categories ====<br /> {| class="wikitable"<br /> !Top level<br /> !2nd level<br /> !3rd level<br /> !Note<br /> |-<br /> |Basics<br /> |Tutorials<br /> |<br /> |covers the necessary understanding required before envisaging a conversion project (maybe merge the 2 categories?)<br /> |-<br /> |Conversion<br /> |<br /> |<br /> |ongoing and succesful conversion projects<br /> |}<br /> <br /> ==== Proposed for deletion ====<br /> {| class="wikitable"<br /> !Name<br /> !Number of Pages<br /> !Reason for request for deletion<br /> |-<br /> |Accessories<br /> |0<br /> |what is mandatory? What is an accessory? better consider they are parts. the category has 0 page so far<br /> |-<br /> |Hardware<br /> |0<br /> |better call it parts - 0 page<br /> |-<br /> |<br /> |<br /> |<br /> |}</div>

Powercontrol https://openinverter.org/wiki/index.php?title=Content_Management&diff=5771 Content Management 2025-05-10T12:19:52Z

<p>Powercontrol: /* Categories */</p> <hr /> <div>'''DRAFT - DRAFT - DRAFT'''<br /> <br /> the objective of this page is to explain how the content of the wiki page could be structured using Semantic for Mediawiki (SMW) to build a scalable and object-based wiki (for search and relation-building aspects) and still keeping the freedom for authors to create their content. There needs to be a trade-off to be found between freedom and structure.<br /> <br /> === Why Semantic for Mediawiki? ===<br /> SMW allows to have a form-based creation of objects. the form asks the users some key information then create the corresponding page and render the entered information in a consistent way, assign the category accordingly etc.<br /> <br /> Because the page created is based on a template, changing the template modifies the instantiation of the created pages. <br /> <br /> SMW also allows to create dynamic queries inside pages. The content will be modified based on other pages content. this is a powerful manner to make references to other pages without doing manual maintenance of the page. A practical and basic example would be that if the query below was inserted a page creation (a template being called by a form):<br /> <br /> <nowiki>{{#ask:<br /> [[FoundIn.Page::{{PAGENAME}}]]<br /> | format=list<br /> | link=all<br /> }}</nowiki><br /> The page content will update itself to list all other pages that refer to this new page. There are much more granular type of queries to be done (including on categories) which then become really handy.<br /> === General Principles and Naming Convention ===<br /> SMW uses multiple notions. They are key to be used properly for good use.<br /> {| class="wikitable"<br /> |+<br /> !Object<br /> !Usage<br /> !Naming Convention<br /> !Example<br /> |-<br /> |'''Page'''<br /> |the core component of the wiki and what readers are consuming. By default, there is no hierarchical structure of pages - and categories are the better way for structuring a wiki<br /> |each Word is start with a capital letter. Spaces and brackets are allowed. mutiple words are recommended to be separated by a space (mediawiki uses underscore instead of %20 for URL)<br /> '''''Title Case'''''<br /> |Nissan Leaf (2010-2017)<br /> |-<br /> |'''Category'''<br /> |the categories are part of the generic Mediawiki structure. its reflects a categorization or labeling of pages. Categories can be nested which are useful to reflect a structure of "component of" and for "is a subtype of". Multiple categories can be assigned to page, hence it can provide multiple view at once. A dedicated section of this page will cover their aspects.<br /> There are cases where it is not obvious whether a property or a category makes more sense. one does not prevent the other, by the way.<br /> |as the wiki already as categories created and they use naming similar to Page, the categories will further be named the same way. <br /> '''''Title Case'''''<br /> |Battery<br /> Connector<br /> |-<br /> |'''Property'''<br /> |SMW specific - it defines a relation between 2 objects, or assign an attribute to an object. the target (called [[Special:Types]]) can be a list, another page. When defining a property, it would make sense to refer to a specific category of object (for instance, FoundIn would be referring to a Vehicle or a Component), but the type of object we can refer to are Pages, Numbers, Date,... nothing to do with category. <br /> |'''''UpperCamelCase.DestinationObjectType''''' or '''''UpperCamelCase.DestinationAttributeType'''''<br /> |FoundIn.Page<br /> HasWeight.Qty<br /> |-<br /> |'''Template'''<br /> |SMW specific - defines which properties values shall be defined at the creation of an object. Not all pages must be created using templates, but objects which have relations between themselves are best created using templates.<br /> |the template name shall refer to a corresponding category name, and the template shall enforce that category at page creation.<br /> '''''T/UpperCamelCase.OutputFormat'''''<br /> |T/Connector.Infobox<br /> T/Battery.PlainText<br /> |-<br /> |'''Form'''<br /> |SMW specific - A Form is an helper for the author to create a templated object. The form allows to create a consistent visual structure to pages<br /> |'''''F/UpperCamelCase''''' - the Form refers to a corresponding Template, but the output format will not be referred to in the form name.<br /> A form can also call multiple templates - in such case its name will refer to the first one<br /> |F/Connector<br /> F/Battery<br /> |}<br /> <br /> === Categories ===<br /> At the time of writing, the following category structure exist: (in the absence of CategoryTree extension, doing my best to represent it):<br /> <br /> {| class="wikitable"<br /> ! Level 1 !! Level 2 !! Level 3 !! Level 4<br /> |-<br /> | Basics || || ||<br /> |-<br /> | Parts || Inverter || ||<br /> |-<br /> | || Motor || || <br /> |-<br /> | || Battery || || <br /> |-<br /> | || Charger || || <br /> |-<br /> | || DC/DC || || <br /> |-<br /> | || HVJB (High Voltage Junction Box) || || <br /> |-<br /> | || Contactor || || <br /> |-<br /> | || PCB || || <br /> |-<br /> | || CAN || || <br /> |-<br /> | || LIN || || <br /> |-<br /> | || ISA Shunt || || <br /> |-<br /> | || Accelerator Pedals and Position Sensors || || <br /> |-<br /> | || Gearbox || || <br /> |-<br /> | || Gear Selectors || || <br /> |-<br /> | || Power Steering || || <br /> |-<br /> | || HVAC || || <br /> |-<br /> | || Heater Air || || <br /> |-<br /> | || Heater Coolant || || <br /> |-<br /> | || Water Pumps || || <br /> |-<br /> | || AC Compressor || || <br /> |-<br /> | || Adapter || || <br /> |-<br /> | || Arduino || || <br /> |-<br /> | || ESP32 || || <br /> |-<br /> | || ESP8266 || || <br /> |-<br /> | || ZombieVerter || || <br /> |-<br /> | || VCU || || <br /> |-<br /> | OEM Manufacturers || BMW || || <br /> |-<br /> | || Bosch || || <br /> |-<br /> | || Chevrolet || || <br /> |-<br /> | || Ford || || <br /> |-<br /> | || Honda || || <br /> |-<br /> | || Hyundai || || <br /> |-<br /> | || Isabellenhütte || || <br /> |-<br /> | || Land Rover || || <br /> |-<br /> | || Lexus || || <br /> |-<br /> | || Mercedes-Benz || || <br /> |-<br /> | || MG || || <br /> |-<br /> | || Mitsubishi || || <br /> |-<br /> | || Nissan || || <br /> |-<br /> | || Opel || || <br /> |-<br /> | || Peugeot || || <br /> |-<br /> | || Renault || || <br /> |-<br /> | || Tesla || || <br /> |-<br /> | || Toyota || || <br /> |-<br /> | || VAG (Volkswagen Audi Group) || VW || <br /> |-<br /> | || Vauxhall || || <br /> |-<br /> | || Volvo || || <br /> |-<br /> | Charging Systems || ChaDeMo || Chademo with Zombieverter || <br /> |-<br /> | || CCS || || <br /> |-<br /> | || Charge Ports || || <br /> |-<br /> | || Rapid Charging || || <br /> |-<br /> | || Fast Charging || || <br /> |-<br /> | Conversions || Mechanical || Parts || <br /> |-<br /> | || OpenInverter Projects || || <br /> |-<br /> | || OEM Repurposing || || <br /> |-<br /> | || Obsolete || || <br /> |-<br /> | Accessories || || ||<br /> |-<br /> | Education || || ||<br /> |-<br /> | Errors || || ||<br /> |-<br /> | Fix Links || || ||<br /> |-<br /> | Imported Vocabulary || || ||<br /> |-<br /> | Pages with Broken File Links || || ||<br /> |-<br /> | Pages with Ignored Display Titles || || ||<br /> |-<br /> | Request for Review || || ||<br /> |-<br /> | Troubleshoot || || ||<br /> |-<br /> | Webasto || || ||<br /> |}<br /> <br /> <br /> I am proposing to shuffle the categories in such structure - italic names are to be created<br /> {| class="wikitable"<br /> |+<br /> !Top level<br /> !first level<br /> !second level<br /> !third level<br /> |-<br /> |Manufacturer<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |}</div>

Powercontrol https://openinverter.org/wiki/index.php?title=Content_Management&diff=5770 Content Management 2025-05-10T08:56:11Z

<p>Powercontrol: /* Categories */</p> <hr /> <div>'''DRAFT - DRAFT - DRAFT'''<br /> <br /> the objective of this page is to explain how the content of the wiki page could be structured using Semantic for Mediawiki (SMW) to build a scalable and object-based wiki (for search and relation-building aspects) and still keeping the freedom for authors to create their content. There needs to be a trade-off to be found between freedom and structure.<br /> <br /> === Why Semantic for Mediawiki? ===<br /> SMW allows to have a form-based creation of objects. the form asks the users some key information then create the corresponding page and render the entered information in a consistent way, assign the category accordingly etc.<br /> <br /> Because the page created is based on a template, changing the template modifies the instantiation of the created pages. <br /> <br /> SMW also allows to create dynamic queries inside pages. The content will be modified based on other pages content. this is a powerful manner to make references to other pages without doing manual maintenance of the page. A practical and basic example would be that if the query below was inserted a page creation (a template being called by a form):<br /> <br /> <nowiki>{{#ask:<br /> [[FoundIn.Page::{{PAGENAME}}]]<br /> | format=list<br /> | link=all<br /> }}</nowiki><br /> The page content will update itself to list all other pages that refer to this new page. There are much more granular type of queries to be done (including on categories) which then become really handy.<br /> === General Principles and Naming Convention ===<br /> SMW uses multiple notions. They are key to be used properly for good use.<br /> {| class="wikitable"<br /> |+<br /> !Object<br /> !Usage<br /> !Naming Convention<br /> !Example<br /> |-<br /> |'''Page'''<br /> |the core component of the wiki and what readers are consuming. By default, there is no hierarchical structure of pages - and categories are the better way for structuring a wiki<br /> |each Word is start with a capital letter. Spaces and brackets are allowed. mutiple words are recommended to be separated by a space (mediawiki uses underscore instead of %20 for URL)<br /> '''''Title Case'''''<br /> |Nissan Leaf (2010-2017)<br /> |-<br /> |'''Category'''<br /> |the categories are part of the generic Mediawiki structure. its reflects a categorization or labeling of pages. Categories can be nested which are useful to reflect a structure of "component of" and for "is a subtype of". Multiple categories can be assigned to page, hence it can provide multiple view at once. A dedicated section of this page will cover their aspects.<br /> There are cases where it is not obvious whether a property or a category makes more sense. one does not prevent the other, by the way.<br /> |as the wiki already as categories created and they use naming similar to Page, the categories will further be named the same way. <br /> '''''Title Case'''''<br /> |Battery<br /> Connector<br /> |-<br /> |'''Property'''<br /> |SMW specific - it defines a relation between 2 objects, or assign an attribute to an object. the target (called [[Special:Types]]) can be a list, another page. When defining a property, it would make sense to refer to a specific category of object (for instance, FoundIn would be referring to a Vehicle or a Component), but the type of object we can refer to are Pages, Numbers, Date,... nothing to do with category. <br /> |'''''UpperCamelCase.DestinationObjectType''''' or '''''UpperCamelCase.DestinationAttributeType'''''<br /> |FoundIn.Page<br /> HasWeight.Qty<br /> |-<br /> |'''Template'''<br /> |SMW specific - defines which properties values shall be defined at the creation of an object. Not all pages must be created using templates, but objects which have relations between themselves are best created using templates.<br /> |the template name shall refer to a corresponding category name, and the template shall enforce that category at page creation.<br /> '''''T/UpperCamelCase.OutputFormat'''''<br /> |T/Connector.Infobox<br /> T/Battery.PlainText<br /> |-<br /> |'''Form'''<br /> |SMW specific - A Form is an helper for the author to create a templated object. The form allows to create a consistent visual structure to pages<br /> |'''''F/UpperCamelCase''''' - the Form refers to a corresponding Template, but the output format will not be referred to in the form name.<br /> A form can also call multiple templates - in such case its name will refer to the first one<br /> |F/Connector<br /> F/Battery<br /> |}<br /> <br /> === Categories ===<br /> At the time of writing, the following category structure exist: (in the absence of CategoryTree extension, doing my best to represent it):<br /> <br /> {| class="wikitable"<br /> ! Level 1 !! Level 2 !! Level 3 !! Level 4<br /> |-<br /> | Basics || || ||<br /> |-<br /> | Inverter || || ||<br /> |-<br /> | || Motor || || <br /> |-<br /> | || Battery || || <br /> |-<br /> | || Charger || || <br /> |-<br /> | || DC/DC || || <br /> |-<br /> | || HVJB (High Voltage Junction Box) || || <br /> |-<br /> | || Contactor || || <br /> |-<br /> | || PCB || || <br /> |-<br /> | || CAN || || <br /> |-<br /> | || LIN || || <br /> |-<br /> | || ISA Shunt || || <br /> |-<br /> | || Accelerator Pedals and Position Sensors || || <br /> |-<br /> | || Gearbox || || <br /> |-<br /> | || Gear Selectors || || <br /> |-<br /> | || Power Steering || || <br /> |-<br /> | || HVAC || || <br /> |-<br /> | || Heater Air || || <br /> |-<br /> | || Heater Coolant || || <br /> |-<br /> | || Water Pumps || || <br /> |-<br /> | || AC Compressor || || <br /> |-<br /> | || Adapter || || <br /> |-<br /> | || Arduino || || <br /> |-<br /> | || ESP32 || || <br /> |-<br /> | || ESP8266 || || <br /> |-<br /> | || ZombieVerter || || <br /> |-<br /> | || VCU || || <br /> |-<br /> | OEM Manufacturers || BMW || || <br /> |-<br /> | || Bosch || || <br /> |-<br /> | || Chevrolet || || <br /> |-<br /> | || Ford || || <br /> |-<br /> | || Honda || || <br /> |-<br /> | || Hyundai || || <br /> |-<br /> | || Isabellenhütte || || <br /> |-<br /> | || Land Rover || || <br /> |-<br /> | || Lexus || || <br /> |-<br /> | || Mercedes-Benz || || <br /> |-<br /> | || MG || || <br /> |-<br /> | || Mitsubishi || || <br /> |-<br /> | || Nissan || || <br /> |-<br /> | || Opel || || <br /> |-<br /> | || Peugeot || || <br /> |-<br /> | || Renault || || <br /> |-<br /> | || Tesla || || <br /> |-<br /> | || Toyota || || <br /> |-<br /> | || VAG (Volkswagen Audi Group) || VW || <br /> |-<br /> | || Vauxhall || || <br /> |-<br /> | || Volvo || || <br /> |-<br /> | Charging Systems || ChaDeMo || Chademo with Zombieverter || <br /> |-<br /> | || CCS || || <br /> |-<br /> | || Charge Ports || || <br /> |-<br /> | || Rapid Charging || || <br /> |-<br /> | || Fast Charging || || <br /> |-<br /> | Conversions || Mechanical || Parts || <br /> |-<br /> | || OpenInverter Projects || || <br /> |-<br /> | || OEM Repurposing || || <br /> |-<br /> | || Obsolete || || <br /> |-<br /> | Accessories || || ||<br /> |-<br /> | Education || || ||<br /> |-<br /> | Errors || || ||<br /> |-<br /> | Fix Links || || ||<br /> |-<br /> | Imported Vocabulary || || ||<br /> |-<br /> | Pages with Broken File Links || || ||<br /> |-<br /> | Pages with Ignored Display Titles || || ||<br /> |-<br /> | Request for Review || || ||<br /> |-<br /> | Troubleshoot || || ||<br /> |-<br /> | Webasto || || ||<br /> |}<br /> <br /> <br /> I am proposing to shuffle the categories in such structure - italic names are to be created<br /> {| class="wikitable"<br /> |+<br /> !Top level<br /> !first level<br /> !second level<br /> !third level<br /> |-<br /> |Manufacturer<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |}</div>

Powercontrol https://openinverter.org/wiki/index.php?title=Content_Management&diff=5769 Content Management 2025-05-10T08:54:31Z

<p>Powercontrol: </p> <hr /> <div>'''DRAFT - DRAFT - DRAFT'''<br /> <br /> the objective of this page is to explain how the content of the wiki page could be structured using Semantic for Mediawiki (SMW) to build a scalable and object-based wiki (for search and relation-building aspects) and still keeping the freedom for authors to create their content. There needs to be a trade-off to be found between freedom and structure.<br /> <br /> === Why Semantic for Mediawiki? ===<br /> SMW allows to have a form-based creation of objects. the form asks the users some key information then create the corresponding page and render the entered information in a consistent way, assign the category accordingly etc.<br /> <br /> Because the page created is based on a template, changing the template modifies the instantiation of the created pages. <br /> <br /> SMW also allows to create dynamic queries inside pages. The content will be modified based on other pages content. this is a powerful manner to make references to other pages without doing manual maintenance of the page. A practical and basic example would be that if the query below was inserted a page creation (a template being called by a form):<br /> <br /> <nowiki>{{#ask:<br /> [[FoundIn.Page::{{PAGENAME}}]]<br /> | format=list<br /> | link=all<br /> }}</nowiki><br /> The page content will update itself to list all other pages that refer to this new page. There are much more granular type of queries to be done (including on categories) which then become really handy.<br /> === General Principles and Naming Convention ===<br /> SMW uses multiple notions. They are key to be used properly for good use.<br /> {| class="wikitable"<br /> |+<br /> !Object<br /> !Usage<br /> !Naming Convention<br /> !Example<br /> |-<br /> |'''Page'''<br /> |the core component of the wiki and what readers are consuming. By default, there is no hierarchical structure of pages - and categories are the better way for structuring a wiki<br /> |each Word is start with a capital letter. Spaces and brackets are allowed. mutiple words are recommended to be separated by a space (mediawiki uses underscore instead of %20 for URL)<br /> '''''Title Case'''''<br /> |Nissan Leaf (2010-2017)<br /> |-<br /> |'''Category'''<br /> |the categories are part of the generic Mediawiki structure. its reflects a categorization or labeling of pages. Categories can be nested which are useful to reflect a structure of "component of" and for "is a subtype of". Multiple categories can be assigned to page, hence it can provide multiple view at once. A dedicated section of this page will cover their aspects.<br /> There are cases where it is not obvious whether a property or a category makes more sense. one does not prevent the other, by the way.<br /> |as the wiki already as categories created and they use naming similar to Page, the categories will further be named the same way. <br /> '''''Title Case'''''<br /> |Battery<br /> Connector<br /> |-<br /> |'''Property'''<br /> |SMW specific - it defines a relation between 2 objects, or assign an attribute to an object. the target (called [[Special:Types]]) can be a list, another page. When defining a property, it would make sense to refer to a specific category of object (for instance, FoundIn would be referring to a Vehicle or a Component), but the type of object we can refer to are Pages, Numbers, Date,... nothing to do with category. <br /> |'''''UpperCamelCase.DestinationObjectType''''' or '''''UpperCamelCase.DestinationAttributeType'''''<br /> |FoundIn.Page<br /> HasWeight.Qty<br /> |-<br /> |'''Template'''<br /> |SMW specific - defines which properties values shall be defined at the creation of an object. Not all pages must be created using templates, but objects which have relations between themselves are best created using templates.<br /> |the template name shall refer to a corresponding category name, and the template shall enforce that category at page creation.<br /> '''''T/UpperCamelCase.OutputFormat'''''<br /> |T/Connector.Infobox<br /> T/Battery.PlainText<br /> |-<br /> |'''Form'''<br /> |SMW specific - A Form is an helper for the author to create a templated object. The form allows to create a consistent visual structure to pages<br /> |'''''F/UpperCamelCase''''' - the Form refers to a corresponding Template, but the output format will not be referred to in the form name.<br /> A form can also call multiple templates - in such case its name will refer to the first one<br /> |F/Connector<br /> F/Battery<br /> |}<br /> <br /> === Categories ===<br /> At the time of writing, the following category structure exist: (in the absence of CategoryTree extension, doing my best to represent it):<br /> <br /> {| class="wikitable"<br /> ! Level 1 !! Level 2 !! Level 3 !! Level 4<br /> |-<br /> | Basics || || ||<br /> |-<br /> | Inverter || || ||<br /> | | Motor || || <br /> | | Battery || || <br /> | | Charger || || <br /> | | DC/DC || || <br /> | | HVJB (High Voltage Junction Box) || || <br /> | | Contactor || || <br /> | | PCB || || <br /> | | CAN || || <br /> | | LIN || || <br /> | | ISA Shunt || || <br /> | | Accelerator Pedals and Position Sensors || || <br /> | | Gearbox || || <br /> | | Gear Selectors || || <br /> | | Power Steering || || <br /> | | HVAC || || <br /> | | Heater Air || || <br /> | | Heater Coolant || || <br /> | | Water Pumps || || <br /> | | AC Compressor || || <br /> | | Adapter || || <br /> | | Arduino || || <br /> | | ESP32 || || <br /> | | ESP8266 || || <br /> | | ZombieVerter || || <br /> | | VCU || || <br /> |-<br /> | OEM Manufacturers || BMW || || <br /> | | Bosch || || <br /> | | Chevrolet || || <br /> | | Ford || || <br /> | | Honda || || <br /> | | Hyundai || || <br /> | | Isabellenhütte || || <br /> | | Land Rover || || <br /> | | Lexus || || <br /> | | Mercedes-Benz || || <br /> | | MG || || <br /> | | Mitsubishi || || <br /> | | Nissan || || <br /> | | Opel || || <br /> | | Peugeot || || <br /> | | Renault || || <br /> | | Tesla || || <br /> | | Toyota || || <br /> | | VAG (Volkswagen Audi Group) || VW || <br /> | | Vauxhall || || <br /> | | Volvo || || <br /> |-<br /> | Charging Systems || ChaDeMo || Chademo with Zombieverter || <br /> | | CCS || || <br /> | | Charge Ports || || <br /> | | Rapid Charging || || <br /> | | Fast Charging || || <br /> |-<br /> | Conversions || Mechanical || Parts || <br /> | | OpenInverter Projects || || <br /> | | OEM Repurposing || || <br /> | | Obsolete || || <br /> |-<br /> | Accessories || || ||<br /> |-<br /> | Education || || ||<br /> |-<br /> | Errors || || ||<br /> |-<br /> | Fix Links || || ||<br /> |-<br /> | Imported Vocabulary || || ||<br /> |-<br /> | Pages with Broken File Links || || ||<br /> |-<br /> | Pages with Ignored Display Titles || || ||<br /> |-<br /> | Request for Review || || ||<br /> |-<br /> | Troubleshoot || || ||<br /> |-<br /> | Webasto || || ||<br /> |}<br /> <br /> <br /> I am proposing to shuffle the categories in such structure - italic names are to be created<br /> {| class="wikitable"<br /> |+<br /> !Top level<br /> !first level<br /> !second level<br /> !third level<br /> |-<br /> |Manufacturer<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |}</div>

Powercontrol https://openinverter.org/wiki/index.php?title=Content_Management&diff=5768 Content Management 2025-05-10T08:54:00Z

<p>Powercontrol: /* Categories */</p> <hr /> <div>'''DRAFT - DRAFT - DRAFT'''<br /> <br /> the objective of this page is to explain how the content of the wiki page could be structured using Semantic for Mediawiki (SMW) to build a scalable and object-based wiki (for search and relation-building aspects) and still keeping the freedom for authors to create their content. There needs to be a trade-off to be found between freedom and structure.<br /> <br /> === Why Semantic for Mediawiki? ===<br /> SMW allows to have a form-based creation of objects. the form asks the users some key information then create the corresponding page and render the entered information in a consistent way, assign the category accordingly etc.<br /> <br /> Because the page created is based on a template, changing the template modifies the instantiation of the created pages. <br /> <br /> SMW also allows to create dynamic queries inside pages. The content will be modified based on other pages content. this is a powerful manner to make references to other pages without doing manual maintenance of the page. A practical and basic example would be that if the query below was inserted a page creation (a template being called by a form):<br /> <br /> <nowiki>{{#ask:<br /> [[FoundIn.Page::{{PAGENAME}}]]<br /> | format=list<br /> | link=all<br /> }}</nowiki><br /> The page content will update itself to list all other pages that refer to this new page. There are much more granular type of queries to be done (including on categories) which then become really handy.<br /> === General Principles and Naming Convention ===<br /> SMW uses multiple notions. They are key to be used properly for good use.<br /> {| class="wikitable"<br /> |+<br /> !Object<br /> !Usage<br /> !Naming Convention<br /> !Example<br /> |-<br /> |'''Page'''<br /> |the core component of the wiki and what readers are consuming. By default, there is no hierarchical structure of pages - and categories are the better way for structuring a wiki<br /> |each Word is start with a capital letter. Spaces and brackets are allowed. mutiple words are recommended to be separated by a space (mediawiki uses underscore instead of %20 for URL)<br /> '''''Title Case'''''<br /> |Nissan Leaf (2010-2017)<br /> |-<br /> |'''Category'''<br /> |the categories are part of the generic Mediawiki structure. its reflects a categorization or labeling of pages. Categories can be nested which are useful to reflect a structure of "component of" and for "is a subtype of". Multiple categories can be assigned to page, hence it can provide multiple view at once. A dedicated section of this page will cover their aspects.<br /> There are cases where it is not obvious whether a property or a category makes more sense. one does not prevent the other, by the way.<br /> |as the wiki already as categories created and they use naming similar to Page, the categories will further be named the same way. <br /> '''''Title Case'''''<br /> |Battery<br /> Connector<br /> |-<br /> |'''Property'''<br /> |SMW specific - it defines a relation between 2 objects, or assign an attribute to an object. the target (called [[Special:Types]]) can be a list, another page. When defining a property, it would make sense to refer to a specific category of object (for instance, FoundIn would be referring to a Vehicle or a Component), but the type of object we can refer to are Pages, Numbers, Date,... nothing to do with category. <br /> |'''''UpperCamelCase.DestinationObjectType''''' or '''''UpperCamelCase.DestinationAttributeType'''''<br /> |FoundIn.Page<br /> HasWeight.Qty<br /> |-<br /> |'''Template'''<br /> |SMW specific - defines which properties values shall be defined at the creation of an object. Not all pages must be created using templates, but objects which have relations between themselves are best created using templates.<br /> |the template name shall refer to a corresponding category name, and the template shall enforce that category at page creation.<br /> '''''T/UpperCamelCase.OutputFormat'''''<br /> |T/Connector.Infobox<br /> T/Battery.PlainText<br /> |-<br /> |'''Form'''<br /> |SMW specific - A Form is an helper for the author to create a templated object. The form allows to create a consistent visual structure to pages<br /> |'''''F/UpperCamelCase''''' - the Form refers to a corresponding Template, but the output format will not be referred to in the form name.<br /> A form can also call multiple templates - in such case its name will refer to the first one<br /> |F/Connector<br /> F/Battery<br /> |}<br /> <br /> === Categories ===<br /> At the time of writing, the following category structure exist: (in the absence of CategoryTree extension, doing my best to represent it):<br /> <br /> {| class="wikitable sortable"<br /> ! Category<br /> ! Notes<br /> !(checked for new structure)<br /> |-<br /> | Basics ||<br /> |<br /> |-<br /> | Introduction ||<br /> |<br /> |-<br /> | Glossary of Terms ||<br /> |<br /> |-<br /> | FAQ ||<br /> |<br /> |-<br /> | Tutorials ||<br /> |<br /> |-<br /> | Legalities ||<br /> |<br /> |-<br /> | Resources ||<br /> |<br /> |-<br /> | Specs ||<br /> |<br /> |-<br /> | Standard ||<br /> |<br /> |-<br /> | Training ||<br /> |<br /> |-<br /> | Inverter || Technical Components<br /> |<br /> |-<br /> | Motor ||<br /> |<br /> |-<br /> | Battery ||<br /> |<br /> |-<br /> | Charger ||<br /> |<br /> |-<br /> | DC/DC ||<br /> |<br /> |-<br /> | HVJB (High Voltage Junction Box) ||<br /> |<br /> |-<br /> | Contactor ||<br /> |<br /> |-<br /> | PCB ||<br /> |<br /> |-<br /> | CAN ||<br /> |<br /> |-<br /> | LIN ||<br /> |<br /> |-<br /> | ISA Shunt ||<br /> |<br /> |-<br /> | Accelerator Pedals and Position Sensors ||<br /> |<br /> |-<br /> | Gearbox ||<br /> |<br /> |-<br /> | Gear Selectors ||<br /> |<br /> |-<br /> | Power Steering ||<br /> |<br /> |-<br /> | HVAC ||<br /> |<br /> |-<br /> | Heater Air ||<br /> |<br /> |-<br /> | Heater Coolant ||<br /> |<br /> |-<br /> | Water Pumps ||<br /> |<br /> |-<br /> | AC Compressor ||<br /> |<br /> |-<br /> | Adapter ||<br /> |<br /> |-<br /> | Arduino ||<br /> |<br /> |-<br /> | ESP32 ||<br /> |<br /> |-<br /> | ESP8266 ||<br /> |<br /> |-<br /> | ZombieVerter ||<br /> |<br /> |-<br /> | VCU ||<br /> |<br /> |-<br /> | BMW || OEM Manufacturers<br /> |<br /> |-<br /> | Bosch ||<br /> |<br /> |-<br /> | Chevrolet ||<br /> |<br /> |-<br /> | Ford ||<br /> |<br /> |-<br /> | Honda ||<br /> |<br /> |-<br /> | Hyundai ||<br /> |<br /> |-<br /> | Isabellenhütte ||<br /> |<br /> |-<br /> | Land Rover ||<br /> |<br /> |-<br /> | Lexus ||<br /> |<br /> |-<br /> | Mercedes-Benz ||<br /> |<br /> |-<br /> | MG ||<br /> |<br /> |-<br /> | Mitsubishi ||<br /> |<br /> |-<br /> | Nissan ||<br /> |<br /> |-<br /> | Opel ||<br /> |<br /> |-<br /> | Peugeot ||<br /> |<br /> |-<br /> | Renault ||<br /> |<br /> |-<br /> | Tesla ||<br /> |<br /> |-<br /> | Toyota ||<br /> |<br /> |-<br /> | VAG (Volkswagen Audi Group) ||<br /> |<br /> |-<br /> | Vauxhall ||<br /> |<br /> |-<br /> | Volvo ||<br /> |<br /> |-<br /> | VW ||<br /> |<br /> |-<br /> | ChaDeMo || Charging Systems<br /> |<br /> |-<br /> | Chademo with Zombieverter ||<br /> |<br /> |-<br /> | CCS ||<br /> |<br /> |-<br /> | Charge Ports ||<br /> |<br /> |-<br /> | Rapid Charging ||<br /> |<br /> |-<br /> | Fast Charging ||<br /> |<br /> |-<br /> | Conversions || Conversion Projects<br /> |<br /> |-<br /> | Mechanical ||<br /> |<br /> |-<br /> | Parts ||<br /> |<br /> |-<br /> | OpenInverter Projects ||<br /> |<br /> |-<br /> | OEM Repurposing ||<br /> |<br /> |-<br /> | Obsolete ||<br /> |<br /> |-<br /> | Accessories || Miscellaneous<br /> |<br /> |-<br /> | Education ||<br /> |<br /> |-<br /> | Errors ||<br /> |<br /> |-<br /> | Fix Links ||<br /> |<br /> |-<br /> | Imported Vocabulary ||<br /> |<br /> |-<br /> | Pages with Broken File Links ||<br /> |<br /> |-<br /> | Pages with Ignored Display Titles ||<br /> |<br /> |-<br /> | Request for Review ||<br /> |<br /> |-<br /> | Troubleshoot ||<br /> |<br /> |-<br /> | Webasto ||<br /> |<br /> |}<br /> I am proposing to shuffle the categories in such structure - italic names are to be created<br /> {| class="wikitable"<br /> |+<br /> !Top level<br /> !first level<br /> !second level<br /> !third level<br /> |-<br /> |Manufacturer<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |}</div>

Powercontrol https://openinverter.org/wiki/index.php?title=Content_Management&diff=5767 Content Management 2025-05-10T08:49:40Z

<p>Powercontrol: </p> <hr /> <div>'''DRAFT - DRAFT - DRAFT'''<br /> <br /> the objective of this page is to explain how the content of the wiki page could be structured using Semantic for Mediawiki (SMW) to build a scalable and object-based wiki (for search and relation-building aspects) and still keeping the freedom for authors to create their content. There needs to be a trade-off to be found between freedom and structure.<br /> <br /> === Why Semantic for Mediawiki? ===<br /> SMW allows to have a form-based creation of objects. the form asks the users some key information then create the corresponding page and render the entered information in a consistent way, assign the category accordingly etc.<br /> <br /> Because the page created is based on a template, changing the template modifies the instantiation of the created pages. <br /> <br /> SMW also allows to create dynamic queries inside pages. The content will be modified based on other pages content. this is a powerful manner to make references to other pages without doing manual maintenance of the page. A practical and basic example would be that if the query below was inserted a page creation (a template being called by a form):<br /> <br /> <nowiki>{{#ask:<br /> [[FoundIn.Page::{{PAGENAME}}]]<br /> | format=list<br /> | link=all<br /> }}</nowiki><br /> The page content will update itself to list all other pages that refer to this new page. There are much more granular type of queries to be done (including on categories) which then become really handy.<br /> === General Principles and Naming Convention ===<br /> SMW uses multiple notions. They are key to be used properly for good use.<br /> {| class="wikitable"<br /> |+<br /> !Object<br /> !Usage<br /> !Naming Convention<br /> !Example<br /> |-<br /> |'''Page'''<br /> |the core component of the wiki and what readers are consuming. By default, there is no hierarchical structure of pages - and categories are the better way for structuring a wiki<br /> |each Word is start with a capital letter. Spaces and brackets are allowed. mutiple words are recommended to be separated by a space (mediawiki uses underscore instead of %20 for URL)<br /> '''''Title Case'''''<br /> |Nissan Leaf (2010-2017)<br /> |-<br /> |'''Category'''<br /> |the categories are part of the generic Mediawiki structure. its reflects a categorization or labeling of pages. Categories can be nested which are useful to reflect a structure of "component of" and for "is a subtype of". Multiple categories can be assigned to page, hence it can provide multiple view at once. A dedicated section of this page will cover their aspects.<br /> There are cases where it is not obvious whether a property or a category makes more sense. one does not prevent the other, by the way.<br /> |as the wiki already as categories created and they use naming similar to Page, the categories will further be named the same way. <br /> '''''Title Case'''''<br /> |Battery<br /> Connector<br /> |-<br /> |'''Property'''<br /> |SMW specific - it defines a relation between 2 objects, or assign an attribute to an object. the target (called [[Special:Types]]) can be a list, another page. When defining a property, it would make sense to refer to a specific category of object (for instance, FoundIn would be referring to a Vehicle or a Component), but the type of object we can refer to are Pages, Numbers, Date,... nothing to do with category. <br /> |'''''UpperCamelCase.DestinationObjectType''''' or '''''UpperCamelCase.DestinationAttributeType'''''<br /> |FoundIn.Page<br /> HasWeight.Qty<br /> |-<br /> |'''Template'''<br /> |SMW specific - defines which properties values shall be defined at the creation of an object. Not all pages must be created using templates, but objects which have relations between themselves are best created using templates.<br /> |the template name shall refer to a corresponding category name, and the template shall enforce that category at page creation.<br /> '''''T/UpperCamelCase.OutputFormat'''''<br /> |T/Connector.Infobox<br /> T/Battery.PlainText<br /> |-<br /> |'''Form'''<br /> |SMW specific - A Form is an helper for the author to create a templated object. The form allows to create a consistent visual structure to pages<br /> |'''''F/UpperCamelCase''''' - the Form refers to a corresponding Template, but the output format will not be referred to in the form name.<br /> A form can also call multiple templates - in such case its name will refer to the first one<br /> |F/Connector<br /> F/Battery<br /> |}<br /> <br /> === Categories ===<br /> At the time of writing, the following category structure exist: (in the absence of CategoryTree extension, doing my best to represent it):<br /> {| class="wikitable sortable"<br /> ! Category<br /> ! Notes<br /> |-<br /> | Basics ||<br /> |-<br /> | Introduction ||<br /> |-<br /> | Glossary of Terms ||<br /> |-<br /> | FAQ ||<br /> |-<br /> | Tutorials ||<br /> |-<br /> | Legalities ||<br /> |-<br /> | Resources ||<br /> |-<br /> | Specs ||<br /> |-<br /> | Standard ||<br /> |-<br /> | Training ||<br /> |-<br /> | Inverter || Technical Components<br /> |-<br /> | Motor || <br /> |-<br /> | Battery || <br /> |-<br /> | Charger || <br /> |-<br /> | DC/DC || <br /> |-<br /> | HVJB (High Voltage Junction Box) || <br /> |-<br /> | Contactor || <br /> |-<br /> | PCB || <br /> |-<br /> | CAN || <br /> |-<br /> | LIN || <br /> |-<br /> | ISA Shunt || <br /> |-<br /> | Accelerator Pedals and Position Sensors || <br /> |-<br /> | Gearbox || <br /> |-<br /> | Gear Selectors || <br /> |-<br /> | Power Steering || <br /> |-<br /> | HVAC || <br /> |-<br /> | Heater Air || <br /> |-<br /> | Heater Coolant || <br /> |-<br /> | Water Pumps || <br /> |-<br /> | AC Compressor || <br /> |-<br /> | Adapter || <br /> |-<br /> | Arduino || <br /> |-<br /> | ESP32 || <br /> |-<br /> | ESP8266 || <br /> |-<br /> | ZombieVerter || <br /> |-<br /> | VCU || <br /> |-<br /> | BMW || OEM Manufacturers<br /> |-<br /> | Bosch || <br /> |-<br /> | Chevrolet || <br /> |-<br /> | Ford || <br /> |-<br /> | Honda || <br /> |-<br /> | Hyundai || <br /> |-<br /> | Isabellenhütte || <br /> |-<br /> | Land Rover || <br /> |-<br /> | Lexus || <br /> |-<br /> | Mercedes-Benz || <br /> |-<br /> | MG || <br /> |-<br /> | Mitsubishi || <br /> |-<br /> | Nissan || <br /> |-<br /> | Opel || <br /> |-<br /> | Peugeot || <br /> |-<br /> | Renault || <br /> |-<br /> | Tesla || <br /> |-<br /> | Toyota || <br /> |-<br /> | VAG (Volkswagen Audi Group) || <br /> |-<br /> | Vauxhall || <br /> |-<br /> | Volvo || <br /> |-<br /> | VW || <br /> |-<br /> | ChaDeMo || Charging Systems<br /> |-<br /> | Chademo with Zombieverter || <br /> |-<br /> | CCS || <br /> |-<br /> | Charge Ports || <br /> |-<br /> | Rapid Charging || <br /> |-<br /> | Fast Charging || <br /> |-<br /> | Conversions || Conversion Projects<br /> |-<br /> | Mechanical || <br /> |-<br /> | Parts || <br /> |-<br /> | OpenInverter Projects || <br /> |-<br /> | OEM Repurposing || <br /> |-<br /> | Obsolete || <br /> |-<br /> | Accessories || Miscellaneous<br /> |-<br /> | Education || <br /> |-<br /> | Errors || <br /> |-<br /> | Fix Links || <br /> |-<br /> | Imported Vocabulary || <br /> |-<br /> | Pages with Broken File Links || <br /> |-<br /> | Pages with Ignored Display Titles || <br /> |-<br /> | Request for Review || <br /> |-<br /> | Troubleshoot || <br /> |-<br /> | Webasto || <br /> |}</div>

Powercontrol https://openinverter.org/wiki/index.php?title=Content_Management&diff=5766 Content Management 2025-05-10T08:49:27Z

<p>Powercontrol: </p> <hr /> <div>'''DRAFT - DRAFT - DRAFT'''<br /> <br /> the objective of this page is to explain how the content of the wiki page could be structured using Semantic for Mediawiki (SMW) to build a scalable and object-based wiki (for search and relation-building aspects) and still keeping the freedom for authors to create their content. There needs to be a trade-off to be found between freedom and structure.<br /> <br /> === Why Semantic for Mediawiki? ===<br /> SMW allows to have a form-based creation of objects. the form asks the users some key information then create the corresponding page and render the entered information in a consistent way, assign the category accordingly etc.<br /> <br /> Because the page created is based on a template, changing the template modifies the instantiation of the created pages. <br /> <br /> SMW also allows to create dynamic queries inside pages. The content will be modified based on other pages content. this is a powerful manner to make references to other pages without doing manual maintenance of the page. A practical and basic example would be that if the query below was inserted a page creation (a template being called by a form):<br /> <br /> <nowiki>{{#ask:<br /> [[FoundIn.Page::{{PAGENAME}}]]<br /> | format=list<br /> | link=all<br /> }}</nowiki><br /> The page content will update itself to list all other pages that refer to this new page. There are much more granular type of queries to be done (including on categories) which then become really handy.<br /> === General Principles and Naming Convention ===<br /> SMW uses multiple notions. They are key to be used properly for good use.<br /> {| class="wikitable"<br /> |+<br /> !Object<br /> !Usage<br /> !Naming Convention<br /> !Example<br /> |-<br /> |'''Page'''<br /> |the core component of the wiki and what readers are consuming. By default, there is no hierarchical structure of pages - and categories are the better way for structuring a wiki<br /> |each Word is start with a capital letter. Spaces and brackets are allowed. mutiple words are recommended to be separated by a space (mediawiki uses underscore instead of %20 for URL)<br /> '''''Title Case'''''<br /> |Nissan Leaf (2010-2017)<br /> |-<br /> |'''Category'''<br /> |the categories are part of the generic Mediawiki structure. its reflects a categorization or labeling of pages. Categories can be nested which are useful to reflect a structure of "component of" and for "is a subtype of". Multiple categories can be assigned to page, hence it can provide multiple view at once. A dedicated section of this page will cover their aspects.<br /> There are cases where it is not obvious whether a property or a category makes more sense. one does not prevent the other, by the way.<br /> |as the wiki already as categories created and they use naming similar to Page, the categories will further be named the same way. <br /> '''''Title Case'''''<br /> |Battery<br /> Connector<br /> |-<br /> |'''Property'''<br /> |SMW specific - it defines a relation between 2 objects, or assign an attribute to an object. the target (called [[Special:Types]]) can be a list, another page. When defining a property, it would make sense to refer to a specific category of object (for instance, FoundIn would be referring to a Vehicle or a Component), but the type of object we can refer to are Pages, Numbers, Date,... nothing to do with category. <br /> |'''''UpperCamelCase.DestinationObjectType''''' or '''''UpperCamelCase.DestinationAttributeType'''''<br /> |FoundIn.Page<br /> HasWeight.Qty<br /> |-<br /> |'''Template'''<br /> |SMW specific - defines which properties values shall be defined at the creation of an object. Not all pages must be created using templates, but objects which have relations between themselves are best created using templates.<br /> |the template name shall refer to a corresponding category name, and the template shall enforce that category at page creation.<br /> '''''T/UpperCamelCase.OutputFormat'''''<br /> |T/Connector.Infobox<br /> T/Battery.PlainText<br /> |-<br /> |'''Form'''<br /> |SMW specific - A Form is an helper for the author to create a templated object. The form allows to create a consistent visual structure to pages<br /> |'''''F/UpperCamelCase''''' - the Form refers to a corresponding Template, but the output format will not be referred to in the form name.<br /> A form can also call multiple templates - in such case its name will refer to the first one<br /> |F/Connector<br /> F/Battery<br /> |}<br /> <br /> === Categories ===<br /> At the time of writing, the following category structure exist: (in the absence of CategoryTree extension, doing my best to represent it):</div>

Powercontrol https://openinverter.org/wiki/index.php?title=Content_Management&diff=5765 Content Management 2025-05-10T08:41:18Z

<p>Powercontrol: </p> <hr /> <div>'''DRAFT - DRAFT - DRAFT'''<br /> <br /> the objective of this page is to explain how the content of the wiki page could be structured using Semantic for Mediawiki (SMW) to build a scalable and object-based wiki (for search and relation-building aspects) and still keeping the freedom for authors to create their content. There needs to be a trade-off to be found between freedom and structure.<br /> <br /> === Why Semantic for Mediawiki? ===<br /> SMW allows to have a form-based creation of objects. the form asks the users some key information then create the corresponding page and render the entered information in a consistent way, assign the category accordingly etc.<br /> <br /> Because the page created is based on a template, changing the template modifies the instantiation of the created pages. <br /> <br /> SMW also allows to create dynamic queries inside pages. The content will be modified based on other pages content. this is a powerful manner to make references to other pages without doing manual maintenance of the page. A practical and basic example would be that if the query below was inserted a page creation (a template being called by a form):<br /> <br /> <nowiki>{{#ask:<br /> [[FoundIn.Page::{{PAGENAME}}]]<br /> | format=list<br /> | link=all<br /> }}</nowiki><br /> The page content will update itself to list all other pages that refer to this new page. There are much more granular type of queries to be done (including on categories) which then become really handy.<br /> === General Principles and Naming Convention ===<br /> SMW uses multiple notions. They are key to be used properly for good use.<br /> {| class="wikitable"<br /> |+<br /> !Object<br /> !Usage<br /> !Naming Convention<br /> !Example<br /> |-<br /> |'''Page'''<br /> |the core component of the wiki and what readers are consuming. By default, there is no hierarchical structure of pages - and categories are the better way for structuring a wiki<br /> |each Word is start with a capital letter. Spaces and brackets are allowed. mutiple words are recommended to be separated by a space (mediawiki uses underscore instead of %20 for URL)<br /> '''''Title Case'''''<br /> |Nissan Leaf (2010-2017)<br /> |-<br /> |'''Category'''<br /> |the categories are part of the generic Mediawiki structure. its reflects a categorization or labeling of pages. Categories can be nested which are useful to reflect a structure of "component of" and for "is a subtype of". Multiple categories can be assigned to page, hence it can provide multiple view at once. A dedicated section of this page will cover their aspects.<br /> There are cases where it is not obvious whether a property or a category makes more sense. one does not prevent the other, by the way.<br /> |as the wiki already as categories created and they use naming similar to Page, the categories will further be named the same way. <br /> '''''Title Case'''''<br /> |Battery<br /> Connector<br /> |-<br /> |'''Property'''<br /> |SMW specific - it defines a relation between 2 objects, or assign an attribute to an object. the target (called [[Special:Types]]) can be a list, another page. When defining a property, it would make sense to refer to a specific category of object (for instance, FoundIn would be referring to a Vehicle or a Component), but the type of object we can refer to are Pages, Numbers, Date,... nothing to do with category. <br /> |'''''UpperCamelCase.DestinationObjectType''''' or '''''UpperCamelCase.DestinationAttributeType'''''<br /> |FoundIn.Page<br /> HasWeight.Qty<br /> |-<br /> |'''Template'''<br /> |SMW specific - defines which properties values shall be defined at the creation of an object. Not all pages must be created using templates, but objects which have relations between themselves are best created using templates.<br /> |the template name shall refer to a corresponding category name, and the template shall enforce that category at page creation.<br /> '''''T/UpperCamelCase.OutputFormat'''''<br /> |T/Connector.Infobox<br /> T/Battery.PlainText<br /> |-<br /> |'''Form'''<br /> |SMW specific - A Form is an helper for the author to create a templated object. The form allows to create a consistent visual structure to pages<br /> |'''''F/UpperCamelCase''''' - the Form refers to a corresponding Template, but the output format will not be referred to in the form name.<br /> A form can also call multiple templates - in such case its name will refer to the first one<br /> |F/Connector<br /> F/Battery<br /> |}<br /> <br /> === Categories ===<br /> At the time of writing, the following category structure exist:<br /> <br /> <categorytree mode=pages depth=10> Categories </categorytree></div>

Powercontrol https://openinverter.org/wiki/index.php?title=Content_Management&diff=5764 Content Management 2025-05-10T08:34:36Z

<p>Powercontrol: /* Why Semantic for Mediawiki? */</p> <hr /> <div>'''DRAFT - DRAFT - DRAFT'''<br /> <br /> the objective of this page is to explain how the content of the wiki page could be structured using Semantic for Mediawiki (SMW) to build a scalable and object-based wiki (for search and relation-building aspects) and still keeping the freedom for authors to create their content. There needs to be a trade-off to be found between freedom and structure.<br /> <br /> === Why Semantic for Mediawiki? ===<br /> SMW allows to have a form-based creation of objects. the form asks the users some key information then create the corresponding page and render the entered information in a consistent way, assign the category accordingly etc.<br /> <br /> Because the page created is based on a template, changing the template modifies the instantiation of the created pages. <br /> <br /> SMW also allows to create dynamic queries inside pages. The content will be modified based on other pages content. this is a powerful manner to make references to other pages without doing manual maintenance of the page. A practical and basic example would be that if the query below was inserted a page creation (a template being called by a form):<br /> <br /> <nowiki>{{#ask:<br /> [[FoundIn.Page::{{PAGENAME}}]]<br /> | format=list<br /> | link=all<br /> }}</nowiki><br /> The page content will update itself to list all other pages that refer to this new page. There are much more granular type of queries to be done (including on categories) which then become really handy.<br /> === General Principles and Naming Convention ===<br /> SMW uses multiple notions. They are key to be used properly for good use.<br /> {| class="wikitable"<br /> |+<br /> !Object<br /> !Usage<br /> !Naming Convention<br /> !Example<br /> |-<br /> |'''Page'''<br /> |the core component of the wiki and what readers are consuming. By default, there is no hierarchical structure of pages - and categories are the better way for structuring a wiki<br /> |each Word is start with a capital letter. Spaces and brackets are allowed. mutiple words are recommended to be separated by a space (mediawiki uses underscore instead of %20 for URL)<br /> '''''Title Case'''''<br /> |Nissan Leaf (2010-2017)<br /> |-<br /> |'''Category'''<br /> |the categories are part of the generic Mediawiki structure. its reflects a categorization or labeling of pages. Categories can be nested which are useful to reflect a structure of "component of" and for "is a subtype of". Multiple categories can be assigned to page, hence it can provide multiple view at once. A dedicated section of this page will cover their aspects.<br /> There are cases where it is not obvious whether a property or a category makes more sense. one does not prevent the other, by the way.<br /> |as the wiki already as categories created and they use naming similar to Page, the categories will further be named the same way. <br /> '''''Title Case'''''<br /> |Battery<br /> Connector<br /> |-<br /> |'''Property'''<br /> |SMW specific - it defines a relation between 2 objects, or assign an attribute to an object. the target (called [[Special:Types]]) can be a list, another page. When defining a property, it would make sense to refer to a specific category of object (for instance, FoundIn would be referring to a Vehicle or a Component), but the type of object we can refer to are Pages, Numbers, Date,... nothing to do with category. <br /> |'''''UpperCamelCase.DestinationObjectType''''' or '''''UpperCamelCase.DestinationAttributeType'''''<br /> |FoundIn.Page<br /> HasWeight.Qty<br /> |-<br /> |'''Template'''<br /> |SMW specific - defines which properties shall be defined at the creation of an object. Not all pages must be created using templates, but objects which have relations between themselves are best created using templates.<br /> |the template name shall refer to a corresponding category name, and the template shall enforce that category at page creation.<br /> '''''T/UpperCamelCase.OutputFormat'''''<br /> |T/Connector.Infobox<br /> T/Battery.PlainText<br /> |-<br /> |'''Form'''<br /> |SMW specific - A Form is an helper for the author to create a templated object. The form allows to create a consistent visual structure to pages<br /> |'''''F/UpperCamelCase''''' - the Form refers to a corresponding Template, but the output format will not be referred to in the form name.<br /> A form can also call multiple templates - in such case its name will refer to the first one<br /> |F/Connector<br /> F/Battery<br /> |}<br /> <br /> === Categories ===<br /> At the time of writing, the following category structure exist:<br /> <br /> <categorytree mode=pages depth=10> Categories </categorytree></div>

Powercontrol https://openinverter.org/wiki/index.php?title=Content_Management&diff=5763 Content Management 2025-05-10T08:12:45Z

<p>Powercontrol: /* Why Semantic for Mediawiki? */</p> <hr /> <div>'''DRAFT - DRAFT - DRAFT'''<br /> <br /> <br /> the objective of this page is to explain how the content of the wiki page could be structured using Semantic for Mediawiki (SMW) to build a scalable and object-based wiki (for search and relation-building aspects) and still keeping the freedom for authors to create their content. There needs to be a trade-off to be found between freedom and structure.<br /> <br /> === General principles and naming convention ===<br /> SMW uses multiple notions. They are key to be used properly for good use.<br /> {| class="wikitable"<br /> |+<br /> !Object<br /> !Usage<br /> !Naming Convention<br /> !Example<br /> |-<br /> |'''Page'''<br /> |the core component of the wiki and what readers are consuming. By default, there is no hierarchical structure of pages - and categories are the better way for structuring a wiki<br /> |each Word is start with a capital letter. Spaces and brackets are allowed. mutiple words are recommended to be separated by a space (mediawiki uses underscore instead of %20 for URL)<br /> |Nissan Leaf (2010-2017)<br /> |-<br /> |'''Category'''<br /> |the categories are part of the generic Mediawiki structure. its reflects a categorization or labeling of pages. Categories can be nested which are useful to reflect a structure of "component of" and for "is a subtype of". Multiple categories can be assigned to page, hence it can provide multiple view at once. A dedicated section of this page will cover their aspects.<br /> There are cases where it is not obvious whether a property or a category makes more sense. one does not prevent the other, by the way.<br /> |'''''UpperCamelCase'''''<br /> |Battery<br /> Connector<br /> |-<br /> |'''Property'''<br /> |SMW specific - it defines a relation between 2 objects, or assign an attribute to an object. the target can be a list, another page <br /> |'''''UpperCamelCase.DestinationObjectType''''' or '''''UpperCamelCase.DestinationAttributeType'''''<br /> |FoundIn.Page<br /> HasWeight.Qty<br /> |-<br /> |'''Template'''<br /> |SMW specific - defines which properties shall be defined at the creation of an object. Not all pages must be created using templates, but objects which have relations between themselves are best created using templates.<br /> |the template name shall refer to a corresponding category name, and the template shall enforce that category at page creation.<br /> '''''T/UpperCamelCase.OutputFormat'''''<br /> |T/Connector.Infobox<br /> T/Battery.Table<br /> |-<br /> |'''Form'''<br /> |SMW specific - A Form is an helper for the author to create a templated object. The form allows to create a consistent visual structure to pages<br /> |'''''F/UpperCamelCase''''' - the Form refers to a corresponding Template, but the output format will not be referred to in the form name.<br /> A form can also call multiple templates - in such case its name will refer to the first one<br /> |F/Connector<br /> F/Battery<br /> |}<br /> <br /> === Why Semantic for Mediawiki? ===<br /> SMW allows to create dynamic queries inside pages. The content will be modified based on other pages content. this is a powerful manner to make references to other pages without doing manual maintenance of the page. A practical example would be that if the query below was inserted a page creation (a template being called by a form), the page content will update itself to list all other pages that refer to this new page.<br /> <nowiki><br /> {{#ask:<br /> [[Found in::{{PAGENAME}}]]<br /> | format=list<br /> | link=all<br /> }}<br /> </nowiki></div>

Powercontrol https://openinverter.org/wiki/index.php?title=Content_Management&diff=5762 Content Management 2025-05-10T08:10:25Z

<p>Powercontrol: </p> <hr /> <div>'''DRAFT - DRAFT - DRAFT'''<br /> <br /> <br /> the objective of this page is to explain how the content of the wiki page could be structured using Semantic for Mediawiki (SMW) to build a scalable and object-based wiki (for search and relation-building aspects) and still keeping the freedom for authors to create their content. There needs to be a trade-off to be found between freedom and structure.<br /> <br /> === General principles and naming convention ===<br /> SMW uses multiple notions. They are key to be used properly for good use.<br /> {| class="wikitable"<br /> |+<br /> !Object<br /> !Usage<br /> !Naming Convention<br /> !Example<br /> |-<br /> |'''Page'''<br /> |the core component of the wiki and what readers are consuming. By default, there is no hierarchical structure of pages - and categories are the better way for structuring a wiki<br /> |each Word is start with a capital letter. Spaces and brackets are allowed. mutiple words are recommended to be separated by a space (mediawiki uses underscore instead of %20 for URL)<br /> |Nissan Leaf (2010-2017)<br /> |-<br /> |'''Category'''<br /> |the categories are part of the generic Mediawiki structure. its reflects a categorization or labeling of pages. Categories can be nested which are useful to reflect a structure of "component of" and for "is a subtype of". Multiple categories can be assigned to page, hence it can provide multiple view at once. A dedicated section of this page will cover their aspects.<br /> There are cases where it is not obvious whether a property or a category makes more sense. one does not prevent the other, by the way.<br /> |'''''UpperCamelCase'''''<br /> |Battery<br /> Connector<br /> |-<br /> |'''Property'''<br /> |SMW specific - it defines a relation between 2 objects, or assign an attribute to an object. the target can be a list, another page <br /> |'''''UpperCamelCase.DestinationObjectType''''' or '''''UpperCamelCase.DestinationAttributeType'''''<br /> |FoundIn.Page<br /> HasWeight.Qty<br /> |-<br /> |'''Template'''<br /> |SMW specific - defines which properties shall be defined at the creation of an object. Not all pages must be created using templates, but objects which have relations between themselves are best created using templates.<br /> |the template name shall refer to a corresponding category name, and the template shall enforce that category at page creation.<br /> '''''T/UpperCamelCase.OutputFormat'''''<br /> |T/Connector.Infobox<br /> T/Battery.Table<br /> |-<br /> |'''Form'''<br /> |SMW specific - A Form is an helper for the author to create a templated object. The form allows to create a consistent visual structure to pages<br /> |'''''F/UpperCamelCase''''' - the Form refers to a corresponding Template, but the output format will not be referred to in the form name.<br /> A form can also call multiple templates - in such case its name will refer to the first one<br /> |F/Connector<br /> F/Battery<br /> |}<br /> <br /> === Why Semantic for Mediawiki? ===<br /> SMW allows to create dynamic queries inside pages. The content will be modified based on other pages content. this is a powerful manner to make references to other pages without doing manual maintenance of the page. A practical example would be:</div>

Powercontrol https://openinverter.org/wiki/index.php?title=Content_Management&diff=5761 Content Management 2025-05-10T08:05:51Z

<p>Powercontrol: </p> <hr /> <div>'''DRAFT - DRAFT - DRAFT'''<br /> <br /> <br /> the objective of this page is to explain how the content of the wiki page could be structured using Semantic for Mediawiki (SMW) to build a scalable and object-based wiki (for search and relation-building aspects) and still keeping the freedom for authors to create their content. There needs to be a trade-off to be found between freedom and structure.<br /> <br /> === General principles and naming convention ===<br /> SMW uses multiple notions. They are key to be used properly for good use.<br /> {| class="wikitable"<br /> |+<br /> !Object<br /> !Usage<br /> !Naming Convention<br /> !Example<br /> |-<br /> |Page<br /> |the core component of the wiki and what readers are consuming. By default, there is no hierarchical structure of pages - and categories are the better way for structuring a wiki<br /> |each Word is start with a capital letter. Spaces and brackets are allowed. mutiple words are recommended to be separated by a space (mediawiki uses underscore instead of %20 for URL)<br /> |Nissan Leaf (2010-2017)<br /> |-<br /> |Category<br /> |the categories are part of the generic Mediawiki structure. its reflects a categorization or labeling of pages. Categories can be nested which are useful to reflect a structure of "component of" and for "is a subtype of". Multiple categories can be assigned to page, hence it can provide multiple view at once. A dedicated section of this page will cover their aspects.<br /> There are cases where it is not obvious whether a property or a category makes more sense. one does not prevent the other, by the way.<br /> |UpperCamelCase<br /> |Battery<br /> Connector<br /> |-<br /> |Property<br /> |SMW specific - it defines a relation between 2 objects, or assign an attribute to an object. the target can be a list, another page <br /> |UpperCamelCase.DestinationObjectType or UpperCamelCase.DestinationAttributeType<br /> |FoundIn.Page<br /> HasWeight.Qty<br /> |-<br /> |Template<br /> |SMW specific - defines which properties shall be defined at the creation of an object. Not all pages must be created using templates, but objects which have relations between themselves are best created using templates.<br /> |the template name shall refer to a corresponding category name, and the template shall enforce that category at page creation.<br /> T/UpperCamelCase.OutputFormat<br /> |T/Connector.Infobox<br /> T/Battery.Table<br /> |-<br /> |Form<br /> |SMW specific - A Form is an helper for the author to create a templated object. The form allows to create a consistent visual structure to pages<br /> |F/UpperCamelCase - the Form refers to a corresponding Template, but the output format will not be referred to in the form name.<br /> A form can also call multiple templates - in such case its name will refer to the first one<br /> |F/Connector<br /> F/Battery<br /> |}<br /> <br /> === Why Semantic for Mediawiki? ===<br /> Aside of the ones reflected in the principles, Page naming is important. Page cannot be renamed. In practice, renaming a page will create a link from the old name to the new name, which eventually clutters the wiki.</div>

Powercontrol https://openinverter.org/wiki/index.php?title=Content_Management&diff=5760 Content Management 2025-05-10T07:11:07Z

<p>Powercontrol: initial commit</p> <hr /> <div>'''DRAFT - DRAFT - DRAFT'''<br /> <br /> <br /> the objective of this page is to explain how the content of the wiki page could be structured using Semantic for Mediawiki (SMW) to build a scalable and object-based wiki (for search and relation-building aspects) and still keeping the freedom for authors to create their content. There needs to be a trade-off to be found between freedom and structure.<br /> <br /> === Principles ===<br /> SMW uses multiple notions. They are key to be used properly for good use.<br /> {| class="wikitable"<br /> |+<br /> !Object<br /> !Usage<br /> !Naming Convention<br /> !Example<br /> |-<br /> |Property<br /> |defines a relation between 2 objects, or assign an attribute to an object <br /> |UpperCamelCase.DestinationObjectType or UpperCamelCase.DestinationAttributeType<br /> |FoundIn.Page<br /> HasWeight.Qty<br /> |-<br /> |Template<br /> |defines which properties shall be defined at the creation of an object. Not all pages must be created using templates, but objects which have relations between themselves are best created using templates.<br /> |T/UpperCamelCase.OutputFormat<br /> |T/Connector.Infobox<br /> T/Battery.Table<br /> |-<br /> |Form<br /> |A Form is an helper for the author to create a templated object. The form allows to create a consistent visual structure to pages<br /> |F/UpperCamelCase - the Form refers to a corresponding Template, but the output format will not be referred to in the form name.<br /> A form can also call mulitple templates<br /> |F/Connector<br /> F/Battery<br /> |}</div>

Powercontrol https://openinverter.org/wiki/index.php?title=CANID_0x5BC&diff=5738 CANID 0x5BC 2025-05-07T09:15:49Z

<p>Powercontrol: </p> <hr /> <div><br /> * '''CAN ID''': 0x5BC<br /> * '''Name''': x5BC<br /> * '''Data length (DLC)''': 8<br /> * '''Transmitter''': HVBAT<br /> <br /> == Byte-Level Representation [ 0 --> 7] ==<br /> {| class="wikitable" style="text-align:left; width: 100%; table-layout: fixed;"<br /> |+ Byte-Level Layout<br /> ! Byte 0 !! Byte 1 !! Byte 2 !! Byte 3 !! Byte 4 !! Byte 5 !! Byte 6 !! Byte 7<br /> |-<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-0" | [[#LB_Remain_Capacity_GIDS|LB_Remain_Capacity_GIDS]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-1" | [[#LB_Remain_Capacity_GIDS|LB_Remain_Capacity_GIDS]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-2" | [[#CapacityBars|CapacityBars]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-3" | [[#LB_Temperature_Segment_For_Dash|LB_Temperature_Segment_For_Dash]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-4" | [[#LB_Capacity_Deterioration_Rate|LB_Capacity_Deterioration_Rate]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-5" | [[#LB_Remain_Charge_Time_Condition|LB_Remain_Charge_Time_Condition]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-6" | [[#LB_Remain_Charge_Time|LB_Remain_Charge_Time]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-7" | [[#LB_Remain_Charge_Time|LB_Remain_Charge_Time]]<br /> |}<br /> <br /> == Bit-Level Views [7 --> 0] ==<br /> {| class="wikitable" style="text-align:left; width: 100%; table-layout: fixed;"<br /> |+ Bit-Level Layout of Byte 2<br /> ! Bit 7 !! Bit 6 !! Bit 5 !! Bit 4 !! Bit 3 !! Bit 2 !! Bit 1 !! Bit 0<br /> |-<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-2" | [[#CapacityBars|CapacityBars]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-2" | [[#CapacityBars|CapacityBars]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-2" | [[#CapacityBars|CapacityBars]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-2" | [[#CapacityBars|CapacityBars]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-2" | Reserved<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-2" | Reserved<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-2" | Reserved<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-2" | Reserved<br /> |}<br /> <br /> {| class="wikitable" style="text-align:left; width: 100%; table-layout: fixed;"<br /> |+ Bit-Level Layout of Byte 4<br /> ! Bit 7 !! Bit 6 !! Bit 5 !! Bit 4 !! Bit 3 !! Bit 2 !! Bit 1 !! Bit 0<br /> |-<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-4" | [[#LB_Capacity_Deterioration_Rate|LB_Capacity_Deterioration_Rate]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-4" | [[#LB_Capacity_Deterioration_Rate|LB_Capacity_Deterioration_Rate]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-4" | [[#LB_Capacity_Deterioration_Rate|LB_Capacity_Deterioration_Rate]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-4" | [[#LB_Capacity_Deterioration_Rate|LB_Capacity_Deterioration_Rate]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-4" | [[#LB_Capacity_Deterioration_Rate|LB_Capacity_Deterioration_Rate]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-4" | [[#LB_Capacity_Deterioration_Rate|LB_Capacity_Deterioration_Rate]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-4" | [[#LB_Capacity_Deterioration_Rate|LB_Capacity_Deterioration_Rate]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-4" | [[#Mux_5BC|Mux_5BC]]<br /> |}<br /> <br /> {| class="wikitable" style="text-align:left; width: 100%; table-layout: fixed;"<br /> |+ Bit-Level Layout of Byte 5<br /> ! Bit 7 !! Bit 6 !! Bit 5 !! Bit 4 !! Bit 3 !! Bit 2 !! Bit 1 !! Bit 0<br /> |-<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-5" | [[#LB_Output_Power_Limit_Reason|LB_Output_Power_Limit_Reason]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-5" | [[#LB_Output_Power_Limit_Reason|LB_Output_Power_Limit_Reason]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-5" | [[#LB_Remain_Charge_Time_Condition|LB_Remain_Charge_Time_Condition]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-5" | [[#LB_Remain_Charge_Time_Condition|LB_Remain_Charge_Time_Condition]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-5" | [[#LB_Remain_Charge_Time_Condition|LB_Remain_Charge_Time_Condition]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-5" | [[#LB_Remain_Charge_Time_Condition|LB_Remain_Charge_Time_Condition]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-5" | [[#LB_Remain_Charge_Time_Condition|LB_Remain_Charge_Time_Condition]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-5" | Reserved<br /> |}<br /> <br /> == Signal Definitions ==<br /> {| class="wikitable"<br /> |+ Detailed Signal Information<br /> ! Signal Name !! Start Bit !! Length (bits) !! Factor !! Offset !! Unit !! Minimum !! Maximum !! Description<br /> |-<br /> | <span id="LB_Remain_Capacity_GIDS">LB_Remain_Capacity_GIDS</span> || 7 || 10 || 1 || 0 || gids || 0 || 500 || 0-281 for 24kWh, 0-363 for 30kWh, 0-498 for 40kWh, 0-775 for 62kWh<br /> 1 LSB = 80WH<br /> <br /> LB_CAPR (aka 'gids') is an 80Wh resolution capacity indication used by the GOM and combined with LB_FULLCAP on gen1 Leafs to generate the capacity dashes behind the GOM.<br /> |-<br /> | <span id="LB_Remaining_Capacity_Segments">LB_Remaining_Capacity_Segments</span> || 16 || 8 || 1 || 0 || – || 0 || 240 || Contains chargebars and capacitybars, alternating depending on mux. Simplified lower down in the message<br /> |-<br /> | <span id="ChargeBars">ChargeBars</span> || 20 || 4 || 1 || 0 || - || 0 || 15 || Range 0-15 (Below data from test at 0%SOC, writing values to bus)<br /> 15 = 12 chargebars<br /> 14 = 12 chargebars<br /> 13 = 11 chargebars<br /> 12 = 10 chargebars<br /> 11 = 9 chargebars<br /> 10 = 8 chargebars !<br /> 9 = 8 chargebars !<br /> 8 = 7 chargebars<br /> 7 = 6 chargebars<br /> 6 = 5 chargebars<br /> 5 = 4 chargebars !<br /> 4 = 4 chargebars !<br /> 3 = 3 chargebars<br /> 2 = 2 chargebars<br /> 1 = 1 chargebars<br /> 0 = 0 chargebars<br /> |-<br /> | <span id="CapacityBars">CapacityBars</span> || 20 || 4 || 1 || 0 || - || 0 || 15 || Range 0-15 Below test data by writing to bus and seeing what happens<br /> 15 = 12 capacitybars<br /> 14 = 12 capacitybars<br /> 13 = 11 capacitybars<br /> 12 = 10 capacitybars<br /> 11 = 9 capacitybars<br /> 10 = 8 capacitybars !<br /> 9 = 8 capacitybars !<br /> 8 = 7 capacitybars<br /> 7 = 6 capacitybars<br /> 6 = 5 capacitybars<br /> 5 = 4 capacitybars !<br /> 4 = 4 capacitybars !<br /> 3 = 3 capacitybars<br /> 2 = 2 capacitybars<br /> 1 = 1 capacitybars<br /> 0 = 0 capacitybars,<br /> |-<br /> | <span id="LB_Temperature_Segment_For_Dash">LB_Temperature_Segment_For_Dash</span> || 24 || 8 || 0.4166666 || 0 || % || 0 || 100 || For instrumentation cluster. Unit is %, times 5/12 according to documentation, kinda strange .Should be average of the 3 sensors inside the battery pack.<br /> |-<br /> | <span id="LB_Remain_Cap_Segment_Swit_Flag">LB_Remain_Cap_Segment_Swit_Flag</span> || 32 || 1 || 1 || 0 || status || 0 || 1 || <br /> |-<br /> | <span id="Mux_5BC">Mux_5BC</span> || 32 || 4 || 1 || 0 || – || – || – || Multiplexor<br /> |-<br /> | <span id="LB_Capacity_Deterioration_Rate">LB_Capacity_Deterioration_Rate</span> || 33 || 7 || 1 || 0 || % || 0 || 100 || SOH (State-of-Health) Effects the charge gauge, lower numbers mean more chargebars<br /> |-<br /> | <span id="LB_MaxGIDS">LB_MaxGIDS</span> || 44 || 1 || 1 || 0 || – || – || – || Only 30kWh AZE0 has this. When this value is 1, the GIDS number is at its maximum.(LB_Remain_Capacity_GIDS)<br /> |-<br /> | <span id="LB_Output_Power_Limit_Reason">LB_Output_Power_Limit_Reason</span> || 45 || 3 || 1 || 0 || modemask || 0 || 7 || Indicates why power is limited<br /> |-<br /> | <span id="LB_Remain_Charge_Time_Condition">LB_Remain_Charge_Time_Condition</span> || 41 || 5 || 1 || 0 || modemask || 0 || 30 || Mux for LB_Remain_charge_time<br /> <br /> 00000b = Quick charge 01001b = Normal Charge 200V SOC100% 01010b = Normal Charge 200V SOC80% 10001b = Normal Charge 100V SOC100% 10010b = Normal Charge 100V SOC80% 11111b = Invalid value<br /> |-<br /> | <span id="LB_Remain_Charge_Time">LB_Remain_Charge_Time</span> || 52 || 13 || 1 || 0 || minutes || 0 || 8190 || 1FFFh is used as "Unavailable value"<br /> |}<br /> [[Category:Nissan]][[Category:BMS]][[Category:Battery]][[Category:CAN]]</div>

Powercontrol https://openinverter.org/wiki/index.php?title=CANID_0x5BC&diff=5737 CANID 0x5BC 2025-05-07T09:14:58Z

<p>Powercontrol: </p> <hr /> <div><br /> * '''CAN ID''': 0x5BC<br /> * '''Name''': x5BC<br /> * '''Data length (DLC)''': 8<br /> * '''Transmitter''': HVBAT<br /> <br /> == Byte-Level Representation [ 0 --> 7] ==<br /> {| class="wikitable" style="text-align:left; width: 100%; table-layout: fixed;"<br /> |+ Byte-Level Layout<br /> ! Byte 0 !! Byte 1 !! Byte 2 !! Byte 3 !! Byte 4 !! Byte 5 !! Byte 6 !! Byte 7<br /> |-<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-0" | [[#LB_Remain_Capacity_GIDS|LB_Remain_Capacity_GIDS]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-1" | [[#LB_Remain_Capacity_GIDS|LB_Remain_Capacity_GIDS]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-2" | [[#CapacityBars|CapacityBars]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-3" | [[#LB_Temperature_Segment_For_Dash|LB_Temperature_Segment_For_Dash]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-4" | [[#LB_Capacity_Deterioration_Rate|LB_Capacity_Deterioration_Rate]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-5" | [[#LB_Remain_Charge_Time_Condition|LB_Remain_Charge_Time_Condition]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-6" | [[#LB_Remain_Charge_Time|LB_Remain_Charge_Time]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-7" | [[#LB_Remain_Charge_Time|LB_Remain_Charge_Time]]<br /> |}<br /> <br /> == Bit-Level Views [7 --> 0] ==<br /> {| class="wikitable" style="text-align:left; width: 100%; table-layout: fixed;"<br /> |+ Bit-Level Layout of Byte 2<br /> ! Bit 7 !! Bit 6 !! Bit 5 !! Bit 4 !! Bit 3 !! Bit 2 !! Bit 1 !! Bit 0<br /> |-<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-2" | [[#CapacityBars|CapacityBars]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-2" | [[#CapacityBars|CapacityBars]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-2" | [[#CapacityBars|CapacityBars]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-2" | [[#CapacityBars|CapacityBars]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-2" | Reserved<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-2" | Reserved<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-2" | Reserved<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-2" | Reserved<br /> |}<br /> <br /> {| class="wikitable" style="text-align:left; width: 100%; table-layout: fixed;"<br /> |+ Bit-Level Layout of Byte 4<br /> ! Bit 7 !! Bit 6 !! Bit 5 !! Bit 4 !! Bit 3 !! Bit 2 !! Bit 1 !! Bit 0<br /> |-<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-4" | [[#LB_Capacity_Deterioration_Rate|LB_Capacity_Deterioration_Rate]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-4" | [[#LB_Capacity_Deterioration_Rate|LB_Capacity_Deterioration_Rate]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-4" | [[#LB_Capacity_Deterioration_Rate|LB_Capacity_Deterioration_Rate]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-4" | [[#LB_Capacity_Deterioration_Rate|LB_Capacity_Deterioration_Rate]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-4" | [[#LB_Capacity_Deterioration_Rate|LB_Capacity_Deterioration_Rate]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-4" | [[#LB_Capacity_Deterioration_Rate|LB_Capacity_Deterioration_Rate]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-4" | [[#LB_Capacity_Deterioration_Rate|LB_Capacity_Deterioration_Rate]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-4" | [[#Mux_5BC|Mux_5BC]]<br /> |}<br /> <br /> {| class="wikitable" style="text-align:left; width: 100%; table-layout: fixed;"<br /> |+ Bit-Level Layout of Byte 5<br /> ! Bit 7 !! Bit 6 !! Bit 5 !! Bit 4 !! Bit 3 !! Bit 2 !! Bit 1 !! Bit 0<br /> |-<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-5" | [[#LB_Output_Power_Limit_Reason|LB_Output_Power_Limit_Reason]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-5" | [[#LB_Output_Power_Limit_Reason|LB_Output_Power_Limit_Reason]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-5" | [[#LB_Remain_Charge_Time_Condition|LB_Remain_Charge_Time_Condition]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-5" | [[#LB_Remain_Charge_Time_Condition|LB_Remain_Charge_Time_Condition]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-5" | [[#LB_Remain_Charge_Time_Condition|LB_Remain_Charge_Time_Condition]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-5" | [[#LB_Remain_Charge_Time_Condition|LB_Remain_Charge_Time_Condition]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-5" | [[#LB_Remain_Charge_Time_Condition|LB_Remain_Charge_Time_Condition]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-5" | Reserved<br /> |}<br /> <br /> == Signal Definitions ==<br /> {| class="wikitable"<br /> |+ Detailed Signal Information<br /> ! Signal Name !! Start Bit !! Length (bits) !! Factor !! Offset !! Unit !! Minimum !! Maximum !! Description<br /> |-<br /> | <span id="LB_Remain_Capacity_GIDS">LB_Remain_Capacity_GIDS</span> || 7 || 10 || 1 || 0 || gids || 0 || 500 || 0-281 for 24kWh, 0-363 for 30kWh, 0-498 for 40kWh, 0-775 for 62kWh<br /> 1 LSB = 80WH<br /> <br /> LB_CAPR (aka 'gids') is an 80Wh resolution capacity indication used by the GOM and combined with LB_FULLCAP on gen1 Leafs to generate the capacity dashes behind the GOM.<br /> |-<br /> | <span id="LB_Remaining_Capacity_Segments">LB_Remaining_Capacity_Segments</span> || 16 || 8 || 1 || 0 || – || 0 || 240 || Contains chargebars and capacitybars, alternating depending on mux. Simplified lower down in the message<br /> |-<br /> | <span id="ChargeBars">ChargeBars</span> || 20 || 4 || 1 || 0 || - || 0 || 15 || Range 0-15 (Below data from test at 0%SOC, writing values to bus)<br /> 15 = 12 chargebars<br /> 14 = 12 chargebars<br /> 13 = 11 chargebars<br /> 12 = 10 chargebars<br /> 11 = 9 chargebars<br /> 10 = 8 chargebars !<br /> 9 = 8 chargebars !<br /> 8 = 7 chargebars<br /> 7 = 6 chargebars<br /> 6 = 5 chargebars<br /> 5 = 4 chargebars !<br /> 4 = 4 chargebars !<br /> 3 = 3 chargebars<br /> 2 = 2 chargebars<br /> 1 = 1 chargebars<br /> 0 = 0 chargebars<br /> |-<br /> | <span id="CapacityBars">CapacityBars</span> || 20 || 4 || 1 || 0 || - || 0 || 15 || Range 0-15 Below test data by writing to bus and seeing what happens<br /> 15 = 12 capacitybars<br /> 14 = 12 capacitybars<br /> 13 = 11 capacitybars<br /> 12 = 10 capacitybars<br /> 11 = 9 capacitybars<br /> 10 = 8 capacitybars !<br /> 9 = 8 capacitybars !<br /> 8 = 7 capacitybars<br /> 7 = 6 capacitybars<br /> 6 = 5 capacitybars<br /> 5 = 4 capacitybars !<br /> 4 = 4 capacitybars !<br /> 3 = 3 capacitybars<br /> 2 = 2 capacitybars<br /> 1 = 1 capacitybars<br /> 0 = 0 capacitybars,<br /> |-<br /> | <span id="LB_Temperature_Segment_For_Dash">LB_Temperature_Segment_For_Dash</span> || 24 || 8 || 0.4166666 || 0 || % || 0 || 100 || For instrumentation cluster. Unit is %, times 5/12 according to documentation, kinda strange .Should be average of the 3 sensors inside the battery pack.<br /> |-<br /> | <span id="LB_Remain_Cap_Segment_Swit_Flag">LB_Remain_Cap_Segment_Swit_Flag</span> || 32 || 1 || 1 || 0 || status || 0 || 1 || <br /> |-<br /> | <span id="Mux_5BC">Mux_5BC</span> || 32 || 4 || 1 || 0 || – || – || – || Multiplexor<br /> |-<br /> | <span id="LB_Capacity_Deterioration_Rate">LB_Capacity_Deterioration_Rate</span> || 33 || 7 || 1 || 0 || % || 0 || 100 || SOH (State-of-Health) Effects the charge gauge, lower numbers mean more chargebars<br /> |-<br /> | <span id="LB_MaxGIDS">LB_MaxGIDS</span> || 44 || 1 || 1 || 0 || – || – || – || Only 30kWh AZE0 has this. When this value is 1, the GIDS number is at its maximum.(LB_Remain_Capacity_GIDS)<br /> |-<br /> | <span id="LB_Output_Power_Limit_Reason">LB_Output_Power_Limit_Reason</span> || 45 || 3 || 1 || 0 || modemask || 0 || 7 || Indicates why power is limited<br /> |-<br /> | <span id="LB_Remain_Charge_Time_Condition">LB_Remain_Charge_Time_Condition</span> || 41 || 5 || 1 || 0 || modemask || 0 || 30 || Mux for LB_Remain_charge_time<br /> <br /> 00000b = Quick charge 01001b = Normal Charge 200V SOC100% 01010b = Normal Charge 200V SOC80% 10001b = Normal Charge 100V SOC100% 10010b = Normal Charge 100V SOC80% 11111b = Invalid value<br /> |-<br /> | <span id="LB_Remain_Charge_Time">LB_Remain_Charge_Time</span> || 52 || 13 || 1 || 0 || minutes || 0 || 8190 || 1FFFh is used as "Unavailable value"<br /> |}<br /> [[Category:Nissan_Leaf_BMS]]</div>

Powercontrol https://openinverter.org/wiki/index.php?title=CANID_0x5BC&diff=5736 CANID 0x5BC 2025-05-07T09:06:25Z

<p>Powercontrol: Created page with " * '''CAN ID''': 0x5BC * '''Name''': x5BC * '''Data length (DLC)''': 8 * '''Transmitter''': HVBAT == Byte-Level Representation [ 0 --> 7] == {| class="wikitable" style="text-align:left; width: 100%; table-layout: fixed;" |+ Byte-Level Layout ! Byte 0 !! Byte 1 !! Byte 2 !! Byte 3 !! Byte 4 !! Byte 5 !! Byte 6 !! Byte 7 |- | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-0" | LB_Remain_Capacity_GIDS | style="width:..."</p> <hr /> <div><br /> * '''CAN ID''': 0x5BC<br /> * '''Name''': x5BC<br /> * '''Data length (DLC)''': 8<br /> * '''Transmitter''': HVBAT<br /> <br /> == Byte-Level Representation [ 0 --> 7] ==<br /> {| class="wikitable" style="text-align:left; width: 100%; table-layout: fixed;"<br /> |+ Byte-Level Layout<br /> ! Byte 0 !! Byte 1 !! Byte 2 !! Byte 3 !! Byte 4 !! Byte 5 !! Byte 6 !! Byte 7<br /> |-<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-0" | [[#LB_Remain_Capacity_GIDS|LB_Remain_Capacity_GIDS]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-1" | [[#LB_Remain_Capacity_GIDS|LB_Remain_Capacity_GIDS]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-2" | [[#CapacityBars|CapacityBars]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-3" | [[#LB_Temperature_Segment_For_Dash|LB_Temperature_Segment_For_Dash]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-4" | [[#LB_Capacity_Deterioration_Rate|LB_Capacity_Deterioration_Rate]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-5" | [[#LB_Remain_Charge_Time_Condition|LB_Remain_Charge_Time_Condition]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-6" | [[#LB_Remain_Charge_Time|LB_Remain_Charge_Time]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-7" | [[#LB_Remain_Charge_Time|LB_Remain_Charge_Time]]<br /> |}<br /> <br /> == Bit-Level Views [7 --> 0] ==<br /> {| class="wikitable" style="text-align:left; width: 100%; table-layout: fixed;"<br /> |+ Bit-Level Layout of Byte 2<br /> ! Bit 7 !! Bit 6 !! Bit 5 !! Bit 4 !! Bit 3 !! Bit 2 !! Bit 1 !! Bit 0<br /> |-<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-2" | [[#CapacityBars|CapacityBars]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-2" | [[#CapacityBars|CapacityBars]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-2" | [[#CapacityBars|CapacityBars]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-2" | [[#CapacityBars|CapacityBars]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-2" | Reserved<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-2" | Reserved<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-2" | Reserved<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-2" | Reserved<br /> |}<br /> <br /> {| class="wikitable" style="text-align:left; width: 100%; table-layout: fixed;"<br /> |+ Bit-Level Layout of Byte 4<br /> ! Bit 7 !! Bit 6 !! Bit 5 !! Bit 4 !! Bit 3 !! Bit 2 !! Bit 1 !! Bit 0<br /> |-<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-4" | [[#LB_Capacity_Deterioration_Rate|LB_Capacity_Deterioration_Rate]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-4" | [[#LB_Capacity_Deterioration_Rate|LB_Capacity_Deterioration_Rate]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-4" | [[#LB_Capacity_Deterioration_Rate|LB_Capacity_Deterioration_Rate]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-4" | [[#LB_Capacity_Deterioration_Rate|LB_Capacity_Deterioration_Rate]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-4" | [[#LB_Capacity_Deterioration_Rate|LB_Capacity_Deterioration_Rate]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-4" | [[#LB_Capacity_Deterioration_Rate|LB_Capacity_Deterioration_Rate]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-4" | [[#LB_Capacity_Deterioration_Rate|LB_Capacity_Deterioration_Rate]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-4" | [[#Mux_5BC|Mux_5BC]]<br /> |}<br /> <br /> {| class="wikitable" style="text-align:left; width: 100%; table-layout: fixed;"<br /> |+ Bit-Level Layout of Byte 5<br /> ! Bit 7 !! Bit 6 !! Bit 5 !! Bit 4 !! Bit 3 !! Bit 2 !! Bit 1 !! Bit 0<br /> |-<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-5" | [[#LB_Output_Power_Limit_Reason|LB_Output_Power_Limit_Reason]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-5" | [[#LB_Output_Power_Limit_Reason|LB_Output_Power_Limit_Reason]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-5" | [[#LB_Remain_Charge_Time_Condition|LB_Remain_Charge_Time_Condition]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-5" | [[#LB_Remain_Charge_Time_Condition|LB_Remain_Charge_Time_Condition]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-5" | [[#LB_Remain_Charge_Time_Condition|LB_Remain_Charge_Time_Condition]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-5" | [[#LB_Remain_Charge_Time_Condition|LB_Remain_Charge_Time_Condition]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-5" | [[#LB_Remain_Charge_Time_Condition|LB_Remain_Charge_Time_Condition]]<br /> | style="width:12.5%; word-wrap:break-word; white-space:normal;" class="byte-5" | Reserved<br /> |}<br /> <br /> == Signal Definitions ==<br /> {| class="wikitable"<br /> |+ Detailed Signal Information<br /> ! Signal Name !! Start Bit !! Length (bits) !! Factor !! Offset !! Unit !! Minimum !! Maximum !! Description<br /> |-<br /> | <span id="LB_Remain_Capacity_GIDS">LB_Remain_Capacity_GIDS</span> || 7 || 10 || 1 || 0 || gids || 0 || 500 || 0-281 for 24kWh, 0-363 for 30kWh, 0-498 for 40kWh, 0-775 for 62kWh<br /> 1 LSB = 80WH<br /> <br /> LB_CAPR (aka 'gids') is an 80Wh resolution capacity indication used by the GOM and combined with LB_FULLCAP on gen1 Leafs to generate the capacity dashes behind the GOM.<br /> |-<br /> | <span id="LB_Remaining_Capacity_Segments">LB_Remaining_Capacity_Segments</span> || 16 || 8 || 1 || 0 || – || 0 || 240 || Contains chargebars and capacitybars, alternating depending on mux. Simplified lower down in the message<br /> |-<br /> | <span id="ChargeBars">ChargeBars</span> || 20 || 4 || 1 || 0 || - || 0 || 15 || Range 0-15 (Below data from test at 0%SOC, writing values to bus)<br /> 15 = 12 chargebars<br /> 14 = 12 chargebars<br /> 13 = 11 chargebars<br /> 12 = 10 chargebars<br /> 11 = 9 chargebars<br /> 10 = 8 chargebars !<br /> 9 = 8 chargebars !<br /> 8 = 7 chargebars<br /> 7 = 6 chargebars<br /> 6 = 5 chargebars<br /> 5 = 4 chargebars !<br /> 4 = 4 chargebars !<br /> 3 = 3 chargebars<br /> 2 = 2 chargebars<br /> 1 = 1 chargebars<br /> 0 = 0 chargebars<br /> |-<br /> | <span id="CapacityBars">CapacityBars</span> || 20 || 4 || 1 || 0 || - || 0 || 15 || Range 0-15 Below test data by writing to bus and seeing what happens<br /> 15 = 12 capacitybars<br /> 14 = 12 capacitybars<br /> 13 = 11 capacitybars<br /> 12 = 10 capacitybars<br /> 11 = 9 capacitybars<br /> 10 = 8 capacitybars !<br /> 9 = 8 capacitybars !<br /> 8 = 7 capacitybars<br /> 7 = 6 capacitybars<br /> 6 = 5 capacitybars<br /> 5 = 4 capacitybars !<br /> 4 = 4 capacitybars !<br /> 3 = 3 capacitybars<br /> 2 = 2 capacitybars<br /> 1 = 1 capacitybars<br /> 0 = 0 capacitybars,<br /> |-<br /> | <span id="LB_Temperature_Segment_For_Dash">LB_Temperature_Segment_For_Dash</span> || 24 || 8 || 0.4166666 || 0 || % || 0 || 100 || For instrumentation cluster. Unit is %, times 5/12 according to documentation, kinda strange .Should be average of the 3 sensors inside the battery pack.<br /> |-<br /> | <span id="LB_Remain_Cap_Segment_Swit_Flag">LB_Remain_Cap_Segment_Swit_Flag</span> || 32 || 1 || 1 || 0 || status || 0 || 1 || <br /> |-<br /> | <span id="Mux_5BC">Mux_5BC</span> || 32 || 4 || 1 || 0 || – || – || – || Multiplexor<br /> |-<br /> | <span id="LB_Capacity_Deterioration_Rate">LB_Capacity_Deterioration_Rate</span> || 33 || 7 || 1 || 0 || % || 0 || 100 || SOH (State-of-Health) Effects the charge gauge, lower numbers mean more chargebars<br /> |-<br /> | <span id="LB_MaxGIDS">LB_MaxGIDS</span> || 44 || 1 || 1 || 0 || – || – || – || Only 30kWh AZE0 has this. When this value is 1, the GIDS number is at its maximum.(LB_Remain_Capacity_GIDS)<br /> |-<br /> | <span id="LB_Output_Power_Limit_Reason">LB_Output_Power_Limit_Reason</span> || 45 || 3 || 1 || 0 || modemask || 0 || 7 || Indicates why power is limited<br /> |-<br /> | <span id="LB_Remain_Charge_Time_Condition">LB_Remain_Charge_Time_Condition</span> || 41 || 5 || 1 || 0 || modemask || 0 || 30 || Mux for LB_Remain_charge_time<br /> <br /> 00000b = Quick charge 01001b = Normal Charge 200V SOC100% 01010b = Normal Charge 200V SOC80% 10001b = Normal Charge 100V SOC100% 10010b = Normal Charge 100V SOC80% 11111b = Invalid value<br /> |-<br /> | <span id="LB_Remain_Charge_Time">LB_Remain_Charge_Time</span> || 52 || 13 || 1 || 0 || minutes || 0 || 8190 || 1FFFh is used as "Unavailable value"<br /> |}</div>

Powercontrol