https://en.canopen-lift.org/api.php?action=feedcontributions&user=Jan.Merkelbag&feedformat=atomCANopen-Lift - User contributions [en]2024-03-28T23:17:44ZUser contributionsMediaWiki 1.41.0https://en.canopen-lift.org/index.php?title=Interlift_2013&diff=3436Interlift 20132013-09-05T12:40:45Z<p>Jan.Merkelbag: </p>
<hr />
<div>[[de:Interlift_2013]]<br />
[[File:Logo-CANopen-Lift.png|right|200px|Logo CANopen-Lift]]<br />
In the period from 15th to 18th October 2013 the world's largest trade fair for elevator technology '''Interlift 2013''' will take place in Augsburg. <br />
<br />
The CiA will be present there once again. They will supply an information stand on CANopen-Lift and the CANopen-Lift Demonstrator to demonstrate the functionality of CANopen in lifts. <br />
<br />
Many new and familiar CANopen products will also be on display at the booths of many manufacturers. <br />
<br />
<br />
== Exhibitors of CANopen Lift products at Interlift 2013==<br />
<br />
In the following table we give an overview on the booths available at which CANopen Lift products will be exhibited.<br />
<br />
'''Caution'''<br />
<br />
The current list is temporary only because it is neither complete and nor confirmed yet!<br />
<br />
<br />
{| class="wikitable sortable" style="background-color:#F3F3FF; border-style: solid; border-width: 1px;"<br />
|+'''Overview table of exhibitors'''<br />
! Hall !! Booth-No. !! Company !! Product group !! class="unsortable" | W !! class="unsortable" | Comment<br />
|-<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1101<br />
| Kollmorgen Steuerungstechnik GmbH<br />
| [[Controller]]<br />
| A, M<br />
| <br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2222<br />
| [[Baumer IVO GmbH & Co. KG]]<br />
| [[Absolut-Drehgeber GXP5W|Position Encoder]]<br />
| A, P, D, M<br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3217<br />
| MICELECT<br />
| Load Measurement <br />
| A, P, M<br />
| <br />
|-<br />
| style="text-align:center" | 7<br />
| style="text-align:center" | 7102<br />
| [[Böhnke & Partner GmbH |Böhnke + Partner GmbH]]<br />
| [[Steuerung bp306|Controller]], [[CAN-DFÜ-Gateway CDG-01|Gateways]], [[CANwizard|Tools]]<br />
| A, P, D, M, I<br />
| <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5196<br />
| [[Sprinte]]<br />
| [[Steuerung ASP116 Evolution|Controller]]<br />
| A, P, D, M <br />
| <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5167<br />
| Klinkhammer<br />
| Controller<br />
| A, P, M <br />
| <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5167<br />
| Intec<br />
| Controller<br />
| A, P, M <br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3236<br />
| [[Bs tableau oHG|bs tableau oHG]]<br />
| Displays<br />
| A, P <br />
| <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5145<br />
| [[CAN in Automation]]<br />
| Standardization<br />
| A, D, M, I<br />
| You can see the [[CANopen-Lift Messemodell|Demonstrator]] at the CiA's booth. <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5126<br />
| [[Control Techniques GmbH]]<br />
| [[Drive frequency converter Unidrive SP 0,75 - 1900kW|Frequency converter]]<br />
| A, P, D, M<br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3184<br />
| [[DMG SPA]]<br />
| [[Tableaus]]<br />
| A, M<br />
|<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3170<br />
| [[ELGO Electronic GmbH]]<br />
| [[LIMAX2 Schachtinformationssystem|Position Encoder]]<br />
| A, P, D, M<br />
| <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5216<br />
| [[Gefran SpA Drive & Motion Control Unit]]<br />
| [[Drive frequency converter]]<br />
| A, M<br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3100<br />
| [[Hans & Jos. Kronenberg GmbH]]<br />
| [[CAN-Bus-Knoten cbk01|Tableaus]]<br />
| A, P, D, M<br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3101<br />
| [[Henning GmbH|Henning GmbH]]<br />
| Load Measurement<br />
| A, P, D, M<br />
| <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5252<br />
| [[Janzhoff Aufzüge GmbH]]<br />
| Lift<br />
| A, P, M<br />
| Complete lift with CANopen Drive, Position Unit, Door Drive Unit, Car Panel, Floor Panels, Load measurement unit, Car electronic <br />
|-<br />
| style="text-align:center" | 7<br />
| style="text-align:center" | 7100<br />
| [[K.A. Schmersal GmbH|K.A. Schmersal GmbH]]<br />
| [[USP-30-CANopen|Position Encoder]]<br />
| A, P, D, M<br />
| <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5086<br />
| [[Leitronic AG]]<br />
| [[Emergency call device]]<br />
| A, M<br />
| <br />
|-<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1131<br />
| LiftEquip<br />
| Frequency converter<br />
| A, P, D, M<br />
| <br />
|- <br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3105<br />
| [[Lika Electronic Srl]]<br />
| Position Encoder<br />
| A, P, M<br />
| <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5246<br />
| [[MEILLER Lifttüren GmbH]]<br />
| [[Automatic lift doors]]<br />
| A, P<br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3106<br />
| [[SafeLine Sweden]]<br />
| [[Digital display]], [[Floor display]], Emergency call device<br />
| A, P, D, M<br />
|<br />
|-<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1123<br />
| [[SCHAEFER GmbH]]<br />
| [[Tableauknoten CANnode CN16|Tableaus]]<br />
| A, P, D, M<br />
| <br />
|-<br />
| style="text-align:center" | 7<br />
| style="text-align:center" | 7103<br />
| [[Siemens Electronic Design and Manufacturing Services GmbH & Co. KG|Siemens EDMS]]<br />
| Door controller<br />
| A, P, M<br />
| <br />
|-<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1141<br />
| [[SODIMAS S.A.]]<br />
| Lift, [[Controller]]<br />
| A, M<br />
|<br />
|-<br />
| style="text-align:center" | 7<br />
| style="text-align:center" | 7116<br />
| [[STEP Sigriner Elektronik GmbH]] <br />
| [[Controller]], [[Tableaus]], [[TFT displays]]<br />
| A, M<br />
| <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5205<br />
| [[Strack Lift Automation GmbH]]<br />
| [[Controller]]<br />
| A, M<br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3245<br />
| [[S. & A.S. Ltd]]<br />
| [[Controller]], [[Digital display]]<br />
| A, M<br />
|<br />
|-<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1136<br />
| [[Wachendorff Automation GmbH & Co. KG]]<br />
| [[Digitale Schachtkopierung Silent Move|Position Encoder]]<br />
| A, P, M<br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3121<br />
| [[Wago Kontakttechnik GmbH & Co. KG]]<br />
| Electronic parts<br />
| A, M<br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3210<br />
| [[Weber Lifttechnik GmbH]]<br />
| [[Controller WECAN]]<br />
| A, P, D, M<br />
| <br />
|-<br />
| style="text-align:center" | 7<br />
| style="text-align:center" | 7136<br />
| [[WITTUR GmbH]]<br />
| Door controller<br />
| A, P, D, M<br />
|<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5254<br />
| [[Yaskawa Europe GmbH Drives + Motion]]<br />
| [[Drive frequency converter]]<br />
| A, M<br />
|<br />
|-<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1120<br />
| [[Ziehl-Abegg AG]]<br />
| [[Drive frequency converter ZETADYN 3BF|Frequency converter]]<br />
| A, P, D, M<br />
| <br />
|-<br />
| style="text-align:center" | 7<br />
| style="text-align:center" | 7217<br />
| Micelect SL <br />
| <br />
| M<br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3106<br />
| [[Masora AG]] <br />
| <br />
| M, A, D, P<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5146<br />
| Pepperl+Fuchs <br />
| <br />
| M, D, P<br />
| <br />
|}<br />
<br />
<br />
* A: Exhibitors with their own stands at the Interlift<br />
* P: A CANopen product is either being produced, developed or sold<br />
* D: A product is shown at the demonstrator<br />
* M: Member of CAN in Automation<br />
* I: Here you receive information about CANopen-Lift<br />
<br />
== CANopen lift products on the Interlift ==<br />
<br />
We will provide an overview of the booths with CANopen products for you here. <br />
<br />
<gallery><br />
Datei:Lageplan2013_CANopen_Halle1.png|Hall 1<br />
Datei:Lageplan2013_CANopen_Halle3.png|Hall 3<br />
Datei:Lageplan2013_CANopen_Halle5.png|Hall 5<br />
Datei:Lageplan2013_CANopen_Halle7.png|Hall 7<br />
</gallery><br />
<br />
== Download == <br />
* [[media:Interlift2013-Lageplan2013_CANopen_Halle1.pdf|Site plan for Hall 1 as a PDF document]]<br />
* [[media:Interlift2013-Lageplan2013_CANopen_Halle3.pdf|Site plan for Hall 3 as a PDF document]]<br />
* [[media:Interlift2013-Lageplan2013_CANopen_Halle5.pdf|Site plan for Hall 5 as a PDF document]]<br />
* [[media:Interlift2013-Lageplan2013_CANopen_Halle7.pdf|Site plan for Hall 7 as a PDF document]]<br />
<br />
== Reiew of the last trade fairs == <br />
* [[Interlift 2011]]<br />
* [[Interlift 2009]]<br />
* [[Messeinfos von der Interlift 2007|Interlift 2007]]<br />
<br />
[[Category:SMG Lift]]</div>Jan.Merkelbaghttps://en.canopen-lift.org/index.php?title=Interlift_2013&diff=3435Interlift 20132013-09-05T12:39:17Z<p>Jan.Merkelbag: </p>
<hr />
<div>[[Interlift_2013]]<br />
[[File:Logo-CANopen-Lift.png|right|200px|Logo CANopen-Lift]]<br />
In the period from 15th to 18th October 2013 the world's largest trade fair for elevator technology '''Interlift 2013''' will take place in Augsburg. <br />
<br />
The CiA will be present there once again. They will supply an information stand on CANopen-Lift and the CANopen-Lift Demonstrator to demonstrate the functionality of CANopen in lifts. <br />
<br />
Many new and familiar CANopen products will also be on display at the booths of many manufacturers. <br />
<br />
<br />
== Exhibitors of CANopen Lift products at Interlift 2013==<br />
<br />
In the following table we give an overview on the booths available at which CANopen Lift products will be exhibited.<br />
<br />
'''Caution'''<br />
<br />
The current list is temporary only because it is neither complete and nor confirmed yet!<br />
<br />
<br />
{| class="wikitable sortable" style="background-color:#F3F3FF; border-style: solid; border-width: 1px;"<br />
|+'''Overview table of exhibitors'''<br />
! Hall !! Booth-No. !! Company !! Product group !! class="unsortable" | W !! class="unsortable" | Comment<br />
|-<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1101<br />
| Kollmorgen Steuerungstechnik GmbH<br />
| [[Controller]]<br />
| A, M<br />
| <br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2222<br />
| [[Baumer IVO GmbH & Co. KG]]<br />
| [[Absolut-Drehgeber GXP5W|Position Encoder]]<br />
| A, P, D, M<br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3217<br />
| MICELECT<br />
| Load Measurement <br />
| A, P, M<br />
| <br />
|-<br />
| style="text-align:center" | 7<br />
| style="text-align:center" | 7102<br />
| [[Böhnke & Partner GmbH |Böhnke + Partner GmbH]]<br />
| [[Steuerung bp306|Controller]], [[CAN-DFÜ-Gateway CDG-01|Gateways]], [[CANwizard|Tools]]<br />
| A, P, D, M, I<br />
| <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5196<br />
| [[Sprinte]]<br />
| [[Steuerung ASP116 Evolution|Controller]]<br />
| A, P, D, M <br />
| <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5167<br />
| Klinkhammer<br />
| Controller<br />
| A, P, M <br />
| <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5167<br />
| Intec<br />
| Controller<br />
| A, P, M <br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3236<br />
| [[Bs tableau oHG|bs tableau oHG]]<br />
| Displays<br />
| A, P <br />
| <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5145<br />
| [[CAN in Automation]]<br />
| Standardization<br />
| A, D, M, I<br />
| You can see the [[CANopen-Lift Messemodell|Demonstrator]] at the CiA's booth. <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5126<br />
| [[Control Techniques GmbH]]<br />
| [[Drive frequency converter Unidrive SP 0,75 - 1900kW|Frequency converter]]<br />
| A, P, D, M<br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3184<br />
| [[DMG SPA]]<br />
| [[Tableaus]]<br />
| A, M<br />
|<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3170<br />
| [[ELGO Electronic GmbH]]<br />
| [[LIMAX2 Schachtinformationssystem|Position Encoder]]<br />
| A, P, D, M<br />
| <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5216<br />
| [[Gefran SpA Drive & Motion Control Unit]]<br />
| [[Drive frequency converter]]<br />
| A, M<br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3100<br />
| [[Hans & Jos. Kronenberg GmbH]]<br />
| [[CAN-Bus-Knoten cbk01|Tableaus]]<br />
| A, P, D, M<br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3101<br />
| [[Henning GmbH|Henning GmbH]]<br />
| Load Measurement<br />
| A, P, D, M<br />
| <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5252<br />
| [[Janzhoff Aufzüge GmbH]]<br />
| Lift<br />
| A, P, M<br />
| Complete lift with CANopen Drive, Position Unit, Door Drive Unit, Car Panel, Floor Panels, Load measurement unit, Car electronic <br />
|-<br />
| style="text-align:center" | 7<br />
| style="text-align:center" | 7100<br />
| [[K.A. Schmersal GmbH|K.A. Schmersal GmbH]]<br />
| [[USP-30-CANopen|Position Encoder]]<br />
| A, P, D, M<br />
| <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5086<br />
| [[Leitronic AG]]<br />
| [[Emergency call device]]<br />
| A, M<br />
| <br />
|-<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1131<br />
| LiftEquip<br />
| Frequency converter<br />
| A, P, D, M<br />
| <br />
|- <br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3105<br />
| [[Lika Electronic Srl]]<br />
| Position Encoder<br />
| A, P, M<br />
| <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5246<br />
| [[MEILLER Lifttüren GmbH]]<br />
| [[Automatic lift doors]]<br />
| A, P<br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3106<br />
| [[SafeLine Sweden]]<br />
| [[Digital display]], [[Floor display]], Emergency call device<br />
| A, P, D, M<br />
|<br />
|-<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1123<br />
| [[SCHAEFER GmbH]]<br />
| [[Tableauknoten CANnode CN16|Tableaus]]<br />
| A, P, D, M<br />
| <br />
|-<br />
| style="text-align:center" | 7<br />
| style="text-align:center" | 7103<br />
| [[Siemens Electronic Design and Manufacturing Services GmbH & Co. KG|Siemens EDMS]]<br />
| Door controller<br />
| A, P, M<br />
| <br />
|-<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1141<br />
| [[SODIMAS S.A.]]<br />
| Lift, [[Controller]]<br />
| A, M<br />
|<br />
|-<br />
| style="text-align:center" | 7<br />
| style="text-align:center" | 7116<br />
| [[STEP Sigriner Elektronik GmbH]] <br />
| [[Controller]], [[Tableaus]], [[TFT displays]]<br />
| A, M<br />
| <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5205<br />
| [[Strack Lift Automation GmbH]]<br />
| [[Controller]]<br />
| A, M<br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3245<br />
| [[S. & A.S. Ltd]]<br />
| [[Controller]], [[Digital display]]<br />
| A, M<br />
|<br />
|-<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1136<br />
| [[Wachendorff Automation GmbH & Co. KG]]<br />
| [[Digitale Schachtkopierung Silent Move|Position Encoder]]<br />
| A, P, M<br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3121<br />
| [[Wago Kontakttechnik GmbH & Co. KG]]<br />
| Electronic parts<br />
| A, M<br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3210<br />
| [[Weber Lifttechnik GmbH]]<br />
| [[Controller WECAN]]<br />
| A, P, D, M<br />
| <br />
|-<br />
| style="text-align:center" | 7<br />
| style="text-align:center" | 7136<br />
| [[WITTUR GmbH]]<br />
| Door controller<br />
| A, P, D, M<br />
|<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5254<br />
| [[Yaskawa Europe GmbH Drives + Motion]]<br />
| [[Drive frequency converter]]<br />
| A, M<br />
|<br />
|-<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1120<br />
| [[Ziehl-Abegg AG]]<br />
| [[Drive frequency converter ZETADYN 3BF|Frequency converter]]<br />
| A, P, D, M<br />
| <br />
|-<br />
| style="text-align:center" | 7<br />
| style="text-align:center" | 7217<br />
| Micelect SL <br />
| <br />
| M<br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3106<br />
| [[Masora AG]] <br />
| <br />
| M, A, D, P<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5146<br />
| Pepperl+Fuchs <br />
| <br />
| M, D, P<br />
| <br />
|}<br />
<br />
<br />
* A: Exhibitors with their own stands at the Interlift<br />
* P: A CANopen product is either being produced, developed or sold<br />
* D: A product is shown at the demonstrator<br />
* M: Member of CAN in Automation<br />
* I: Here you receive information about CANopen-Lift<br />
<br />
== CANopen lift products on the Interlift ==<br />
<br />
We will provide an overview of the booths with CANopen products for you here. <br />
<br />
<gallery><br />
Datei:Lageplan2013_CANopen_Halle1.png|Hall 1<br />
Datei:Lageplan2013_CANopen_Halle3.png|Hall 3<br />
Datei:Lageplan2013_CANopen_Halle5.png|Hall 5<br />
Datei:Lageplan2013_CANopen_Halle7.png|Hall 7<br />
</gallery><br />
<br />
== Download == <br />
* [[media:Interlift2013-Lageplan2013_CANopen_Halle1.pdf|Site plan for Hall 1 as a PDF document]]<br />
* [[media:Interlift2013-Lageplan2013_CANopen_Halle3.pdf|Site plan for Hall 3 as a PDF document]]<br />
* [[media:Interlift2013-Lageplan2013_CANopen_Halle5.pdf|Site plan for Hall 5 as a PDF document]]<br />
* [[media:Interlift2013-Lageplan2013_CANopen_Halle7.pdf|Site plan for Hall 7 as a PDF document]]<br />
<br />
== Reiew of the last trade fairs == <br />
* [[Interlift 2011]]<br />
* [[Interlift 2009]]<br />
* [[Messeinfos von der Interlift 2007|Interlift 2007]]<br />
<br />
[[Category:SMG Lift]]</div>Jan.Merkelbaghttps://en.canopen-lift.org/index.php?title=Interlift_2013&diff=3434Interlift 20132013-09-05T12:36:26Z<p>Jan.Merkelbag: </p>
<hr />
<div>[[Interlift_2013]]<br />
[[File:Logo-CANopen-Lift.png|right|200px|Logo CANopen-Lift]]<br />
In the period from 15th to 18th October 2013 the world's largest trade fair for elevator technology '''Interlift 2013''' will take place in Augsburg. <br />
<br />
The CiA will be present there once again. They will supply an information stand on CANopen-Lift and the CANopen-Lift Demonstrator to demonstrate the functionality of CANopen in lifts. <br />
<br />
Many new and familiar CANopen products will also be on display at the booths of many manufacturers. <br />
<br />
<br />
== Exhibitors of CANopen Lift products at Interlift 2013==<br />
<br />
In the following table we give an overview on the booths available at which CANopen Lift products will be exhibited.<br />
<br />
'''Caution'''<br />
<br />
The current list is temporary only because it is neither complete and nor confirmed yet!<br />
<br />
<br />
{| class="wikitable sortable" style="background-color:#F3F3FF; border-style: solid; border-width: 1px;"<br />
|+'''Tabelle Ausstellerübersicht'''<br />
! Halle !! Stand-Nr. !! Firma !! Produktgruppe !! class="unsortable" | W !! class="unsortable" | Bemerkung<br />
|-<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1101<br />
| Kollmorgen Steuerungstechnik GmbH<br />
| [[Controller]]<br />
| A, M<br />
| <br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2222<br />
| [[Baumer IVO GmbH & Co. KG]]<br />
| [[Absolut-Drehgeber GXP5W|Position Encoder]]<br />
| A, P, D, M<br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3217<br />
| MICELECT<br />
| Load Measurement <br />
| A, P, M<br />
| <br />
|-<br />
| style="text-align:center" | 7<br />
| style="text-align:center" | 7102<br />
| [[Böhnke & Partner GmbH |Böhnke + Partner GmbH]]<br />
| [[Steuerung bp306|Controller]], [[CAN-DFÜ-Gateway CDG-01|Gateways]], [[CANwizard|Tools]]<br />
| A, P, D, M, I<br />
| <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5196<br />
| [[Sprinte]]<br />
| [[Steuerung ASP116 Evolution|Controller]]<br />
| A, P, D, M <br />
| <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5167<br />
| Klinkhammer<br />
| Controller<br />
| A, P, M <br />
| <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5167<br />
| Intec<br />
| Controller<br />
| A, P, M <br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3236<br />
| [[Bs tableau oHG|bs tableau oHG]]<br />
| Displays<br />
| A, P <br />
| <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5145<br />
| [[CAN in Automation]]<br />
| Standardization<br />
| A, D, M, I<br />
| You can see the [[CANopen-Lift Messemodell|Demonstrator]] at the CiA's booth. <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5126<br />
| [[Control Techniques GmbH]]<br />
| [[Drive frequency converter Unidrive SP 0,75 - 1900kW|Frequency converter]]<br />
| A, P, D, M<br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3184<br />
| [[DMG SPA]]<br />
| [[Tableaus]]<br />
| A, M<br />
|<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3170<br />
| [[ELGO Electronic GmbH]]<br />
| [[LIMAX2 Schachtinformationssystem|Position Encoder]]<br />
| A, P, D, M<br />
| <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5216<br />
| [[Gefran SpA Drive & Motion Control Unit]]<br />
| [[Drive frequency converter]]<br />
| A, M<br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3100<br />
| [[Hans & Jos. Kronenberg GmbH]]<br />
| [[CAN-Bus-Knoten cbk01|Tableaus]]<br />
| A, P, D, M<br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3101<br />
| [[Henning GmbH|Henning GmbH]]<br />
| Load Measurement<br />
| A, P, D, M<br />
| <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5252<br />
| [[Janzhoff Aufzüge GmbH]]<br />
| Lift<br />
| A, P, M<br />
| Complete lift with CANopen Drive, Position Unit, Door Drive Unit, Car Panel, Floor Panels, Load measurement unit, Car electronic <br />
|-<br />
| style="text-align:center" | 7<br />
| style="text-align:center" | 7100<br />
| [[K.A. Schmersal GmbH|K.A. Schmersal GmbH]]<br />
| [[USP-30-CANopen|Position Encoder]]<br />
| A, P, D, M<br />
| <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5086<br />
| [[Leitronic AG]]<br />
| [[Emergency call device]]<br />
| A, M<br />
| <br />
|-<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1131<br />
| LiftEquip<br />
| Frequency converter<br />
| A, P, D, M<br />
| <br />
|- <br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3105<br />
| [[Lika Electronic Srl]]<br />
| Position Encoder<br />
| A, P, M<br />
| <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5246<br />
| [[MEILLER Lifttüren GmbH]]<br />
| [[Automatic lift doors]]<br />
| A, P<br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3106<br />
| [[SafeLine Sweden]]<br />
| [[Digital display]], [[Floor display]], Emergency call device<br />
| A, P, D, M<br />
|<br />
|-<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1123<br />
| [[SCHAEFER GmbH]]<br />
| [[Tableauknoten CANnode CN16|Tableaus]]<br />
| A, P, D, M<br />
| <br />
|-<br />
| style="text-align:center" | 7<br />
| style="text-align:center" | 7103<br />
| [[Siemens Electronic Design and Manufacturing Services GmbH & Co. KG|Siemens EDMS]]<br />
| Door controller<br />
| A, P, M<br />
| <br />
|-<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1141<br />
| [[SODIMAS S.A.]]<br />
| Lift, [[Controller]]<br />
| A, M<br />
|<br />
|-<br />
| style="text-align:center" | 7<br />
| style="text-align:center" | 7116<br />
| [[STEP Sigriner Elektronik GmbH]] <br />
| [[Controller]], [[Tableaus]], [[TFT displays]]<br />
| A, M<br />
| <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5205<br />
| [[Strack Lift Automation GmbH]]<br />
| [[Controller]]<br />
| A, M<br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3245<br />
| [[S. & A.S. Ltd]]<br />
| [[Controller]], [[Digital display]]<br />
| A, M<br />
|<br />
|-<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1136<br />
| [[Wachendorff Automation GmbH & Co. KG]]<br />
| [[Digitale Schachtkopierung Silent Move|Position Encoder]]<br />
| A, P, M<br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3121<br />
| [[Wago Kontakttechnik GmbH & Co. KG]]<br />
| Electronic parts<br />
| A, M<br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3210<br />
| [[Weber Lifttechnik GmbH]]<br />
| [[Controller WECAN]]<br />
| A, P, D, M<br />
| <br />
|-<br />
| style="text-align:center" | 7<br />
| style="text-align:center" | 7136<br />
| [[WITTUR GmbH]]<br />
| Door controller<br />
| A, P, D, M<br />
|<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5254<br />
| [[Yaskawa Europe GmbH Drives + Motion]]<br />
| [[Drive frequency converter]]<br />
| A, M<br />
|<br />
|-<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1120<br />
| [[Ziehl-Abegg AG]]<br />
| [[Drive frequency converter ZETADYN 3BF|Frequency converter]]<br />
| A, P, D, M<br />
| <br />
|-<br />
| style="text-align:center" | 7<br />
| style="text-align:center" | 7217<br />
| Micelect SL <br />
| <br />
| M<br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3106<br />
| [[Masora AG]] <br />
| <br />
| M, A, D, P<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5146<br />
| Pepperl+Fuchs <br />
| <br />
| M, D, P<br />
| <br />
|}<br />
<br />
<br />
* A: Exhibitors with their own stands at the Interlift<br />
* P: A CANopen product is either being produced, developed or sold<br />
* D: A product is shown at the demonstrator<br />
* M: Member of CAN in Automation<br />
* I: Here you receive information about CANopen-Lift<br />
<br />
== CANopen lift products on the Interlift ==<br />
<br />
We will provide an overview of the booths with CANopen products for you here. <br />
<br />
<gallery><br />
Datei:Lageplan2013_CANopen_Halle1.png|Hall 1<br />
Datei:Lageplan2013_CANopen_Halle3.png|Hall 3<br />
Datei:Lageplan2013_CANopen_Halle5.png|Hall 5<br />
Datei:Lageplan2013_CANopen_Halle7.png|Hall 7<br />
</gallery><br />
<br />
== Download == <br />
* [[media:Interlift2013-Lageplan2013_CANopen_Halle1.pdf|Site plan for Hall 1 as a PDF document]]<br />
* [[media:Interlift2013-Lageplan2013_CANopen_Halle3.pdf|Site plan for Hall 3 as a PDF document]]<br />
* [[media:Interlift2013-Lageplan2013_CANopen_Halle5.pdf|Site plan for Hall 5 as a PDF document]]<br />
* [[media:Interlift2013-Lageplan2013_CANopen_Halle7.pdf|Site plan for Hall 7 as a PDF document]]<br />
<br />
== Reiew of the last trade fairs == <br />
* [[Interlift 2011]]<br />
* [[Interlift 2009]]<br />
* [[Messeinfos von der Interlift 2007|Interlift 2007]]<br />
<br />
[[Category:SMG Lift]]</div>Jan.Merkelbaghttps://en.canopen-lift.org/index.php?title=Interlift_2013&diff=3433Interlift 20132013-09-05T12:21:33Z<p>Jan.Merkelbag: </p>
<hr />
<div>[[Interlift_2013]]<br />
[[File:Logo-CANopen-Lift.png|right|200px|Logo CANopen-Lift]]<br />
In the period from 15th to 18th October 2013 the world's largest trade fair for elevator technology '''Interlift 2013''' will take place in Augsburg. <br />
<br />
The CiA will be present there once again. They will supply an information stand on CANopen-Lift and the CANopen-Lift Demonstrator to demonstrate the functionality of CANopen in lifts. <br />
<br />
Many new and familiar CANopen products will also be on display at the booths of many manufacturers. <br />
<br />
<br />
== Exhibitors of CANopen Lift products at Interlift 2013==<br />
<br />
In the following table we give an overview on the booths available at which CANopen Lift products will be exhibited.<br />
<br />
'''Caution'''<br />
<br />
The current list is temporary only because it is neither complete and nor confirmed yet!<br />
<br />
<br />
{| class="wikitable sortable" style="background-color:#F3F3FF; border-style: solid; border-width: 1px;"<br />
|+'''Tabelle Ausstellerübersicht'''<br />
! Halle !! Stand-Nr. !! Firma !! Produktgruppe !! class="unsortable" | W !! class="unsortable" | Bemerkung<br />
|-<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1101<br />
| Kollmorgen Steuerungstechnik GmbH<br />
| [[Steuerungen]]<br />
| A, M<br />
| <br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2222<br />
| [[Baumer IVO GmbH & Co. KG]]<br />
| [[Absolut-Drehgeber GXP5W|Position Encoder]]<br />
| A, P, D, M<br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3217<br />
| MICELECT<br />
| Lastmesssensoren <br />
| A, P, M<br />
| <br />
|-<br />
| style="text-align:center" | 7<br />
| style="text-align:center" | 7102<br />
| [[Böhnke & Partner GmbH |Böhnke + Partner GmbH]]<br />
| [[Steuerung bp306|Steuerungen]], [[CAN-DFÜ-Gateway CDG-01|Gateways]], [[CANwizard|Tools]]<br />
| A, P, D, M, I<br />
| <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5196<br />
| [[Sprinte]]<br />
| [[Steuerung ASP116 Evolution|Steuerungen]]<br />
| A, P, D, M <br />
| <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5167<br />
| Klinkhammer<br />
| Steuerungen<br />
| A, P, M <br />
| <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5167<br />
| Intec<br />
| Steuerungen<br />
| A, P, M <br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3236<br />
| [[Bs tableau oHG|bs tableau oHG]]<br />
| Displays<br />
| A, P <br />
| <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5145<br />
| [[CAN in Automation]]<br />
| Normung<br />
| A, D, M, I<br />
| Auf dem Stand der CiA ist wieder der [[CANopen-Lift Messemodell|Demonstrator]] zu sehen.<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5126<br />
| [[Control Techniques GmbH]]<br />
| [[Frequenzumrichter Unidrive SP 0,75 - 1900kW|Umrichter]]<br />
| A, P, D, M<br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3184<br />
| [[DMG SPA]]<br />
| [[Tableaus]]<br />
| A, M<br />
|<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3170<br />
| [[ELGO Electronic GmbH]]<br />
| [[LIMAX2 Schachtinformationssystem|Position Encoder]]<br />
| A, P, D, M<br />
| <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5216<br />
| [[Gefran SpA Drive & Motion Control Unit]]<br />
| [[Frequenzumrichter]]<br />
| A, M<br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3100<br />
| [[Hans & Jos. Kronenberg GmbH]]<br />
| [[CAN-Bus-Knoten cbk01|Tableaus]]<br />
| A, P, D, M<br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3101<br />
| [[Henning GmbH|Henning GmbH]]<br />
| Lastmesssensor<br />
| A, P, D, M<br />
| <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5252<br />
| [[Janzhoff Aufzüge GmbH]]<br />
| Aufzug<br />
| A, P, M<br />
| Vollständiger Aufzug mit CANopen Drive, Position Unit, Door Drive Unit, Car Panel, Floor Panels, Load measurement unit, Car electronic <br />
|-<br />
| style="text-align:center" | 7<br />
| style="text-align:center" | 7100<br />
| [[K.A. Schmersal GmbH|K.A. Schmersal GmbH]]<br />
| [[USP-30-CANopen|Position Encoder]]<br />
| A, P, D, M<br />
| <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5086<br />
| [[Leitronic AG]]<br />
| [[Notrufeinrichtung]]<br />
| A, M<br />
| <br />
|-<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1131<br />
| LiftEquip<br />
| Umrichter<br />
| A, P, D, M<br />
| <br />
|- <br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3105<br />
| [[Lika Electronic Srl]]<br />
| Position Encoder<br />
| A, P, M<br />
| <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5246<br />
| [[MEILLER Aufzugtüren GmbH]]<br />
| [[Automatische Aufzugstüren]]<br />
| A, P<br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3106<br />
| [[SafeLine Sweden]]<br />
| [[Digitalanzeigen]], [[Etagen/Stockwerkanzeige]], Notrufgeräte<br />
| A, P, D, M<br />
|<br />
|-<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1123<br />
| [[SCHAEFER GmbH]]<br />
| [[Tableauknoten CANnode CN16|Tableaus]]<br />
| A, P, D, M<br />
| <br />
|-<br />
| style="text-align:center" | 7<br />
| style="text-align:center" | 7103<br />
| [[Siemens Electronic Design and Manufacturing Services GmbH & Co. KG|Siemens EDMS]]<br />
| Türsteuergerät<br />
| A, P, M<br />
| <br />
|-<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1141<br />
| [[SODIMAS S.A.]]<br />
| Aufzug, [[Steuerungen]]<br />
| A, M<br />
|<br />
|-<br />
| style="text-align:center" | 7<br />
| style="text-align:center" | 7116<br />
| [[STEP Sigriner Elektronik GmbH]] <br />
| [[Steuerungen]], [[Tableaus]], [[TFT Anzeigen]]<br />
| A, M<br />
| <br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5205<br />
| [[Strack Lift Automation GmbH]]<br />
| [[Steuerungen]]<br />
| A, M<br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3245<br />
| [[S. & A.S. Ltd]]<br />
| [[Steuerungen]], [[Digitalanzeigen]]<br />
| A, M<br />
|<br />
|-<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1136<br />
| [[Wachendorff Automation GmbH & Co. KG]]<br />
| [[Digitale Schachtkopierung Silent Move|Position Encoder]]<br />
| A, P, M<br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3121<br />
| [[Wago Kontakttechnik GmbH & Co. KG]]<br />
| Elektronikbauteile<br />
| A, M<br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3210<br />
| [[Weber Lifttechnik GmbH]]<br />
| [[Steuerung WECAN]]<br />
| A, P, D, M<br />
| <br />
|-<br />
| style="text-align:center" | 7<br />
| style="text-align:center" | 7136<br />
| [[WITTUR GmbH]]<br />
| Türsteuergerät<br />
| A, P, D, M<br />
|<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5254<br />
| [[Yaskawa Europe GmbH Drives + Motion]]<br />
| [[Frequenzumrichter]]<br />
| A, M<br />
|<br />
|-<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1120<br />
| [[Ziehl-Abegg AG]]<br />
| [[Frequenzumrichter ZETADYN 3BF|Umrichter]]<br />
| A, P, D, M<br />
| <br />
|-<br />
| style="text-align:center" | 7<br />
| style="text-align:center" | 7217<br />
| Micelect SL <br />
| <br />
| M<br />
| <br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3106<br />
| [[Masora AG]] <br />
| <br />
| M, A, D, P<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 5146<br />
| Pepperl+Fuchs <br />
| <br />
| M, D, P<br />
| <br />
|}<br />
<br />
<br />
* A: Exhibitors with their own stands at the Interlift<br />
* P: A CANopen product is either being produced, developed or sold<br />
* D: A product is shown at the demonstrator<br />
* M: Member of CAN in Automation<br />
* I: Here you receive information about CANopen-Lift<br />
<br />
== CANopen lift products on the Interlift ==<br />
<br />
We will provide an overview of the booths with CANopen products for you here. <br />
<br />
<gallery><br />
Datei:Lageplan2013_CANopen_Halle1.png|Hall 1<br />
Datei:Lageplan2013_CANopen_Halle3.png|Hall 3<br />
Datei:Lageplan2013_CANopen_Halle5.png|Hall 5<br />
Datei:Lageplan2013_CANopen_Halle7.png|Hall 7<br />
</gallery><br />
<br />
== Download == <br />
* [[media:Interlift2013-Lageplan2013_CANopen_Halle1.pdf|Site plan for Hall 1 as a PDF document]]<br />
* [[media:Interlift2013-Lageplan2013_CANopen_Halle3.pdf|Site plan for Hall 3 as a PDF document]]<br />
* [[media:Interlift2013-Lageplan2013_CANopen_Halle5.pdf|Site plan for Hall 5 as a PDF document]]<br />
* [[media:Interlift2013-Lageplan2013_CANopen_Halle7.pdf|Site plan for Hall 7 as a PDF document]]<br />
<br />
== Reiew of the last trade fairs == <br />
* [[Interlift 2011]]<br />
* [[Interlift 2009]]<br />
* [[Messeinfos von der Interlift 2007|Interlift 2007]]<br />
<br />
[[Category:SMG Lift]]</div>Jan.Merkelbaghttps://en.canopen-lift.org/index.php?title=CANopen-Lift:Current_events&diff=3034CANopen-Lift:Current events2013-01-19T11:03:44Z<p>Jan.Merkelbag: fixed a broken link</p>
<hr />
<div>[[de:Aktuelle_Ereignisse]]<br />
[[File:Calendar.png|right]]<br />
= Dates =<br />
== CANopen in general == <br />
The current meetings for CANopen you will find on [http://www.can-cia.org/ www.can-cia.org/] and if you are a CiA member on [http://member.can-cia.org/ http://member.can-cia.org/]<br />
<br />
== CANopen Lift ==<br />
=== 2012-09-12 Meeting MG Lift ===<br />
The next meeting of the marketing group lift [[MG Lift]] will take place on September 12th 2012 at [[ELFIN GmbH]], Cologne, Germany. <br />
<br />
The CiA invited all members of the marketing group to the next meeting. <br />
<br />
=== 2012-09-25 SIG Lift Plugfest ===<br />
CAN in Automation would like to invite you to the 5th plug fest CiA 417 V2.1 (CANopen lift), on September 25, 2012, in Nuremberg, Germany.<br />
<br />
The 5th CiA 417 plug fest is focused on testing the interoperability. <br />
<br />
The following functions will be tested as well:<br />
* The error counter<br />
* Energy saving functions as well as energy measurement issues<br />
* Changing the parameter set<br />
* The bootloader<br />
<br />
If you didn't got an invitation, please contact the CiA office.<br />
<br />
=== 2012-09-26 Meeting SIG Lift ===<br />
The netxt meeting will take place on '''26th September 2012''' in Nuremberg, one day after the next plugfest.<br />
<br />
The CiA will invite all members to this meeting. <br />
<br />
=== 2013-01-29 Meeting of the [[MG Lift]] ===<br />
The last meeting of the Marketing group lift took place on 12 September 2012 at the company [[ELFIN GmbH]] in Cologne.<br />
<br />
The next meeting of the SMG lift is scheduled for 29 January 2013 again at [[ELFIN GmbH|ELFIN]] in Cologne. An invitation to the meeting was sent to the members of CiA. Directions to this meeting is available on the homepage of the [http://elfin.de/en/get_in_touch ELFIN GmbH]. <br />
<br />
You can find the topics of the upcoming meeting at [[Marketing_Group_Lift|Marketing Group lift]].<br />
<br />
The date for the meeting after the next meeting was set on before. The marketing group will meet on 5 March 2013 in Heilbronn. Please reserve this date before.<br />
<br />
=== 2013-07 [[CANopen Lift Plugfest|Plugfest]] of the SIG Lift ===<br />
To verify the interoperability of the CANopen modules in July 2013, the 6th CANopen Lift Plugfest takes place in Nuremberg.<br />
<br />
The focus of the next Plugfests are among others in the test of the functions of the current version 2.1:<br />
<br />
* the ErrorCounter<br />
* the energy-saving features and power measurements<br />
* Load / save parameter sets<br />
* the bootloader function<br />
<br />
The CiA will send the invitations to the members of the group to lift Plugfest as soon as the exact date has been set. If you are interested to test your components, you should contact the CiA and send the latest EDS files of the test equipment to the CiA.<br />
<br />
=== 2013-07 Meeting of the SIG Lift ===<br />
The last meeting of [[SIG Lift]] was held on 26th September 2012 in Nuremberg. The next meeting of the [[SIG Lift]] is planned for July 2013, one day after the next Plugfest. The invitation will be sent in due time by the CiA to members. For [[Suggestions_of_topics_for_the_next_workshop|the topics for the next workshop]], see this wiki. Please complete your desired topics.<br />
<br />
[[Category: SIG_Lift]]<br />
[[Category: MG Lift]]</div>Jan.Merkelbaghttps://en.canopen-lift.org/index.php?title=CANopen-Lift:Current_events&diff=3033CANopen-Lift:Current events2013-01-19T11:03:00Z<p>Jan.Merkelbag: appended the meetings in 2013</p>
<hr />
<div>[[de:Aktuelle_Ereignisse]]<br />
[[File:Calendar.png|right]]<br />
= Dates =<br />
== CANopen in general == <br />
The current meetings for CANopen you will find on [http://www.can-cia.org/ www.can-cia.org/] and if you are a CiA member on [http://member.can-cia.org/ http://member.can-cia.org/]<br />
<br />
== CANopen Lift ==<br />
=== 2012-09-12 Meeting MG Lift ===<br />
The next meeting of the marketing group lift [[MG Lift]] will take place on September 12th 2012 at [[ELFIN GmbH]], Cologne, Germany. <br />
<br />
The CiA invited all members of the marketing group to the next meeting. <br />
<br />
=== 2012-09-25 SIG Lift Plugfest ===<br />
CAN in Automation would like to invite you to the 5th plug fest CiA 417 V2.1 (CANopen lift), on September 25, 2012, in Nuremberg, Germany.<br />
<br />
The 5th CiA 417 plug fest is focused on testing the interoperability. <br />
<br />
The following functions will be tested as well:<br />
* The error counter<br />
* Energy saving functions as well as energy measurement issues<br />
* Changing the parameter set<br />
* The bootloader<br />
<br />
If you didn't got an invitation, please contact the CiA office.<br />
<br />
=== 2012-09-26 Meeting SIG Lift ===<br />
The netxt meeting will take place on '''26th September 2012''' in Nuremberg, one day after the next plugfest.<br />
<br />
The CiA will invite all members to this meeting. <br />
<br />
=== 2013-01-29 Meeting of the [[MG Lift]] ===<br />
The last meeting of the Marketing group lift took place on 12 September 2012 at the company [[ELFIN GmbH]] in Cologne.<br />
<br />
The next meeting of the SMG lift is scheduled for 29 January 2013 again at [[ELFIN GmbH|ELFIN]] in Cologne. An invitation to the meeting was sent to the members of CiA. Directions to this meeting is available on the homepage of the [http://elfin.de/en/get_in_touch ELFIN GmbH]. <br />
<br />
You can find the topics of the upcoming meeting at [[Marketing_Group_Lift|Marketing Group lift]].<br />
<br />
The date for the meeting after the next meeting was set on before. The marketing group will meet on 5 March 2013 in Heilbronn. Please reserve this date before.<br />
<br />
=== 2013-07 [[CANopen Lift Plugfest|Plugfest]] of the SIG Lift ===<br />
To verify the interoperability of the CANopen modules in July 2013, the 6th CANopen Lift Plugfest takes place in Nuremberg.<br />
<br />
The focus of the next Plugfests are among others in the test of the functions of the current version 2.1:<br />
<br />
* the ErrorCounter<br />
* the energy-saving features and power measurements<br />
* Load / save parameter sets<br />
* the bootloader function<br />
<br />
The CiA will send the invitations to the members of the group to lift Plugfest as soon as the exact date has been set. If you are interested to test your components, you should contact the CiA and send the latest EDS files of the test equipment to the CiA.<br />
<br />
=== 2013-07 Meeting of the SIG Lift ===<br />
The last meeting of [[SIG Lift]] was held on 26th September 2012 in Nuremberg. The next meeting of the [[SIG Lift]] is planned for July 2013, one day after the next Plugfest. The invitation will be sent in due time by the CiA to members. For [[Suggestions_of_topics_for_the_next_workshop|the topics for the next workshop]], see this wiki. Please complete your desired topics.<br />
<br />
[[Category: SIG Lift]]<br />
[[Category: MG Lift]]</div>Jan.Merkelbaghttps://en.canopen-lift.org/index.php?title=CANopen-Lift:Community_portal&diff=3032CANopen-Lift:Community portal2012-10-31T10:37:33Z<p>Jan.Merkelbag: broken link correction</p>
<hr />
<div>[[de:CANopen-Lift:Portal]]<br />
<div style="padding: 5px; border:solid 2px #6688aa; background-color:#F9F9F9;"><br />
<div style="padding: 3px; text-align: center; font-size:180%; line-height:180%;"><br />
CANopen-Lift.org Overview<br />
[[Image:CANopen-Lift-Portal.gif |center|700px]]</div><br />
{| border="0" cellpadding="10" style="background-color:#F9F9F9;" <br />
|-<br />
| valign="top" width="33%" | <br />
<div style="padding: 4px; text-align: center; font-size:130%; border-bottom: solid 2px #6688aa;">'''Application Profile'''</div><br />
* [[General about CANopen in a lift]]<br />
* [[Questions about CANopen-Lift]]<br />
* [[The CANopen application profile for lifts CiA-417]]<br />
* [[Introduction to the standardized network for lift control systems]]<br />
* [[Current state]]<br />
* [http://www.can-cia.org/ CAN in Automation]<br />
* [[Suggestions_of_topics_for_the_next_workshop|Topic suggestions for upcoming meetings]]<br />
* [[Current events]]<br />
* [[Extensions of the profile]]<br />
* [[Recommendations for CANopen-Lift-products]]<br />
* [[CANopen-Lift projects]]<br />
* [[Application Notes]]<br />
<br />
| valign="top" width="33%" | <br />
<div style="padding: 4px; text-align: center; font-size:130%; border-bottom: solid 2px #6688aa;">'''CANopen-Lift Products'''</div><br />
<br />
;Controller<br />
* [[Controller bp306]]<br />
* [[Controller bp308]]<br />
* [[Controller dc206]]<br />
* [[CAN-Leistungs-Platine CLK-01]]<br />
* [[Controller MLC-4000]]<br />
* [[Controller WECAN]]<br />
* [[Lift Master Controller LMC-350-20]]<br />
<br />
;Drive<br />
* [[Drive frequency converter DSV 5445]]<br />
* [[Drive frequency converter Unidrive LFT]]<br />
* [[Drive frequency converter ZETADYN 3BF]]<br />
<br />
;Input/Output<br />
* [[Lift I/O Module LIO-350-20]]<br />
<br />
;Panel<br />
* [[CAN-Adapter-Platine CAP-01]]<br />
* [[CAN-Bus-Knoten cbk01]]<br />
* [[CAN-LCD LCI128 with 6 I/O ]]<br />
* [[CAN-LCD LCI16 with 8 I/O ]]<br />
* [[Panel Node CANnode CN16]]<br />
* [[Hall Panel Node CANsmall CS08]]<br />
* [[Lift Hall Call Module LHC-350-20]]<br />
* [[Lift Hall Call Module LHC-355-20]]<br />
* [[Lift Fire Module LFM-350-20]]<br />
* [[Lift Car Call Module LCC-350-20]]<br />
* [[Lift Car Call Module LCC-320-20]]<br />
* [[Lift Display Module LDM-050-xx]]<br />
* [[Lift Display Unit LDU-350-xx]]<br />
<br />
;Position<br />
* [[Absolut position encoder GXP5W]]<br />
* [[Absolute Rotary Encoder CANopen Lift]]<br />
* [[Absolut multiturn position encoder CANLift]]<br />
* [[Schachtkopierung WDGMSM]]<br />
* [[USP-30-CANopen]]<br />
* [[Lift Positioning Module LPM-350-A0]]<br />
* [[Lift Positioning Module LPM-350-E0]]<br />
<br />
;Tools<br />
* [[CANalyzer.CANopen]]<br />
* [[CANoe.CANopen]]<br />
* [[CANopen Device Monitor]]<br />
* [[CANopen Design Tool and Protocol Stack]]<br />
* [[CANopen Source Code]]<br />
* [[CAN remote gateway CDG-01]]<br />
* [[CANwizard]]<br />
* [[CANwizard CN16]]<br />
* [[CANwizard CS08]]<br />
<br />
| valign="top" width="33%" | <br />
<div style="padding: 4px; text-align: center; font-size:130%; border-bottom: solid 2px #6688aa;">'''Manufacturer/Supplier'''</div><br />
<br />
;Controller<br />
* [[Böhnke & Partner GmbH |Böhnke + Partner GmbH]]<br />
* [[Intec GmbH]]<br />
* [[Masora AG]]<br />
* [[Strack Lift Automation GmbH]]<br />
* [[HEC GmbH]]<br />
* [[Weber Lifttechnik GmbH]]<br />
<br />
;Door Drive<br />
* [[Siemens AG (I&S EDM)]] <br />
<br />
;Drive<br />
* [[Control Techniques GmbH]] <br />
* [[Emotron - Lift Center GmbH]]<br />
* [[LiftEquip GmbH Elevator Components]]<br />
* [[Ziehl-Abegg AG]]<br />
<br />
;Network<br />
* [[Agilion GmbH]]<br />
* [[Böhnke & Partner GmbH |Böhnke + Partner GmbH]]<br />
<br />
<br />
;Panel<br />
* [[Böhnke & Partner GmbH |Böhnke + Partner GmbH]]<br />
* [[bs tableau oHG]]<br />
* [[Hans & Jos. Kronenberg GmbH]]<br />
* [[Hisselektronik AB]]<br />
* [[Intec GmbH]]<br />
* [[Masora AG]]<br />
* [[Safeline Europe]]<br />
* [[SCHAEFER GmbH]]<br />
<br />
;Position<br />
* [[Attosensor GmbH]]<br />
* [[Baumer IVO GmbH & Co. KG]]<br />
* [[ELGO Electronic GmbH]]<br />
* [[Fritz Kübler GmbH]]<br />
* [[K.A. Schmersal GmbH]]<br />
* [[POSITAL GmbH]] <br />
* [[Masora AG]]<br />
* [[Wachendorff Automation GmbH & Co. KG]]<br />
<br />
;Tools<br />
* [[Agilion GmbH]]<br />
* [[Böhnke & Partner GmbH |Böhnke + Partner GmbH]]<br />
* [[MicroControl GmbH & Co. KG]]<br />
* [[port GmbH]]<br />
* [[Vector Informatik GmbH]]<br />
<br />
;other<br />
* [[Heilbronn University]]<br />
* [[ELFIN GmbH]]<br />
|}<br />
<br />
{| border="0" cellpadding="10" style="background-color:#F9F9F9;" <br />
|-<br />
| valign="top" width="50%" | <br />
<div style="padding: 4px; text-align: center; font-size:130%; border-bottom: solid 2px #6688aa;">'''Press and Marketing'''</div><br />
<br />
;Marketing Group Lift<br />
* [[Reference List|References]]<br />
* [[CANopen-Lift Projects#Reference Lift|Reference Lift]]<br />
<br />
;Press<br />
; -2011-<br />
*[[Meeting CANopen Spezial Interest Group Lift 5-2011]]<br />
; -2010-<br />
* [[3rd CANopen Lift plug fest]]<br />
* [[CiA 417 (CANopen Lift) version 2.0]]<br />
* [[The standardized network for lift control systems]]<br />
* [[CANopen-Safety-Chip CSC02 certified by TÜV]]<br />
* [[Displays can do much more than showing numbers]]<br />
* [[Standardized networking for elevator components based on CiA-417 Lift Control]]<br />
; -2009-<br />
* [[CANopen Lift demonstrator in action]]<br />
* [[CANopen Lift products at Interlift 2009]]<br />
* [[CANopen Plugfest Results, Plans]]<br />
; -2007-<br />
* [[Report - Interlift Augsburg, DE]]<br />
* [[CANopen encoders for elevator engineering]]<br />
* [[CANopen lifts people]]<br />
* [[CANopen specification for lift control systems]]<br />
* [[Drive for CANopen lift]]<br />
* [[Experiences with CANopen Lift networks]]<br />
* [[Hamburg church with a view - CANopen lifts visitors]]<br />
* [[Lift operating panels with CANopen interface]]<br />
* [[Safe and simple - CANopen encoders for lift technology]]<br />
* [[Vertical transport saves energy]]<br />
* [[Lift by Wire - LiftReport 2/2002]]<br />
<br />
| valign="top" width="50%" |<br />
<div style="padding: 4px; text-align: center; font-size:130%; border-bottom: solid 2px #6688aa;">'''Current events'''</div><br />
<div style="font-size:100%" ><br />
'''Open-Device-Project published''' <br />
<br />
The first version of the [[Open Device|Open-Device-Project]] was published. <br />
<br />
</div><br />
|}</div>Jan.Merkelbaghttps://en.canopen-lift.org/index.php?title=Suggestions_of_topics_for_the_next_workshop&diff=3031Suggestions of topics for the next workshop2012-10-31T10:20:53Z<p>Jan.Merkelbag: updating</p>
<hr />
<div>[[de:Themenvorschläge_für_das_nächste_Arbeitstreffen]]<br />
= Special Interest Group (SIG) Lift =<br />
The next meeting of the SIG Lift takes place on 26 September 2012 in Nuremberg. <br />
<br />
== Agenda for the meeting of the SIG Lift on 26 September ==<br />
* '''Topic 1 – Formalities'''<br />
** Adoption of the agenda<br />
** Introduction of participants<br />
** Minutes of the [[Meeting_CANopen_Special_Interest_Group_Lift_4-2012|meeting of April 2012]]<br />
** Analysis of the current status of CANopen Lift <br />
<br />
* '''Topic 2 – Bootloader for CANopen Lift equipment''' <br />
** Uniform procedure for the firmware update of CANopen Lift equipment <br />
<br />
* '''Topic 3 – Extension of the specification''' <br />
** [[Access_Control|Objects for the RFID Reader]] <br />
** Quick-stop function for the Drive Unit using [[Error_Handling|Error Handling]]<br />
<br />
* '''Topic 4 – Documentation'''<br />
** [[Application_Notes|Application notes]] (e.g. of the Quick-stop function for the Drive Unit)<br />
<br />
* '''Top 5 - Marketing'''<br />
** Review of the SMG Lift's workshop of 12 September 2012<br />
** Information on current and planned marketing activities<br />
** Information on the [[CANopen-Lift_Presentation_Model|presentation model]], eventually retrofitting an energy management function<br />
** Recalling subgroup SMG Lift UK + FR<br />
<br />
* '''Top 6 - CANopen Lift Plugfest'''<br />
** Looking back at the previous day's Plugfest<br />
** Requests for special tests during future Plugfests<br />
** Elaboration of checklists as a prerequisite for an automatic test system <br />
<br />
* '''Top 7 - Miscellaneous'''<br />
** Introduction of new CANopen products<br />
** New date, place and topics for the next meeting<br />
** Definition of PDOs for proprietary items<br />
** ...<br />
<br />
If you have further suggestions, please feel free to add them to '''Topic 7 - Miscellaneous'''.<br />
<br />
<br />
[[Category: SIG Lift]]</div>Jan.Merkelbaghttps://en.canopen-lift.org/index.php?title=CANopen-Lift:Community_portal&diff=3029CANopen-Lift:Community portal2012-10-31T08:48:42Z<p>Jan.Merkelbag: </p>
<hr />
<div>[[de:CANopen-Lift:Portal]]<br />
<div style="padding: 5px; border:solid 2px #6688aa; background-color:#F9F9F9;"><br />
<div style="padding: 3px; text-align: center; font-size:180%; line-height:180%;"><br />
CANopen-Lift.org Overview<br />
[[Image:CANopen-Lift-Portal.gif |center|700px]]</div><br />
{| border="0" cellpadding="10" style="background-color:#F9F9F9;" <br />
|-<br />
| valign="top" width="33%" | <br />
<div style="padding: 4px; text-align: center; font-size:130%; border-bottom: solid 2px #6688aa;">'''Application Profile'''</div><br />
* [[General about CANopen in a lift]]<br />
* [[Questions about CANopen-Lift]]<br />
* [[The CANopen application profile for lifts CiA-417]]<br />
* [[Introduction to the standardized network for lift control systems]]<br />
* [[Current state]]<br />
* [http://www.can-cia.org/ CAN in Automation]<br />
* [[Topic_suggestions_for_upcoming_workshops|Topic suggestions for upcoming workshops]]<br />
* [[Current events]]<br />
* [[Extensions of the profile]]<br />
* [[Recommendations for CANopen-Lift-products]]<br />
* [[CANopen-Lift projects]]<br />
* [[Application Notes]]<br />
<br />
| valign="top" width="33%" | <br />
<div style="padding: 4px; text-align: center; font-size:130%; border-bottom: solid 2px #6688aa;">'''CANopen-Lift Products'''</div><br />
<br />
;Controller<br />
* [[Controller bp306]]<br />
* [[Controller bp308]]<br />
* [[Controller dc206]]<br />
* [[CAN-Leistungs-Platine CLK-01]]<br />
* [[Controller MLC-4000]]<br />
* [[Controller WECAN]]<br />
* [[Lift Master Controller LMC-350-20]]<br />
<br />
;Drive<br />
* [[Drive frequency converter DSV 5445]]<br />
* [[Drive frequency converter Unidrive LFT]]<br />
* [[Drive frequency converter ZETADYN 3BF]]<br />
<br />
;Input/Output<br />
* [[Lift I/O Module LIO-350-20]]<br />
<br />
;Panel<br />
* [[CAN-Adapter-Platine CAP-01]]<br />
* [[CAN-Bus-Knoten cbk01]]<br />
* [[CAN-LCD LCI128 with 6 I/O ]]<br />
* [[CAN-LCD LCI16 with 8 I/O ]]<br />
* [[Panel Node CANnode CN16]]<br />
* [[Hall Panel Node CANsmall CS08]]<br />
* [[Lift Hall Call Module LHC-350-20]]<br />
* [[Lift Hall Call Module LHC-355-20]]<br />
* [[Lift Fire Module LFM-350-20]]<br />
* [[Lift Car Call Module LCC-350-20]]<br />
* [[Lift Car Call Module LCC-320-20]]<br />
* [[Lift Display Module LDM-050-xx]]<br />
* [[Lift Display Unit LDU-350-xx]]<br />
<br />
;Position<br />
* [[Absolut position encoder GXP5W]]<br />
* [[Absolute Rotary Encoder CANopen Lift]]<br />
* [[Absolut multiturn position encoder CANLift]]<br />
* [[Schachtkopierung WDGMSM]]<br />
* [[USP-30-CANopen]]<br />
* [[Lift Positioning Module LPM-350-A0]]<br />
* [[Lift Positioning Module LPM-350-E0]]<br />
<br />
;Tools<br />
* [[CANalyzer.CANopen]]<br />
* [[CANoe.CANopen]]<br />
* [[CANopen Device Monitor]]<br />
* [[CANopen Design Tool and Protocol Stack]]<br />
* [[CANopen Source Code]]<br />
* [[CAN remote gateway CDG-01]]<br />
* [[CANwizard]]<br />
* [[CANwizard CN16]]<br />
* [[CANwizard CS08]]<br />
<br />
| valign="top" width="33%" | <br />
<div style="padding: 4px; text-align: center; font-size:130%; border-bottom: solid 2px #6688aa;">'''Manufacturer/Supplier'''</div><br />
<br />
;Controller<br />
* [[Böhnke & Partner GmbH |Böhnke + Partner GmbH]]<br />
* [[Intec GmbH]]<br />
* [[Masora AG]]<br />
* [[Strack Lift Automation GmbH]]<br />
* [[HEC GmbH]]<br />
* [[Weber Lifttechnik GmbH]]<br />
<br />
;Door Drive<br />
* [[Siemens AG (I&S EDM)]] <br />
<br />
;Drive<br />
* [[Control Techniques GmbH]] <br />
* [[Emotron - Lift Center GmbH]]<br />
* [[LiftEquip GmbH Elevator Components]]<br />
* [[Ziehl-Abegg AG]]<br />
<br />
;Network<br />
* [[Agilion GmbH]]<br />
* [[Böhnke & Partner GmbH |Böhnke + Partner GmbH]]<br />
<br />
<br />
;Panel<br />
* [[Böhnke & Partner GmbH |Böhnke + Partner GmbH]]<br />
* [[bs tableau oHG]]<br />
* [[Hans & Jos. Kronenberg GmbH]]<br />
* [[Hisselektronik AB]]<br />
* [[Intec GmbH]]<br />
* [[Masora AG]]<br />
* [[Safeline Europe]]<br />
* [[SCHAEFER GmbH]]<br />
<br />
;Position<br />
* [[Attosensor GmbH]]<br />
* [[Baumer IVO GmbH & Co. KG]]<br />
* [[ELGO Electronic GmbH]]<br />
* [[Fritz Kübler GmbH]]<br />
* [[K.A. Schmersal GmbH]]<br />
* [[POSITAL GmbH]] <br />
* [[Masora AG]]<br />
* [[Wachendorff Automation GmbH & Co. KG]]<br />
<br />
;Tools<br />
* [[Agilion GmbH]]<br />
* [[Böhnke & Partner GmbH |Böhnke + Partner GmbH]]<br />
* [[MicroControl GmbH & Co. KG]]<br />
* [[port GmbH]]<br />
* [[Vector Informatik GmbH]]<br />
<br />
;other<br />
* [[Heilbronn University]]<br />
* [[ELFIN GmbH]]<br />
|}<br />
<br />
{| border="0" cellpadding="10" style="background-color:#F9F9F9;" <br />
|-<br />
| valign="top" width="50%" | <br />
<div style="padding: 4px; text-align: center; font-size:130%; border-bottom: solid 2px #6688aa;">'''Press and Marketing'''</div><br />
<br />
;Marketing Group Lift<br />
* [[Reference List|References]]<br />
* [[CANopen-Lift Projects#Reference Lift|Reference Lift]]<br />
<br />
;Press<br />
; -2011-<br />
*[[Meeting CANopen Spezial Interest Group Lift 5-2011]]<br />
; -2010-<br />
* [[3rd CANopen Lift plug fest]]<br />
* [[CiA 417 (CANopen Lift) version 2.0]]<br />
* [[The standardized network for lift control systems]]<br />
* [[CANopen-Safety-Chip CSC02 certified by TÜV]]<br />
* [[Displays can do much more than showing numbers]]<br />
* [[Standardized networking for elevator components based on CiA-417 Lift Control]]<br />
; -2009-<br />
* [[CANopen Lift demonstrator in action]]<br />
* [[CANopen Lift products at Interlift 2009]]<br />
* [[CANopen Plugfest Results, Plans]]<br />
; -2007-<br />
* [[Report - Interlift Augsburg, DE]]<br />
* [[CANopen encoders for elevator engineering]]<br />
* [[CANopen lifts people]]<br />
* [[CANopen specification for lift control systems]]<br />
* [[Drive for CANopen lift]]<br />
* [[Experiences with CANopen Lift networks]]<br />
* [[Hamburg church with a view - CANopen lifts visitors]]<br />
* [[Lift operating panels with CANopen interface]]<br />
* [[Safe and simple - CANopen encoders for lift technology]]<br />
* [[Vertical transport saves energy]]<br />
* [[Lift by Wire - LiftReport 2/2002]]<br />
<br />
| valign="top" width="50%" |<br />
<div style="padding: 4px; text-align: center; font-size:130%; border-bottom: solid 2px #6688aa;">'''Current events'''</div><br />
<div style="font-size:100%" ><br />
'''Open-Device-Project published''' <br />
<br />
The first version of the [[Open Device|Open-Device-Project]] was published. <br />
<br />
</div><br />
|}</div>Jan.Merkelbaghttps://en.canopen-lift.org/index.php?title=CANopen-Lift:Community_portal&diff=3028CANopen-Lift:Community portal2012-10-31T08:37:41Z<p>Jan.Merkelbag: corrected translation</p>
<hr />
<div>[[de:CANopen-Lift:Portal]]<br />
<div style="padding: 5px; border:solid 2px #6688aa; background-color:#F9F9F9;"><br />
<div style="padding: 3px; text-align: center; font-size:180%; line-height:180%;"><br />
CANopen-Lift.org Overview<br />
[[Image:CANopen-Lift-Portal.gif |center|700px]]</div><br />
{| border="0" cellpadding="10" style="background-color:#F9F9F9;" <br />
|-<br />
| valign="top" width="33%" | <br />
<div style="padding: 4px; text-align: center; font-size:130%; border-bottom: solid 2px #6688aa;">'''Application Profile'''</div><br />
* [[General about CANopen in a lift]]<br />
* [[Questions about CANopen-Lift]]<br />
* [[The CANopen application profile for lifts CiA-417]]<br />
* [[Introduction to the standardized network for lift control systems]]<br />
* [[Current state]]<br />
* [http://www.can-cia.org/ CAN in Automation]<br />
* [[Topic suggestions for upcoming meetings]]<br />
* [[Current events]]<br />
* [[Extensions of the profile]]<br />
* [[Recommendations for CANopen-Lift-products]]<br />
* [[CANopen-Lift projects]]<br />
* [[Application Notes]]<br />
<br />
| valign="top" width="33%" | <br />
<div style="padding: 4px; text-align: center; font-size:130%; border-bottom: solid 2px #6688aa;">'''CANopen-Lift Products'''</div><br />
<br />
;Controller<br />
* [[Controller bp306]]<br />
* [[Controller bp308]]<br />
* [[Controller dc206]]<br />
* [[CAN-Leistungs-Platine CLK-01]]<br />
* [[Controller MLC-4000]]<br />
* [[Controller WECAN]]<br />
* [[Lift Master Controller LMC-350-20]]<br />
<br />
;Drive<br />
* [[Drive frequency converter DSV 5445]]<br />
* [[Drive frequency converter Unidrive LFT]]<br />
* [[Drive frequency converter ZETADYN 3BF]]<br />
<br />
;Input/Output<br />
* [[Lift I/O Module LIO-350-20]]<br />
<br />
;Panel<br />
* [[CAN-Adapter-Platine CAP-01]]<br />
* [[CAN-Bus-Knoten cbk01]]<br />
* [[CAN-LCD LCI128 with 6 I/O ]]<br />
* [[CAN-LCD LCI16 with 8 I/O ]]<br />
* [[Panel Node CANnode CN16]]<br />
* [[Hall Panel Node CANsmall CS08]]<br />
* [[Lift Hall Call Module LHC-350-20]]<br />
* [[Lift Hall Call Module LHC-355-20]]<br />
* [[Lift Fire Module LFM-350-20]]<br />
* [[Lift Car Call Module LCC-350-20]]<br />
* [[Lift Car Call Module LCC-320-20]]<br />
* [[Lift Display Module LDM-050-xx]]<br />
* [[Lift Display Unit LDU-350-xx]]<br />
<br />
;Position<br />
* [[Absolut position encoder GXP5W]]<br />
* [[Absolute Rotary Encoder CANopen Lift]]<br />
* [[Absolut multiturn position encoder CANLift]]<br />
* [[Schachtkopierung WDGMSM]]<br />
* [[USP-30-CANopen]]<br />
* [[Lift Positioning Module LPM-350-A0]]<br />
* [[Lift Positioning Module LPM-350-E0]]<br />
<br />
;Tools<br />
* [[CANalyzer.CANopen]]<br />
* [[CANoe.CANopen]]<br />
* [[CANopen Device Monitor]]<br />
* [[CANopen Design Tool and Protocol Stack]]<br />
* [[CANopen Source Code]]<br />
* [[CAN remote gateway CDG-01]]<br />
* [[CANwizard]]<br />
* [[CANwizard CN16]]<br />
* [[CANwizard CS08]]<br />
<br />
| valign="top" width="33%" | <br />
<div style="padding: 4px; text-align: center; font-size:130%; border-bottom: solid 2px #6688aa;">'''Manufacturer/Supplier'''</div><br />
<br />
;Controller<br />
* [[Böhnke & Partner GmbH |Böhnke + Partner GmbH]]<br />
* [[Intec GmbH]]<br />
* [[Masora AG]]<br />
* [[Strack Lift Automation GmbH]]<br />
* [[HEC GmbH]]<br />
* [[Weber Lifttechnik GmbH]]<br />
<br />
;Door Drive<br />
* [[Siemens AG (I&S EDM)]] <br />
<br />
;Drive<br />
* [[Control Techniques GmbH]] <br />
* [[Emotron - Lift Center GmbH]]<br />
* [[LiftEquip GmbH Elevator Components]]<br />
* [[Ziehl-Abegg AG]]<br />
<br />
;Network<br />
* [[Agilion GmbH]]<br />
* [[Böhnke & Partner GmbH |Böhnke + Partner GmbH]]<br />
<br />
<br />
;Panel<br />
* [[Böhnke & Partner GmbH |Böhnke + Partner GmbH]]<br />
* [[bs tableau oHG]]<br />
* [[Hans & Jos. Kronenberg GmbH]]<br />
* [[Hisselektronik AB]]<br />
* [[Intec GmbH]]<br />
* [[Masora AG]]<br />
* [[Safeline Europe]]<br />
* [[SCHAEFER GmbH]]<br />
<br />
;Position<br />
* [[Attosensor GmbH]]<br />
* [[Baumer IVO GmbH & Co. KG]]<br />
* [[ELGO Electronic GmbH]]<br />
* [[Fritz Kübler GmbH]]<br />
* [[K.A. Schmersal GmbH]]<br />
* [[POSITAL GmbH]] <br />
* [[Masora AG]]<br />
* [[Wachendorff Automation GmbH & Co. KG]]<br />
<br />
;Tools<br />
* [[Agilion GmbH]]<br />
* [[Böhnke & Partner GmbH |Böhnke + Partner GmbH]]<br />
* [[MicroControl GmbH & Co. KG]]<br />
* [[port GmbH]]<br />
* [[Vector Informatik GmbH]]<br />
<br />
;other<br />
* [[Heilbronn University]]<br />
* [[ELFIN GmbH]]<br />
|}<br />
<br />
{| border="0" cellpadding="10" style="background-color:#F9F9F9;" <br />
|-<br />
| valign="top" width="50%" | <br />
<div style="padding: 4px; text-align: center; font-size:130%; border-bottom: solid 2px #6688aa;">'''Press and Marketing'''</div><br />
<br />
;Marketing Group Lift<br />
* [[Reference List|References]]<br />
* [[CANopen-Lift Projects#Reference Lift|Reference Lift]]<br />
<br />
;Press<br />
; -2011-<br />
*[[Meeting CANopen Spezial Interest Group Lift 5-2011]]<br />
; -2010-<br />
* [[3rd CANopen Lift plug fest]]<br />
* [[CiA 417 (CANopen Lift) version 2.0]]<br />
* [[The standardized network for lift control systems]]<br />
* [[CANopen-Safety-Chip CSC02 certified by TÜV]]<br />
* [[Displays can do much more than showing numbers]]<br />
* [[Standardized networking for elevator components based on CiA-417 Lift Control]]<br />
; -2009-<br />
* [[CANopen Lift demonstrator in action]]<br />
* [[CANopen Lift products at Interlift 2009]]<br />
* [[CANopen Plugfest Results, Plans]]<br />
; -2007-<br />
* [[Report - Interlift Augsburg, DE]]<br />
* [[CANopen encoders for elevator engineering]]<br />
* [[CANopen lifts people]]<br />
* [[CANopen specification for lift control systems]]<br />
* [[Drive for CANopen lift]]<br />
* [[Experiences with CANopen Lift networks]]<br />
* [[Hamburg church with a view - CANopen lifts visitors]]<br />
* [[Lift operating panels with CANopen interface]]<br />
* [[Safe and simple - CANopen encoders for lift technology]]<br />
* [[Vertical transport saves energy]]<br />
* [[Lift by Wire - LiftReport 2/2002]]<br />
<br />
| valign="top" width="50%" |<br />
<div style="padding: 4px; text-align: center; font-size:130%; border-bottom: solid 2px #6688aa;">'''Current events'''</div><br />
<div style="font-size:100%" ><br />
'''Open-Device-Project published''' <br />
<br />
The first version of the [[Open Device|Open-Device-Project]] was published. <br />
<br />
</div><br />
|}</div>Jan.Merkelbaghttps://en.canopen-lift.org/index.php?title=Demo_Lift&diff=3014Demo Lift2012-09-28T14:14:05Z<p>Jan.Merkelbag: </p>
<hr />
<div>[[de:Referenzaufzug]]<br />
=Model lift system with CANopen components=<br />
<br />
The Heilbronn University is known for congresses and conferences in the field of elevators for many years. Now, a research project is started which aims various aspects of the automation of elevators with CANopen. Examples are compliance tests "in the loop" and the possibilities of telemetry and remote diagnostics. Suggestions and discussions on the project currently come from Mr. Hellmich, Böhnke + Partner, Bergisch Gladbach (now c/o [http://elfin.de elfin.de]).<br />
<br />
''You could also be a part of this project!''<br />
<br />
In order to obtain a realistic test environment, a group of four students from the master's degree courses in Mechanical Engineering and Mechatronics at the Heilbronn University under the direction of Prof. Dr.-Ing. Ansgar Meroth started a project in which an elevator system model on a scale of 1:10 is built and controlled via original CANopen components. All CANopen components are simultaneously simulated by a corresponding function model in Vector CANoe and MathWorks Matlab/Simulink, allowing to replace components by real time simulated functions.<br />
<br />
The resulting model system shall demonstrate the CANopen standards and provide an opportunity to review new components for conformity. It differs fundamentally from a previous model, designed in the MG lift, by a higher mechanical detail. With its open architecture, a combination of both demonstrators is possible.<br />
<br />
=Model=<br />
<br />
The aim of the model is to construct and build an elevator system on a scale of 1:10. The model will show two shafts, each with three floors and one cabin per shaft. The functionality of the model will correspond as far as possible to the actual functionality of real elevators. However, due to the miniaturization and the better handling, all control panels and control units are not directly installed inside the model, but separated in a control cabinet.<br />
<br />
Because the usage on fairs and exhibitions is possible and welcome, as many components as possible will be provided with windows or will be made of transparent material to allow a better insight. Furthermore, the model will be secured, so that visitors can not touch moving parts or electrical components. To enable the usage on exhibitions, the model will be transportable. This leads to additional demands on the model. The model with dimensions of 1200 mm x 600 mm x 400 mm (HxWxD) is transportable in a car. Furthermore, splitting of the model and securing the movable parts will be guaranteed.<br />
<br />
=Control Units and Network=<br />
All control units used in the demonstrator should be, as far as possible, original equipment of real CANopen lifts. <br />
<br />
The project additionally aims a simulation of the model with all control units with the aid of Vector CANoe and MathWorks Matlab/Simulink. By monitoring the CAN signals of the demonstrator, both programs shall reflect the status of the system. Furthermore, additional control messages should be able to send from these programs to enable a remote control (e.g. call a lift). Thus, additional components or a third shaft may be simulated. In a follow-up project, remote diagnosis is planned.<br />
<br />
<br />
[[file:Gesamt_Front-Ansicht_edit.jpg|300px|Gesamtmodell]] [[file:Gesamt_iso-Ansicht_edit.jpg|300px|Gesamtmodell]] <br />
<br />
<br />
<br />
[[file:Kabine_Front-Ansicht_edit.jpg|300px|Kabine]] [[file:Kabine_in_schiene_iso-Ansicht_edit.jpg|300px|Kabine mit Führung]]<br />
<br />
=Current Status of the Project=<br />
Currently, the design of the system is made with CATIA V5 R19 by Dassault Systèmes. <br />
<br />
Simultaneously, the Matlab/Simulink and CANoe models are built.<br />
<br />
=Sponsors=<br />
Because some components of the elevator model are very expensive, especially the electronic components, you are kindly invited to contribute with your products. We will attach your logo at a prominent place on the model to indicate you as a sponsor. <br />
<br />
The following companies already contribute to the model:<br />
<br />
* Böhnke + Partner GmbH Steuerungssysteme<br />
* SCHAEFER GmbH<br />
* SICK AG<br />
* SafeLine Deutschland GmbH<br />
* Henning GmbH & Co. KG<br />
* Murrplastik Systemtechnik GmbH<br />
* Weidmüller Interface GmbH & Co KG<br />
* …to be continued with your help….<br />
<br />
<br />
If you are interested in sponsoring this project, please contact Mr. Meroth at the following address: ansgar.meroth (at) hs-heilbronn.de</div>Jan.Merkelbaghttps://en.canopen-lift.org/index.php?title=The_standardized_network_for_lift_control_systems&diff=3013The standardized network for lift control systems2012-09-28T14:13:19Z<p>Jan.Merkelbag: </p>
<hr />
<div>''by Jörg Hellmich ([[Böhnke & Partner GmbH |Böhnke + Partner GmbH]], now c/o [http://elfin.de elfin.de])''<br />
<br />
In general, lifts are becoming more complex. An increasing number of electronic devices are installed in lift control systems so as to be able to satisfy both rising demands in regard to functionality and the requirements set forth in current standards and safety specifications. Embedded microprocessors respond to input signals or sensor data and thus generate output signals or messages, which are determined on the basis of algorithms written in the internal firmware. To make it possible for the electronic devices to work together and exchange internal information or commands they will have to be connected with each other by means of serial networks. Controller Are Network (CAN), originally developed for in-vehicle networking, meets the equirements of the lift industry regarding reliability and robustness. By using the principle of prioritized messages, several units can each start sending a message through a transmission medium. The CAN identifier, a prefix to the message, is used to determine, which message has the highest priority. The message with the highest priority will be sent without delay. Lower priority messages will be postponed. Thus real-time communications are possible. <br />
<br />
[[File:plugfest-impressions.jpg|right|450px|PlugFest 2010]]<br />
Many European device manufacturers have decided on the CAN technology to be used in lifts (elevators) to develop a joint language for standardized communication. The primary criteria to be satisfied are the ability to function in real-time, safety, <br />
speed, freedom of licensing requirements, autonomy from any given manufacturer, price and widespread use. But the standardization of the low-level communication protocol is not sufficient for interoperability and exchangeability of devices. <br />
Also the application layer protocol and the content of the messages need to be standardized.<br />
<br />
Therefore, several companies started in 2001 the standardization of higher-layer protocols and profiles for the lift industry within the nonprofit CAN in Automation (CiA) international users’ and manufacturers’ group. Based on CANopen (EN 50325-4/ CiA 301) the CiA 417 application profile for lift control systems was developed. In October 2003, the first prototypes were exhibited at the Interlift. In the meantime, the CiA 417 specification has been reviewed and has been released as version 2.0 beginning of this year.<br />
<br />
==For up to 254 landings==<br />
[[File:Floor-indicator-254.png|right|450px|floor indicator]]<br />
The CiA 417 profile has some limitations: It supports lift group controller with up to eight elevators, 254 landings, and four doors per lift car. Associated with the profile are various specifications and supplementary recommendations, such as for plug connectors or for the colors of the wires. This insures on the one hand that the devices using the CAN network are as compatible as possible and that maximum plug-and-play capability will be achieved. On the other hand, the device manufacturers and lift engineers enjoy great flexibility in designing individual and unique features. Standardization is referenced exclusively to the communications among components attached to the system bus.<br />
<br />
All the functions that can be used within the application are defined as “virtual devices”. These virtual devices are abstract software objects that represent a real-world device (e.g. an absolute value transmitter or a door controller). The concept of virtual devices is used to depict various types of devices, all in the same class of devices, on a common interface. In application profiles there are, as a rule, no master/slave communications in regard to the process data objects (PDO). The normal case is that only virtual devices are specified in application profiles. This lets the equipment manufacturer decide which virtual device is to be implemented in a physical device. This makes it possible to assemble widely varying systems, the topologies of which are not determined by the application profile, since bridges and gateways can quite easily be developed. The lift manufacturer, for instance, can use separate CANopen networks for car control and for the control panels inside the hoist-way.<br />
<br />
==Diagnostics==<br />
In comparison to the past, this application profile offers a wide variety of possibilities to carry out diagnostics work. Firstly, one can naturally equip each device with a status LED or a display. The disadvantage here is, however, that an integrated display involves costs and the technician has to be present on site in order to read the information shown in the display.<br />
<br />
Furthermore, one can use the “virtual console” defined in CANopen-Lift. The virtual console defines a procedure a device uses to apply the content of its own display to the system bus and how this data can be displayed by other devices. Moreover, it is possible, with the help of a control command, to navigate through the menus from other units. Thus not only the content of the frequency inverter display can be depicted in the controls. Additionally, the menu of each individual device can be shown at every other device equipped with a display.<br />
<br />
If a laptop is available for diagnosis and configuration work, it is possible, with a single software program, to parameterize all the devices in an elevator, as the communications and the parameters sets for all the devices are standardized. One configuration tool of this type is the “CANwizard” software.<br />
<br />
Once the laptop has been joined with the system bus the CANwizard scans the bus and reads out the parameters for all the devices connected to it. If the operator has the proper authorization, then the parameters can be changed and written back into the device.<br />
<br />
Additionally, a complete image of the elevator can be archived. This can be used to configure lifts of a similar design, to facilitate configuration of a replacement part or to detect manipulations in parameters.<br />
<br />
The CANwizard makes it possible to execute a software update, for one or more assemblies, regardless of which manufacturer built the units.<br />
<br />
Thanks to the standardization of the process and the fault messages in the bus, a single tool can be used to diagnose all the components and the system as a whole. All the process messages – such as “Low-priority hallway call in floor 8 at door A of lift 1” – can be depicted in plain text, in real time, and stored in a log file together with a time stamp. Thus the technician, working from just a single location, can obtain status information on all the devices and the entire process.<br />
<br />
An electronic data log is associated with each CANopen device and is stored in EDS (electronic data sheet) files. These files describe, in a standardized text format, both the most important parameters for the device as well as physical parameters. Configuration tools can read EDS files and, with their help, can also communicate with previously unknown devices and possibly parameterize them. CANwizard provides an EDS library containing the EDS files for all the known CANopen-Lift devices. <br />
<br />
CANwizard is not associated with any manufacturer but available to every engineer and developer of CANopen devices. It is not desirable that competitors have access to internal know-how concerning certain functions. That is why CANwizard is fitted with an interface to accept add-ons that expand the program’s functions to reflect current standards and the functions of devices on the market. The developers of CANwizard build confidence in their products by communicating openly with users. That includes providing a continuously updated history of the software, accessible for every user, and providing information on expansions of functions and corrections of errors.<br />
<br />
In an age when the Internet is ubiquitous, it is quite natural to offer remote diagnosis. This works as soon as the lift is linked to the Internet via a suitable gateway to CANopen-based control systems.<br />
<br />
==Interoperability==<br />
The objective of the standardization was to define a specification valid around the world, one that was available for use by everyone and one that could not be dominated by any single manufacturer or professional association. The committee members were also supposed to have a background in active standardization work and experience in such efforts. They were to share insights and lend support in the work.<br />
<br />
All these conditions were satisfied by the impartial, CiA organization. CiA takes responsibility for standardization work, organizes training sessions on CANopen, certifies devices, disseminates information at trade fairs and does much more. Work for lifts is done in two areas within CiA. The “Special Interest Group (SIG) Lift” is made up of developers who define new functions, work out the protocol, test and certify devices.<br />
<br />
The “Marketing Group (MG) Lift” provides information about the protocol and the devices on the market, drafts brochures and flyers and organizes trade fair presentations and road shows. The MG Lift also supervised the building of a demonstration unit to show the functionality of the profile and the assemblies. In addition, the CiA independent website at www.canopen-lift.org maintains an open Wiki, where recommendations for new products, application notes and new functions can be discussed.<br />
<br />
To check device interoperability, several meetings a year are held in the framework of SIG Lift (plugfests), in which – using checklists – the compatibility of devices in relationship to the standard and their functionality with other devices are examined. Elaborate and difficult stress tests are also conducted at the plug-fests. These inspect, for example, the behavior of devices at maximum permissible bus lengths or at maximum bus loading.<br />
<br />
In case someone buys a new software version with minor change in between plug-fests, [[Böhnke & Partner GmbH |Böhnke + Partner]] connected several control systems with the Internet. After installing the appropriate driver, any manufacturer can connect a CANopen-Lift lift device – via the Internet – with these controls and examine the functionality of the assemblies.<br />
<br />
==Perspectives==<br />
We believe that in the future all devices will be fitted with standardized bus connectors. These devices can be analyzed and parameterized using all-purpose diagnostics tools.<br />
<br />
Standardized networking in and among elevators also simplifies linkage to the building control center and to remote diagnosis capabilities via the Internet.<br />
<br />
The capability to access many internal parameters in the individual devices gives rise to many new functions that, without this standard, would be very complex or not feasible at all.<br />
<br />
Elevator safety is increased since redundancies arise and devices can monitor each other. In Pessral, for example, the safety-critical sensors and limit switches are replaced with electronic assemblies that offer far greater functionality and thus enhance elevator safety. If these systems are supposed to trade information, then they will have to be interconnected with a safe, non-proprietary bus. “CANopen Safety” makes available a standard used around the world.<br />
<br />
== Weblinks ==<br />
* [http://www.boehnkepartner.de www.boehnkepartner.de] <br />
* [http://www.can-cia.org CAN in Automation (CiA)]<br />
<br />
[[Category: press]]</div>Jan.Merkelbaghttps://en.canopen-lift.org/index.php?title=Standardized_networking_for_elevator_components_based_on_CiA-417_Lift_Control&diff=3012Standardized networking for elevator components based on CiA-417 Lift Control2012-09-28T14:12:54Z<p>Jan.Merkelbag: </p>
<hr />
<div>[[de:Standardisierte_Vernetzung_von_Aufzugskomponenten_auf_der_Grundlage_der_CiA-417_Lift_Control]]<br />
''by Jörg Hellmich, Böhnke + Partner GmbH (http://www.boehnkepartner.de, now c/o [http://elfin.de elfin.de])''<br />
==Preface==<br />
'''Technical systems are, in general, becoming ever more complex. Electronic systems – usually equipped with tiny embedded microprocessors – are implementing new functions, increasing convenience or improving system safety and reliability. Responding to signals made provided by sensors or arriving at inputs, these processors employ the algorithms written in the internal firmware to determine what the assembly actually does. The more information available about the system, the broader the basis upon which decisions can be made.'''<br />
<br />
In order for the electronic assemblies in a system to interact with each other properly and exchange internal information or<br />
commands, they have to be connected one with another by way of a field bus. Various types of field bus, with differing<br />
properties, are used in the automation industry.<br />
<br />
A number of proprietary buses are used in the elevator industry along with the standardized '''CANopen-Lift''' field bus (as per the<br />
CiA-417 application profile).<br />
<br />
This article introduces the basic structure, the properties and the advantages of the latter in comparison with proprietary<br />
systems and provides an insight into the organizational structure of the developer community behind the system.<br />
<br />
This is followed by a description of functions that become possible only with open networking among components built by<br />
different manufacturers. Finally, perspectives for coming developments will be described.<br />
<br />
==Background==<br />
Elevators are becoming ever more complex. More and more electronic devices are being installed in elevators so as to be able to satisfy both rising demands in regard to functionality and the requirements set forth in current standards and safety specifications.<br />
<br />
Embedded microprocessors are usually hard at work inside these electronic devices. Responding to input signals or sensor data, these microprocessors generate output signals or messages. The nature of the signals and when they are emitted are determined on the basis of algorithms written in the internal firmware. Thos algorithms determine which functions the assembly carries out. The more information is available in regard to the system as a whole, the broader the basis upon which decisions can be made.<br />
<br />
To make it possible for the electronic assemblies in a system to work together and exchange internal information or commands they will have to be connected with each other by way of a field bus.<br />
<br />
Pursuant to the adoption of the EN 81 standard, all newly installed or modernized elevators must have a telephone connection for emergency calls. This line is, however, usually reserved exclusively for use by the emergency calling device. Thus, for example, a door control device cannot use the telephone connection already on hand to send along malfunction reports or maintenance information. The emergency call unit could, indeed, transmit such communications but it knows nothing about the internal fault in the door control device.<br />
<br />
A technician will learn about the malfunctioning device only when a passenger – possibly one who is trapped – calls in a complaint. The technician must then go immediately to the site and troubleshoot the elevator there.<br />
<br />
This situation would be improved if the door controller and the emergency call unit were able to communicate with each other.<br />
<br />
==Definition==<br />
<br />
Communication [Latin: communicare] sharing, notifying, allowing participation, doing something together, joining<br />
<br />
==Interruptions in communication==<br />
<br />
During communication activities an encoded message with a defined character set is transported through a certain medium from a sender to a receiver; this is followed by encoded feedback to the sender. Communication transpires within a certain context.<br />
<br />
A variety of external influences can interfere with communication. This makes it necessary to integrate mechanisms that can recognize a message error and, if necessary cause that message to be sent again.<br />
<br />
===Elements in communication===<br />
<br />
In order to be able to communicate with each other, we require:<br />
*a verbal or nonverbal language or protocol<br />
*a transmission medium or communication channel<br />
*communication rules<br />
*perhaps a discussion leader/moderator/master<br />
<br />
===Types of communication===<br />
<br />
Depending on the number of elements participating in communications, one differentiates among the following communication types.<br />
<br />
====Monolog====<br />
One device or participant sends messages and at least one participant receives the messages and emits a response.<br />
<br />
====Dialog====<br />
Two participants send encoded messages to each other.<br />
<br />
====Multi-master communications====<br />
Many participants send messages to each other.<br />
This latter type of communication, among humans, has proven to be impractical since too many messages would be disrupted.<br />
<br />
Multi-master communications are possible in technical systems without the messages being corrupted. The principle of prioritized messages will be used here, for instance.<br />
<br />
In this type of communication several units can each start sending a message through a transmission medium. An identifier included as a prefix to the message is used to determine which message has the highest priority. The message with the highest priority will be sent, right after the identifi er, without delay. Lower-priority messages will be postponed.<br />
<br />
This procedure prevents message corruption. Real-time communications are possible.<br />
<br />
==Technology in the elevator==<br />
<br />
''Survey of various bus systems''<br />
<br />
To enable electronic devices in an elevator to communicate with each other, a field bus will have to be provided to connect them.<br />
<br />
There are currently several field bus systems – with varying technical properties – being used widely in the industry. Thus there are low-bandwidth systems that can transmit just a few messages over great distances. Others, with great bandwidth, can transmit large volumes of data across short distances. Depending on the needs of the system in which a field bus system is to be employed, the designer will select the field bus with the best properties for the particular application.<br />
<br />
{|<br />
|Designation<br />
|Uses<br />
|-<br />
|Bacnet<br />
|Building automation<br />
|-<br />
|CAN<br />
|Vehicles, robots, machines<br />
|-<br />
|EIB<br />
|Building automation<br />
|-<br />
|Ethernet<br />
|Internet, building automation, production systems<br />
|-<br />
|Interbus<br />
|Production systems<br />
|-<br />
|LON<br />
|Building automation<br />
|-<br />
|Profibus<br />
|Production systems<br />
|-<br />
|RS485<br />
|Proprietary systems<br />
|}<br />
<br />
''Advantages and disadvantages''<br />
<br />
After an extensive analysis of the various systems, many European components manufacturers have decided on the CAN concept as the field bus to be used in elevators.<br />
<br />
The primary criteria to be satisfied are the ability to function in real-time, safety, speed, freedom of licensing requirements,<br />
autonomy from any given manufacturer, price and widespread use.<br />
<br />
Basing on the CAN bus, a joint language was developed for standardized communication. The designations CANopen-Lift and CANopen CiA-417 are used.<br />
<br />
==The CANopen-Lift application profile==<br />
<br />
Work on the application profile commenced in 2001. In the summer of 2003 Version 1.0 was adopted and in October of that same year prototypes of the first products were to be seen at the Interlift.<br />
<br />
The application profile is designated CANopen-Lift or CiA 417 V2.0. The profile describes an application with<br />
*a group of eight elevators,<br />
*254 landings<br />
*and 4 doors per car.<br />
<br />
Moreover, all the devices that can be used within this application are defined as “virtual devices”. The functions of the “virtual devices” are then described, along with all the messages these devices can generate and/or receive.<br />
<br />
Associated with the profile are various regulations and supplementary recommendations. Thus, for instance, various plug connectors are recommended for use with elevator components. Pin assignment for the plugs is, however, prescribed and mandatory. It is also recommended that the device interfaces be equipped with a status indicator LED. If an LED is present, then its blinking patterns are standardized to signify various status reports.<br />
<br />
There are also recommendations for the colors of the conductors used in the bus line, for the structure of the topology for networking the components, for the assignment of node IDs, for the baud rate or auto-baud functions, software updating procedures in the components and much, much more.<br />
<br />
This insures on the one hand that the components using the bus are as compatible as possible and that maximum plug-and-play capability will be achieved. On the other hand, the component manufacturers and elevator engineers enjoy great flexibility in designing individual and unique features. Standardization is referenced exclusively to the communications among components attached to the system bus. The functions of the devices are not described. This continues to be within the domain of the manufacturer’s know-how.<br />
<br />
==The principle of virtual devices==<br />
<br />
Virtual devices are abstract software objects that represent a real-world device (e.g. an absolute value transmitter or a door controller). The concept of virtual devices is used to depict various types of devices, all in the same class of devices, on a common<br />
interface. In application profiles there are, as a rule, no master/slave communications in regard to the process data objects (PDO). The CiA-417 CANopen application profi le for elevator controls, for example, defines direct PDO connections that link the elevator door and the door controls.<br />
<br />
The normal case is that only virtual devices are specified in application profiles. This lets the equipment manufacturer decide which virtual device is to be implemented in a physical device. Here is an example to further illustrate the principle behind the<br />
virtual devices. Two manufacturers of position sensors equip their devices with a CANopen-Lift interface. One manufacturer’s<br />
system is a rotary encoder that incrementally resolves a change in angle. If the circumference of the driving gear, sprocket or<br />
sheave is known, then the change in position can be calculated. The second manufacturer develops a linear encoder in which<br />
the lag time of a pulse is used to determine directly the distance to a reference point.<br />
<br />
Both manufacturers implement a virtual device, the “position unit”, in their encoders and thus both units impress the same information on the bus: the position of the car, its velocity and, as an option, its acceleration, as well.<br />
<br />
From the viewpoint of the overall elevator system, how position is determined is of no importance. The controls, the frequency inverter, diagnostics tools and displays need only know the position and velocity values for the car.<br />
<br />
The virtual devices principle yields a number of advantages. For one thing, a rotary encoder can be substituted for a linear encoder should the latter not be available for delivery or if technical considerations require this change. Additionally, other devices need know nothing about the nature or technical properties of the encoder. They can nonetheless access and use the position information. A display manufacturer, for instance, will program the display so that the position information from a virtual device – the “position unit” – will be shown. If virtual a device of this type is present in the elevator, then the position data can be shown without the display manufacturer ever having to see the encoder.<br />
<br />
This makes it possible to assemble widely varying systems, the topologies of which are not determined by the application profile, since bridges and gateways can quite easily be developed. The elevator manufacturer, for instance, can use separate CANopen networks for car control and for the control panels inside the hoist-way.<br />
<br />
==Diagnostics==<br />
<br />
One major problem associated with bus systems in the past was the capability to carry out diagnostics work. Here the application<br />
profile offers a wide variety of possibilities.<br />
<br />
Firstly, one can naturally equip each device with a status LED or a display, as is typical for conventional systems. The disadvantage here is, however, that an integrated display involves costs and the technician has to be present on site, at the device, in order to read the information shown in the display. <br />
<br />
Furthermore, one can use the “virtual console” defined in CANopen-Lift. The virtual console defines a procedure a device uses to apply the content of its own display to the system bus and how this data can be displayed by other devices. Moreover, it is possible, with the help of a control command, to navigate through the menus from other units. Thus not only the content of the frequency inverter display can be depicted in the controls, as is possible in the DCP protocol. Additionally, the menu of each individual device can be shown at every other device equipped with a display. This need not necessarily be an elevator component. This technology also makes it possible to show the menu on a cell phone that accesses the CAN bus via Bluetooth, for instance. It may also be shown using diagnostics software running on a laptop.<br />
<br />
If the technician has a laptop, then there are far better diagnostic possibilities. Since the parameter sets are standardized, all<br />
the devices connected to the bus can be parameterized with a single, uniform tool.<br />
<br />
==Diagnoses with a laptop==<br />
<br />
If a laptop is available for diagnosis and configuration work, then there are many and very convenient options to choose from.<br />
<br />
Given the fact that the communications and the parameters sets for all the devices are standardized, it is possible, with a single<br />
software program, to parameterize all the devices in an elevator. One universal-use configuration tool of this type is the<br />
“CANwizard®” software, which is already being used by many manufacturers.<br />
<br />
===Assigning parameters===<br />
<br />
Once the laptop has been joined with the system bus by way of an adapter available on the commercial market, the CANwizard® scans the bus and reads out the parameters for all the devices connected to it. If the operator has the proper authorization, then the parameters can be changed and written back into the device.<br />
<br />
Additionally, a complete image of the elevator, including all the parameters, can be archived. The parameter data records in storage can be used to configure lifts of a similar design or to facilitate configuration of a replacement part. Additionally, the<br />
parameter data records can be used by a system’s operator or by a certified surveillance agency to detect manipulations in<br />
parameters. This makes it simple to determine whether any relevant parameters have been changed after commissioning and acceptance.<br />
<br />
===Firmware update===<br />
<br />
Programs are never entirely error-free and today the functions of any given assembly are determined by internal firmware. This frequently makes it necessary to update the software in an assembly.<br />
<br />
The CANwizard® makes it possible to execute a software update, using a standardized procedure, for one or more assemblies, regardless of which manufacturer built the units. This can be used with modern LCD displays, for example, to change the depiction to match current needs, and that can be done with just a few mouse clicks. It would also be possible to update audio files in annunciator modules.<br />
<br />
===Real-time monitoring===<br />
<br />
One major problem with technical systems networked using a proprietary bus system is the extent to which it supports diagnostics activities. The technician on site has to rely on the status reports issued by a just few assemblies.<br />
<br />
Thanks to the standardization of the process and the fault messages in the bus, a single tool can be used to diagnose all the<br />
components and the system as a whole. All the process messages – such as “Low-priority hallway call in floor 8 at door A of<br />
elevator 1” or “Limit switch A, elevator 1, open” or “Position 18.2356 m, velocity 0.832 m/s, acceleration 0 m/s” – can be<br />
depicted in plain text, in real time, and stored in a log file together with a time stamp. Thus the technician, working from<br />
just a single location, can obtain status information on all the devices and the entire process. Elevator functions taking place<br />
sequentially can be examined using plain text or graphs. This is an option that would not be possible without a standardized<br />
procedure.<br />
<br />
===Management functions for EDS files===<br />
<br />
An electronic data log is associated with each CANopen device and is stored in EDS – electronic data sheet – files. These files describe, in a standardized text format, both the most important parameters for the device as well as physical parameters such as the baud rates the device supports. Configuration tools can read EDS files and, with their help, can also communicate with previously unknown devices and possibly parameterize them.<br />
<br />
CANwizard® provides an EDS library containing the EDS files for all the known CANopen-Lift devices. Additional devices can be added using an import function.<br />
<br />
===Expansion===<br />
<br />
No software program can ever take account of every conceivable function and particularly in the case of software not associated with a given manufacturer it is not desirable that competitors have access to internal know-how concerning certain functions. That is why it has become customary to equip programs with interfaces to accept add-ons that expand the program’s functions.<br />
<br />
CANwizard® is fitted with an interface like this and lets manufacturers write their own add-ons in order to parameterize their own devices.<br />
<br />
===Staying up to date===<br />
<br />
It is very important to be able to regularly modify the scope of a diagnostics tool’s functions to reflect current standards and the<br />
functions of devices on the market. A continuous development process for CANwizard® ensures this. Employing an online update function, users can be sure they always have the latest version of the software.<br />
<br />
A major release for the software is issued when each new version of the standard is published. It takes account of changes in the standard.<br />
<br />
===Openness===<br />
<br />
The developers of tools intended to work with devices made by any of a number of manufacturers has to build confidence in their products. One vital factor here is communicating openly with users. That includes providing a continuously updated history of the software, accessible for every user, and providing information on expansions of functions and corrections of errors.<br />
<br />
===Not associated with any manufacturer===<br />
<br />
CANwizard® is available to every engineer and developer of CANopen devices and is also employed by universities and manufacturers<br />
in production process.<br />
<br />
===Remote diagnosis===<br />
<br />
In an age when the Internet is ubiquitous, it quite natural to offer this functionality not just on site, at the elevator, but also at remote locations.<br />
<br />
If the elevator is linked to the Internet via a suitable gateway, then all the functions can be executed remotely as soon as the<br />
PC is connected with the Internet and authorization has been verified.<br />
<br />
==Standardization==<br />
<br />
Some organizational questions had to be clarified when standardization work commenced. The objective was to define a standard valid around the world, one that was available for use by everyone and one that could not be dominated by any single manufacturer or professional association. The committee members were also supposed to have a background in active standardization work and experience in such efforts. They were to share insights and lend support in the work.<br />
<br />
All these conditions were satisfied by the CAN in Automation (CiA) organization. This impartial, non-profit organization has its head offices in Nürnberg and locations in the most important markets around the world.<br />
<br />
The CiA takes responsibility for standardization work, organizes training sessions on CANopen, certifies devices, disseminates<br />
information at trade fairs and does much, much more.<br />
<br />
Work for elevators is done in two areas within CiA. The “Special Interest Group Lift” (SIG Lift) is made up of developers who define new functions, work out the protocol, and test and certify devices.<br />
<br />
The “Marketing Group Lift” provides information about the protocol and the devices on the market. It was under the supervision of the MG Lift that a demonstration unit was built to show the functionality of the profile and the assemblies. Additionally, MG Lift drafts brochures and flyers and organizes trade fair presentations and road shows.<br />
<br />
In order to standardize a non-proprietary protocol in this fastmoving world, and always keeping that protocol up to date, it is necessary for the following conditions to be fulfilled for standardization work:<br />
*Speed<br />
*Transparency<br />
*Openness<br />
<br />
Several platforms are available in the Internet intended to achieve this. On the one hand the CiA makes a content management system available on its Web site, by way of which the members can exchange information, both internally and externally.<br />
<br />
On the other hand, the Web site at www.CANopen-Lift.org maintains an open Wiki where recommendations for new products, application notes and new functions can be discussed.<br />
<br />
The members of SIG Lift meet twice a year to expand the specifications and – usually in a lively exchange of information – to discuss new functions that are to be included in the specifications in the future.<br />
<br />
==Plug Fests==<br />
<br />
So much for the theory involved in preparing a standard. But at some point it is necessary to develop the corresponding devices<br />
and examine interoperability.<br />
<br />
To check device interoperability, regular meetings are held in the framework of SIG Lift (Plug Fests), in which – using checklists<br />
– the compatibility of devices in relationship to the standard and their functionality with other devices are examined. If a device successfully satisfies all the items in a checklist, then this is something like a certificate as per the standard at that particular point in time.<br />
<br />
Stress tests are also conducted at the Plug Fests. These inspect, for example, the behavior of devices at maximum permissible bus lengths or at maximum bus loading. These tests are very elaborate and it would be quite difficult for any individual manufacturer<br />
to conduct them.<br />
<br />
The Plug Fests are held several times a year, but one would not want to wait until the next Plug Fest to market a new software<br />
version with only a minor change.<br />
<br />
That is why Böhnke + Partner connected several control systems, via a gateway, with the Internet. After installing the appropriate<br />
driver, any manufacturer can connect a CANopen-Lift elevator device – via the Internet – with these controls and examine the functionality of the assemblies.<br />
<br />
==Perspectives==<br />
<br />
Where are these standardized specifications for inter-component communications in an elevator likely to lead us? We believe that in the future all devices will be fitted with standardized bus connectors. These devices can be analyzed and parameterized using all-purpose diagnostics tools.<br />
<br />
Standardized networking in and among elevators also simplifies linkage to the building control center and to remote diagnosis capabilities via the Internet.<br />
<br />
The capability to access many internal parameters in the individual devices gives rise to many new functions that, without this standard, would be very complex or not feasible at all.<br />
<br />
Elevator safety is increased since redundancies arise and devices can monitor each other. As of 2005 PESSRAL (Programmable Electronic System in Safety Related Applications) has been an annex to EN 81 1/2. In PESSRAL the safety-critical sensors and limit switches are replaced with electronic assemblies that offer far greater functionality and thus enhance elevator safety. If these systems are supposed to trade information, then they will have to be interconnected with a safe, non-proprietary bus. “CANopen Safety” makes available a standard used around the world.<br />
<br />
Again and again new field bus systems appear on the market while others disappear. Systems based on fiber optics or radio technologies might well come on the scene in the future. At present some larger manufactures are attempting to render Ethernet-based systems suitable for real-time use and to establish them as field bus systems. These systems are not compatible with each other and are usually forced onto the market only by a single, mighty manufacturer. The most “open” system is Powerlink, which can run on standard Ethernet hardware. Here, again, there are still many problems to be solved. Once the hardware and message transport layers have been clarified, the parameter sets for devices and applications will still have to be defined. There is an agreement between Powerlink and “CAN in Automation” that the object dictionary for devices and applications may also be used for Powerlink. Anyone who already uses CANopen-Lift today is fully equipped for the future.<br />
<br />
A further simplification arises almost coincidentally from standardization. Many elevator and component manufacturers use different designations or names for the same thing. Defining messages and parameter sets encourages the use of uniform terminology. Operating levels and menu prompts in devices made by different manufacturers are becoming more similar. Service technicians on site and the employees at certified surveillance agencies thus find it easier to deal with differing systems.<br />
<br />
==Sources==<br />
<br />
The following is a brief listing of sources that may be used to delve further into the subject:<br />
* BÖHNKE + PARTNER GmbH www.boehnkepartner.de<br />
* CAN in Automation Organization www.can-cia.org<br />
* CANopen-Lift-Wiki www.CANopen-Lift.org<br />
* Configuration software www.CANwizard.de<br />
* Information on Powerlink de.wikipedia.org/wiki/Ethernet_Powerlink<br />
<br />
[[category:press]]<br />
[[category:PESSRAL]]</div>Jan.Merkelbaghttps://en.canopen-lift.org/index.php?title=Lift_by_Wire_-_LiftReport_2/2002&diff=3011Lift by Wire - LiftReport 2/20022012-09-28T14:12:15Z<p>Jan.Merkelbag: </p>
<hr />
<div>[[de:Lift_by_Wire_-_Liftreport_1/2002]]<br />
'''Source: LiftReport 1/2002''' ''by [[Jörg Hellmich]] ([[Böhnke & Partner GmbH |BÖHNKE + PARTNER GmbH Steuerungssysteme]], now c/o [http://elfin.de elfin.de])''<br />
<br />
The Interlift fair in Augsburg showed us once again that the trend in the lift industry is moving towards networking components by using standard Bus systems. So, most of today’s firms offer their component parts with a CAN or LON connection.<br />
<br />
Parallel to hardware interface compatibility there were first talks at the fair about standardising protocols on the CAN Bus basis to enable the interconnection of components from various manufacturers to make up a complete lift system. In the meantime a group of component manufacturers have declared themselves willing to take up this task under the patronage of the CIA ([http://www.can-cia.org Can in Automation]) organisation. It is their goal is to generate a profile for the lift industry based on CANopen which is to enable Plug- and- Play facilities for the various manufacturer’s components as well as uniform diagnosis systems.<br />
The future still sees implementation of the failsafe system CANopen Safety, whereby all limit switches in the shaft and the complete safety circuit, in it’s present form, could become superfluous. It would then be feasible that, for the first time since Mr. Otis introduced the catching facility, this would no longer be triggered mechanically but electrically; i.e. when the encoder or converter determines the cabin is moving too fast.<br />
<br />
What is ”Drive by Wire” to the automotive industry will become Lift by Wire in the lift industry!<br />
<br />
[[Category:Marketing]]<br />
[[Category:Press]]</div>Jan.Merkelbaghttps://en.canopen-lift.org/index.php?title=Hamburg_church_with_a_view_-_CANopen_lifts_visitors&diff=3010Hamburg church with a view - CANopen lifts visitors2012-09-28T14:09:38Z<p>Jan.Merkelbag: </p>
<hr />
<div>[[de:Hamburger Kirche mit Weitsicht - Besucher des CANopen Lifts]]<br />
''By Monika Mack, CAN in Automation [http://www.can-cia.org/lift (www.can-cia.org/lift)]''<br />
<br />
At the southern end of Hamburg stand the remains of the St. Nikolai church. The gothic style church was built in the 19th century and was an architectural masterpiece of its time. It is one of the few remaining landmarks from prewar Hamburg and after heavy raids by Allied forces in 1943 it was virtually the only structure left standing in the city center. The church was left blackened with soot and partially destroyed; the ruins were left standing in order to serve as a memorial to the victims of persecution in the Third Reich. The third highest church tower in Germany spirals up to an impressive 147 m height. In 2001 the church was restored and a platform in 75 m height was repaired to enable visitors to enjoy the splendid view over the city and port of Hamburg.<br />
<br />
The lift that transports visitors up to the platform at a speed of 2.5 m/s is networked completely via the CANopen Lift profile CiA-417. [[Böhnke & Partner GmbH |Böhnke and Partner]] [http://www.boehnkepartner.de/ (www.boehnkepartner.de)] supplied the bp306 control unit with two CANopen interfaces.<br />
<br />
The network consists of two separate CANopen sub-networks. One of them leads into the lift cabin, where a CLK-01 evaluates the cabin’s I/Os. The CLK-01 I/O modules provide signal inputs and outputs and calls in the lift cabin and control the display to indicate the lift position. They provide the CiA-417 virtual devices “input panel unit”, “output panel unit”, and “door unit”. This line also incorporates the CAN absolute encoder by Baumer IVO [http://www.baumerivo.com (www.baumerivo.com)]. It is used to position the cabin in the church tower. It transmits PDOs cyclically every 20 ms. All other PDOs in the networks are event-triggered, the bus load is approximately 5%. Further CLK-01 units are connected via repeaters by Ixxat [http://www.ixxat.de (www.ixxat.de)]; these I/O modules control LED dot-matrix displays, which visualize the position information of the cabin. They receive the position information from the absolute encoder, which transmits its data to the network. A gateway connects the two CANopen sub-networks together at the CDG-01 diagnostic gateway. Located on the gateway is a modem, which enables the connection to a remote service center. The service center can thus diagnose and parameterize all devices on the two CANopen busses via this modem with the help of the CANwizard software.<br />
<br />
Leading from the main control unit to the floors is the second CANopen sub-network. Here the CAP-01 floor panels process lift calls from the floors and also indicate the lift’s position.<br />
<br />
'''CANopen lifts will dominate the market'''<br />
<br />
According to Jörg Hellmich, Development Engineer at [[Böhnke & Partner GmbH |Böhnke and Partner]] (now c/o [http://elfin.de elfin.de]), more than 150 lifts with CANopen components have been sold since 2003. Approximately 70% of the systems used the CANopen network just for connecting the panels, the other 30% of lift systems were networked entirely via CANopen, tendency increasing he says. Future developments, he estimates, will see a complete abandonment of the currently common system control and an enormous growth of CANopen systems, in which everything is networked via the application profile for lifts. In case of the St. Nikolai church lift, there were no problems installing the network communication at all. Thanks to the application profile CiA-417 the system components are plug-and-play capable. The only adjusting that had to be done was the encoder offset values, which had to be set for the cabin position and the position data of the individual floors. This took all of about three minutes. Software tool used for the system configuration was the CANwizard, which is a configuration software that allows configuring CiA-417 devices without specific CANopen know how, according to the manufacturer.<br />
<br />
The lift builders decided to use a CANopen network for the lift installation because it is the only real-time capable standardized protocol in the lift industry. It is multi-master capable, provides robust and error-free communication, and the micro-controllers used are available inexpensively due to their million-fold usage in automobiles. Jörg Hellmich is confident that CANopen is the way of the future for lift builders. According to him, those that use it now have a strategic advantage on the market. He also appreciates the possibility of actively participating in the further development of the application profile through his CiA-membership. <br />
<br />
''Source: CAN Newsletter Special Lift 2005 [http://www.can-cia.org/newsletter (www.can-cia.org/newsletter)]''</div>Jan.Merkelbaghttps://en.canopen-lift.org/index.php?title=Hamburg_church_with_a_view_-_CANopen_lifts_visitors&diff=3009Hamburg church with a view - CANopen lifts visitors2012-09-28T14:09:17Z<p>Jan.Merkelbag: </p>
<hr />
<div>[[de:Hamburger Kirche mit Weitsicht - Besucher des CANopen Lifts]]<br />
''By Monika Mack, CAN in Automation [http://www.can-cia.org/lift (www.can-cia.org/lift)]''<br />
<br />
At the southern end of Hamburg stand the remains of the St. Nikolai church. The gothic style church was built in the 19th century and was an architectural masterpiece of its time. It is one of the few remaining landmarks from prewar Hamburg and after heavy raids by Allied forces in 1943 it was virtually the only structure left standing in the city center. The church was left blackened with soot and partially destroyed; the ruins were left standing in order to serve as a memorial to the victims of persecution in the Third Reich. The third highest church tower in Germany spirals up to an impressive 147 m height. In 2001 the church was restored and a platform in 75 m height was repaired to enable visitors to enjoy the splendid view over the city and port of Hamburg.<br />
<br />
The lift that transports visitors up to the platform at a speed of 2.5 m/s is networked completely via the CANopen Lift profile CiA-417. [[Böhnke & Partner GmbH |Böhnke and Partner]] [http://www.boehnkepartner.de/ (www.boehnkepartner.de)] supplied the bp306 control unit with two CANopen interfaces.<br />
<br />
The network consists of two separate CANopen sub-networks. One of them leads into the lift cabin, where a CLK-01 evaluates the cabin’s I/Os. The CLK-01 I/O modules provide signal inputs and outputs and calls in the lift cabin and control the display to indicate the lift position. They provide the CiA-417 virtual devices “input panel unit”, “output panel unit”, and “door unit”. This line also incorporates the CAN absolute encoder by Baumer IVO [http://www.baumerivo.com (www.baumerivo.com)]. It is used to position the cabin in the church tower. It transmits PDOs cyclically every 20 ms. All other PDOs in the networks are event-triggered, the bus load is approximately 5%. Further CLK-01 units are connected via repeaters by Ixxat [http://www.ixxat.de (www.ixxat.de)]; these I/O modules control LED dot-matrix displays, which visualize the position information of the cabin. They receive the position information from the absolute encoder, which transmits its data to the network. A gateway connects the two CANopen sub-networks together at the CDG-01 diagnostic gateway. Located on the gateway is a modem, which enables the connection to a remote service center. The service center can thus diagnose and parameterize all devices on the two CANopen busses via this modem with the help of the CANwizard software.<br />
<br />
Leading from the main control unit to the floors is the second CANopen sub-network. Here the CAP-01 floor panels process lift calls from the floors and also indicate the lift’s position.<br />
<br />
'''CANopen lifts will dominate the market'''<br />
<br />
According to Jörg Hellmich, Development Engineer at [[Böhnke & Partner GmbH |Böhnke and Partner]] (c/o [http://elfin.de elfin.de]), more than 150 lifts with CANopen components have been sold since 2003. Approximately 70% of the systems used the CANopen network just for connecting the panels, the other 30% of lift systems were networked entirely via CANopen, tendency increasing he says. Future developments, he estimates, will see a complete abandonment of the currently common system control and an enormous growth of CANopen systems, in which everything is networked via the application profile for lifts. In case of the St. Nikolai church lift, there were no problems installing the network communication at all. Thanks to the application profile CiA-417 the system components are plug-and-play capable. The only adjusting that had to be done was the encoder offset values, which had to be set for the cabin position and the position data of the individual floors. This took all of about three minutes. Software tool used for the system configuration was the CANwizard, which is a configuration software that allows configuring CiA-417 devices without specific CANopen know how, according to the manufacturer.<br />
<br />
The lift builders decided to use a CANopen network for the lift installation because it is the only real-time capable standardized protocol in the lift industry. It is multi-master capable, provides robust and error-free communication, and the micro-controllers used are available inexpensively due to their million-fold usage in automobiles. Jörg Hellmich is confident that CANopen is the way of the future for lift builders. According to him, those that use it now have a strategic advantage on the market. He also appreciates the possibility of actively participating in the further development of the application profile through his CiA-membership. <br />
<br />
''Source: CAN Newsletter Special Lift 2005 [http://www.can-cia.org/newsletter (www.can-cia.org/newsletter)]''</div>Jan.Merkelbaghttps://en.canopen-lift.org/index.php?title=Webmin&diff=3008Webmin2012-09-28T14:05:27Z<p>Jan.Merkelbag: typos and corrections</p>
<hr />
<div>[[de:Webmin]]<br />
[[Image:Webmin.jpg|right|Webmin]]<br />
The webmin of this wiki is [[Jörg Hellmich]]. He rents the server for this wiki and is responsible for its administration. Furthermore he ensures that only content belonging to the topic ''CANopen in a lift'' is part of this wiki. <br />
You can find milestones of this wiki's development in the article '''[[Wiki]]'''.<br />
<br />
If you have any questions or suggestions concerning this wiki, please send an e-mail to webmin@CANopen-Lift.org.</div>Jan.Merkelbaghttps://en.canopen-lift.org/index.php?title=Current_state&diff=3007Current state2012-09-28T09:17:41Z<p>Jan.Merkelbag: translation of http://de.canopen-lift.org/wiki/Aktueller_Stand finished</p>
<hr />
<div>[[de:Aktueller_Stand]]<br />
[[File:Hauptbahnhof-Berlin-2.jpg|right|350px|Central station of Berlin]]<br />
<br />
The development of the open standard CANopen CiA-417 was begun in year 2001. The present version 2.0 of the specification has existed since December 2009 and is supported by many products. These products are tested for compatibility and interoperability at the regularly [[CANopen_Lift_Plugfest|PlugFests]]. <br />
<br />
Almost a year after its release version 2.0 can be declared stable. Many products implemented the features and have been running successfully in the field. Therefore the [[SIG_Lift|SIG Lift]] concluded at the [[SIG_Lift#2010-09-07|meeting on 7th September 2010]] that the version 2.1 should be transitioned into the Draft Standard (DS) and offered as a free download. The publishing of this version is expected at the beginning of year 2011. <br />
<br />
Meanwhile the standard was extended by many features and is close to its passing of version 2.1. This version provides functions for measuring the energy consumption of lifts, control commands for reduction of the energy use of components, functions for accelerating the start and stop of lifts and [[CAN-statisics-counter|extensions for the diagnose of networks]].<br />
<br />
[[File:Flyer_CANopen-Lift_2009-1.jpg|left|200px|Flyer CANopen-Lift 2009]]<br />
<br />
The marketing group ([[Marketing_Group_Lift|SMG Lift]]) organised multiple trade-fair appearances, constructed the [[CANopen-Lift_Demonstrator|CANopen-Lift Demonstrator]] and worked out a flyer about the standart CANopen-Lift. Currently the trade-fair appearances for Mailand 2010 and the Interlift 2011 as well as the exhibition in Heilbronn + Schwelm 2011 are prepared. Furthermore a road show for the springtime of 2011 in Lindau, Berlin and Düsseldorf is planned. <br />
<br />
The list of manufacturers for CANopen-Lift products is becomming longer and more international. By now, CANopen-Lift products are produced in Germany, Great Britain, France, Sweden und Switzerland. In Australia, India, Italy and Spain are more products developed. <br />
<br />
For most of the products are already alternatives by multiple manufacturers available which decreases the costs of the offered modules. Even before the Interlift 2011 three additional control systems, two inverters, tableaus and displays are offered. <br />
<br />
The [[reference_list|reference list]] shows that the offered systems have placed themselves firmly on the market.</div>Jan.Merkelbaghttps://en.canopen-lift.org/index.php?title=File:Flyer_CANopen-Lift_2009-1.jpg&diff=3006File:Flyer CANopen-Lift 2009-1.jpg2012-09-28T08:45:48Z<p>Jan.Merkelbag: Flyer CANopen-Lift January 2009</p>
<hr />
<div>Flyer CANopen-Lift January 2009</div>Jan.Merkelbaghttps://en.canopen-lift.org/index.php?title=File:Hauptbahnhof-Berlin-2.jpg&diff=3005File:Hauptbahnhof-Berlin-2.jpg2012-09-28T08:26:43Z<p>Jan.Merkelbag: Hauptbahnhof Berlin - 2008 - CC-by-SA 3.0</p>
<hr />
<div>Hauptbahnhof Berlin - 2008 - CC-by-SA 3.0</div>Jan.Merkelbaghttps://en.canopen-lift.org/index.php?title=Current_state&diff=3004Current state2012-09-28T08:24:07Z<p>Jan.Merkelbag: Created page with "de:Aktueller_Stand Central station of Berlin The development of the open standard CANopen CiA-417 was begun in year 2001. T..."</p>
<hr />
<div>[[de:Aktueller_Stand]]<br />
[[File:Hauptbahnhof-Berlin-2.jpg|right|350px|Central station of Berlin]]<br />
<br />
The development of the open standard CANopen CiA-417 was begun in year 2001. The present version 2.0 of the specification has existed since December 2009 and is supported by many products. These products are tested for compatibility and interoperability at the regularly [[CANopen_Lift_Plugfest|PlugFests]]. <br />
<br />
Almost a year after its release version 2.0 can be declared stable. Many products implemented the features and have been running successfully in the field. Therefore the [[SIG_Lift|SIG Lift]] concluded at the [[SIG_Lift#2010-09-07|meeting on 7th September 2010]] that the version 2.1 should be transitioned into the Draft Standard (DS) and offered as a free download. The publishing of this version is expected at the beginning of year 2011. <br />
<br />
Meanwhile the standard was extended by many features and is close to its passing of version 2.1. This version provides functions for measuring the energy consumption of lifts, control commands for reduction of the energy use of components, functions vor accelerating the starting and stopping of lifts and extensions for the diagnose of networks.</div>Jan.Merkelbaghttps://en.canopen-lift.org/index.php?title=Node-IDs&diff=3002Node-IDs2012-09-27T13:30:47Z<p>Jan.Merkelbag: /* Topology: 2 seperate busses for car and shaft */</p>
<hr />
<div>[[de:Node-IDs]]<br />
The node-IDs depend on the CANopen network's topology. Here you can see a recommendation for node-IDs in CANopen-lift networks. <br />
<br />
= Topology: 2 seperate busses for car and shaft =<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="5"<br />
|+ Node-ID recommendation:<br />
! width="10%" bgcolor="#F0F0F0" | Node-ID <br /> (dez)<br />
! width="45%" bgcolor="#F0F0F0" | CAN1 <br> local bus<br />
! width="45%" bgcolor="#F0F0F0" | CAN2 <br> shaft/group bus<br />
|-<br />
| align="center" | 1<br />
| lift controller (Call/car drive/door controller, NMT “flying” master)<br />
| lift controller G1 (Call/car drive/door controller lift 1, NMT “flying” master)<br />
|-<br />
| align="center" | 2<br />
| drive (frequency inverter, car drive unit)<br />
| lift controller G2 (Call/car drive/door controller lift 2, NMT “flying” master)<br />
|-<br />
| align="center" | 3<br />
| ''reserved''<br />
| lift controller G3 (Call/car drive/door controller lift 3, NMT “flying” master)<br />
|-<br />
| align="center" | 4<br />
| encoder/position system 1 (Car position unit 1)<br />
| lift controller G4 (Call/car drive/door controller lift 4, NMT “flying” master)<br />
|-<br />
| align="center" | 5<br />
| encoder/position system 2 (Car position unit 2)<br />
| lift controller G5 (Call/car drive/door controller lift 5, NMT “flying” master)<br />
|-<br />
| align="center" | 6<br />
| ''reserved''<br />
| lift controller G6 (Call/car drive/door controller lift 6, NMT “flying” master)<br />
|-<br />
| align="center" | 7<br />
| door drive unit 1 (door A)<br />
| lift controller G7 (Call/car drive/door controller lift 7, NMT “flying” master)<br />
|-<br />
| align="center" | 8<br />
| door drive unit 2 (door B)<br />
| lift controller G8 (Call/car drive/door controller lift 8, NMT “flying” master)<br />
|-<br />
| align="center" | 9<br />
| door drive unit 3 (door C)<br />
| gateway/repeater (Remote data transmission unit 1)<br />
|-<br />
| align="center" | 10<br />
| gateway (CDG-01)<br />
| gateway/repeater 2 (Remote data transmission unit 2)<br />
|-<br />
| align="center" | 11<br />
| ''reserved (e.g. Wago-I/O)''<br />
| gateway/repeater 3 (Remote data transmission unit 3)<br />
|-<br />
| align="center" | 12<br />
| ''reserved (inspection box)''<br />
| gateway/repeater 4 (Remote data transmission unit 4)<br />
|-<br />
| align="center" | 13<br />
| weight measurement unit<br />
| gateway/repeater 5 (Remote data transmission unit 5)<br />
|-<br />
| align="center" | 14<br />
| ''energy measurent unit''<br />
| gateway/repeater 6 (Remote data transmission unit 6)<br />
|-<br />
| align="center" | 15<br />
| ''reserved (emergency call device)''<br />
| gateway/repeater 7 (Remote data transmission unit 7)<br />
|-<br />
| align="center" | 16<br />
| car call panel node 1 (Car I/O panel 1)<br />
| gateway/repeater 8 (Remote data transmission unit 8)<br />
|-<br />
| align="center" | 17<br />
| car call panel node 2 (Car I/O panel 2)<br />
| &nbsp;<br />
|-<br />
| align="center" | 18<br />
| car call panel node 3 (Car I/O panel 3)<br />
| &nbsp;<br />
|-<br />
| align="center" | 19<br />
| car call panel node 4 (Car I/O panel 4)<br />
| &nbsp;<br />
|-<br />
| align="center" | 20<br />
| car call panel node 5 (Car I/O panel 5)<br />
| &nbsp;<br />
|-<br />
| align="center" | 21 - 84<br />
| colspan="2" | floor I/O panel 1 to 64<br />
|-<br />
| align="center" | 85 - 119<br />
| colspan="2" | free<br />
|-<br />
| align="center" | 120 - 124<br />
| colspan="2" | ''reserved''<br />
|-<br />
| align="center" | 125<br />
| colspan="2" | default setting of a non-parameterized device and [[wpde:Daisy chain|daisy-chain systems]]<br />
|-<br />
| align="center" | 126<br />
| colspan="2" | [[firmware update|firmware update boot loader]]<br />
|-<br />
| align="center" | 127 <br />
| colspan="2" | diagnostic tool<br />
|}<br />
<br />
[[category:recommedations]]</div>Jan.Merkelbaghttps://en.canopen-lift.org/index.php?title=Node-IDs&diff=3001Node-IDs2012-09-27T13:29:13Z<p>Jan.Merkelbag: </p>
<hr />
<div>[[de:Node-IDs]]<br />
The node-IDs depend on the CANopen network's topology. Here you can see a recommendation for node-IDs in CANopen-lift networks. <br />
<br />
= Topology: 2 seperate busses for car and shaft =<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="5"<br />
|+ Node-ID Recommedation:<br />
! width="10%" bgcolor="#F0F0F0" | Node-ID <br /> (dez)<br />
! width="45%" bgcolor="#F0F0F0" | CAN1 <br> local bus<br />
! width="45%" bgcolor="#F0F0F0" | CAN2 <br> shaft/group bus<br />
|-<br />
| align="center" | 1<br />
| lift controller (Call/car drive/door controller, NMT “flying” master)<br />
| lift controller G1 (Call/car drive/door controller lift 1, NMT “flying” master)<br />
|-<br />
| align="center" | 2<br />
| drive (frequency inverter, car drive unit)<br />
| lift controller G2 (Call/car drive/door controller lift 2, NMT “flying” master)<br />
|-<br />
| align="center" | 3<br />
| ''reserved''<br />
| lift controller G3 (Call/car drive/door controller lift 3, NMT “flying” master)<br />
|-<br />
| align="center" | 4<br />
| encoder/position system 1 (Car position unit 1)<br />
| lift controller G4 (Call/car drive/door controller lift 4, NMT “flying” master)<br />
|-<br />
| align="center" | 5<br />
| encoder/position system 2 (Car position unit 2)<br />
| lift controller G5 (Call/car drive/door controller lift 5, NMT “flying” master)<br />
|-<br />
| align="center" | 6<br />
| ''reserved''<br />
| lift controller G6 (Call/car drive/door controller lift 6, NMT “flying” master)<br />
|-<br />
| align="center" | 7<br />
| door drive unit 1 (door A)<br />
| lift controller G7 (Call/car drive/door controller lift 7, NMT “flying” master)<br />
|-<br />
| align="center" | 8<br />
| door drive unit 2 (door B)<br />
| lift controller G8 (Call/car drive/door controller lift 8, NMT “flying” master)<br />
|-<br />
| align="center" | 9<br />
| door drive unit 3 (door C)<br />
| gateway/repeater (Remote data transmission unit 1)<br />
|-<br />
| align="center" | 10<br />
| gateway (CDG-01)<br />
| gateway/repeater 2 (Remote data transmission unit 2)<br />
|-<br />
| align="center" | 11<br />
| ''reserved (e.g. Wago-I/O)''<br />
| gateway/repeater 3 (Remote data transmission unit 3)<br />
|-<br />
| align="center" | 12<br />
| ''reserved (inspection box)''<br />
| gateway/repeater 4 (Remote data transmission unit 4)<br />
|-<br />
| align="center" | 13<br />
| weight measurement unit<br />
| gateway/repeater 5 (Remote data transmission unit 5)<br />
|-<br />
| align="center" | 14<br />
| ''energy measurent unit''<br />
| gateway/repeater 6 (Remote data transmission unit 6)<br />
|-<br />
| align="center" | 15<br />
| ''reserved (emergency call device)''<br />
| gateway/repeater 7 (Remote data transmission unit 7)<br />
|-<br />
| align="center" | 16<br />
| car call panel node 1 (Car I/O panel 1)<br />
| gateway/repeater 8 (Remote data transmission unit 8)<br />
|-<br />
| align="center" | 17<br />
| car call panel node 2 (Car I/O panel 2)<br />
| &nbsp;<br />
|-<br />
| align="center" | 18<br />
| car call panel node 3 (Car I/O panel 3)<br />
| &nbsp;<br />
|-<br />
| align="center" | 19<br />
| car call panel node 4 (Car I/O panel 4)<br />
| &nbsp;<br />
|-<br />
| align="center" | 20<br />
| car call panel node 5 (Car I/O panel 5)<br />
| &nbsp;<br />
|-<br />
| align="center" | 21 - 84<br />
| colspan="2" | floor I/O panel 1 to 64<br />
|-<br />
| align="center" | 85 - 119<br />
| colspan="2" | free<br />
|-<br />
| align="center" | 120 - 124<br />
| colspan="2" | ''reserved''<br />
|-<br />
| align="center" | 125<br />
| colspan="2" | default setting of a non-parameterized device and [[wpde:Daisy chain|daisy-chain systems]]<br />
|-<br />
| align="center" | 126<br />
| colspan="2" | [[firmware update|firmware update boot loader]]<br />
|-<br />
| align="center" | 127 <br />
| colspan="2" | diagnostic tool<br />
|}<br />
<br />
[[category:recommedations]]</div>Jan.Merkelbaghttps://en.canopen-lift.org/index.php?title=Node-IDs&diff=3000Node-IDs2012-09-27T13:28:56Z<p>Jan.Merkelbag: </p>
<hr />
<div>[[de:Node-IDs]]<br />
The node-IDs depend on the CANopen network' topology. Here you can see a recommendation for node-IDs in CANopen-lift networks. <br />
<br />
= Topology: 2 seperate busses for car and shaft =<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="5"<br />
|+ Node-ID Recommedation:<br />
! width="10%" bgcolor="#F0F0F0" | Node-ID <br /> (dez)<br />
! width="45%" bgcolor="#F0F0F0" | CAN1 <br> local bus<br />
! width="45%" bgcolor="#F0F0F0" | CAN2 <br> shaft/group bus<br />
|-<br />
| align="center" | 1<br />
| lift controller (Call/car drive/door controller, NMT “flying” master)<br />
| lift controller G1 (Call/car drive/door controller lift 1, NMT “flying” master)<br />
|-<br />
| align="center" | 2<br />
| drive (frequency inverter, car drive unit)<br />
| lift controller G2 (Call/car drive/door controller lift 2, NMT “flying” master)<br />
|-<br />
| align="center" | 3<br />
| ''reserved''<br />
| lift controller G3 (Call/car drive/door controller lift 3, NMT “flying” master)<br />
|-<br />
| align="center" | 4<br />
| encoder/position system 1 (Car position unit 1)<br />
| lift controller G4 (Call/car drive/door controller lift 4, NMT “flying” master)<br />
|-<br />
| align="center" | 5<br />
| encoder/position system 2 (Car position unit 2)<br />
| lift controller G5 (Call/car drive/door controller lift 5, NMT “flying” master)<br />
|-<br />
| align="center" | 6<br />
| ''reserved''<br />
| lift controller G6 (Call/car drive/door controller lift 6, NMT “flying” master)<br />
|-<br />
| align="center" | 7<br />
| door drive unit 1 (door A)<br />
| lift controller G7 (Call/car drive/door controller lift 7, NMT “flying” master)<br />
|-<br />
| align="center" | 8<br />
| door drive unit 2 (door B)<br />
| lift controller G8 (Call/car drive/door controller lift 8, NMT “flying” master)<br />
|-<br />
| align="center" | 9<br />
| door drive unit 3 (door C)<br />
| gateway/repeater (Remote data transmission unit 1)<br />
|-<br />
| align="center" | 10<br />
| gateway (CDG-01)<br />
| gateway/repeater 2 (Remote data transmission unit 2)<br />
|-<br />
| align="center" | 11<br />
| ''reserved (e.g. Wago-I/O)''<br />
| gateway/repeater 3 (Remote data transmission unit 3)<br />
|-<br />
| align="center" | 12<br />
| ''reserved (inspection box)''<br />
| gateway/repeater 4 (Remote data transmission unit 4)<br />
|-<br />
| align="center" | 13<br />
| weight measurement unit<br />
| gateway/repeater 5 (Remote data transmission unit 5)<br />
|-<br />
| align="center" | 14<br />
| ''energy measurent unit''<br />
| gateway/repeater 6 (Remote data transmission unit 6)<br />
|-<br />
| align="center" | 15<br />
| ''reserved (emergency call device)''<br />
| gateway/repeater 7 (Remote data transmission unit 7)<br />
|-<br />
| align="center" | 16<br />
| car call panel node 1 (Car I/O panel 1)<br />
| gateway/repeater 8 (Remote data transmission unit 8)<br />
|-<br />
| align="center" | 17<br />
| car call panel node 2 (Car I/O panel 2)<br />
| &nbsp;<br />
|-<br />
| align="center" | 18<br />
| car call panel node 3 (Car I/O panel 3)<br />
| &nbsp;<br />
|-<br />
| align="center" | 19<br />
| car call panel node 4 (Car I/O panel 4)<br />
| &nbsp;<br />
|-<br />
| align="center" | 20<br />
| car call panel node 5 (Car I/O panel 5)<br />
| &nbsp;<br />
|-<br />
| align="center" | 21 - 84<br />
| colspan="2" | floor I/O panel 1 to 64<br />
|-<br />
| align="center" | 85 - 119<br />
| colspan="2" | free<br />
|-<br />
| align="center" | 120 - 124<br />
| colspan="2" | ''reserved''<br />
|-<br />
| align="center" | 125<br />
| colspan="2" | default setting of a non-parameterized device and [[wpde:Daisy chain|daisy-chain systems]]<br />
|-<br />
| align="center" | 126<br />
| colspan="2" | [[firmware update|firmware update boot loader]]<br />
|-<br />
| align="center" | 127 <br />
| colspan="2" | diagnostic tool<br />
|}<br />
<br />
[[category:recommedations]]</div>Jan.Merkelbaghttps://en.canopen-lift.org/index.php?title=Node-IDs&diff=2999Node-IDs2012-09-27T13:27:24Z<p>Jan.Merkelbag: </p>
<hr />
<div>[[de:Node-IDs]]<br />
The node-IDs depend on the topology of the CANopen network. Here you can see a recommedation of node-IDs in CANopen-lift networks. <br />
<br />
= Topology: 2 seperate busses for car and shaft =<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="5"<br />
|+ Node-ID Recommedation:<br />
! width="10%" bgcolor="#F0F0F0" | Node-ID <br /> (dez)<br />
! width="45%" bgcolor="#F0F0F0" | CAN1 <br> local bus<br />
! width="45%" bgcolor="#F0F0F0" | CAN2 <br> shaft/group bus<br />
|-<br />
| align="center" | 1<br />
| lift controller (Call/car drive/door controller, NMT “flying” master)<br />
| lift controller G1 (Call/car drive/door controller lift 1, NMT “flying” master)<br />
|-<br />
| align="center" | 2<br />
| drive (frequency inverter, car drive unit)<br />
| lift controller G2 (Call/car drive/door controller lift 2, NMT “flying” master)<br />
|-<br />
| align="center" | 3<br />
| ''reserved''<br />
| lift controller G3 (Call/car drive/door controller lift 3, NMT “flying” master)<br />
|-<br />
| align="center" | 4<br />
| encoder/position system 1 (Car position unit 1)<br />
| lift controller G4 (Call/car drive/door controller lift 4, NMT “flying” master)<br />
|-<br />
| align="center" | 5<br />
| encoder/position system 2 (Car position unit 2)<br />
| lift controller G5 (Call/car drive/door controller lift 5, NMT “flying” master)<br />
|-<br />
| align="center" | 6<br />
| ''reserved''<br />
| lift controller G6 (Call/car drive/door controller lift 6, NMT “flying” master)<br />
|-<br />
| align="center" | 7<br />
| door drive unit 1 (door A)<br />
| lift controller G7 (Call/car drive/door controller lift 7, NMT “flying” master)<br />
|-<br />
| align="center" | 8<br />
| door drive unit 2 (door B)<br />
| lift controller G8 (Call/car drive/door controller lift 8, NMT “flying” master)<br />
|-<br />
| align="center" | 9<br />
| door drive unit 3 (door C)<br />
| gateway/repeater (Remote data transmission unit 1)<br />
|-<br />
| align="center" | 10<br />
| gateway (CDG-01)<br />
| gateway/repeater 2 (Remote data transmission unit 2)<br />
|-<br />
| align="center" | 11<br />
| ''reserved (e.g. Wago-I/O)''<br />
| gateway/repeater 3 (Remote data transmission unit 3)<br />
|-<br />
| align="center" | 12<br />
| ''reserved (inspection box)''<br />
| gateway/repeater 4 (Remote data transmission unit 4)<br />
|-<br />
| align="center" | 13<br />
| weight measurement unit<br />
| gateway/repeater 5 (Remote data transmission unit 5)<br />
|-<br />
| align="center" | 14<br />
| ''energy measurent unit''<br />
| gateway/repeater 6 (Remote data transmission unit 6)<br />
|-<br />
| align="center" | 15<br />
| ''reserved (emergency call device)''<br />
| gateway/repeater 7 (Remote data transmission unit 7)<br />
|-<br />
| align="center" | 16<br />
| car call panel node 1 (Car I/O panel 1)<br />
| gateway/repeater 8 (Remote data transmission unit 8)<br />
|-<br />
| align="center" | 17<br />
| car call panel node 2 (Car I/O panel 2)<br />
| &nbsp;<br />
|-<br />
| align="center" | 18<br />
| car call panel node 3 (Car I/O panel 3)<br />
| &nbsp;<br />
|-<br />
| align="center" | 19<br />
| car call panel node 4 (Car I/O panel 4)<br />
| &nbsp;<br />
|-<br />
| align="center" | 20<br />
| car call panel node 5 (Car I/O panel 5)<br />
| &nbsp;<br />
|-<br />
| align="center" | 21 - 84<br />
| colspan="2" | floor I/O panel 1 to 64<br />
|-<br />
| align="center" | 85 - 119<br />
| colspan="2" | free<br />
|-<br />
| align="center" | 120 - 124<br />
| colspan="2" | ''reserved''<br />
|-<br />
| align="center" | 125<br />
| colspan="2" | default setting of a non-parameterized device and [[wpde:Daisy chain|daisy-chain systems]]<br />
|-<br />
| align="center" | 126<br />
| colspan="2" | [[firmware update|firmware update boot loader]]<br />
|-<br />
| align="center" | 127 <br />
| colspan="2" | diagnostic tool<br />
|}<br />
<br />
[[category:recommedations]]</div>Jan.Merkelbaghttps://en.canopen-lift.org/index.php?title=Node-IDs&diff=2998Node-IDs2012-09-27T13:25:15Z<p>Jan.Merkelbag: /* Topology: 2 seperate busses for car and shaft */</p>
<hr />
<div>[[de:Node-IDs]]<br />
The node-IDs depents on the topology of the CANopen network. Here you can see a recommedation of node-IDs in CANopen-lift networks. <br />
<br />
= Topology: 2 seperate busses for car and shaft =<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="5"<br />
|+ Node-ID Recommedation:<br />
! width="10%" bgcolor="#F0F0F0" | Node-ID <br /> (dez)<br />
! width="45%" bgcolor="#F0F0F0" | CAN1 <br> local bus<br />
! width="45%" bgcolor="#F0F0F0" | CAN2 <br> shaft/group bus<br />
|-<br />
| align="center" | 1<br />
| lift controller (Call/car drive/door controller, NMT “flying” master)<br />
| lift controller G1 (Call/car drive/door controller lift 1, NMT “flying” master)<br />
|-<br />
| align="center" | 2<br />
| drive (frequency inverter, car drive unit)<br />
| lift controller G2 (Call/car drive/door controller lift 2, NMT “flying” master)<br />
|-<br />
| align="center" | 3<br />
| ''reserved''<br />
| lift controller G3 (Call/car drive/door controller lift 3, NMT “flying” master)<br />
|-<br />
| align="center" | 4<br />
| encoder/position system 1 (Car position unit 1)<br />
| lift controller G4 (Call/car drive/door controller lift 4, NMT “flying” master)<br />
|-<br />
| align="center" | 5<br />
| encoder/position system 2 (Car position unit 2)<br />
| lift controller G5 (Call/car drive/door controller lift 5, NMT “flying” master)<br />
|-<br />
| align="center" | 6<br />
| ''reserved''<br />
| lift controller G6 (Call/car drive/door controller lift 6, NMT “flying” master)<br />
|-<br />
| align="center" | 7<br />
| door drive unit 1 (door A)<br />
| lift controller G7 (Call/car drive/door controller lift 7, NMT “flying” master)<br />
|-<br />
| align="center" | 8<br />
| door drive unit 2 (door B)<br />
| lift controller G8 (Call/car drive/door controller lift 8, NMT “flying” master)<br />
|-<br />
| align="center" | 9<br />
| door drive unit 3 (door C)<br />
| gateway/repeater (Remote data transmission unit 1)<br />
|-<br />
| align="center" | 10<br />
| gateway (CDG-01)<br />
| gateway/repeater 2 (Remote data transmission unit 2)<br />
|-<br />
| align="center" | 11<br />
| ''reserved (e.g. Wago-I/O)''<br />
| gateway/repeater 3 (Remote data transmission unit 3)<br />
|-<br />
| align="center" | 12<br />
| ''reserved (inspection box)''<br />
| gateway/repeater 4 (Remote data transmission unit 4)<br />
|-<br />
| align="center" | 13<br />
| weight measurement unit<br />
| gateway/repeater 5 (Remote data transmission unit 5)<br />
|-<br />
| align="center" | 14<br />
| ''energy measurent unit''<br />
| gateway/repeater 6 (Remote data transmission unit 6)<br />
|-<br />
| align="center" | 15<br />
| ''reserved (emergency call device)''<br />
| gateway/repeater 7 (Remote data transmission unit 7)<br />
|-<br />
| align="center" | 16<br />
| car call panel node 1 (Car I/O panel 1)<br />
| gateway/repeater 8 (Remote data transmission unit 8)<br />
|-<br />
| align="center" | 17<br />
| car call panel node 2 (Car I/O panel 2)<br />
| &nbsp;<br />
|-<br />
| align="center" | 18<br />
| car call panel node 3 (Car I/O panel 3)<br />
| &nbsp;<br />
|-<br />
| align="center" | 19<br />
| car call panel node 4 (Car I/O panel 4)<br />
| &nbsp;<br />
|-<br />
| align="center" | 20<br />
| car call panel node 5 (Car I/O panel 5)<br />
| &nbsp;<br />
|-<br />
| align="center" | 21 - 84<br />
| colspan="2" | floor I/O panel 1 to 64<br />
|-<br />
| align="center" | 85 - 119<br />
| colspan="2" | free<br />
|-<br />
| align="center" | 120 - 124<br />
| colspan="2" | ''reserved''<br />
|-<br />
| align="center" | 125<br />
| colspan="2" | default setting of a non-parameterized device and [[wpde:Daisy chain|daisy-chain systems]]<br />
|-<br />
| align="center" | 126<br />
| colspan="2" | [[firmware update|firmware update boot loader]]<br />
|-<br />
| align="center" | 127 <br />
| colspan="2" | diagnostic tool<br />
|}<br />
<br />
[[category:recommedations]]</div>Jan.Merkelbaghttps://en.canopen-lift.org/index.php?title=Node-IDs&diff=2997Node-IDs2012-09-27T13:20:27Z<p>Jan.Merkelbag: /* Topology: 2 seperate busses for car and shaft */</p>
<hr />
<div>[[de:Node-IDs]]<br />
The node-IDs depents on the topology of the CANopen network. Here you can see a recommedation of node-IDs in CANopen-lift networks. <br />
<br />
= Topology: 2 seperate busses for car and shaft =<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="5"<br />
|+ Node-ID Recommedation:<br />
! width="10%" bgcolor="#F0F0F0" | Node-ID <br /> (dez)<br />
! width="45%" bgcolor="#F0F0F0" | CAN1 <br> local bus<br />
! width="45%" bgcolor="#F0F0F0" | CAN2 <br> shaft/group bus<br />
|-<br />
| align="center" | 1<br />
| lift controller (Call/car drive/door controller, NMT “flying” master)<br />
| lift controller G1<br />
|-<br />
| align="center" | 2<br />
| drive (frequency inverter, car drive unit)<br />
| lift controller G2<br />
|-<br />
| align="center" | 3<br />
| ''reserved''<br />
| lift controller G3<br />
|-<br />
| align="center" | 4<br />
| encoder/position system 1 (Car position unit 1)<br />
| lift controller G4<br />
|-<br />
| align="center" | 5<br />
| encoder/position system 2 (Car position unit 2)<br />
| lift controller G5<br />
|-<br />
| align="center" | 6<br />
| ''reserved''<br />
| lift controller G6<br />
|-<br />
| align="center" | 7<br />
| door drive unit 1 (door A)<br />
| lift controller G7<br />
|-<br />
| align="center" | 8<br />
| door drive unit 2 (door B)<br />
| lift controller G8<br />
|-<br />
| align="center" | 9<br />
| door drive unit 3 (door C)<br />
| gateway 1 (CDG-01)<br />
|-<br />
| align="center" | 10<br />
| gateway (CDG-01)<br />
| gateway 2 (CDG-01)<br />
|-<br />
| align="center" | 11<br />
| ''reserved (e.g. Wago-I/O)''<br />
| gateway 3 (CDG-01)<br />
|-<br />
| align="center" | 12<br />
| ''reserved (inspection box)''<br />
| gateway 4 (CDG-01)<br />
|-<br />
| align="center" | 13<br />
| weight measurement unit<br />
| gateway 5 (CDG-01)<br />
|-<br />
| align="center" | 14<br />
| ''energy measurent unit''<br />
| gateway 6 (CDG-01)<br />
|-<br />
| align="center" | 15<br />
| ''reserved (emergency call device)''<br />
| gateway 7 (CDG-01)<br />
|-<br />
| align="center" | 16<br />
| car call panel node 1 (Car I/O panel 1)<br />
| gateway 8 (CDG-01)<br />
|-<br />
| align="center" | 17<br />
| car call panel node 2 (Car I/O panel 2)<br />
| &nbsp;<br />
|-<br />
| align="center" | 18<br />
| car call panel node 3 (Car I/O panel 3)<br />
| &nbsp;<br />
|-<br />
| align="center" | 19<br />
| car call panel node 4 (Car I/O panel 4)<br />
| &nbsp;<br />
|-<br />
| align="center" | 20<br />
| car call panel node 5 (Car I/O panel 5)<br />
| &nbsp;<br />
|-<br />
| align="center" | 21 - 84<br />
| colspan="2" | floor I/O panel 1 to 64<br />
|-<br />
| align="center" | 85 - 119<br />
| colspan="2" | free<br />
|-<br />
| align="center" | 120 - 124<br />
| colspan="2" | ''reserved''<br />
|-<br />
| align="center" | 125<br />
| colspan="2" | default setting of a non-parameterized device and [[wpde:Daisy chain|daisy-chain systems]]<br />
|-<br />
| align="center" | 126<br />
| colspan="2" | [[firmware update|firmware update boot loader]]<br />
|-<br />
| align="center" | 127 <br />
| colspan="2" | diagnostic tool<br />
|}<br />
<br />
[[category:recommedations]]</div>Jan.Merkelbaghttps://en.canopen-lift.org/index.php?title=Node-IDs&diff=2996Node-IDs2012-09-27T13:09:36Z<p>Jan.Merkelbag: /* Topology: 2 seperate busses for car and shaft */</p>
<hr />
<div>[[de:Node-IDs]]<br />
The node-IDs depents on the topology of the CANopen network. Here you can see a recommedation of node-IDs in CANopen-lift networks. <br />
<br />
= Topology: 2 seperate busses for car and shaft =<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="5"<br />
|+ Node-ID Recommedation:<br />
! width="10%" bgcolor="#F0F0F0" | Node-ID <br /> (dez)<br />
! width="45%" bgcolor="#F0F0F0" | CAN1 <br> local bus<br />
! width="45%" bgcolor="#F0F0F0" | CAN2 <br> shaft/group bus<br />
|-<br />
| align="center" | 1<br />
| lift controller (Call/car drive/door controller, NMT “flying” master)<br />
| lift controller G1<br />
|-<br />
| align="center" | 2<br />
| drive (frequency inverter, car drive unit)<br />
| lift controller G2<br />
|-<br />
| align="center" | 3<br />
| ''reserved''<br />
| lift controller G3<br />
|-<br />
| align="center" | 4<br />
| encoder/position system 1 (Car position unit 1)<br />
| lift controller G4<br />
|-<br />
| align="center" | 5<br />
| encoder/position system 2 (Car position unit 2)<br />
| lift controller G5<br />
|-<br />
| align="center" | 6<br />
| ''reserved''<br />
| lift controller G6<br />
|-<br />
| align="center" | 7<br />
| door drive unit 1 (door A)<br />
| lift controller G7<br />
|-<br />
| align="center" | 8<br />
| door drive unit 2 (door B)<br />
| lift controller G8<br />
|-<br />
| align="center" | 9<br />
| gateway (CDG-01)<br />
| gateway 1 (CDG-01)<br />
|-<br />
| align="center" | 10<br />
| door drive unit 3 (door C)<br />
| gateway 2 (CDG-01)<br />
|-<br />
| align="center" | 11<br />
| ''reserved (e.g. Wago-I/O)''<br />
| gateway 3 (CDG-01)<br />
|-<br />
| align="center" | 12<br />
| top of car inspection box (car electronic)<br />
| gateway 4 (CDG-01)<br />
|-<br />
| align="center" | 13<br />
| weight measurement unit<br />
| gateway 5 (CDG-01)<br />
|-<br />
| align="center" | 14<br />
| ''energy measurent unit''<br />
| gateway 6 (CDG-01)<br />
|-<br />
| align="center" | 15<br />
| ''reserved (emergency call device)''<br />
| gateway 7 (CDG-01)<br />
|-<br />
| align="center" | 16<br />
| car call panel node 1<br />
| gateway 8 (CDG-01)<br />
|-<br />
| align="center" | 17<br />
| car call panel node 2<br />
| &nbsp;<br />
|-<br />
| align="center" | 18<br />
| car call panel node 3<br />
| &nbsp;<br />
|-<br />
| align="center" | 19<br />
| car call panel node 4<br />
| &nbsp;<br />
|-<br />
| align="center" | 20<br />
| car call panel node 5<br />
| &nbsp;<br />
|-<br />
| align="center" | 21 - 70<br />
| colspan="2" | landing panel floor 1 to 50 (e.g. line 1 resp. door A)<br />
|-<br />
| align="center" | 71 - 120<br />
| colspan="2" | landing panel floor 1 to 50 (e.g. line 2 resp. door B)<br />
|-<br />
| align="center" | 121 - 124<br />
| colspan="2" | free<br />
|-<br />
| align="center" | 125<br />
| colspan="2" | default setting of a new device and [[wpde:Daisy chain|daisy-chain systems]]<br />
|-<br />
| align="center" | 126<br />
| colspan="2" | [[firmware update|firmware update boot loader]]<br />
|-<br />
| align="center" | 127 <br />
| colspan="2" | diagnostic tool<br />
|}<br />
<br />
[[category:recommedations]]</div>Jan.Merkelbag