PLC NFC Programming Tool User Manual

Transcription

1 PLC NFC Programming Tool User Manual 1

2 Introduction The PLC series of Programmable LED Drivers from Hatch use Near Field Communication (NFC) to allow for simple and easy programming of the desired output characteristics. The Hatch PLC series gives customers the ability to stock less SKUs and program the units themselves allowing for more flexibility and customization. The Hatch NFC Programming Tool allows customers to configure output characteristics and features with ease. The Tool offers an Engineering Profile with unrestricted access to make desired modifications and an Operator Profile with restricted access for accurate streamlined production programming. 2

3 Table of Contents Introduction... 2 Table of Contents... 3 System Requirements... 4 Download & Installation... 4 Getting Started... 6 General... 6 Equipment... 6 Engineering Profile... 7 User Login... 7 Programming... 9 Saving Files Operator Profile User Login Programming Trouble Shooting Software Updates Copyright Disclaimer Limitations of Damages Table of Figures

4 System Requirements The minimum system requirements for using the Hatch PLC NFC Programming Tool are: PC or laptop with Microsoft Windows 7 or later One USB 2.0 port 512 MB of free disk space Download & Installation The Hatch NFC Programming Tool can be downloaded as a zip file from the Hatch website after completing the customer information form. A password is required to download the Programming Tool, which can be obtained from a Hatch sales representative. The zip file contains the following necessary files: Setup.exe HatchNFCProgrammer.application NFC Programming Tool User Manual.pdf NFC Quick Start Guide.pdf The setup.exe file is the installer for the full version of the Hatch NFC Programming Tool, which contains both the Engineering Profile (password protected) and the Operator profile. To install the software, launch the installer and follow the instructions on your screen to begin set up. Once set up is complete the NFC Programming tool will Launch Automatically. If the application is already installed you can launch the software by selecting the application file. In some instances on installation a security warning may pop up (Figure 1). Select Install to allow the installation to properly install (Figure 2). 4

5 Figure 1 Figure 2 5

6 Getting Started General The Hatch NFC Programming Tool is designed to provide engineers and others with a simple tool for programming the output characteristics of the Hatch PLC series of programmable LED Drivers. All Hatch PLC series drivers have a programming port. This port can be found on the side of the driver and is covered by a black Hatch branded port cover. It is not necessary or recommended to remove the port cover to program the driver. Be sure to connect the programming wand via USB port to your computer before attempting to launch the programming software tool. You will also see a red or green visual confirmation at the bottom left hand corner of the program as to whether or not the programming wand has been successfully connected or not (Figure 3). Figure 3 Equipment The Hatch programming wand NFC WAND is a USB connected device that is the interface between the computer and the PLC LED Driver. NFC WAND comes standard with a 5 foot USB cable and can be purchased through Hatch directly (Figure 4). When using the NFC WAND to program a PLC LED Driver, simply place the end of the wand that reads NFC on the T in Hatch on the driver programming port. 6

7 Figure 4 Engineering Profile User Login Once the installation has completed and the NFC WAND is connected (before launching the program), the user can select to use the Programming Tool in the Engineering Profile (Requires a Password) or in the Operator Profile.(Figure 5). The user will be given the default password when they receive the software, but it can also be obtained from a Hatch Sales Representative. In order to change the password or log into the engineering profile for the first time the default password is required. At the user login screen, the Engineering password can and should be updated by selecting CHANGE PASSWORD. If selected, an additional user log in screen appears (Figure 6) with basic instructions on creating a new password. The new password must contain 8 characters: 1 upper case, 1 lower case and 1 number. In the engineering profile, the user can program the output current of any Hatch PLC driver and has the ability to create and save CONFIG.DRVR files as well as LABEL.TXT files. At this point the user can either open a previously generated configuration file by clicking open or follow the on screen steps to create a configuration file / program a driver for testing (Figure 7). 7

8 Figure 5 Figure 6 8

9 Programming Once logged into the Engineering profile, the programming screen will appear. The user can either scan a Hatch PLC driver by using the NFC WAND (Figure 7) or if they know the exact model they are working on they can select the part number from a drop down list (Figure 8). To scan a Hatch PLC driver by using the NFC WAND simply click SEARCH FOR DRIVER beside 1 (Figure 9). Figure 7 9

10 Figure 8 Next touch and hold the NFC WAND on the black programming port on the PLC driver. Be sure to place the NFC labeling on the NFC WAND on the T in HATCH on the programming port; this will help make programming easier and faster. NOTE: The NFC WAND must be plugged into the computer before running the software. 10

11 Figure 9 Once the software has recognized the driver, the user can proceed to step 2- setting the output current level. The user should note that upon scanning the PLC driver, all of the necessary driver information (Part number, adjustable output current range, output voltage range, and max output power) now appears on the right hand side of the screen (Figure 10). The user can adjust the output current to the desired level by either using the slider bar or typing in the SET OUTPUT CURRRENT box. Desired output current level should be entered in ma. The user will notice that once an output current has been selected the information on the right hand side of the screen will update accordingly (output voltage range and max output power) (Figure 11). 11

12 Figure 10 Figure 11 12

13 Once satisfied with the output current selection, the user can proceed to step 3- Programming the driver (Figure 12). After clicking PROGRAM DRIVER, the user should touch and hold the NFC WAND on the black programming port on the PLC driver. Again, the user should be sure to place the NFC labeling on the NFC WAND on the T in HATCH on the programming port for best results. Figure 12 When programming is successful, the user will receive a positive SUCCESS confirmation on the screen (Figure 13) as well as an audible confirmation Beep. Visual confirmation will appear for 2 seconds, then return the user to the previous screen, whereby additional units can be programmed or the user can CANCEL PROGRAMMING if done. On occasion a unit may not program properly. This can be due to any number of reasons. If that occurs, a red FAILED screen will appear for 5 seconds (Figure 14), and the user will hear a reject buzz sound. After the 5 seconds the user can either try again or CANCEL PROGRAMMING. 13

14 Figure 13 Figure 14 14

15 There are scenarios where a DRIVER NOT COMPATIBLE confirmation could also appear (Figure 15). The user will also hear a reject buzz sound when the onscreen notification appears. Example 1: If in step 1 the user scanned Driver A but once the user finished adjusting the output current in step 2 they grabbed a different driver, Driver B to program in step 3. (In step 1 the user scanned a unit that could be programmed to 1400mA in step 2. When ready to program the driver in step 3 the user grabs a different unit that has a max output of 1050mA.) The user will not be able to program the driver to 1400mA and will receive the DRIVER NOT COMPATIBLE confirmation. Example 2: If a user tries to read a non HATCH PLC Driver in step 1 they will receive the DRIVER NOT COMPATIBLE confirmation. Example 3: If the user tries to program a Non- Hatch PLC driver in step 3 they will receive the DRIVER NOT COMPATIBLE Confirmation. Figure 15 If the user wants to verify that the PLC driver was programmed correctly, simply go back to Step 1 and search for the driver again. Once found the data on the right hand side should match the newly programmed information. 15

16 Saving Files Once the driver has been programmed and tested and the user is satisfied with the operation, the programming file and product label can be saved for future use. Select whether or not a label should be saved (default yes) then click SAVE in the bottom right hand corner. The.DRVR file and the.txt file can then be saved into the appropriate folder selected by the user (Figure 16). These files can be recalled by both the Engineering profile and the Operator profile for future use. Figure 16 It is suggested to save the file in the following format to help the Operator ensure they have selected the correct configuration file on a future date. Driver Part Number- Programmed Output-Project/Product. Example: PLC Z-UNV-PP- 750mA-Fixture A (Figure 17). This way the Operator can see the standard part number that matches the driver that they will be programming, the output current it will be programmed to, as well as the fixture/product that it is going into. 16

17 Figure 17 If the user wants to make a change to the file they must open the file in the engineering profile, make the necessary changes and then resave the file (Figure 18). If the file is opened in the operator profile no further changes can be made. The software was designed this way to help eliminate unauthorized changes and programming errors while in production..txt files contain information that the user can create/print a label to put on the driver indicating the settings for the newly programmed driver (Figure 19). By providing the.txt file the user can use any type of label printer they like as long as the label size is 1 ¼ x ¼. 17

18 Figure 18 Figure 19 18

19 Operator Profile User Login Once installation has completed and the NFC WAND is connected (before launching the program), the user can select to use the Programming Tool in the Engineering Profile (Requires a Password) or in the Operator Profile. The Operator Profile does not require a password (Figure 20). Figure 20 To use the NFC Programming Tool in the Operator Profile the user simply clicks OPEN on the left hand side of the screen. Select the desired programming file and click open (Figure 21). Files cannot be created or edited in the Operator profile. 19

20 Figure 21 Programming Now that the programming file has been selected, the CONFIG LOADED screen appears (Figure 22), the user can either select BEGIN PROGRAMMING if the correct file name is displayed (Figure 23), or select CANCEL PROGRAMMING to go back to the previous screen so that a different configuration file can be selected. After selecting BEGIN PROGRAMMING, touch and hold the NFC WAND on the black programming port on the PLC driver. Be sure to place the NFC labeling on the NFC WAND on the T in HATCH on the programming port; this will help make programming easier and faster. NOTE: The NFC WAND must be plugged into the computer before running the software. 20

21 Figure 22 Figure 23 21

22 When programming is successful, the user will receive a positive SUCCESS confirmation on the screen (Figure 24) as well as an audible confirmation Beep. Visual confirmation will appear for 2 seconds, then return the user to the previous screen, whereby additional units can be programmed or the user can CANCEL PROGRAMMING if done. On occasion a unit may not program properly. This can be due to any number of reasons. If that occurs, a red FAILED screen will appear for 5 seconds (Figure 25) and the user will hear a reject buzz sound. After the 5 seconds the user can either try again or CANCEL PROGRAMMING. If programming is attempted on a model that was not in the configuration file that was opened, a DRIVER NOT COMPATIBLE screen (Figure 26) will appear for 5 seconds and the user will hear a reject buzz sound. From that point the user can either decide to CANCEL PROGRAMMING and select the correct configuration file or continue to attempt to program the correct units. Figure 24 22

23 Figure 25 Figure 26 23

24 Trouble Shooting In both the Engineering Profile and the Operator Profile a green? Help Icon is available on most screens in the top right hand corner (Figure 27). Figure 27 Make sure that the programming wand is connected to the computer via USB port before launching the programming software. Place the NFC on the NFC WAND on the T in HATCH on the programming port for best results. Do not move the NFC WAND away from the programming port too quickly. Wait until you hear the beep or see the SUCCESS confirmation on the screen. 24

25 Software Updates Software updates are manual and will be sent to the user from a Hatch Sales Representative when new software is available. The user will need to uninstall the old software before installing the updated version. Copyright Copyright 2017 Hatch Transformers Inc. All rights reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system or translated into any language or computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual or otherwise, without prior written permission from Hatch. Disclaimer Hatch Transformers Inc. makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hatch assumes no responsibility for any error that may appear in this document. Hatch makes no commitment to update or keep current the information contained in this document. Limitations of Damages The vendor will not be liable for any indirect, special, incidental or consequential damages (including damages for loss of business, loss of profits, or the like), whether based on breach of contract, tort (including negligence), product liability or otherwise, even if the vendor or its representatives have been advised of the possibility of such damages and even if a remedy set forth herein is found to have failed its essential purpose. 25

26 Table of Figures Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure