{"id":41,"date":"2016-11-20T19:28:08","date_gmt":"2016-11-20T18:28:08","guid":{"rendered":"http:\/\/localhost\/arc\/wordpress\/?page_id=38"},"modified":"2017-04-08T10:37:45","modified_gmt":"2017-04-08T09:37:45","slug":"aufbau-und-inbetriebnahme","status":"publish","type":"page","link":"https:\/\/plauffs.de\/arc\/arc1\/aufbau-und-inbetriebnahme\/","title":{"rendered":"Setup and Commissioning"},"content":{"rendered":"

Hardware<\/h3>\n

For connecting the various components without the need for soldering, the use of so-called jumper-wires<\/a> is recommended. Of course, also regular cables can be soldered onto the pin headers. For the optional Bluetooth Bee module, soldering unfortunately is inevitable because of the short pins and their small pitch.<\/p>\n

    \n
  1. The jumper-settings on the Discovery Board must be as follows:
    \nCN4<\/strong> \u2013 Both jumpers fitted (\u201cDISCOVERY\u201d-setting). This enables the onboard ST-LINK\/V2 programmer\/debugger to be used for our STM32 microcontroller. If the jumpers are not fitted, you can use the ST-LINK programmer for programming external microcontrollers.
    \nJP3<\/strong> \u2013 fitted. With this jumper, you can measure the current consumption of the microcontroller. Just remove it and insert a current measurement device instead.
    \nJP1<\/strong> and JP2<\/strong> are fitted by default and can be kept like this. Both jumpers connect GND to GND and thus have no direct use. If you would require more ground pins \u2013 here you go!<\/li>\n
  2. Besides the jumpers, there are several solder bridges on the board that don\u2019t need to be changed. Further information on their use can be found in the board\u2019s User Manual<\/a>.<\/li>\n
  3. Now you can wire all components according to the following table:
    \n\n\n\n\n\t\n\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t
    Port \/ Pin<\/th>Connection to
    \n<\/th>    		<\/th>\n<\/tr>\n<\/thead>\n
    Connectors for rotary encoder (speed controller)
    \n<\/td>    		\"stm32f429i_disco_bottom_markup\"
    \nBottom view of the board
    \n<\/td>\n<\/tr>\n
    PA5<\/td>Rotary encoder (speed controller) Channel A
    \n<\/td>\n<\/tr>\n
    PB3<\/td>Rotary encoder (speed controller) Channel B
    \n<\/td>\n<\/tr>\n
    PC13<\/td>Rotary encoder pushbutton (Select)
    \n<\/td>\n<\/tr>\n
    3V<\/td>Rotary encoder supply voltage
    \n<\/td>\n<\/tr>\n
    GND<\/td>Rotary encoder ground
    \n<\/td>\n<\/tr>\n
    PA0<\/td>External Emergency Stop button (optional) as alternative to the blue button on the board. The button must pull PA0 to VDD (3.3V). The internal Pull-Down resistor of the blue on-board button does the rest. For more information please consult the schematics or the User Manual<\/a>.
    \n<\/td>\n<\/tr>\n
    LED Ring<\/td>\n<\/tr>\n
    PE2<\/td>Sparkfun LED Ring CLK Pin or<\/em> Seeed Studio Circular LED DCKI Pin<\/td>\n<\/tr>\n
    PE3<\/td>Sparkfun LED Ring LATCH Pin<\/td>\n<\/tr>\n
    PE6<\/td>Sparkfun LED Ring DAT Pin or<\/em> Seeed Studio Circular LED DI Pin <\/td>\n<\/tr>\n
    3V<\/td>Seeed Studio Circular LED Ring supply voltage
    \n<\/td>\n<\/tr>\n
    GND<\/td>Seeed Studio Circular LED Ring ground
    \n<\/td>\n<\/tr>\n
    DCC signal output to input-optocoupler of a DCC booster
    \n<\/td>\n<\/tr>\n
    PC8<\/td>DCC signal to booster
    \n<\/td>\n<\/tr>\n
    PA7<\/td>DCC signal (complementary) to booster
    \n<\/td>\n<\/tr>\n
    GND<\/td>DCC reference ground to booster
    \n<\/td>\n<\/tr>\n
    Bluetooth module for a wireless connection to an Android mobile device
    \n<\/td>\n<\/tr>\n
    PA9<\/td>Bluetooth Bee v2.0 Rx Pin<\/td>\n<\/tr>\n
    PA10<\/td>Bluetooth Bee v2.0 Tx Pin<\/td>\n<\/tr>\n
    GND<\/td>Bluetooth Bee v2.0 GND Pin<\/td>\n<\/tr>\n
    3V<\/td>Bluetooth Bee v2.0 3V3 Pin<\/td>\n<\/tr>\n
    Connection of an external 5V power supply as alternative to USB power supply
    \n<\/td>\n<\/tr>\n
    GND<\/td>External ground
    \n<\/td>\n<\/tr>\n
    5V<\/td>External 5V power supply
    \n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/li>\n<\/ol>\n

    Encoder-Interface<\/h4>\n

    If you use the Seeed Studio Grove encoder, the signal of the encoder pushbutton unfortunately is not available on the 4-pole interface. The pushbutton also connects to GND instead of supply voltage level. Thus some minor modifications have to be done: a separate jumper cable must be soldered to the pushbutton pin at the encoder (to be able to connect it to PC13 on ARC1) and the circuit track to R5 must be opened, e.g. by cutting with a knife (see figure).<\/p>\n

    \"seeed_encoder_mod\"<\/a><\/p>\n

    When using an arbitrary custom encoder (neither the Seeed Studio Grove encoder nor the Sparkfun Illuminated encoder), the encoder must switch its phases A and B against VDD (3V). Depending on whether the pushbutton switches to GND or to VDD, you have to choose between different ARC1 firmware versions:<\/p>\n

    ARC1 version for Seeed Studio: Encoder-Pushbutton switches to GND
    \nARC1 Version for Sparkfun: Encoder- Pushbutton switches to VDD (3V)<\/p>\n

    Booster-Interface<\/h4>\n

    As there are many commercial and DIY boosters on the market \/ on the web and a booster would require a custom PCB layout, a booster is not (yet) part of the ARC project. A good list of boosters is given here<\/a>, but also Google will give a bunch of good results for boosters. Also recommended are the boosters<\/a> of the OpenDCC project.<\/p>\n

    ARC1 provides a differential 3.3V DCC signal on pins PC8 and PA7 (positive signal on PC8, negative signal on PA7). Any GND pin can be used as reference for the DCC signal. Thus ARC1 should be compatible with almost any available booster circuit.<\/p>\n

    Import for the selection and connection of a booster is the galvanic isolation between the booster and ARC1 (e.g. by use of an optocoupler). Most of the commercial and DIY boosters provide adequate means of galvanic isolation. The isolation is important, as in many cases the command station (e.g. ARC1) and the boosters are supplied by different power sources or are localized at different places and thus operate at a different ground level. If there is no galvanic isolation, equalizing currents on the DCC signal lines can permanently destroy your command station.<\/p>\n

    Software<\/h3>\n

    A great advantage of the ST Microelectronics development boards is, that they are already equipped with an on-board programmer and you won\u2019t need to buy or build a separate programmer for flashing the firmware to ARC1. ST\u2019s proprietary programming and debugging interface is called ST-LINK\/V2 or ST-LINK\/V2-1 and uses the Mini-USB interface of the board.<\/p>\n

    Important note:<\/strong> For flashing the firmware, any external 5V power supply should be disconnected. While flashing, the board will get powered by USB.<\/p>\n

      \n
    1. First of all, you need the ST-LINK USB driver. You can find it here: http:\/\/www.st.com\/en\/embedded-software\/stsw-link009.html<\/a>. Unfortunately you have to register on the ST website first.<\/li>\n
    2. You will also need the STM32 ST-LINK utility for programming \/ flashing of ARC1 based on the compiled firmware binary files<\/a>. You can download this tool after registering (of course you will only need one registration) here: http:\/\/www.st.com\/en\/embedded-software\/stsw-link004.html<\/a>.<\/li>\n
    3. Connect the Mini-USB interface (NOT the Micro-USB interface next to the display) of the development board with your PC. After some seconds the demo-software of ST should appear on the LCD display.<\/li>\n
    4. Double-check the correct jumper setting (see above).<\/li>\n
    5. Run the STM32 ST-LINK utility and open the ARC-firmware file (*.hex) with \u201cFile->Open File\u201d (STRG+O).<\/li>\n
    6. Establish a connection to the development board with \u201cTarget->Connect\u201d. If the USB driver was installed successfully, this should not evoke any problems. A successfully established connection should give the following log output:
      \n16:40:44 : Connected via SWD.<\/em>
      \n16:40:44 : Connection mode: Normal.<\/em>
      \n16:40:44 : Debug in Low Power mode enabled.<\/em>
      \n16:40:44 : Device ID: 0x419<\/em>
      \n16:40:44 : Device flash Size: 2MBytes<\/em>
      \n16:40:44 : Device family: STM32F42xxx\/F43xxx<\/em><\/li>\n
    7. After the connection is established, select \u201cTarget->Program & Verify\u201d (STRG+P) and \u201cStart\u201d in the following dialog window to start the programming. You don\u2019t need to change the settings.<\/li>\n
    8. The programming and verification should take around 10-20 seconds. After it is completed successfully, the board should restart and boot into the ARC1 firmware. The log output should list something like this:
      \n16:47:16 : Memory programmed in 12s and 293ms.<\/em>
      \n16:47:16 : Verification\u2026OK<\/em>
      \n16:47:16 : Programmed memory Checksum: 0x015A31B9<\/em><\/li>\n
    9. ARC1 is now ready for use and the ST-LINK utility can be closed. Sometimes a manual reset is required before the board starts into the firmware for the first time (reset by pressing the black reset button on the board or by shortly disconnecting the power supply).<\/li>\n<\/ol>\n

       <\/p>\n

      Connection to
      \n<\/th>

    		<\/th>\n<\/tr>\n<\/thead>\n
    Connectors for rotary encoder (speed controller)
    \n<\/td>    		\"stm32f429i_disco_bottom_markup\"
    \nBottom view of the board
    \n<\/td>\n<\/tr>\n
    PA5<\/td>Rotary encoder (speed controller) Channel A
    \n<\/td>\n<\/tr>\n
    PB3<\/td>Rotary encoder (speed controller) Channel B
    \n<\/td>\n<\/tr>\n
    PC13<\/td>Rotary encoder pushbutton (Select)
    \n<\/td>\n<\/tr>\n
    3V<\/td>Rotary encoder supply voltage
    \n<\/td>\n<\/tr>\n
    GND<\/td>Rotary encoder ground
    \n<\/td>\n<\/tr>\n
    PA0<\/td>External Emergency Stop button (optional) as alternative to the blue button on the board. The button must pull PA0 to VDD (3.3V). The internal Pull-Down resistor of the blue on-board button does the rest. For more information please consult the schematics or the User Manual<\/a>.
    \n<\/td>\n<\/tr>\n
    LED Ring<\/td>\n<\/tr>\n
    PE2<\/td>Sparkfun LED Ring CLK Pin or<\/em> Seeed Studio Circular LED DCKI Pin<\/td>\n<\/tr>\n
    PE3<\/td>Sparkfun LED Ring LATCH Pin<\/td>\n<\/tr>\n
    PE6<\/td>Sparkfun LED Ring DAT Pin or<\/em> Seeed Studio Circular LED DI Pin <\/td>\n<\/tr>\n
    3V<\/td>Seeed Studio Circular LED Ring supply voltage
    \n<\/td>\n<\/tr>\n
    GND<\/td>Seeed Studio Circular LED Ring ground
    \n<\/td>\n<\/tr>\n
    DCC signal output to input-optocoupler of a DCC booster
    \n<\/td>\n<\/tr>\n
    PC8<\/td>DCC signal to booster
    \n<\/td>\n<\/tr>\n
    PA7<\/td>DCC signal (complementary) to booster
    \n<\/td>\n<\/tr>\n
    GND<\/td>DCC reference ground to booster
    \n<\/td>\n<\/tr>\n
    Bluetooth module for a wireless connection to an Android mobile device
    \n<\/td>\n<\/tr>\n
    PA9<\/td>Bluetooth Bee v2.0 Rx Pin<\/td>\n<\/tr>\n
    PA10<\/td>Bluetooth Bee v2.0 Tx Pin<\/td>\n<\/tr>\n
    GND<\/td>Bluetooth Bee v2.0 GND Pin<\/td>\n<\/tr>\n
    3V<\/td>Bluetooth Bee v2.0 3V3 Pin<\/td>\n<\/tr>\n
    Connection of an external 5V power supply as alternative to USB power supply
    \n<\/td>\n<\/tr>\n
    GND<\/td>External ground
    \n<\/td>\n<\/tr>\n
    5V<\/td>External 5V power supply
    \n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/li>\n<\/ol>\n

    Encoder-Interface<\/h4>\n

    Bei der Verwendung des Seeed Studio Grove Encoders ist das Signal des Encoder-Tasters leider nicht auf der vierpoligen Schnittstelle mit vorgesehen. Zudem schaltet der Encoder-Taster dort auf GND. Es muss daher an dieser Stelle eine (einfache) elektrische Modifikation vorgenommen werden. Zum einen muss ein separates Jumper-Kabel an den Taster-Ausgang des Encoders angel\u00f6tet werden, um ihn mit Pin PC13 von ARC1 verbinden zu k\u00f6nnen, zum anderen muss die Leiterbahn vor R5 z.B. mit einem Cutter-Messer gekappt werden (siehe Bild).<\/p>\n

    \"seeed_encoder_mod\"<\/a><\/p>\n

    Wird ein eigener Drehencoder verwendet (also weder der Seeed Studio Grove Encoder noch der Sparkfun Illuminated Encoder), sollte darauf geachtet werden, dass der Encoder seine Phasen A und B gegen VDD (also 3V) schaltet. Je nachdem ob der Encoder-Taster gegen GND oder VDD schaltet, muss die entsprechende ARC1 Softwareversion programmiert werden. Dabei gilt folgendes:<\/p>\n

    ARC1 Version f\u00fcr Seeed Studio: Encoder-Taster schaltet auf GND
    \nARC1 Version f\u00fcr Sparkfun: Encoder-Taster schaltet auf VDD (3V)<\/p>\n

    Booster-Interface<\/h4>\n

    Momentan ist ein Booster (noch) nicht Teil des ARC-Projektes, da es zum einen bereits eine Vielzahl an kommerziellen und DIY-Boostern zu finden gibt, zum anderen weil sich ein DIY-Booster nur schwer ohne eigenes Platinenlayout umsetzen l\u00e4sst. Eine gute Auflistung von Boostern findet sich hier<\/a>, aber auch Google liefert eine F\u00fclle von aktuellen Projekten zu Tage. Zu empfehlen sind ebenfalls die Booster<\/a> des OpenDCC-Projektes.<\/p>\n

    ARC1 stellt \u00fcber die Pins PC8 und PA7 ein komplement\u00e4res DCC Signal mit 3.3V Pegel zur Verf\u00fcgung. Dabei liegt auf PC8 das regul\u00e4re DCC Signal an, auf PA7 das negierte DCC Signal. Als Referenzpegel f\u00fcr das DCC Signal dient ein beliebiger GND Pin. Somit sollte ARC1 mit einem Gro\u00dfteil frei verf\u00fcgbarer oder kommerzieller Booster kompatibel sein.<\/p>\n

    Wichtig bei der Auswahl und beim Anschluss eines Boosters ist, dass der DCC-Signaleingang des Boosters \u00fcber eine galvanische Trennung verf\u00fcgt (z.B. mit Hilfe eines Optokopplers). Dies ist deshalb wichtig, da DCC Zentralen (und somit auch ARC1) in den meisten F\u00e4llen \u00fcber eine vom Booster unabh\u00e4ngige Stromversorgung verf\u00fcgen und dadurch – aber auch durch r\u00e4umliche Trennung – einen anderen Massepegel besitzen k\u00f6nnen. Wird nun ein Booster mit anderem Massepegel ohne galvanische Trennung an die Zentrale angeschlossen, k\u00f6nnen Ausgleichsstr\u00f6me \u00fcber die DCC-Signalverbindung flie\u00dfen und die Zentrale dauerhaft besch\u00e4digen.<\/p>\n

    Software<\/h3>\n

    Ein gro\u00dfer Vorteil der Development Boards von ST Microelectronics ist, dass diese bereits einen On-Board-Programmer besitzen und somit zum Flashen der Firmware kein separater Programmer gekauft oder gebastelt werden muss. ST’s eigene Programmier- und Debugschnittstelle nennt sich ST-LINK\/V2 bzw. ST-LINK\/V2-1 und arbeitet \u00fcber die stromversorgende Mini-USB-Schnittstelle des Boards.<\/p>\n

    Wichtiger Hinweis:<\/strong> Zum Programmieren der Software sollte eine ggf. vorhandene externe 5V Stromversorgung getrennt werden! W\u00e4hrend des Programmiervorganges wird das Board ausschlie\u00dflich \u00fcber die USB-Spannungsversorgung gespeist.<\/p>\n

      \n
    1. Zuerst wird der passende ST-LINK USB-Treiber ben\u00f6tigt. Diesen gibt es unter http:\/\/www.st.com\/en\/embedded-software\/stsw-link009.html<\/a> zum Download. Leider erfordert der Dowload zun\u00e4chst eine Registrierung bei ST.<\/li>\n
    2. Zum Programmieren der ARC-Firmware basierend auf den kompilierten Binaries<\/a> kommt das STM32 ST-LINK Utility zum Einsatz. Dieses gibt es ebenfalls nach erfolgter Registrierung (nat\u00fcrlich ist insgesamt nur eine Registrierung n\u00f6tig) auf der ST-Website zum Download: http:\/\/www.st.com\/en\/embedded-software\/stsw-link004.html<\/a><\/li>\n
    3. Das Development Board \u00fcber die linke Mini-USB Schnittstelle (nicht<\/span> die Micro-USB Schnittstelle direkt neben den Display) mit dem PC verbinden. Nach kurzer Zeit sollte auf dem Display die Demo-Software des Herstellers ST erscheinen.<\/li>\n
    4. \u00dcberpr\u00fcfen, ob sich alle Jumper in der oben genannten Konfiguration befinden.<\/li>\n
    5. Das STM32 ST-LINK Utility starten und \u00fcber das Men\u00fc “File->Open File” (STRG+O) die gew\u00fcnschte ARC-Firmware Datei (im *.hex Dateiformat) ausw\u00e4hlen.<\/li>\n
    6. \u00dcber das Men\u00fc “Target->Connect” mit dem Development Board, bzw. mit dem darauf befindlichen ST-LINK Programmer eine Verbindung aufbauen. Wurde der USB-Treiber korrekt installiert, sollte dies problemlos funktionieren. Eine erfolgreiche Verbindung sollte im Log-Bereich ungef\u00e4hr so aussehen:
      \n16:40:44 : Connected via SWD.<\/em>
      \n 16:40:44 : Connection mode: Normal.<\/em>
      \n 16:40:44 : Debug in Low Power mode enabled.<\/em>
      \n 16:40:44 : Device ID: 0x419<\/em>
      \n 16:40:44 : Device flash Size: 2MBytes<\/em>
      \n 16:40:44 : Device family: STM32F42xxx\/F43xxx<\/em><\/li>\n
    7. Nach erfolgreichem Verbinden, \u00fcber das Men\u00fc “Target->Program & Verify” (STRG-P) und im anschlie\u00dfenden Dialogfenster “Start” den Programmiervorgang starten. An den Einstellungen m\u00fcssen keine \u00c4nderungen vorgenommen werden.<\/li>\n
    8. Der Flash- und Verifikationsvorgang dauert ca. 10-20 Sekunden. Nach erfolgtem Programmieren sollte sich das Board neu starten und direkt in die ARC1 Firmware booten. Der Log-Bereich sollte in etwa folgendes enthalten:
      \n16:47:16 : Memory programmed in 12s and 293ms.<\/em>
      \n 16:47:16 : Verification…OK<\/em>
      \n 16:47:16 : Programmed memory Checksum: 0x015A31B9<\/em><\/li>\n
    9. Das ST-LINK Utility kann nun geschlossen werden und ARC1 ist bereit zum Einsatz. Ggf. ist noch ein manueller Reset (\u00fcber den schwarzen Taster oder durch kurzes Trennen der Stromversorgung) n\u00f6tig.<\/li>\n<\/ol>","protected":false},"excerpt":{"rendered":"

      Hardware For connecting the various components without the need for soldering, the use of so-called jumper-wires is recommended. Of course, also regular cables can be soldered onto the pin headers. For the optional Bluetooth Bee module, soldering unfortunately is inevitable…<\/span><\/p>\n

      Read more Setup and Commissioning<\/span> ›<\/span><\/a><\/div>\n

      <\/p>\n","protected":false},"author":2,"featured_media":0,"parent":8,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"tags":[],"_links":{"self":[{"href":"https:\/\/plauffs.de\/arc\/wp-json\/wp\/v2\/pages\/41"}],"collection":[{"href":"https:\/\/plauffs.de\/arc\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/plauffs.de\/arc\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/plauffs.de\/arc\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/plauffs.de\/arc\/wp-json\/wp\/v2\/comments?post=41"}],"version-history":[{"count":4,"href":"https:\/\/plauffs.de\/arc\/wp-json\/wp\/v2\/pages\/41\/revisions"}],"predecessor-version":[{"id":585,"href":"https:\/\/plauffs.de\/arc\/wp-json\/wp\/v2\/pages\/41\/revisions\/585"}],"up":[{"embeddable":true,"href":"https:\/\/plauffs.de\/arc\/wp-json\/wp\/v2\/pages\/8"}],"wp:attachment":[{"href":"https:\/\/plauffs.de\/arc\/wp-json\/wp\/v2\/media?parent=41"}],"wp:term":[{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/plauffs.de\/arc\/wp-json\/wp\/v2\/tags?post=41"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}