|
|
| (121 dazwischenliegende Versionen von 4 Benutzern werden nicht angezeigt) |
| Zeile 1: |
Zeile 1: |
| − | == Electronic cam controls ==
| + | * [[en:Frequently asked questions UNIGATE|UNIGATE]] |
| − | ===Are there replacements for a product that is no longer available? (LOCON32-HC, LOCON32-PM)...===
| + | * [[en:Frequently asked questions UNIGATE CL|UNIGATE CL]] |
| − | 1. Substitution option with LOCON24:
| + | * [[en:Frequently asked questions UNIGATE IC|UNIGATE IC]] |
| | + | * [[en:Frequently asked questions UNIGATE RS|UNIGATE RS]] |
| | | | |
| − | In order to be able to offer you an alternate device we need to know the encoder type that was used before (absolute, parallel or incremental...), the encoder's resolution, the idle time type (bitwise or blockwise - in case of doubt the bitwise version is the more flexible one - and the number of used outputs.
| + | * [[en:Frequently asked questions CANopen|CANopen]] |
| − | | + | * [[en:Frequently asked questions DeviceNet|DeviceNet]] |
| − | Note: The standard version of the operator panel features protection type IP54. If you require IP65 (as with LOCON 32-HC) then it has to be ordered optionally.
| + | * [[en:Frequently asked questions EtherNet/IP|EtherNet/IP]] |
| − | | + | * [[en:Frequently asked questions Fast Ethernet|Fast Ethernet]] |
| − | 2. Substitution option with LOCON100/LOCON200:
| + | * [[en:Frequently asked questions PROFIBUS|PROFIBUS]] |
| − | | + | * [[en:Frequently asked questions PROFINET|PROFINET]] |
| − | Basically the following points ALWAYS have to be clarified in case of replacing a product that is no longer available: (Example in italic)
| |
| − | * Which encoder is used in connection with the cam control (NSW) (maximum of 16 inputs) -> number of encoder inputs -> at INC. at least 2, at absolute -> number of tracks = number inputs) | |
| − | | |
| − | ''A TA58-O360-GYE is used -> 9 tracks = 9 inputs''
| |
| − | | |
| − | * What other pins are used? (e. g. at INC. encoders Clear + and/or Clear- -> number of inputs +1 or +2)
| |
| − | | |
| − | ''None -> + 0 inputs''
| |
| − | | |
| − | * Is the Prog.Enable wired? (if yes -> number of inputs +1)
| |
| − | | |
| − | ''Yes. -> +1 input''
| |
| − | | |
| − | * Is the external program selection wired? If yes, how many programs? (number of inputs +2 ... +7)
| |
| − | | |
| − | ''Yes, up to program 8. 5 pins are required for it -> +5 inputs''
| |
| − | | |
| − | According to the amount here the decision is made, whether a LOCON100 or a LOCON200 can be used. Provided that the amount remains below 16, either a LOCON100 or a LOCON200 can be used. If the amount of required inputs exceeds 16, then a LOCON100 has to be used, provided that the number of inputs without the external program selection is less than 16. 9 encoder inputs +1 Prog.Enable input + 5 program inputs = total of 15 inputs. Either a LOCON100 or a LOCON200 can be used. Quantity determination of expansion modules that have to be used (LOCON100-A32 or LOCON200-IO8):
| |
| − | | |
| − | * Is the RunControl-relay wired? If yes -> number of outputs + 1
| |
| − | | |
| − | ''Yes. + 1 output for RunControl''
| |
| − | | |
| − | * How many outputs are used at the cam control? -> Number of the basis' remaining outputs (LOCON100 + LOCON200) = 16 - number of inputs
| |
| − | | |
| − | ''32 outputs are used. -> Total = 1 + 32 = 33 outputs. Either a LOCON100 (1 output) with an LOCON100-A32 extension (=32 outputs) OR a LOCON200 (1 output) + 3 x LOCON200-IO8 (8 outputs each = 32 outputs) can be used here.''
| |
| − | | |
| − | Basically the version LOCON200 + LOCON200-IO8 is to be favored, since the cycle times for this constellation are lower than those for LOCON100.
| |
| − | | |
| − | On principle it does not matter which TERM is used. LOCON100 & LOCON200 are supported by TERM6, TERM24 & TERM32 to a partially limited extent. For that reason the parameterization and configuration should principally always be carried out with WINLOC32 and the mentioned TERMs should be used for operation.
| |
| − | | |
| − | ===How do I connect my LOCON with the RS232-interface (COM port) at the PC?===
| |
| − | At the PC COM port there is a 9-pole D-SUB pin connection with the following assignment:
| |
| − | | |
| − | PIN 2 - Rx (from the PC's point of view)
| |
| − | | |
| − | PIN 3 - Tx (from the PC's point of view)
| |
| − | | |
| − | PIN 5 - GND
| |
| − | | |
| − | Example:
| |
| − | | |
| − | At the LOCON16/17 the assignment of the X2 is as follows:
| |
| − | | |
| − | PIN 26 - GND
| |
| − | | |
| − | PIN 27 - Rx 232 (from the LOCON's point of view)
| |
| − | | |
| − | PIN 28 - Tx 232 (from the LOCON's point of view)
| |
| − | | |
| − | Generally always the Rx of the PC has to be connected with the Tx of the LOCON and the Tx of the PC with the Rx of the LOCON. Also the GND always has to be connected. In case there is no separate signal "AP-GND, RS-GND" or similar, then the "standard" GND is used.
| |
| − | | |
| − | For the above example it comes to the following cable assignment:
| |
| − | | |
| − | LOCON X2 PIN26 <-> PC PIN5
| |
| − | | |
| − | LOCON X2 PIN27 <-> PC PIN3
| |
| − | | |
| − | LOCON X2 PIN28 <-> PC PIN2
| |
| − | | |
| − | Note:
| |
| − | Possible existing blue bridges between the signals "DICNET-/Rx" <-> "R-" and "DICNET+/Tx" <-> "R+" have to be removed.
| |
| − | | |
| − | ===How do I reset my LOCON90, LOCON100, LOCON100-PB, LOCON200, LOCON200-PB, ROTARNOCK100 or ROTARNOCK100-PB to the condition as supplied (reset)?===
| |
| − | In order to be able to reset the device to the condition it was supplied it has to be connected to a PC and the programming software WINLOC32 has to run. Here it does not matter whether the device is connected to the PC via the RS232-interface or via DICNET and a DICADAP3.In order to initialize the procedure the device has to show the starting message (the example shows a LOCON100 with an expansion LOCON100-A32 with DICNET communication, configured as Timer with a counting range of 16):
| |
| − | | |
| − | ''L100-48(48)-T16-485(DICNET) V3.4''
| |
| − | | |
| − | Now place the cursor behind the last character in WINLOC32 with a "left click" and by means of the keyboardkeep "STRG/CTRL" pressed and enter "i". A safety query follows:
| |
| − | ''Reset configuration to defaultvalue and clear all programmed data (Y/N)? N''
| |
| − | | |
| − | This query has to be confirmed with "y" within 3 seconds and another safety query follows:
| |
| − | | |
| − | ''Cancel operation (Y/N) N'' which is to be confirmed with "n".
| |
| − | | |
| − | If the entry is correct, the following message appears in the terminal window:
| |
| − | | |
| − | ''Clear EEROM 0H-1fffH ...............................
| |
| − | | |
| − | Restart
| |
| − | | |
| − | L100-48(48)-S4096-485(DICNET) V3.4 ok
| |
| − | | |
| − | (Error: 108)''
| |
| − | | |
| − | With it the device was set back to the condition it was originally supplied.
| |
| − | | |
| − | Error108 may be normal since the device expects an encoder (with a resolution of 4096) that may not be connected and therefore causes a timeout.
| |
| − | Note: After a reset the optional LOGIC-function has to be activated again. At the devices LOCON100 & LOCON200 the interface (RS232 or DICNET) can be set by means of a configuration file. If relating to software "DICNET" was previously configured then the interface is put back to RS232.
| |
| − | | |
| − | ===How do I activate the logic function of LOCON90, LOCON100, LOCON100-PB, LOCON200, LOCON200-PB, ROTARNOCK100 or ROTARNOCK100-PB?===
| |
| − | A "release code" ("key") is required to be able to release the optional logic functions. You can purchase this code either from us directly or from your reseller. The serial number of the unit, that is supposed to be extended by this function has to be mentioned on the purchase order. For LOCON100, LOCON100-PB, LOCON200 or LOCON200-PB only the serial number of the basic device has to be stated. The logic function will automatically be activated for all extensions. You will receive the release code by e-mail.
| |
| − | | |
| − | The device to be extended by the logic function must be connected to the PC and a start-up string has to be shown WINLOC32.
| |
| − | | |
| − | With a click on the menue ''Extras -> Product Option Activation'' a window opens for activation.
| |
| − | | |
| − | The DICNET-ID is entered in the line Device ID. For a connection through RS232 this value remains on "0".
| |
| − | | |
| − | With a click on ''read serial number'' the serial number of the device is read out and displayed (at the same time this is a test, that the connection cam control <-> PC works).
| |
| − | | |
| − | The release code is entered in the line ''Activation key''. Start behind the "-".
| |
| − | Click on ''Run'' afterwards.
| |
| − | | |
| − | (In case of an error "Returncode=4" is the result.)
| |
| − | | |
| − | A successful release is confirmed with ''Options activated''. Furthermore you can tell the logic function is released by the characters ''LG'' in the switch-on message, e. g. at LOCON 200:
| |
| − | | |
| − | L200-16-S4096-H-''LG''-232 Vx.x
| |
| − | | |
| − | Now the logic functions can be used. By a click with the right mouse button In the upload window under "Logic" a function can be defined:
| |
| − | | |
| − | Note: After a "Clear all" the logic function has to be released again.
| |
| − | | |
| − | In the category Manuals in the download area you can find directions with screen shots by the name "Instructions for the release of the logic function of LOCON100(-PB) / 200(-PB) & ROTARNOCK100(-PB)".
| |
| − | | |
| − | ===External wiring===
| |
| − | ====How is the modification from LOCON32-HC or LOCON32-PM to LOCON24 carried out?====
| |
| − | Introductorily we like to point out that this description refers to a LOCON32-HC, that is/was configured "absolute parallel 360" as encoder type. Consequently the LOCON24 also has to contain this "O360" in the article text.
| |
| − | | |
| − | {| class="wikitable"
| |
| − | !LOCON 24 !!Signal !!LOCON 32-HC !!LOCON 32-PM
| |
| − | |-
| |
| − | |X1 PIN 1 ||OUT 1 ||X10 PIN 2 ||X1 PIN 1
| |
| − | |-
| |
| − | |X1 PIN 2 ||OUT 2 ||X10 PIN 1 ||X1 PIN 2
| |
| − | |-
| |
| − | |X1 PIN 3 ||OUT 3 ||X10 PIN 4 ||X1 PIN 3
| |
| − | |-
| |
| − | |X1 PIN 4 ||OUT 4 ||X10 PIN 3 ||X1 PIN 4
| |
| − | |-
| |
| − | |X1 PIN 5 ||OUT 5 ||X10 PIN 6 ||X1 PIN 5
| |
| − | |-
| |
| − | |X1 PIN 6 ||OUT 6 ||X10 PIN 5 ||X1 PIN 6
| |
| − | |-
| |
| − | |X1 PIN 7 ||OUT 7 ||X10 PIN 8 ||X1 PIN 7
| |
| − | |-
| |
| − | |X1 PIN 8 ||OUT 8 ||X10 PIN 7 ||X1 PIN 8
| |
| − | |-
| |
| − | |X1 PIN 9 ||OUT 9 ||X10 PIN 10 ||X1 PIN 9
| |
| − | |}
| |
| − | | |
| − | ... [http://www.deutschmann.de/en/support/faq_detail.html?question=18 more]
| |
| − | | |
| − | === Modelle ===
| |
| − | ==== What has to be considered when using a LOCON200 in connection with TERM24? ====
| |
| − | If a (discontinued) device is supposed to be replaced by a LOCON200 and in case a TERM24 is used in the assembly, then the TERM24's Firmware must be updated at any rate. For the update the device has to be sent back to us.
| |
| − | | |
| − | ==== TN65 - ROTARNOCK - what is it? ====
| |
| − | It is the same unit. ROTARNOCK describes the product line and TN65 is the specific type or the article description.
| |
| − | | |
| − | Example:
| |
| − | ROTARNOCK 100 - describes the ROTARNOCK-family "100". The exact article description would be:
| |
| − | <nowiki>
| |
| − | TN65-4096-100-I232-E-N - there are different versions though.
| |
| − | | | | | | |
| |
| − | | | | | | -> Hardware option = here zero-point LED
| |
| − | | | | | -> Shaft diameter = always 10mm
| |
| − | | | | -> Type of idle time and interface = here bitwise and RS232
| |
| − | | | -> Device family = ROTARNOCK 100
| |
| − | | -> Resolution per revolution (real) = At R100 configurable as desired
| |
| − | -> Identification for ROTARNOCK
| |
| − | </nowiki>
| |
| − | In case of questions concerning the order designation or an alternative device for a unit, whose production is discontinued, our distribution partners are pleased to be at your assistance.
| |
| − | | |
| − | ==== How do you change the Profibus Ident Number? ====
| |
| − | To change the Profibus Ident Number from 3606H to 3231 the ROTARNOCK100-PB has to be connected with the PC via a serial communication (RS232). For the serial communication the following pin assignemt is valid here:
| |
| − | | |
| − | PC PIN2 (Rx) ↔ ROTARNOCK 25pin D-Sub PIN17 (Tx RED)<br />
| |
| − | PC PIN3 (Tx) ↔ ROTARNOCK 25pin D-Sub PIN18 (Rx RED)<br />
| |
| − | PC PIN5 (GND) ↔ ROTARNOCK 25pin D-Sub PIN25 (GND)
| |
| − | | |
| − | A corresponding programming cable (including plug-in power supply) is to be ordered with the article number V3467.
| |
| − | | |
| − | The software WINLOC32 has to be installed on th PC. The interface parameters are entered in "Extras → Options → Port".
| |
| − | | |
| − | If the ROTARNOCK is now supplied with voltage a window opens automatically and the device brings its start-up message, e. g.:
| |
| − | '''R100-48-O4096-PB(126)-232 V3.54 Ok'''
| |
| − | Now place in WINLOC32 the cursor behind the last character (through a "left click") and press "n" while keeping the keys "STRG/CTRL" pressed.
| |
| − | The following confirmation prompt appears:
| |
| − | '''Ident-Nr=3606H, change to 3231H (Y/N)? N'''
| |
| − | This query has to be confirmed with "'''y'''" within 3 seconds and the following confirmation appears:
| |
| − | '''New Ident-Nr = 3231H'''
| |
| − | After a re-start the device uses the new Ident Number and it can be put into operation.
| |
| − | | |
| − | The same way the Ident Number can also be changed back from 3231H to 3606H.
| |
| − | | |
| − | ==== How do I replace a ROTARNOCK1/2/3/4 by a ROTARNOCK100? ====
| |
| − | There are two ways to carry out the exchange.
| |
| − | | |
| − | '''1.'''
| |
| − | Exchange with the convenient programming software for cam controls WINLOC32 (recommended procedure):
| |
| − | Read out (File->Upload) the ROTARNOCK that is to be replaced with the software WINLOC32 and store (File->Save) it on the hard disk or open an existing configuration file. Change from the current view to the view device configuration by clicking on the lettering Configuration on the left side of the configuration file. Activate all selection buttons on the right side. Please write down the following values provided that they are indicated:
| |
| − | Encoder resolution, ITC (=idle time compensation) Type, Display factor, ITC Function, Turn Direction, Run-Control and Zero shift.
| |
| − | Important: Please write down the indicated position during downtime (best in the basic position if possible) before removing the old device!
| |
| − | Connect the ROTARNOCK100 now and carry out an upload or open an existing configuration file. Both, the ROTARNOCK 100 as well as the available configuration file should be unused, otherwise a configuration is not possible. How to set the ROTARNOK100 back in default mode can be found here. Change the current view by clicking on the lettering Configuration. Carry out the configuration now by clicking on Device Reconfiguration on the window's right side. Enter the value for the Virtual Resolution here and select the ITC Type and confirm it with OK. Change to the configuration view again and activate all selection buttons on the right side. Transfer those values from the old ROTARNOCK, you have written down before, to the new device. Provided that you have written down the value RunControl=yes, you have to set the Run-Control-output to I/O16 and the Run-Control-type to blink!
| |
| − | '''Important advice:'''
| |
| − | Depending on the application's construction there are different safety mechanisms. If you continue to transfer the cam values now and to download the complete program into the ROTARNOCK the outputs are directly active in dependence on the position and the cam values. This might lead to an unintentional "failure/scrap" of the application.
| |
| − | We recommend to carry out the zero adjustment first before the cams are being transmitted to the device.
| |
| − | Load the newly generated configuration in the ROTARNOCK100 through Download. Install the ROTARNOCK100 now and change the zero shift offset's value, until (or change the axis mechanically) the currently displayed position is the same as the one you have written down before. There are many different possibilities to carry out the zero adjustment. Sometimes they are also combined. Therefore please carry out an update again after the adjustment.
| |
| − | In WINLOC32 the cam values, idle times and output names are transmitted from the old configuration file to the new one through Extras -> Data transfer. This function is only available in the Comfort version of WINLOC32.
| |
| − | We are pleased to help you transmitting the data also without the Comfort version. To do so, please send an e-mail with both configuration files to hotline@deutschmann.de.
| |
| − | After the data has been transmitted and verified, the complete file can be saved now and loaded into the device. With it the exchange is completed.
| |
| − | | |
| − | '''2.'''
| |
| − | Exchange with manual configuration and programming with TERM6 or TERM24 (with current Firmware):
| |
| − | The following information on the ROTARNOCK that is to be exchanged should be available:
| |
| − | Encoder resolution, type of idle time, turn direction, indicated position before removing the old device (best in the basic position) as well as all cam values and idle times.
| |
| − | Advice: In case your old device features the option R - RunControl, then the device has to be configured with WINLOC32.
| |
| − | Carry out the exchange. Set the (virtual) encoder resolution and the idle time accordingly via the terminal now. The procedure is described in the corresponding manual. After that the adaptation of the sense of rotation, if necessary, occurs and after that the adjustment of the zero point. The TERM is supposed to indicate the same position as before the exchange. Now you can start entering the cams and idle times and finally the application can be tested and be put into operation.
| |
| − | Note: Even though this procedure sounds to be short and simple you have to proceed very carefully. To enter a lot of cams is much more time-consuming than the procedure with WINLOC32.
| |
| − | | |
| − | ===Software tools===
| |
| − | ====Configuration- and programming-software for cam controls?====
| |
| − | A configuration- and programming-software WINLOC32 is available for all Deutschmann cam controls (NS).
| |
| − | The basic version of that software is available free of charge (in the download-area and on the support CD). This basic version already features extensive functions. The cam control can be read out, configured and programmed. Also these files can be stored. By means of a »key« available against charge the comfort functions will be activated (online function, comfortable copying and displacing of programs....). A license that was purchased once is valid for all existing and following versions of the program.
| |
| − | Cam controls with RS232-interface can directly be connected with the PC's COM-interface (see corresponding instruction manual for the cable connection). The cam control's signal TxD has to be wired with the PC's signal Rx and vice versa. The GND has to be wired as well.
| |
| − | For cam controls with DICNET(485)-interface a DICADAP3 has to be used in order to connect the device with the PC. At the same time the DIC+ and DIC- wires are interconnected.
| |
| − | | |
| − | ====How and where do I enter the WINLOC32 comfort version license key?====
| |
| − | First of all start WINLOC32.
| |
| − | In the menu line "Extras" -> select "Options". A window opens. If necessary please change to the register "License".
| |
| − | Now enter the license key you received from us.
| |
| − | Note: When you start to enter the key the line "licence code valid" is displayed in red. If the key is entered correctly, then it turns to green. Each entered character is displayed as "*".
| |
| − | A license that have been purchased once can be used for all follow-up versions. A WINLOC16 license also works with WINLOC32.
| |
| − | | |
| − | == UNIGATE ==
| |
| − | ===How do I carry out a Firmware-update at UNIGATE?===
| |
| − | The following conditions have to be fulfilled in order to carry out the update:
| |
| − | | |
| − | * The physical connection between the PC and UNIGATE has to be established. Here the application interface has to be connected with one of the PC's COM-ports and also the UNIGATE has to be supplied with voltage +24V GND
| |
| − | | |
| − | Rx (UNIGATE) <-> PIN 3 at the 9 pole Sub-D (PC-side)
| |
| − | | |
| − | Tx (UNIGATE) <-> PIN 2 at the 9 pole Sub-D (PC-side)
| |
| − | | |
| − | GND RS (if existing) - otherwise GND <-> PIN 5 at the 9 pole Sub-D (PC-side)
| |
| − | | |
| − | * The software FDT.exe has to be available on the PC
| |
| − | | |
| − | * The device-dependent Firmware has to be available | |
| − | | |
| − | Realization of the update:
| |
| − | | |
| − | # Start the software FDT and select the COM-interface to which the UNIGATE is connected under ''Options -> Settings''.
| |
| − | # Set the rotary switches S4 + S5 at UNIGATE RS, UNIGATE SC and UNIGATE CL to "FF", at UNIGATE IC set the config-PIN in order to place the device into the config-mode.
| |
| − | # Supply the UNIGATE with power now. In the main view of the software FDT the device's actuation message has to appear now.
| |
| − | # Now press the button ''Firmware Download'', confirm the warning message with OK and carry out the following steps.
| |
| − | | |
| − | In case of problems, please download the instructions for the Firmware update from the dowload area to your PC. There you will find detailed information, such as screenshots and suggested solutions for problems.
| |
| − | | |
| − | ===I encountered problems with the RS232 connection between UNIGATE and PC. What can I do when WINGATE says "no Gateway found"?===
| |
| − | If the UNIGATE sends a message, but WINGATE says "no Gateway found", the Rx line is not properly connected to the UNIGATE. Check the line with a meter (DVM): between GND and Rx = 7 V, as well as GND and Tx = 7 V. The 7 V may vary between 6 and 9 V, but have to be equal on one unit. If one of the two connections is 0 V, Rx and Tx are switched or connected incorrectly.
| |
| − | | |
| − | ===Is Deutschmann providing test devices for testing?===
| |
| − | We have the longstanding rule that if a customer buys a device, he has a general right of return of 30 days.
| |
| − | | |
| − | ===How do I set the UNIGATE into the configuration mode (Configmode)?===
| |
| − | For all Deutschmann UNIGATE devices (except UNIGATE CL & UNIGATE IC) the interface switch has to be set to "RS232" and the two rotary switches S4+S5 must be set to "FF" on the serial side.
| |
| − | For the UNIGATE CL the RS232 interface is automatically active throught the switch positions of S4+S5 with "FF".
| |
| − | If you use the UNIGATE IC the basis board of the J17.
| |
| − | | |
| − | After a reboot of the device, the device sends the switch-on message in a terminal program (eg WINGATE) via the application interface (NOT DEBUG)
| |
| − | Nach einem Neustart des Gerätes bringt das Gerät über die Applikationsschnittstelle (NICHT DEBUG!) die Einschaltmeldung in einem Terminalprogramm (z.B. WINGATE):
| |
| − | | |
| − | ''IC-PB-SC PV5.9B[30] (c)dA Script(2k)="Leer" Author="Deutschmann Automation GmbH" Version="1.0" Date=21.08.2001 SN=xxxxxxxx ID=1''
| |
| − | Configmode...
| |
| − | | |
| − | Now you know that the unit is in configuration mode.
| |
| − | | |
| − | '''Practice Tip:''' With UNIGATE CL, RS and SC the configuration mode is visually indicated by the RS-"State" LED flashing red.
| |
| − | | |
| − | === What do I have to consider when I switch to UNIGATE CL from UNIGATE SC? ===
| |
| − | There is one significant difference between a SC and a CL: the SC devices have a hardware switch "232 <-> 485", which does not exist on a CL. The CL on the other hand has all interfaces (232/485/422) on board. You still have to consider that if you don't run the RS, you have to run an extra Set(RS_Type,[?]) command.
| |
| − | In the PROFIBUS version there is also the difference of the ID number. The UNIGATE CL-DP needs the GSD file UGIC3218.gsd.
| |
| − | | |
| − | === Does the UNIGATE IC support SPI?===
| |
| − | Yes, the UNIGATE IC supoorts SPI. (Up-to-date [http://www.deutschmann.de/de/produkte/download.php?file_id=412 UNIGATE IC Pinout-List] in XLS Format)
| |
| − | Pin 3...7 are for the SPI Master (SPI slave on request only)
| |
| − | We support 2 different SPI functions: SPI Slow and SPI normal. For SPI Slow you can use the example "example_SPI_slow.dss". For SPI normal, the example "example_SPI.dss" is available (not available for FIDO based Hardware: PROFINET, EtherNet/IP). For FIDO based hardware you can make use of the example "example_SPI_Pinout_Real.dss". I2C is currently not supported.
| |
| − | | |
| − | ===How can I connect two networks(PROFIBUS / PROFINET)?===
| |
| − | To establish a connection between two networks (PROFIBUS / PROFINET) you can use a UNIGATE CX. In the delivery state the default setting makes for a transparent data exchange between the two fieldbus systems.
| |
| − | You have to keep in mind that the UNIGATE CX works as a slave, which means the Master must take over the communication in every network.
| |
| − | | |
| − | ===Fieldbus===
| |
| − | ====CANopen====
| |
| − | =====UNIGATE CO (M)-PROFIBUS DP=====
| |
| − | =====I encountered problems after downloading the existing/old GWC-file into my new device. Can you list the various steps?=====
| |
| − | #Open the desired GWC file with the configuration tool WINGATE.
| |
| − | #Then start the new device and perform the download
| |
| − | #Now perform an Upload from the device
| |
| − | #The parameter "CAN baud rate" is now at 125k.
| |
| − | #If the baudrate is set using the DIP switch you have to change the parameter. Therefor the parameter has to be selected. By double-clicking a window opens in which the "DIP switch" has to be selected.
| |
| − | #Afterwards perform another download
| |
| − | #Save the change, respectively the "new" GWC file
| |
| − | | |
| − | In a further download of these "new" GWC files into a new device the "CAN baud rate" parameter is now set accordingly and doesn't have to be changed again.
| |
| − | | |
| − | =====How do I replace CANopen (Master) - PROFIBUS DP (Slave)?=====
| |
| − | #Start WINGATE:
| |
| − | #Connect the RS232 from PC to UNIGATE (3 wire, 3 pin connector)
| |
| − | #Connect power supply
| |
| − | #Upload file
| |
| − | #Save file
| |
| − | #Disconnect the old UNIGATE
| |
| − | #Connect the new UNIGATE (see Step 1)
| |
| − | #Afterwards click "File - Download" (write to device)
| |
| − | | |
| − | | |
| − | <gallery>
| |
| − | Datei:Start WINGATE V2.65(379).png|1. Start WINGATE
| |
| − | Datei:WINGATE_V2.64(379)_Versorgungsanschluss.png|3. Connect power supply
| |
| − | Datei:WINGATE_V2.65(379)_File_upload.png|4. File upload
| |
| − | Datei:WINGATE_Save_as.png|4. Save as
| |
| − | Datei:WINGATE_V2.65(379)_File_download_screen.png|8. File-Download
| |
| − | </gallery>
| |
| − | | |
| − | =====In WINGATE-File the Adresse 0x14 is set to 0=====
| |
| − | With the new Firmware V2.60 in WINGATE the config file has to be stored with the setting "baud rate: DIP Switch"
| |
| − | | |
| − | ====DeviceNet====
| |
| − | =====How much power does the UNIGATE IC draw at the DeviceNet power supply 24 Volt connector, PIN 17?=====
| |
| − | The current consumption is max. 35mA.
| |
| − | | |
| − | ====EtherNet/IP====
| |
| − | =====How do I switch to EtherNet/IP 2Port?=====
| |
| − | [[UNIGATE_CL-EtherNet/IP/en#Changeover_to_2-Port-devices|Changeover to 2-Port devices]] | |
| − | | |
| − | Explanation: [[UNIGATE_CL-EtherNet/IP/en#Address_Conflict_Detection|Address Conflict Detection]]
| |
| − | | |
| − | [http://en.wikipedia.org/wiki/Quality_of_service]:[[UNIGATE_CL-EtherNet/IP/en#Option_QoS|Option_QoS]] | |
| − | | |
| − | ===== Why does the function <code>ReadNewObjectDataEIP</code> show a change of input data, altough all of the data is identical? =====
| |
| − | In the cyclic data packets a counter value is also transmitted besides the payload. This counter can be incremented into every cycle by the SPS, or only if a change of payload occurs. The command <code>ReadNewObjectDataEIP</code> indicates a change if the counter value changes.
| |
| − | | |
| − | ===== Can I only transfer an even number of bytes with an EtherNet/IP device? =====
| |
| − | No, as of firmware version 4.0 the number of transferredd bytes per cycle can also be odd (e.g. 7 byte Input, 3 byte Output).
| |
| − | | |
| − | =====Can a power supply separation be avoided through a script adaptation in a UNIGATE EtherNet/IP with firmware 4.0?=====
| |
| − | The UNIGATE has to be restarted after setting the IP address via "Set(FieldbusID,". Unfortunately, from a programm technology perspective there is no other way, since the IP address is already read from the EEROM area when booting to start the Ethernet part of the Fieldbusstacks. Only if this part is started correctly our application begins (i.e. the script).
| |
| − | | |
| − | ====Fast Ethernet====
| |
| − | =====Is there an example of the web server functionality ?=====
| |
| − | Yes, there is an example, which is available after installing the PROTOCOL DEVELOPER.
| |
| − | # Start the UNIGATE CL-FE in configmode
| |
| − | # Reset device (WINGATE - options - reset device)
| |
| − | # Save the script example: Wingate – File – Write script ... :\Software\ProtocolDeveloper\Example\08 Bus specific\Fast Ethernet script.dcs
| |
| − | # Set the IP address and the subnet mask (Do not forget to download the file)
| |
| − | # Start the UNIGATE in Run mode (S4+5 not FF and not EE)
| |
| − | # Start a FTP Client, such as [http://www.ghisler.com/index.htm Total Commander]. Establish a FTP connection. (Username and password: deutschmann)
| |
| − | # Directory: Flash
| |
| − | # Copy "index.html" to CL-FE
| |
| − | # Start your browser and enter the IP address you created in WINGATE
| |
| − | # If you refresh your browser (F5) you will see that the numerical value increased
| |
| − | # That's it!
| |
| − | | |
| − | <gallery>
| |
| − | Datei:WINGATE V2.72(385) Set IP Adress set subnet mask.png|4. IP address and subnet mask
| |
| − | Datei:FTP TotalCommander Connection details.png|6. FTP Client
| |
| − | Datei:FTP TotalCommander Verzeichnis flash.png|7. Change directory
| |
| − | Datei:FTP TotalCommander Copy index.png|8. Copy index.html
| |
| − | Datei:WINGATE FTP Browser.png|9. IP address in Browser
| |
| − | </gallery>
| |
| − | | |
| − | =====Is the temperature range down to -40°C by now available for CL devices with RJ45 connectors?=====
| |
| − | We did not make changes to the CL. We only have the statement of the manufacturer that -40°C are no problem if there are no plug connections made at these temperatures.
| |
| − | In our expansion card for CL and FC a RJ45 for -40°C is used.
| |
| − | | |
| − | ====PROFIBUS====
| |
| − | =====How can I use the UNIGATE IC PROFIBUS DPV1 5V without driver 485 and how much current can the DC/DC converter provide on the fieldbus side?=====
| |
| − | Deutschmann uses 1W-DC/DC converter, which can be supplied at 5V with 200mA. On the board without driver we need much less than 50mA of these 200mA, which means 150mA remain for the user. These are certainly adequate.
| |
| − | | |
| − | =====Changing of the Slave ID via SPS=====
| |
| − | ID is stored in EEROM.
| |
| − | <source lang="delphi">
| |
| − | var LBusState : Long ;
| |
| − | var L0xE0 : Long ; moveconst ( L0xE0, 0xE0);
| |
| − | | |
| − | BusStart ;
| |
| − | //Wait ( Bus_Active ) ;
| |
| − | | |
| − | :LoopBusState;
| |
| − | Get ( ReadBusState , LBusState ) ;
| |
| − | if LBusState less L0xE0 then :LoopBusState; //!!! neu
| |
| − | </source>
| |
| − | | |
| − | =====GSD Datei - How to create a different configuration?=====
| |
| − | [[Datei:PB_GSD_Configuration_telegramm_8_Word_Out.jpg|thumb|Create a configuration]] | |
| − | | |
| − | It is also possible in some configuration tools, like Step 7, to use a “Universal Modul”, this is not mentioned in the GSD file. It seams this is a special feature.
| |
| − | In this Modul, you can setup every size.
| |
| − | | |
| − | =====How do I set the Slave ID via the Master?=====
| |
| − | If the Slave ID is set via a Master and the MSB is also set ("Slave address can not be changed anymore"), the flag can only be reset through a "Reset Device" in the configuration mode in WINGATE.
| |
| − | | |
| − | WARNING: With it the EEROM will be re-initialized and the script will be deleted.
| |
| − | | |
| − | ====PROFINET====
| |
| − | =====Can I rename the GSDML file?=====
| |
| − | The GSDML file can not be renamed. The file name of the GSDML file is also stored in the file itself. If you now rename the file, the original file name is retained in the file. Using this renamed GSDML file, the system reports that the inserted file can not be included because it does not correspond to the valid format.
| |
| − | | |
| − | =====Why can't I assign a device name to my UNIGATE?=====
| |
| − | For PROFINET the device name is subject to a [[PROFINET Gerätename|naming convention]]. For example, the use of capital letters is not allowed.
| |
| − | | |
| − | =====How can I connect Deutschmann PROFINET devices to a S7?=====
| |
| − | PDF Download in German/English [http://deutschmann.de/produkte/download.php?file_id=681]
| |
| − | | |
| − | =====Script with station name=====
| |
| − | [[Datei:PN_Script_mit_Stationsname_Set_device.png|thumb|Script with station name]]
| |
| − | A BusStart has to be done in the script, then the name will be passed to the stack and appear in the PROFINET Master. However, the name is only given temporarily. Meaning, if the UNIGATE will be started in the config mode, the name will be taken from the file devname.txt.
| |
| − | If a name is then set in the PROFINET Master it is effective from now on.
| |
| − | | |
| − | ===Series===
| |
| − | | |
| − | ===PROTOCOL DEVELOPER===
| |
| − | ===WINGATE===
| |
