https://wiki.deutschmann.de/api.php?action=feedcontributions&user=Reith&feedformat=atomDeutschmann Wiki - Benutzerbeiträge [de-formal]2024-03-29T11:08:08ZBenutzerbeiträgeMediaWiki 1.34.0https://wiki.deutschmann.de/index.php?title=Operating_TERM_5,_TERM_6,_LOCON_16,_LOCON_17&diff=3461Operating TERM 5, TERM 6, LOCON 16, LOCON 172019-10-17T13:49:43Z<p>Reith: /* Programming */</p>
<hr />
<div>== Configuration ==<br />
[[Datei:Parametertabelle.png|thumb|Parameter table]]<br />
The here described configuration is '''only''' valid for cam controls [[LOCON 90 (English)|LOCON 90]], [[LOCON 100 (English)|LOCON 100]], [[LOCON 200 (English)|LOCON 200]], [[ROTARNOCK 80 (English)|ROTARNOCK 80]] and [[ROTARNOCK 100 (English)|ROTARNOCK 100]], which is done by [[TERM 6 (English)|TERM 6]]. [[LOCON 16 (English)|LOCON 16]] and [[LOCON 17 (English)|LOCON 17]] can '''only''' be configured by factory.<br />
<br />
'''Reading and changing cam control parameters'''<br />
All cam control parameters that can be reached via the communication profile with GET/SET-PARAMETER can be read and changed via a “menu point“ that is integrated in TERM 6.<br /><br />
'''Procedure:'''<br />
#Starting from the main menu the keys '''+''' und '''-''' are pressed '''long''' for the same time period.<br />
#Thereupon the function LED shines and a '''1''' (current parameter number) appears on the very right side of the TERM 6 display. <br />
#Now this number can by changed by the keys '''+''' or '''-''' corresponding to the wanted parameter.<br />
#Please see parameter table in the corresponding manual. '''Change of virtual encoder resolution'''<br />
For instance please find here the change of the virtual encoder resolution.<br />
#If the virtual encoder resolution is to be read/changed, please select (see parameter table in the manual communication profile) the corresponding parameter number '''19''' (corresponds 13H = PNR_SCALED_ENCODER_RES).<br />
#Confirm with key '''Enter''' and the virtual encoder resolution of the connected cam control is displayed (e.g. '''4096''').<br />
#If you want to change this value, please press the key '''Enter''' again '''long''' , until the '''Prog.Mode LED''' and the '''Function LED''' starts to flash.<br />
#Now the value cany be changed with the keys '''+''' or '''-''' (e.g. '''1000'''). <br />
#By pressing again the key '''Enter''' the new value is loaded into the cam control.<br />
#The value is rejected by pressing the key '''Esc'''.<br />
'''Note'''<br />
The following error messages may appear in case of incorrect use during configuration:<br />
*'''E34:''' change of the parameter not allowed<br />
*'''E36:''' parameter dos not exist<br />
*'''E37:''' Programming of an angle-time-cam larger than '''Output 16''' ('''Output 8''' only ROTARNOCK 80)<br />
The parameter table can be found in the manuals of LOCON 90, LOCON 100, LOCON 200, ROTARNOCK 80 und ROTARNOCK 100. Here for example the parameter table of the manual ROTARNOCK 100.<br />
<br />
== Programming ==<br />
[[Datei:Kurzbedienungsanleitung.png|thumb|Brief Instruction "Programming"]]<br />
Please find here an example how to program via the 4-key control panel in program 1, output 1 a cam from 100 to 200.<br /><br />
'''Procedure:'''<br />
#By pressing the key '''Mode/Esc''' you can go to the program selection.<br />
#With the keys '''+''' und '''-''' you can choose the wanted program (e.g. Program '''1'''). Please confirm by pressing '''Enter'''.<br />
#Thereupon you can select by pressing the keys '''+''' and '''-''' the wanted output (e.g. output '''1'''). This output has to be confirmed by pressing the key '''Enter'''.<br />
#Please press again the key '''Enter''' long until '''Prog. Mode LED''' and '''On LED''' start flashing.<br />
#By using the keys '''+''' und '''-''' the switch-on-point can be programmed now (e.g. '''100'''). Please confirm by pressing the key '''Enter'''.<br />
#Now start flashing '''Prog. Mode LED''' and '''Off LED'''. By using the keys '''+''' and '''-''' the switch-off-point can be programmed now (z.B. '''200'''). Again please confirm by pressing the key '''Enter'''.<br />
#By pressing the key '''Mode/Esc''' you can leave the programming of the output resp. the otput itself and the selected program ( in this order).<br />
A short manual regarding the programming is to be found in the manuals of [[LOCON 7 (English)|LOCON 7]], [[LOCON 9 (English)|LOCON 9]], LOCON 16, LOCON 17, LOCON 90, LOCON 100, LOCON 200, [[ROTARNOCK 1 (English)|ROTARNOCK 1]], [[ROTARNOCK 2 (English)|ROTARNOCK 2]], [[ROTARNOCK 3 (English)|ROTARNOCK 3]], [[ROTARNOCK 4 (English)|ROTARNOCK 4]], ROTARNOCK 80 und ROTARNOCK 100. Her as an example the short manual-programming for ROTARNOCK 100, originating from the manual of ROTARNOCK 100.<br />
<br />
== Program Change ==<br />
Please find here an example how to change from program 0 to program 1 via the 4-key control panel.<br /><br />
#By pressing the key '''Mode/Esc''' you will reach the program selection. The active program is displayed (e.g. „'''P 0'''“ for program '''0''').<br />
#By pressing the keys '''+''' and '''-''' you may select the desired program (e.g. „'''P 1'''“ for program '''1'''). <br />
#In order to activate the selected program, you have to press the key '''Enter''' for a longer time. In the display will appear '''PG CHG''' (Programm Changed).<br />
#Thereafter please press the key '''Enter''' again for a longer time, only then the selected program is the active program.<br />
<br />
== Initialisation ==<br />
[[Datei:Kurzbedienungsanleitung Initialisierung.png|thumb|Brief Instruction "Initialisation"]]<br />
===Zero-point offset===<br />
'''Example:''' Your plant is mechanically already in position '''0''' . The new encoder is only to be set in the same position with a lot of work and effort. Via the 4 keys of the control panel the zero-point offset maybe handled in an easy way in a few steps without positioning the encoder with an effort. <br />
Please find here a description how to program a zero-point offset.The actual encoder position (e.g.'''315''') is not of importance. <br /><br />
'''Procedure:'''<br />
#Please press long the key '''-''' until the '''Zero LED''' lights. The value displayed is changing from the actual encoder position (z.B. '''315''') to position '''0'''. <br />
#Please press now long the key '''Enter''' until '''Prog.Mode LED''' and '''Zero LED''' are flashing.<br />
#Now you can program the desired encoder position by using the keys '''+''' and '''-''' (e.g. '''0'''). <br />
#Please confirm this value by pressing the key '''Enter''' , then the programmed value is stored in the cam control.<br />
#The display shows now the acutal encoder position '''0'''.<br />
<br />
'''Note:''' This example is valid only for a cam control where '''no''' zero-Point offset is yet programmed.<br />
<br />
===Inverting the rotational direction of the absolute encoder===<br />
By factory setting all cam controls have a rotational direction '''clockwise'''.<br />
Please find here a description how to program the inversion of the rotational direction. <br /><br />
'''Procedure:'''<br />
#The key '''+''' has to be pressed long until '''Prog.Mode LED''', '''Zero LED''' and '''Function LED''' are flashing. Now the display shows '''0000'''.<br />
#Now the inversion of the rotational direction can be done by pressing the key '''-''', clockwise ('''0000''') and anti-clockwise '''(0001)'''.<br />
#This change is confirmed by pressing the key '''Enter'''. <br />
#By using the key '''ESC''' you return to the normal mode.<br />
#Done. <br />
A short manual regarding the initialisation can be found in the manuals of LOCON 7, LOCON 9, LOCON 16, LOCON 17, LOCON 90, LOCON 100, LOCON 200, ROTARNOCK 1, ROTARNOCK 2, ROTARNOCK 3, ROTARNOCK 4, ROTARNOCK 80 und ROTARNOCK 100. Please find here as an example the short manual for initalisation originating from the ROTARNOCK 100 manual.<br />
<br />
== Interfaces ==<br />
'''Available interfaces'''<br />
All devices are featuring a '''RS232''' and a '''RS485 ([[DICNET (English)|DICNET]])''' interface. By factory setting it is always set to '''RS485 (DICNET)''' interface. The interface can be switched manually. At the bottom site of the device is to be found a sticker with the imprint '''Interface'''. Under this sticker a microswitch is to be found to change the interface as desired.<br />
<br />
== Weblinks ==<br />
*[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/LOCON%2016_17/English/LOCON_16_17_e.pdf Manual for LOCON 16, LOCON 17 und TERM 6] (PDF-file)<br />
*[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/ROTARNOCK1-4,MT,PB/English/Rotarnock_e.pdf Manual for TERM 5] (PDF-file)</div>Reithhttps://wiki.deutschmann.de/index.php?title=Operating_TERM_5,_TERM_6,_LOCON_16,_LOCON_17&diff=3460Operating TERM 5, TERM 6, LOCON 16, LOCON 172019-10-17T13:49:24Z<p>Reith: /* Programming */</p>
<hr />
<div>== Configuration ==<br />
[[Datei:Parametertabelle.png|thumb|Parameter table]]<br />
The here described configuration is '''only''' valid for cam controls [[LOCON 90 (English)|LOCON 90]], [[LOCON 100 (English)|LOCON 100]], [[LOCON 200 (English)|LOCON 200]], [[ROTARNOCK 80 (English)|ROTARNOCK 80]] and [[ROTARNOCK 100 (English)|ROTARNOCK 100]], which is done by [[TERM 6 (English)|TERM 6]]. [[LOCON 16 (English)|LOCON 16]] and [[LOCON 17 (English)|LOCON 17]] can '''only''' be configured by factory.<br />
<br />
'''Reading and changing cam control parameters'''<br />
All cam control parameters that can be reached via the communication profile with GET/SET-PARAMETER can be read and changed via a “menu point“ that is integrated in TERM 6.<br /><br />
'''Procedure:'''<br />
#Starting from the main menu the keys '''+''' und '''-''' are pressed '''long''' for the same time period.<br />
#Thereupon the function LED shines and a '''1''' (current parameter number) appears on the very right side of the TERM 6 display. <br />
#Now this number can by changed by the keys '''+''' or '''-''' corresponding to the wanted parameter.<br />
#Please see parameter table in the corresponding manual. '''Change of virtual encoder resolution'''<br />
For instance please find here the change of the virtual encoder resolution.<br />
#If the virtual encoder resolution is to be read/changed, please select (see parameter table in the manual communication profile) the corresponding parameter number '''19''' (corresponds 13H = PNR_SCALED_ENCODER_RES).<br />
#Confirm with key '''Enter''' and the virtual encoder resolution of the connected cam control is displayed (e.g. '''4096''').<br />
#If you want to change this value, please press the key '''Enter''' again '''long''' , until the '''Prog.Mode LED''' and the '''Function LED''' starts to flash.<br />
#Now the value cany be changed with the keys '''+''' or '''-''' (e.g. '''1000'''). <br />
#By pressing again the key '''Enter''' the new value is loaded into the cam control.<br />
#The value is rejected by pressing the key '''Esc'''.<br />
'''Note'''<br />
The following error messages may appear in case of incorrect use during configuration:<br />
*'''E34:''' change of the parameter not allowed<br />
*'''E36:''' parameter dos not exist<br />
*'''E37:''' Programming of an angle-time-cam larger than '''Output 16''' ('''Output 8''' only ROTARNOCK 80)<br />
The parameter table can be found in the manuals of LOCON 90, LOCON 100, LOCON 200, ROTARNOCK 80 und ROTARNOCK 100. Here for example the parameter table of the manual ROTARNOCK 100.<br />
<br />
== Programming ==<br />
[[Datei:Kurzbedienungsanleitung.png|thumb|Brief Instruction "Programming"]]<br />
Please find here an example how to program via the 4-key control Panel in program 1, output 1 a cam from 100 to 200.<br /><br />
'''Procedure:'''<br />
#By pressing the key '''Mode/Esc''' you can go to the program selection.<br />
#With the keys '''+''' und '''-''' you can choose the wanted program (e.g. Program '''1'''). Please confirm by pressing '''Enter'''.<br />
#Thereupon you can select by pressing the keys '''+''' and '''-''' the wanted output (e.g. output '''1'''). This output has to be confirmed by pressing the key '''Enter'''.<br />
#Please press again the key '''Enter''' long until '''Prog. Mode LED''' and '''On LED''' start flashing.<br />
#By using the keys '''+''' und '''-''' the switch-on-point can be programmed now (e.g. '''100'''). Please confirm by pressing the key '''Enter'''.<br />
#Now start flashing '''Prog. Mode LED''' and '''Off LED'''. By using the keys '''+''' and '''-''' the switch-off-point can be programmed now (z.B. '''200'''). Again please confirm by pressing the key '''Enter'''.<br />
#By pressing the key '''Mode/Esc''' you can leave the programming of the output resp. the otput itself and the selected program ( in this order).<br />
A short manual regarding the programming is to be found in the manuals of [[LOCON 7 (English)|LOCON 7]], [[LOCON 9 (English)|LOCON 9]], LOCON 16, LOCON 17, LOCON 90, LOCON 100, LOCON 200, [[ROTARNOCK 1 (English)|ROTARNOCK 1]], [[ROTARNOCK 2 (English)|ROTARNOCK 2]], [[ROTARNOCK 3 (English)|ROTARNOCK 3]], [[ROTARNOCK 4 (English)|ROTARNOCK 4]], ROTARNOCK 80 und ROTARNOCK 100. Her as an example the short manual-programming for ROTARNOCK 100, originating from the manual of ROTARNOCK 100.<br />
<br />
== Program Change ==<br />
Please find here an example how to change from program 0 to program 1 via the 4-key control panel.<br /><br />
#By pressing the key '''Mode/Esc''' you will reach the program selection. The active program is displayed (e.g. „'''P 0'''“ for program '''0''').<br />
#By pressing the keys '''+''' and '''-''' you may select the desired program (e.g. „'''P 1'''“ for program '''1'''). <br />
#In order to activate the selected program, you have to press the key '''Enter''' for a longer time. In the display will appear '''PG CHG''' (Programm Changed).<br />
#Thereafter please press the key '''Enter''' again for a longer time, only then the selected program is the active program.<br />
<br />
== Initialisation ==<br />
[[Datei:Kurzbedienungsanleitung Initialisierung.png|thumb|Brief Instruction "Initialisation"]]<br />
===Zero-point offset===<br />
'''Example:''' Your plant is mechanically already in position '''0''' . The new encoder is only to be set in the same position with a lot of work and effort. Via the 4 keys of the control panel the zero-point offset maybe handled in an easy way in a few steps without positioning the encoder with an effort. <br />
Please find here a description how to program a zero-point offset.The actual encoder position (e.g.'''315''') is not of importance. <br /><br />
'''Procedure:'''<br />
#Please press long the key '''-''' until the '''Zero LED''' lights. The value displayed is changing from the actual encoder position (z.B. '''315''') to position '''0'''. <br />
#Please press now long the key '''Enter''' until '''Prog.Mode LED''' and '''Zero LED''' are flashing.<br />
#Now you can program the desired encoder position by using the keys '''+''' and '''-''' (e.g. '''0'''). <br />
#Please confirm this value by pressing the key '''Enter''' , then the programmed value is stored in the cam control.<br />
#The display shows now the acutal encoder position '''0'''.<br />
<br />
'''Note:''' This example is valid only for a cam control where '''no''' zero-Point offset is yet programmed.<br />
<br />
===Inverting the rotational direction of the absolute encoder===<br />
By factory setting all cam controls have a rotational direction '''clockwise'''.<br />
Please find here a description how to program the inversion of the rotational direction. <br /><br />
'''Procedure:'''<br />
#The key '''+''' has to be pressed long until '''Prog.Mode LED''', '''Zero LED''' and '''Function LED''' are flashing. Now the display shows '''0000'''.<br />
#Now the inversion of the rotational direction can be done by pressing the key '''-''', clockwise ('''0000''') and anti-clockwise '''(0001)'''.<br />
#This change is confirmed by pressing the key '''Enter'''. <br />
#By using the key '''ESC''' you return to the normal mode.<br />
#Done. <br />
A short manual regarding the initialisation can be found in the manuals of LOCON 7, LOCON 9, LOCON 16, LOCON 17, LOCON 90, LOCON 100, LOCON 200, ROTARNOCK 1, ROTARNOCK 2, ROTARNOCK 3, ROTARNOCK 4, ROTARNOCK 80 und ROTARNOCK 100. Please find here as an example the short manual for initalisation originating from the ROTARNOCK 100 manual.<br />
<br />
== Interfaces ==<br />
'''Available interfaces'''<br />
All devices are featuring a '''RS232''' and a '''RS485 ([[DICNET (English)|DICNET]])''' interface. By factory setting it is always set to '''RS485 (DICNET)''' interface. The interface can be switched manually. At the bottom site of the device is to be found a sticker with the imprint '''Interface'''. Under this sticker a microswitch is to be found to change the interface as desired.<br />
<br />
== Weblinks ==<br />
*[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/LOCON%2016_17/English/LOCON_16_17_e.pdf Manual for LOCON 16, LOCON 17 und TERM 6] (PDF-file)<br />
*[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/ROTARNOCK1-4,MT,PB/English/Rotarnock_e.pdf Manual for TERM 5] (PDF-file)</div>Reithhttps://wiki.deutschmann.de/index.php?title=Bedienung_TERM_5,_TERM_6,_LOCON_16,_LOCON_17&diff=3459Bedienung TERM 5, TERM 6, LOCON 16, LOCON 172019-10-17T13:48:35Z<p>Reith: /* Konfiguration */</p>
<hr />
<div>== Konfiguration ==<br />
[[Datei:Parametertabelle.png|thumb|Parametertabelle]]<br />
Die hier beschriebene Konfiguration betrifft '''nur''' die Nockensteuerungen [[LOCON 90]], [[LOCON 100]], [[LOCON 200]], [[ROTARNOCK 80]] und [[ROTARNOCK 100]], die über das [[TERM 6]] durchgeführt werden kann. Die Geräte [[LOCON 16]] und [[LOCON 17]] können '''nur''' werksseitig konfiguriert werden.<br />
<br />
'''Nockensteuerungsparameter lesen und ändern'''<br />
Im TERM 6 ist ein "Menüpunkt" integriert, über den alle Nockensteuerungs-Parameter, die über das Kommunikationsprofil mit GET/SET-PARAMETER erreicht werden können, gelesen und geändert werden können. <br /><br />
'''Vorgehensweise:'''<br />
#Ausgehend aus dem Hauptmenü müssen die beiden Tasten '''+''' und '''-''' gleichzeitig '''lang''' gedrückt werden.<br />
#Daraufhin leuchtet die Function-LED und es erscheint eine '''1''' (aktuelle Parameternummer) ganz rechts in der Anzeige des TERM 6. <br />
#Über die Tasten '''+''' oder '''-''' kann diese Nummer dann entsprechend dem gewünschten Parameter geändert werden.<br />
#Die Parametertabelle ist dem jeweiligen Handbuch zu entnehmen. '''Ändern der virtuellen Geberauflösung'''<br />
Als Beispiel wird nachfolgend die Änderung der virtuellen Geberauflösung beschrieben.<br />
#Wenn die virtuelle Geberauflösung gelesen/geändert werden soll, muss zunächst der entsprechende Parameter (s. Parametertabelle im Kommunikationsprofil) die Nummer '''19''' (entspricht 13H = PNR_SCALED_ENCODER_RES) angewählt werden.<br />
#Nach der Bestätigung durch die Taste '''Enter''' wird die virtuelle Geberauflösung des angeschlossenen Nockenschaltwerks angezeigt (z.B. '''4096''').<br />
#Um den Wert zu ändern, muss die Taste '''Enter''' nochmals '''lang''' gedrückt werden, bis die '''Prog.Mode LED''' und die '''Function LED''' beginnen zu blinken.<br />
#Jetzt kann der Wert über die Tasten '''+''' oder '''-''' geändert werden (z.B. '''1000'''). <br />
#Drückt man erneut die Taste '''Enter''' wird der neue Wert im Nockenschaltwerk übernommen.<br />
#Drückt man dagegen die Taste '''Esc''' wird der neue Wert wieder verworfen.<br />
'''Hinweis'''<br />
Folgende Fehlermeldungen können bei falscher Anwendung während der Konfiguration auftreten:<br />
*'''E34:''' Ändern des Parameters nicht zulässig<br />
*'''E36:''' Parameter nicht vorhanden<br />
*'''E37:''' Bei Programmierung einer Winkel-Zeit-Nocke größer '''Ausgang 16''' ('''Ausgang 8''' nur ROTARNOCK 80)<br />
Die Parametertabelle befindet sich in den Handbüchern für das LOCON 90, LOCON 100, LOCON 200, ROTARNOCK 80 und ROTARNOCK 100. Hier beispielhaft die Parametertabelle aus dem Handbuch für ROTARNOCK 100.<br />
<br />
== Programmierung ==<br />
[[Datei:Kurzbedienungsanleitung.png|thumb|Kurzbedienungsanleitung "Programmierung"]]<br />
Nachfolgend wird beispielhaft beschrieben wie über die 4-Tasten der Bedienfront im Programm 1, Ausgang 1 eine Nocke von 100 bis 200 programmiert wird. <br /><br />
'''Vorgehensweise:'''<br />
#Über die Taste '''Mode/Esc''' gelangt man zur Programmanwahl.<br />
#Mit den Tasten '''+''' und '''-''' kann dann das gewünschte Programm angewählt werden (z.B. Programm '''1'''). Dieses muss dann mit der Taste '''Enter''' bestätigt werden.<br />
#Im Anschluss kann über die Tasten '''+''' und '''-''' der gewünschte Ausgang angewählt werden (z.B. Ausgang '''1'''). Dieser muss dann mit der Taste '''Enter''' bestätigt werden.<br />
#Die Taste '''Enter''' muss nochmals lang gedrückt werden, bis die '''Prog. Mode LED''' und die '''On LED''' beginnen zu blinken.<br />
#Über die Tasten '''+''' und '''-''' kann nun der Einschaltpunkt programmiert werden (z.B. '''100'''). Dieser muss dann mit der Taste '''Enter''' bestätigt werden.<br />
#Danach blinken die '''Prog. Mode LED''' und die '''Off LED'''. Über die Tasten '''+''' und '''-''' kann nun der Ausschaltpunkt programmiert werden (z.B. '''200'''). Dieser muss dann mit der Taste '''Enter''' bestätigt werden.<br />
#Über die Taste '''Mode/Esc''' kann die Programmierung des Ausgangs sowie der Ausgang selbst und auch das angewählte Programm (in dieser Reihenfolge) wieder verlassen werden.<br />
Eine Kurzbedienungsanleitung bzgl. der Programmierung befindet sich in den Handbüchern für das [[LOCON 7]], [[LOCON 9]], LOCON 16, LOCON 17, LOCON 90, LOCON 100, LOCON 200, [[ROTARNOCK 1]], [[ROTARNOCK 2]], [[ROTARNOCK 3]], [[ROTARNOCK 4]], ROTARNOCK 80 und ROTARNOCK 100. Hier beispielhaft die Kurzbedienungsanleitung-Programmierung aus dem Handbuch für ROTARNOCK 100.<br />
<br />
== Programmwechsel ==<br />
Nachfolgend wird beispielhaft beschrieben wie über die 4-Tasten der Bedienfront von Programm 0 zu Programm 1 gewechselt wird. <br /><br />
#Über die Taste '''Mode/Esc''' gelangt man zur Programmanwahl. Das aktive Programm wird angezeigt (z.B. „'''P 0'''“ für Programm '''0''').<br />
#Mit den Tasten '''+''' und '''-''' kann dann das gewünschte Programm angewählt werden (z.B. „'''P 1'''“ für Programm '''1'''). <br />
#Um das angewählte Programm zum aktiven Programm zu machen, muss die Taste '''Enter''' lange gedrückt werden. In der Anzeige erscheint '''PG CHG''' (Programm Changed).<br />
#Danach muss die Taste '''Enter''' erneut lange gedrückt werden. Erst dann ist das angewählte Programm das aktive Programm. <br />
<br />
== Initialisierung ==<br />
[[Datei:Kurzbedienungsanleitung Initialisierung.png|thumb|Kurzbedienungsanleitung "Initialisierung"]]<br />
===Nullpunktverschiebung===<br />
'''Beispiel:''' Ihre Anlage befindet sich mechanisch bereits in der Position '''0'''. Der neue Geber lässt sich aber nur mit Mühe und relativ großem Aufwand in die gleiche Position bringen. Über die 4-Tasten der Bedienfront kann in wenigen Schritten einfach und bequem eine Nullpunktverschiebung durchgeführt werden ohne das der Geber mühsam positioniert werden muss. <br />
Nachfolgend wird beispielhaft beschrieben wie eine Nullpunktverschiebung programmiert werden muss. Dabei ist die aktuelle Geberposition (z.B. '''315''') nicht weiter von Bedeutung. <br /><br />
'''Vorgehensweise:'''<br />
#Die Taste '''-''' muss lang gedrückt werden, bis die '''Zero LED''' leuchtet. Die Anzeige wechselt von der aktuellen Geberposition (z.B. '''315''') auf die Position '''0'''. <br />
#Danach muss die Taste '''Enter''' lang gedrückt werden bis die '''Prog.Mode LED''' und die '''Zero LED''' blinken.<br />
#Jetzt kann mit den Tasten '''+''' und '''-''' die gewünschte Geberposition (z.B. '''0''') eingestellt werden. <br />
#Anschließend wird der Wert mit der Taste '''Enter''' bestätigt und im Nockenschaltwerk gespeichert.<br />
#In der Anzeige erscheint nun die aktuelle Geberposition '''0'''.<br />
<br />
'''Hinweis:''' Das Beispiel bezieht sich auf eine Nockensteuerung, bei der noch '''keine''' Nullpunktverschiebung programmiert worden ist.<br />
<br />
===Drehrichtungsumkehr===<br />
Im Auslieferungszustand haben die Nockensteuerungen die Drehrichtung '''im Uhrzeigersinn'''.<br />
Nachfolgend wird beschrieben wie eine Drehrichtungsumkehr programmiert werden muss. <br /><br />
'''Vorgehensweise:'''<br />
#Die Taste '''+''' muss lang gedrückt werden, bis die '''Prog.Mode LED''', die '''Zero LED''' und die '''Function LED''' blinken. In der Anzeige steht nun '''0000'''.<br />
#Mit der Taste '''-''' kann nun die Drehrichtungsumkehr durchgeführt werden. Im Uhrzeigersinn ('''0000''') und gegen den Uhrzeigersinn '''(0001)'''.<br />
#Mit der Taste '''Enter''' muss die Änderung noch bestätigt werden. <br />
#Mit der Taste '''ESC''' kann die Initialisierung wieder verlassen werden.<br />
#Fertig. <br />
Eine Kurzbedienungsanleitung bzgl. der Initialisierung befindet sich in den Handbüchern für das LOCON 7, LOCON 9, LOCON 16, LOCON 17, LOCON 90, LOCON 100, LOCON 200, ROTARNOCK 1, ROTARNOCK 2, ROTARNOCK 3, ROTARNOCK 4, ROTARNOCK 80 und ROTARNOCK 100. Hier beispielhaft die Kurzbedienungsanleitung-Initialisierung aus dem Handbuch für ROTARNOCK 100.<br />
<br />
== Schnittstellen ==<br />
'''Verfügbare Schnittstellen'''<br />
Die Geräte verfügen über eine '''RS232''' und eine '''RS485 ([[DICNET]])''' Schnittstelle. Im Auslieferungszustand ist immer die '''RS485 (DICNET)''' Schnittstelle eingestellt. Die Schnittstelle ist manuell umschaltbar. An der Geräteunterseite befindet sich ein Aufkleber mit dem Aufdruck '''Interface'''. Unter diesem Aufkleber befindet sich ein Schiebeschalter mit dem die Schnittstelle umgeschaltet werden kann.<br />
== Weblinks ==<br />
*[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/LOCON%2016_17/German/Locon16_17.pdf Handbuch für LOCON 16, LOCON 17 und TERM 6] (PDF-Datei)<br />
*[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/ROTARNOCK1-4,MT,PB/German/Rotarnock_1-4.pdf Handbuch für das TERM 5] (PDF-Datei)</div>Reithhttps://wiki.deutschmann.de/index.php?title=Bedienung_TERM_5,_TERM_6,_LOCON_16,_LOCON_17&diff=3458Bedienung TERM 5, TERM 6, LOCON 16, LOCON 172019-10-17T13:46:23Z<p>Reith: /* Konfiguration */</p>
<hr />
<div>== Konfiguration ==<br />
[[Datei:Parametertabelle.png|thumb|Parametertabelle]]<br />
Die hier beschriebene Konfiguration betrifft '''nur''' die Nockensteuerungen [[LOCON 90]], [[LOCON 100]], [[LOCON 200]], [[ROTARNOCK 80]] und [[ROTARNOCK 100]], die über das [[TERM 6]] durchgeführt werden kann. Die Geräte [[LOCON 16]] und [[LOCON 17]] können '''nur''' werksseitig konfiguriert werden.<br />
'''Nockensteuerungsparameter lesen und ändern'''<br />
Im TERM 6 ist ein "Menüpunkt" integriert, über den alle Nockensteuerungs-Parameter, die über das Kommunikationsprofil mit GET/SET-PARAMETER erreicht werden können, gelesen und geändert werden können. <br /><br />
'''Vorgehensweise:'''<br />
#Ausgehend aus dem Hauptmenü müssen die beiden Tasten '''+''' und '''-''' gleichzeitig '''lang''' gedrückt werden.<br />
#Daraufhin leuchtet die Function-LED und es erscheint eine '''1''' (aktuelle Parameternummer) ganz rechts in der Anzeige des TERM 6. <br />
#Über die Tasten '''+''' oder '''-''' kann diese Nummer dann entsprechend dem gewünschten Parameter geändert werden.<br />
#Die Parametertabelle ist dem jeweiligen Handbuch zu entnehmen. '''Ändern der virtuellen Geberauflösung'''<br />
Als Beispiel wird nachfolgend die Änderung der virtuellen Geberauflösung beschrieben.<br />
#Wenn die virtuelle Geberauflösung gelesen/geändert werden soll, muss zunächst der entsprechende Parameter (s. Parametertabelle im Kommunikationsprofil) die Nummer '''19''' (entspricht 13H = PNR_SCALED_ENCODER_RES) angewählt werden.<br />
#Nach der Bestätigung durch die Taste '''Enter''' wird die virtuelle Geberauflösung des angeschlossenen Nockenschaltwerks angezeigt (z.B. '''4096''').<br />
#Um den Wert zu ändern, muss die Taste '''Enter''' nochmals '''lang''' gedrückt werden, bis die '''Prog.Mode LED''' und die '''Function LED''' beginnen zu blinken.<br />
#Jetzt kann der Wert über die Tasten '''+''' oder '''-''' geändert werden (z.B. '''1000'''). <br />
#Drückt man erneut die Taste '''Enter''' wird der neue Wert im Nockenschaltwerk übernommen.<br />
#Drückt man dagegen die Taste '''Esc''' wird der neue Wert wieder verworfen.<br />
'''Hinweis'''<br />
Folgende Fehlermeldungen können bei falscher Anwendung während der Konfiguration auftreten:<br />
*'''E34:''' Ändern des Parameters nicht zulässig<br />
*'''E36:''' Parameter nicht vorhanden<br />
*'''E37:''' Bei Programmierung einer Winkel-Zeit-Nocke größer '''Ausgang 16''' ('''Ausgang 8''' nur ROTARNOCK 80)<br />
Die Parametertabelle befindet sich in den Handbüchern für das LOCON 90, LOCON 100, LOCON 200, ROTARNOCK 80 und ROTARNOCK 100. Hier beispielhaft die Parametertabelle aus dem Handbuch für ROTARNOCK 100.<br />
<br />
== Programmierung ==<br />
[[Datei:Kurzbedienungsanleitung.png|thumb|Kurzbedienungsanleitung "Programmierung"]]<br />
Nachfolgend wird beispielhaft beschrieben wie über die 4-Tasten der Bedienfront im Programm 1, Ausgang 1 eine Nocke von 100 bis 200 programmiert wird. <br /><br />
'''Vorgehensweise:'''<br />
#Über die Taste '''Mode/Esc''' gelangt man zur Programmanwahl.<br />
#Mit den Tasten '''+''' und '''-''' kann dann das gewünschte Programm angewählt werden (z.B. Programm '''1'''). Dieses muss dann mit der Taste '''Enter''' bestätigt werden.<br />
#Im Anschluss kann über die Tasten '''+''' und '''-''' der gewünschte Ausgang angewählt werden (z.B. Ausgang '''1'''). Dieser muss dann mit der Taste '''Enter''' bestätigt werden.<br />
#Die Taste '''Enter''' muss nochmals lang gedrückt werden, bis die '''Prog. Mode LED''' und die '''On LED''' beginnen zu blinken.<br />
#Über die Tasten '''+''' und '''-''' kann nun der Einschaltpunkt programmiert werden (z.B. '''100'''). Dieser muss dann mit der Taste '''Enter''' bestätigt werden.<br />
#Danach blinken die '''Prog. Mode LED''' und die '''Off LED'''. Über die Tasten '''+''' und '''-''' kann nun der Ausschaltpunkt programmiert werden (z.B. '''200'''). Dieser muss dann mit der Taste '''Enter''' bestätigt werden.<br />
#Über die Taste '''Mode/Esc''' kann die Programmierung des Ausgangs sowie der Ausgang selbst und auch das angewählte Programm (in dieser Reihenfolge) wieder verlassen werden.<br />
Eine Kurzbedienungsanleitung bzgl. der Programmierung befindet sich in den Handbüchern für das [[LOCON 7]], [[LOCON 9]], LOCON 16, LOCON 17, LOCON 90, LOCON 100, LOCON 200, [[ROTARNOCK 1]], [[ROTARNOCK 2]], [[ROTARNOCK 3]], [[ROTARNOCK 4]], ROTARNOCK 80 und ROTARNOCK 100. Hier beispielhaft die Kurzbedienungsanleitung-Programmierung aus dem Handbuch für ROTARNOCK 100.<br />
<br />
== Programmwechsel ==<br />
Nachfolgend wird beispielhaft beschrieben wie über die 4-Tasten der Bedienfront von Programm 0 zu Programm 1 gewechselt wird. <br /><br />
#Über die Taste '''Mode/Esc''' gelangt man zur Programmanwahl. Das aktive Programm wird angezeigt (z.B. „'''P 0'''“ für Programm '''0''').<br />
#Mit den Tasten '''+''' und '''-''' kann dann das gewünschte Programm angewählt werden (z.B. „'''P 1'''“ für Programm '''1'''). <br />
#Um das angewählte Programm zum aktiven Programm zu machen, muss die Taste '''Enter''' lange gedrückt werden. In der Anzeige erscheint '''PG CHG''' (Programm Changed).<br />
#Danach muss die Taste '''Enter''' erneut lange gedrückt werden. Erst dann ist das angewählte Programm das aktive Programm. <br />
<br />
== Initialisierung ==<br />
[[Datei:Kurzbedienungsanleitung Initialisierung.png|thumb|Kurzbedienungsanleitung "Initialisierung"]]<br />
===Nullpunktverschiebung===<br />
'''Beispiel:''' Ihre Anlage befindet sich mechanisch bereits in der Position '''0'''. Der neue Geber lässt sich aber nur mit Mühe und relativ großem Aufwand in die gleiche Position bringen. Über die 4-Tasten der Bedienfront kann in wenigen Schritten einfach und bequem eine Nullpunktverschiebung durchgeführt werden ohne das der Geber mühsam positioniert werden muss. <br />
Nachfolgend wird beispielhaft beschrieben wie eine Nullpunktverschiebung programmiert werden muss. Dabei ist die aktuelle Geberposition (z.B. '''315''') nicht weiter von Bedeutung. <br /><br />
'''Vorgehensweise:'''<br />
#Die Taste '''-''' muss lang gedrückt werden, bis die '''Zero LED''' leuchtet. Die Anzeige wechselt von der aktuellen Geberposition (z.B. '''315''') auf die Position '''0'''. <br />
#Danach muss die Taste '''Enter''' lang gedrückt werden bis die '''Prog.Mode LED''' und die '''Zero LED''' blinken.<br />
#Jetzt kann mit den Tasten '''+''' und '''-''' die gewünschte Geberposition (z.B. '''0''') eingestellt werden. <br />
#Anschließend wird der Wert mit der Taste '''Enter''' bestätigt und im Nockenschaltwerk gespeichert.<br />
#In der Anzeige erscheint nun die aktuelle Geberposition '''0'''.<br />
<br />
'''Hinweis:''' Das Beispiel bezieht sich auf eine Nockensteuerung, bei der noch '''keine''' Nullpunktverschiebung programmiert worden ist.<br />
<br />
===Drehrichtungsumkehr===<br />
Im Auslieferungszustand haben die Nockensteuerungen die Drehrichtung '''im Uhrzeigersinn'''.<br />
Nachfolgend wird beschrieben wie eine Drehrichtungsumkehr programmiert werden muss. <br /><br />
'''Vorgehensweise:'''<br />
#Die Taste '''+''' muss lang gedrückt werden, bis die '''Prog.Mode LED''', die '''Zero LED''' und die '''Function LED''' blinken. In der Anzeige steht nun '''0000'''.<br />
#Mit der Taste '''-''' kann nun die Drehrichtungsumkehr durchgeführt werden. Im Uhrzeigersinn ('''0000''') und gegen den Uhrzeigersinn '''(0001)'''.<br />
#Mit der Taste '''Enter''' muss die Änderung noch bestätigt werden. <br />
#Mit der Taste '''ESC''' kann die Initialisierung wieder verlassen werden.<br />
#Fertig. <br />
Eine Kurzbedienungsanleitung bzgl. der Initialisierung befindet sich in den Handbüchern für das LOCON 7, LOCON 9, LOCON 16, LOCON 17, LOCON 90, LOCON 100, LOCON 200, ROTARNOCK 1, ROTARNOCK 2, ROTARNOCK 3, ROTARNOCK 4, ROTARNOCK 80 und ROTARNOCK 100. Hier beispielhaft die Kurzbedienungsanleitung-Initialisierung aus dem Handbuch für ROTARNOCK 100.<br />
<br />
== Schnittstellen ==<br />
'''Verfügbare Schnittstellen'''<br />
Die Geräte verfügen über eine '''RS232''' und eine '''RS485 ([[DICNET]])''' Schnittstelle. Im Auslieferungszustand ist immer die '''RS485 (DICNET)''' Schnittstelle eingestellt. Die Schnittstelle ist manuell umschaltbar. An der Geräteunterseite befindet sich ein Aufkleber mit dem Aufdruck '''Interface'''. Unter diesem Aufkleber befindet sich ein Schiebeschalter mit dem die Schnittstelle umgeschaltet werden kann.<br />
== Weblinks ==<br />
*[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/LOCON%2016_17/German/Locon16_17.pdf Handbuch für LOCON 16, LOCON 17 und TERM 6] (PDF-Datei)<br />
*[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/ROTARNOCK1-4,MT,PB/German/Rotarnock_1-4.pdf Handbuch für das TERM 5] (PDF-Datei)</div>Reithhttps://wiki.deutschmann.de/index.php?title=en:Frequently_asked_questions_Fieldbus-_and_Industrial-Ethernet-Devices&diff=3457en:Frequently asked questions Fieldbus- and Industrial-Ethernet-Devices2019-08-27T14:13:30Z<p>Reith: /* How to replace ROTARNOCK 1/2/3/4 by ROTARNOCK 100? */</p>
<hr />
<div>== Electronic Cam Controls ==<br />
===Are there replacements for a product that is no longer available? (LOCON 32-HC, LOCON 32-PM)...===<br />
1. Substitution option with [[LOCON 24 (English)|LOCON 24]]:<br />
<br />
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.<br />
<br />
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.<br />
<br />
2. Substitution option with [[LOCON 100 (English)|LOCON 100]] / [[LOCON 200 (English)|LOCON 200]]:<br />
<br />
Basically the following points ALWAYS have to be clarified in case of replacing a product that is no longer available: (Example in italic)<br />
* Which encoder is used in connection with the cam control (NSW) (maximum of 16 inputs) &rarr; number of encoder inputs &rarr; at INC. at least 2, at absolute &rarr; number of tracks = number inputs)<br />
<br />
''A TA58-O360-GYE is used &rarr; 9 tracks = 9 inputs''<br />
<br />
* What other pins are used? (e. g. at INC. encoders Clear + and/or Clear- &rarr; number of inputs +1 or +2)<br />
<br />
''None &rarr; + 0 inputs''<br />
<br />
* Is the Prog.Enable wired? (if yes &rarr; number of inputs +1)<br />
<br />
''Yes. &rarr; +1 input''<br />
<br />
* Is the external program selection wired? If yes, how many programs? (number of inputs +2 ... +7)<br />
<br />
''Yes, up to program 8. 5 pins are required for it &rarr; +5 inputs''<br />
<br />
According to the amount here the decision is made, whether [[LOCON 100 (English)|LOCON 100]] or [[LOCON 200 (English)|LOCON 200]] can be used. Provided that the amount remains below 16, either a [[LOCON 100 (English)|LOCON 100]] or a [[LOCON 200 (English)|LOCON 200]] can be used. If the amount of required inputs exceeds 16, then a [[LOCON 100 (English)|LOCON 100]] 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 [[LOCON 100 (English)|LOCON 100]] or [[LOCON 200 (English)|LOCON 200]] can be used. <br />
<br />
Quantity determination of expansion modules that have to be used (LOCON 100-A32 or LOCON 200-IO8):<br />
<br />
* Is the RunControl-relay wired? If yes &rarr; number of outputs + 1<br />
<br />
''Yes. + 1 output for RunControl''<br />
<br />
* How many outputs are used at the cam control? &rarr; Number of the basis' remaining outputs (LOCON 100 + LOCON 200) = 16 - number of inputs<br />
<br />
''32 outputs are used. &rarr; Total = 1 + 32 = 33 outputs. Either LOCON 100 (1 output) with an LOCON 100-A32 extension (=32 outputs) OR LOCON 200 (1 output) + 3 x LOCON 200-IO8 (8 outputs each = 32 outputs) can be used here.''<br />
<br />
Basically the version LOCON 200 + LOCON 200-IO8 is to be favored, since the cycle times for this constellation are lower than those for LOCON 100.<br />
<br />
On principle it does not matter which TERM is used. [[LOCON 100 (English)|LOCON 100]] & [[LOCON 200 (English)|LOCON 200]] are supported by TERM 6, TERM 24 & TERM 32 to a partially limited extent. For that reason the parameterization and configuration should principally always be carried out with [[WINLOC 32 (English)|WINLOC 32]] and the mentioned TERMs should be used for operation.<br />
<br />
===How to connect a LOCON with the RS232-interface (COM port) at the PC?===<br />
At the PC COM port there is a 9-pole D-SUB pin connection with the following assignment:<br />
<br />
PIN 2 - Rx (from the PC's point of view)<br />
<br />
PIN 3 - Tx (from the PC's point of view)<br />
<br />
PIN 5 - GND<br />
<br />
Example:<br />
<br />
At the LOCON16/17 the assignment of the X2 is as follows:<br />
<br />
PIN 26 - GND<br />
<br />
PIN 27 - Rx 232 (from the LOCON's point of view)<br />
<br />
PIN 28 - Tx 232 (from the LOCON's point of view)<br />
<br />
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.<br />
<br />
For the above example it comes to the following cable assignment:<br />
<br />
LOCON X2 PIN26 &harr; PC PIN5<br />
<br />
LOCON X2 PIN27 &harr; PC PIN3<br />
<br />
LOCON X2 PIN28 &harr; PC PIN2<br />
<br />
Note:<br />
Possible existing blue bridges between the signals "DICNET-/Rx" &harr; "R-" and "DICNET+/Tx" &harr; "R+" have to be removed.<br />
<br />
===How to reset LOCON 90, LOCON 100, LOCON 100-PB, LOCON 200, LOCON 200-PB, ROTARNOCK 100 or ROTARNOCK 100-PB back to delivery condition (reset)?===<br />
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 WINLOC 32 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 LOCON 100 with an expansion LOCON 100-A32 with DICNET communication, configured as Timer with a counting range of 16):<br />
<br />
''L100-48(48)-T16-485(DICNET) V3.4''<br />
<br />
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: <br />
''Reset configuration to defaultvalue and clear all programmed data (Y/N)? N''<br />
<br />
This query has to be confirmed with "y" within 3 seconds and another safety query follows:<br />
<br />
''Cancel operation (Y/N) N'' which is to be confirmed with "n".<br />
<br />
If the entry is correct, the following message appears in the terminal window:<br />
<div style="border: 1px solid #136db9; background-color: #fafafa; padding: 8px;"><br />
''Clear EEROM 0H-1fffH ...............................<br />
<br />
Restart<br />
<br />
L100-48(48)-S4096-485(DICNET) V3.4 ok<br />
<br />
(Error: 108)''<br />
</div><br />
With it the device was set back to the condition it was originally supplied.<br />
<br />
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.<br />
Note: After a reset the optional LOGIC-function has to be activated again. At the devices LOCON 100 & LOCON 200 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.<br />
<br />
===How to activate the logic function of LOCON 100-PB, LOCON 200, LOCON 200-PB, ROTARNOCK 100 or ROTARNOCK 100-PB?===<br />
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 LOCON 100-PB, LOCON 200 or LOCON 200-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.<br />
<br />
The device to be extended by the logic function must be connected to the PC and a start-up string has to be shown WINLOC 32.<br />
<br />
With a click on the menue ''Extras &rarr; Product Option Activation'' a window opens for activation.<br />
<br />
The DICNET-ID is entered in the line Device ID. For a connection through RS232 this value remains on "0".<br />
<br />
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 &harr; PC works).<br />
<br />
The release code is entered in the line ''Activation key''. Start behind the "-".<br />
Click on ''Run'' afterwards.<br />
<br />
(In case of an error "Returncode=4" is the result.)<br />
<br />
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:<br />
<br />
L200-16-S4096-H-''LG''-232 Vx.x<br />
<br />
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:<br />
<br />
Note: After a "Clear all" the logic function has to be released again.<br />
<br />
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 LOCON 100-PB; LOCON 200(-PB) & ROTARNOCK 100(-PB)".<br />
<br />
===External Wiring===<br />
====How is the modification from LOCON 32-HC or LOCON 32-PM to LOCON 24 carried out?====<br />
Introductorily we like to point out that this description refers to a LOCON 32-HC, that is/was configured "absolute parallel 360" as encoder type. Consequently the LOCON 24 also has to contain this "O360" in the article text.<br />
<br />
{| class="wikitable"<br />
!LOCON 24 !!Signal !!LOCON 32-HC !!LOCON 32-PM<br />
|-<br />
|X1 PIN 1 ||OUT 1 ||X10 PIN 2 ||X1 PIN 1<br />
|-<br />
|X1 PIN 2 ||OUT 2 ||X10 PIN 1 ||X1 PIN 2<br />
|-<br />
|X1 PIN 3 ||OUT 3 ||X10 PIN 4 ||X1 PIN 3<br />
|-<br />
|X1 PIN 4 ||OUT 4 ||X10 PIN 3 ||X1 PIN 4<br />
|-<br />
|X1 PIN 5 ||OUT 5 ||X10 PIN 6 ||X1 PIN 5<br />
|-<br />
|X1 PIN 6 ||OUT 6 ||X10 PIN 5 ||X1 PIN 6<br />
|-<br />
|X1 PIN 7 ||OUT 7 ||X10 PIN 8 ||X1 PIN 7<br />
|-<br />
|X1 PIN 8 ||OUT 8 ||X10 PIN 7 ||X1 PIN 8<br />
|-<br />
|X1 PIN 9 ||OUT 9 ||X10 PIN 10 ||X1 PIN 9<br />
|}<br />
<br />
... [http://www.deutschmann.de/en/support/faq_detail.html?question=18 more]<br />
<br />
=== Models ===<br />
==== What has to be considered when using a LOCON 200 in connection with TERM 24? ====<br />
If a (discontinued) device is supposed to be replaced by LOCON 200 and in case TERM 24 is used in the assembly, then the TERM 24's Firmware must be updated at any rate. For the update the device has to be sent back to us.<br />
<br />
==== TN65 - ROTARNOCK - what is it? ====<br />
It is the same unit. ROTARNOCK describes the product line and TN65 is the specific type or the article description.<br />
<br />
Example:<br />
ROTARNOCK 100 - describes the ROTARNOCK-family "100". The detailed article description is explained on the picture "Article description".<br />
<br />
[[Datei:Article description Rotarnock English.jpg|thumb|Article description]]<br />
<br />
<br />
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.<br />
<br />
==== How to change the Profibus Ident Number? ====<br />
To change the Profibus Ident Number from 3606H to 3231 the ROTARNOCK 100-PB has to be connected with the PC via a serial communication (RS232). For the serial communication the following pin assignemt is valid here:<br />
<br />
PC PIN2 (Rx) ↔ ROTARNOCK 25pin D-Sub PIN17 (Tx RED)<br /><br />
PC PIN3 (Tx) ↔ ROTARNOCK 25pin D-Sub PIN18 (Rx RED)<br /><br />
PC PIN5 (GND) ↔ ROTARNOCK 25pin D-Sub PIN25 (GND)<br />
<br />
A corresponding programming cable (including plug-in power supply) is to be ordered with the article number V3467. ( V3467 - Programming cable for ROTARNOCK - 232/PB).<br />
<br />
The software WINLOC 32 has to be installed on the PC. The interface parameters are entered in "Extras → Options → Port".<br />
<br />
If the ROTARNOCK is now supplied with voltage a window opens automatically and the device brings its start-up message, e. g.:<br />
'''R100-48-O4096-PB(126)-232 V3.54 Ok'''<br />
Now place in WINLOC 32 the cursor behind the last character (through a "left click") and press "n" while keeping the keys "STRG/CTRL" pressed.<br />
The following confirmation prompt appears:<br />
'''Ident-Nr=3606H, change to 3231H (Y/N)? N'''<br />
This query has to be confirmed with "'''y'''" within 3 seconds and the following confirmation appears:<br />
'''New Ident-Nr = 3231H'''<br />
After a re-start the device uses the new Ident Number and it can be put into operation.<br />
<br />
The same way the Ident Number can also be changed back from 3231H to 3606H.<br />
<br />
==== How to replace ROTARNOCK 1/2/3/4 by ROTARNOCK 100? ====<br />
There are two ways to carry out the exchange.<br />
<br />
'''1.'''<br />
Exchange with the convenient programming software for cam controls WINLOC 32 (recommended procedure):<br />
<br />
Read out (File&rarr;Upload) the ROTARNOCK that is to be replaced with the software WINLOC 32 and store (File&rarr;Save) it on the hard disk or open an existing configuration file.<br />
<br />
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:<br />
Encoder resolution, ITC (=idle time compensation) Type, Display factor, ITC Function, Turn Direction, Run-Control and Zero shift.<br />
<br />
Important: Please write down the indicated position during downtime (best in the basic position if possible) before removing the old device! <br />
<br />
Connect the ROTARNOCK 100 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 ROTARNOCK 100 back in default mode can be found here.<br />
<br />
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.<br />
<br />
Enter the value for the Virtual Resolution here and select the ITC Type and confirm it with OK. <br />
<br />
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!<br />
<br />
'''Important advice:'''<br />
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.<br />
<br />
We recommend to carry out the zero adjustment first before the cams are being transmitted to the device.<br />
Load the newly generated configuration in the ROTARNOCK 100 through Download. Install the ROTARNOCK 100 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.<br />
<br />
In WINLOC32 the cam values, idle times and output names are transmitted from the old configuration file to the new one through Extras &rarr; Data transfer. This function is only available in the Comfort version of WINLOC 32.<br />
<br />
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 [mailto:hotline@deutschmann.de hotline@deutschmann.de].<br />
<br />
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. <br />
<br />
'''2.'''<br />
Exchange with manual configuration and programming with TERM 6 or TERM 24 (with current Firmware):<br />
<br />
The following information on the ROTARNOCK that is to be exchanged should be available:<br />
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.<br />
<br />
Advice: In case your old device features the option R - RunControl, then the device has to be configured with WINLOC 32.<br />
<br />
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. <br />
<br />
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.<br />
<br />
Now you can start entering the cams and idle times and finally the application can be tested and be put into operation.<br />
<br />
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 WINLOC 32.<br />
<br />
===Software Tools===<br />
====Configuration- and programming-software for cam controls?====<br />
A configuration- and programming-software [[WINLOC 32 (English)|WINLOC 32]] is available for all Deutschmann cam controls (NS).<br />
<br />
The basic version of that software is available free of charge (in the download-area and on the support-DVD). This basic version already features extensive functions. The cam control can be read out, configured and programmed. Also these files can be stored. <br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
====How and where is to enter the WINLOC 32 comfort version license key?====<br />
First of all start WINLOC 32.<br />
<br />
In the menu line "Extras" &rarr; select "Options". A window opens. If necessary please change to the register "License".<br />
Now enter the license key you received from us.<br />
<br />
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 "*".<br />
<br />
A license that have been purchased once can be used for all follow-up versions. A WINLOC 6 license also works with WINLOC 32.<br />
<br />
== UNIGATE ==<br />
===How to carry out a Firmware update at UNIGATE?===<br />
You can find an explanation on the site [[Firmware-Aktualisierung/en|Firmware update]].<br />
<br />
===I encountered problems with the RS232 connection between UNIGATE and PC. What to do when WINGATE says "no Gateway found"?===<br />
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.<br />
<br />
===How to connect an UNIGATE with the RS232-interface (COM port) at the PC?===<br />
At the PC COM port there is a 9-pole D-SUB pin connection with the following assignment:<br />
<br />
PIN 2 - Rx (from the PC's point of view)<br />
<br />
PIN 3 - Tx (from the PC's point of view)<br />
<br />
PIN 5 - GND<br />
<br />
Example: At the UNIGATE CL the assignment of the X1 is as follows:<br />
<br />
PIN 1 - Rx 232 (from the UNIGATE's point of view)<br />
<br />
PIN 2 - Tx 232 (from the UNIGATE's point of view)<br />
<br />
PIN 3 - AP-GND<br />
<br />
Generally always the Rx of the PC has to be connected with the Tx of the UNIGATE and the Tx of the PC with the Rx of the UNIGATE. Also the GND always has to be connected.<br />
<br />
For the above example it comes to the following cable assignment:<br />
<br />
UNIGATE X1 PIN1 &harr; PC PIN3<br />
<br />
UNIGATE X1 PIN2 &harr; PC PIN2<br />
<br />
UNIGATE X1 PIN3 &harr; PC PIN5<br />
<br />
===Does UNIGATE have a "test mode"?===<br />
Yes, there is a test mode.<br />
<br />
The interface-switch has to be set to position »RS232« and the two rotary coding switches on the serial side (S4 + S5) have to be set to »EE« in order to put the device into the test mode.<br />
<br />
After the restart the UNIGATE sends a byte on the serial side from »0-F« every second (some devices will first do a 15 to 30 seconds lasting self test). On the Fieldbus this output occurs accordinglywith the length depending on the set bus width. If useful data is sent to the UNIGATE (serial and Fieldbus) they are sent back from the UNIGATE (ECHO).<br />
<br />
===How to get my script into the device?===<br />
'''Advice:''' Please always use the current version of the corresponding software.<br />
<br />
Basically there are two ways to load the script into the UNIGATE.<br />
<br />
'''Possibility 1''' - via the serial (application-) interface: (applies to ALL UNIGATE SC, IC & CL) The script has to be compiled in the PROTOCOL DEVELOPER by "File &rarr; save compiled file" (the script receives the file extension *.dcs), so that the script gets into the device this way. The device has to be set into the configuration mode in order to load the script into the device. The script download can be started with the software WINGATE through "File &rarr; Write Script". With the software SPT (ScriptProgramTool) the downlaod is initiated through "File &rarr; Open file and program".<br />
<br />
'''Possibility 2''' - via the DEBUG-interface and the software PROTOCOL DEVELOPER: (applies to ALL UNIGATE IC & CL as well as UNIGATE SC with option "DB") In this case the device's DEBUG-interface has to be connected with a PC COM-Port. In the software PROTOCOL DEVELOPER and belated power up of the device (NOT in the configuration mode) the message "Device started in Debug mode" appears in the bottom left corner. Now the download can be started with "DEBUG".<br />
<br />
===How to set the UNIGATE into the configuration mode (Configmode)?===<br />
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.<br />
For the UNIGATE CL the RS232 interface is automatically active throught the switch positions of S4+S5 with "FF".<br />
If you use the UNIGATE IC the basis board of the J17.<br />
<br />
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):<br />
<br />
''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''<br />
Configmode...<br />
<br />
Now you know that the unit is in configuration mode.<br />
<br />
'''Practice Tip:''' With UNIGATE CL, RS and SC the configuration mode is visually indicated by the RS-"State" LED flashing red.<br />
<br />
=== What is to consider when switching to UNIGATE CL from UNIGATE SC? ===<br />
There is one significant difference between an UNIGATE SC and an UNIGATE CL: the UNIGATE SC devices have a hardware switch "232 &harr; 485", which does not exist on an UNIGATE CL. The UNIGATE 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 <br />
<source lang="delphi"> Set(RS_Type,[?]) </source> <br />
command.<br />
In the PROFIBUS version there is also the difference of the ID number. The UNIGATE CL-DP needs the GSD file UGIC3218.gsd.<br />
<br />
=== Does the UNIGATE IC support SPI?===<br />
Yes, the UNIGATE IC supports SPI. (Up-to-date [http://www.deutschmann.de/de/produkte/download.php?file_id=412 UNIGATE IC Pinout-List] in XLS Format)<br />
Pin 3...7 are for the SPI Master (SPI slave on request only)<br />
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.<br />
<br />
===How to connect two networks (PROFIBUS / PROFINET)?===<br />
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.<br />
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.<br />
<br />
===Fieldbus===<br />
====CANopen====<br />
=====UNIGATE CO (M)-PROFIBUS DP===== <br />
=====I encountered problems after downloading the existing/old GWC-file into my new device. Can you list the various steps?=====<br />
#Open the desired GWC file with the configuration tool WINGATE. <br />
#Then start the new device and perform the download<br />
#Now perform an Upload from the device<br />
#The parameter "CAN baud rate" is now at 125k. <br />
#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.<br />
#Afterwards perform another download<br />
#Save the change, respectively the "new" GWC file<br />
<br />
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.<br />
<br />
=====How to replace CANopen (Master) - PROFIBUS DP (Slave)?=====<br />
#Start WINGATE:<br />
#Connect the RS232 from PC to UNIGATE (3 wire, 3 pin connector)<br />
#Connect power supply<br />
#Upload file<br />
#Save file<br />
#Disconnect the old UNIGATE <br />
#Connect the new UNIGATE (see Step 1)<br />
#Afterwards click "File - Download" (write to device)<br />
<br />
<br />
<gallery><br />
Datei:Start WINGATE V2.65(379).png|1. Start WINGATE<br />
Datei:WINGATE_V2.64(379)_Versorgungsanschluss.png|3. Connect power supply<br />
Datei:WINGATE_V2.65(379)_File_upload.png|4. File upload<br />
Datei:WINGATE_Save_as.png|4. Save as<br />
Datei:WINGATE_V2.65(379)_File_download_screen.png|8. File-Download<br />
</gallery><br />
<br />
=====In WINGATE-File the Adresse 0x14 is set to 0=====<br />
With the new Firmware V2.60 in WINGATE the config file has to be stored with the setting "baud rate: DIP Switch"<br />
<br />
====DeviceNet====<br />
=====How much power does the UNIGATE IC draw at the DeviceNet power supply 24 Volt connector, PIN 17?=====<br />
The current consumption is max. 35mA.<br />
<br />
====EtherNet/IP====<br />
=====How to switch to EtherNet/IP 2Port?=====<br />
You can find more about switching to EtherNet/IP 2 Port on the UNIGATE CL EtherNet/IP site: [[UNIGATE_EtherNet/IP/en|Changeover to 2-Port devices]]<br />
<br />
=====My PLC cannot establish a connection to my EtherNet/IP device. What could be the reason?=====<br />
Maybe you configured your PLC to use a Unicast connection.<br />
<br />
If you are using the Rockwell software RSLogix 5000 you can check this in the UNIGATE's module properties dialogue. Please make sure the option "Use Unicast Connection over EtherNet/IP" on the connection tab is disabled.<br />
<br />
===== Why does the function <code>ReadNewObjectDataEIP</code> show a change of input data, altough all of the data is identical? =====<br />
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.<br />
<br />
===== Can I only transfer an even number of bytes with an EtherNet/IP device? =====<br />
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).<br />
<br />
=====Can a power supply separation be avoided through a script adaptation in a UNIGATE EtherNet/IP with firmware 4.0?=====<br />
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).<br />
<br />
====Fast Ethernet====<br />
=====Is there an example of the web server functionality ?=====<br />
Yes, there is an example, which is available after installing the PROTOCOL DEVELOPER.<br />
# Start the UNIGATE CL-FE in configmode<br />
# Reset device (WINGATE - options - reset device)<br />
# Save the script example: Wingate – File – Write script ... :\Software\ProtocolDeveloper\Example\08 Bus specific\Fast Ethernet script.dcs<br />
# Set the IP address and the subnet mask (Do not forget to download the file)<br />
# Start the UNIGATE in Run mode (S4+5 not FF and not EE)<br />
# Start a FTP Client, such as [http://www.ghisler.com/index.htm Total Commander]. Establish a FTP connection. (Username and password: deutschmann)<br />
# Directory: Flash<br />
# Copy "index.html" to CL-FE<br />
# Start your browser and enter the IP address you created in WINGATE<br />
# If you refresh your browser (F5) you will see that the numerical value increased<br />
# That's it!<br />
<br />
<gallery><br />
Datei:WINGATE V2.72(385) Set IP Adress set subnet mask.png|4. IP address and subnet mask<br />
Datei:FTP TotalCommander Connection details.png|6. FTP Client<br />
Datei:FTP TotalCommander Verzeichnis flash.png|7. Change directory<br />
Datei:FTP TotalCommander Copy index.png|8. Copy index.html <br />
Datei:WINGATE FTP Browser.png|9. IP address in Browser<br />
</gallery><br />
<br />
=====Is the temperature range down to -40°C by now available for CL devices with RJ45 connectors?=====<br />
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.<br />
In our expansion card for CL and FC a RJ45 for -40°C is used.<br />
<br />
====PROFIBUS====<br />
=====At commissioning a PROFIBUS-slave I do not see any input data when put and also it is not possible to send data to the device.=====<br />
For CPUs from the company Siemens only direct access up to 4 bytes is possible. Provided that useful data > 4 bytes are supposed to be read or written, then the access has to be made through the SFC14 (read) and SFC15 (write). Further information can be found in the projection software's help.<br />
<br />
=====How to use the UNIGATE IC PROFIBUS DPV1 5V without driver 485 and how much current can the DC/DC converter provide on the fieldbus side?=====<br />
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.<br />
<br />
=====Changing of the Slave ID via SPS=====<br />
ID is stored in EEROM.<br />
<source lang="delphi"><br />
var LBusState : Long ;<br />
var L0xE0 : Long ; moveconst ( L0xE0, 0xE0);<br />
<br />
BusStart ;<br />
//Wait ( Bus_Active ) ;<br />
<br />
:LoopBusState;<br />
Get ( ReadBusState , LBusState ) ;<br />
if LBusState less L0xE0 then :LoopBusState; //!!! neu<br />
</source><br />
<br />
=====Which GSD-file is meant for my device?=====<br />
We distinguish between 2 versions: DPV0 and DPV1. You can tell from the article description which device is in front of you. A »DP« stands for DPV0; a »DPV1« for itself. The UNIGATE IC-DPL and UNIGATE CL is a DPV1-device.<br />
<br />
In the download-area of the respective device only that GSD-file, which is valid for the corresponding device only, is placed at your disposal for download.<br />
<br />
A DPV1 slave is downwards compatible and it can also operate in the DPV0 mode. Nevertheless, the DPV1 GSD-file has to be used.<br />
<br />
DPV0 slave &rarr; GSDfile »DAGW2079.GSD«<br />
<br />
DPV1 slave &rarr; GSD-file »UGIC3218.GSD«<br />
<br />
=====GSD Datei - How to create a different configuration?=====<br />
[[Datei:PB_GSD_Configuration_telegramm_8_Word_Out.jpg|thumb|Create a configuration]]<br />
<br />
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.<br />
In this Modul, you can setup every size.<br />
<br />
=====How to set the Slave ID via the Master?=====<br />
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.<br />
<br />
WARNING: With it the EEROM will be re-initialized and the script will be deleted.<br />
<br />
=====How to realize the conversion from Fieldbus &harr; Modbus RTU (Master)?=====<br />
''This proceeding for a UNIGATE CL-PROFIBUS DPV1 is used as an example for all UNIGATEs and the supported Fieldbuses.''<br />
<br />
UNIGATE CL is supplied with a Universal Script that makes setting the "Modbus RTU (Master)" protocol very simple. A detailed description how to configure the device can be found here.<br />
<br />
Note: In case you want to read out the same register several times, then the parameter ''"Data Exchange"'' should be adjusted to ''"On Trigger"''. In this case the UNIGATE expects the togglebyte in the Fieldbus Master's first byte.<br />
<br />
Application:<br />
<br />
The Fieldbus Master requests (read holding register = 03) the register "4567" with the length of 1 word from the Modbus Slave with the ID=2. The resulting inquiry from the Profibus-Master to the UNIGATE is:<br />
<br />
02 03 45 67 00 01<br />
<br />
(ID=2, read register=03, register=4567 and length in words high + low=0001) <br />
<br />
The UNIGATE converts data to Modbus and adds the checksum (=xx):<br />
<br />
02 03 4567 00 01 xx<br />
<br />
The UNIGATE receives the following response from the Modbus Slave with the ID=2:<br />
<br />
02 03 02 03 E8 xx<br />
<br />
(ID=2, read register=03, length in byte =02, value of the register 4567=03E8 and checksum=xx)<br />
<br />
The UNIGATE puts the Modbusslave's response on the Fieldbus:<br />
<br />
02 03 02 03 E8<br />
<br />
Consequently a complete inquiry from the Fieldbus Masters has been converted to Modbus and the Slave's response has been issued to the Fieldbus in turn.<br />
<br />
The above proceeding describes the function of the UNIGATE RS, UNIGATE CL with Universal Script and configured Modbus-RTU(Master) protocol as well as our Script examples Modbus-RTU(Master).<br />
<br />
There are also applications, in which the UNIGATE is supposed to read out a corresponding register or also the UNIGATE cyclically reads the same regsiter again and again through only 1 byte of the Fieldbus Master. With our UNIGATE SC, CL and IC this is possible without a problem. In these two cases the Script only has to be adapted to this requirement. Please use our Script examples for this.<br />
<br />
====PROFINET====<br />
=====How to connect Deutschmann PROFINET devices to a S7?=====<br />
For a step-by-step instruction, please download the PDF [http://deutschmann.de/produkte/download.php?file_id=681].<br />
<br />
=====How to evaluate a UNIGATE device with a PROFINET interface?=====<br />
You can evaluate your PROFINET device (UNIGATE CL-Profinet, UNIGATE IC-Profinet, UNIGATE FC-Profinet) with our free PROFINET Module software. All you need is a Microsoft Windows computer with an Ethernet port. The PROFINET Module software is part of our Starter Kit software collection which can be obtained from the download section.<br />
<br />
=====Why can't I assign a device name to my UNIGATE?=====<br />
For PROFINET the device name is subject to a [[PROFINET_Device_name_(English)|naming convention]]. For example, the use of capital letters is not allowed.<br />
<br />
=====How to rename the GSDML file?=====<br />
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.<br />
<br />
=====Script with station name=====<br />
[[Datei:PN_Script_mit_Stationsname_Set_device.png|thumb|Script with station name]]<br />
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.<br />
If a name is then set in the PROFINET Master it is effective from now on.<br />
<br />
===Series===<br />
====UNIGATE CL====<br />
=====Can I use my configuration file of the series UNIGATE RS for UNIGATE CL as well?=====<br />
We will be supplying the devices UNIGATE CL with a "UNIVERSAL" script (if it had not been handled that way so far). This script then acts as if it was a UNIGATE RS. That means that the UNIGATE CL can be parameterized via the configuration software WINGATE. An "old" UNIGATE RS configuration file is not compatible with that of the UNIGATE CL. If a UNIGATE RS is to be changed over to UNIGATE CL, then the UNIGATE CL must be read out once via WINGATE and the protocol settings have to be made. This configuration can then be stored in the usual manner and it can be used again for devices of the same type.<br />
<br />
Note: If a "Reset Device" is carried out with a UNIGATE CL, then the "UNIVERSAL" script gets lost and it has to be loaded again.<br />
<br />
=====I want to download my UNIGATE SC-PB Script into the UNIGATE CL-PB. The PROFIBUS State LED remains red and/or the serial communication does not work.=====<br />
This "phenomenon" has two reasons:<br />
<br />
# The UNIGATE SC-PB requires the GSD-file "DAGW2079.gsd" and the UNIGATE CL-PB requires the GSD-file "UGIC3218.gsd".<br />
# The interface of the UNIGATE SC-PB is set via the switch "Interface" and at the UNIGATE CL-PB it is set in the Script.<br />
<br />
Remedy:<br />
1. Either the GSD-file for the UNIGATE CL-PB in the PROFIBUS Master in the hardware configuration is changed to "UGIC3218.gsd" or the Ident number has to be changed to "2079" in the Script through the command:<br />
Set ( IdentNumber , 0x2079 ) ; //default: 0x3218<br />
<br />
After the Script download the UNIGATE CL-PB acts like a UNIGATE SC-PB at the PROFIBUS.<br />
<br />
2. The interfaces of the UNIGATE CL-PB have to be defined in the Script by means of the Script command:<br />
Set ( RS_Type , RS232 ) ; //or RS485 or RS422<br />
<br />
=====How to configure the UNIGATE CL with WINGATE?=====<br />
Note: This instruction refers to the configuration of UNIGATE CL in connection with the Universal Script.<br />
<br />
The current version of the software WINGATE has to be installed on the PC in order to be able to configure the UNIGATE CL.<br />
<br />
Subsequently the UNIGATE CL has to be connected to the PC via the application interface X1. The required wiring can be found here.<br />
<br />
<br />
The "Universalscript Deutschmann" has to be available in the device, so that it can be configured by WINGATE. When the software WINGATE is executed and the UNIGATE is restarted then you receive the following actuation message from the UNIGATE in the lower part of WINGATE (example: V3553 UNIGATE CL-ProfibusDP):<br />
<br />
RS-PBV1-CL (232/422/485) V7.31[30] (c)dA Switch=0x01FF Script(16k)="Universalscript Deutschmann" Author="G/S" Version="V 0.2d" Date 24.07.2008 SN: 3553xxxx ID=1<br />
Konfigmode...<br />
<br />
IMPORTANT: ALL following points cannot be carried out unless you receive this message (with or without "Universalscript Deutschmann")!<br />
<br />
In case the Script is not in the device, it can be loaded into the UNIGATE with the function File -> ''Write Script'' (the Script can be found on the Support CD at: \Software\ProtocolDeveloper\Example\Universal\CL_Universal.dcs or on our website in category "Software").<br />
<br />
Now the UNIGATE CL can be read-out through ''File &rarr; Upload''. Both options ''more items visible & more items editable'' have to be acivated in order to be able to set all functions.<br />
<br />
The configuration itself should be made from the top to the bottom. The desired parameters can be moved to the corresponding line with double-click.<br />
<br />
When the configuration is completed the altered values have to written into the device with ''File &rarr; Download''. This is confirmed by the UNIGATE with:<br />
<br />
Download ok<br />
<br />
Store data... ...<br />
<br />
Restart<br />
<br />
RS-PBV1-CL (232/422/485) V7.31[30] (c)dA Switch=0x01FF Script(16k)="Universalscript Deutschmann" Author="G/S" Version="V 0.2d" Date 24.07.2008 SN: 3553xxxx ID=1<br />
Konfigmode...<br />
<br />
With it the configuration is finished. Now the device has to be switched to 'voltageless' and the rotary switch at the device has to be adjusted accordingly and connected to the application. Now the device can be put into operation.<br />
<br />
=====Can you deliver the Protocol Converter UNIGATE CL in a lacquered version?=====<br />
The lacquering of this series does not make sense, since the mechanical oponents such as rotary coding switches, plug connectors, etc. can not be lacquered and thus a disruption would occur.<br />
<br />
====UNIGATE IC====<br />
=====Problem with the virtual COM-ports via USB=====<br />
If the Developerboard UNIGATE IC-AB is connected via the USB-interface, then the following procedure has to be taken into account:<br />
<br />
# Adjust all switches, rotary switches and jumpers in accordance to the UNIGATE IC that is to be used.<br />
# Connect the Developerboard UNIGATE IC-AB through the USB-cable to the PC/laptop and supply the Developerboard UNIGATE IC-AB with voltage through the provided power supply.<br />
# Put the UNIGATE IC on the socket of the Developerboard UNIGATE IC-AB and set the switch ''POWER'' to position ON afterwards. Only now the operating system of the PC recognizes the new virtual interfaces and during initial startup the drivers are installed.<br />
# Execute the corresponding software application now and select the (new) interface in ''Options''.<br />
# Please push the button ''Reset''. The device responds now (provided that the switch ''Mode is set to Config'') with the startup message or the Script is being executed (switch ''Mode on Run'' and the software ''PROTOCOL DEVELOPER'' is not initiated) or the device starts in the DebugMode (if the switch ''Mode is set to Run'' and the software ''PROTOCOL DEVELOPER'' is being executed).<br />
<br />
Therefore the switch ''POWER'' should not be changed any more since the virtual COM-ports will be re-initialized again with any change from ''ON&rarr;OFF&rarr;ON''.<br />
<br />
=====Is it possible to lacquer the series UNIGATE IC?=====<br />
There is no reason why the series UNIGATE IC cannot be lacquered. However, the complete assembly (the whole customer's device) should be lacquered in one piece. To lacquer the UNIGATE IC first would involve a disproportionate high effort, which would lead to high costs (e. g. The software would have to be downloaded before, tapeing of the pins and so on). Therefore we are not supplying the UNIGATE IC-series in lacquered form.<br />
<br />
====UNIGATE RS====<br />
The lacquering of this series does not make sense, since the mechanical oponents such as rotary coding switches, plug connectors, etc. can not be lacquered and thus a disruption would occur. We offer die-cast aluminium housing for these applications.<br />
<br />
===PROTOCOL DEVELOPER===<br />
====The PROTOCOL DEVELOPERs help window is empty. What can I do?====<br />
By default the help-file has to be existent on a local drive (e. g. C:\)<br />
<br />
In order to be able to also access the help-file from a network drive the following lines have to be entered into Notepad and saved as "*.REG" file:REGEDIT4 <br />
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp] <br />
<br />
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp\1.x\HHRestrictions] <br />
<br />
"MaxAllowedZone"=dword:00000001 "EnableFrameNavigationInSafeMode"=dword:00000001 <br />
<br />
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp\1.x\ItssRestrictions] <br />
<br />
"MaxAllowedZone"=dword:00000001When the file has been generated it is executed with a double click. The PC has to be restarted, so that the changes will be accepted.<br />
<br />
For further information as well as possible risks please log on to: http://support.microsoft.com/kb/896358/de<br />
<br />
<br />
''Microsoft Windows Vista:''<br />
<br />
By default the access to "*.CHM"-files is denied. In order to make an access possible though, click with the right button on the the file properties under General on Unblock. The help file opens now.<br />
<br />
===WINGATE===</div>Reithhttps://wiki.deutschmann.de/index.php?title=en:Frequently_asked_questions_Fieldbus-_and_Industrial-Ethernet-Devices&diff=3456en:Frequently asked questions Fieldbus- and Industrial-Ethernet-Devices2019-08-27T14:12:49Z<p>Reith: /* How to replace a ROTARNOCK 1/2/3/4 by a ROTARNOCK 100? */</p>
<hr />
<div>== Electronic Cam Controls ==<br />
===Are there replacements for a product that is no longer available? (LOCON 32-HC, LOCON 32-PM)...===<br />
1. Substitution option with [[LOCON 24 (English)|LOCON 24]]:<br />
<br />
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.<br />
<br />
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.<br />
<br />
2. Substitution option with [[LOCON 100 (English)|LOCON 100]] / [[LOCON 200 (English)|LOCON 200]]:<br />
<br />
Basically the following points ALWAYS have to be clarified in case of replacing a product that is no longer available: (Example in italic)<br />
* Which encoder is used in connection with the cam control (NSW) (maximum of 16 inputs) &rarr; number of encoder inputs &rarr; at INC. at least 2, at absolute &rarr; number of tracks = number inputs)<br />
<br />
''A TA58-O360-GYE is used &rarr; 9 tracks = 9 inputs''<br />
<br />
* What other pins are used? (e. g. at INC. encoders Clear + and/or Clear- &rarr; number of inputs +1 or +2)<br />
<br />
''None &rarr; + 0 inputs''<br />
<br />
* Is the Prog.Enable wired? (if yes &rarr; number of inputs +1)<br />
<br />
''Yes. &rarr; +1 input''<br />
<br />
* Is the external program selection wired? If yes, how many programs? (number of inputs +2 ... +7)<br />
<br />
''Yes, up to program 8. 5 pins are required for it &rarr; +5 inputs''<br />
<br />
According to the amount here the decision is made, whether [[LOCON 100 (English)|LOCON 100]] or [[LOCON 200 (English)|LOCON 200]] can be used. Provided that the amount remains below 16, either a [[LOCON 100 (English)|LOCON 100]] or a [[LOCON 200 (English)|LOCON 200]] can be used. If the amount of required inputs exceeds 16, then a [[LOCON 100 (English)|LOCON 100]] 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 [[LOCON 100 (English)|LOCON 100]] or [[LOCON 200 (English)|LOCON 200]] can be used. <br />
<br />
Quantity determination of expansion modules that have to be used (LOCON 100-A32 or LOCON 200-IO8):<br />
<br />
* Is the RunControl-relay wired? If yes &rarr; number of outputs + 1<br />
<br />
''Yes. + 1 output for RunControl''<br />
<br />
* How many outputs are used at the cam control? &rarr; Number of the basis' remaining outputs (LOCON 100 + LOCON 200) = 16 - number of inputs<br />
<br />
''32 outputs are used. &rarr; Total = 1 + 32 = 33 outputs. Either LOCON 100 (1 output) with an LOCON 100-A32 extension (=32 outputs) OR LOCON 200 (1 output) + 3 x LOCON 200-IO8 (8 outputs each = 32 outputs) can be used here.''<br />
<br />
Basically the version LOCON 200 + LOCON 200-IO8 is to be favored, since the cycle times for this constellation are lower than those for LOCON 100.<br />
<br />
On principle it does not matter which TERM is used. [[LOCON 100 (English)|LOCON 100]] & [[LOCON 200 (English)|LOCON 200]] are supported by TERM 6, TERM 24 & TERM 32 to a partially limited extent. For that reason the parameterization and configuration should principally always be carried out with [[WINLOC 32 (English)|WINLOC 32]] and the mentioned TERMs should be used for operation.<br />
<br />
===How to connect a LOCON with the RS232-interface (COM port) at the PC?===<br />
At the PC COM port there is a 9-pole D-SUB pin connection with the following assignment:<br />
<br />
PIN 2 - Rx (from the PC's point of view)<br />
<br />
PIN 3 - Tx (from the PC's point of view)<br />
<br />
PIN 5 - GND<br />
<br />
Example:<br />
<br />
At the LOCON16/17 the assignment of the X2 is as follows:<br />
<br />
PIN 26 - GND<br />
<br />
PIN 27 - Rx 232 (from the LOCON's point of view)<br />
<br />
PIN 28 - Tx 232 (from the LOCON's point of view)<br />
<br />
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.<br />
<br />
For the above example it comes to the following cable assignment:<br />
<br />
LOCON X2 PIN26 &harr; PC PIN5<br />
<br />
LOCON X2 PIN27 &harr; PC PIN3<br />
<br />
LOCON X2 PIN28 &harr; PC PIN2<br />
<br />
Note:<br />
Possible existing blue bridges between the signals "DICNET-/Rx" &harr; "R-" and "DICNET+/Tx" &harr; "R+" have to be removed.<br />
<br />
===How to reset LOCON 90, LOCON 100, LOCON 100-PB, LOCON 200, LOCON 200-PB, ROTARNOCK 100 or ROTARNOCK 100-PB back to delivery condition (reset)?===<br />
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 WINLOC 32 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 LOCON 100 with an expansion LOCON 100-A32 with DICNET communication, configured as Timer with a counting range of 16):<br />
<br />
''L100-48(48)-T16-485(DICNET) V3.4''<br />
<br />
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: <br />
''Reset configuration to defaultvalue and clear all programmed data (Y/N)? N''<br />
<br />
This query has to be confirmed with "y" within 3 seconds and another safety query follows:<br />
<br />
''Cancel operation (Y/N) N'' which is to be confirmed with "n".<br />
<br />
If the entry is correct, the following message appears in the terminal window:<br />
<div style="border: 1px solid #136db9; background-color: #fafafa; padding: 8px;"><br />
''Clear EEROM 0H-1fffH ...............................<br />
<br />
Restart<br />
<br />
L100-48(48)-S4096-485(DICNET) V3.4 ok<br />
<br />
(Error: 108)''<br />
</div><br />
With it the device was set back to the condition it was originally supplied.<br />
<br />
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.<br />
Note: After a reset the optional LOGIC-function has to be activated again. At the devices LOCON 100 & LOCON 200 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.<br />
<br />
===How to activate the logic function of LOCON 100-PB, LOCON 200, LOCON 200-PB, ROTARNOCK 100 or ROTARNOCK 100-PB?===<br />
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 LOCON 100-PB, LOCON 200 or LOCON 200-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.<br />
<br />
The device to be extended by the logic function must be connected to the PC and a start-up string has to be shown WINLOC 32.<br />
<br />
With a click on the menue ''Extras &rarr; Product Option Activation'' a window opens for activation.<br />
<br />
The DICNET-ID is entered in the line Device ID. For a connection through RS232 this value remains on "0".<br />
<br />
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 &harr; PC works).<br />
<br />
The release code is entered in the line ''Activation key''. Start behind the "-".<br />
Click on ''Run'' afterwards.<br />
<br />
(In case of an error "Returncode=4" is the result.)<br />
<br />
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:<br />
<br />
L200-16-S4096-H-''LG''-232 Vx.x<br />
<br />
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:<br />
<br />
Note: After a "Clear all" the logic function has to be released again.<br />
<br />
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 LOCON 100-PB; LOCON 200(-PB) & ROTARNOCK 100(-PB)".<br />
<br />
===External Wiring===<br />
====How is the modification from LOCON 32-HC or LOCON 32-PM to LOCON 24 carried out?====<br />
Introductorily we like to point out that this description refers to a LOCON 32-HC, that is/was configured "absolute parallel 360" as encoder type. Consequently the LOCON 24 also has to contain this "O360" in the article text.<br />
<br />
{| class="wikitable"<br />
!LOCON 24 !!Signal !!LOCON 32-HC !!LOCON 32-PM<br />
|-<br />
|X1 PIN 1 ||OUT 1 ||X10 PIN 2 ||X1 PIN 1<br />
|-<br />
|X1 PIN 2 ||OUT 2 ||X10 PIN 1 ||X1 PIN 2<br />
|-<br />
|X1 PIN 3 ||OUT 3 ||X10 PIN 4 ||X1 PIN 3<br />
|-<br />
|X1 PIN 4 ||OUT 4 ||X10 PIN 3 ||X1 PIN 4<br />
|-<br />
|X1 PIN 5 ||OUT 5 ||X10 PIN 6 ||X1 PIN 5<br />
|-<br />
|X1 PIN 6 ||OUT 6 ||X10 PIN 5 ||X1 PIN 6<br />
|-<br />
|X1 PIN 7 ||OUT 7 ||X10 PIN 8 ||X1 PIN 7<br />
|-<br />
|X1 PIN 8 ||OUT 8 ||X10 PIN 7 ||X1 PIN 8<br />
|-<br />
|X1 PIN 9 ||OUT 9 ||X10 PIN 10 ||X1 PIN 9<br />
|}<br />
<br />
... [http://www.deutschmann.de/en/support/faq_detail.html?question=18 more]<br />
<br />
=== Models ===<br />
==== What has to be considered when using a LOCON 200 in connection with TERM 24? ====<br />
If a (discontinued) device is supposed to be replaced by LOCON 200 and in case TERM 24 is used in the assembly, then the TERM 24's Firmware must be updated at any rate. For the update the device has to be sent back to us.<br />
<br />
==== TN65 - ROTARNOCK - what is it? ====<br />
It is the same unit. ROTARNOCK describes the product line and TN65 is the specific type or the article description.<br />
<br />
Example:<br />
ROTARNOCK 100 - describes the ROTARNOCK-family "100". The detailed article description is explained on the picture "Article description".<br />
<br />
[[Datei:Article description Rotarnock English.jpg|thumb|Article description]]<br />
<br />
<br />
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.<br />
<br />
==== How to change the Profibus Ident Number? ====<br />
To change the Profibus Ident Number from 3606H to 3231 the ROTARNOCK 100-PB has to be connected with the PC via a serial communication (RS232). For the serial communication the following pin assignemt is valid here:<br />
<br />
PC PIN2 (Rx) ↔ ROTARNOCK 25pin D-Sub PIN17 (Tx RED)<br /><br />
PC PIN3 (Tx) ↔ ROTARNOCK 25pin D-Sub PIN18 (Rx RED)<br /><br />
PC PIN5 (GND) ↔ ROTARNOCK 25pin D-Sub PIN25 (GND)<br />
<br />
A corresponding programming cable (including plug-in power supply) is to be ordered with the article number V3467. ( V3467 - Programming cable for ROTARNOCK - 232/PB).<br />
<br />
The software WINLOC 32 has to be installed on the PC. The interface parameters are entered in "Extras → Options → Port".<br />
<br />
If the ROTARNOCK is now supplied with voltage a window opens automatically and the device brings its start-up message, e. g.:<br />
'''R100-48-O4096-PB(126)-232 V3.54 Ok'''<br />
Now place in WINLOC 32 the cursor behind the last character (through a "left click") and press "n" while keeping the keys "STRG/CTRL" pressed.<br />
The following confirmation prompt appears:<br />
'''Ident-Nr=3606H, change to 3231H (Y/N)? N'''<br />
This query has to be confirmed with "'''y'''" within 3 seconds and the following confirmation appears:<br />
'''New Ident-Nr = 3231H'''<br />
After a re-start the device uses the new Ident Number and it can be put into operation.<br />
<br />
The same way the Ident Number can also be changed back from 3231H to 3606H.<br />
<br />
==== How to replace ROTARNOCK 1/2/3/4 by ROTARNOCK 100? ====<br />
There are two ways to carry out the exchange.<br />
<br />
'''1.'''<br />
Exchange with the convenient programming software for cam controls WINLOC 32 (recommended procedure):<br />
<br />
Read out (File&rarr;Upload) the ROTARNOCK that is to be replaced with the software WINLOC 32 and store (File&rarr;Save) it on the hard disk or open an existing configuration file.<br />
<br />
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:<br />
Encoder resolution, ITC (=idle time compensation) Type, Display factor, ITC Function, Turn Direction, Run-Control and Zero shift.<br />
<br />
Important: Please write down the indicated position during downtime (best in the basic position if possible) before removing the old device! <br />
<br />
Connect the ROTARNOCK 100 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 ROTARNOCK 100 back in default mode can be found here.<br />
<br />
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.<br />
<br />
Enter the value for the Virtual Resolution here and select the ITC Type and confirm it with OK. <br />
<br />
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!<br />
<br />
'''Important advice:'''<br />
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.<br />
<br />
We recommend to carry out the zero adjustment first before the cams are being transmitted to the device.<br />
Load the newly generated configuration in the ROTARNOCK 100 through Download. Install the ROTARNOCK 100 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.<br />
<br />
In WINLOC32 the cam values, idle times and output names are transmitted from the old configuration file to the new one through Extras &rarr; Data transfer. This function is only available in the Comfort version of WINLOC 32.<br />
<br />
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 [mailto:hotline@deutschmann.de hotline@deutschmann.de].<br />
<br />
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. <br />
<br />
'''2.'''<br />
Exchange with manual configuration and programming with TERM 6 or TERM 24 (with current Firmware):<br />
<br />
The following information on the ROTARNOCK that is to be exchanged should be available:<br />
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.<br />
<br />
Advice: In case your old device features the option R - RunControl, then the device has to be configured with WINLOC 32.<br />
<br />
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. <br />
<br />
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.<br />
<br />
Now you can start entering the cams and idle times and finally the application can be tested and be put into operation.<br />
<br />
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 WINLOC 32.<br />
<br />
===Software Tools===<br />
====Configuration- and programming-software for cam controls?====<br />
A configuration- and programming-software [[WINLOC 32 (English)|WINLOC 32]] is available for all Deutschmann cam controls (NS).<br />
<br />
The basic version of that software is available free of charge (in the download-area and on the support-DVD). This basic version already features extensive functions. The cam control can be read out, configured and programmed. Also these files can be stored. <br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
====How and where is to enter the WINLOC 32 comfort version license key?====<br />
First of all start WINLOC 32.<br />
<br />
In the menu line "Extras" &rarr; select "Options". A window opens. If necessary please change to the register "License".<br />
Now enter the license key you received from us.<br />
<br />
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 "*".<br />
<br />
A license that have been purchased once can be used for all follow-up versions. A WINLOC 6 license also works with WINLOC 32.<br />
<br />
== UNIGATE ==<br />
===How to carry out a Firmware update at UNIGATE?===<br />
You can find an explanation on the site [[Firmware-Aktualisierung/en|Firmware update]].<br />
<br />
===I encountered problems with the RS232 connection between UNIGATE and PC. What to do when WINGATE says "no Gateway found"?===<br />
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.<br />
<br />
===How to connect an UNIGATE with the RS232-interface (COM port) at the PC?===<br />
At the PC COM port there is a 9-pole D-SUB pin connection with the following assignment:<br />
<br />
PIN 2 - Rx (from the PC's point of view)<br />
<br />
PIN 3 - Tx (from the PC's point of view)<br />
<br />
PIN 5 - GND<br />
<br />
Example: At the UNIGATE CL the assignment of the X1 is as follows:<br />
<br />
PIN 1 - Rx 232 (from the UNIGATE's point of view)<br />
<br />
PIN 2 - Tx 232 (from the UNIGATE's point of view)<br />
<br />
PIN 3 - AP-GND<br />
<br />
Generally always the Rx of the PC has to be connected with the Tx of the UNIGATE and the Tx of the PC with the Rx of the UNIGATE. Also the GND always has to be connected.<br />
<br />
For the above example it comes to the following cable assignment:<br />
<br />
UNIGATE X1 PIN1 &harr; PC PIN3<br />
<br />
UNIGATE X1 PIN2 &harr; PC PIN2<br />
<br />
UNIGATE X1 PIN3 &harr; PC PIN5<br />
<br />
===Does UNIGATE have a "test mode"?===<br />
Yes, there is a test mode.<br />
<br />
The interface-switch has to be set to position »RS232« and the two rotary coding switches on the serial side (S4 + S5) have to be set to »EE« in order to put the device into the test mode.<br />
<br />
After the restart the UNIGATE sends a byte on the serial side from »0-F« every second (some devices will first do a 15 to 30 seconds lasting self test). On the Fieldbus this output occurs accordinglywith the length depending on the set bus width. If useful data is sent to the UNIGATE (serial and Fieldbus) they are sent back from the UNIGATE (ECHO).<br />
<br />
===How to get my script into the device?===<br />
'''Advice:''' Please always use the current version of the corresponding software.<br />
<br />
Basically there are two ways to load the script into the UNIGATE.<br />
<br />
'''Possibility 1''' - via the serial (application-) interface: (applies to ALL UNIGATE SC, IC & CL) The script has to be compiled in the PROTOCOL DEVELOPER by "File &rarr; save compiled file" (the script receives the file extension *.dcs), so that the script gets into the device this way. The device has to be set into the configuration mode in order to load the script into the device. The script download can be started with the software WINGATE through "File &rarr; Write Script". With the software SPT (ScriptProgramTool) the downlaod is initiated through "File &rarr; Open file and program".<br />
<br />
'''Possibility 2''' - via the DEBUG-interface and the software PROTOCOL DEVELOPER: (applies to ALL UNIGATE IC & CL as well as UNIGATE SC with option "DB") In this case the device's DEBUG-interface has to be connected with a PC COM-Port. In the software PROTOCOL DEVELOPER and belated power up of the device (NOT in the configuration mode) the message "Device started in Debug mode" appears in the bottom left corner. Now the download can be started with "DEBUG".<br />
<br />
===How to set the UNIGATE into the configuration mode (Configmode)?===<br />
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.<br />
For the UNIGATE CL the RS232 interface is automatically active throught the switch positions of S4+S5 with "FF".<br />
If you use the UNIGATE IC the basis board of the J17.<br />
<br />
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):<br />
<br />
''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''<br />
Configmode...<br />
<br />
Now you know that the unit is in configuration mode.<br />
<br />
'''Practice Tip:''' With UNIGATE CL, RS and SC the configuration mode is visually indicated by the RS-"State" LED flashing red.<br />
<br />
=== What is to consider when switching to UNIGATE CL from UNIGATE SC? ===<br />
There is one significant difference between an UNIGATE SC and an UNIGATE CL: the UNIGATE SC devices have a hardware switch "232 &harr; 485", which does not exist on an UNIGATE CL. The UNIGATE 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 <br />
<source lang="delphi"> Set(RS_Type,[?]) </source> <br />
command.<br />
In the PROFIBUS version there is also the difference of the ID number. The UNIGATE CL-DP needs the GSD file UGIC3218.gsd.<br />
<br />
=== Does the UNIGATE IC support SPI?===<br />
Yes, the UNIGATE IC supports SPI. (Up-to-date [http://www.deutschmann.de/de/produkte/download.php?file_id=412 UNIGATE IC Pinout-List] in XLS Format)<br />
Pin 3...7 are for the SPI Master (SPI slave on request only)<br />
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.<br />
<br />
===How to connect two networks (PROFIBUS / PROFINET)?===<br />
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.<br />
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.<br />
<br />
===Fieldbus===<br />
====CANopen====<br />
=====UNIGATE CO (M)-PROFIBUS DP===== <br />
=====I encountered problems after downloading the existing/old GWC-file into my new device. Can you list the various steps?=====<br />
#Open the desired GWC file with the configuration tool WINGATE. <br />
#Then start the new device and perform the download<br />
#Now perform an Upload from the device<br />
#The parameter "CAN baud rate" is now at 125k. <br />
#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.<br />
#Afterwards perform another download<br />
#Save the change, respectively the "new" GWC file<br />
<br />
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.<br />
<br />
=====How to replace CANopen (Master) - PROFIBUS DP (Slave)?=====<br />
#Start WINGATE:<br />
#Connect the RS232 from PC to UNIGATE (3 wire, 3 pin connector)<br />
#Connect power supply<br />
#Upload file<br />
#Save file<br />
#Disconnect the old UNIGATE <br />
#Connect the new UNIGATE (see Step 1)<br />
#Afterwards click "File - Download" (write to device)<br />
<br />
<br />
<gallery><br />
Datei:Start WINGATE V2.65(379).png|1. Start WINGATE<br />
Datei:WINGATE_V2.64(379)_Versorgungsanschluss.png|3. Connect power supply<br />
Datei:WINGATE_V2.65(379)_File_upload.png|4. File upload<br />
Datei:WINGATE_Save_as.png|4. Save as<br />
Datei:WINGATE_V2.65(379)_File_download_screen.png|8. File-Download<br />
</gallery><br />
<br />
=====In WINGATE-File the Adresse 0x14 is set to 0=====<br />
With the new Firmware V2.60 in WINGATE the config file has to be stored with the setting "baud rate: DIP Switch"<br />
<br />
====DeviceNet====<br />
=====How much power does the UNIGATE IC draw at the DeviceNet power supply 24 Volt connector, PIN 17?=====<br />
The current consumption is max. 35mA.<br />
<br />
====EtherNet/IP====<br />
=====How to switch to EtherNet/IP 2Port?=====<br />
You can find more about switching to EtherNet/IP 2 Port on the UNIGATE CL EtherNet/IP site: [[UNIGATE_EtherNet/IP/en|Changeover to 2-Port devices]]<br />
<br />
=====My PLC cannot establish a connection to my EtherNet/IP device. What could be the reason?=====<br />
Maybe you configured your PLC to use a Unicast connection.<br />
<br />
If you are using the Rockwell software RSLogix 5000 you can check this in the UNIGATE's module properties dialogue. Please make sure the option "Use Unicast Connection over EtherNet/IP" on the connection tab is disabled.<br />
<br />
===== Why does the function <code>ReadNewObjectDataEIP</code> show a change of input data, altough all of the data is identical? =====<br />
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.<br />
<br />
===== Can I only transfer an even number of bytes with an EtherNet/IP device? =====<br />
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).<br />
<br />
=====Can a power supply separation be avoided through a script adaptation in a UNIGATE EtherNet/IP with firmware 4.0?=====<br />
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).<br />
<br />
====Fast Ethernet====<br />
=====Is there an example of the web server functionality ?=====<br />
Yes, there is an example, which is available after installing the PROTOCOL DEVELOPER.<br />
# Start the UNIGATE CL-FE in configmode<br />
# Reset device (WINGATE - options - reset device)<br />
# Save the script example: Wingate – File – Write script ... :\Software\ProtocolDeveloper\Example\08 Bus specific\Fast Ethernet script.dcs<br />
# Set the IP address and the subnet mask (Do not forget to download the file)<br />
# Start the UNIGATE in Run mode (S4+5 not FF and not EE)<br />
# Start a FTP Client, such as [http://www.ghisler.com/index.htm Total Commander]. Establish a FTP connection. (Username and password: deutschmann)<br />
# Directory: Flash<br />
# Copy "index.html" to CL-FE<br />
# Start your browser and enter the IP address you created in WINGATE<br />
# If you refresh your browser (F5) you will see that the numerical value increased<br />
# That's it!<br />
<br />
<gallery><br />
Datei:WINGATE V2.72(385) Set IP Adress set subnet mask.png|4. IP address and subnet mask<br />
Datei:FTP TotalCommander Connection details.png|6. FTP Client<br />
Datei:FTP TotalCommander Verzeichnis flash.png|7. Change directory<br />
Datei:FTP TotalCommander Copy index.png|8. Copy index.html <br />
Datei:WINGATE FTP Browser.png|9. IP address in Browser<br />
</gallery><br />
<br />
=====Is the temperature range down to -40°C by now available for CL devices with RJ45 connectors?=====<br />
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.<br />
In our expansion card for CL and FC a RJ45 for -40°C is used.<br />
<br />
====PROFIBUS====<br />
=====At commissioning a PROFIBUS-slave I do not see any input data when put and also it is not possible to send data to the device.=====<br />
For CPUs from the company Siemens only direct access up to 4 bytes is possible. Provided that useful data > 4 bytes are supposed to be read or written, then the access has to be made through the SFC14 (read) and SFC15 (write). Further information can be found in the projection software's help.<br />
<br />
=====How to use the UNIGATE IC PROFIBUS DPV1 5V without driver 485 and how much current can the DC/DC converter provide on the fieldbus side?=====<br />
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.<br />
<br />
=====Changing of the Slave ID via SPS=====<br />
ID is stored in EEROM.<br />
<source lang="delphi"><br />
var LBusState : Long ;<br />
var L0xE0 : Long ; moveconst ( L0xE0, 0xE0);<br />
<br />
BusStart ;<br />
//Wait ( Bus_Active ) ;<br />
<br />
:LoopBusState;<br />
Get ( ReadBusState , LBusState ) ;<br />
if LBusState less L0xE0 then :LoopBusState; //!!! neu<br />
</source><br />
<br />
=====Which GSD-file is meant for my device?=====<br />
We distinguish between 2 versions: DPV0 and DPV1. You can tell from the article description which device is in front of you. A »DP« stands for DPV0; a »DPV1« for itself. The UNIGATE IC-DPL and UNIGATE CL is a DPV1-device.<br />
<br />
In the download-area of the respective device only that GSD-file, which is valid for the corresponding device only, is placed at your disposal for download.<br />
<br />
A DPV1 slave is downwards compatible and it can also operate in the DPV0 mode. Nevertheless, the DPV1 GSD-file has to be used.<br />
<br />
DPV0 slave &rarr; GSDfile »DAGW2079.GSD«<br />
<br />
DPV1 slave &rarr; GSD-file »UGIC3218.GSD«<br />
<br />
=====GSD Datei - How to create a different configuration?=====<br />
[[Datei:PB_GSD_Configuration_telegramm_8_Word_Out.jpg|thumb|Create a configuration]]<br />
<br />
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.<br />
In this Modul, you can setup every size.<br />
<br />
=====How to set the Slave ID via the Master?=====<br />
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.<br />
<br />
WARNING: With it the EEROM will be re-initialized and the script will be deleted.<br />
<br />
=====How to realize the conversion from Fieldbus &harr; Modbus RTU (Master)?=====<br />
''This proceeding for a UNIGATE CL-PROFIBUS DPV1 is used as an example for all UNIGATEs and the supported Fieldbuses.''<br />
<br />
UNIGATE CL is supplied with a Universal Script that makes setting the "Modbus RTU (Master)" protocol very simple. A detailed description how to configure the device can be found here.<br />
<br />
Note: In case you want to read out the same register several times, then the parameter ''"Data Exchange"'' should be adjusted to ''"On Trigger"''. In this case the UNIGATE expects the togglebyte in the Fieldbus Master's first byte.<br />
<br />
Application:<br />
<br />
The Fieldbus Master requests (read holding register = 03) the register "4567" with the length of 1 word from the Modbus Slave with the ID=2. The resulting inquiry from the Profibus-Master to the UNIGATE is:<br />
<br />
02 03 45 67 00 01<br />
<br />
(ID=2, read register=03, register=4567 and length in words high + low=0001) <br />
<br />
The UNIGATE converts data to Modbus and adds the checksum (=xx):<br />
<br />
02 03 4567 00 01 xx<br />
<br />
The UNIGATE receives the following response from the Modbus Slave with the ID=2:<br />
<br />
02 03 02 03 E8 xx<br />
<br />
(ID=2, read register=03, length in byte =02, value of the register 4567=03E8 and checksum=xx)<br />
<br />
The UNIGATE puts the Modbusslave's response on the Fieldbus:<br />
<br />
02 03 02 03 E8<br />
<br />
Consequently a complete inquiry from the Fieldbus Masters has been converted to Modbus and the Slave's response has been issued to the Fieldbus in turn.<br />
<br />
The above proceeding describes the function of the UNIGATE RS, UNIGATE CL with Universal Script and configured Modbus-RTU(Master) protocol as well as our Script examples Modbus-RTU(Master).<br />
<br />
There are also applications, in which the UNIGATE is supposed to read out a corresponding register or also the UNIGATE cyclically reads the same regsiter again and again through only 1 byte of the Fieldbus Master. With our UNIGATE SC, CL and IC this is possible without a problem. In these two cases the Script only has to be adapted to this requirement. Please use our Script examples for this.<br />
<br />
====PROFINET====<br />
=====How to connect Deutschmann PROFINET devices to a S7?=====<br />
For a step-by-step instruction, please download the PDF [http://deutschmann.de/produkte/download.php?file_id=681].<br />
<br />
=====How to evaluate a UNIGATE device with a PROFINET interface?=====<br />
You can evaluate your PROFINET device (UNIGATE CL-Profinet, UNIGATE IC-Profinet, UNIGATE FC-Profinet) with our free PROFINET Module software. All you need is a Microsoft Windows computer with an Ethernet port. The PROFINET Module software is part of our Starter Kit software collection which can be obtained from the download section.<br />
<br />
=====Why can't I assign a device name to my UNIGATE?=====<br />
For PROFINET the device name is subject to a [[PROFINET_Device_name_(English)|naming convention]]. For example, the use of capital letters is not allowed.<br />
<br />
=====How to rename the GSDML file?=====<br />
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.<br />
<br />
=====Script with station name=====<br />
[[Datei:PN_Script_mit_Stationsname_Set_device.png|thumb|Script with station name]]<br />
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.<br />
If a name is then set in the PROFINET Master it is effective from now on.<br />
<br />
===Series===<br />
====UNIGATE CL====<br />
=====Can I use my configuration file of the series UNIGATE RS for UNIGATE CL as well?=====<br />
We will be supplying the devices UNIGATE CL with a "UNIVERSAL" script (if it had not been handled that way so far). This script then acts as if it was a UNIGATE RS. That means that the UNIGATE CL can be parameterized via the configuration software WINGATE. An "old" UNIGATE RS configuration file is not compatible with that of the UNIGATE CL. If a UNIGATE RS is to be changed over to UNIGATE CL, then the UNIGATE CL must be read out once via WINGATE and the protocol settings have to be made. This configuration can then be stored in the usual manner and it can be used again for devices of the same type.<br />
<br />
Note: If a "Reset Device" is carried out with a UNIGATE CL, then the "UNIVERSAL" script gets lost and it has to be loaded again.<br />
<br />
=====I want to download my UNIGATE SC-PB Script into the UNIGATE CL-PB. The PROFIBUS State LED remains red and/or the serial communication does not work.=====<br />
This "phenomenon" has two reasons:<br />
<br />
# The UNIGATE SC-PB requires the GSD-file "DAGW2079.gsd" and the UNIGATE CL-PB requires the GSD-file "UGIC3218.gsd".<br />
# The interface of the UNIGATE SC-PB is set via the switch "Interface" and at the UNIGATE CL-PB it is set in the Script.<br />
<br />
Remedy:<br />
1. Either the GSD-file for the UNIGATE CL-PB in the PROFIBUS Master in the hardware configuration is changed to "UGIC3218.gsd" or the Ident number has to be changed to "2079" in the Script through the command:<br />
Set ( IdentNumber , 0x2079 ) ; //default: 0x3218<br />
<br />
After the Script download the UNIGATE CL-PB acts like a UNIGATE SC-PB at the PROFIBUS.<br />
<br />
2. The interfaces of the UNIGATE CL-PB have to be defined in the Script by means of the Script command:<br />
Set ( RS_Type , RS232 ) ; //or RS485 or RS422<br />
<br />
=====How to configure the UNIGATE CL with WINGATE?=====<br />
Note: This instruction refers to the configuration of UNIGATE CL in connection with the Universal Script.<br />
<br />
The current version of the software WINGATE has to be installed on the PC in order to be able to configure the UNIGATE CL.<br />
<br />
Subsequently the UNIGATE CL has to be connected to the PC via the application interface X1. The required wiring can be found here.<br />
<br />
<br />
The "Universalscript Deutschmann" has to be available in the device, so that it can be configured by WINGATE. When the software WINGATE is executed and the UNIGATE is restarted then you receive the following actuation message from the UNIGATE in the lower part of WINGATE (example: V3553 UNIGATE CL-ProfibusDP):<br />
<br />
RS-PBV1-CL (232/422/485) V7.31[30] (c)dA Switch=0x01FF Script(16k)="Universalscript Deutschmann" Author="G/S" Version="V 0.2d" Date 24.07.2008 SN: 3553xxxx ID=1<br />
Konfigmode...<br />
<br />
IMPORTANT: ALL following points cannot be carried out unless you receive this message (with or without "Universalscript Deutschmann")!<br />
<br />
In case the Script is not in the device, it can be loaded into the UNIGATE with the function File -> ''Write Script'' (the Script can be found on the Support CD at: \Software\ProtocolDeveloper\Example\Universal\CL_Universal.dcs or on our website in category "Software").<br />
<br />
Now the UNIGATE CL can be read-out through ''File &rarr; Upload''. Both options ''more items visible & more items editable'' have to be acivated in order to be able to set all functions.<br />
<br />
The configuration itself should be made from the top to the bottom. The desired parameters can be moved to the corresponding line with double-click.<br />
<br />
When the configuration is completed the altered values have to written into the device with ''File &rarr; Download''. This is confirmed by the UNIGATE with:<br />
<br />
Download ok<br />
<br />
Store data... ...<br />
<br />
Restart<br />
<br />
RS-PBV1-CL (232/422/485) V7.31[30] (c)dA Switch=0x01FF Script(16k)="Universalscript Deutschmann" Author="G/S" Version="V 0.2d" Date 24.07.2008 SN: 3553xxxx ID=1<br />
Konfigmode...<br />
<br />
With it the configuration is finished. Now the device has to be switched to 'voltageless' and the rotary switch at the device has to be adjusted accordingly and connected to the application. Now the device can be put into operation.<br />
<br />
=====Can you deliver the Protocol Converter UNIGATE CL in a lacquered version?=====<br />
The lacquering of this series does not make sense, since the mechanical oponents such as rotary coding switches, plug connectors, etc. can not be lacquered and thus a disruption would occur.<br />
<br />
====UNIGATE IC====<br />
=====Problem with the virtual COM-ports via USB=====<br />
If the Developerboard UNIGATE IC-AB is connected via the USB-interface, then the following procedure has to be taken into account:<br />
<br />
# Adjust all switches, rotary switches and jumpers in accordance to the UNIGATE IC that is to be used.<br />
# Connect the Developerboard UNIGATE IC-AB through the USB-cable to the PC/laptop and supply the Developerboard UNIGATE IC-AB with voltage through the provided power supply.<br />
# Put the UNIGATE IC on the socket of the Developerboard UNIGATE IC-AB and set the switch ''POWER'' to position ON afterwards. Only now the operating system of the PC recognizes the new virtual interfaces and during initial startup the drivers are installed.<br />
# Execute the corresponding software application now and select the (new) interface in ''Options''.<br />
# Please push the button ''Reset''. The device responds now (provided that the switch ''Mode is set to Config'') with the startup message or the Script is being executed (switch ''Mode on Run'' and the software ''PROTOCOL DEVELOPER'' is not initiated) or the device starts in the DebugMode (if the switch ''Mode is set to Run'' and the software ''PROTOCOL DEVELOPER'' is being executed).<br />
<br />
Therefore the switch ''POWER'' should not be changed any more since the virtual COM-ports will be re-initialized again with any change from ''ON&rarr;OFF&rarr;ON''.<br />
<br />
=====Is it possible to lacquer the series UNIGATE IC?=====<br />
There is no reason why the series UNIGATE IC cannot be lacquered. However, the complete assembly (the whole customer's device) should be lacquered in one piece. To lacquer the UNIGATE IC first would involve a disproportionate high effort, which would lead to high costs (e. g. The software would have to be downloaded before, tapeing of the pins and so on). Therefore we are not supplying the UNIGATE IC-series in lacquered form.<br />
<br />
====UNIGATE RS====<br />
The lacquering of this series does not make sense, since the mechanical oponents such as rotary coding switches, plug connectors, etc. can not be lacquered and thus a disruption would occur. We offer die-cast aluminium housing for these applications.<br />
<br />
===PROTOCOL DEVELOPER===<br />
====The PROTOCOL DEVELOPERs help window is empty. What can I do?====<br />
By default the help-file has to be existent on a local drive (e. g. C:\)<br />
<br />
In order to be able to also access the help-file from a network drive the following lines have to be entered into Notepad and saved as "*.REG" file:REGEDIT4 <br />
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp] <br />
<br />
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp\1.x\HHRestrictions] <br />
<br />
"MaxAllowedZone"=dword:00000001 "EnableFrameNavigationInSafeMode"=dword:00000001 <br />
<br />
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp\1.x\ItssRestrictions] <br />
<br />
"MaxAllowedZone"=dword:00000001When the file has been generated it is executed with a double click. The PC has to be restarted, so that the changes will be accepted.<br />
<br />
For further information as well as possible risks please log on to: http://support.microsoft.com/kb/896358/de<br />
<br />
<br />
''Microsoft Windows Vista:''<br />
<br />
By default the access to "*.CHM"-files is denied. In order to make an access possible though, click with the right button on the the file properties under General on Unblock. The help file opens now.<br />
<br />
===WINGATE===</div>Reithhttps://wiki.deutschmann.de/index.php?title=en:Frequently_asked_questions_Fieldbus-_and_Industrial-Ethernet-Devices&diff=3455en:Frequently asked questions Fieldbus- and Industrial-Ethernet-Devices2019-08-27T14:11:48Z<p>Reith: /* How to change the Profibus Ident Number? */</p>
<hr />
<div>== Electronic Cam Controls ==<br />
===Are there replacements for a product that is no longer available? (LOCON 32-HC, LOCON 32-PM)...===<br />
1. Substitution option with [[LOCON 24 (English)|LOCON 24]]:<br />
<br />
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.<br />
<br />
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.<br />
<br />
2. Substitution option with [[LOCON 100 (English)|LOCON 100]] / [[LOCON 200 (English)|LOCON 200]]:<br />
<br />
Basically the following points ALWAYS have to be clarified in case of replacing a product that is no longer available: (Example in italic)<br />
* Which encoder is used in connection with the cam control (NSW) (maximum of 16 inputs) &rarr; number of encoder inputs &rarr; at INC. at least 2, at absolute &rarr; number of tracks = number inputs)<br />
<br />
''A TA58-O360-GYE is used &rarr; 9 tracks = 9 inputs''<br />
<br />
* What other pins are used? (e. g. at INC. encoders Clear + and/or Clear- &rarr; number of inputs +1 or +2)<br />
<br />
''None &rarr; + 0 inputs''<br />
<br />
* Is the Prog.Enable wired? (if yes &rarr; number of inputs +1)<br />
<br />
''Yes. &rarr; +1 input''<br />
<br />
* Is the external program selection wired? If yes, how many programs? (number of inputs +2 ... +7)<br />
<br />
''Yes, up to program 8. 5 pins are required for it &rarr; +5 inputs''<br />
<br />
According to the amount here the decision is made, whether [[LOCON 100 (English)|LOCON 100]] or [[LOCON 200 (English)|LOCON 200]] can be used. Provided that the amount remains below 16, either a [[LOCON 100 (English)|LOCON 100]] or a [[LOCON 200 (English)|LOCON 200]] can be used. If the amount of required inputs exceeds 16, then a [[LOCON 100 (English)|LOCON 100]] 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 [[LOCON 100 (English)|LOCON 100]] or [[LOCON 200 (English)|LOCON 200]] can be used. <br />
<br />
Quantity determination of expansion modules that have to be used (LOCON 100-A32 or LOCON 200-IO8):<br />
<br />
* Is the RunControl-relay wired? If yes &rarr; number of outputs + 1<br />
<br />
''Yes. + 1 output for RunControl''<br />
<br />
* How many outputs are used at the cam control? &rarr; Number of the basis' remaining outputs (LOCON 100 + LOCON 200) = 16 - number of inputs<br />
<br />
''32 outputs are used. &rarr; Total = 1 + 32 = 33 outputs. Either LOCON 100 (1 output) with an LOCON 100-A32 extension (=32 outputs) OR LOCON 200 (1 output) + 3 x LOCON 200-IO8 (8 outputs each = 32 outputs) can be used here.''<br />
<br />
Basically the version LOCON 200 + LOCON 200-IO8 is to be favored, since the cycle times for this constellation are lower than those for LOCON 100.<br />
<br />
On principle it does not matter which TERM is used. [[LOCON 100 (English)|LOCON 100]] & [[LOCON 200 (English)|LOCON 200]] are supported by TERM 6, TERM 24 & TERM 32 to a partially limited extent. For that reason the parameterization and configuration should principally always be carried out with [[WINLOC 32 (English)|WINLOC 32]] and the mentioned TERMs should be used for operation.<br />
<br />
===How to connect a LOCON with the RS232-interface (COM port) at the PC?===<br />
At the PC COM port there is a 9-pole D-SUB pin connection with the following assignment:<br />
<br />
PIN 2 - Rx (from the PC's point of view)<br />
<br />
PIN 3 - Tx (from the PC's point of view)<br />
<br />
PIN 5 - GND<br />
<br />
Example:<br />
<br />
At the LOCON16/17 the assignment of the X2 is as follows:<br />
<br />
PIN 26 - GND<br />
<br />
PIN 27 - Rx 232 (from the LOCON's point of view)<br />
<br />
PIN 28 - Tx 232 (from the LOCON's point of view)<br />
<br />
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.<br />
<br />
For the above example it comes to the following cable assignment:<br />
<br />
LOCON X2 PIN26 &harr; PC PIN5<br />
<br />
LOCON X2 PIN27 &harr; PC PIN3<br />
<br />
LOCON X2 PIN28 &harr; PC PIN2<br />
<br />
Note:<br />
Possible existing blue bridges between the signals "DICNET-/Rx" &harr; "R-" and "DICNET+/Tx" &harr; "R+" have to be removed.<br />
<br />
===How to reset LOCON 90, LOCON 100, LOCON 100-PB, LOCON 200, LOCON 200-PB, ROTARNOCK 100 or ROTARNOCK 100-PB back to delivery condition (reset)?===<br />
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 WINLOC 32 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 LOCON 100 with an expansion LOCON 100-A32 with DICNET communication, configured as Timer with a counting range of 16):<br />
<br />
''L100-48(48)-T16-485(DICNET) V3.4''<br />
<br />
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: <br />
''Reset configuration to defaultvalue and clear all programmed data (Y/N)? N''<br />
<br />
This query has to be confirmed with "y" within 3 seconds and another safety query follows:<br />
<br />
''Cancel operation (Y/N) N'' which is to be confirmed with "n".<br />
<br />
If the entry is correct, the following message appears in the terminal window:<br />
<div style="border: 1px solid #136db9; background-color: #fafafa; padding: 8px;"><br />
''Clear EEROM 0H-1fffH ...............................<br />
<br />
Restart<br />
<br />
L100-48(48)-S4096-485(DICNET) V3.4 ok<br />
<br />
(Error: 108)''<br />
</div><br />
With it the device was set back to the condition it was originally supplied.<br />
<br />
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.<br />
Note: After a reset the optional LOGIC-function has to be activated again. At the devices LOCON 100 & LOCON 200 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.<br />
<br />
===How to activate the logic function of LOCON 100-PB, LOCON 200, LOCON 200-PB, ROTARNOCK 100 or ROTARNOCK 100-PB?===<br />
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 LOCON 100-PB, LOCON 200 or LOCON 200-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.<br />
<br />
The device to be extended by the logic function must be connected to the PC and a start-up string has to be shown WINLOC 32.<br />
<br />
With a click on the menue ''Extras &rarr; Product Option Activation'' a window opens for activation.<br />
<br />
The DICNET-ID is entered in the line Device ID. For a connection through RS232 this value remains on "0".<br />
<br />
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 &harr; PC works).<br />
<br />
The release code is entered in the line ''Activation key''. Start behind the "-".<br />
Click on ''Run'' afterwards.<br />
<br />
(In case of an error "Returncode=4" is the result.)<br />
<br />
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:<br />
<br />
L200-16-S4096-H-''LG''-232 Vx.x<br />
<br />
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:<br />
<br />
Note: After a "Clear all" the logic function has to be released again.<br />
<br />
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 LOCON 100-PB; LOCON 200(-PB) & ROTARNOCK 100(-PB)".<br />
<br />
===External Wiring===<br />
====How is the modification from LOCON 32-HC or LOCON 32-PM to LOCON 24 carried out?====<br />
Introductorily we like to point out that this description refers to a LOCON 32-HC, that is/was configured "absolute parallel 360" as encoder type. Consequently the LOCON 24 also has to contain this "O360" in the article text.<br />
<br />
{| class="wikitable"<br />
!LOCON 24 !!Signal !!LOCON 32-HC !!LOCON 32-PM<br />
|-<br />
|X1 PIN 1 ||OUT 1 ||X10 PIN 2 ||X1 PIN 1<br />
|-<br />
|X1 PIN 2 ||OUT 2 ||X10 PIN 1 ||X1 PIN 2<br />
|-<br />
|X1 PIN 3 ||OUT 3 ||X10 PIN 4 ||X1 PIN 3<br />
|-<br />
|X1 PIN 4 ||OUT 4 ||X10 PIN 3 ||X1 PIN 4<br />
|-<br />
|X1 PIN 5 ||OUT 5 ||X10 PIN 6 ||X1 PIN 5<br />
|-<br />
|X1 PIN 6 ||OUT 6 ||X10 PIN 5 ||X1 PIN 6<br />
|-<br />
|X1 PIN 7 ||OUT 7 ||X10 PIN 8 ||X1 PIN 7<br />
|-<br />
|X1 PIN 8 ||OUT 8 ||X10 PIN 7 ||X1 PIN 8<br />
|-<br />
|X1 PIN 9 ||OUT 9 ||X10 PIN 10 ||X1 PIN 9<br />
|}<br />
<br />
... [http://www.deutschmann.de/en/support/faq_detail.html?question=18 more]<br />
<br />
=== Models ===<br />
==== What has to be considered when using a LOCON 200 in connection with TERM 24? ====<br />
If a (discontinued) device is supposed to be replaced by LOCON 200 and in case TERM 24 is used in the assembly, then the TERM 24's Firmware must be updated at any rate. For the update the device has to be sent back to us.<br />
<br />
==== TN65 - ROTARNOCK - what is it? ====<br />
It is the same unit. ROTARNOCK describes the product line and TN65 is the specific type or the article description.<br />
<br />
Example:<br />
ROTARNOCK 100 - describes the ROTARNOCK-family "100". The detailed article description is explained on the picture "Article description".<br />
<br />
[[Datei:Article description Rotarnock English.jpg|thumb|Article description]]<br />
<br />
<br />
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.<br />
<br />
==== How to change the Profibus Ident Number? ====<br />
To change the Profibus Ident Number from 3606H to 3231 the ROTARNOCK 100-PB has to be connected with the PC via a serial communication (RS232). For the serial communication the following pin assignemt is valid here:<br />
<br />
PC PIN2 (Rx) ↔ ROTARNOCK 25pin D-Sub PIN17 (Tx RED)<br /><br />
PC PIN3 (Tx) ↔ ROTARNOCK 25pin D-Sub PIN18 (Rx RED)<br /><br />
PC PIN5 (GND) ↔ ROTARNOCK 25pin D-Sub PIN25 (GND)<br />
<br />
A corresponding programming cable (including plug-in power supply) is to be ordered with the article number V3467. ( V3467 - Programming cable for ROTARNOCK - 232/PB).<br />
<br />
The software WINLOC 32 has to be installed on the PC. The interface parameters are entered in "Extras → Options → Port".<br />
<br />
If the ROTARNOCK is now supplied with voltage a window opens automatically and the device brings its start-up message, e. g.:<br />
'''R100-48-O4096-PB(126)-232 V3.54 Ok'''<br />
Now place in WINLOC 32 the cursor behind the last character (through a "left click") and press "n" while keeping the keys "STRG/CTRL" pressed.<br />
The following confirmation prompt appears:<br />
'''Ident-Nr=3606H, change to 3231H (Y/N)? N'''<br />
This query has to be confirmed with "'''y'''" within 3 seconds and the following confirmation appears:<br />
'''New Ident-Nr = 3231H'''<br />
After a re-start the device uses the new Ident Number and it can be put into operation.<br />
<br />
The same way the Ident Number can also be changed back from 3231H to 3606H.<br />
<br />
==== How to replace a ROTARNOCK 1/2/3/4 by a ROTARNOCK 100? ====<br />
There are two ways to carry out the exchange.<br />
<br />
'''1.'''<br />
Exchange with the convenient programming software for cam controls WINLOC 32 (recommended procedure):<br />
<br />
Read out (File&rarr;Upload) the ROTARNOCK that is to be replaced with the software WINLOC 32 and store (File&rarr;Save) it on the hard disk or open an existing configuration file.<br />
<br />
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:<br />
Encoder resolution, ITC (=idle time compensation) Type, Display factor, ITC Function, Turn Direction, Run-Control and Zero shift.<br />
<br />
Important: Please write down the indicated position during downtime (best in the basic position if possible) before removing the old device! <br />
<br />
Connect the ROTARNOCK 100 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 ROTARNOCK 100 back in default mode can be found here.<br />
<br />
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.<br />
<br />
Enter the value for the Virtual Resolution here and select the ITC Type and confirm it with OK. <br />
<br />
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!<br />
<br />
'''Important advice:'''<br />
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.<br />
<br />
We recommend to carry out the zero adjustment first before the cams are being transmitted to the device.<br />
Load the newly generated configuration in the ROTARNOCK 100 through Download. Install the ROTARNOCK 100 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.<br />
<br />
In WINLOC32 the cam values, idle times and output names are transmitted from the old configuration file to the new one through Extras &rarr; Data transfer. This function is only available in the Comfort version of WINLOC 32.<br />
<br />
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 [mailto:hotline@deutschmann.de hotline@deutschmann.de].<br />
<br />
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. <br />
<br />
'''2.'''<br />
Exchange with manual configuration and programming with TERM 6 or TERM 24 (with current Firmware):<br />
<br />
The following information on the ROTARNOCK that is to be exchanged should be available:<br />
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.<br />
<br />
Advice: In case your old device features the option R - RunControl, then the device has to be configured with WINLOC 32.<br />
<br />
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. <br />
<br />
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.<br />
<br />
Now you can start entering the cams and idle times and finally the application can be tested and be put into operation.<br />
<br />
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 WINLOC 32.<br />
<br />
===Software Tools===<br />
====Configuration- and programming-software for cam controls?====<br />
A configuration- and programming-software [[WINLOC 32 (English)|WINLOC 32]] is available for all Deutschmann cam controls (NS).<br />
<br />
The basic version of that software is available free of charge (in the download-area and on the support-DVD). This basic version already features extensive functions. The cam control can be read out, configured and programmed. Also these files can be stored. <br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
====How and where is to enter the WINLOC 32 comfort version license key?====<br />
First of all start WINLOC 32.<br />
<br />
In the menu line "Extras" &rarr; select "Options". A window opens. If necessary please change to the register "License".<br />
Now enter the license key you received from us.<br />
<br />
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 "*".<br />
<br />
A license that have been purchased once can be used for all follow-up versions. A WINLOC 6 license also works with WINLOC 32.<br />
<br />
== UNIGATE ==<br />
===How to carry out a Firmware update at UNIGATE?===<br />
You can find an explanation on the site [[Firmware-Aktualisierung/en|Firmware update]].<br />
<br />
===I encountered problems with the RS232 connection between UNIGATE and PC. What to do when WINGATE says "no Gateway found"?===<br />
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.<br />
<br />
===How to connect an UNIGATE with the RS232-interface (COM port) at the PC?===<br />
At the PC COM port there is a 9-pole D-SUB pin connection with the following assignment:<br />
<br />
PIN 2 - Rx (from the PC's point of view)<br />
<br />
PIN 3 - Tx (from the PC's point of view)<br />
<br />
PIN 5 - GND<br />
<br />
Example: At the UNIGATE CL the assignment of the X1 is as follows:<br />
<br />
PIN 1 - Rx 232 (from the UNIGATE's point of view)<br />
<br />
PIN 2 - Tx 232 (from the UNIGATE's point of view)<br />
<br />
PIN 3 - AP-GND<br />
<br />
Generally always the Rx of the PC has to be connected with the Tx of the UNIGATE and the Tx of the PC with the Rx of the UNIGATE. Also the GND always has to be connected.<br />
<br />
For the above example it comes to the following cable assignment:<br />
<br />
UNIGATE X1 PIN1 &harr; PC PIN3<br />
<br />
UNIGATE X1 PIN2 &harr; PC PIN2<br />
<br />
UNIGATE X1 PIN3 &harr; PC PIN5<br />
<br />
===Does UNIGATE have a "test mode"?===<br />
Yes, there is a test mode.<br />
<br />
The interface-switch has to be set to position »RS232« and the two rotary coding switches on the serial side (S4 + S5) have to be set to »EE« in order to put the device into the test mode.<br />
<br />
After the restart the UNIGATE sends a byte on the serial side from »0-F« every second (some devices will first do a 15 to 30 seconds lasting self test). On the Fieldbus this output occurs accordinglywith the length depending on the set bus width. If useful data is sent to the UNIGATE (serial and Fieldbus) they are sent back from the UNIGATE (ECHO).<br />
<br />
===How to get my script into the device?===<br />
'''Advice:''' Please always use the current version of the corresponding software.<br />
<br />
Basically there are two ways to load the script into the UNIGATE.<br />
<br />
'''Possibility 1''' - via the serial (application-) interface: (applies to ALL UNIGATE SC, IC & CL) The script has to be compiled in the PROTOCOL DEVELOPER by "File &rarr; save compiled file" (the script receives the file extension *.dcs), so that the script gets into the device this way. The device has to be set into the configuration mode in order to load the script into the device. The script download can be started with the software WINGATE through "File &rarr; Write Script". With the software SPT (ScriptProgramTool) the downlaod is initiated through "File &rarr; Open file and program".<br />
<br />
'''Possibility 2''' - via the DEBUG-interface and the software PROTOCOL DEVELOPER: (applies to ALL UNIGATE IC & CL as well as UNIGATE SC with option "DB") In this case the device's DEBUG-interface has to be connected with a PC COM-Port. In the software PROTOCOL DEVELOPER and belated power up of the device (NOT in the configuration mode) the message "Device started in Debug mode" appears in the bottom left corner. Now the download can be started with "DEBUG".<br />
<br />
===How to set the UNIGATE into the configuration mode (Configmode)?===<br />
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.<br />
For the UNIGATE CL the RS232 interface is automatically active throught the switch positions of S4+S5 with "FF".<br />
If you use the UNIGATE IC the basis board of the J17.<br />
<br />
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):<br />
<br />
''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''<br />
Configmode...<br />
<br />
Now you know that the unit is in configuration mode.<br />
<br />
'''Practice Tip:''' With UNIGATE CL, RS and SC the configuration mode is visually indicated by the RS-"State" LED flashing red.<br />
<br />
=== What is to consider when switching to UNIGATE CL from UNIGATE SC? ===<br />
There is one significant difference between an UNIGATE SC and an UNIGATE CL: the UNIGATE SC devices have a hardware switch "232 &harr; 485", which does not exist on an UNIGATE CL. The UNIGATE 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 <br />
<source lang="delphi"> Set(RS_Type,[?]) </source> <br />
command.<br />
In the PROFIBUS version there is also the difference of the ID number. The UNIGATE CL-DP needs the GSD file UGIC3218.gsd.<br />
<br />
=== Does the UNIGATE IC support SPI?===<br />
Yes, the UNIGATE IC supports SPI. (Up-to-date [http://www.deutschmann.de/de/produkte/download.php?file_id=412 UNIGATE IC Pinout-List] in XLS Format)<br />
Pin 3...7 are for the SPI Master (SPI slave on request only)<br />
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.<br />
<br />
===How to connect two networks (PROFIBUS / PROFINET)?===<br />
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.<br />
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.<br />
<br />
===Fieldbus===<br />
====CANopen====<br />
=====UNIGATE CO (M)-PROFIBUS DP===== <br />
=====I encountered problems after downloading the existing/old GWC-file into my new device. Can you list the various steps?=====<br />
#Open the desired GWC file with the configuration tool WINGATE. <br />
#Then start the new device and perform the download<br />
#Now perform an Upload from the device<br />
#The parameter "CAN baud rate" is now at 125k. <br />
#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.<br />
#Afterwards perform another download<br />
#Save the change, respectively the "new" GWC file<br />
<br />
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.<br />
<br />
=====How to replace CANopen (Master) - PROFIBUS DP (Slave)?=====<br />
#Start WINGATE:<br />
#Connect the RS232 from PC to UNIGATE (3 wire, 3 pin connector)<br />
#Connect power supply<br />
#Upload file<br />
#Save file<br />
#Disconnect the old UNIGATE <br />
#Connect the new UNIGATE (see Step 1)<br />
#Afterwards click "File - Download" (write to device)<br />
<br />
<br />
<gallery><br />
Datei:Start WINGATE V2.65(379).png|1. Start WINGATE<br />
Datei:WINGATE_V2.64(379)_Versorgungsanschluss.png|3. Connect power supply<br />
Datei:WINGATE_V2.65(379)_File_upload.png|4. File upload<br />
Datei:WINGATE_Save_as.png|4. Save as<br />
Datei:WINGATE_V2.65(379)_File_download_screen.png|8. File-Download<br />
</gallery><br />
<br />
=====In WINGATE-File the Adresse 0x14 is set to 0=====<br />
With the new Firmware V2.60 in WINGATE the config file has to be stored with the setting "baud rate: DIP Switch"<br />
<br />
====DeviceNet====<br />
=====How much power does the UNIGATE IC draw at the DeviceNet power supply 24 Volt connector, PIN 17?=====<br />
The current consumption is max. 35mA.<br />
<br />
====EtherNet/IP====<br />
=====How to switch to EtherNet/IP 2Port?=====<br />
You can find more about switching to EtherNet/IP 2 Port on the UNIGATE CL EtherNet/IP site: [[UNIGATE_EtherNet/IP/en|Changeover to 2-Port devices]]<br />
<br />
=====My PLC cannot establish a connection to my EtherNet/IP device. What could be the reason?=====<br />
Maybe you configured your PLC to use a Unicast connection.<br />
<br />
If you are using the Rockwell software RSLogix 5000 you can check this in the UNIGATE's module properties dialogue. Please make sure the option "Use Unicast Connection over EtherNet/IP" on the connection tab is disabled.<br />
<br />
===== Why does the function <code>ReadNewObjectDataEIP</code> show a change of input data, altough all of the data is identical? =====<br />
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.<br />
<br />
===== Can I only transfer an even number of bytes with an EtherNet/IP device? =====<br />
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).<br />
<br />
=====Can a power supply separation be avoided through a script adaptation in a UNIGATE EtherNet/IP with firmware 4.0?=====<br />
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).<br />
<br />
====Fast Ethernet====<br />
=====Is there an example of the web server functionality ?=====<br />
Yes, there is an example, which is available after installing the PROTOCOL DEVELOPER.<br />
# Start the UNIGATE CL-FE in configmode<br />
# Reset device (WINGATE - options - reset device)<br />
# Save the script example: Wingate – File – Write script ... :\Software\ProtocolDeveloper\Example\08 Bus specific\Fast Ethernet script.dcs<br />
# Set the IP address and the subnet mask (Do not forget to download the file)<br />
# Start the UNIGATE in Run mode (S4+5 not FF and not EE)<br />
# Start a FTP Client, such as [http://www.ghisler.com/index.htm Total Commander]. Establish a FTP connection. (Username and password: deutschmann)<br />
# Directory: Flash<br />
# Copy "index.html" to CL-FE<br />
# Start your browser and enter the IP address you created in WINGATE<br />
# If you refresh your browser (F5) you will see that the numerical value increased<br />
# That's it!<br />
<br />
<gallery><br />
Datei:WINGATE V2.72(385) Set IP Adress set subnet mask.png|4. IP address and subnet mask<br />
Datei:FTP TotalCommander Connection details.png|6. FTP Client<br />
Datei:FTP TotalCommander Verzeichnis flash.png|7. Change directory<br />
Datei:FTP TotalCommander Copy index.png|8. Copy index.html <br />
Datei:WINGATE FTP Browser.png|9. IP address in Browser<br />
</gallery><br />
<br />
=====Is the temperature range down to -40°C by now available for CL devices with RJ45 connectors?=====<br />
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.<br />
In our expansion card for CL and FC a RJ45 for -40°C is used.<br />
<br />
====PROFIBUS====<br />
=====At commissioning a PROFIBUS-slave I do not see any input data when put and also it is not possible to send data to the device.=====<br />
For CPUs from the company Siemens only direct access up to 4 bytes is possible. Provided that useful data > 4 bytes are supposed to be read or written, then the access has to be made through the SFC14 (read) and SFC15 (write). Further information can be found in the projection software's help.<br />
<br />
=====How to use the UNIGATE IC PROFIBUS DPV1 5V without driver 485 and how much current can the DC/DC converter provide on the fieldbus side?=====<br />
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.<br />
<br />
=====Changing of the Slave ID via SPS=====<br />
ID is stored in EEROM.<br />
<source lang="delphi"><br />
var LBusState : Long ;<br />
var L0xE0 : Long ; moveconst ( L0xE0, 0xE0);<br />
<br />
BusStart ;<br />
//Wait ( Bus_Active ) ;<br />
<br />
:LoopBusState;<br />
Get ( ReadBusState , LBusState ) ;<br />
if LBusState less L0xE0 then :LoopBusState; //!!! neu<br />
</source><br />
<br />
=====Which GSD-file is meant for my device?=====<br />
We distinguish between 2 versions: DPV0 and DPV1. You can tell from the article description which device is in front of you. A »DP« stands for DPV0; a »DPV1« for itself. The UNIGATE IC-DPL and UNIGATE CL is a DPV1-device.<br />
<br />
In the download-area of the respective device only that GSD-file, which is valid for the corresponding device only, is placed at your disposal for download.<br />
<br />
A DPV1 slave is downwards compatible and it can also operate in the DPV0 mode. Nevertheless, the DPV1 GSD-file has to be used.<br />
<br />
DPV0 slave &rarr; GSDfile »DAGW2079.GSD«<br />
<br />
DPV1 slave &rarr; GSD-file »UGIC3218.GSD«<br />
<br />
=====GSD Datei - How to create a different configuration?=====<br />
[[Datei:PB_GSD_Configuration_telegramm_8_Word_Out.jpg|thumb|Create a configuration]]<br />
<br />
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.<br />
In this Modul, you can setup every size.<br />
<br />
=====How to set the Slave ID via the Master?=====<br />
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.<br />
<br />
WARNING: With it the EEROM will be re-initialized and the script will be deleted.<br />
<br />
=====How to realize the conversion from Fieldbus &harr; Modbus RTU (Master)?=====<br />
''This proceeding for a UNIGATE CL-PROFIBUS DPV1 is used as an example for all UNIGATEs and the supported Fieldbuses.''<br />
<br />
UNIGATE CL is supplied with a Universal Script that makes setting the "Modbus RTU (Master)" protocol very simple. A detailed description how to configure the device can be found here.<br />
<br />
Note: In case you want to read out the same register several times, then the parameter ''"Data Exchange"'' should be adjusted to ''"On Trigger"''. In this case the UNIGATE expects the togglebyte in the Fieldbus Master's first byte.<br />
<br />
Application:<br />
<br />
The Fieldbus Master requests (read holding register = 03) the register "4567" with the length of 1 word from the Modbus Slave with the ID=2. The resulting inquiry from the Profibus-Master to the UNIGATE is:<br />
<br />
02 03 45 67 00 01<br />
<br />
(ID=2, read register=03, register=4567 and length in words high + low=0001) <br />
<br />
The UNIGATE converts data to Modbus and adds the checksum (=xx):<br />
<br />
02 03 4567 00 01 xx<br />
<br />
The UNIGATE receives the following response from the Modbus Slave with the ID=2:<br />
<br />
02 03 02 03 E8 xx<br />
<br />
(ID=2, read register=03, length in byte =02, value of the register 4567=03E8 and checksum=xx)<br />
<br />
The UNIGATE puts the Modbusslave's response on the Fieldbus:<br />
<br />
02 03 02 03 E8<br />
<br />
Consequently a complete inquiry from the Fieldbus Masters has been converted to Modbus and the Slave's response has been issued to the Fieldbus in turn.<br />
<br />
The above proceeding describes the function of the UNIGATE RS, UNIGATE CL with Universal Script and configured Modbus-RTU(Master) protocol as well as our Script examples Modbus-RTU(Master).<br />
<br />
There are also applications, in which the UNIGATE is supposed to read out a corresponding register or also the UNIGATE cyclically reads the same regsiter again and again through only 1 byte of the Fieldbus Master. With our UNIGATE SC, CL and IC this is possible without a problem. In these two cases the Script only has to be adapted to this requirement. Please use our Script examples for this.<br />
<br />
====PROFINET====<br />
=====How to connect Deutschmann PROFINET devices to a S7?=====<br />
For a step-by-step instruction, please download the PDF [http://deutschmann.de/produkte/download.php?file_id=681].<br />
<br />
=====How to evaluate a UNIGATE device with a PROFINET interface?=====<br />
You can evaluate your PROFINET device (UNIGATE CL-Profinet, UNIGATE IC-Profinet, UNIGATE FC-Profinet) with our free PROFINET Module software. All you need is a Microsoft Windows computer with an Ethernet port. The PROFINET Module software is part of our Starter Kit software collection which can be obtained from the download section.<br />
<br />
=====Why can't I assign a device name to my UNIGATE?=====<br />
For PROFINET the device name is subject to a [[PROFINET_Device_name_(English)|naming convention]]. For example, the use of capital letters is not allowed.<br />
<br />
=====How to rename the GSDML file?=====<br />
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.<br />
<br />
=====Script with station name=====<br />
[[Datei:PN_Script_mit_Stationsname_Set_device.png|thumb|Script with station name]]<br />
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.<br />
If a name is then set in the PROFINET Master it is effective from now on.<br />
<br />
===Series===<br />
====UNIGATE CL====<br />
=====Can I use my configuration file of the series UNIGATE RS for UNIGATE CL as well?=====<br />
We will be supplying the devices UNIGATE CL with a "UNIVERSAL" script (if it had not been handled that way so far). This script then acts as if it was a UNIGATE RS. That means that the UNIGATE CL can be parameterized via the configuration software WINGATE. An "old" UNIGATE RS configuration file is not compatible with that of the UNIGATE CL. If a UNIGATE RS is to be changed over to UNIGATE CL, then the UNIGATE CL must be read out once via WINGATE and the protocol settings have to be made. This configuration can then be stored in the usual manner and it can be used again for devices of the same type.<br />
<br />
Note: If a "Reset Device" is carried out with a UNIGATE CL, then the "UNIVERSAL" script gets lost and it has to be loaded again.<br />
<br />
=====I want to download my UNIGATE SC-PB Script into the UNIGATE CL-PB. The PROFIBUS State LED remains red and/or the serial communication does not work.=====<br />
This "phenomenon" has two reasons:<br />
<br />
# The UNIGATE SC-PB requires the GSD-file "DAGW2079.gsd" and the UNIGATE CL-PB requires the GSD-file "UGIC3218.gsd".<br />
# The interface of the UNIGATE SC-PB is set via the switch "Interface" and at the UNIGATE CL-PB it is set in the Script.<br />
<br />
Remedy:<br />
1. Either the GSD-file for the UNIGATE CL-PB in the PROFIBUS Master in the hardware configuration is changed to "UGIC3218.gsd" or the Ident number has to be changed to "2079" in the Script through the command:<br />
Set ( IdentNumber , 0x2079 ) ; //default: 0x3218<br />
<br />
After the Script download the UNIGATE CL-PB acts like a UNIGATE SC-PB at the PROFIBUS.<br />
<br />
2. The interfaces of the UNIGATE CL-PB have to be defined in the Script by means of the Script command:<br />
Set ( RS_Type , RS232 ) ; //or RS485 or RS422<br />
<br />
=====How to configure the UNIGATE CL with WINGATE?=====<br />
Note: This instruction refers to the configuration of UNIGATE CL in connection with the Universal Script.<br />
<br />
The current version of the software WINGATE has to be installed on the PC in order to be able to configure the UNIGATE CL.<br />
<br />
Subsequently the UNIGATE CL has to be connected to the PC via the application interface X1. The required wiring can be found here.<br />
<br />
<br />
The "Universalscript Deutschmann" has to be available in the device, so that it can be configured by WINGATE. When the software WINGATE is executed and the UNIGATE is restarted then you receive the following actuation message from the UNIGATE in the lower part of WINGATE (example: V3553 UNIGATE CL-ProfibusDP):<br />
<br />
RS-PBV1-CL (232/422/485) V7.31[30] (c)dA Switch=0x01FF Script(16k)="Universalscript Deutschmann" Author="G/S" Version="V 0.2d" Date 24.07.2008 SN: 3553xxxx ID=1<br />
Konfigmode...<br />
<br />
IMPORTANT: ALL following points cannot be carried out unless you receive this message (with or without "Universalscript Deutschmann")!<br />
<br />
In case the Script is not in the device, it can be loaded into the UNIGATE with the function File -> ''Write Script'' (the Script can be found on the Support CD at: \Software\ProtocolDeveloper\Example\Universal\CL_Universal.dcs or on our website in category "Software").<br />
<br />
Now the UNIGATE CL can be read-out through ''File &rarr; Upload''. Both options ''more items visible & more items editable'' have to be acivated in order to be able to set all functions.<br />
<br />
The configuration itself should be made from the top to the bottom. The desired parameters can be moved to the corresponding line with double-click.<br />
<br />
When the configuration is completed the altered values have to written into the device with ''File &rarr; Download''. This is confirmed by the UNIGATE with:<br />
<br />
Download ok<br />
<br />
Store data... ...<br />
<br />
Restart<br />
<br />
RS-PBV1-CL (232/422/485) V7.31[30] (c)dA Switch=0x01FF Script(16k)="Universalscript Deutschmann" Author="G/S" Version="V 0.2d" Date 24.07.2008 SN: 3553xxxx ID=1<br />
Konfigmode...<br />
<br />
With it the configuration is finished. Now the device has to be switched to 'voltageless' and the rotary switch at the device has to be adjusted accordingly and connected to the application. Now the device can be put into operation.<br />
<br />
=====Can you deliver the Protocol Converter UNIGATE CL in a lacquered version?=====<br />
The lacquering of this series does not make sense, since the mechanical oponents such as rotary coding switches, plug connectors, etc. can not be lacquered and thus a disruption would occur.<br />
<br />
====UNIGATE IC====<br />
=====Problem with the virtual COM-ports via USB=====<br />
If the Developerboard UNIGATE IC-AB is connected via the USB-interface, then the following procedure has to be taken into account:<br />
<br />
# Adjust all switches, rotary switches and jumpers in accordance to the UNIGATE IC that is to be used.<br />
# Connect the Developerboard UNIGATE IC-AB through the USB-cable to the PC/laptop and supply the Developerboard UNIGATE IC-AB with voltage through the provided power supply.<br />
# Put the UNIGATE IC on the socket of the Developerboard UNIGATE IC-AB and set the switch ''POWER'' to position ON afterwards. Only now the operating system of the PC recognizes the new virtual interfaces and during initial startup the drivers are installed.<br />
# Execute the corresponding software application now and select the (new) interface in ''Options''.<br />
# Please push the button ''Reset''. The device responds now (provided that the switch ''Mode is set to Config'') with the startup message or the Script is being executed (switch ''Mode on Run'' and the software ''PROTOCOL DEVELOPER'' is not initiated) or the device starts in the DebugMode (if the switch ''Mode is set to Run'' and the software ''PROTOCOL DEVELOPER'' is being executed).<br />
<br />
Therefore the switch ''POWER'' should not be changed any more since the virtual COM-ports will be re-initialized again with any change from ''ON&rarr;OFF&rarr;ON''.<br />
<br />
=====Is it possible to lacquer the series UNIGATE IC?=====<br />
There is no reason why the series UNIGATE IC cannot be lacquered. However, the complete assembly (the whole customer's device) should be lacquered in one piece. To lacquer the UNIGATE IC first would involve a disproportionate high effort, which would lead to high costs (e. g. The software would have to be downloaded before, tapeing of the pins and so on). Therefore we are not supplying the UNIGATE IC-series in lacquered form.<br />
<br />
====UNIGATE RS====<br />
The lacquering of this series does not make sense, since the mechanical oponents such as rotary coding switches, plug connectors, etc. can not be lacquered and thus a disruption would occur. We offer die-cast aluminium housing for these applications.<br />
<br />
===PROTOCOL DEVELOPER===<br />
====The PROTOCOL DEVELOPERs help window is empty. What can I do?====<br />
By default the help-file has to be existent on a local drive (e. g. C:\)<br />
<br />
In order to be able to also access the help-file from a network drive the following lines have to be entered into Notepad and saved as "*.REG" file:REGEDIT4 <br />
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp] <br />
<br />
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp\1.x\HHRestrictions] <br />
<br />
"MaxAllowedZone"=dword:00000001 "EnableFrameNavigationInSafeMode"=dword:00000001 <br />
<br />
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp\1.x\ItssRestrictions] <br />
<br />
"MaxAllowedZone"=dword:00000001When the file has been generated it is executed with a double click. The PC has to be restarted, so that the changes will be accepted.<br />
<br />
For further information as well as possible risks please log on to: http://support.microsoft.com/kb/896358/de<br />
<br />
<br />
''Microsoft Windows Vista:''<br />
<br />
By default the access to "*.CHM"-files is denied. In order to make an access possible though, click with the right button on the the file properties under General on Unblock. The help file opens now.<br />
<br />
===WINGATE===</div>Reithhttps://wiki.deutschmann.de/index.php?title=en:Frequently_asked_questions_Fieldbus-_and_Industrial-Ethernet-Devices&diff=3454en:Frequently asked questions Fieldbus- and Industrial-Ethernet-Devices2019-08-27T14:11:17Z<p>Reith: /* What has to be considered when using a LOCON 200 in connection with TERM 24? */</p>
<hr />
<div>== Electronic Cam Controls ==<br />
===Are there replacements for a product that is no longer available? (LOCON 32-HC, LOCON 32-PM)...===<br />
1. Substitution option with [[LOCON 24 (English)|LOCON 24]]:<br />
<br />
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.<br />
<br />
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.<br />
<br />
2. Substitution option with [[LOCON 100 (English)|LOCON 100]] / [[LOCON 200 (English)|LOCON 200]]:<br />
<br />
Basically the following points ALWAYS have to be clarified in case of replacing a product that is no longer available: (Example in italic)<br />
* Which encoder is used in connection with the cam control (NSW) (maximum of 16 inputs) &rarr; number of encoder inputs &rarr; at INC. at least 2, at absolute &rarr; number of tracks = number inputs)<br />
<br />
''A TA58-O360-GYE is used &rarr; 9 tracks = 9 inputs''<br />
<br />
* What other pins are used? (e. g. at INC. encoders Clear + and/or Clear- &rarr; number of inputs +1 or +2)<br />
<br />
''None &rarr; + 0 inputs''<br />
<br />
* Is the Prog.Enable wired? (if yes &rarr; number of inputs +1)<br />
<br />
''Yes. &rarr; +1 input''<br />
<br />
* Is the external program selection wired? If yes, how many programs? (number of inputs +2 ... +7)<br />
<br />
''Yes, up to program 8. 5 pins are required for it &rarr; +5 inputs''<br />
<br />
According to the amount here the decision is made, whether [[LOCON 100 (English)|LOCON 100]] or [[LOCON 200 (English)|LOCON 200]] can be used. Provided that the amount remains below 16, either a [[LOCON 100 (English)|LOCON 100]] or a [[LOCON 200 (English)|LOCON 200]] can be used. If the amount of required inputs exceeds 16, then a [[LOCON 100 (English)|LOCON 100]] 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 [[LOCON 100 (English)|LOCON 100]] or [[LOCON 200 (English)|LOCON 200]] can be used. <br />
<br />
Quantity determination of expansion modules that have to be used (LOCON 100-A32 or LOCON 200-IO8):<br />
<br />
* Is the RunControl-relay wired? If yes &rarr; number of outputs + 1<br />
<br />
''Yes. + 1 output for RunControl''<br />
<br />
* How many outputs are used at the cam control? &rarr; Number of the basis' remaining outputs (LOCON 100 + LOCON 200) = 16 - number of inputs<br />
<br />
''32 outputs are used. &rarr; Total = 1 + 32 = 33 outputs. Either LOCON 100 (1 output) with an LOCON 100-A32 extension (=32 outputs) OR LOCON 200 (1 output) + 3 x LOCON 200-IO8 (8 outputs each = 32 outputs) can be used here.''<br />
<br />
Basically the version LOCON 200 + LOCON 200-IO8 is to be favored, since the cycle times for this constellation are lower than those for LOCON 100.<br />
<br />
On principle it does not matter which TERM is used. [[LOCON 100 (English)|LOCON 100]] & [[LOCON 200 (English)|LOCON 200]] are supported by TERM 6, TERM 24 & TERM 32 to a partially limited extent. For that reason the parameterization and configuration should principally always be carried out with [[WINLOC 32 (English)|WINLOC 32]] and the mentioned TERMs should be used for operation.<br />
<br />
===How to connect a LOCON with the RS232-interface (COM port) at the PC?===<br />
At the PC COM port there is a 9-pole D-SUB pin connection with the following assignment:<br />
<br />
PIN 2 - Rx (from the PC's point of view)<br />
<br />
PIN 3 - Tx (from the PC's point of view)<br />
<br />
PIN 5 - GND<br />
<br />
Example:<br />
<br />
At the LOCON16/17 the assignment of the X2 is as follows:<br />
<br />
PIN 26 - GND<br />
<br />
PIN 27 - Rx 232 (from the LOCON's point of view)<br />
<br />
PIN 28 - Tx 232 (from the LOCON's point of view)<br />
<br />
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.<br />
<br />
For the above example it comes to the following cable assignment:<br />
<br />
LOCON X2 PIN26 &harr; PC PIN5<br />
<br />
LOCON X2 PIN27 &harr; PC PIN3<br />
<br />
LOCON X2 PIN28 &harr; PC PIN2<br />
<br />
Note:<br />
Possible existing blue bridges between the signals "DICNET-/Rx" &harr; "R-" and "DICNET+/Tx" &harr; "R+" have to be removed.<br />
<br />
===How to reset LOCON 90, LOCON 100, LOCON 100-PB, LOCON 200, LOCON 200-PB, ROTARNOCK 100 or ROTARNOCK 100-PB back to delivery condition (reset)?===<br />
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 WINLOC 32 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 LOCON 100 with an expansion LOCON 100-A32 with DICNET communication, configured as Timer with a counting range of 16):<br />
<br />
''L100-48(48)-T16-485(DICNET) V3.4''<br />
<br />
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: <br />
''Reset configuration to defaultvalue and clear all programmed data (Y/N)? N''<br />
<br />
This query has to be confirmed with "y" within 3 seconds and another safety query follows:<br />
<br />
''Cancel operation (Y/N) N'' which is to be confirmed with "n".<br />
<br />
If the entry is correct, the following message appears in the terminal window:<br />
<div style="border: 1px solid #136db9; background-color: #fafafa; padding: 8px;"><br />
''Clear EEROM 0H-1fffH ...............................<br />
<br />
Restart<br />
<br />
L100-48(48)-S4096-485(DICNET) V3.4 ok<br />
<br />
(Error: 108)''<br />
</div><br />
With it the device was set back to the condition it was originally supplied.<br />
<br />
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.<br />
Note: After a reset the optional LOGIC-function has to be activated again. At the devices LOCON 100 & LOCON 200 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.<br />
<br />
===How to activate the logic function of LOCON 100-PB, LOCON 200, LOCON 200-PB, ROTARNOCK 100 or ROTARNOCK 100-PB?===<br />
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 LOCON 100-PB, LOCON 200 or LOCON 200-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.<br />
<br />
The device to be extended by the logic function must be connected to the PC and a start-up string has to be shown WINLOC 32.<br />
<br />
With a click on the menue ''Extras &rarr; Product Option Activation'' a window opens for activation.<br />
<br />
The DICNET-ID is entered in the line Device ID. For a connection through RS232 this value remains on "0".<br />
<br />
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 &harr; PC works).<br />
<br />
The release code is entered in the line ''Activation key''. Start behind the "-".<br />
Click on ''Run'' afterwards.<br />
<br />
(In case of an error "Returncode=4" is the result.)<br />
<br />
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:<br />
<br />
L200-16-S4096-H-''LG''-232 Vx.x<br />
<br />
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:<br />
<br />
Note: After a "Clear all" the logic function has to be released again.<br />
<br />
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 LOCON 100-PB; LOCON 200(-PB) & ROTARNOCK 100(-PB)".<br />
<br />
===External Wiring===<br />
====How is the modification from LOCON 32-HC or LOCON 32-PM to LOCON 24 carried out?====<br />
Introductorily we like to point out that this description refers to a LOCON 32-HC, that is/was configured "absolute parallel 360" as encoder type. Consequently the LOCON 24 also has to contain this "O360" in the article text.<br />
<br />
{| class="wikitable"<br />
!LOCON 24 !!Signal !!LOCON 32-HC !!LOCON 32-PM<br />
|-<br />
|X1 PIN 1 ||OUT 1 ||X10 PIN 2 ||X1 PIN 1<br />
|-<br />
|X1 PIN 2 ||OUT 2 ||X10 PIN 1 ||X1 PIN 2<br />
|-<br />
|X1 PIN 3 ||OUT 3 ||X10 PIN 4 ||X1 PIN 3<br />
|-<br />
|X1 PIN 4 ||OUT 4 ||X10 PIN 3 ||X1 PIN 4<br />
|-<br />
|X1 PIN 5 ||OUT 5 ||X10 PIN 6 ||X1 PIN 5<br />
|-<br />
|X1 PIN 6 ||OUT 6 ||X10 PIN 5 ||X1 PIN 6<br />
|-<br />
|X1 PIN 7 ||OUT 7 ||X10 PIN 8 ||X1 PIN 7<br />
|-<br />
|X1 PIN 8 ||OUT 8 ||X10 PIN 7 ||X1 PIN 8<br />
|-<br />
|X1 PIN 9 ||OUT 9 ||X10 PIN 10 ||X1 PIN 9<br />
|}<br />
<br />
... [http://www.deutschmann.de/en/support/faq_detail.html?question=18 more]<br />
<br />
=== Models ===<br />
==== What has to be considered when using a LOCON 200 in connection with TERM 24? ====<br />
If a (discontinued) device is supposed to be replaced by LOCON 200 and in case TERM 24 is used in the assembly, then the TERM 24's Firmware must be updated at any rate. For the update the device has to be sent back to us.<br />
<br />
==== TN65 - ROTARNOCK - what is it? ====<br />
It is the same unit. ROTARNOCK describes the product line and TN65 is the specific type or the article description.<br />
<br />
Example:<br />
ROTARNOCK 100 - describes the ROTARNOCK-family "100". The detailed article description is explained on the picture "Article description".<br />
<br />
[[Datei:Article description Rotarnock English.jpg|thumb|Article description]]<br />
<br />
<br />
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.<br />
<br />
==== How to change the Profibus Ident Number? ====<br />
To change the Profibus Ident Number from 3606H to 3231 the ROTARNOCK 100-PB has to be connected with the PC via a serial communication (RS232). For the serial communication the following pin assignemt is valid here:<br />
<br />
PC PIN2 (Rx) ↔ ROTARNOCK 25pin D-Sub PIN17 (Tx RED)<br /><br />
PC PIN3 (Tx) ↔ ROTARNOCK 25pin D-Sub PIN18 (Rx RED)<br /><br />
PC PIN5 (GND) ↔ ROTARNOCK 25pin D-Sub PIN25 (GND)<br />
<br />
A corresponding programming cable (including plug-in power supply) is to be ordered with the article number V3467. ( V3467 - Programming cable for ROTARNOCK - 232/PB).<br />
<br />
The software WINLOC 32 has to be installed on th PC. The interface parameters are entered in "Extras → Options → Port".<br />
<br />
If the ROTARNOCK is now supplied with voltage a window opens automatically and the device brings its start-up message, e. g.:<br />
'''R100-48-O4096-PB(126)-232 V3.54 Ok'''<br />
Now place in WINLOC 32 the cursor behind the last character (through a "left click") and press "n" while keeping the keys "STRG/CTRL" pressed.<br />
The following confirmation prompt appears:<br />
'''Ident-Nr=3606H, change to 3231H (Y/N)? N'''<br />
This query has to be confirmed with "'''y'''" within 3 seconds and the following confirmation appears:<br />
'''New Ident-Nr = 3231H'''<br />
After a re-start the device uses the new Ident Number and it can be put into operation.<br />
<br />
The same way the Ident Number can also be changed back from 3231H to 3606H.<br />
<br />
==== How to replace a ROTARNOCK 1/2/3/4 by a ROTARNOCK 100? ====<br />
There are two ways to carry out the exchange.<br />
<br />
'''1.'''<br />
Exchange with the convenient programming software for cam controls WINLOC 32 (recommended procedure):<br />
<br />
Read out (File&rarr;Upload) the ROTARNOCK that is to be replaced with the software WINLOC 32 and store (File&rarr;Save) it on the hard disk or open an existing configuration file.<br />
<br />
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:<br />
Encoder resolution, ITC (=idle time compensation) Type, Display factor, ITC Function, Turn Direction, Run-Control and Zero shift.<br />
<br />
Important: Please write down the indicated position during downtime (best in the basic position if possible) before removing the old device! <br />
<br />
Connect the ROTARNOCK 100 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 ROTARNOCK 100 back in default mode can be found here.<br />
<br />
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.<br />
<br />
Enter the value for the Virtual Resolution here and select the ITC Type and confirm it with OK. <br />
<br />
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!<br />
<br />
'''Important advice:'''<br />
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.<br />
<br />
We recommend to carry out the zero adjustment first before the cams are being transmitted to the device.<br />
Load the newly generated configuration in the ROTARNOCK 100 through Download. Install the ROTARNOCK 100 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.<br />
<br />
In WINLOC32 the cam values, idle times and output names are transmitted from the old configuration file to the new one through Extras &rarr; Data transfer. This function is only available in the Comfort version of WINLOC 32.<br />
<br />
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 [mailto:hotline@deutschmann.de hotline@deutschmann.de].<br />
<br />
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. <br />
<br />
'''2.'''<br />
Exchange with manual configuration and programming with TERM 6 or TERM 24 (with current Firmware):<br />
<br />
The following information on the ROTARNOCK that is to be exchanged should be available:<br />
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.<br />
<br />
Advice: In case your old device features the option R - RunControl, then the device has to be configured with WINLOC 32.<br />
<br />
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. <br />
<br />
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.<br />
<br />
Now you can start entering the cams and idle times and finally the application can be tested and be put into operation.<br />
<br />
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 WINLOC 32.<br />
<br />
===Software Tools===<br />
====Configuration- and programming-software for cam controls?====<br />
A configuration- and programming-software [[WINLOC 32 (English)|WINLOC 32]] is available for all Deutschmann cam controls (NS).<br />
<br />
The basic version of that software is available free of charge (in the download-area and on the support-DVD). This basic version already features extensive functions. The cam control can be read out, configured and programmed. Also these files can be stored. <br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
====How and where is to enter the WINLOC 32 comfort version license key?====<br />
First of all start WINLOC 32.<br />
<br />
In the menu line "Extras" &rarr; select "Options". A window opens. If necessary please change to the register "License".<br />
Now enter the license key you received from us.<br />
<br />
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 "*".<br />
<br />
A license that have been purchased once can be used for all follow-up versions. A WINLOC 6 license also works with WINLOC 32.<br />
<br />
== UNIGATE ==<br />
===How to carry out a Firmware update at UNIGATE?===<br />
You can find an explanation on the site [[Firmware-Aktualisierung/en|Firmware update]].<br />
<br />
===I encountered problems with the RS232 connection between UNIGATE and PC. What to do when WINGATE says "no Gateway found"?===<br />
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.<br />
<br />
===How to connect an UNIGATE with the RS232-interface (COM port) at the PC?===<br />
At the PC COM port there is a 9-pole D-SUB pin connection with the following assignment:<br />
<br />
PIN 2 - Rx (from the PC's point of view)<br />
<br />
PIN 3 - Tx (from the PC's point of view)<br />
<br />
PIN 5 - GND<br />
<br />
Example: At the UNIGATE CL the assignment of the X1 is as follows:<br />
<br />
PIN 1 - Rx 232 (from the UNIGATE's point of view)<br />
<br />
PIN 2 - Tx 232 (from the UNIGATE's point of view)<br />
<br />
PIN 3 - AP-GND<br />
<br />
Generally always the Rx of the PC has to be connected with the Tx of the UNIGATE and the Tx of the PC with the Rx of the UNIGATE. Also the GND always has to be connected.<br />
<br />
For the above example it comes to the following cable assignment:<br />
<br />
UNIGATE X1 PIN1 &harr; PC PIN3<br />
<br />
UNIGATE X1 PIN2 &harr; PC PIN2<br />
<br />
UNIGATE X1 PIN3 &harr; PC PIN5<br />
<br />
===Does UNIGATE have a "test mode"?===<br />
Yes, there is a test mode.<br />
<br />
The interface-switch has to be set to position »RS232« and the two rotary coding switches on the serial side (S4 + S5) have to be set to »EE« in order to put the device into the test mode.<br />
<br />
After the restart the UNIGATE sends a byte on the serial side from »0-F« every second (some devices will first do a 15 to 30 seconds lasting self test). On the Fieldbus this output occurs accordinglywith the length depending on the set bus width. If useful data is sent to the UNIGATE (serial and Fieldbus) they are sent back from the UNIGATE (ECHO).<br />
<br />
===How to get my script into the device?===<br />
'''Advice:''' Please always use the current version of the corresponding software.<br />
<br />
Basically there are two ways to load the script into the UNIGATE.<br />
<br />
'''Possibility 1''' - via the serial (application-) interface: (applies to ALL UNIGATE SC, IC & CL) The script has to be compiled in the PROTOCOL DEVELOPER by "File &rarr; save compiled file" (the script receives the file extension *.dcs), so that the script gets into the device this way. The device has to be set into the configuration mode in order to load the script into the device. The script download can be started with the software WINGATE through "File &rarr; Write Script". With the software SPT (ScriptProgramTool) the downlaod is initiated through "File &rarr; Open file and program".<br />
<br />
'''Possibility 2''' - via the DEBUG-interface and the software PROTOCOL DEVELOPER: (applies to ALL UNIGATE IC & CL as well as UNIGATE SC with option "DB") In this case the device's DEBUG-interface has to be connected with a PC COM-Port. In the software PROTOCOL DEVELOPER and belated power up of the device (NOT in the configuration mode) the message "Device started in Debug mode" appears in the bottom left corner. Now the download can be started with "DEBUG".<br />
<br />
===How to set the UNIGATE into the configuration mode (Configmode)?===<br />
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.<br />
For the UNIGATE CL the RS232 interface is automatically active throught the switch positions of S4+S5 with "FF".<br />
If you use the UNIGATE IC the basis board of the J17.<br />
<br />
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):<br />
<br />
''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''<br />
Configmode...<br />
<br />
Now you know that the unit is in configuration mode.<br />
<br />
'''Practice Tip:''' With UNIGATE CL, RS and SC the configuration mode is visually indicated by the RS-"State" LED flashing red.<br />
<br />
=== What is to consider when switching to UNIGATE CL from UNIGATE SC? ===<br />
There is one significant difference between an UNIGATE SC and an UNIGATE CL: the UNIGATE SC devices have a hardware switch "232 &harr; 485", which does not exist on an UNIGATE CL. The UNIGATE 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 <br />
<source lang="delphi"> Set(RS_Type,[?]) </source> <br />
command.<br />
In the PROFIBUS version there is also the difference of the ID number. The UNIGATE CL-DP needs the GSD file UGIC3218.gsd.<br />
<br />
=== Does the UNIGATE IC support SPI?===<br />
Yes, the UNIGATE IC supports SPI. (Up-to-date [http://www.deutschmann.de/de/produkte/download.php?file_id=412 UNIGATE IC Pinout-List] in XLS Format)<br />
Pin 3...7 are for the SPI Master (SPI slave on request only)<br />
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.<br />
<br />
===How to connect two networks (PROFIBUS / PROFINET)?===<br />
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.<br />
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.<br />
<br />
===Fieldbus===<br />
====CANopen====<br />
=====UNIGATE CO (M)-PROFIBUS DP===== <br />
=====I encountered problems after downloading the existing/old GWC-file into my new device. Can you list the various steps?=====<br />
#Open the desired GWC file with the configuration tool WINGATE. <br />
#Then start the new device and perform the download<br />
#Now perform an Upload from the device<br />
#The parameter "CAN baud rate" is now at 125k. <br />
#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.<br />
#Afterwards perform another download<br />
#Save the change, respectively the "new" GWC file<br />
<br />
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.<br />
<br />
=====How to replace CANopen (Master) - PROFIBUS DP (Slave)?=====<br />
#Start WINGATE:<br />
#Connect the RS232 from PC to UNIGATE (3 wire, 3 pin connector)<br />
#Connect power supply<br />
#Upload file<br />
#Save file<br />
#Disconnect the old UNIGATE <br />
#Connect the new UNIGATE (see Step 1)<br />
#Afterwards click "File - Download" (write to device)<br />
<br />
<br />
<gallery><br />
Datei:Start WINGATE V2.65(379).png|1. Start WINGATE<br />
Datei:WINGATE_V2.64(379)_Versorgungsanschluss.png|3. Connect power supply<br />
Datei:WINGATE_V2.65(379)_File_upload.png|4. File upload<br />
Datei:WINGATE_Save_as.png|4. Save as<br />
Datei:WINGATE_V2.65(379)_File_download_screen.png|8. File-Download<br />
</gallery><br />
<br />
=====In WINGATE-File the Adresse 0x14 is set to 0=====<br />
With the new Firmware V2.60 in WINGATE the config file has to be stored with the setting "baud rate: DIP Switch"<br />
<br />
====DeviceNet====<br />
=====How much power does the UNIGATE IC draw at the DeviceNet power supply 24 Volt connector, PIN 17?=====<br />
The current consumption is max. 35mA.<br />
<br />
====EtherNet/IP====<br />
=====How to switch to EtherNet/IP 2Port?=====<br />
You can find more about switching to EtherNet/IP 2 Port on the UNIGATE CL EtherNet/IP site: [[UNIGATE_EtherNet/IP/en|Changeover to 2-Port devices]]<br />
<br />
=====My PLC cannot establish a connection to my EtherNet/IP device. What could be the reason?=====<br />
Maybe you configured your PLC to use a Unicast connection.<br />
<br />
If you are using the Rockwell software RSLogix 5000 you can check this in the UNIGATE's module properties dialogue. Please make sure the option "Use Unicast Connection over EtherNet/IP" on the connection tab is disabled.<br />
<br />
===== Why does the function <code>ReadNewObjectDataEIP</code> show a change of input data, altough all of the data is identical? =====<br />
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.<br />
<br />
===== Can I only transfer an even number of bytes with an EtherNet/IP device? =====<br />
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).<br />
<br />
=====Can a power supply separation be avoided through a script adaptation in a UNIGATE EtherNet/IP with firmware 4.0?=====<br />
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).<br />
<br />
====Fast Ethernet====<br />
=====Is there an example of the web server functionality ?=====<br />
Yes, there is an example, which is available after installing the PROTOCOL DEVELOPER.<br />
# Start the UNIGATE CL-FE in configmode<br />
# Reset device (WINGATE - options - reset device)<br />
# Save the script example: Wingate – File – Write script ... :\Software\ProtocolDeveloper\Example\08 Bus specific\Fast Ethernet script.dcs<br />
# Set the IP address and the subnet mask (Do not forget to download the file)<br />
# Start the UNIGATE in Run mode (S4+5 not FF and not EE)<br />
# Start a FTP Client, such as [http://www.ghisler.com/index.htm Total Commander]. Establish a FTP connection. (Username and password: deutschmann)<br />
# Directory: Flash<br />
# Copy "index.html" to CL-FE<br />
# Start your browser and enter the IP address you created in WINGATE<br />
# If you refresh your browser (F5) you will see that the numerical value increased<br />
# That's it!<br />
<br />
<gallery><br />
Datei:WINGATE V2.72(385) Set IP Adress set subnet mask.png|4. IP address and subnet mask<br />
Datei:FTP TotalCommander Connection details.png|6. FTP Client<br />
Datei:FTP TotalCommander Verzeichnis flash.png|7. Change directory<br />
Datei:FTP TotalCommander Copy index.png|8. Copy index.html <br />
Datei:WINGATE FTP Browser.png|9. IP address in Browser<br />
</gallery><br />
<br />
=====Is the temperature range down to -40°C by now available for CL devices with RJ45 connectors?=====<br />
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.<br />
In our expansion card for CL and FC a RJ45 for -40°C is used.<br />
<br />
====PROFIBUS====<br />
=====At commissioning a PROFIBUS-slave I do not see any input data when put and also it is not possible to send data to the device.=====<br />
For CPUs from the company Siemens only direct access up to 4 bytes is possible. Provided that useful data > 4 bytes are supposed to be read or written, then the access has to be made through the SFC14 (read) and SFC15 (write). Further information can be found in the projection software's help.<br />
<br />
=====How to use the UNIGATE IC PROFIBUS DPV1 5V without driver 485 and how much current can the DC/DC converter provide on the fieldbus side?=====<br />
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.<br />
<br />
=====Changing of the Slave ID via SPS=====<br />
ID is stored in EEROM.<br />
<source lang="delphi"><br />
var LBusState : Long ;<br />
var L0xE0 : Long ; moveconst ( L0xE0, 0xE0);<br />
<br />
BusStart ;<br />
//Wait ( Bus_Active ) ;<br />
<br />
:LoopBusState;<br />
Get ( ReadBusState , LBusState ) ;<br />
if LBusState less L0xE0 then :LoopBusState; //!!! neu<br />
</source><br />
<br />
=====Which GSD-file is meant for my device?=====<br />
We distinguish between 2 versions: DPV0 and DPV1. You can tell from the article description which device is in front of you. A »DP« stands for DPV0; a »DPV1« for itself. The UNIGATE IC-DPL and UNIGATE CL is a DPV1-device.<br />
<br />
In the download-area of the respective device only that GSD-file, which is valid for the corresponding device only, is placed at your disposal for download.<br />
<br />
A DPV1 slave is downwards compatible and it can also operate in the DPV0 mode. Nevertheless, the DPV1 GSD-file has to be used.<br />
<br />
DPV0 slave &rarr; GSDfile »DAGW2079.GSD«<br />
<br />
DPV1 slave &rarr; GSD-file »UGIC3218.GSD«<br />
<br />
=====GSD Datei - How to create a different configuration?=====<br />
[[Datei:PB_GSD_Configuration_telegramm_8_Word_Out.jpg|thumb|Create a configuration]]<br />
<br />
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.<br />
In this Modul, you can setup every size.<br />
<br />
=====How to set the Slave ID via the Master?=====<br />
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.<br />
<br />
WARNING: With it the EEROM will be re-initialized and the script will be deleted.<br />
<br />
=====How to realize the conversion from Fieldbus &harr; Modbus RTU (Master)?=====<br />
''This proceeding for a UNIGATE CL-PROFIBUS DPV1 is used as an example for all UNIGATEs and the supported Fieldbuses.''<br />
<br />
UNIGATE CL is supplied with a Universal Script that makes setting the "Modbus RTU (Master)" protocol very simple. A detailed description how to configure the device can be found here.<br />
<br />
Note: In case you want to read out the same register several times, then the parameter ''"Data Exchange"'' should be adjusted to ''"On Trigger"''. In this case the UNIGATE expects the togglebyte in the Fieldbus Master's first byte.<br />
<br />
Application:<br />
<br />
The Fieldbus Master requests (read holding register = 03) the register "4567" with the length of 1 word from the Modbus Slave with the ID=2. The resulting inquiry from the Profibus-Master to the UNIGATE is:<br />
<br />
02 03 45 67 00 01<br />
<br />
(ID=2, read register=03, register=4567 and length in words high + low=0001) <br />
<br />
The UNIGATE converts data to Modbus and adds the checksum (=xx):<br />
<br />
02 03 4567 00 01 xx<br />
<br />
The UNIGATE receives the following response from the Modbus Slave with the ID=2:<br />
<br />
02 03 02 03 E8 xx<br />
<br />
(ID=2, read register=03, length in byte =02, value of the register 4567=03E8 and checksum=xx)<br />
<br />
The UNIGATE puts the Modbusslave's response on the Fieldbus:<br />
<br />
02 03 02 03 E8<br />
<br />
Consequently a complete inquiry from the Fieldbus Masters has been converted to Modbus and the Slave's response has been issued to the Fieldbus in turn.<br />
<br />
The above proceeding describes the function of the UNIGATE RS, UNIGATE CL with Universal Script and configured Modbus-RTU(Master) protocol as well as our Script examples Modbus-RTU(Master).<br />
<br />
There are also applications, in which the UNIGATE is supposed to read out a corresponding register or also the UNIGATE cyclically reads the same regsiter again and again through only 1 byte of the Fieldbus Master. With our UNIGATE SC, CL and IC this is possible without a problem. In these two cases the Script only has to be adapted to this requirement. Please use our Script examples for this.<br />
<br />
====PROFINET====<br />
=====How to connect Deutschmann PROFINET devices to a S7?=====<br />
For a step-by-step instruction, please download the PDF [http://deutschmann.de/produkte/download.php?file_id=681].<br />
<br />
=====How to evaluate a UNIGATE device with a PROFINET interface?=====<br />
You can evaluate your PROFINET device (UNIGATE CL-Profinet, UNIGATE IC-Profinet, UNIGATE FC-Profinet) with our free PROFINET Module software. All you need is a Microsoft Windows computer with an Ethernet port. The PROFINET Module software is part of our Starter Kit software collection which can be obtained from the download section.<br />
<br />
=====Why can't I assign a device name to my UNIGATE?=====<br />
For PROFINET the device name is subject to a [[PROFINET_Device_name_(English)|naming convention]]. For example, the use of capital letters is not allowed.<br />
<br />
=====How to rename the GSDML file?=====<br />
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.<br />
<br />
=====Script with station name=====<br />
[[Datei:PN_Script_mit_Stationsname_Set_device.png|thumb|Script with station name]]<br />
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.<br />
If a name is then set in the PROFINET Master it is effective from now on.<br />
<br />
===Series===<br />
====UNIGATE CL====<br />
=====Can I use my configuration file of the series UNIGATE RS for UNIGATE CL as well?=====<br />
We will be supplying the devices UNIGATE CL with a "UNIVERSAL" script (if it had not been handled that way so far). This script then acts as if it was a UNIGATE RS. That means that the UNIGATE CL can be parameterized via the configuration software WINGATE. An "old" UNIGATE RS configuration file is not compatible with that of the UNIGATE CL. If a UNIGATE RS is to be changed over to UNIGATE CL, then the UNIGATE CL must be read out once via WINGATE and the protocol settings have to be made. This configuration can then be stored in the usual manner and it can be used again for devices of the same type.<br />
<br />
Note: If a "Reset Device" is carried out with a UNIGATE CL, then the "UNIVERSAL" script gets lost and it has to be loaded again.<br />
<br />
=====I want to download my UNIGATE SC-PB Script into the UNIGATE CL-PB. The PROFIBUS State LED remains red and/or the serial communication does not work.=====<br />
This "phenomenon" has two reasons:<br />
<br />
# The UNIGATE SC-PB requires the GSD-file "DAGW2079.gsd" and the UNIGATE CL-PB requires the GSD-file "UGIC3218.gsd".<br />
# The interface of the UNIGATE SC-PB is set via the switch "Interface" and at the UNIGATE CL-PB it is set in the Script.<br />
<br />
Remedy:<br />
1. Either the GSD-file for the UNIGATE CL-PB in the PROFIBUS Master in the hardware configuration is changed to "UGIC3218.gsd" or the Ident number has to be changed to "2079" in the Script through the command:<br />
Set ( IdentNumber , 0x2079 ) ; //default: 0x3218<br />
<br />
After the Script download the UNIGATE CL-PB acts like a UNIGATE SC-PB at the PROFIBUS.<br />
<br />
2. The interfaces of the UNIGATE CL-PB have to be defined in the Script by means of the Script command:<br />
Set ( RS_Type , RS232 ) ; //or RS485 or RS422<br />
<br />
=====How to configure the UNIGATE CL with WINGATE?=====<br />
Note: This instruction refers to the configuration of UNIGATE CL in connection with the Universal Script.<br />
<br />
The current version of the software WINGATE has to be installed on the PC in order to be able to configure the UNIGATE CL.<br />
<br />
Subsequently the UNIGATE CL has to be connected to the PC via the application interface X1. The required wiring can be found here.<br />
<br />
<br />
The "Universalscript Deutschmann" has to be available in the device, so that it can be configured by WINGATE. When the software WINGATE is executed and the UNIGATE is restarted then you receive the following actuation message from the UNIGATE in the lower part of WINGATE (example: V3553 UNIGATE CL-ProfibusDP):<br />
<br />
RS-PBV1-CL (232/422/485) V7.31[30] (c)dA Switch=0x01FF Script(16k)="Universalscript Deutschmann" Author="G/S" Version="V 0.2d" Date 24.07.2008 SN: 3553xxxx ID=1<br />
Konfigmode...<br />
<br />
IMPORTANT: ALL following points cannot be carried out unless you receive this message (with or without "Universalscript Deutschmann")!<br />
<br />
In case the Script is not in the device, it can be loaded into the UNIGATE with the function File -> ''Write Script'' (the Script can be found on the Support CD at: \Software\ProtocolDeveloper\Example\Universal\CL_Universal.dcs or on our website in category "Software").<br />
<br />
Now the UNIGATE CL can be read-out through ''File &rarr; Upload''. Both options ''more items visible & more items editable'' have to be acivated in order to be able to set all functions.<br />
<br />
The configuration itself should be made from the top to the bottom. The desired parameters can be moved to the corresponding line with double-click.<br />
<br />
When the configuration is completed the altered values have to written into the device with ''File &rarr; Download''. This is confirmed by the UNIGATE with:<br />
<br />
Download ok<br />
<br />
Store data... ...<br />
<br />
Restart<br />
<br />
RS-PBV1-CL (232/422/485) V7.31[30] (c)dA Switch=0x01FF Script(16k)="Universalscript Deutschmann" Author="G/S" Version="V 0.2d" Date 24.07.2008 SN: 3553xxxx ID=1<br />
Konfigmode...<br />
<br />
With it the configuration is finished. Now the device has to be switched to 'voltageless' and the rotary switch at the device has to be adjusted accordingly and connected to the application. Now the device can be put into operation.<br />
<br />
=====Can you deliver the Protocol Converter UNIGATE CL in a lacquered version?=====<br />
The lacquering of this series does not make sense, since the mechanical oponents such as rotary coding switches, plug connectors, etc. can not be lacquered and thus a disruption would occur.<br />
<br />
====UNIGATE IC====<br />
=====Problem with the virtual COM-ports via USB=====<br />
If the Developerboard UNIGATE IC-AB is connected via the USB-interface, then the following procedure has to be taken into account:<br />
<br />
# Adjust all switches, rotary switches and jumpers in accordance to the UNIGATE IC that is to be used.<br />
# Connect the Developerboard UNIGATE IC-AB through the USB-cable to the PC/laptop and supply the Developerboard UNIGATE IC-AB with voltage through the provided power supply.<br />
# Put the UNIGATE IC on the socket of the Developerboard UNIGATE IC-AB and set the switch ''POWER'' to position ON afterwards. Only now the operating system of the PC recognizes the new virtual interfaces and during initial startup the drivers are installed.<br />
# Execute the corresponding software application now and select the (new) interface in ''Options''.<br />
# Please push the button ''Reset''. The device responds now (provided that the switch ''Mode is set to Config'') with the startup message or the Script is being executed (switch ''Mode on Run'' and the software ''PROTOCOL DEVELOPER'' is not initiated) or the device starts in the DebugMode (if the switch ''Mode is set to Run'' and the software ''PROTOCOL DEVELOPER'' is being executed).<br />
<br />
Therefore the switch ''POWER'' should not be changed any more since the virtual COM-ports will be re-initialized again with any change from ''ON&rarr;OFF&rarr;ON''.<br />
<br />
=====Is it possible to lacquer the series UNIGATE IC?=====<br />
There is no reason why the series UNIGATE IC cannot be lacquered. However, the complete assembly (the whole customer's device) should be lacquered in one piece. To lacquer the UNIGATE IC first would involve a disproportionate high effort, which would lead to high costs (e. g. The software would have to be downloaded before, tapeing of the pins and so on). Therefore we are not supplying the UNIGATE IC-series in lacquered form.<br />
<br />
====UNIGATE RS====<br />
The lacquering of this series does not make sense, since the mechanical oponents such as rotary coding switches, plug connectors, etc. can not be lacquered and thus a disruption would occur. We offer die-cast aluminium housing for these applications.<br />
<br />
===PROTOCOL DEVELOPER===<br />
====The PROTOCOL DEVELOPERs help window is empty. What can I do?====<br />
By default the help-file has to be existent on a local drive (e. g. C:\)<br />
<br />
In order to be able to also access the help-file from a network drive the following lines have to be entered into Notepad and saved as "*.REG" file:REGEDIT4 <br />
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp] <br />
<br />
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp\1.x\HHRestrictions] <br />
<br />
"MaxAllowedZone"=dword:00000001 "EnableFrameNavigationInSafeMode"=dword:00000001 <br />
<br />
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp\1.x\ItssRestrictions] <br />
<br />
"MaxAllowedZone"=dword:00000001When the file has been generated it is executed with a double click. The PC has to be restarted, so that the changes will be accepted.<br />
<br />
For further information as well as possible risks please log on to: http://support.microsoft.com/kb/896358/de<br />
<br />
<br />
''Microsoft Windows Vista:''<br />
<br />
By default the access to "*.CHM"-files is denied. In order to make an access possible though, click with the right button on the the file properties under General on Unblock. The help file opens now.<br />
<br />
===WINGATE===</div>Reithhttps://wiki.deutschmann.de/index.php?title=en:Frequently_asked_questions_Fieldbus-_and_Industrial-Ethernet-Devices&diff=3453en:Frequently asked questions Fieldbus- and Industrial-Ethernet-Devices2019-08-27T14:10:01Z<p>Reith: /* How to reset a LOCON 90, LOCON 100, LOCON 100-PB, LOCON 200, LOCON 200-PB, ROTARNOCK 100 or ROTARNOCK 100-PB back to delivery condition (reset)? */</p>
<hr />
<div>== Electronic Cam Controls ==<br />
===Are there replacements for a product that is no longer available? (LOCON 32-HC, LOCON 32-PM)...===<br />
1. Substitution option with [[LOCON 24 (English)|LOCON 24]]:<br />
<br />
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.<br />
<br />
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.<br />
<br />
2. Substitution option with [[LOCON 100 (English)|LOCON 100]] / [[LOCON 200 (English)|LOCON 200]]:<br />
<br />
Basically the following points ALWAYS have to be clarified in case of replacing a product that is no longer available: (Example in italic)<br />
* Which encoder is used in connection with the cam control (NSW) (maximum of 16 inputs) &rarr; number of encoder inputs &rarr; at INC. at least 2, at absolute &rarr; number of tracks = number inputs)<br />
<br />
''A TA58-O360-GYE is used &rarr; 9 tracks = 9 inputs''<br />
<br />
* What other pins are used? (e. g. at INC. encoders Clear + and/or Clear- &rarr; number of inputs +1 or +2)<br />
<br />
''None &rarr; + 0 inputs''<br />
<br />
* Is the Prog.Enable wired? (if yes &rarr; number of inputs +1)<br />
<br />
''Yes. &rarr; +1 input''<br />
<br />
* Is the external program selection wired? If yes, how many programs? (number of inputs +2 ... +7)<br />
<br />
''Yes, up to program 8. 5 pins are required for it &rarr; +5 inputs''<br />
<br />
According to the amount here the decision is made, whether [[LOCON 100 (English)|LOCON 100]] or [[LOCON 200 (English)|LOCON 200]] can be used. Provided that the amount remains below 16, either a [[LOCON 100 (English)|LOCON 100]] or a [[LOCON 200 (English)|LOCON 200]] can be used. If the amount of required inputs exceeds 16, then a [[LOCON 100 (English)|LOCON 100]] 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 [[LOCON 100 (English)|LOCON 100]] or [[LOCON 200 (English)|LOCON 200]] can be used. <br />
<br />
Quantity determination of expansion modules that have to be used (LOCON 100-A32 or LOCON 200-IO8):<br />
<br />
* Is the RunControl-relay wired? If yes &rarr; number of outputs + 1<br />
<br />
''Yes. + 1 output for RunControl''<br />
<br />
* How many outputs are used at the cam control? &rarr; Number of the basis' remaining outputs (LOCON 100 + LOCON 200) = 16 - number of inputs<br />
<br />
''32 outputs are used. &rarr; Total = 1 + 32 = 33 outputs. Either LOCON 100 (1 output) with an LOCON 100-A32 extension (=32 outputs) OR LOCON 200 (1 output) + 3 x LOCON 200-IO8 (8 outputs each = 32 outputs) can be used here.''<br />
<br />
Basically the version LOCON 200 + LOCON 200-IO8 is to be favored, since the cycle times for this constellation are lower than those for LOCON 100.<br />
<br />
On principle it does not matter which TERM is used. [[LOCON 100 (English)|LOCON 100]] & [[LOCON 200 (English)|LOCON 200]] are supported by TERM 6, TERM 24 & TERM 32 to a partially limited extent. For that reason the parameterization and configuration should principally always be carried out with [[WINLOC 32 (English)|WINLOC 32]] and the mentioned TERMs should be used for operation.<br />
<br />
===How to connect a LOCON with the RS232-interface (COM port) at the PC?===<br />
At the PC COM port there is a 9-pole D-SUB pin connection with the following assignment:<br />
<br />
PIN 2 - Rx (from the PC's point of view)<br />
<br />
PIN 3 - Tx (from the PC's point of view)<br />
<br />
PIN 5 - GND<br />
<br />
Example:<br />
<br />
At the LOCON16/17 the assignment of the X2 is as follows:<br />
<br />
PIN 26 - GND<br />
<br />
PIN 27 - Rx 232 (from the LOCON's point of view)<br />
<br />
PIN 28 - Tx 232 (from the LOCON's point of view)<br />
<br />
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.<br />
<br />
For the above example it comes to the following cable assignment:<br />
<br />
LOCON X2 PIN26 &harr; PC PIN5<br />
<br />
LOCON X2 PIN27 &harr; PC PIN3<br />
<br />
LOCON X2 PIN28 &harr; PC PIN2<br />
<br />
Note:<br />
Possible existing blue bridges between the signals "DICNET-/Rx" &harr; "R-" and "DICNET+/Tx" &harr; "R+" have to be removed.<br />
<br />
===How to reset LOCON 90, LOCON 100, LOCON 100-PB, LOCON 200, LOCON 200-PB, ROTARNOCK 100 or ROTARNOCK 100-PB back to delivery condition (reset)?===<br />
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 WINLOC 32 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 LOCON 100 with an expansion LOCON 100-A32 with DICNET communication, configured as Timer with a counting range of 16):<br />
<br />
''L100-48(48)-T16-485(DICNET) V3.4''<br />
<br />
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: <br />
''Reset configuration to defaultvalue and clear all programmed data (Y/N)? N''<br />
<br />
This query has to be confirmed with "y" within 3 seconds and another safety query follows:<br />
<br />
''Cancel operation (Y/N) N'' which is to be confirmed with "n".<br />
<br />
If the entry is correct, the following message appears in the terminal window:<br />
<div style="border: 1px solid #136db9; background-color: #fafafa; padding: 8px;"><br />
''Clear EEROM 0H-1fffH ...............................<br />
<br />
Restart<br />
<br />
L100-48(48)-S4096-485(DICNET) V3.4 ok<br />
<br />
(Error: 108)''<br />
</div><br />
With it the device was set back to the condition it was originally supplied.<br />
<br />
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.<br />
Note: After a reset the optional LOGIC-function has to be activated again. At the devices LOCON 100 & LOCON 200 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.<br />
<br />
===How to activate the logic function of LOCON 100-PB, LOCON 200, LOCON 200-PB, ROTARNOCK 100 or ROTARNOCK 100-PB?===<br />
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 LOCON 100-PB, LOCON 200 or LOCON 200-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.<br />
<br />
The device to be extended by the logic function must be connected to the PC and a start-up string has to be shown WINLOC 32.<br />
<br />
With a click on the menue ''Extras &rarr; Product Option Activation'' a window opens for activation.<br />
<br />
The DICNET-ID is entered in the line Device ID. For a connection through RS232 this value remains on "0".<br />
<br />
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 &harr; PC works).<br />
<br />
The release code is entered in the line ''Activation key''. Start behind the "-".<br />
Click on ''Run'' afterwards.<br />
<br />
(In case of an error "Returncode=4" is the result.)<br />
<br />
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:<br />
<br />
L200-16-S4096-H-''LG''-232 Vx.x<br />
<br />
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:<br />
<br />
Note: After a "Clear all" the logic function has to be released again.<br />
<br />
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 LOCON 100-PB; LOCON 200(-PB) & ROTARNOCK 100(-PB)".<br />
<br />
===External Wiring===<br />
====How is the modification from LOCON 32-HC or LOCON 32-PM to LOCON 24 carried out?====<br />
Introductorily we like to point out that this description refers to a LOCON 32-HC, that is/was configured "absolute parallel 360" as encoder type. Consequently the LOCON 24 also has to contain this "O360" in the article text.<br />
<br />
{| class="wikitable"<br />
!LOCON 24 !!Signal !!LOCON 32-HC !!LOCON 32-PM<br />
|-<br />
|X1 PIN 1 ||OUT 1 ||X10 PIN 2 ||X1 PIN 1<br />
|-<br />
|X1 PIN 2 ||OUT 2 ||X10 PIN 1 ||X1 PIN 2<br />
|-<br />
|X1 PIN 3 ||OUT 3 ||X10 PIN 4 ||X1 PIN 3<br />
|-<br />
|X1 PIN 4 ||OUT 4 ||X10 PIN 3 ||X1 PIN 4<br />
|-<br />
|X1 PIN 5 ||OUT 5 ||X10 PIN 6 ||X1 PIN 5<br />
|-<br />
|X1 PIN 6 ||OUT 6 ||X10 PIN 5 ||X1 PIN 6<br />
|-<br />
|X1 PIN 7 ||OUT 7 ||X10 PIN 8 ||X1 PIN 7<br />
|-<br />
|X1 PIN 8 ||OUT 8 ||X10 PIN 7 ||X1 PIN 8<br />
|-<br />
|X1 PIN 9 ||OUT 9 ||X10 PIN 10 ||X1 PIN 9<br />
|}<br />
<br />
... [http://www.deutschmann.de/en/support/faq_detail.html?question=18 more]<br />
<br />
=== Models ===<br />
==== What has to be considered when using a LOCON 200 in connection with TERM 24? ====<br />
If a (discontinued) device is supposed to be replaced by a LOCON 200 and in case a TERM 24 is used in the assembly, then the TERM 24's Firmware must be updated at any rate. For the update the device has to be sent back to us.<br />
<br />
==== TN65 - ROTARNOCK - what is it? ====<br />
It is the same unit. ROTARNOCK describes the product line and TN65 is the specific type or the article description.<br />
<br />
Example:<br />
ROTARNOCK 100 - describes the ROTARNOCK-family "100". The detailed article description is explained on the picture "Article description".<br />
<br />
[[Datei:Article description Rotarnock English.jpg|thumb|Article description]]<br />
<br />
<br />
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.<br />
<br />
==== How to change the Profibus Ident Number? ====<br />
To change the Profibus Ident Number from 3606H to 3231 the ROTARNOCK 100-PB has to be connected with the PC via a serial communication (RS232). For the serial communication the following pin assignemt is valid here:<br />
<br />
PC PIN2 (Rx) ↔ ROTARNOCK 25pin D-Sub PIN17 (Tx RED)<br /><br />
PC PIN3 (Tx) ↔ ROTARNOCK 25pin D-Sub PIN18 (Rx RED)<br /><br />
PC PIN5 (GND) ↔ ROTARNOCK 25pin D-Sub PIN25 (GND)<br />
<br />
A corresponding programming cable (including plug-in power supply) is to be ordered with the article number V3467. ( V3467 - Programming cable for ROTARNOCK - 232/PB).<br />
<br />
The software WINLOC 32 has to be installed on th PC. The interface parameters are entered in "Extras → Options → Port".<br />
<br />
If the ROTARNOCK is now supplied with voltage a window opens automatically and the device brings its start-up message, e. g.:<br />
'''R100-48-O4096-PB(126)-232 V3.54 Ok'''<br />
Now place in WINLOC 32 the cursor behind the last character (through a "left click") and press "n" while keeping the keys "STRG/CTRL" pressed.<br />
The following confirmation prompt appears:<br />
'''Ident-Nr=3606H, change to 3231H (Y/N)? N'''<br />
This query has to be confirmed with "'''y'''" within 3 seconds and the following confirmation appears:<br />
'''New Ident-Nr = 3231H'''<br />
After a re-start the device uses the new Ident Number and it can be put into operation.<br />
<br />
The same way the Ident Number can also be changed back from 3231H to 3606H.<br />
<br />
==== How to replace a ROTARNOCK 1/2/3/4 by a ROTARNOCK 100? ====<br />
There are two ways to carry out the exchange.<br />
<br />
'''1.'''<br />
Exchange with the convenient programming software for cam controls WINLOC 32 (recommended procedure):<br />
<br />
Read out (File&rarr;Upload) the ROTARNOCK that is to be replaced with the software WINLOC 32 and store (File&rarr;Save) it on the hard disk or open an existing configuration file.<br />
<br />
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:<br />
Encoder resolution, ITC (=idle time compensation) Type, Display factor, ITC Function, Turn Direction, Run-Control and Zero shift.<br />
<br />
Important: Please write down the indicated position during downtime (best in the basic position if possible) before removing the old device! <br />
<br />
Connect the ROTARNOCK 100 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 ROTARNOCK 100 back in default mode can be found here.<br />
<br />
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.<br />
<br />
Enter the value for the Virtual Resolution here and select the ITC Type and confirm it with OK. <br />
<br />
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!<br />
<br />
'''Important advice:'''<br />
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.<br />
<br />
We recommend to carry out the zero adjustment first before the cams are being transmitted to the device.<br />
Load the newly generated configuration in the ROTARNOCK 100 through Download. Install the ROTARNOCK 100 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.<br />
<br />
In WINLOC32 the cam values, idle times and output names are transmitted from the old configuration file to the new one through Extras &rarr; Data transfer. This function is only available in the Comfort version of WINLOC 32.<br />
<br />
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 [mailto:hotline@deutschmann.de hotline@deutschmann.de].<br />
<br />
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. <br />
<br />
'''2.'''<br />
Exchange with manual configuration and programming with TERM 6 or TERM 24 (with current Firmware):<br />
<br />
The following information on the ROTARNOCK that is to be exchanged should be available:<br />
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.<br />
<br />
Advice: In case your old device features the option R - RunControl, then the device has to be configured with WINLOC 32.<br />
<br />
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. <br />
<br />
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.<br />
<br />
Now you can start entering the cams and idle times and finally the application can be tested and be put into operation.<br />
<br />
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 WINLOC 32.<br />
<br />
===Software Tools===<br />
====Configuration- and programming-software for cam controls?====<br />
A configuration- and programming-software [[WINLOC 32 (English)|WINLOC 32]] is available for all Deutschmann cam controls (NS).<br />
<br />
The basic version of that software is available free of charge (in the download-area and on the support-DVD). This basic version already features extensive functions. The cam control can be read out, configured and programmed. Also these files can be stored. <br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
====How and where is to enter the WINLOC 32 comfort version license key?====<br />
First of all start WINLOC 32.<br />
<br />
In the menu line "Extras" &rarr; select "Options". A window opens. If necessary please change to the register "License".<br />
Now enter the license key you received from us.<br />
<br />
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 "*".<br />
<br />
A license that have been purchased once can be used for all follow-up versions. A WINLOC 6 license also works with WINLOC 32.<br />
<br />
== UNIGATE ==<br />
===How to carry out a Firmware update at UNIGATE?===<br />
You can find an explanation on the site [[Firmware-Aktualisierung/en|Firmware update]].<br />
<br />
===I encountered problems with the RS232 connection between UNIGATE and PC. What to do when WINGATE says "no Gateway found"?===<br />
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.<br />
<br />
===How to connect an UNIGATE with the RS232-interface (COM port) at the PC?===<br />
At the PC COM port there is a 9-pole D-SUB pin connection with the following assignment:<br />
<br />
PIN 2 - Rx (from the PC's point of view)<br />
<br />
PIN 3 - Tx (from the PC's point of view)<br />
<br />
PIN 5 - GND<br />
<br />
Example: At the UNIGATE CL the assignment of the X1 is as follows:<br />
<br />
PIN 1 - Rx 232 (from the UNIGATE's point of view)<br />
<br />
PIN 2 - Tx 232 (from the UNIGATE's point of view)<br />
<br />
PIN 3 - AP-GND<br />
<br />
Generally always the Rx of the PC has to be connected with the Tx of the UNIGATE and the Tx of the PC with the Rx of the UNIGATE. Also the GND always has to be connected.<br />
<br />
For the above example it comes to the following cable assignment:<br />
<br />
UNIGATE X1 PIN1 &harr; PC PIN3<br />
<br />
UNIGATE X1 PIN2 &harr; PC PIN2<br />
<br />
UNIGATE X1 PIN3 &harr; PC PIN5<br />
<br />
===Does UNIGATE have a "test mode"?===<br />
Yes, there is a test mode.<br />
<br />
The interface-switch has to be set to position »RS232« and the two rotary coding switches on the serial side (S4 + S5) have to be set to »EE« in order to put the device into the test mode.<br />
<br />
After the restart the UNIGATE sends a byte on the serial side from »0-F« every second (some devices will first do a 15 to 30 seconds lasting self test). On the Fieldbus this output occurs accordinglywith the length depending on the set bus width. If useful data is sent to the UNIGATE (serial and Fieldbus) they are sent back from the UNIGATE (ECHO).<br />
<br />
===How to get my script into the device?===<br />
'''Advice:''' Please always use the current version of the corresponding software.<br />
<br />
Basically there are two ways to load the script into the UNIGATE.<br />
<br />
'''Possibility 1''' - via the serial (application-) interface: (applies to ALL UNIGATE SC, IC & CL) The script has to be compiled in the PROTOCOL DEVELOPER by "File &rarr; save compiled file" (the script receives the file extension *.dcs), so that the script gets into the device this way. The device has to be set into the configuration mode in order to load the script into the device. The script download can be started with the software WINGATE through "File &rarr; Write Script". With the software SPT (ScriptProgramTool) the downlaod is initiated through "File &rarr; Open file and program".<br />
<br />
'''Possibility 2''' - via the DEBUG-interface and the software PROTOCOL DEVELOPER: (applies to ALL UNIGATE IC & CL as well as UNIGATE SC with option "DB") In this case the device's DEBUG-interface has to be connected with a PC COM-Port. In the software PROTOCOL DEVELOPER and belated power up of the device (NOT in the configuration mode) the message "Device started in Debug mode" appears in the bottom left corner. Now the download can be started with "DEBUG".<br />
<br />
===How to set the UNIGATE into the configuration mode (Configmode)?===<br />
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.<br />
For the UNIGATE CL the RS232 interface is automatically active throught the switch positions of S4+S5 with "FF".<br />
If you use the UNIGATE IC the basis board of the J17.<br />
<br />
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):<br />
<br />
''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''<br />
Configmode...<br />
<br />
Now you know that the unit is in configuration mode.<br />
<br />
'''Practice Tip:''' With UNIGATE CL, RS and SC the configuration mode is visually indicated by the RS-"State" LED flashing red.<br />
<br />
=== What is to consider when switching to UNIGATE CL from UNIGATE SC? ===<br />
There is one significant difference between an UNIGATE SC and an UNIGATE CL: the UNIGATE SC devices have a hardware switch "232 &harr; 485", which does not exist on an UNIGATE CL. The UNIGATE 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 <br />
<source lang="delphi"> Set(RS_Type,[?]) </source> <br />
command.<br />
In the PROFIBUS version there is also the difference of the ID number. The UNIGATE CL-DP needs the GSD file UGIC3218.gsd.<br />
<br />
=== Does the UNIGATE IC support SPI?===<br />
Yes, the UNIGATE IC supports SPI. (Up-to-date [http://www.deutschmann.de/de/produkte/download.php?file_id=412 UNIGATE IC Pinout-List] in XLS Format)<br />
Pin 3...7 are for the SPI Master (SPI slave on request only)<br />
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.<br />
<br />
===How to connect two networks (PROFIBUS / PROFINET)?===<br />
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.<br />
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.<br />
<br />
===Fieldbus===<br />
====CANopen====<br />
=====UNIGATE CO (M)-PROFIBUS DP===== <br />
=====I encountered problems after downloading the existing/old GWC-file into my new device. Can you list the various steps?=====<br />
#Open the desired GWC file with the configuration tool WINGATE. <br />
#Then start the new device and perform the download<br />
#Now perform an Upload from the device<br />
#The parameter "CAN baud rate" is now at 125k. <br />
#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.<br />
#Afterwards perform another download<br />
#Save the change, respectively the "new" GWC file<br />
<br />
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.<br />
<br />
=====How to replace CANopen (Master) - PROFIBUS DP (Slave)?=====<br />
#Start WINGATE:<br />
#Connect the RS232 from PC to UNIGATE (3 wire, 3 pin connector)<br />
#Connect power supply<br />
#Upload file<br />
#Save file<br />
#Disconnect the old UNIGATE <br />
#Connect the new UNIGATE (see Step 1)<br />
#Afterwards click "File - Download" (write to device)<br />
<br />
<br />
<gallery><br />
Datei:Start WINGATE V2.65(379).png|1. Start WINGATE<br />
Datei:WINGATE_V2.64(379)_Versorgungsanschluss.png|3. Connect power supply<br />
Datei:WINGATE_V2.65(379)_File_upload.png|4. File upload<br />
Datei:WINGATE_Save_as.png|4. Save as<br />
Datei:WINGATE_V2.65(379)_File_download_screen.png|8. File-Download<br />
</gallery><br />
<br />
=====In WINGATE-File the Adresse 0x14 is set to 0=====<br />
With the new Firmware V2.60 in WINGATE the config file has to be stored with the setting "baud rate: DIP Switch"<br />
<br />
====DeviceNet====<br />
=====How much power does the UNIGATE IC draw at the DeviceNet power supply 24 Volt connector, PIN 17?=====<br />
The current consumption is max. 35mA.<br />
<br />
====EtherNet/IP====<br />
=====How to switch to EtherNet/IP 2Port?=====<br />
You can find more about switching to EtherNet/IP 2 Port on the UNIGATE CL EtherNet/IP site: [[UNIGATE_EtherNet/IP/en|Changeover to 2-Port devices]]<br />
<br />
=====My PLC cannot establish a connection to my EtherNet/IP device. What could be the reason?=====<br />
Maybe you configured your PLC to use a Unicast connection.<br />
<br />
If you are using the Rockwell software RSLogix 5000 you can check this in the UNIGATE's module properties dialogue. Please make sure the option "Use Unicast Connection over EtherNet/IP" on the connection tab is disabled.<br />
<br />
===== Why does the function <code>ReadNewObjectDataEIP</code> show a change of input data, altough all of the data is identical? =====<br />
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.<br />
<br />
===== Can I only transfer an even number of bytes with an EtherNet/IP device? =====<br />
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).<br />
<br />
=====Can a power supply separation be avoided through a script adaptation in a UNIGATE EtherNet/IP with firmware 4.0?=====<br />
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).<br />
<br />
====Fast Ethernet====<br />
=====Is there an example of the web server functionality ?=====<br />
Yes, there is an example, which is available after installing the PROTOCOL DEVELOPER.<br />
# Start the UNIGATE CL-FE in configmode<br />
# Reset device (WINGATE - options - reset device)<br />
# Save the script example: Wingate – File – Write script ... :\Software\ProtocolDeveloper\Example\08 Bus specific\Fast Ethernet script.dcs<br />
# Set the IP address and the subnet mask (Do not forget to download the file)<br />
# Start the UNIGATE in Run mode (S4+5 not FF and not EE)<br />
# Start a FTP Client, such as [http://www.ghisler.com/index.htm Total Commander]. Establish a FTP connection. (Username and password: deutschmann)<br />
# Directory: Flash<br />
# Copy "index.html" to CL-FE<br />
# Start your browser and enter the IP address you created in WINGATE<br />
# If you refresh your browser (F5) you will see that the numerical value increased<br />
# That's it!<br />
<br />
<gallery><br />
Datei:WINGATE V2.72(385) Set IP Adress set subnet mask.png|4. IP address and subnet mask<br />
Datei:FTP TotalCommander Connection details.png|6. FTP Client<br />
Datei:FTP TotalCommander Verzeichnis flash.png|7. Change directory<br />
Datei:FTP TotalCommander Copy index.png|8. Copy index.html <br />
Datei:WINGATE FTP Browser.png|9. IP address in Browser<br />
</gallery><br />
<br />
=====Is the temperature range down to -40°C by now available for CL devices with RJ45 connectors?=====<br />
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.<br />
In our expansion card for CL and FC a RJ45 for -40°C is used.<br />
<br />
====PROFIBUS====<br />
=====At commissioning a PROFIBUS-slave I do not see any input data when put and also it is not possible to send data to the device.=====<br />
For CPUs from the company Siemens only direct access up to 4 bytes is possible. Provided that useful data > 4 bytes are supposed to be read or written, then the access has to be made through the SFC14 (read) and SFC15 (write). Further information can be found in the projection software's help.<br />
<br />
=====How to use the UNIGATE IC PROFIBUS DPV1 5V without driver 485 and how much current can the DC/DC converter provide on the fieldbus side?=====<br />
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.<br />
<br />
=====Changing of the Slave ID via SPS=====<br />
ID is stored in EEROM.<br />
<source lang="delphi"><br />
var LBusState : Long ;<br />
var L0xE0 : Long ; moveconst ( L0xE0, 0xE0);<br />
<br />
BusStart ;<br />
//Wait ( Bus_Active ) ;<br />
<br />
:LoopBusState;<br />
Get ( ReadBusState , LBusState ) ;<br />
if LBusState less L0xE0 then :LoopBusState; //!!! neu<br />
</source><br />
<br />
=====Which GSD-file is meant for my device?=====<br />
We distinguish between 2 versions: DPV0 and DPV1. You can tell from the article description which device is in front of you. A »DP« stands for DPV0; a »DPV1« for itself. The UNIGATE IC-DPL and UNIGATE CL is a DPV1-device.<br />
<br />
In the download-area of the respective device only that GSD-file, which is valid for the corresponding device only, is placed at your disposal for download.<br />
<br />
A DPV1 slave is downwards compatible and it can also operate in the DPV0 mode. Nevertheless, the DPV1 GSD-file has to be used.<br />
<br />
DPV0 slave &rarr; GSDfile »DAGW2079.GSD«<br />
<br />
DPV1 slave &rarr; GSD-file »UGIC3218.GSD«<br />
<br />
=====GSD Datei - How to create a different configuration?=====<br />
[[Datei:PB_GSD_Configuration_telegramm_8_Word_Out.jpg|thumb|Create a configuration]]<br />
<br />
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.<br />
In this Modul, you can setup every size.<br />
<br />
=====How to set the Slave ID via the Master?=====<br />
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.<br />
<br />
WARNING: With it the EEROM will be re-initialized and the script will be deleted.<br />
<br />
=====How to realize the conversion from Fieldbus &harr; Modbus RTU (Master)?=====<br />
''This proceeding for a UNIGATE CL-PROFIBUS DPV1 is used as an example for all UNIGATEs and the supported Fieldbuses.''<br />
<br />
UNIGATE CL is supplied with a Universal Script that makes setting the "Modbus RTU (Master)" protocol very simple. A detailed description how to configure the device can be found here.<br />
<br />
Note: In case you want to read out the same register several times, then the parameter ''"Data Exchange"'' should be adjusted to ''"On Trigger"''. In this case the UNIGATE expects the togglebyte in the Fieldbus Master's first byte.<br />
<br />
Application:<br />
<br />
The Fieldbus Master requests (read holding register = 03) the register "4567" with the length of 1 word from the Modbus Slave with the ID=2. The resulting inquiry from the Profibus-Master to the UNIGATE is:<br />
<br />
02 03 45 67 00 01<br />
<br />
(ID=2, read register=03, register=4567 and length in words high + low=0001) <br />
<br />
The UNIGATE converts data to Modbus and adds the checksum (=xx):<br />
<br />
02 03 4567 00 01 xx<br />
<br />
The UNIGATE receives the following response from the Modbus Slave with the ID=2:<br />
<br />
02 03 02 03 E8 xx<br />
<br />
(ID=2, read register=03, length in byte =02, value of the register 4567=03E8 and checksum=xx)<br />
<br />
The UNIGATE puts the Modbusslave's response on the Fieldbus:<br />
<br />
02 03 02 03 E8<br />
<br />
Consequently a complete inquiry from the Fieldbus Masters has been converted to Modbus and the Slave's response has been issued to the Fieldbus in turn.<br />
<br />
The above proceeding describes the function of the UNIGATE RS, UNIGATE CL with Universal Script and configured Modbus-RTU(Master) protocol as well as our Script examples Modbus-RTU(Master).<br />
<br />
There are also applications, in which the UNIGATE is supposed to read out a corresponding register or also the UNIGATE cyclically reads the same regsiter again and again through only 1 byte of the Fieldbus Master. With our UNIGATE SC, CL and IC this is possible without a problem. In these two cases the Script only has to be adapted to this requirement. Please use our Script examples for this.<br />
<br />
====PROFINET====<br />
=====How to connect Deutschmann PROFINET devices to a S7?=====<br />
For a step-by-step instruction, please download the PDF [http://deutschmann.de/produkte/download.php?file_id=681].<br />
<br />
=====How to evaluate a UNIGATE device with a PROFINET interface?=====<br />
You can evaluate your PROFINET device (UNIGATE CL-Profinet, UNIGATE IC-Profinet, UNIGATE FC-Profinet) with our free PROFINET Module software. All you need is a Microsoft Windows computer with an Ethernet port. The PROFINET Module software is part of our Starter Kit software collection which can be obtained from the download section.<br />
<br />
=====Why can't I assign a device name to my UNIGATE?=====<br />
For PROFINET the device name is subject to a [[PROFINET_Device_name_(English)|naming convention]]. For example, the use of capital letters is not allowed.<br />
<br />
=====How to rename the GSDML file?=====<br />
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.<br />
<br />
=====Script with station name=====<br />
[[Datei:PN_Script_mit_Stationsname_Set_device.png|thumb|Script with station name]]<br />
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.<br />
If a name is then set in the PROFINET Master it is effective from now on.<br />
<br />
===Series===<br />
====UNIGATE CL====<br />
=====Can I use my configuration file of the series UNIGATE RS for UNIGATE CL as well?=====<br />
We will be supplying the devices UNIGATE CL with a "UNIVERSAL" script (if it had not been handled that way so far). This script then acts as if it was a UNIGATE RS. That means that the UNIGATE CL can be parameterized via the configuration software WINGATE. An "old" UNIGATE RS configuration file is not compatible with that of the UNIGATE CL. If a UNIGATE RS is to be changed over to UNIGATE CL, then the UNIGATE CL must be read out once via WINGATE and the protocol settings have to be made. This configuration can then be stored in the usual manner and it can be used again for devices of the same type.<br />
<br />
Note: If a "Reset Device" is carried out with a UNIGATE CL, then the "UNIVERSAL" script gets lost and it has to be loaded again.<br />
<br />
=====I want to download my UNIGATE SC-PB Script into the UNIGATE CL-PB. The PROFIBUS State LED remains red and/or the serial communication does not work.=====<br />
This "phenomenon" has two reasons:<br />
<br />
# The UNIGATE SC-PB requires the GSD-file "DAGW2079.gsd" and the UNIGATE CL-PB requires the GSD-file "UGIC3218.gsd".<br />
# The interface of the UNIGATE SC-PB is set via the switch "Interface" and at the UNIGATE CL-PB it is set in the Script.<br />
<br />
Remedy:<br />
1. Either the GSD-file for the UNIGATE CL-PB in the PROFIBUS Master in the hardware configuration is changed to "UGIC3218.gsd" or the Ident number has to be changed to "2079" in the Script through the command:<br />
Set ( IdentNumber , 0x2079 ) ; //default: 0x3218<br />
<br />
After the Script download the UNIGATE CL-PB acts like a UNIGATE SC-PB at the PROFIBUS.<br />
<br />
2. The interfaces of the UNIGATE CL-PB have to be defined in the Script by means of the Script command:<br />
Set ( RS_Type , RS232 ) ; //or RS485 or RS422<br />
<br />
=====How to configure the UNIGATE CL with WINGATE?=====<br />
Note: This instruction refers to the configuration of UNIGATE CL in connection with the Universal Script.<br />
<br />
The current version of the software WINGATE has to be installed on the PC in order to be able to configure the UNIGATE CL.<br />
<br />
Subsequently the UNIGATE CL has to be connected to the PC via the application interface X1. The required wiring can be found here.<br />
<br />
<br />
The "Universalscript Deutschmann" has to be available in the device, so that it can be configured by WINGATE. When the software WINGATE is executed and the UNIGATE is restarted then you receive the following actuation message from the UNIGATE in the lower part of WINGATE (example: V3553 UNIGATE CL-ProfibusDP):<br />
<br />
RS-PBV1-CL (232/422/485) V7.31[30] (c)dA Switch=0x01FF Script(16k)="Universalscript Deutschmann" Author="G/S" Version="V 0.2d" Date 24.07.2008 SN: 3553xxxx ID=1<br />
Konfigmode...<br />
<br />
IMPORTANT: ALL following points cannot be carried out unless you receive this message (with or without "Universalscript Deutschmann")!<br />
<br />
In case the Script is not in the device, it can be loaded into the UNIGATE with the function File -> ''Write Script'' (the Script can be found on the Support CD at: \Software\ProtocolDeveloper\Example\Universal\CL_Universal.dcs or on our website in category "Software").<br />
<br />
Now the UNIGATE CL can be read-out through ''File &rarr; Upload''. Both options ''more items visible & more items editable'' have to be acivated in order to be able to set all functions.<br />
<br />
The configuration itself should be made from the top to the bottom. The desired parameters can be moved to the corresponding line with double-click.<br />
<br />
When the configuration is completed the altered values have to written into the device with ''File &rarr; Download''. This is confirmed by the UNIGATE with:<br />
<br />
Download ok<br />
<br />
Store data... ...<br />
<br />
Restart<br />
<br />
RS-PBV1-CL (232/422/485) V7.31[30] (c)dA Switch=0x01FF Script(16k)="Universalscript Deutschmann" Author="G/S" Version="V 0.2d" Date 24.07.2008 SN: 3553xxxx ID=1<br />
Konfigmode...<br />
<br />
With it the configuration is finished. Now the device has to be switched to 'voltageless' and the rotary switch at the device has to be adjusted accordingly and connected to the application. Now the device can be put into operation.<br />
<br />
=====Can you deliver the Protocol Converter UNIGATE CL in a lacquered version?=====<br />
The lacquering of this series does not make sense, since the mechanical oponents such as rotary coding switches, plug connectors, etc. can not be lacquered and thus a disruption would occur.<br />
<br />
====UNIGATE IC====<br />
=====Problem with the virtual COM-ports via USB=====<br />
If the Developerboard UNIGATE IC-AB is connected via the USB-interface, then the following procedure has to be taken into account:<br />
<br />
# Adjust all switches, rotary switches and jumpers in accordance to the UNIGATE IC that is to be used.<br />
# Connect the Developerboard UNIGATE IC-AB through the USB-cable to the PC/laptop and supply the Developerboard UNIGATE IC-AB with voltage through the provided power supply.<br />
# Put the UNIGATE IC on the socket of the Developerboard UNIGATE IC-AB and set the switch ''POWER'' to position ON afterwards. Only now the operating system of the PC recognizes the new virtual interfaces and during initial startup the drivers are installed.<br />
# Execute the corresponding software application now and select the (new) interface in ''Options''.<br />
# Please push the button ''Reset''. The device responds now (provided that the switch ''Mode is set to Config'') with the startup message or the Script is being executed (switch ''Mode on Run'' and the software ''PROTOCOL DEVELOPER'' is not initiated) or the device starts in the DebugMode (if the switch ''Mode is set to Run'' and the software ''PROTOCOL DEVELOPER'' is being executed).<br />
<br />
Therefore the switch ''POWER'' should not be changed any more since the virtual COM-ports will be re-initialized again with any change from ''ON&rarr;OFF&rarr;ON''.<br />
<br />
=====Is it possible to lacquer the series UNIGATE IC?=====<br />
There is no reason why the series UNIGATE IC cannot be lacquered. However, the complete assembly (the whole customer's device) should be lacquered in one piece. To lacquer the UNIGATE IC first would involve a disproportionate high effort, which would lead to high costs (e. g. The software would have to be downloaded before, tapeing of the pins and so on). Therefore we are not supplying the UNIGATE IC-series in lacquered form.<br />
<br />
====UNIGATE RS====<br />
The lacquering of this series does not make sense, since the mechanical oponents such as rotary coding switches, plug connectors, etc. can not be lacquered and thus a disruption would occur. We offer die-cast aluminium housing for these applications.<br />
<br />
===PROTOCOL DEVELOPER===<br />
====The PROTOCOL DEVELOPERs help window is empty. What can I do?====<br />
By default the help-file has to be existent on a local drive (e. g. C:\)<br />
<br />
In order to be able to also access the help-file from a network drive the following lines have to be entered into Notepad and saved as "*.REG" file:REGEDIT4 <br />
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp] <br />
<br />
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp\1.x\HHRestrictions] <br />
<br />
"MaxAllowedZone"=dword:00000001 "EnableFrameNavigationInSafeMode"=dword:00000001 <br />
<br />
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp\1.x\ItssRestrictions] <br />
<br />
"MaxAllowedZone"=dword:00000001When the file has been generated it is executed with a double click. The PC has to be restarted, so that the changes will be accepted.<br />
<br />
For further information as well as possible risks please log on to: http://support.microsoft.com/kb/896358/de<br />
<br />
<br />
''Microsoft Windows Vista:''<br />
<br />
By default the access to "*.CHM"-files is denied. In order to make an access possible though, click with the right button on the the file properties under General on Unblock. The help file opens now.<br />
<br />
===WINGATE===</div>Reithhttps://wiki.deutschmann.de/index.php?title=en:Frequently_asked_questions_Fieldbus-_and_Industrial-Ethernet-Devices&diff=3452en:Frequently asked questions Fieldbus- and Industrial-Ethernet-Devices2019-08-27T13:20:59Z<p>Reith: /* Are there replacements for a product that is no longer available? (LOCON 32-HC, LOCON 32-PM)... */</p>
<hr />
<div>== Electronic Cam Controls ==<br />
===Are there replacements for a product that is no longer available? (LOCON 32-HC, LOCON 32-PM)...===<br />
1. Substitution option with [[LOCON 24 (English)|LOCON 24]]:<br />
<br />
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.<br />
<br />
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.<br />
<br />
2. Substitution option with [[LOCON 100 (English)|LOCON 100]] / [[LOCON 200 (English)|LOCON 200]]:<br />
<br />
Basically the following points ALWAYS have to be clarified in case of replacing a product that is no longer available: (Example in italic)<br />
* Which encoder is used in connection with the cam control (NSW) (maximum of 16 inputs) &rarr; number of encoder inputs &rarr; at INC. at least 2, at absolute &rarr; number of tracks = number inputs)<br />
<br />
''A TA58-O360-GYE is used &rarr; 9 tracks = 9 inputs''<br />
<br />
* What other pins are used? (e. g. at INC. encoders Clear + and/or Clear- &rarr; number of inputs +1 or +2)<br />
<br />
''None &rarr; + 0 inputs''<br />
<br />
* Is the Prog.Enable wired? (if yes &rarr; number of inputs +1)<br />
<br />
''Yes. &rarr; +1 input''<br />
<br />
* Is the external program selection wired? If yes, how many programs? (number of inputs +2 ... +7)<br />
<br />
''Yes, up to program 8. 5 pins are required for it &rarr; +5 inputs''<br />
<br />
According to the amount here the decision is made, whether [[LOCON 100 (English)|LOCON 100]] or [[LOCON 200 (English)|LOCON 200]] can be used. Provided that the amount remains below 16, either a [[LOCON 100 (English)|LOCON 100]] or a [[LOCON 200 (English)|LOCON 200]] can be used. If the amount of required inputs exceeds 16, then a [[LOCON 100 (English)|LOCON 100]] 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 [[LOCON 100 (English)|LOCON 100]] or [[LOCON 200 (English)|LOCON 200]] can be used. <br />
<br />
Quantity determination of expansion modules that have to be used (LOCON 100-A32 or LOCON 200-IO8):<br />
<br />
* Is the RunControl-relay wired? If yes &rarr; number of outputs + 1<br />
<br />
''Yes. + 1 output for RunControl''<br />
<br />
* How many outputs are used at the cam control? &rarr; Number of the basis' remaining outputs (LOCON 100 + LOCON 200) = 16 - number of inputs<br />
<br />
''32 outputs are used. &rarr; Total = 1 + 32 = 33 outputs. Either LOCON 100 (1 output) with an LOCON 100-A32 extension (=32 outputs) OR LOCON 200 (1 output) + 3 x LOCON 200-IO8 (8 outputs each = 32 outputs) can be used here.''<br />
<br />
Basically the version LOCON 200 + LOCON 200-IO8 is to be favored, since the cycle times for this constellation are lower than those for LOCON 100.<br />
<br />
On principle it does not matter which TERM is used. [[LOCON 100 (English)|LOCON 100]] & [[LOCON 200 (English)|LOCON 200]] are supported by TERM 6, TERM 24 & TERM 32 to a partially limited extent. For that reason the parameterization and configuration should principally always be carried out with [[WINLOC 32 (English)|WINLOC 32]] and the mentioned TERMs should be used for operation.<br />
<br />
===How to connect a LOCON with the RS232-interface (COM port) at the PC?===<br />
At the PC COM port there is a 9-pole D-SUB pin connection with the following assignment:<br />
<br />
PIN 2 - Rx (from the PC's point of view)<br />
<br />
PIN 3 - Tx (from the PC's point of view)<br />
<br />
PIN 5 - GND<br />
<br />
Example:<br />
<br />
At the LOCON16/17 the assignment of the X2 is as follows:<br />
<br />
PIN 26 - GND<br />
<br />
PIN 27 - Rx 232 (from the LOCON's point of view)<br />
<br />
PIN 28 - Tx 232 (from the LOCON's point of view)<br />
<br />
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.<br />
<br />
For the above example it comes to the following cable assignment:<br />
<br />
LOCON X2 PIN26 &harr; PC PIN5<br />
<br />
LOCON X2 PIN27 &harr; PC PIN3<br />
<br />
LOCON X2 PIN28 &harr; PC PIN2<br />
<br />
Note:<br />
Possible existing blue bridges between the signals "DICNET-/Rx" &harr; "R-" and "DICNET+/Tx" &harr; "R+" have to be removed.<br />
<br />
===How to reset a LOCON 90, LOCON 100, LOCON 100-PB, LOCON 200, LOCON 200-PB, ROTARNOCK 100 or ROTARNOCK 100-PB back to delivery condition (reset)?===<br />
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 WINLOC 32 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 LOCON 100 with an expansion LOCON 100-A32 with DICNET communication, configured as Timer with a counting range of 16):<br />
<br />
''L100-48(48)-T16-485(DICNET) V3.4''<br />
<br />
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: <br />
''Reset configuration to defaultvalue and clear all programmed data (Y/N)? N''<br />
<br />
This query has to be confirmed with "y" within 3 seconds and another safety query follows:<br />
<br />
''Cancel operation (Y/N) N'' which is to be confirmed with "n".<br />
<br />
If the entry is correct, the following message appears in the terminal window:<br />
<div style="border: 1px solid #136db9; background-color: #fafafa; padding: 8px;"><br />
''Clear EEROM 0H-1fffH ...............................<br />
<br />
Restart<br />
<br />
L100-48(48)-S4096-485(DICNET) V3.4 ok<br />
<br />
(Error: 108)''<br />
</div><br />
With it the device was set back to the condition it was originally supplied.<br />
<br />
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.<br />
Note: After a reset the optional LOGIC-function has to be activated again. At the devices LOCON 100 & LOCON 200 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.<br />
<br />
===How to activate the logic function of LOCON 100-PB, LOCON 200, LOCON 200-PB, ROTARNOCK 100 or ROTARNOCK 100-PB?===<br />
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 LOCON 100-PB, LOCON 200 or LOCON 200-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.<br />
<br />
The device to be extended by the logic function must be connected to the PC and a start-up string has to be shown WINLOC 32.<br />
<br />
With a click on the menue ''Extras &rarr; Product Option Activation'' a window opens for activation.<br />
<br />
The DICNET-ID is entered in the line Device ID. For a connection through RS232 this value remains on "0".<br />
<br />
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 &harr; PC works).<br />
<br />
The release code is entered in the line ''Activation key''. Start behind the "-".<br />
Click on ''Run'' afterwards.<br />
<br />
(In case of an error "Returncode=4" is the result.)<br />
<br />
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:<br />
<br />
L200-16-S4096-H-''LG''-232 Vx.x<br />
<br />
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:<br />
<br />
Note: After a "Clear all" the logic function has to be released again.<br />
<br />
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 LOCON 100-PB; LOCON 200(-PB) & ROTARNOCK 100(-PB)".<br />
<br />
===External Wiring===<br />
====How is the modification from LOCON 32-HC or LOCON 32-PM to LOCON 24 carried out?====<br />
Introductorily we like to point out that this description refers to a LOCON 32-HC, that is/was configured "absolute parallel 360" as encoder type. Consequently the LOCON 24 also has to contain this "O360" in the article text.<br />
<br />
{| class="wikitable"<br />
!LOCON 24 !!Signal !!LOCON 32-HC !!LOCON 32-PM<br />
|-<br />
|X1 PIN 1 ||OUT 1 ||X10 PIN 2 ||X1 PIN 1<br />
|-<br />
|X1 PIN 2 ||OUT 2 ||X10 PIN 1 ||X1 PIN 2<br />
|-<br />
|X1 PIN 3 ||OUT 3 ||X10 PIN 4 ||X1 PIN 3<br />
|-<br />
|X1 PIN 4 ||OUT 4 ||X10 PIN 3 ||X1 PIN 4<br />
|-<br />
|X1 PIN 5 ||OUT 5 ||X10 PIN 6 ||X1 PIN 5<br />
|-<br />
|X1 PIN 6 ||OUT 6 ||X10 PIN 5 ||X1 PIN 6<br />
|-<br />
|X1 PIN 7 ||OUT 7 ||X10 PIN 8 ||X1 PIN 7<br />
|-<br />
|X1 PIN 8 ||OUT 8 ||X10 PIN 7 ||X1 PIN 8<br />
|-<br />
|X1 PIN 9 ||OUT 9 ||X10 PIN 10 ||X1 PIN 9<br />
|}<br />
<br />
... [http://www.deutschmann.de/en/support/faq_detail.html?question=18 more]<br />
<br />
=== Models ===<br />
==== What has to be considered when using a LOCON 200 in connection with TERM 24? ====<br />
If a (discontinued) device is supposed to be replaced by a LOCON 200 and in case a TERM 24 is used in the assembly, then the TERM 24's Firmware must be updated at any rate. For the update the device has to be sent back to us.<br />
<br />
==== TN65 - ROTARNOCK - what is it? ====<br />
It is the same unit. ROTARNOCK describes the product line and TN65 is the specific type or the article description.<br />
<br />
Example:<br />
ROTARNOCK 100 - describes the ROTARNOCK-family "100". The detailed article description is explained on the picture "Article description".<br />
<br />
[[Datei:Article description Rotarnock English.jpg|thumb|Article description]]<br />
<br />
<br />
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.<br />
<br />
==== How to change the Profibus Ident Number? ====<br />
To change the Profibus Ident Number from 3606H to 3231 the ROTARNOCK 100-PB has to be connected with the PC via a serial communication (RS232). For the serial communication the following pin assignemt is valid here:<br />
<br />
PC PIN2 (Rx) ↔ ROTARNOCK 25pin D-Sub PIN17 (Tx RED)<br /><br />
PC PIN3 (Tx) ↔ ROTARNOCK 25pin D-Sub PIN18 (Rx RED)<br /><br />
PC PIN5 (GND) ↔ ROTARNOCK 25pin D-Sub PIN25 (GND)<br />
<br />
A corresponding programming cable (including plug-in power supply) is to be ordered with the article number V3467. ( V3467 - Programming cable for ROTARNOCK - 232/PB).<br />
<br />
The software WINLOC 32 has to be installed on th PC. The interface parameters are entered in "Extras → Options → Port".<br />
<br />
If the ROTARNOCK is now supplied with voltage a window opens automatically and the device brings its start-up message, e. g.:<br />
'''R100-48-O4096-PB(126)-232 V3.54 Ok'''<br />
Now place in WINLOC 32 the cursor behind the last character (through a "left click") and press "n" while keeping the keys "STRG/CTRL" pressed.<br />
The following confirmation prompt appears:<br />
'''Ident-Nr=3606H, change to 3231H (Y/N)? N'''<br />
This query has to be confirmed with "'''y'''" within 3 seconds and the following confirmation appears:<br />
'''New Ident-Nr = 3231H'''<br />
After a re-start the device uses the new Ident Number and it can be put into operation.<br />
<br />
The same way the Ident Number can also be changed back from 3231H to 3606H.<br />
<br />
==== How to replace a ROTARNOCK 1/2/3/4 by a ROTARNOCK 100? ====<br />
There are two ways to carry out the exchange.<br />
<br />
'''1.'''<br />
Exchange with the convenient programming software for cam controls WINLOC 32 (recommended procedure):<br />
<br />
Read out (File&rarr;Upload) the ROTARNOCK that is to be replaced with the software WINLOC 32 and store (File&rarr;Save) it on the hard disk or open an existing configuration file.<br />
<br />
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:<br />
Encoder resolution, ITC (=idle time compensation) Type, Display factor, ITC Function, Turn Direction, Run-Control and Zero shift.<br />
<br />
Important: Please write down the indicated position during downtime (best in the basic position if possible) before removing the old device! <br />
<br />
Connect the ROTARNOCK 100 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 ROTARNOCK 100 back in default mode can be found here.<br />
<br />
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.<br />
<br />
Enter the value for the Virtual Resolution here and select the ITC Type and confirm it with OK. <br />
<br />
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!<br />
<br />
'''Important advice:'''<br />
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.<br />
<br />
We recommend to carry out the zero adjustment first before the cams are being transmitted to the device.<br />
Load the newly generated configuration in the ROTARNOCK 100 through Download. Install the ROTARNOCK 100 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.<br />
<br />
In WINLOC32 the cam values, idle times and output names are transmitted from the old configuration file to the new one through Extras &rarr; Data transfer. This function is only available in the Comfort version of WINLOC 32.<br />
<br />
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 [mailto:hotline@deutschmann.de hotline@deutschmann.de].<br />
<br />
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. <br />
<br />
'''2.'''<br />
Exchange with manual configuration and programming with TERM 6 or TERM 24 (with current Firmware):<br />
<br />
The following information on the ROTARNOCK that is to be exchanged should be available:<br />
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.<br />
<br />
Advice: In case your old device features the option R - RunControl, then the device has to be configured with WINLOC 32.<br />
<br />
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. <br />
<br />
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.<br />
<br />
Now you can start entering the cams and idle times and finally the application can be tested and be put into operation.<br />
<br />
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 WINLOC 32.<br />
<br />
===Software Tools===<br />
====Configuration- and programming-software for cam controls?====<br />
A configuration- and programming-software [[WINLOC 32 (English)|WINLOC 32]] is available for all Deutschmann cam controls (NS).<br />
<br />
The basic version of that software is available free of charge (in the download-area and on the support-DVD). This basic version already features extensive functions. The cam control can be read out, configured and programmed. Also these files can be stored. <br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
====How and where is to enter the WINLOC 32 comfort version license key?====<br />
First of all start WINLOC 32.<br />
<br />
In the menu line "Extras" &rarr; select "Options". A window opens. If necessary please change to the register "License".<br />
Now enter the license key you received from us.<br />
<br />
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 "*".<br />
<br />
A license that have been purchased once can be used for all follow-up versions. A WINLOC 6 license also works with WINLOC 32.<br />
<br />
== UNIGATE ==<br />
===How to carry out a Firmware update at UNIGATE?===<br />
You can find an explanation on the site [[Firmware-Aktualisierung/en|Firmware update]].<br />
<br />
===I encountered problems with the RS232 connection between UNIGATE and PC. What to do when WINGATE says "no Gateway found"?===<br />
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.<br />
<br />
===How to connect an UNIGATE with the RS232-interface (COM port) at the PC?===<br />
At the PC COM port there is a 9-pole D-SUB pin connection with the following assignment:<br />
<br />
PIN 2 - Rx (from the PC's point of view)<br />
<br />
PIN 3 - Tx (from the PC's point of view)<br />
<br />
PIN 5 - GND<br />
<br />
Example: At the UNIGATE CL the assignment of the X1 is as follows:<br />
<br />
PIN 1 - Rx 232 (from the UNIGATE's point of view)<br />
<br />
PIN 2 - Tx 232 (from the UNIGATE's point of view)<br />
<br />
PIN 3 - AP-GND<br />
<br />
Generally always the Rx of the PC has to be connected with the Tx of the UNIGATE and the Tx of the PC with the Rx of the UNIGATE. Also the GND always has to be connected.<br />
<br />
For the above example it comes to the following cable assignment:<br />
<br />
UNIGATE X1 PIN1 &harr; PC PIN3<br />
<br />
UNIGATE X1 PIN2 &harr; PC PIN2<br />
<br />
UNIGATE X1 PIN3 &harr; PC PIN5<br />
<br />
===Does UNIGATE have a "test mode"?===<br />
Yes, there is a test mode.<br />
<br />
The interface-switch has to be set to position »RS232« and the two rotary coding switches on the serial side (S4 + S5) have to be set to »EE« in order to put the device into the test mode.<br />
<br />
After the restart the UNIGATE sends a byte on the serial side from »0-F« every second (some devices will first do a 15 to 30 seconds lasting self test). On the Fieldbus this output occurs accordinglywith the length depending on the set bus width. If useful data is sent to the UNIGATE (serial and Fieldbus) they are sent back from the UNIGATE (ECHO).<br />
<br />
===How to get my script into the device?===<br />
'''Advice:''' Please always use the current version of the corresponding software.<br />
<br />
Basically there are two ways to load the script into the UNIGATE.<br />
<br />
'''Possibility 1''' - via the serial (application-) interface: (applies to ALL UNIGATE SC, IC & CL) The script has to be compiled in the PROTOCOL DEVELOPER by "File &rarr; save compiled file" (the script receives the file extension *.dcs), so that the script gets into the device this way. The device has to be set into the configuration mode in order to load the script into the device. The script download can be started with the software WINGATE through "File &rarr; Write Script". With the software SPT (ScriptProgramTool) the downlaod is initiated through "File &rarr; Open file and program".<br />
<br />
'''Possibility 2''' - via the DEBUG-interface and the software PROTOCOL DEVELOPER: (applies to ALL UNIGATE IC & CL as well as UNIGATE SC with option "DB") In this case the device's DEBUG-interface has to be connected with a PC COM-Port. In the software PROTOCOL DEVELOPER and belated power up of the device (NOT in the configuration mode) the message "Device started in Debug mode" appears in the bottom left corner. Now the download can be started with "DEBUG".<br />
<br />
===How to set the UNIGATE into the configuration mode (Configmode)?===<br />
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.<br />
For the UNIGATE CL the RS232 interface is automatically active throught the switch positions of S4+S5 with "FF".<br />
If you use the UNIGATE IC the basis board of the J17.<br />
<br />
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):<br />
<br />
''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''<br />
Configmode...<br />
<br />
Now you know that the unit is in configuration mode.<br />
<br />
'''Practice Tip:''' With UNIGATE CL, RS and SC the configuration mode is visually indicated by the RS-"State" LED flashing red.<br />
<br />
=== What is to consider when switching to UNIGATE CL from UNIGATE SC? ===<br />
There is one significant difference between an UNIGATE SC and an UNIGATE CL: the UNIGATE SC devices have a hardware switch "232 &harr; 485", which does not exist on an UNIGATE CL. The UNIGATE 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 <br />
<source lang="delphi"> Set(RS_Type,[?]) </source> <br />
command.<br />
In the PROFIBUS version there is also the difference of the ID number. The UNIGATE CL-DP needs the GSD file UGIC3218.gsd.<br />
<br />
=== Does the UNIGATE IC support SPI?===<br />
Yes, the UNIGATE IC supports SPI. (Up-to-date [http://www.deutschmann.de/de/produkte/download.php?file_id=412 UNIGATE IC Pinout-List] in XLS Format)<br />
Pin 3...7 are for the SPI Master (SPI slave on request only)<br />
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.<br />
<br />
===How to connect two networks (PROFIBUS / PROFINET)?===<br />
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.<br />
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.<br />
<br />
===Fieldbus===<br />
====CANopen====<br />
=====UNIGATE CO (M)-PROFIBUS DP===== <br />
=====I encountered problems after downloading the existing/old GWC-file into my new device. Can you list the various steps?=====<br />
#Open the desired GWC file with the configuration tool WINGATE. <br />
#Then start the new device and perform the download<br />
#Now perform an Upload from the device<br />
#The parameter "CAN baud rate" is now at 125k. <br />
#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.<br />
#Afterwards perform another download<br />
#Save the change, respectively the "new" GWC file<br />
<br />
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.<br />
<br />
=====How to replace CANopen (Master) - PROFIBUS DP (Slave)?=====<br />
#Start WINGATE:<br />
#Connect the RS232 from PC to UNIGATE (3 wire, 3 pin connector)<br />
#Connect power supply<br />
#Upload file<br />
#Save file<br />
#Disconnect the old UNIGATE <br />
#Connect the new UNIGATE (see Step 1)<br />
#Afterwards click "File - Download" (write to device)<br />
<br />
<br />
<gallery><br />
Datei:Start WINGATE V2.65(379).png|1. Start WINGATE<br />
Datei:WINGATE_V2.64(379)_Versorgungsanschluss.png|3. Connect power supply<br />
Datei:WINGATE_V2.65(379)_File_upload.png|4. File upload<br />
Datei:WINGATE_Save_as.png|4. Save as<br />
Datei:WINGATE_V2.65(379)_File_download_screen.png|8. File-Download<br />
</gallery><br />
<br />
=====In WINGATE-File the Adresse 0x14 is set to 0=====<br />
With the new Firmware V2.60 in WINGATE the config file has to be stored with the setting "baud rate: DIP Switch"<br />
<br />
====DeviceNet====<br />
=====How much power does the UNIGATE IC draw at the DeviceNet power supply 24 Volt connector, PIN 17?=====<br />
The current consumption is max. 35mA.<br />
<br />
====EtherNet/IP====<br />
=====How to switch to EtherNet/IP 2Port?=====<br />
You can find more about switching to EtherNet/IP 2 Port on the UNIGATE CL EtherNet/IP site: [[UNIGATE_EtherNet/IP/en|Changeover to 2-Port devices]]<br />
<br />
=====My PLC cannot establish a connection to my EtherNet/IP device. What could be the reason?=====<br />
Maybe you configured your PLC to use a Unicast connection.<br />
<br />
If you are using the Rockwell software RSLogix 5000 you can check this in the UNIGATE's module properties dialogue. Please make sure the option "Use Unicast Connection over EtherNet/IP" on the connection tab is disabled.<br />
<br />
===== Why does the function <code>ReadNewObjectDataEIP</code> show a change of input data, altough all of the data is identical? =====<br />
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.<br />
<br />
===== Can I only transfer an even number of bytes with an EtherNet/IP device? =====<br />
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).<br />
<br />
=====Can a power supply separation be avoided through a script adaptation in a UNIGATE EtherNet/IP with firmware 4.0?=====<br />
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).<br />
<br />
====Fast Ethernet====<br />
=====Is there an example of the web server functionality ?=====<br />
Yes, there is an example, which is available after installing the PROTOCOL DEVELOPER.<br />
# Start the UNIGATE CL-FE in configmode<br />
# Reset device (WINGATE - options - reset device)<br />
# Save the script example: Wingate – File – Write script ... :\Software\ProtocolDeveloper\Example\08 Bus specific\Fast Ethernet script.dcs<br />
# Set the IP address and the subnet mask (Do not forget to download the file)<br />
# Start the UNIGATE in Run mode (S4+5 not FF and not EE)<br />
# Start a FTP Client, such as [http://www.ghisler.com/index.htm Total Commander]. Establish a FTP connection. (Username and password: deutschmann)<br />
# Directory: Flash<br />
# Copy "index.html" to CL-FE<br />
# Start your browser and enter the IP address you created in WINGATE<br />
# If you refresh your browser (F5) you will see that the numerical value increased<br />
# That's it!<br />
<br />
<gallery><br />
Datei:WINGATE V2.72(385) Set IP Adress set subnet mask.png|4. IP address and subnet mask<br />
Datei:FTP TotalCommander Connection details.png|6. FTP Client<br />
Datei:FTP TotalCommander Verzeichnis flash.png|7. Change directory<br />
Datei:FTP TotalCommander Copy index.png|8. Copy index.html <br />
Datei:WINGATE FTP Browser.png|9. IP address in Browser<br />
</gallery><br />
<br />
=====Is the temperature range down to -40°C by now available for CL devices with RJ45 connectors?=====<br />
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.<br />
In our expansion card for CL and FC a RJ45 for -40°C is used.<br />
<br />
====PROFIBUS====<br />
=====At commissioning a PROFIBUS-slave I do not see any input data when put and also it is not possible to send data to the device.=====<br />
For CPUs from the company Siemens only direct access up to 4 bytes is possible. Provided that useful data > 4 bytes are supposed to be read or written, then the access has to be made through the SFC14 (read) and SFC15 (write). Further information can be found in the projection software's help.<br />
<br />
=====How to use the UNIGATE IC PROFIBUS DPV1 5V without driver 485 and how much current can the DC/DC converter provide on the fieldbus side?=====<br />
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.<br />
<br />
=====Changing of the Slave ID via SPS=====<br />
ID is stored in EEROM.<br />
<source lang="delphi"><br />
var LBusState : Long ;<br />
var L0xE0 : Long ; moveconst ( L0xE0, 0xE0);<br />
<br />
BusStart ;<br />
//Wait ( Bus_Active ) ;<br />
<br />
:LoopBusState;<br />
Get ( ReadBusState , LBusState ) ;<br />
if LBusState less L0xE0 then :LoopBusState; //!!! neu<br />
</source><br />
<br />
=====Which GSD-file is meant for my device?=====<br />
We distinguish between 2 versions: DPV0 and DPV1. You can tell from the article description which device is in front of you. A »DP« stands for DPV0; a »DPV1« for itself. The UNIGATE IC-DPL and UNIGATE CL is a DPV1-device.<br />
<br />
In the download-area of the respective device only that GSD-file, which is valid for the corresponding device only, is placed at your disposal for download.<br />
<br />
A DPV1 slave is downwards compatible and it can also operate in the DPV0 mode. Nevertheless, the DPV1 GSD-file has to be used.<br />
<br />
DPV0 slave &rarr; GSDfile »DAGW2079.GSD«<br />
<br />
DPV1 slave &rarr; GSD-file »UGIC3218.GSD«<br />
<br />
=====GSD Datei - How to create a different configuration?=====<br />
[[Datei:PB_GSD_Configuration_telegramm_8_Word_Out.jpg|thumb|Create a configuration]]<br />
<br />
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.<br />
In this Modul, you can setup every size.<br />
<br />
=====How to set the Slave ID via the Master?=====<br />
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.<br />
<br />
WARNING: With it the EEROM will be re-initialized and the script will be deleted.<br />
<br />
=====How to realize the conversion from Fieldbus &harr; Modbus RTU (Master)?=====<br />
''This proceeding for a UNIGATE CL-PROFIBUS DPV1 is used as an example for all UNIGATEs and the supported Fieldbuses.''<br />
<br />
UNIGATE CL is supplied with a Universal Script that makes setting the "Modbus RTU (Master)" protocol very simple. A detailed description how to configure the device can be found here.<br />
<br />
Note: In case you want to read out the same register several times, then the parameter ''"Data Exchange"'' should be adjusted to ''"On Trigger"''. In this case the UNIGATE expects the togglebyte in the Fieldbus Master's first byte.<br />
<br />
Application:<br />
<br />
The Fieldbus Master requests (read holding register = 03) the register "4567" with the length of 1 word from the Modbus Slave with the ID=2. The resulting inquiry from the Profibus-Master to the UNIGATE is:<br />
<br />
02 03 45 67 00 01<br />
<br />
(ID=2, read register=03, register=4567 and length in words high + low=0001) <br />
<br />
The UNIGATE converts data to Modbus and adds the checksum (=xx):<br />
<br />
02 03 4567 00 01 xx<br />
<br />
The UNIGATE receives the following response from the Modbus Slave with the ID=2:<br />
<br />
02 03 02 03 E8 xx<br />
<br />
(ID=2, read register=03, length in byte =02, value of the register 4567=03E8 and checksum=xx)<br />
<br />
The UNIGATE puts the Modbusslave's response on the Fieldbus:<br />
<br />
02 03 02 03 E8<br />
<br />
Consequently a complete inquiry from the Fieldbus Masters has been converted to Modbus and the Slave's response has been issued to the Fieldbus in turn.<br />
<br />
The above proceeding describes the function of the UNIGATE RS, UNIGATE CL with Universal Script and configured Modbus-RTU(Master) protocol as well as our Script examples Modbus-RTU(Master).<br />
<br />
There are also applications, in which the UNIGATE is supposed to read out a corresponding register or also the UNIGATE cyclically reads the same regsiter again and again through only 1 byte of the Fieldbus Master. With our UNIGATE SC, CL and IC this is possible without a problem. In these two cases the Script only has to be adapted to this requirement. Please use our Script examples for this.<br />
<br />
====PROFINET====<br />
=====How to connect Deutschmann PROFINET devices to a S7?=====<br />
For a step-by-step instruction, please download the PDF [http://deutschmann.de/produkte/download.php?file_id=681].<br />
<br />
=====How to evaluate a UNIGATE device with a PROFINET interface?=====<br />
You can evaluate your PROFINET device (UNIGATE CL-Profinet, UNIGATE IC-Profinet, UNIGATE FC-Profinet) with our free PROFINET Module software. All you need is a Microsoft Windows computer with an Ethernet port. The PROFINET Module software is part of our Starter Kit software collection which can be obtained from the download section.<br />
<br />
=====Why can't I assign a device name to my UNIGATE?=====<br />
For PROFINET the device name is subject to a [[PROFINET_Device_name_(English)|naming convention]]. For example, the use of capital letters is not allowed.<br />
<br />
=====How to rename the GSDML file?=====<br />
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.<br />
<br />
=====Script with station name=====<br />
[[Datei:PN_Script_mit_Stationsname_Set_device.png|thumb|Script with station name]]<br />
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.<br />
If a name is then set in the PROFINET Master it is effective from now on.<br />
<br />
===Series===<br />
====UNIGATE CL====<br />
=====Can I use my configuration file of the series UNIGATE RS for UNIGATE CL as well?=====<br />
We will be supplying the devices UNIGATE CL with a "UNIVERSAL" script (if it had not been handled that way so far). This script then acts as if it was a UNIGATE RS. That means that the UNIGATE CL can be parameterized via the configuration software WINGATE. An "old" UNIGATE RS configuration file is not compatible with that of the UNIGATE CL. If a UNIGATE RS is to be changed over to UNIGATE CL, then the UNIGATE CL must be read out once via WINGATE and the protocol settings have to be made. This configuration can then be stored in the usual manner and it can be used again for devices of the same type.<br />
<br />
Note: If a "Reset Device" is carried out with a UNIGATE CL, then the "UNIVERSAL" script gets lost and it has to be loaded again.<br />
<br />
=====I want to download my UNIGATE SC-PB Script into the UNIGATE CL-PB. The PROFIBUS State LED remains red and/or the serial communication does not work.=====<br />
This "phenomenon" has two reasons:<br />
<br />
# The UNIGATE SC-PB requires the GSD-file "DAGW2079.gsd" and the UNIGATE CL-PB requires the GSD-file "UGIC3218.gsd".<br />
# The interface of the UNIGATE SC-PB is set via the switch "Interface" and at the UNIGATE CL-PB it is set in the Script.<br />
<br />
Remedy:<br />
1. Either the GSD-file for the UNIGATE CL-PB in the PROFIBUS Master in the hardware configuration is changed to "UGIC3218.gsd" or the Ident number has to be changed to "2079" in the Script through the command:<br />
Set ( IdentNumber , 0x2079 ) ; //default: 0x3218<br />
<br />
After the Script download the UNIGATE CL-PB acts like a UNIGATE SC-PB at the PROFIBUS.<br />
<br />
2. The interfaces of the UNIGATE CL-PB have to be defined in the Script by means of the Script command:<br />
Set ( RS_Type , RS232 ) ; //or RS485 or RS422<br />
<br />
=====How to configure the UNIGATE CL with WINGATE?=====<br />
Note: This instruction refers to the configuration of UNIGATE CL in connection with the Universal Script.<br />
<br />
The current version of the software WINGATE has to be installed on the PC in order to be able to configure the UNIGATE CL.<br />
<br />
Subsequently the UNIGATE CL has to be connected to the PC via the application interface X1. The required wiring can be found here.<br />
<br />
<br />
The "Universalscript Deutschmann" has to be available in the device, so that it can be configured by WINGATE. When the software WINGATE is executed and the UNIGATE is restarted then you receive the following actuation message from the UNIGATE in the lower part of WINGATE (example: V3553 UNIGATE CL-ProfibusDP):<br />
<br />
RS-PBV1-CL (232/422/485) V7.31[30] (c)dA Switch=0x01FF Script(16k)="Universalscript Deutschmann" Author="G/S" Version="V 0.2d" Date 24.07.2008 SN: 3553xxxx ID=1<br />
Konfigmode...<br />
<br />
IMPORTANT: ALL following points cannot be carried out unless you receive this message (with or without "Universalscript Deutschmann")!<br />
<br />
In case the Script is not in the device, it can be loaded into the UNIGATE with the function File -> ''Write Script'' (the Script can be found on the Support CD at: \Software\ProtocolDeveloper\Example\Universal\CL_Universal.dcs or on our website in category "Software").<br />
<br />
Now the UNIGATE CL can be read-out through ''File &rarr; Upload''. Both options ''more items visible & more items editable'' have to be acivated in order to be able to set all functions.<br />
<br />
The configuration itself should be made from the top to the bottom. The desired parameters can be moved to the corresponding line with double-click.<br />
<br />
When the configuration is completed the altered values have to written into the device with ''File &rarr; Download''. This is confirmed by the UNIGATE with:<br />
<br />
Download ok<br />
<br />
Store data... ...<br />
<br />
Restart<br />
<br />
RS-PBV1-CL (232/422/485) V7.31[30] (c)dA Switch=0x01FF Script(16k)="Universalscript Deutschmann" Author="G/S" Version="V 0.2d" Date 24.07.2008 SN: 3553xxxx ID=1<br />
Konfigmode...<br />
<br />
With it the configuration is finished. Now the device has to be switched to 'voltageless' and the rotary switch at the device has to be adjusted accordingly and connected to the application. Now the device can be put into operation.<br />
<br />
=====Can you deliver the Protocol Converter UNIGATE CL in a lacquered version?=====<br />
The lacquering of this series does not make sense, since the mechanical oponents such as rotary coding switches, plug connectors, etc. can not be lacquered and thus a disruption would occur.<br />
<br />
====UNIGATE IC====<br />
=====Problem with the virtual COM-ports via USB=====<br />
If the Developerboard UNIGATE IC-AB is connected via the USB-interface, then the following procedure has to be taken into account:<br />
<br />
# Adjust all switches, rotary switches and jumpers in accordance to the UNIGATE IC that is to be used.<br />
# Connect the Developerboard UNIGATE IC-AB through the USB-cable to the PC/laptop and supply the Developerboard UNIGATE IC-AB with voltage through the provided power supply.<br />
# Put the UNIGATE IC on the socket of the Developerboard UNIGATE IC-AB and set the switch ''POWER'' to position ON afterwards. Only now the operating system of the PC recognizes the new virtual interfaces and during initial startup the drivers are installed.<br />
# Execute the corresponding software application now and select the (new) interface in ''Options''.<br />
# Please push the button ''Reset''. The device responds now (provided that the switch ''Mode is set to Config'') with the startup message or the Script is being executed (switch ''Mode on Run'' and the software ''PROTOCOL DEVELOPER'' is not initiated) or the device starts in the DebugMode (if the switch ''Mode is set to Run'' and the software ''PROTOCOL DEVELOPER'' is being executed).<br />
<br />
Therefore the switch ''POWER'' should not be changed any more since the virtual COM-ports will be re-initialized again with any change from ''ON&rarr;OFF&rarr;ON''.<br />
<br />
=====Is it possible to lacquer the series UNIGATE IC?=====<br />
There is no reason why the series UNIGATE IC cannot be lacquered. However, the complete assembly (the whole customer's device) should be lacquered in one piece. To lacquer the UNIGATE IC first would involve a disproportionate high effort, which would lead to high costs (e. g. The software would have to be downloaded before, tapeing of the pins and so on). Therefore we are not supplying the UNIGATE IC-series in lacquered form.<br />
<br />
====UNIGATE RS====<br />
The lacquering of this series does not make sense, since the mechanical oponents such as rotary coding switches, plug connectors, etc. can not be lacquered and thus a disruption would occur. We offer die-cast aluminium housing for these applications.<br />
<br />
===PROTOCOL DEVELOPER===<br />
====The PROTOCOL DEVELOPERs help window is empty. What can I do?====<br />
By default the help-file has to be existent on a local drive (e. g. C:\)<br />
<br />
In order to be able to also access the help-file from a network drive the following lines have to be entered into Notepad and saved as "*.REG" file:REGEDIT4 <br />
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp] <br />
<br />
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp\1.x\HHRestrictions] <br />
<br />
"MaxAllowedZone"=dword:00000001 "EnableFrameNavigationInSafeMode"=dword:00000001 <br />
<br />
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp\1.x\ItssRestrictions] <br />
<br />
"MaxAllowedZone"=dword:00000001When the file has been generated it is executed with a double click. The PC has to be restarted, so that the changes will be accepted.<br />
<br />
For further information as well as possible risks please log on to: http://support.microsoft.com/kb/896358/de<br />
<br />
<br />
''Microsoft Windows Vista:''<br />
<br />
By default the access to "*.CHM"-files is denied. In order to make an access possible though, click with the right button on the the file properties under General on Unblock. The help file opens now.<br />
<br />
===WINGATE===</div>Reithhttps://wiki.deutschmann.de/index.php?title=en:Frequently_asked_questions_Fieldbus-_and_Industrial-Ethernet-Devices&diff=3451en:Frequently asked questions Fieldbus- and Industrial-Ethernet-Devices2019-08-27T13:17:57Z<p>Reith: /* Are there replacements for a product that is no longer available? (LOCON 32-HC, LOCON 32-PM)... */</p>
<hr />
<div>== Electronic Cam Controls ==<br />
===Are there replacements for a product that is no longer available? (LOCON 32-HC, LOCON 32-PM)...===<br />
1. Substitution option with [[LOCON 24 (English)|LOCON 24]]:<br />
<br />
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.<br />
<br />
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.<br />
<br />
2. Substitution option with [[LOCON 100 (English)|LOCON 100]] / [[LOCON 200 (English)|LOCON 200]]:<br />
<br />
Basically the following points ALWAYS have to be clarified in case of replacing a product that is no longer available: (Example in italic)<br />
* Which encoder is used in connection with the cam control (NSW) (maximum of 16 inputs) &rarr; number of encoder inputs &rarr; at INC. at least 2, at absolute &rarr; number of tracks = number inputs)<br />
<br />
''A TA58-O360-GYE is used &rarr; 9 tracks = 9 inputs''<br />
<br />
* What other pins are used? (e. g. at INC. encoders Clear + and/or Clear- &rarr; number of inputs +1 or +2)<br />
<br />
''None &rarr; + 0 inputs''<br />
<br />
* Is the Prog.Enable wired? (if yes &rarr; number of inputs +1)<br />
<br />
''Yes. &rarr; +1 input''<br />
<br />
* Is the external program selection wired? If yes, how many programs? (number of inputs +2 ... +7)<br />
<br />
''Yes, up to program 8. 5 pins are required for it &rarr; +5 inputs''<br />
<br />
According to the amount here the decision is made, whether [[LOCON 100 (English)|LOCON 100]] or [[LOCON 200 (English)|LOCON 200]] can be used. Provided that the amount remains below 16, either a [[LOCON 100 (English)|LOCON 100]] or a [[LOCON 200 (English)|LOCON 200]] can be used. If the amount of required inputs exceeds 16, then a [[LOCON 100 (English)|LOCON 100]] 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 [[LOCON 100 (English)|LOCON 100]] or [[LOCON 200 (English)|LOCON 200]] can be used. Quantity determination of expansion modules that have to be used (LOCON 100-A32 or LOCON 200-IO8):<br />
<br />
* Is the RunControl-relay wired? If yes &rarr; number of outputs + 1<br />
<br />
''Yes. + 1 output for RunControl''<br />
<br />
* How many outputs are used at the cam control? &rarr; Number of the basis' remaining outputs (LOCON 100 + LOCON 200) = 16 - number of inputs<br />
<br />
''32 outputs are used. &rarr; Total = 1 + 32 = 33 outputs. Either LOCON 100 (1 output) with an LOCON 100-A32 extension (=32 outputs) OR LOCON 200 (1 output) + 3 x LOCON 200-IO8 (8 outputs each = 32 outputs) can be used here.''<br />
<br />
Basically the version LOCON 200 + LOCON 200-IO8 is to be favored, since the cycle times for this constellation are lower than those for LOCON 100.<br />
<br />
On principle it does not matter which TERM is used. [[LOCON 100 (English)|LOCON 100]] & [[LOCON 200 (English)|LOCON 200]] are supported by TERM 6, TERM 24 & TERM 32 to a partially limited extent. For that reason the parameterization and configuration should principally always be carried out with [[WINLOC 32 (English)|WINLOC 32]] and the mentioned TERMs should be used for operation.<br />
<br />
===How to connect a LOCON with the RS232-interface (COM port) at the PC?===<br />
At the PC COM port there is a 9-pole D-SUB pin connection with the following assignment:<br />
<br />
PIN 2 - Rx (from the PC's point of view)<br />
<br />
PIN 3 - Tx (from the PC's point of view)<br />
<br />
PIN 5 - GND<br />
<br />
Example:<br />
<br />
At the LOCON16/17 the assignment of the X2 is as follows:<br />
<br />
PIN 26 - GND<br />
<br />
PIN 27 - Rx 232 (from the LOCON's point of view)<br />
<br />
PIN 28 - Tx 232 (from the LOCON's point of view)<br />
<br />
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.<br />
<br />
For the above example it comes to the following cable assignment:<br />
<br />
LOCON X2 PIN26 &harr; PC PIN5<br />
<br />
LOCON X2 PIN27 &harr; PC PIN3<br />
<br />
LOCON X2 PIN28 &harr; PC PIN2<br />
<br />
Note:<br />
Possible existing blue bridges between the signals "DICNET-/Rx" &harr; "R-" and "DICNET+/Tx" &harr; "R+" have to be removed.<br />
<br />
===How to reset a LOCON 90, LOCON 100, LOCON 100-PB, LOCON 200, LOCON 200-PB, ROTARNOCK 100 or ROTARNOCK 100-PB back to delivery condition (reset)?===<br />
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 WINLOC 32 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 LOCON 100 with an expansion LOCON 100-A32 with DICNET communication, configured as Timer with a counting range of 16):<br />
<br />
''L100-48(48)-T16-485(DICNET) V3.4''<br />
<br />
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: <br />
''Reset configuration to defaultvalue and clear all programmed data (Y/N)? N''<br />
<br />
This query has to be confirmed with "y" within 3 seconds and another safety query follows:<br />
<br />
''Cancel operation (Y/N) N'' which is to be confirmed with "n".<br />
<br />
If the entry is correct, the following message appears in the terminal window:<br />
<div style="border: 1px solid #136db9; background-color: #fafafa; padding: 8px;"><br />
''Clear EEROM 0H-1fffH ...............................<br />
<br />
Restart<br />
<br />
L100-48(48)-S4096-485(DICNET) V3.4 ok<br />
<br />
(Error: 108)''<br />
</div><br />
With it the device was set back to the condition it was originally supplied.<br />
<br />
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.<br />
Note: After a reset the optional LOGIC-function has to be activated again. At the devices LOCON 100 & LOCON 200 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.<br />
<br />
===How to activate the logic function of LOCON 100-PB, LOCON 200, LOCON 200-PB, ROTARNOCK 100 or ROTARNOCK 100-PB?===<br />
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 LOCON 100-PB, LOCON 200 or LOCON 200-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.<br />
<br />
The device to be extended by the logic function must be connected to the PC and a start-up string has to be shown WINLOC 32.<br />
<br />
With a click on the menue ''Extras &rarr; Product Option Activation'' a window opens for activation.<br />
<br />
The DICNET-ID is entered in the line Device ID. For a connection through RS232 this value remains on "0".<br />
<br />
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 &harr; PC works).<br />
<br />
The release code is entered in the line ''Activation key''. Start behind the "-".<br />
Click on ''Run'' afterwards.<br />
<br />
(In case of an error "Returncode=4" is the result.)<br />
<br />
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:<br />
<br />
L200-16-S4096-H-''LG''-232 Vx.x<br />
<br />
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:<br />
<br />
Note: After a "Clear all" the logic function has to be released again.<br />
<br />
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 LOCON 100-PB; LOCON 200(-PB) & ROTARNOCK 100(-PB)".<br />
<br />
===External Wiring===<br />
====How is the modification from LOCON 32-HC or LOCON 32-PM to LOCON 24 carried out?====<br />
Introductorily we like to point out that this description refers to a LOCON 32-HC, that is/was configured "absolute parallel 360" as encoder type. Consequently the LOCON 24 also has to contain this "O360" in the article text.<br />
<br />
{| class="wikitable"<br />
!LOCON 24 !!Signal !!LOCON 32-HC !!LOCON 32-PM<br />
|-<br />
|X1 PIN 1 ||OUT 1 ||X10 PIN 2 ||X1 PIN 1<br />
|-<br />
|X1 PIN 2 ||OUT 2 ||X10 PIN 1 ||X1 PIN 2<br />
|-<br />
|X1 PIN 3 ||OUT 3 ||X10 PIN 4 ||X1 PIN 3<br />
|-<br />
|X1 PIN 4 ||OUT 4 ||X10 PIN 3 ||X1 PIN 4<br />
|-<br />
|X1 PIN 5 ||OUT 5 ||X10 PIN 6 ||X1 PIN 5<br />
|-<br />
|X1 PIN 6 ||OUT 6 ||X10 PIN 5 ||X1 PIN 6<br />
|-<br />
|X1 PIN 7 ||OUT 7 ||X10 PIN 8 ||X1 PIN 7<br />
|-<br />
|X1 PIN 8 ||OUT 8 ||X10 PIN 7 ||X1 PIN 8<br />
|-<br />
|X1 PIN 9 ||OUT 9 ||X10 PIN 10 ||X1 PIN 9<br />
|}<br />
<br />
... [http://www.deutschmann.de/en/support/faq_detail.html?question=18 more]<br />
<br />
=== Models ===<br />
==== What has to be considered when using a LOCON 200 in connection with TERM 24? ====<br />
If a (discontinued) device is supposed to be replaced by a LOCON 200 and in case a TERM 24 is used in the assembly, then the TERM 24's Firmware must be updated at any rate. For the update the device has to be sent back to us.<br />
<br />
==== TN65 - ROTARNOCK - what is it? ====<br />
It is the same unit. ROTARNOCK describes the product line and TN65 is the specific type or the article description.<br />
<br />
Example:<br />
ROTARNOCK 100 - describes the ROTARNOCK-family "100". The detailed article description is explained on the picture "Article description".<br />
<br />
[[Datei:Article description Rotarnock English.jpg|thumb|Article description]]<br />
<br />
<br />
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.<br />
<br />
==== How to change the Profibus Ident Number? ====<br />
To change the Profibus Ident Number from 3606H to 3231 the ROTARNOCK 100-PB has to be connected with the PC via a serial communication (RS232). For the serial communication the following pin assignemt is valid here:<br />
<br />
PC PIN2 (Rx) ↔ ROTARNOCK 25pin D-Sub PIN17 (Tx RED)<br /><br />
PC PIN3 (Tx) ↔ ROTARNOCK 25pin D-Sub PIN18 (Rx RED)<br /><br />
PC PIN5 (GND) ↔ ROTARNOCK 25pin D-Sub PIN25 (GND)<br />
<br />
A corresponding programming cable (including plug-in power supply) is to be ordered with the article number V3467. ( V3467 - Programming cable for ROTARNOCK - 232/PB).<br />
<br />
The software WINLOC 32 has to be installed on th PC. The interface parameters are entered in "Extras → Options → Port".<br />
<br />
If the ROTARNOCK is now supplied with voltage a window opens automatically and the device brings its start-up message, e. g.:<br />
'''R100-48-O4096-PB(126)-232 V3.54 Ok'''<br />
Now place in WINLOC 32 the cursor behind the last character (through a "left click") and press "n" while keeping the keys "STRG/CTRL" pressed.<br />
The following confirmation prompt appears:<br />
'''Ident-Nr=3606H, change to 3231H (Y/N)? N'''<br />
This query has to be confirmed with "'''y'''" within 3 seconds and the following confirmation appears:<br />
'''New Ident-Nr = 3231H'''<br />
After a re-start the device uses the new Ident Number and it can be put into operation.<br />
<br />
The same way the Ident Number can also be changed back from 3231H to 3606H.<br />
<br />
==== How to replace a ROTARNOCK 1/2/3/4 by a ROTARNOCK 100? ====<br />
There are two ways to carry out the exchange.<br />
<br />
'''1.'''<br />
Exchange with the convenient programming software for cam controls WINLOC 32 (recommended procedure):<br />
<br />
Read out (File&rarr;Upload) the ROTARNOCK that is to be replaced with the software WINLOC 32 and store (File&rarr;Save) it on the hard disk or open an existing configuration file.<br />
<br />
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:<br />
Encoder resolution, ITC (=idle time compensation) Type, Display factor, ITC Function, Turn Direction, Run-Control and Zero shift.<br />
<br />
Important: Please write down the indicated position during downtime (best in the basic position if possible) before removing the old device! <br />
<br />
Connect the ROTARNOCK 100 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 ROTARNOCK 100 back in default mode can be found here.<br />
<br />
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.<br />
<br />
Enter the value for the Virtual Resolution here and select the ITC Type and confirm it with OK. <br />
<br />
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!<br />
<br />
'''Important advice:'''<br />
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.<br />
<br />
We recommend to carry out the zero adjustment first before the cams are being transmitted to the device.<br />
Load the newly generated configuration in the ROTARNOCK 100 through Download. Install the ROTARNOCK 100 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.<br />
<br />
In WINLOC32 the cam values, idle times and output names are transmitted from the old configuration file to the new one through Extras &rarr; Data transfer. This function is only available in the Comfort version of WINLOC 32.<br />
<br />
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 [mailto:hotline@deutschmann.de hotline@deutschmann.de].<br />
<br />
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. <br />
<br />
'''2.'''<br />
Exchange with manual configuration and programming with TERM 6 or TERM 24 (with current Firmware):<br />
<br />
The following information on the ROTARNOCK that is to be exchanged should be available:<br />
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.<br />
<br />
Advice: In case your old device features the option R - RunControl, then the device has to be configured with WINLOC 32.<br />
<br />
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. <br />
<br />
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.<br />
<br />
Now you can start entering the cams and idle times and finally the application can be tested and be put into operation.<br />
<br />
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 WINLOC 32.<br />
<br />
===Software Tools===<br />
====Configuration- and programming-software for cam controls?====<br />
A configuration- and programming-software [[WINLOC 32 (English)|WINLOC 32]] is available for all Deutschmann cam controls (NS).<br />
<br />
The basic version of that software is available free of charge (in the download-area and on the support-DVD). This basic version already features extensive functions. The cam control can be read out, configured and programmed. Also these files can be stored. <br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
====How and where is to enter the WINLOC 32 comfort version license key?====<br />
First of all start WINLOC 32.<br />
<br />
In the menu line "Extras" &rarr; select "Options". A window opens. If necessary please change to the register "License".<br />
Now enter the license key you received from us.<br />
<br />
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 "*".<br />
<br />
A license that have been purchased once can be used for all follow-up versions. A WINLOC 6 license also works with WINLOC 32.<br />
<br />
== UNIGATE ==<br />
===How to carry out a Firmware update at UNIGATE?===<br />
You can find an explanation on the site [[Firmware-Aktualisierung/en|Firmware update]].<br />
<br />
===I encountered problems with the RS232 connection between UNIGATE and PC. What to do when WINGATE says "no Gateway found"?===<br />
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.<br />
<br />
===How to connect an UNIGATE with the RS232-interface (COM port) at the PC?===<br />
At the PC COM port there is a 9-pole D-SUB pin connection with the following assignment:<br />
<br />
PIN 2 - Rx (from the PC's point of view)<br />
<br />
PIN 3 - Tx (from the PC's point of view)<br />
<br />
PIN 5 - GND<br />
<br />
Example: At the UNIGATE CL the assignment of the X1 is as follows:<br />
<br />
PIN 1 - Rx 232 (from the UNIGATE's point of view)<br />
<br />
PIN 2 - Tx 232 (from the UNIGATE's point of view)<br />
<br />
PIN 3 - AP-GND<br />
<br />
Generally always the Rx of the PC has to be connected with the Tx of the UNIGATE and the Tx of the PC with the Rx of the UNIGATE. Also the GND always has to be connected.<br />
<br />
For the above example it comes to the following cable assignment:<br />
<br />
UNIGATE X1 PIN1 &harr; PC PIN3<br />
<br />
UNIGATE X1 PIN2 &harr; PC PIN2<br />
<br />
UNIGATE X1 PIN3 &harr; PC PIN5<br />
<br />
===Does UNIGATE have a "test mode"?===<br />
Yes, there is a test mode.<br />
<br />
The interface-switch has to be set to position »RS232« and the two rotary coding switches on the serial side (S4 + S5) have to be set to »EE« in order to put the device into the test mode.<br />
<br />
After the restart the UNIGATE sends a byte on the serial side from »0-F« every second (some devices will first do a 15 to 30 seconds lasting self test). On the Fieldbus this output occurs accordinglywith the length depending on the set bus width. If useful data is sent to the UNIGATE (serial and Fieldbus) they are sent back from the UNIGATE (ECHO).<br />
<br />
===How to get my script into the device?===<br />
'''Advice:''' Please always use the current version of the corresponding software.<br />
<br />
Basically there are two ways to load the script into the UNIGATE.<br />
<br />
'''Possibility 1''' - via the serial (application-) interface: (applies to ALL UNIGATE SC, IC & CL) The script has to be compiled in the PROTOCOL DEVELOPER by "File &rarr; save compiled file" (the script receives the file extension *.dcs), so that the script gets into the device this way. The device has to be set into the configuration mode in order to load the script into the device. The script download can be started with the software WINGATE through "File &rarr; Write Script". With the software SPT (ScriptProgramTool) the downlaod is initiated through "File &rarr; Open file and program".<br />
<br />
'''Possibility 2''' - via the DEBUG-interface and the software PROTOCOL DEVELOPER: (applies to ALL UNIGATE IC & CL as well as UNIGATE SC with option "DB") In this case the device's DEBUG-interface has to be connected with a PC COM-Port. In the software PROTOCOL DEVELOPER and belated power up of the device (NOT in the configuration mode) the message "Device started in Debug mode" appears in the bottom left corner. Now the download can be started with "DEBUG".<br />
<br />
===How to set the UNIGATE into the configuration mode (Configmode)?===<br />
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.<br />
For the UNIGATE CL the RS232 interface is automatically active throught the switch positions of S4+S5 with "FF".<br />
If you use the UNIGATE IC the basis board of the J17.<br />
<br />
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):<br />
<br />
''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''<br />
Configmode...<br />
<br />
Now you know that the unit is in configuration mode.<br />
<br />
'''Practice Tip:''' With UNIGATE CL, RS and SC the configuration mode is visually indicated by the RS-"State" LED flashing red.<br />
<br />
=== What is to consider when switching to UNIGATE CL from UNIGATE SC? ===<br />
There is one significant difference between an UNIGATE SC and an UNIGATE CL: the UNIGATE SC devices have a hardware switch "232 &harr; 485", which does not exist on an UNIGATE CL. The UNIGATE 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 <br />
<source lang="delphi"> Set(RS_Type,[?]) </source> <br />
command.<br />
In the PROFIBUS version there is also the difference of the ID number. The UNIGATE CL-DP needs the GSD file UGIC3218.gsd.<br />
<br />
=== Does the UNIGATE IC support SPI?===<br />
Yes, the UNIGATE IC supports SPI. (Up-to-date [http://www.deutschmann.de/de/produkte/download.php?file_id=412 UNIGATE IC Pinout-List] in XLS Format)<br />
Pin 3...7 are for the SPI Master (SPI slave on request only)<br />
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.<br />
<br />
===How to connect two networks (PROFIBUS / PROFINET)?===<br />
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.<br />
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.<br />
<br />
===Fieldbus===<br />
====CANopen====<br />
=====UNIGATE CO (M)-PROFIBUS DP===== <br />
=====I encountered problems after downloading the existing/old GWC-file into my new device. Can you list the various steps?=====<br />
#Open the desired GWC file with the configuration tool WINGATE. <br />
#Then start the new device and perform the download<br />
#Now perform an Upload from the device<br />
#The parameter "CAN baud rate" is now at 125k. <br />
#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.<br />
#Afterwards perform another download<br />
#Save the change, respectively the "new" GWC file<br />
<br />
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.<br />
<br />
=====How to replace CANopen (Master) - PROFIBUS DP (Slave)?=====<br />
#Start WINGATE:<br />
#Connect the RS232 from PC to UNIGATE (3 wire, 3 pin connector)<br />
#Connect power supply<br />
#Upload file<br />
#Save file<br />
#Disconnect the old UNIGATE <br />
#Connect the new UNIGATE (see Step 1)<br />
#Afterwards click "File - Download" (write to device)<br />
<br />
<br />
<gallery><br />
Datei:Start WINGATE V2.65(379).png|1. Start WINGATE<br />
Datei:WINGATE_V2.64(379)_Versorgungsanschluss.png|3. Connect power supply<br />
Datei:WINGATE_V2.65(379)_File_upload.png|4. File upload<br />
Datei:WINGATE_Save_as.png|4. Save as<br />
Datei:WINGATE_V2.65(379)_File_download_screen.png|8. File-Download<br />
</gallery><br />
<br />
=====In WINGATE-File the Adresse 0x14 is set to 0=====<br />
With the new Firmware V2.60 in WINGATE the config file has to be stored with the setting "baud rate: DIP Switch"<br />
<br />
====DeviceNet====<br />
=====How much power does the UNIGATE IC draw at the DeviceNet power supply 24 Volt connector, PIN 17?=====<br />
The current consumption is max. 35mA.<br />
<br />
====EtherNet/IP====<br />
=====How to switch to EtherNet/IP 2Port?=====<br />
You can find more about switching to EtherNet/IP 2 Port on the UNIGATE CL EtherNet/IP site: [[UNIGATE_EtherNet/IP/en|Changeover to 2-Port devices]]<br />
<br />
=====My PLC cannot establish a connection to my EtherNet/IP device. What could be the reason?=====<br />
Maybe you configured your PLC to use a Unicast connection.<br />
<br />
If you are using the Rockwell software RSLogix 5000 you can check this in the UNIGATE's module properties dialogue. Please make sure the option "Use Unicast Connection over EtherNet/IP" on the connection tab is disabled.<br />
<br />
===== Why does the function <code>ReadNewObjectDataEIP</code> show a change of input data, altough all of the data is identical? =====<br />
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.<br />
<br />
===== Can I only transfer an even number of bytes with an EtherNet/IP device? =====<br />
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).<br />
<br />
=====Can a power supply separation be avoided through a script adaptation in a UNIGATE EtherNet/IP with firmware 4.0?=====<br />
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).<br />
<br />
====Fast Ethernet====<br />
=====Is there an example of the web server functionality ?=====<br />
Yes, there is an example, which is available after installing the PROTOCOL DEVELOPER.<br />
# Start the UNIGATE CL-FE in configmode<br />
# Reset device (WINGATE - options - reset device)<br />
# Save the script example: Wingate – File – Write script ... :\Software\ProtocolDeveloper\Example\08 Bus specific\Fast Ethernet script.dcs<br />
# Set the IP address and the subnet mask (Do not forget to download the file)<br />
# Start the UNIGATE in Run mode (S4+5 not FF and not EE)<br />
# Start a FTP Client, such as [http://www.ghisler.com/index.htm Total Commander]. Establish a FTP connection. (Username and password: deutschmann)<br />
# Directory: Flash<br />
# Copy "index.html" to CL-FE<br />
# Start your browser and enter the IP address you created in WINGATE<br />
# If you refresh your browser (F5) you will see that the numerical value increased<br />
# That's it!<br />
<br />
<gallery><br />
Datei:WINGATE V2.72(385) Set IP Adress set subnet mask.png|4. IP address and subnet mask<br />
Datei:FTP TotalCommander Connection details.png|6. FTP Client<br />
Datei:FTP TotalCommander Verzeichnis flash.png|7. Change directory<br />
Datei:FTP TotalCommander Copy index.png|8. Copy index.html <br />
Datei:WINGATE FTP Browser.png|9. IP address in Browser<br />
</gallery><br />
<br />
=====Is the temperature range down to -40°C by now available for CL devices with RJ45 connectors?=====<br />
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.<br />
In our expansion card for CL and FC a RJ45 for -40°C is used.<br />
<br />
====PROFIBUS====<br />
=====At commissioning a PROFIBUS-slave I do not see any input data when put and also it is not possible to send data to the device.=====<br />
For CPUs from the company Siemens only direct access up to 4 bytes is possible. Provided that useful data > 4 bytes are supposed to be read or written, then the access has to be made through the SFC14 (read) and SFC15 (write). Further information can be found in the projection software's help.<br />
<br />
=====How to use the UNIGATE IC PROFIBUS DPV1 5V without driver 485 and how much current can the DC/DC converter provide on the fieldbus side?=====<br />
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.<br />
<br />
=====Changing of the Slave ID via SPS=====<br />
ID is stored in EEROM.<br />
<source lang="delphi"><br />
var LBusState : Long ;<br />
var L0xE0 : Long ; moveconst ( L0xE0, 0xE0);<br />
<br />
BusStart ;<br />
//Wait ( Bus_Active ) ;<br />
<br />
:LoopBusState;<br />
Get ( ReadBusState , LBusState ) ;<br />
if LBusState less L0xE0 then :LoopBusState; //!!! neu<br />
</source><br />
<br />
=====Which GSD-file is meant for my device?=====<br />
We distinguish between 2 versions: DPV0 and DPV1. You can tell from the article description which device is in front of you. A »DP« stands for DPV0; a »DPV1« for itself. The UNIGATE IC-DPL and UNIGATE CL is a DPV1-device.<br />
<br />
In the download-area of the respective device only that GSD-file, which is valid for the corresponding device only, is placed at your disposal for download.<br />
<br />
A DPV1 slave is downwards compatible and it can also operate in the DPV0 mode. Nevertheless, the DPV1 GSD-file has to be used.<br />
<br />
DPV0 slave &rarr; GSDfile »DAGW2079.GSD«<br />
<br />
DPV1 slave &rarr; GSD-file »UGIC3218.GSD«<br />
<br />
=====GSD Datei - How to create a different configuration?=====<br />
[[Datei:PB_GSD_Configuration_telegramm_8_Word_Out.jpg|thumb|Create a configuration]]<br />
<br />
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.<br />
In this Modul, you can setup every size.<br />
<br />
=====How to set the Slave ID via the Master?=====<br />
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.<br />
<br />
WARNING: With it the EEROM will be re-initialized and the script will be deleted.<br />
<br />
=====How to realize the conversion from Fieldbus &harr; Modbus RTU (Master)?=====<br />
''This proceeding for a UNIGATE CL-PROFIBUS DPV1 is used as an example for all UNIGATEs and the supported Fieldbuses.''<br />
<br />
UNIGATE CL is supplied with a Universal Script that makes setting the "Modbus RTU (Master)" protocol very simple. A detailed description how to configure the device can be found here.<br />
<br />
Note: In case you want to read out the same register several times, then the parameter ''"Data Exchange"'' should be adjusted to ''"On Trigger"''. In this case the UNIGATE expects the togglebyte in the Fieldbus Master's first byte.<br />
<br />
Application:<br />
<br />
The Fieldbus Master requests (read holding register = 03) the register "4567" with the length of 1 word from the Modbus Slave with the ID=2. The resulting inquiry from the Profibus-Master to the UNIGATE is:<br />
<br />
02 03 45 67 00 01<br />
<br />
(ID=2, read register=03, register=4567 and length in words high + low=0001) <br />
<br />
The UNIGATE converts data to Modbus and adds the checksum (=xx):<br />
<br />
02 03 4567 00 01 xx<br />
<br />
The UNIGATE receives the following response from the Modbus Slave with the ID=2:<br />
<br />
02 03 02 03 E8 xx<br />
<br />
(ID=2, read register=03, length in byte =02, value of the register 4567=03E8 and checksum=xx)<br />
<br />
The UNIGATE puts the Modbusslave's response on the Fieldbus:<br />
<br />
02 03 02 03 E8<br />
<br />
Consequently a complete inquiry from the Fieldbus Masters has been converted to Modbus and the Slave's response has been issued to the Fieldbus in turn.<br />
<br />
The above proceeding describes the function of the UNIGATE RS, UNIGATE CL with Universal Script and configured Modbus-RTU(Master) protocol as well as our Script examples Modbus-RTU(Master).<br />
<br />
There are also applications, in which the UNIGATE is supposed to read out a corresponding register or also the UNIGATE cyclically reads the same regsiter again and again through only 1 byte of the Fieldbus Master. With our UNIGATE SC, CL and IC this is possible without a problem. In these two cases the Script only has to be adapted to this requirement. Please use our Script examples for this.<br />
<br />
====PROFINET====<br />
=====How to connect Deutschmann PROFINET devices to a S7?=====<br />
For a step-by-step instruction, please download the PDF [http://deutschmann.de/produkte/download.php?file_id=681].<br />
<br />
=====How to evaluate a UNIGATE device with a PROFINET interface?=====<br />
You can evaluate your PROFINET device (UNIGATE CL-Profinet, UNIGATE IC-Profinet, UNIGATE FC-Profinet) with our free PROFINET Module software. All you need is a Microsoft Windows computer with an Ethernet port. The PROFINET Module software is part of our Starter Kit software collection which can be obtained from the download section.<br />
<br />
=====Why can't I assign a device name to my UNIGATE?=====<br />
For PROFINET the device name is subject to a [[PROFINET_Device_name_(English)|naming convention]]. For example, the use of capital letters is not allowed.<br />
<br />
=====How to rename the GSDML file?=====<br />
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.<br />
<br />
=====Script with station name=====<br />
[[Datei:PN_Script_mit_Stationsname_Set_device.png|thumb|Script with station name]]<br />
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.<br />
If a name is then set in the PROFINET Master it is effective from now on.<br />
<br />
===Series===<br />
====UNIGATE CL====<br />
=====Can I use my configuration file of the series UNIGATE RS for UNIGATE CL as well?=====<br />
We will be supplying the devices UNIGATE CL with a "UNIVERSAL" script (if it had not been handled that way so far). This script then acts as if it was a UNIGATE RS. That means that the UNIGATE CL can be parameterized via the configuration software WINGATE. An "old" UNIGATE RS configuration file is not compatible with that of the UNIGATE CL. If a UNIGATE RS is to be changed over to UNIGATE CL, then the UNIGATE CL must be read out once via WINGATE and the protocol settings have to be made. This configuration can then be stored in the usual manner and it can be used again for devices of the same type.<br />
<br />
Note: If a "Reset Device" is carried out with a UNIGATE CL, then the "UNIVERSAL" script gets lost and it has to be loaded again.<br />
<br />
=====I want to download my UNIGATE SC-PB Script into the UNIGATE CL-PB. The PROFIBUS State LED remains red and/or the serial communication does not work.=====<br />
This "phenomenon" has two reasons:<br />
<br />
# The UNIGATE SC-PB requires the GSD-file "DAGW2079.gsd" and the UNIGATE CL-PB requires the GSD-file "UGIC3218.gsd".<br />
# The interface of the UNIGATE SC-PB is set via the switch "Interface" and at the UNIGATE CL-PB it is set in the Script.<br />
<br />
Remedy:<br />
1. Either the GSD-file for the UNIGATE CL-PB in the PROFIBUS Master in the hardware configuration is changed to "UGIC3218.gsd" or the Ident number has to be changed to "2079" in the Script through the command:<br />
Set ( IdentNumber , 0x2079 ) ; //default: 0x3218<br />
<br />
After the Script download the UNIGATE CL-PB acts like a UNIGATE SC-PB at the PROFIBUS.<br />
<br />
2. The interfaces of the UNIGATE CL-PB have to be defined in the Script by means of the Script command:<br />
Set ( RS_Type , RS232 ) ; //or RS485 or RS422<br />
<br />
=====How to configure the UNIGATE CL with WINGATE?=====<br />
Note: This instruction refers to the configuration of UNIGATE CL in connection with the Universal Script.<br />
<br />
The current version of the software WINGATE has to be installed on the PC in order to be able to configure the UNIGATE CL.<br />
<br />
Subsequently the UNIGATE CL has to be connected to the PC via the application interface X1. The required wiring can be found here.<br />
<br />
<br />
The "Universalscript Deutschmann" has to be available in the device, so that it can be configured by WINGATE. When the software WINGATE is executed and the UNIGATE is restarted then you receive the following actuation message from the UNIGATE in the lower part of WINGATE (example: V3553 UNIGATE CL-ProfibusDP):<br />
<br />
RS-PBV1-CL (232/422/485) V7.31[30] (c)dA Switch=0x01FF Script(16k)="Universalscript Deutschmann" Author="G/S" Version="V 0.2d" Date 24.07.2008 SN: 3553xxxx ID=1<br />
Konfigmode...<br />
<br />
IMPORTANT: ALL following points cannot be carried out unless you receive this message (with or without "Universalscript Deutschmann")!<br />
<br />
In case the Script is not in the device, it can be loaded into the UNIGATE with the function File -> ''Write Script'' (the Script can be found on the Support CD at: \Software\ProtocolDeveloper\Example\Universal\CL_Universal.dcs or on our website in category "Software").<br />
<br />
Now the UNIGATE CL can be read-out through ''File &rarr; Upload''. Both options ''more items visible & more items editable'' have to be acivated in order to be able to set all functions.<br />
<br />
The configuration itself should be made from the top to the bottom. The desired parameters can be moved to the corresponding line with double-click.<br />
<br />
When the configuration is completed the altered values have to written into the device with ''File &rarr; Download''. This is confirmed by the UNIGATE with:<br />
<br />
Download ok<br />
<br />
Store data... ...<br />
<br />
Restart<br />
<br />
RS-PBV1-CL (232/422/485) V7.31[30] (c)dA Switch=0x01FF Script(16k)="Universalscript Deutschmann" Author="G/S" Version="V 0.2d" Date 24.07.2008 SN: 3553xxxx ID=1<br />
Konfigmode...<br />
<br />
With it the configuration is finished. Now the device has to be switched to 'voltageless' and the rotary switch at the device has to be adjusted accordingly and connected to the application. Now the device can be put into operation.<br />
<br />
=====Can you deliver the Protocol Converter UNIGATE CL in a lacquered version?=====<br />
The lacquering of this series does not make sense, since the mechanical oponents such as rotary coding switches, plug connectors, etc. can not be lacquered and thus a disruption would occur.<br />
<br />
====UNIGATE IC====<br />
=====Problem with the virtual COM-ports via USB=====<br />
If the Developerboard UNIGATE IC-AB is connected via the USB-interface, then the following procedure has to be taken into account:<br />
<br />
# Adjust all switches, rotary switches and jumpers in accordance to the UNIGATE IC that is to be used.<br />
# Connect the Developerboard UNIGATE IC-AB through the USB-cable to the PC/laptop and supply the Developerboard UNIGATE IC-AB with voltage through the provided power supply.<br />
# Put the UNIGATE IC on the socket of the Developerboard UNIGATE IC-AB and set the switch ''POWER'' to position ON afterwards. Only now the operating system of the PC recognizes the new virtual interfaces and during initial startup the drivers are installed.<br />
# Execute the corresponding software application now and select the (new) interface in ''Options''.<br />
# Please push the button ''Reset''. The device responds now (provided that the switch ''Mode is set to Config'') with the startup message or the Script is being executed (switch ''Mode on Run'' and the software ''PROTOCOL DEVELOPER'' is not initiated) or the device starts in the DebugMode (if the switch ''Mode is set to Run'' and the software ''PROTOCOL DEVELOPER'' is being executed).<br />
<br />
Therefore the switch ''POWER'' should not be changed any more since the virtual COM-ports will be re-initialized again with any change from ''ON&rarr;OFF&rarr;ON''.<br />
<br />
=====Is it possible to lacquer the series UNIGATE IC?=====<br />
There is no reason why the series UNIGATE IC cannot be lacquered. However, the complete assembly (the whole customer's device) should be lacquered in one piece. To lacquer the UNIGATE IC first would involve a disproportionate high effort, which would lead to high costs (e. g. The software would have to be downloaded before, tapeing of the pins and so on). Therefore we are not supplying the UNIGATE IC-series in lacquered form.<br />
<br />
====UNIGATE RS====<br />
The lacquering of this series does not make sense, since the mechanical oponents such as rotary coding switches, plug connectors, etc. can not be lacquered and thus a disruption would occur. We offer die-cast aluminium housing for these applications.<br />
<br />
===PROTOCOL DEVELOPER===<br />
====The PROTOCOL DEVELOPERs help window is empty. What can I do?====<br />
By default the help-file has to be existent on a local drive (e. g. C:\)<br />
<br />
In order to be able to also access the help-file from a network drive the following lines have to be entered into Notepad and saved as "*.REG" file:REGEDIT4 <br />
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp] <br />
<br />
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp\1.x\HHRestrictions] <br />
<br />
"MaxAllowedZone"=dword:00000001 "EnableFrameNavigationInSafeMode"=dword:00000001 <br />
<br />
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp\1.x\ItssRestrictions] <br />
<br />
"MaxAllowedZone"=dword:00000001When the file has been generated it is executed with a double click. The PC has to be restarted, so that the changes will be accepted.<br />
<br />
For further information as well as possible risks please log on to: http://support.microsoft.com/kb/896358/de<br />
<br />
<br />
''Microsoft Windows Vista:''<br />
<br />
By default the access to "*.CHM"-files is denied. In order to make an access possible though, click with the right button on the the file properties under General on Unblock. The help file opens now.<br />
<br />
===WINGATE===</div>Reithhttps://wiki.deutschmann.de/index.php?title=en:Frequently_asked_questions_Fieldbus-_and_Industrial-Ethernet-Devices&diff=3450en:Frequently asked questions Fieldbus- and Industrial-Ethernet-Devices2019-08-27T13:16:18Z<p>Reith: /* Are there replacements for a product that is no longer available? (LOCON 32-HC, LOCON 32-PM)... */</p>
<hr />
<div>== Electronic Cam Controls ==<br />
===Are there replacements for a product that is no longer available? (LOCON 32-HC, LOCON 32-PM)...===<br />
1. Substitution option with [[LOCON 24 (English)|LOCON 24]]:<br />
<br />
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.<br />
<br />
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.<br />
<br />
2. Substitution option with [[LOCON 100 (English)|LOCON 100]] / [[LOCON 200 (English)|LOCON 200]]:<br />
<br />
Basically the following points ALWAYS have to be clarified in case of replacing a product that is no longer available: (Example in italic)<br />
* Which encoder is used in connection with the cam control (NSW) (maximum of 16 inputs) &rarr; number of encoder inputs &rarr; at INC. at least 2, at absolute &rarr; number of tracks = number inputs)<br />
<br />
''A TA58-O360-GYE is used &rarr; 9 tracks = 9 inputs''<br />
<br />
* What other pins are used? (e. g. at INC. encoders Clear + and/or Clear- &rarr; number of inputs +1 or +2)<br />
<br />
''None &rarr; + 0 inputs''<br />
<br />
* Is the Prog.Enable wired? (if yes &rarr; number of inputs +1)<br />
<br />
''Yes. &rarr; +1 input''<br />
<br />
* Is the external program selection wired? If yes, how many programs? (number of inputs +2 ... +7)<br />
<br />
''Yes, up to program 8. 5 pins are required for it &rarr; +5 inputs''<br />
<br />
According to the amount here the decision is made, whether [[LOCON 100 (English)|LOCON 100]] or [[LOCON 200 (English)|LOCON 200]] can be used. Provided that the amount remains below 16, either a [[LOCON 100 (English)|LOCON 100]] or a [[LOCON 200 (English)|LOCON 200]] can be used. If the amount of required inputs exceeds 16, then a [[LOCON 100 (English)|LOCON 100]] 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 [[LOCON 100 (English)|LOCON 100]] or a [[LOCON 200 (English)|LOCON 200]] can be used. Quantity determination of expansion modules that have to be used (LOCON 100-A32 or LOCON 200-IO8):<br />
<br />
* Is the RunControl-relay wired? If yes &rarr; number of outputs + 1<br />
<br />
''Yes. + 1 output for RunControl''<br />
<br />
* How many outputs are used at the cam control? &rarr; Number of the basis' remaining outputs (LOCON 100 + LOCON 200) = 16 - number of inputs<br />
<br />
''32 outputs are used. &rarr; Total = 1 + 32 = 33 outputs. Either a LOCON 100 (1 output) with an LOCON 100-A32 extension (=32 outputs) OR a LOCON 200 (1 output) + 3 x LOCON 200-IO8 (8 outputs each = 32 outputs) can be used here.''<br />
<br />
Basically the version LOCON 200 + LOCON 200-IO8 is to be favored, since the cycle times for this constellation are lower than those for LOCON 100.<br />
<br />
On principle it does not matter which TERM is used. [[LOCON 100 (English)|LOCON 100]] & [[LOCON 200 (English)|LOCON 200]] are supported by TERM 6, TERM 24 & TERM 32 to a partially limited extent. For that reason the parameterization and configuration should principally always be carried out with [[WINLOC 32 (English)|WINLOC 32]] and the mentioned TERMs should be used for operation.<br />
<br />
===How to connect a LOCON with the RS232-interface (COM port) at the PC?===<br />
At the PC COM port there is a 9-pole D-SUB pin connection with the following assignment:<br />
<br />
PIN 2 - Rx (from the PC's point of view)<br />
<br />
PIN 3 - Tx (from the PC's point of view)<br />
<br />
PIN 5 - GND<br />
<br />
Example:<br />
<br />
At the LOCON16/17 the assignment of the X2 is as follows:<br />
<br />
PIN 26 - GND<br />
<br />
PIN 27 - Rx 232 (from the LOCON's point of view)<br />
<br />
PIN 28 - Tx 232 (from the LOCON's point of view)<br />
<br />
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.<br />
<br />
For the above example it comes to the following cable assignment:<br />
<br />
LOCON X2 PIN26 &harr; PC PIN5<br />
<br />
LOCON X2 PIN27 &harr; PC PIN3<br />
<br />
LOCON X2 PIN28 &harr; PC PIN2<br />
<br />
Note:<br />
Possible existing blue bridges between the signals "DICNET-/Rx" &harr; "R-" and "DICNET+/Tx" &harr; "R+" have to be removed.<br />
<br />
===How to reset a LOCON 90, LOCON 100, LOCON 100-PB, LOCON 200, LOCON 200-PB, ROTARNOCK 100 or ROTARNOCK 100-PB back to delivery condition (reset)?===<br />
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 WINLOC 32 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 LOCON 100 with an expansion LOCON 100-A32 with DICNET communication, configured as Timer with a counting range of 16):<br />
<br />
''L100-48(48)-T16-485(DICNET) V3.4''<br />
<br />
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: <br />
''Reset configuration to defaultvalue and clear all programmed data (Y/N)? N''<br />
<br />
This query has to be confirmed with "y" within 3 seconds and another safety query follows:<br />
<br />
''Cancel operation (Y/N) N'' which is to be confirmed with "n".<br />
<br />
If the entry is correct, the following message appears in the terminal window:<br />
<div style="border: 1px solid #136db9; background-color: #fafafa; padding: 8px;"><br />
''Clear EEROM 0H-1fffH ...............................<br />
<br />
Restart<br />
<br />
L100-48(48)-S4096-485(DICNET) V3.4 ok<br />
<br />
(Error: 108)''<br />
</div><br />
With it the device was set back to the condition it was originally supplied.<br />
<br />
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.<br />
Note: After a reset the optional LOGIC-function has to be activated again. At the devices LOCON 100 & LOCON 200 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.<br />
<br />
===How to activate the logic function of LOCON 100-PB, LOCON 200, LOCON 200-PB, ROTARNOCK 100 or ROTARNOCK 100-PB?===<br />
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 LOCON 100-PB, LOCON 200 or LOCON 200-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.<br />
<br />
The device to be extended by the logic function must be connected to the PC and a start-up string has to be shown WINLOC 32.<br />
<br />
With a click on the menue ''Extras &rarr; Product Option Activation'' a window opens for activation.<br />
<br />
The DICNET-ID is entered in the line Device ID. For a connection through RS232 this value remains on "0".<br />
<br />
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 &harr; PC works).<br />
<br />
The release code is entered in the line ''Activation key''. Start behind the "-".<br />
Click on ''Run'' afterwards.<br />
<br />
(In case of an error "Returncode=4" is the result.)<br />
<br />
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:<br />
<br />
L200-16-S4096-H-''LG''-232 Vx.x<br />
<br />
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:<br />
<br />
Note: After a "Clear all" the logic function has to be released again.<br />
<br />
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 LOCON 100-PB; LOCON 200(-PB) & ROTARNOCK 100(-PB)".<br />
<br />
===External Wiring===<br />
====How is the modification from LOCON 32-HC or LOCON 32-PM to LOCON 24 carried out?====<br />
Introductorily we like to point out that this description refers to a LOCON 32-HC, that is/was configured "absolute parallel 360" as encoder type. Consequently the LOCON 24 also has to contain this "O360" in the article text.<br />
<br />
{| class="wikitable"<br />
!LOCON 24 !!Signal !!LOCON 32-HC !!LOCON 32-PM<br />
|-<br />
|X1 PIN 1 ||OUT 1 ||X10 PIN 2 ||X1 PIN 1<br />
|-<br />
|X1 PIN 2 ||OUT 2 ||X10 PIN 1 ||X1 PIN 2<br />
|-<br />
|X1 PIN 3 ||OUT 3 ||X10 PIN 4 ||X1 PIN 3<br />
|-<br />
|X1 PIN 4 ||OUT 4 ||X10 PIN 3 ||X1 PIN 4<br />
|-<br />
|X1 PIN 5 ||OUT 5 ||X10 PIN 6 ||X1 PIN 5<br />
|-<br />
|X1 PIN 6 ||OUT 6 ||X10 PIN 5 ||X1 PIN 6<br />
|-<br />
|X1 PIN 7 ||OUT 7 ||X10 PIN 8 ||X1 PIN 7<br />
|-<br />
|X1 PIN 8 ||OUT 8 ||X10 PIN 7 ||X1 PIN 8<br />
|-<br />
|X1 PIN 9 ||OUT 9 ||X10 PIN 10 ||X1 PIN 9<br />
|}<br />
<br />
... [http://www.deutschmann.de/en/support/faq_detail.html?question=18 more]<br />
<br />
=== Models ===<br />
==== What has to be considered when using a LOCON 200 in connection with TERM 24? ====<br />
If a (discontinued) device is supposed to be replaced by a LOCON 200 and in case a TERM 24 is used in the assembly, then the TERM 24's Firmware must be updated at any rate. For the update the device has to be sent back to us.<br />
<br />
==== TN65 - ROTARNOCK - what is it? ====<br />
It is the same unit. ROTARNOCK describes the product line and TN65 is the specific type or the article description.<br />
<br />
Example:<br />
ROTARNOCK 100 - describes the ROTARNOCK-family "100". The detailed article description is explained on the picture "Article description".<br />
<br />
[[Datei:Article description Rotarnock English.jpg|thumb|Article description]]<br />
<br />
<br />
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.<br />
<br />
==== How to change the Profibus Ident Number? ====<br />
To change the Profibus Ident Number from 3606H to 3231 the ROTARNOCK 100-PB has to be connected with the PC via a serial communication (RS232). For the serial communication the following pin assignemt is valid here:<br />
<br />
PC PIN2 (Rx) ↔ ROTARNOCK 25pin D-Sub PIN17 (Tx RED)<br /><br />
PC PIN3 (Tx) ↔ ROTARNOCK 25pin D-Sub PIN18 (Rx RED)<br /><br />
PC PIN5 (GND) ↔ ROTARNOCK 25pin D-Sub PIN25 (GND)<br />
<br />
A corresponding programming cable (including plug-in power supply) is to be ordered with the article number V3467. ( V3467 - Programming cable for ROTARNOCK - 232/PB).<br />
<br />
The software WINLOC 32 has to be installed on th PC. The interface parameters are entered in "Extras → Options → Port".<br />
<br />
If the ROTARNOCK is now supplied with voltage a window opens automatically and the device brings its start-up message, e. g.:<br />
'''R100-48-O4096-PB(126)-232 V3.54 Ok'''<br />
Now place in WINLOC 32 the cursor behind the last character (through a "left click") and press "n" while keeping the keys "STRG/CTRL" pressed.<br />
The following confirmation prompt appears:<br />
'''Ident-Nr=3606H, change to 3231H (Y/N)? N'''<br />
This query has to be confirmed with "'''y'''" within 3 seconds and the following confirmation appears:<br />
'''New Ident-Nr = 3231H'''<br />
After a re-start the device uses the new Ident Number and it can be put into operation.<br />
<br />
The same way the Ident Number can also be changed back from 3231H to 3606H.<br />
<br />
==== How to replace a ROTARNOCK 1/2/3/4 by a ROTARNOCK 100? ====<br />
There are two ways to carry out the exchange.<br />
<br />
'''1.'''<br />
Exchange with the convenient programming software for cam controls WINLOC 32 (recommended procedure):<br />
<br />
Read out (File&rarr;Upload) the ROTARNOCK that is to be replaced with the software WINLOC 32 and store (File&rarr;Save) it on the hard disk or open an existing configuration file.<br />
<br />
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:<br />
Encoder resolution, ITC (=idle time compensation) Type, Display factor, ITC Function, Turn Direction, Run-Control and Zero shift.<br />
<br />
Important: Please write down the indicated position during downtime (best in the basic position if possible) before removing the old device! <br />
<br />
Connect the ROTARNOCK 100 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 ROTARNOCK 100 back in default mode can be found here.<br />
<br />
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.<br />
<br />
Enter the value for the Virtual Resolution here and select the ITC Type and confirm it with OK. <br />
<br />
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!<br />
<br />
'''Important advice:'''<br />
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.<br />
<br />
We recommend to carry out the zero adjustment first before the cams are being transmitted to the device.<br />
Load the newly generated configuration in the ROTARNOCK 100 through Download. Install the ROTARNOCK 100 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.<br />
<br />
In WINLOC32 the cam values, idle times and output names are transmitted from the old configuration file to the new one through Extras &rarr; Data transfer. This function is only available in the Comfort version of WINLOC 32.<br />
<br />
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 [mailto:hotline@deutschmann.de hotline@deutschmann.de].<br />
<br />
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. <br />
<br />
'''2.'''<br />
Exchange with manual configuration and programming with TERM 6 or TERM 24 (with current Firmware):<br />
<br />
The following information on the ROTARNOCK that is to be exchanged should be available:<br />
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.<br />
<br />
Advice: In case your old device features the option R - RunControl, then the device has to be configured with WINLOC 32.<br />
<br />
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. <br />
<br />
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.<br />
<br />
Now you can start entering the cams and idle times and finally the application can be tested and be put into operation.<br />
<br />
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 WINLOC 32.<br />
<br />
===Software Tools===<br />
====Configuration- and programming-software for cam controls?====<br />
A configuration- and programming-software [[WINLOC 32 (English)|WINLOC 32]] is available for all Deutschmann cam controls (NS).<br />
<br />
The basic version of that software is available free of charge (in the download-area and on the support-DVD). This basic version already features extensive functions. The cam control can be read out, configured and programmed. Also these files can be stored. <br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
====How and where is to enter the WINLOC 32 comfort version license key?====<br />
First of all start WINLOC 32.<br />
<br />
In the menu line "Extras" &rarr; select "Options". A window opens. If necessary please change to the register "License".<br />
Now enter the license key you received from us.<br />
<br />
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 "*".<br />
<br />
A license that have been purchased once can be used for all follow-up versions. A WINLOC 6 license also works with WINLOC 32.<br />
<br />
== UNIGATE ==<br />
===How to carry out a Firmware update at UNIGATE?===<br />
You can find an explanation on the site [[Firmware-Aktualisierung/en|Firmware update]].<br />
<br />
===I encountered problems with the RS232 connection between UNIGATE and PC. What to do when WINGATE says "no Gateway found"?===<br />
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.<br />
<br />
===How to connect an UNIGATE with the RS232-interface (COM port) at the PC?===<br />
At the PC COM port there is a 9-pole D-SUB pin connection with the following assignment:<br />
<br />
PIN 2 - Rx (from the PC's point of view)<br />
<br />
PIN 3 - Tx (from the PC's point of view)<br />
<br />
PIN 5 - GND<br />
<br />
Example: At the UNIGATE CL the assignment of the X1 is as follows:<br />
<br />
PIN 1 - Rx 232 (from the UNIGATE's point of view)<br />
<br />
PIN 2 - Tx 232 (from the UNIGATE's point of view)<br />
<br />
PIN 3 - AP-GND<br />
<br />
Generally always the Rx of the PC has to be connected with the Tx of the UNIGATE and the Tx of the PC with the Rx of the UNIGATE. Also the GND always has to be connected.<br />
<br />
For the above example it comes to the following cable assignment:<br />
<br />
UNIGATE X1 PIN1 &harr; PC PIN3<br />
<br />
UNIGATE X1 PIN2 &harr; PC PIN2<br />
<br />
UNIGATE X1 PIN3 &harr; PC PIN5<br />
<br />
===Does UNIGATE have a "test mode"?===<br />
Yes, there is a test mode.<br />
<br />
The interface-switch has to be set to position »RS232« and the two rotary coding switches on the serial side (S4 + S5) have to be set to »EE« in order to put the device into the test mode.<br />
<br />
After the restart the UNIGATE sends a byte on the serial side from »0-F« every second (some devices will first do a 15 to 30 seconds lasting self test). On the Fieldbus this output occurs accordinglywith the length depending on the set bus width. If useful data is sent to the UNIGATE (serial and Fieldbus) they are sent back from the UNIGATE (ECHO).<br />
<br />
===How to get my script into the device?===<br />
'''Advice:''' Please always use the current version of the corresponding software.<br />
<br />
Basically there are two ways to load the script into the UNIGATE.<br />
<br />
'''Possibility 1''' - via the serial (application-) interface: (applies to ALL UNIGATE SC, IC & CL) The script has to be compiled in the PROTOCOL DEVELOPER by "File &rarr; save compiled file" (the script receives the file extension *.dcs), so that the script gets into the device this way. The device has to be set into the configuration mode in order to load the script into the device. The script download can be started with the software WINGATE through "File &rarr; Write Script". With the software SPT (ScriptProgramTool) the downlaod is initiated through "File &rarr; Open file and program".<br />
<br />
'''Possibility 2''' - via the DEBUG-interface and the software PROTOCOL DEVELOPER: (applies to ALL UNIGATE IC & CL as well as UNIGATE SC with option "DB") In this case the device's DEBUG-interface has to be connected with a PC COM-Port. In the software PROTOCOL DEVELOPER and belated power up of the device (NOT in the configuration mode) the message "Device started in Debug mode" appears in the bottom left corner. Now the download can be started with "DEBUG".<br />
<br />
===How to set the UNIGATE into the configuration mode (Configmode)?===<br />
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.<br />
For the UNIGATE CL the RS232 interface is automatically active throught the switch positions of S4+S5 with "FF".<br />
If you use the UNIGATE IC the basis board of the J17.<br />
<br />
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):<br />
<br />
''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''<br />
Configmode...<br />
<br />
Now you know that the unit is in configuration mode.<br />
<br />
'''Practice Tip:''' With UNIGATE CL, RS and SC the configuration mode is visually indicated by the RS-"State" LED flashing red.<br />
<br />
=== What is to consider when switching to UNIGATE CL from UNIGATE SC? ===<br />
There is one significant difference between an UNIGATE SC and an UNIGATE CL: the UNIGATE SC devices have a hardware switch "232 &harr; 485", which does not exist on an UNIGATE CL. The UNIGATE 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 <br />
<source lang="delphi"> Set(RS_Type,[?]) </source> <br />
command.<br />
In the PROFIBUS version there is also the difference of the ID number. The UNIGATE CL-DP needs the GSD file UGIC3218.gsd.<br />
<br />
=== Does the UNIGATE IC support SPI?===<br />
Yes, the UNIGATE IC supports SPI. (Up-to-date [http://www.deutschmann.de/de/produkte/download.php?file_id=412 UNIGATE IC Pinout-List] in XLS Format)<br />
Pin 3...7 are for the SPI Master (SPI slave on request only)<br />
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.<br />
<br />
===How to connect two networks (PROFIBUS / PROFINET)?===<br />
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.<br />
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.<br />
<br />
===Fieldbus===<br />
====CANopen====<br />
=====UNIGATE CO (M)-PROFIBUS DP===== <br />
=====I encountered problems after downloading the existing/old GWC-file into my new device. Can you list the various steps?=====<br />
#Open the desired GWC file with the configuration tool WINGATE. <br />
#Then start the new device and perform the download<br />
#Now perform an Upload from the device<br />
#The parameter "CAN baud rate" is now at 125k. <br />
#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.<br />
#Afterwards perform another download<br />
#Save the change, respectively the "new" GWC file<br />
<br />
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.<br />
<br />
=====How to replace CANopen (Master) - PROFIBUS DP (Slave)?=====<br />
#Start WINGATE:<br />
#Connect the RS232 from PC to UNIGATE (3 wire, 3 pin connector)<br />
#Connect power supply<br />
#Upload file<br />
#Save file<br />
#Disconnect the old UNIGATE <br />
#Connect the new UNIGATE (see Step 1)<br />
#Afterwards click "File - Download" (write to device)<br />
<br />
<br />
<gallery><br />
Datei:Start WINGATE V2.65(379).png|1. Start WINGATE<br />
Datei:WINGATE_V2.64(379)_Versorgungsanschluss.png|3. Connect power supply<br />
Datei:WINGATE_V2.65(379)_File_upload.png|4. File upload<br />
Datei:WINGATE_Save_as.png|4. Save as<br />
Datei:WINGATE_V2.65(379)_File_download_screen.png|8. File-Download<br />
</gallery><br />
<br />
=====In WINGATE-File the Adresse 0x14 is set to 0=====<br />
With the new Firmware V2.60 in WINGATE the config file has to be stored with the setting "baud rate: DIP Switch"<br />
<br />
====DeviceNet====<br />
=====How much power does the UNIGATE IC draw at the DeviceNet power supply 24 Volt connector, PIN 17?=====<br />
The current consumption is max. 35mA.<br />
<br />
====EtherNet/IP====<br />
=====How to switch to EtherNet/IP 2Port?=====<br />
You can find more about switching to EtherNet/IP 2 Port on the UNIGATE CL EtherNet/IP site: [[UNIGATE_EtherNet/IP/en|Changeover to 2-Port devices]]<br />
<br />
=====My PLC cannot establish a connection to my EtherNet/IP device. What could be the reason?=====<br />
Maybe you configured your PLC to use a Unicast connection.<br />
<br />
If you are using the Rockwell software RSLogix 5000 you can check this in the UNIGATE's module properties dialogue. Please make sure the option "Use Unicast Connection over EtherNet/IP" on the connection tab is disabled.<br />
<br />
===== Why does the function <code>ReadNewObjectDataEIP</code> show a change of input data, altough all of the data is identical? =====<br />
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.<br />
<br />
===== Can I only transfer an even number of bytes with an EtherNet/IP device? =====<br />
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).<br />
<br />
=====Can a power supply separation be avoided through a script adaptation in a UNIGATE EtherNet/IP with firmware 4.0?=====<br />
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).<br />
<br />
====Fast Ethernet====<br />
=====Is there an example of the web server functionality ?=====<br />
Yes, there is an example, which is available after installing the PROTOCOL DEVELOPER.<br />
# Start the UNIGATE CL-FE in configmode<br />
# Reset device (WINGATE - options - reset device)<br />
# Save the script example: Wingate – File – Write script ... :\Software\ProtocolDeveloper\Example\08 Bus specific\Fast Ethernet script.dcs<br />
# Set the IP address and the subnet mask (Do not forget to download the file)<br />
# Start the UNIGATE in Run mode (S4+5 not FF and not EE)<br />
# Start a FTP Client, such as [http://www.ghisler.com/index.htm Total Commander]. Establish a FTP connection. (Username and password: deutschmann)<br />
# Directory: Flash<br />
# Copy "index.html" to CL-FE<br />
# Start your browser and enter the IP address you created in WINGATE<br />
# If you refresh your browser (F5) you will see that the numerical value increased<br />
# That's it!<br />
<br />
<gallery><br />
Datei:WINGATE V2.72(385) Set IP Adress set subnet mask.png|4. IP address and subnet mask<br />
Datei:FTP TotalCommander Connection details.png|6. FTP Client<br />
Datei:FTP TotalCommander Verzeichnis flash.png|7. Change directory<br />
Datei:FTP TotalCommander Copy index.png|8. Copy index.html <br />
Datei:WINGATE FTP Browser.png|9. IP address in Browser<br />
</gallery><br />
<br />
=====Is the temperature range down to -40°C by now available for CL devices with RJ45 connectors?=====<br />
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.<br />
In our expansion card for CL and FC a RJ45 for -40°C is used.<br />
<br />
====PROFIBUS====<br />
=====At commissioning a PROFIBUS-slave I do not see any input data when put and also it is not possible to send data to the device.=====<br />
For CPUs from the company Siemens only direct access up to 4 bytes is possible. Provided that useful data > 4 bytes are supposed to be read or written, then the access has to be made through the SFC14 (read) and SFC15 (write). Further information can be found in the projection software's help.<br />
<br />
=====How to use the UNIGATE IC PROFIBUS DPV1 5V without driver 485 and how much current can the DC/DC converter provide on the fieldbus side?=====<br />
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.<br />
<br />
=====Changing of the Slave ID via SPS=====<br />
ID is stored in EEROM.<br />
<source lang="delphi"><br />
var LBusState : Long ;<br />
var L0xE0 : Long ; moveconst ( L0xE0, 0xE0);<br />
<br />
BusStart ;<br />
//Wait ( Bus_Active ) ;<br />
<br />
:LoopBusState;<br />
Get ( ReadBusState , LBusState ) ;<br />
if LBusState less L0xE0 then :LoopBusState; //!!! neu<br />
</source><br />
<br />
=====Which GSD-file is meant for my device?=====<br />
We distinguish between 2 versions: DPV0 and DPV1. You can tell from the article description which device is in front of you. A »DP« stands for DPV0; a »DPV1« for itself. The UNIGATE IC-DPL and UNIGATE CL is a DPV1-device.<br />
<br />
In the download-area of the respective device only that GSD-file, which is valid for the corresponding device only, is placed at your disposal for download.<br />
<br />
A DPV1 slave is downwards compatible and it can also operate in the DPV0 mode. Nevertheless, the DPV1 GSD-file has to be used.<br />
<br />
DPV0 slave &rarr; GSDfile »DAGW2079.GSD«<br />
<br />
DPV1 slave &rarr; GSD-file »UGIC3218.GSD«<br />
<br />
=====GSD Datei - How to create a different configuration?=====<br />
[[Datei:PB_GSD_Configuration_telegramm_8_Word_Out.jpg|thumb|Create a configuration]]<br />
<br />
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.<br />
In this Modul, you can setup every size.<br />
<br />
=====How to set the Slave ID via the Master?=====<br />
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.<br />
<br />
WARNING: With it the EEROM will be re-initialized and the script will be deleted.<br />
<br />
=====How to realize the conversion from Fieldbus &harr; Modbus RTU (Master)?=====<br />
''This proceeding for a UNIGATE CL-PROFIBUS DPV1 is used as an example for all UNIGATEs and the supported Fieldbuses.''<br />
<br />
UNIGATE CL is supplied with a Universal Script that makes setting the "Modbus RTU (Master)" protocol very simple. A detailed description how to configure the device can be found here.<br />
<br />
Note: In case you want to read out the same register several times, then the parameter ''"Data Exchange"'' should be adjusted to ''"On Trigger"''. In this case the UNIGATE expects the togglebyte in the Fieldbus Master's first byte.<br />
<br />
Application:<br />
<br />
The Fieldbus Master requests (read holding register = 03) the register "4567" with the length of 1 word from the Modbus Slave with the ID=2. The resulting inquiry from the Profibus-Master to the UNIGATE is:<br />
<br />
02 03 45 67 00 01<br />
<br />
(ID=2, read register=03, register=4567 and length in words high + low=0001) <br />
<br />
The UNIGATE converts data to Modbus and adds the checksum (=xx):<br />
<br />
02 03 4567 00 01 xx<br />
<br />
The UNIGATE receives the following response from the Modbus Slave with the ID=2:<br />
<br />
02 03 02 03 E8 xx<br />
<br />
(ID=2, read register=03, length in byte =02, value of the register 4567=03E8 and checksum=xx)<br />
<br />
The UNIGATE puts the Modbusslave's response on the Fieldbus:<br />
<br />
02 03 02 03 E8<br />
<br />
Consequently a complete inquiry from the Fieldbus Masters has been converted to Modbus and the Slave's response has been issued to the Fieldbus in turn.<br />
<br />
The above proceeding describes the function of the UNIGATE RS, UNIGATE CL with Universal Script and configured Modbus-RTU(Master) protocol as well as our Script examples Modbus-RTU(Master).<br />
<br />
There are also applications, in which the UNIGATE is supposed to read out a corresponding register or also the UNIGATE cyclically reads the same regsiter again and again through only 1 byte of the Fieldbus Master. With our UNIGATE SC, CL and IC this is possible without a problem. In these two cases the Script only has to be adapted to this requirement. Please use our Script examples for this.<br />
<br />
====PROFINET====<br />
=====How to connect Deutschmann PROFINET devices to a S7?=====<br />
For a step-by-step instruction, please download the PDF [http://deutschmann.de/produkte/download.php?file_id=681].<br />
<br />
=====How to evaluate a UNIGATE device with a PROFINET interface?=====<br />
You can evaluate your PROFINET device (UNIGATE CL-Profinet, UNIGATE IC-Profinet, UNIGATE FC-Profinet) with our free PROFINET Module software. All you need is a Microsoft Windows computer with an Ethernet port. The PROFINET Module software is part of our Starter Kit software collection which can be obtained from the download section.<br />
<br />
=====Why can't I assign a device name to my UNIGATE?=====<br />
For PROFINET the device name is subject to a [[PROFINET_Device_name_(English)|naming convention]]. For example, the use of capital letters is not allowed.<br />
<br />
=====How to rename the GSDML file?=====<br />
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.<br />
<br />
=====Script with station name=====<br />
[[Datei:PN_Script_mit_Stationsname_Set_device.png|thumb|Script with station name]]<br />
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.<br />
If a name is then set in the PROFINET Master it is effective from now on.<br />
<br />
===Series===<br />
====UNIGATE CL====<br />
=====Can I use my configuration file of the series UNIGATE RS for UNIGATE CL as well?=====<br />
We will be supplying the devices UNIGATE CL with a "UNIVERSAL" script (if it had not been handled that way so far). This script then acts as if it was a UNIGATE RS. That means that the UNIGATE CL can be parameterized via the configuration software WINGATE. An "old" UNIGATE RS configuration file is not compatible with that of the UNIGATE CL. If a UNIGATE RS is to be changed over to UNIGATE CL, then the UNIGATE CL must be read out once via WINGATE and the protocol settings have to be made. This configuration can then be stored in the usual manner and it can be used again for devices of the same type.<br />
<br />
Note: If a "Reset Device" is carried out with a UNIGATE CL, then the "UNIVERSAL" script gets lost and it has to be loaded again.<br />
<br />
=====I want to download my UNIGATE SC-PB Script into the UNIGATE CL-PB. The PROFIBUS State LED remains red and/or the serial communication does not work.=====<br />
This "phenomenon" has two reasons:<br />
<br />
# The UNIGATE SC-PB requires the GSD-file "DAGW2079.gsd" and the UNIGATE CL-PB requires the GSD-file "UGIC3218.gsd".<br />
# The interface of the UNIGATE SC-PB is set via the switch "Interface" and at the UNIGATE CL-PB it is set in the Script.<br />
<br />
Remedy:<br />
1. Either the GSD-file for the UNIGATE CL-PB in the PROFIBUS Master in the hardware configuration is changed to "UGIC3218.gsd" or the Ident number has to be changed to "2079" in the Script through the command:<br />
Set ( IdentNumber , 0x2079 ) ; //default: 0x3218<br />
<br />
After the Script download the UNIGATE CL-PB acts like a UNIGATE SC-PB at the PROFIBUS.<br />
<br />
2. The interfaces of the UNIGATE CL-PB have to be defined in the Script by means of the Script command:<br />
Set ( RS_Type , RS232 ) ; //or RS485 or RS422<br />
<br />
=====How to configure the UNIGATE CL with WINGATE?=====<br />
Note: This instruction refers to the configuration of UNIGATE CL in connection with the Universal Script.<br />
<br />
The current version of the software WINGATE has to be installed on the PC in order to be able to configure the UNIGATE CL.<br />
<br />
Subsequently the UNIGATE CL has to be connected to the PC via the application interface X1. The required wiring can be found here.<br />
<br />
<br />
The "Universalscript Deutschmann" has to be available in the device, so that it can be configured by WINGATE. When the software WINGATE is executed and the UNIGATE is restarted then you receive the following actuation message from the UNIGATE in the lower part of WINGATE (example: V3553 UNIGATE CL-ProfibusDP):<br />
<br />
RS-PBV1-CL (232/422/485) V7.31[30] (c)dA Switch=0x01FF Script(16k)="Universalscript Deutschmann" Author="G/S" Version="V 0.2d" Date 24.07.2008 SN: 3553xxxx ID=1<br />
Konfigmode...<br />
<br />
IMPORTANT: ALL following points cannot be carried out unless you receive this message (with or without "Universalscript Deutschmann")!<br />
<br />
In case the Script is not in the device, it can be loaded into the UNIGATE with the function File -> ''Write Script'' (the Script can be found on the Support CD at: \Software\ProtocolDeveloper\Example\Universal\CL_Universal.dcs or on our website in category "Software").<br />
<br />
Now the UNIGATE CL can be read-out through ''File &rarr; Upload''. Both options ''more items visible & more items editable'' have to be acivated in order to be able to set all functions.<br />
<br />
The configuration itself should be made from the top to the bottom. The desired parameters can be moved to the corresponding line with double-click.<br />
<br />
When the configuration is completed the altered values have to written into the device with ''File &rarr; Download''. This is confirmed by the UNIGATE with:<br />
<br />
Download ok<br />
<br />
Store data... ...<br />
<br />
Restart<br />
<br />
RS-PBV1-CL (232/422/485) V7.31[30] (c)dA Switch=0x01FF Script(16k)="Universalscript Deutschmann" Author="G/S" Version="V 0.2d" Date 24.07.2008 SN: 3553xxxx ID=1<br />
Konfigmode...<br />
<br />
With it the configuration is finished. Now the device has to be switched to 'voltageless' and the rotary switch at the device has to be adjusted accordingly and connected to the application. Now the device can be put into operation.<br />
<br />
=====Can you deliver the Protocol Converter UNIGATE CL in a lacquered version?=====<br />
The lacquering of this series does not make sense, since the mechanical oponents such as rotary coding switches, plug connectors, etc. can not be lacquered and thus a disruption would occur.<br />
<br />
====UNIGATE IC====<br />
=====Problem with the virtual COM-ports via USB=====<br />
If the Developerboard UNIGATE IC-AB is connected via the USB-interface, then the following procedure has to be taken into account:<br />
<br />
# Adjust all switches, rotary switches and jumpers in accordance to the UNIGATE IC that is to be used.<br />
# Connect the Developerboard UNIGATE IC-AB through the USB-cable to the PC/laptop and supply the Developerboard UNIGATE IC-AB with voltage through the provided power supply.<br />
# Put the UNIGATE IC on the socket of the Developerboard UNIGATE IC-AB and set the switch ''POWER'' to position ON afterwards. Only now the operating system of the PC recognizes the new virtual interfaces and during initial startup the drivers are installed.<br />
# Execute the corresponding software application now and select the (new) interface in ''Options''.<br />
# Please push the button ''Reset''. The device responds now (provided that the switch ''Mode is set to Config'') with the startup message or the Script is being executed (switch ''Mode on Run'' and the software ''PROTOCOL DEVELOPER'' is not initiated) or the device starts in the DebugMode (if the switch ''Mode is set to Run'' and the software ''PROTOCOL DEVELOPER'' is being executed).<br />
<br />
Therefore the switch ''POWER'' should not be changed any more since the virtual COM-ports will be re-initialized again with any change from ''ON&rarr;OFF&rarr;ON''.<br />
<br />
=====Is it possible to lacquer the series UNIGATE IC?=====<br />
There is no reason why the series UNIGATE IC cannot be lacquered. However, the complete assembly (the whole customer's device) should be lacquered in one piece. To lacquer the UNIGATE IC first would involve a disproportionate high effort, which would lead to high costs (e. g. The software would have to be downloaded before, tapeing of the pins and so on). Therefore we are not supplying the UNIGATE IC-series in lacquered form.<br />
<br />
====UNIGATE RS====<br />
The lacquering of this series does not make sense, since the mechanical oponents such as rotary coding switches, plug connectors, etc. can not be lacquered and thus a disruption would occur. We offer die-cast aluminium housing for these applications.<br />
<br />
===PROTOCOL DEVELOPER===<br />
====The PROTOCOL DEVELOPERs help window is empty. What can I do?====<br />
By default the help-file has to be existent on a local drive (e. g. C:\)<br />
<br />
In order to be able to also access the help-file from a network drive the following lines have to be entered into Notepad and saved as "*.REG" file:REGEDIT4 <br />
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp] <br />
<br />
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp\1.x\HHRestrictions] <br />
<br />
"MaxAllowedZone"=dword:00000001 "EnableFrameNavigationInSafeMode"=dword:00000001 <br />
<br />
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp\1.x\ItssRestrictions] <br />
<br />
"MaxAllowedZone"=dword:00000001When the file has been generated it is executed with a double click. The PC has to be restarted, so that the changes will be accepted.<br />
<br />
For further information as well as possible risks please log on to: http://support.microsoft.com/kb/896358/de<br />
<br />
<br />
''Microsoft Windows Vista:''<br />
<br />
By default the access to "*.CHM"-files is denied. In order to make an access possible though, click with the right button on the the file properties under General on Unblock. The help file opens now.<br />
<br />
===WINGATE===</div>Reithhttps://wiki.deutschmann.de/index.php?title=TERM_32_(English)&diff=3449TERM 32 (English)2019-08-27T13:11:42Z<p>Reith: /* Device replacement */</p>
<hr />
<div>[[Datei:TERM32.png|thumb|TERM 32]]<br />
== Device replacement ==<br />
There is '''no''' direct replacement for TERM 32. As an alternative you can use the operating units [[TERM 6 (English)|TERM 6]] or [[TERM 24 (English)|TERM 24]] or the configuration and programming software [[WINLOC 32 (English)|WINLOC 32]].<br />
In order to ensure a proper and fast replacement, we need the following information and components: <br />
#We have to know the serial-no. of the used cam control in order to check the compatibilty to a new TERM 6 or new TERM 24. <br />
#If the used cam control is not compatible to the new and actual TERM 6 or the new and actual TERM 24, then this cam control has to be replaced, too.<br />
#For read-out of the used cam control and its programming or, if needed for the configuration and programming of a new cam control with WINLOC32-Basic-or-comfort Version, a corresponding programming cable is needed.<br />
#For the configuration and programming with WINLOC 32-Basic-or-comfort Version, the PC is in need of a real COM-Port. If there is no real COM-Port at the PC, then a [[USB-to-RS232 converter]] has to be used.<br />
'''For a corresponding offer please let us know the serial no. of the used cam control.'''<br />
<br />
== Weblinks ==<br />
[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/Locon%2032,324abs,324ink/English/Locon32_e.pdf Manual for TERM 32] (PDF-file)</div>Reithhttps://wiki.deutschmann.de/index.php?title=LOCON_9_(English)&diff=3448LOCON 9 (English)2019-08-27T13:07:21Z<p>Reith: /* Device replacement */</p>
<hr />
<div>[[Datei:LOCON9.jpg|thumb|LOCON 9]]<br />
== Device replacement ==<br />
LOCON 9 was available until '''31.12.2014'''. Depending on the version used, LOCON 9 can be replaced by a corresponding [[LOCON 16 (English)|LOCON 16]], [[LOCON 17 (English)|LOCON 17]], [[LOCON 24 (English)|LOCON 24]], [[LOCON 90 (English)|LOCON 90]], [[LOCON 100 (English)|LOCON 100]], [[LOCON 200 (English)|LOCON 200]] or [[ROTARNOCK 100 (English)|ROTARNOCK 100]]. For all the required information regarding device replacement please check: [[Device replacement LOCON 7 & 9]].<br />
<br />
== Weblinks ==<br />
[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/Locon%207,9,9MT/English/LOCON%207_9_e.pdf Manual for LOCON 9] (PDF-file)</div>Reithhttps://wiki.deutschmann.de/index.php?title=LOCON_7_(English)&diff=3447LOCON 7 (English)2019-08-27T13:06:55Z<p>Reith: /* Device replacement */</p>
<hr />
<div>[[Datei:LOCON7.jpg|thumb|LOCON 7]]<br />
== Device replacement ==<br />
LOCON 7 was available until '''31.12.2014'''. Depending on the version used, LOCON 7 can be replaced by a corresponding [[LOCON 16 (English)|LOCON 16]], [[LOCON 17 (English)|LOCON 17]], [[LOCON 24 (English)|LOCON 24]], [[LOCON 90 (English)|LOCON 90]], [[LOCON 100 (English)|LOCON 100]], [[LOCON 200 (English)|LOCON 200]] or [[ROTARNOCK 100 (English)|ROTARNOCK 100]]. For all the required information regarding device replacement please check: [[Device replacement LOCON 7 & 9]].<br />
<br />
== Weblinks ==<br />
[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/Locon%207,9,9MT/English/LOCON%207_9_e.pdf Manual for LOCON 7] (PDF-file)</div>Reithhttps://wiki.deutschmann.de/index.php?title=LOCON_7_(English)&diff=3446LOCON 7 (English)2019-08-27T13:06:42Z<p>Reith: /* Device replacement */</p>
<hr />
<div>[[Datei:LOCON7.jpg|thumb|LOCON 7]]<br />
== Device replacement ==<br />
LOCON 7 was available until '''31.12.2014'''. Depending on the version used,LOCON 7 can be replaced by a corresponding [[LOCON 16 (English)|LOCON 16]], [[LOCON 17 (English)|LOCON 17]], [[LOCON 24 (English)|LOCON 24]], [[LOCON 90 (English)|LOCON 90]], [[LOCON 100 (English)|LOCON 100]], [[LOCON 200 (English)|LOCON 200]] or [[ROTARNOCK 100 (English)|ROTARNOCK 100]]. For all the required information regarding device replacement please check: [[Device replacement LOCON 7 & 9]].<br />
<br />
== Weblinks ==<br />
[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/Locon%207,9,9MT/English/LOCON%207_9_e.pdf Manual for LOCON 7] (PDF-file)</div>Reithhttps://wiki.deutschmann.de/index.php?title=LOCON_200_(English)&diff=3445LOCON 200 (English)2019-08-27T12:55:55Z<p>Reith: /* Programming */</p>
<hr />
<div>[[Datei:LOCON200_LOCON200_IO8.jpg|thumb|LOCON 200 and extension module LOCON 200-Out I/O8]]<br />
== Configuration ==<br />
By factory setting '''all''' LOCON 200 cam controls are configured as follows:<br />
*Outputs: '''16'''<br />
*Encoder Type: '''SSI Singleturn'''<br />
*Real Encoder resolution: '''4096'''<br />
*Virtual Encoder resolution: '''4096'''<br />
*Idle time: '''Bitwise'''<br />
This configuration set by default may be changed by using [[TERM 6 (English)|TERM 6]] or the software [[WINLOC 32 (English)|WINLOC 32]].<br />
<br />
== Programming ==<br />
LOCON 200 can be programmed by TERM 6 or [[TERM 24 (English)|TERM 24]] or the software WINLOC 32. The PROFIBUS-Version can be programmed also via PROFIBUS.<br />
<br />
== Device versions ==<br />
=== LOCON 200 ===<br />
LOCON 200 features a serial RS232-interface and a RS485-([[DICNET (English)|DICNET]]) interface, the needed setting is made through the corresponding rotary coding switches ''High'' und ''Low'', located at the bottom side of the device.<br />
{| class="wikitable"<br />
|+Switch Position<br />
|-<br />
! High !! Low !! Meaning<br />
|-<br />
| D || DICNET-Adress || DICNET-Operation, Bus Termination inactive<br />
|-<br />
| E || DICNET-Adress || DICNET-Operation, Bus Termination active<br />
|-<br />
| F || F || RS232-Operation<br />
|}<br />
'''Only''' the DICNET-Addresses '''0 ... 15''' (decimal) are supported (right rotary coding switch ''Low'' = DICNET-Address). Examples:<br />
{| class="wikitable"<br />
|+Switch Position<br />
|-<br />
! High !! Low !! Meaning<br />
|-<br />
| D || 3 || bus termination inactive, DICNET-Address '''3'''<br />
|-<br />
| E || C || bus termination active, DICNET-Address '''12'''<br />
|}<br />
''''Note:''' The setting via the rotary coding switches is done in ''hexadecimal''.<br />
<br />
=== LOCON 200-PB (PROFIBUS) ===<br />
LOCON 200-PB (PROFIBUS) is '''always''' PROFIBUS-Slave and features a serial RS232-interface and a PROFIBUS-Interface, instead of the RS485-(DICNET) Interface, the needed setting is made through the corresponding rotary coding switches ''High'' und ''Low'', located at the bottom side of the device. <br />
{| class="wikitable"<br />
|+Switch Position<br />
|-<br />
! High !! Low !! Meaning<br />
|-<br />
| 0 || 0 || PROFIBUS-operation, external address assignment <br />
|-<br />
| 0 || 1 || PROFIBUS-operation, Adress 1<br />
|-<br />
|colspan="3" align="center"| …<br />
|-<br />
| 7 || D || PROFIBUS-operation, Adress 125<br />
|-<br />
| 7 || E || PROFIBUS-operation, external address assignment <br />
|-<br />
| F || F || RS232-operation<br />
|}<br />
'''Note:''' The setting via the rotary coding switches is done in ''hexadecimal''.<br /><br />
In LOCON 200-PB two modes are selectable through WINLOC32 via the PROFIBUS-Interface.<br />
* '''S7-Modus''' (ex-works condition): For an operation at a Simatic S7 and for use of the [[Data component simulator]].<br />
* '''Communication Profile Mode''': For the Operation via the [[#Weblinks|Communication Profile for Deutschmann cam controls]].<br />
The PROFIBUS-Address (Slave-ID) is set on 126 (decimal) in the factory setting. <br />
If the rotary coding switch is on position "'''00'''" und "'''7E'''" then any desired address can be assigned either through WINLOC32 or the PROFIBUS-Master.<br />
The [[#Weblinks|'''GSD-file''' (L200.GSD)]] and a [[#Weblinks|'''S7-example project''']] are available for download on our homepage.<br />
Further information regarding LOCON 200-PB can be found in the manual [[#Weblinks|Cam Controls with Fieldbus-Connection]].<br />
=== LOCON 200-MB (Modbus) ===<br />
LOCON 200-MB (Modbus) is '''always''' a Modbus-RTU-Slave and is '''only''' available in the '''2-core cable-version'''. LOCON 200-MB features a RS232-Standard-Interface as well as a RS232-(Modbus-RTU) Interface and a RS485-(Modbus-RTU) Interface, which can be changed by adjusting the rotary coding switch ''High'' located at the bottom side of the device.<br />
{| class="wikitable"<br />
|+Switch position<br />
|-<br />
! High !! Low !! Meaning<br />
|-<br />
| C || x || RS232-Modbus (X = ModbusSlave-ID)<br />
|-<br />
| D || x || RS485-Modbus without bus termination (x = Modbus-Slave-ID)<br />
|-<br />
| E || x || RS485-Modbus with activated bus termination (x = Modbus-Slave-ID)<br />
|-<br />
| F || x || RS232-Standard Interface<br />
|}<br />
'''Note:''' '''Only''' Modbus-Addresses '''1 ... 15''' (decimal) are supported (right rotary coding switch ''Low'' = ID). The Broadcast address '''0''' is '''not''' supported. The Setting via the rotary coding switch is done in ''hexadecimal''.<br /><br />
The following Modbus-RTU-commands are supported by the device: <br />
{| class="wikitable"<br />
|+Modbus-RTU-commands<br />
|-<br />
! command !! meaning<br />
|-<br />
| 03 || (0x03) Read Holding Registers <br />
|-<br />
| 16 || (0x10) Preset Multiple Regs<br />
|}<br />
The transmission baud rate is '''19200 Baud'''; '''No Parity'''. Further information regarding LOCON 200-MB can be found in chapter ''LOCON 200 with Modbus'' of the [[#Weblinks|Manual for LOCON 200]].<br />
<br />
===LOCON 200-Out I/O8 (extension module)===<br />
LOCON 200-Out I/O8 is an '''extension module''' and contains 8 I/Os. With this extension module the basic device LOCON 200 resp. (-PB)/(-MB) can be expanded (depending on the version) by 8 I/Os step-by-step to a maximum configuration level of 144 I/Os (incl. the 16 I/Os of LOCON 200 resp. (-PB)/(-MB)). LOCON 200-Out I/O8 contains an own processor. Therefore, the switching accuracy (cycle time) is independent of the LOCON 200(-PB)/(-MB) Basic module.<br />
<br />
=== NT Module for LOCON 200-Out I/O8 ===<br />
The NT module for LOCON 200-Out I/O8 is a power supply that must be used for a configuration level step of more than 8 LOCON 200-Out I/O8 expansion modules.<br />
The NT module must be inserted immediately after the LOCON 200 basic unit. Nothing can be connected to the NT module itself. The voltage supply of the NT module takes place via the 24V/DC of the LOCON 200 basic unit. The voltage supply of the then following LOCON 200-Out I/O8 expansion modules is adopted by the NT module<br />
<br />
== Weblinks ==<br />
* [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/LOCON%20200/English/LOCON_200-e.pdf Manual for LOCON 200] (PDF-file)<br />
* [https://www.deutschmann.de/downloads/Support/Profibus/L200.GSD GSD-file for LOCON 200-PB]<br />
* [https://www.deutschmann.de/downloads/Support/S7/Nockenschaltwerk_CamSwitch/Nsw_v2_e.zip S7-example project] (ZIP-file)<br />
* Manual [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/DIVERS/Kommunikationsprofil/Kommunikationsprofil%20englisch/komm_profil_e.pdf Communication profile for Deutschmann cam controls] (PDF-file)<br />
* Manual [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/NSW%20mit%20Feldbus-CamControlWithFieldbusConnection/English/CamControlsWithFieldbusConnection.pdf Cam controls with fieldbus connection] (PDF-file)</div>Reithhttps://wiki.deutschmann.de/index.php?title=LOCON_100_(English)&diff=3444LOCON 100 (English)2019-08-27T12:53:31Z<p>Reith: /* Programming */</p>
<hr />
<div>[[Datei:LOCON 100.jpg|thumb|LOCON 100 and extension module LOCON 100-Out I/O32]]<br />
== Configuration ==<br />
By factory setting '''all''' LOCON 100 cam controls are configured as follows:<br />
*Outputs: '''16'''<br />
*Encoder type: '''SSI Singleturn'''<br />
*Real encoder resolution: '''4096'''<br />
*Virtual encoder resolution: '''4096'''<br />
*Idle time: '''Bitwise'''<br />
This by default configuration can be changed by using [[TERM 6 (English)|TERM 6]] or the software [[WINLOC 32 (English)|WINLOC 32]].<br />
<br />
== Programming ==<br />
LOCON 100 can be programmed by TERM 6 or [[TERM 24 (English)|TERM 24]] or the software WINLOC 32. The PROFIBUS-Version can be programmed also via PROFIBUS. The Modbus-version can by programmed via Modbus.<br />
<br />
== device versions ==<br />
=== LOCON 100 ===<br />
LOCON 100 features a serial RS232-interface and a RS485-([[DICNET (English)|DICNET]]) interface, the needed setting is made through the corresponding rotary coding switches ''High'' und ''Low'', located at the bottom side of the device.<br />
{| class="wikitable"<br />
|+Switch position<br />
|-<br />
! High !! Low !! Meaning<br />
|-<br />
| D || DICNET-Address || DICNET-Operation, Bus Termination inactive<br />
|-<br />
| E || DICNET-Address || DICNET-Operation, Bus Termination active<br />
|-<br />
| F || F || RS232-Operation<br />
|}<br />
'''Only''' the DICNET-Addresses '''0 ... 15''' (decimal) are supported (right rotary coding switch ''Low'' = DICNET-Address). Examples:<br />
{| class="wikitable"<br />
|+Switch Position<br />
|-<br />
! High !! Low !! Meaning<br />
|-<br />
| D || 3 || bus termination inactive, DICNET-Address '''3'''<br />
|-<br />
| E || C || bus termination active, DICNET-Address '''12'''<br />
|}<br />
'''Note:''' The setting via the rotary coding switches is done in ''hexadecimal''.<br />
<br />
=== LOCON 100-PB (PROFIBUS) ===<br />
LOCON 100-PB (PROFIBUS) is '''always''' PROFIBUS-Slave and features a serial RS232-interface and a PROFIBUS-Interface, instead of the RS485-(DICNET) Interface, the needed setting is made through the corresponding rotary coding switches ''High'' und ''Low'', located at the bottom side of the device.<br />
<br />
{| class="wikitable"<br />
|+Switch Position<br />
|-<br />
! High !! Low !! Meaning<br />
|-<br />
| 0 || 0 || PROFIBUS-operation, external address assignment <br />
|-<br />
| 0 || 1 || PROFIBUS-operation, Address 1<br />
|-<br />
|colspan="3" align="center"| …<br />
|-<br />
| 7 || D || PROFIBUS-operation, Address 125<br />
|-<br />
| 7 || E || PROFIBUS-operation, external address assignment <br />
|-<br />
| F || F || RS232-operation<br />
|}<br />
'''Note:''' The setting via the rotary coding switches is done in ''hexadecimal''.<br /><br />
In LOCON 100-PB two modes are selectable through WINLOC32 via the PROFIBUS-Interface.<br />
* '''S7-Modus''' (ex-works condition): For an operation at a Simatic S7 and for use of the [[Data component simulator]].<br />
* '''Communication Profile Mode''': For the Operation via the [[#Weblinks|Communication Profile for Deutschmann cam controls]].<br />
The PROFIBUS-Address (Slave-ID) is set by factory Setting on 126 (decimal). <br />
If the rotary coding switch is on position "'''00'''" und "'''7E'''" then any desired address can be assigned either through WINLOC32 or the PROFIBUS-Master.<br />
The [[#Weblinks|'''GSD-file''' (L100.GSD)]] and a [[#Weblinks|'''S7-example project''']] are available for download on our homepage.<br />
Further information regarding LOCON 100-PB can be found in the manual [[#Weblinks|Cam Controls with Fieldbus-Connection]].<br />
<br />
=== LOCON 100-MB (Modbus) ===<br />
LOCON 100-MB (Modbus) is '''always''' a Modbus-RTU-Slave and is '''only''' available in the '''2-core cable-version'''. LOCON 100-MB features a RS232-Standard-Interface as well as a RS232-(Modbus-RTU) Interface and a RS485-(Modbus-RTU) Interface, which can be changed by adjusting the rotary coding switch ''High'' located at the bottom side of the device.<br />
{| class="wikitable"<br />
|+Switch position<br />
|-<br />
! High !! Low !! Meaning<br />
|-<br />
| C || x || RS232-Modbus (X = ModbusSlave-ID)<br />
|-<br />
| D || x || RS485-Modbus without bus termination (x = Modbus-Slave-ID)<br />
|-<br />
| E || x || RS485-Modbus with activated bus termination (x = Modbus-Slave-ID)<br />
|-<br />
| F || x || RS232-Standard Interface<br />
|}<br />
'''Note:''' '''Only''' Modbus-Addresses '''1 ... 15''' (decimal) are supported (right rotary coding switch ''Low'' = ID). The Broadcast address '''0''' is '''not''' supported. The Setting via the rotary coding switch is done in ''hexadecimal''.<br /><br />
The following Modbus-RTU-commands are supported by the device: <br />
{| class="wikitable"<br />
|+Modbus-RTU-commands<br />
|-<br />
! command !! meaning<br />
|-<br />
| 03 || (0x03) Read Holding Registers <br />
|-<br />
| 16 || (0x10) Preset Multiple Regs<br />
|}<br />
The transmission baud rate is '''19200 Baud'''; '''No Parity'''. The manual [[#Weblinks|LOCON 100-MB Communication with ModScan32]] describes how cams are set via a Modbus master. Further information regarding LOCON 100-MB can be found in chapter 8 ''LOCON 100 with Modbus'' of the [[#Weblinks|Manual for LOCON 100]].<br />
<br />
=== LOCON 100-Out I/O32 (Extension module) ===<br />
LOCON 100-Out I/O32 is an '''extension module''' and contains 32 I/Os. With this extension module the basic device LOCON 100 resp. (-PB)) is expanded to a total of 48 I/Os (incl. 16 I/Os of LOCON 100 bzw. (-PB)). LOCON 100-Out I/O32 does '''not''' contain its own processor. Therefore, the switching accuracy (cycle time) depends on the LOCON 100 bzw. (-PB)).<br />
<br />
== Weblinks ==<br />
*[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/LOCON%20100/English/LOCON_100-e.pdf Manual for LOCON 100] (PDF-file)<br />
*[https://www.deutschmann.de/downloads/Support/Profibus/L100.GSD GSD-file for LOCON 100-PB]<br />
*[https://www.deutschmann.de/downloads/Support/S7/Nockenschaltwerk_CamSwitch/Nsw_v2_e.zip S7-example project] (ZIP-file)<br />
*Manual [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/DIVERS/Kommunikationsprofil/Kommunikationsprofil%20englisch/komm_profil_e.pdf Communication profile for Deutschmann cam controls] (PDF-file)<br />
*Manual [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/NSW%20mit%20Feldbus-CamControlWithFieldbusConnection/English/CamControlsWithFieldbusConnection.pdf Cam controls with fieldbus connection] (PDF-file)<br />
*Manual [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/LOCON%20100/German/LOCON100_MB.pdf LOCON 100-MB Communication with ModSca32] (PDF-file)</div>Reithhttps://wiki.deutschmann.de/index.php?title=ROTARNOCK_4_(English)&diff=3443ROTARNOCK 4 (English)2019-08-27T12:47:25Z<p>Reith: /* Device replacement */</p>
<hr />
<div>== Device replacement ==<br />
ROTARNOCK 4 can be replaced with a ROTARNOCK 100. You find all needed information on the site [[Device_replacement_ROTARNOCK_1,_2,_3_and_4_(English)|Device replacement ROTARNOCK 1, 2, 3 and 4]].<br />
<br />
== Weblinks ==<br />
[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/ROTARNOCK1-4,MT,PB/English/Rotarnock_e.pdf Manual for ROTARNOCK 4] (PDF-file)</div>Reithhttps://wiki.deutschmann.de/index.php?title=ROTARNOCK_3_(English)&diff=3442ROTARNOCK 3 (English)2019-08-27T12:46:48Z<p>Reith: /* Device replacement */</p>
<hr />
<div>== Device replacement ==<br />
ROTARNOCK 3 can be replaced with a ROTARNOCK 100. You find all needed information on <br />
[[Device_replacement_ROTARNOCK_1,_2,_3_and_4_(English)|Device replacement ROTARNOCK 1, 2, 3 and 4]].<br />
<br />
== Weblinks ==<br />
[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/ROTARNOCK1-4,MT,PB/English/Rotarnock_e.pdf Manual for ROTARNOCK 3] (PDF-file)</div>Reithhttps://wiki.deutschmann.de/index.php?title=ROTARNOCK_2_(English)&diff=3441ROTARNOCK 2 (English)2019-08-27T12:46:22Z<p>Reith: /* Device replacement */</p>
<hr />
<div>== Device replacement ==<br />
ROTARNOCK 2 can be replaced with a ROTARNOCK 100. You find all needed information on the site <br />
[[Device_replacement_ROTARNOCK_1,_2,_3_and_4_(English)|Device replacement ROTARNOCK 1, 2, 3 and 4]].<br />
<br />
== Weblinks ==<br />
[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/ROTARNOCK1-4,MT,PB/English/Rotarnock_e.pdf Manual for ROTARNOCK 2] (PDF-file)</div>Reithhttps://wiki.deutschmann.de/index.php?title=ROTARNOCK_1_(English)&diff=3440ROTARNOCK 1 (English)2019-08-27T12:45:49Z<p>Reith: </p>
<hr />
<div>== Device replacement ==<br />
ROTARNOCK 1 can be replaced with a ROTARNOCK 100. You find all needed information on the site <br />
[[Device_replacement_ROTARNOCK_1,_2,_3_and_4_(English)|Device replacement ROTARNOCK 1, 2, 3 and 4]].<br />
== Weblinks ==<br />
[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/ROTARNOCK1-4,MT,PB/English/Rotarnock_e.pdf Manual for ROTARNOCK 1] (PDF-file)</div>Reithhttps://wiki.deutschmann.de/index.php?title=Device_replacement_ROTARNOCK_1,_2,_3_and_4_(English)&diff=3439Device replacement ROTARNOCK 1, 2, 3 and 4 (English)2019-08-27T12:28:11Z<p>Reith: /* Programming - zero offset - program selection */</p>
<hr />
<div>Rotarnock 1,2,3 and 4 as well as the corresponding PROFIBUS variants were replaced by [[ROTARNOCK 100 (English)|ROTARNOCK 100]]. This is available with or without PROFIBUS. The following information and components are needed to guarantee a quick exchange and programming of the new device:<br />
# The serial number or the article number (Vxxxx) of the old device have to be known to ensure that an appropriate new device can be offered.<br />
# If a TERM 6 or a TERM 24 is already in use, we also need to know the serial number of this device to check the compatibility with the new device. '''Note''': TERM 5 is '''not''' compatible with ROTARNOCK 100!<br />
# To read-out the old device and possibly for the configuration and programming of the new device with the WINLOC32-Basis-or comfort-version, a corresponding [[Programming cable]] is needed. '''Note''': Whether the programming cable can also be used for a necessary read-out of the old device has to be tested in each case!<br />
# A TERM 6 or the WINLOC32-Basis or comfort-version is needed for the configuration of the new device.<br />
# There has to be a real COM-Port on the PC for the configuration and programming of the new device with WINLOC32. If there is no real COM-Port on the PC, you need a USB-RS232-converter.<br />
=== Programming - zero offset - program selection ===<br />
# The programming of the new device can be performed with TERM 6, TERM 24 or with the WINLOC32-Basis or comfort-version. With the PROFIBUS version you can also program via PROFIBUS.<br />
# The zero offset can be performed with TERM 6, TERM 24 or with the WINLOC32-comfort-version. With the PROFIBUS version you can also program via PROFIBUS.<br />
# The program selection can be done with TERM 6, TERM 24 or via the external program selection. With the PROFIBUS version you can also program via PROFIBUS.<br />
'''For a corresponding offer please let us know the serial number or the article number (Vxxxx) of the old device and, if used, the serial-no. of TERM 6 resp. TERM 24.'''</div>Reithhttps://wiki.deutschmann.de/index.php?title=Device_replacement_ROTARNOCK_1,_2,_3_and_4_(English)&diff=3438Device replacement ROTARNOCK 1, 2, 3 and 4 (English)2019-08-27T12:13:18Z<p>Reith: /* Programming - zero offset - program selection */</p>
<hr />
<div>Rotarnock 1,2,3 and 4 as well as the corresponding PROFIBUS variants were replaced by [[ROTARNOCK 100 (English)|ROTARNOCK 100]]. This is available with or without PROFIBUS. The following information and components are needed to guarantee a quick exchange and programming of the new device:<br />
# The serial number or the article number (Vxxxx) of the old device have to be known to ensure that an appropriate new device can be offered.<br />
# If a TERM 6 or a TERM 24 is already in use, we also need to know the serial number of this device to check the compatibility with the new device. '''Note''': TERM 5 is '''not''' compatible with ROTARNOCK 100!<br />
# To read-out the old device and possibly for the configuration and programming of the new device with the WINLOC32-Basis-or comfort-version, a corresponding [[Programming cable]] is needed. '''Note''': Whether the programming cable can also be used for a necessary read-out of the old device has to be tested in each case!<br />
# A TERM 6 or the WINLOC32-Basis or comfort-version is needed for the configuration of the new device.<br />
# There has to be a real COM-Port on the PC for the configuration and programming of the new device with WINLOC32. If there is no real COM-Port on the PC, you need a USB-RS232-converter.<br />
=== Programming - zero offset - program selection ===<br />
# The programming of the new device can be performed with a TERM 6, a TERM 24 or with the WINLOC32-Basis or comfort-version. With the PROFIBUS version you can also program via PROFIBUS.<br />
# The zero offset can be performed with a TERM 6, a TERM 24 or with the WINLOC32-comfort-version. With the PROFIBUS version you can also program via PROFIBUS.<br />
# The program selection can be done with a TERM 6, a TERM 24 or via the external program selection. With the PROFIBUS version you can also program via PROFIBUS.<br />
'''For a corresponding offer please let us know the serial number or the article number (Vxxxx) of the old device and, if used, the serial-no. of TERM 6 resp. TERM 24.'''</div>Reithhttps://wiki.deutschmann.de/index.php?title=Device_replacement_ROTARNOCK_1,_2,_3_and_4_(English)&diff=3437Device replacement ROTARNOCK 1, 2, 3 and 4 (English)2019-08-27T11:56:52Z<p>Reith: </p>
<hr />
<div>Rotarnock 1,2,3 and 4 as well as the corresponding PROFIBUS variants were replaced by [[ROTARNOCK 100 (English)|ROTARNOCK 100]]. This is available with or without PROFIBUS. The following information and components are needed to guarantee a quick exchange and programming of the new device:<br />
# The serial number or the article number (Vxxxx) of the old device have to be known to ensure that an appropriate new device can be offered.<br />
# If a TERM 6 or a TERM 24 is already in use, we also need to know the serial number of this device to check the compatibility with the new device. '''Note''': TERM 5 is '''not''' compatible with ROTARNOCK 100!<br />
# To read-out the old device and possibly for the configuration and programming of the new device with the WINLOC32-Basis-or comfort-version, a corresponding [[Programming cable]] is needed. '''Note''': Whether the programming cable can also be used for a necessary read-out of the old device has to be tested in each case!<br />
# A TERM 6 or the WINLOC32-Basis or comfort-version is needed for the configuration of the new device.<br />
# There has to be a real COM-Port on the PC for the configuration and programming of the new device with WINLOC32. If there is no real COM-Port on the PC, you need a USB-RS232-converter.<br />
=== Programming - zero offset - program selection ===<br />
# The programming of the new device can be performed with a TERM 6, a TERM 24 or with the WINLOC32-Basis or comfort-version. With the PROFIBUS version you can also program via the PROFIBUS.<br />
# The zero offset can be performed with a TERM 6, a TERM 24 or with the WINLOC32-comfort-version. With the PROFIBUS version you can also program via the PROFIBUS.<br />
# The program selection can be done with a TERM 6, a TERM 24 or via the external program selection. With the PROFIBUS version you can also program via the PROFIBUS.<br />
'''For a corresponding offer please let us know the serial number or the article number (Vxxxx) of the old device and, if used, the serial-no. of TERM 6 resp. TERM 24.'''</div>Reithhttps://wiki.deutschmann.de/index.php?title=Ger%C3%A4teaustausch_ROTARNOCK_-_PROFIBUS&diff=3359Geräteaustausch ROTARNOCK - PROFIBUS2017-12-18T11:59:09Z<p>Reith: /* Gerätekonfiguration */</p>
<hr />
<div>'''ROTARNOCK 1-PB''' und '''ROTARNOCK 2-PB''' können durch ein '''ROTARNOCK 100-PB''' ersetzt werden. Da aber ein 1:1 Austausch nicht möglich ist, müssen folgende Punkte dabei beachtet werden:<br />
<br />
==Gerätekonfiguration== <br />
Die Konfiguration muss mit der Software [[WINLOC 32]]-Basis-oder Komfortversion durchgeführt werden. Dafür wird ein entsprechendes [[Programmierkabel]] benötigt. '''Hinweis:''' Ob dieses Programmierkabel auch für ein ggf. benötigtes Auslesen des Altgerätes verwendet werden kann, muss im jeweiligen Fall geprüft werden. '''Achtung:''' Für die Konfiguration muss ein echter COM-Port am PC vorhanden sein. Wenn kein echter COM-Port mehr am PC vorhanden ist, wird ein [[USB-RS232-Konverter]] benötigt.<br />
*'''Virtuelle Geberauflösung:''' Damit die Nockenwerte der vorhandenen elektronischen Nockensteuerung im neuen Datenbaustein wiederverwendet werden können, muss die virtuelle Geberauflösung auf den Wert der vorhandenen elektronischen Nockensteuerung geändert werden.<br />
*'''Art der Totzeitkompensation:''' Damit die Totzeiten der vorhandenen elektronischen Nockensteuerung im neuen Datenbaustein wiederverwendet werden können, muss die Art der Totzeit (Bitweise; Blockweise; ...) auf die von der vorhandenen elektronischen Nockensteuerung verwendeten Art geändert werden.<br />
*'''PROFIBUS-Slave-ID:''' Die gewünschte PROFIBUS-Slave-ID muss mit der Software WINLOC 32 eingestellt werden, wenn diese nicht über den PROFIBUS-Master zugewiesen werden soll. Im Auslieferungszustand ist die PROFIBUS-Slave-ID auf 126 eingestellt.<br />
*'''Betriebs-Modi:''' In Verbindung mit einem PROFIBUS-Master muss dieser auf '''S7-Mode''' eingestellt sein. Im Auslieferungszustand ist der S7-Mode bereits eingestellt. <br />
*'''Logik:''' Wenn im Altgerät die Logikfunktion verwendet wird, muss diese im ROTARNOCK 100-PB noch freigeschaltet werden. Dafür wird ein Freischaltcode benötigt, der kostenpflichtig ist. '''Achtung:''' Der Freischaltcode für die Logikfunktion ist an die Serien-Nr. gebunden und kann daher nicht für andere elektronische Nockensteuerungen verwendet werden.<br />
<br />
==SPS Projekt==<br />
*'''GSD-Datei:''' Um das ROTARNOCK 100-PB in das Projekt einbinden zu können, muss die GSD-Datei [[#Weblinks|'''(R100.GSD)''']] in die Steuerung geladen werden.<br />
*'''AWL-Datei:''' Die im Projekt befindliche AWL-Datei, die im Datenbaustein abgebildet wird, muss durch eine für ROTARNOCK 100-PB passende AWL-Datei ersetzt werden. Dazu muss der [[Datenbausteingenerator]]2 verwendet werden.<br />
<br />
==Weblinks==<br />
*[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/ROTARNOCK%20100/German/ROTARNOCK_100.pdf Handbuch für das ROTARNOCK 100] (PDF-Datei)<br />
*[https://www.deutschmann.de/downloads/Support/Profibus/R100.GSD GSD-Datei für das ROTARNOCK 100-PB] <br />
*Handbuch [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/NSW%20mit%20Feldbus-CamControlWithFieldbusConnection/German/NSWmitFeldbus.pdf Nockensteuerungen mit Feldbusanbindung] (PDF-Datei)<br />
*Handbuch [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/L100,%20200,%20R80,%20100%20mit%20Feldbusanbindung-WithFieldbusConnection/German/L-R%20mit%20Feldbus_d.pdf ROTARNOCK 100 mit Feldbusanbindung] (PDF-Datei)</div>Reithhttps://wiki.deutschmann.de/index.php?title=Device_replacement_ROTARNOCK_-_PROFIBUS_(English)&diff=3358Device replacement ROTARNOCK - PROFIBUS (English)2017-12-18T10:30:54Z<p>Reith: /* Device Configuration */</p>
<hr />
<div>'''ROTARNOCK 1-PB''' und '''ROTARNOCK 2-PB''' can be replaced by '''ROTARNOCK 100-PB''' . As an 1:1 exchange is not possible, the following points have to be noted:<br />
<br />
==Device Configuration== <br />
The configuration has to be done with our software [[WINLOC 32 (English)|WINLOC 32]]-Basis-or Comfort version. Herefore is needed a corresponding [[Programming cable]]. '''Note:''' Whether the programming cable can also be used for a necessary read-out of the old device has to be tested in each case! '''Attention:''' For the configuration, the PC is in need of a real COM-Port. If there is no real COM-Port at the PC, then an [[USB-to-RS232 converter]] has to be used.<br />
*'''Virtual encoder resolution:''' If the cam values of the existing electronic cam control should be reused in the new data block, the virtual encoder resolution must be changed to the value of the existing electronic cam control.<br />
*'''Type of idle time compensation:''' If the idle time of the existing electronic cam control should be reused in the new data block, then the type of idle time (Bitwise; Blockwise; ...) has to be set accordingly.<br />
*'''PROFIBUS-Slave-ID:''' The desired PROFIBUS-Slave-ID has to be set via WINLOC 32 software, if this is not to be assigned via the PROFIBUS master. The PROFIBUS-Slave-ID is set to 126 at delivery state.<br />
*'''Operation modes:''' In conjunction with a PROFIBUS-Master this must be set to '''S7-mode'''. This S7-mode is already set at delivery state. <br />
*'''Logic function:''' If the logic function is used in the old device then this function has to be unlocked for ROTARNOCK 100-PB. Therefore a chargeable release code is needed. '''Attention:''' This release code is bounded to the serial-no. and can not be used for other cam controls.<br />
<br />
==SPS Project==<br />
*'''GSD-file:''' In order to integrate ROTARNOCK 100-PB into a project, the GSD-file [[#Weblinks|'''(R100.GSD)''']] has to be loaded in the cam control.<br />
*'''AWL-file:''' The AWL-file contained in the project which is pictured in the data block has to be replaced by an AWL-file fitting for ROTARNOCK 100-PB. Herefore has to be used the [[Data component generator]]2.<br />
<br />
==Weblinks==<br />
*[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/ROTARNOCK%20100/German/ROTARNOCK_100.pdf Handbuch für das ROTARNOCK 100] (PDF-Datei)<br />
*[https://www.deutschmann.de/downloads/Support/Profibus/R100.GSD GSD-Datei für das ROTARNOCK 100-PB] <br />
*Handbuch [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/NSW%20mit%20Feldbus-CamControlWithFieldbusConnection/German/NSWmitFeldbus.pdf Nockensteuerungen mit Feldbusanbindung] (PDF-Datei)<br />
*Handbuch [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/L100,%20200,%20R80,%20100%20mit%20Feldbusanbindung-WithFieldbusConnection/German/L-R%20mit%20Feldbus_d.pdf ROTARNOCK 100 mit Feldbusanbindung] (PDF-Datei)</div>Reithhttps://wiki.deutschmann.de/index.php?title=Device_replacement_ROTARNOCK_-_PROFIBUS_(English)&diff=3357Device replacement ROTARNOCK - PROFIBUS (English)2017-12-18T10:30:15Z<p>Reith: /* Device Configuration */</p>
<hr />
<div>'''ROTARNOCK 1-PB''' und '''ROTARNOCK 2-PB''' can be replaced by '''ROTARNOCK 100-PB''' . As an 1:1 exchange is not possible, the following points have to be noted:<br />
<br />
==Device Configuration== <br />
The configuration has to be done with our software [[WINLOC 32 (English)|WINLOC 32]]-Basis-or Comfortversion. Herefore is needed a corresponding [[Programming cable]]. '''Note:''' Whether the programming cable can also be used for a necessary read-out of the old device has to be tested in each case! '''Attention:''' For the configuration, the PC is in need of a real COM-Port. If there is no real COM-Port at the PC, then an [[USB-to-RS232 converter]] has to be used.<br />
*'''Virtual encoder resolution:''' If the cam values of the existing electronic cam control should be reused in the new data block, the virtual encoder resolution must be changed to the value of the existing electronic cam control.<br />
*'''Type of idle time compensation:''' If the idle time of the existing electronic cam control should be reused in the new data block, then the type of idle time (Bitwise; Blockwise; ...) has to be set accordingly.<br />
*'''PROFIBUS-Slave-ID:''' The desired PROFIBUS-Slave-ID has to be set via WINLOC 32 software, if this is not to be assigned via the PROFIBUS master. The PROFIBUS-Slave-ID is set to 126 at delivery state.<br />
*'''Operation modes:''' In conjunction with a PROFIBUS-Master this must be set to '''S7-mode'''. This S7-mode is already set at delivery state. <br />
*'''Logic function:''' If the logic function is used in the old device then this function has to be unlocked for ROTARNOCK 100-PB. Therefore a chargeable release code is needed. '''Attention:''' This release code is bounded to the serial-no. and can not be used for other cam controls.<br />
<br />
==SPS Project==<br />
*'''GSD-file:''' In order to integrate ROTARNOCK 100-PB into a project, the GSD-file [[#Weblinks|'''(R100.GSD)''']] has to be loaded in the cam control.<br />
*'''AWL-file:''' The AWL-file contained in the project which is pictured in the data block has to be replaced by an AWL-file fitting for ROTARNOCK 100-PB. Herefore has to be used the [[Data component generator]]2.<br />
<br />
==Weblinks==<br />
*[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/ROTARNOCK%20100/German/ROTARNOCK_100.pdf Handbuch für das ROTARNOCK 100] (PDF-Datei)<br />
*[https://www.deutschmann.de/downloads/Support/Profibus/R100.GSD GSD-Datei für das ROTARNOCK 100-PB] <br />
*Handbuch [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/NSW%20mit%20Feldbus-CamControlWithFieldbusConnection/German/NSWmitFeldbus.pdf Nockensteuerungen mit Feldbusanbindung] (PDF-Datei)<br />
*Handbuch [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/L100,%20200,%20R80,%20100%20mit%20Feldbusanbindung-WithFieldbusConnection/German/L-R%20mit%20Feldbus_d.pdf ROTARNOCK 100 mit Feldbusanbindung] (PDF-Datei)</div>Reithhttps://wiki.deutschmann.de/index.php?title=Device_replacement_ROTARNOCK_-_PROFIBUS_(English)&diff=3356Device replacement ROTARNOCK - PROFIBUS (English)2017-12-18T10:18:31Z<p>Reith: /* SPS Projekt */</p>
<hr />
<div>'''ROTARNOCK 1-PB''' und '''ROTARNOCK 2-PB''' can be replaced by '''ROTARNOCK 100-PB''' . As an 1:1 exchange is not possible, the following points have to be noted:<br />
<br />
==Device Configuration== <br />
The configuration has to be done with our software [[WINLOC 32 (English)|WINLOC 32]]-Basis-or Comfortversion. Herefore is needed a corresponding [[Programming cable]]. '''Note:''' Whether the programming cable can also be used for a necessary read-out of the old device has to be tested in each case! '''Attention:''' For the configuration, the PC is in need of a real COM-Port. If there is no real COM-Port at the PC, then a [[USB-to-RS232 converter]] has to be used.<br />
*'''Virtual encoder resolution:''' If the cam values of the existing electronic cam control should be reused in the new data block, the virtual encoder resolution must be changed to the value of the existing electronic cam control.<br />
*'''Type of idle time compensation:''' If the idle times of the existing electronic cam control should be reused in the new data block, then the type of idle time (Bitwise; Blockwise; ...) has to be set accordingly.<br />
*'''PROFIBUS-Slave-ID:''' The desired PROFIBUS-Slave-ID has to be set via WINLOC 32 software, if this if this is not to be assigned via the PROFIBUS master. The PROFIBUS-Slave-ID is set to 126 at delivery state.<br />
*'''Operation modes:''' In conjunction with a PROFIBUS-Master this must be set to '''S7-mode'''. This S7-mode is already set at delivery state. <br />
*'''Logic function:''' If the logic function is used in the old device then this function has to be unlocked for ROTARNOCK 100-PB. Therefore a chargeable release code is needed. '''Attention:''' This release code is bounded to the serial-no. and can not be used for other cam controls.<br />
<br />
==SPS Project==<br />
*'''GSD-file:''' In order to integrate ROTARNOCK 100-PB into a project, the GSD-file [[#Weblinks|'''(R100.GSD)''']] has to be loaded in the cam control.<br />
*'''AWL-file:''' The AWL-file contained in the project which is pictured in the data block has to be replaced by an AWL-file fitting for ROTARNOCK 100-PB. Herefore has to be used the [[Data component generator]]2.<br />
<br />
==Weblinks==<br />
*[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/ROTARNOCK%20100/German/ROTARNOCK_100.pdf Handbuch für das ROTARNOCK 100] (PDF-Datei)<br />
*[https://www.deutschmann.de/downloads/Support/Profibus/R100.GSD GSD-Datei für das ROTARNOCK 100-PB] <br />
*Handbuch [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/NSW%20mit%20Feldbus-CamControlWithFieldbusConnection/German/NSWmitFeldbus.pdf Nockensteuerungen mit Feldbusanbindung] (PDF-Datei)<br />
*Handbuch [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/L100,%20200,%20R80,%20100%20mit%20Feldbusanbindung-WithFieldbusConnection/German/L-R%20mit%20Feldbus_d.pdf ROTARNOCK 100 mit Feldbusanbindung] (PDF-Datei)</div>Reithhttps://wiki.deutschmann.de/index.php?title=Device_replacement_ROTARNOCK_-_PROFIBUS_(English)&diff=3355Device replacement ROTARNOCK - PROFIBUS (English)2017-12-18T10:02:28Z<p>Reith: /* SPS Projekt */</p>
<hr />
<div>'''ROTARNOCK 1-PB''' und '''ROTARNOCK 2-PB''' can be replaced by '''ROTARNOCK 100-PB''' . As an 1:1 exchange is not possible, the following points have to be noted:<br />
<br />
==Device Configuration== <br />
The configuration has to be done with our software [[WINLOC 32 (English)|WINLOC 32]]-Basis-or Comfortversion. Herefore is needed a corresponding [[Programming cable]]. '''Note:''' Whether the programming cable can also be used for a necessary read-out of the old device has to be tested in each case! '''Attention:''' For the configuration, the PC is in need of a real COM-Port. If there is no real COM-Port at the PC, then a [[USB-to-RS232 converter]] has to be used.<br />
*'''Virtual encoder resolution:''' If the cam values of the existing electronic cam control should be reused in the new data block, the virtual encoder resolution must be changed to the value of the existing electronic cam control.<br />
*'''Type of idle time compensation:''' If the idle times of the existing electronic cam control should be reused in the new data block, then the type of idle time (Bitwise; Blockwise; ...) has to be set accordingly.<br />
*'''PROFIBUS-Slave-ID:''' The desired PROFIBUS-Slave-ID has to be set via WINLOC 32 software, if this if this is not to be assigned via the PROFIBUS master. The PROFIBUS-Slave-ID is set to 126 at delivery state.<br />
*'''Operation modes:''' In conjunction with a PROFIBUS-Master this must be set to '''S7-mode'''. This S7-mode is already set at delivery state. <br />
*'''Logic function:''' If the logic function is used in the old device then this function has to be unlocked for ROTARNOCK 100-PB. Therefore a chargeable release code is needed. '''Attention:''' This release code is bounded to the serial-no. and can not be used for other cam controls.<br />
<br />
==SPS Projekt==<br />
*'''GSD-file:''' In order to integrate ROTARNOCK 100-PB into a project, the GSD-file [[#Weblinks|'''(R100.GSD)''']] has to be loaded in the cam control.<br />
*'''AWL-file:''' Die im Projekt befindliche AWL-Datei, die im Datenbaustein abgebildet wird, muss durch eine für ROTARNOCK 100-PB passende AWL-Datei ersetzt werden. Dazu muss der [[Datenbausteingenerator]]2 verwendet werden.<br />
<br />
==Weblinks==<br />
*[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/ROTARNOCK%20100/German/ROTARNOCK_100.pdf Handbuch für das ROTARNOCK 100] (PDF-Datei)<br />
*[https://www.deutschmann.de/downloads/Support/Profibus/R100.GSD GSD-Datei für das ROTARNOCK 100-PB] <br />
*Handbuch [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/NSW%20mit%20Feldbus-CamControlWithFieldbusConnection/German/NSWmitFeldbus.pdf Nockensteuerungen mit Feldbusanbindung] (PDF-Datei)<br />
*Handbuch [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/L100,%20200,%20R80,%20100%20mit%20Feldbusanbindung-WithFieldbusConnection/German/L-R%20mit%20Feldbus_d.pdf ROTARNOCK 100 mit Feldbusanbindung] (PDF-Datei)</div>Reithhttps://wiki.deutschmann.de/index.php?title=Device_replacement_ROTARNOCK_-_PROFIBUS_(English)&diff=3354Device replacement ROTARNOCK - PROFIBUS (English)2017-12-18T10:00:13Z<p>Reith: /* Device Configuration */</p>
<hr />
<div>'''ROTARNOCK 1-PB''' und '''ROTARNOCK 2-PB''' can be replaced by '''ROTARNOCK 100-PB''' . As an 1:1 exchange is not possible, the following points have to be noted:<br />
<br />
==Device Configuration== <br />
The configuration has to be done with our software [[WINLOC 32 (English)|WINLOC 32]]-Basis-or Comfortversion. Herefore is needed a corresponding [[Programming cable]]. '''Note:''' Whether the programming cable can also be used for a necessary read-out of the old device has to be tested in each case! '''Attention:''' For the configuration, the PC is in need of a real COM-Port. If there is no real COM-Port at the PC, then a [[USB-to-RS232 converter]] has to be used.<br />
*'''Virtual encoder resolution:''' If the cam values of the existing electronic cam control should be reused in the new data block, the virtual encoder resolution must be changed to the value of the existing electronic cam control.<br />
*'''Type of idle time compensation:''' If the idle times of the existing electronic cam control should be reused in the new data block, then the type of idle time (Bitwise; Blockwise; ...) has to be set accordingly.<br />
*'''PROFIBUS-Slave-ID:''' The desired PROFIBUS-Slave-ID has to be set via WINLOC 32 software, if this if this is not to be assigned via the PROFIBUS master. The PROFIBUS-Slave-ID is set to 126 at delivery state.<br />
*'''Operation modes:''' In conjunction with a PROFIBUS-Master this must be set to '''S7-mode'''. This S7-mode is already set at delivery state. <br />
*'''Logic function:''' If the logic function is used in the old device then this function has to be unlocked for ROTARNOCK 100-PB. Therefore a chargeable release code is needed. '''Attention:''' This release code is bounded to the serial-no. and can not be used for other cam controls.<br />
<br />
==SPS Projekt==<br />
*'''GSD-Datei:''' Um das ROTARNOCK 100-PB in das Projekt einbinden zu können, muss die GSD-Datei [[#Weblinks|'''(R100.GSD)''']] in die Steuerung geladen werden.<br />
*'''AWL-Datei:''' Die im Projekt befindliche AWL-Datei, die im Datenbaustein abgebildet wird, muss durch eine für ROTARNOCK 100-PB passende AWL-Datei ersetzt werden. Dazu muss der [[Datenbausteingenerator]]2 verwendet werden.<br />
<br />
==Weblinks==<br />
*[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/ROTARNOCK%20100/German/ROTARNOCK_100.pdf Handbuch für das ROTARNOCK 100] (PDF-Datei)<br />
*[https://www.deutschmann.de/downloads/Support/Profibus/R100.GSD GSD-Datei für das ROTARNOCK 100-PB] <br />
*Handbuch [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/NSW%20mit%20Feldbus-CamControlWithFieldbusConnection/German/NSWmitFeldbus.pdf Nockensteuerungen mit Feldbusanbindung] (PDF-Datei)<br />
*Handbuch [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/L100,%20200,%20R80,%20100%20mit%20Feldbusanbindung-WithFieldbusConnection/German/L-R%20mit%20Feldbus_d.pdf ROTARNOCK 100 mit Feldbusanbindung] (PDF-Datei)</div>Reithhttps://wiki.deutschmann.de/index.php?title=Device_replacement_ROTARNOCK_1,_2,_3_and_4_(English)&diff=3353Device replacement ROTARNOCK 1, 2, 3 and 4 (English)2017-12-18T09:58:53Z<p>Reith: </p>
<hr />
<div>Rotarnock 1,2,3 and 4 as well as the corresponding PROFIBUS variants were replaced by [[ROTARNOCK 100 (English)|ROTARNOCK 100]]. This is available with or without PROFIBUS. The following information and components are needed to guarantee a quick exchange and programming of the new device:<br />
# The serial number or the article number (Vxxxx) of the old device have to be known to ensure that an appropriate new device can be offered.<br />
# If a TERM 6 oder a TERM 24 is already in use, we also need to know the serial number of this device to check the compatibility with the new device. '''Note''': TERM 5 is '''not''' compatible with ROTARNOCK 100!<br />
# To read-out the old device and possibly for the configuration and programming of the new device with the WINLOC32-Basis-or comfort-version, a corresponding [[Programming cable]] is needed. '''Note''': Whether the programming cable can also be used for a necessary read-out of the old device has to be tested in each case!<br />
# A TERM 6 or the WINLOC32-Basis or comfort-version is needed for the configuration of the new device.<br />
# There has to be a real COM-Port on the PC for the configuration and programming of the new device with WINLOC32. If there is no real COM-Port on the PC, you need a USB-RS232-converter.<br />
=== Programming - zero offset - program selection ===<br />
# The programming of the new device can be performed with a TERM 6, a TERM 24 or with the WINLOC32-Basis or comfort-version. With the PROFIBUS version you can also program via the PROFIBUS.<br />
# The zero offset can be performed with a TERM 6, a TERM 24 or with the WINLOC32-comfort-version. With the PROFIBUS version you can also program via the PROFIBUS.<br />
# The program selection can be done with a TERM 6, a TERM 24 or via the external program selection. With the PROFIBUS version you can also program via the PROFIBUS.<br />
'''For a corresponding offer please let us know the serial number or the article number (Vxxxx) of the old device and, if used, the serial-no. of TERM 6 resp. TERM 24.'''</div>Reithhttps://wiki.deutschmann.de/index.php?title=Device_replacement_ROTARNOCK_-_PROFIBUS_(English)&diff=3352Device replacement ROTARNOCK - PROFIBUS (English)2017-12-18T09:56:18Z<p>Reith: /* Device Configuration */</p>
<hr />
<div>'''ROTARNOCK 1-PB''' und '''ROTARNOCK 2-PB''' can be replaced by '''ROTARNOCK 100-PB''' . As an 1:1 exchange is not possible, the following points have to be noted:<br />
<br />
==Device Configuration== <br />
The configuration has to be done with our software [[WINLOC 32 (English)|WINLOC 32]]-Basis-or Comfortversion. Herefore is needed a corresponding [[Programming cable]]. '''Note:''' If this programming cable should be used for a needed read out of the old device then this has to be checked separately. '''Attention:''' For the configuration, the PC is in need of a real COM-Port. If there is no real COM-Port at the PC, then a [[USB-to-RS232 converter]] has to be used.<br />
*'''Virtual encoder resolution:''' If the cam values of the existing electronic cam control should be reused in the new data block, the virtual encoder resolution must be changed to the value of the existing electronic cam control.<br />
*'''Type of idle time compensation:''' If the idle times of the existing electronic cam control should be reused in the new data block, then the type of idle time (Bitwise; Blockwise; ...) has to be set accordingly.<br />
*'''PROFIBUS-Slave-ID:''' The desired PROFIBUS-Slave-ID has to be set via WINLOC 32 software, if this if this is not to be assigned via the PROFIBUS master. The PROFIBUS-Slave-ID is set to 126 at delivery state.<br />
*'''Operation modes:''' In conjunction with a PROFIBUS-Master this must be set to '''S7-mode'''. This S7-mode is already set at delivery state. <br />
*'''Logic function:''' If the logic function is used in the old device then this function has to be unlocked for ROTARNOCK 100-PB. Therefore a chargeable release code is needed. '''Attention:''' This release code is bounded to the serial-no. and can not be used for other cam controls.<br />
<br />
==SPS Projekt==<br />
*'''GSD-Datei:''' Um das ROTARNOCK 100-PB in das Projekt einbinden zu können, muss die GSD-Datei [[#Weblinks|'''(R100.GSD)''']] in die Steuerung geladen werden.<br />
*'''AWL-Datei:''' Die im Projekt befindliche AWL-Datei, die im Datenbaustein abgebildet wird, muss durch eine für ROTARNOCK 100-PB passende AWL-Datei ersetzt werden. Dazu muss der [[Datenbausteingenerator]]2 verwendet werden.<br />
<br />
==Weblinks==<br />
*[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/ROTARNOCK%20100/German/ROTARNOCK_100.pdf Handbuch für das ROTARNOCK 100] (PDF-Datei)<br />
*[https://www.deutschmann.de/downloads/Support/Profibus/R100.GSD GSD-Datei für das ROTARNOCK 100-PB] <br />
*Handbuch [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/NSW%20mit%20Feldbus-CamControlWithFieldbusConnection/German/NSWmitFeldbus.pdf Nockensteuerungen mit Feldbusanbindung] (PDF-Datei)<br />
*Handbuch [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/L100,%20200,%20R80,%20100%20mit%20Feldbusanbindung-WithFieldbusConnection/German/L-R%20mit%20Feldbus_d.pdf ROTARNOCK 100 mit Feldbusanbindung] (PDF-Datei)</div>Reithhttps://wiki.deutschmann.de/index.php?title=Device_replacement_ROTARNOCK_-_PROFIBUS_(English)&diff=3351Device replacement ROTARNOCK - PROFIBUS (English)2017-12-18T09:44:46Z<p>Reith: /* Device Configuration */</p>
<hr />
<div>'''ROTARNOCK 1-PB''' und '''ROTARNOCK 2-PB''' can be replaced by '''ROTARNOCK 100-PB''' . As an 1:1 exchange is not possible, the following points have to be noted:<br />
<br />
==Device Configuration== <br />
The configuration has to be done with our software [[WINLOC 32 (English)|WINLOC 32]]-Basis-or Comfortversion. Herefore is needed a corresponding [[Programming cable]]. '''Note:''' If this programming cable should be used for a needed read out of the old device then this has to be checked separately. '''Attention:''' For the configuration, the PC is in need of a real COM-Port. If there is no real COM-Port at the PC, then a [[USB-to-RS232 converter]] has to be used.<br />
*'''Virtual encoder resolution:''' If the cam values of the existing electronic cam control should be reused in the new data block, the virtual encoder resolution must be changed to the value of the existing electronic cam control.<br />
*'''Type of idle time compensation:''' Damit die Totzeiten der vorhandenen elektronischen Nockensteuerung im neuen Datenbaustein wiederverwendet werden können, muss die Art der Totzeit (Bitweise; Blockweise; ...) auf die von der vorhandenen elektronischen Nockensteuerung verwendeten Art geändert werden.<br />
*'''PROFIBUS-Slave-ID:''' Die gewünschte PROFIBUS-Slave-ID muss mit der Software WINLOC 32 eingestellt werden, wenn diese nicht über den PROFIBUS-Master zugewiesen werden soll. Im Auslieferungszustand ist die PROFIBUS-Slave-ID auf 126 eingestellt.<br />
*'''Operation modes:''' In conjunction with a PROFIBUS-Master this must be set to '''S7-mode''' This S7-mode is already set in the delivery state. <br />
*'''Logic function:''' If the logic function is used in the old device then this function has to be unlocked for ROTARNOCK 100-PB. Therefore a chargeable release code is needed. '''Attention:''' This release code is bounded to the serial-no. and can not be used for other cam controls.<br />
<br />
==SPS Projekt==<br />
*'''GSD-Datei:''' Um das ROTARNOCK 100-PB in das Projekt einbinden zu können, muss die GSD-Datei [[#Weblinks|'''(R100.GSD)''']] in die Steuerung geladen werden.<br />
*'''AWL-Datei:''' Die im Projekt befindliche AWL-Datei, die im Datenbaustein abgebildet wird, muss durch eine für ROTARNOCK 100-PB passende AWL-Datei ersetzt werden. Dazu muss der [[Datenbausteingenerator]]2 verwendet werden.<br />
<br />
==Weblinks==<br />
*[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/ROTARNOCK%20100/German/ROTARNOCK_100.pdf Handbuch für das ROTARNOCK 100] (PDF-Datei)<br />
*[https://www.deutschmann.de/downloads/Support/Profibus/R100.GSD GSD-Datei für das ROTARNOCK 100-PB] <br />
*Handbuch [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/NSW%20mit%20Feldbus-CamControlWithFieldbusConnection/German/NSWmitFeldbus.pdf Nockensteuerungen mit Feldbusanbindung] (PDF-Datei)<br />
*Handbuch [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/L100,%20200,%20R80,%20100%20mit%20Feldbusanbindung-WithFieldbusConnection/German/L-R%20mit%20Feldbus_d.pdf ROTARNOCK 100 mit Feldbusanbindung] (PDF-Datei)</div>Reithhttps://wiki.deutschmann.de/index.php?title=Device_replacement_ROTARNOCK_-_PROFIBUS_(English)&diff=3350Device replacement ROTARNOCK - PROFIBUS (English)2017-12-18T09:33:38Z<p>Reith: /* Device Configuration */</p>
<hr />
<div>'''ROTARNOCK 1-PB''' und '''ROTARNOCK 2-PB''' can be replaced by '''ROTARNOCK 100-PB''' . As an 1:1 exchange is not possible, the following points have to be noted:<br />
<br />
==Device Configuration== <br />
The configuration has to be done with our software [[WINLOC 32 (English)|WINLOC 32]]-Basis-or Comfortversion. Herefore is needed a corresponding [[Programming cable]]. '''Note:''' If this programming cable may be used for a needed read out of the old device then this has to be checked separately. '''Attention:''' For the configuration, the PC is in need of a real COM-Port. If there is no real COM-Port at the PC, then a [[USB-to-RS232 converter]] has to be used.<br />
*'''Virtuelle Geberauflösung:''' Damit die Nockenwerte der vorhandenen elektronischen Nockensteuerung im neuen Datenbaustein wiederverwendet werden können, muss die virtuelle Geberauflösung auf den Wert der vorhandenen elektronischen Nockensteuerung geändert werden.<br />
*'''Art der Totzeitkompensation:''' Damit die Totzeiten der vorhandenen elektronischen Nockensteuerung im neuen Datenbaustein wiederverwendet werden können, muss die Art der Totzeit (Bitweise; Blockweise; ...) auf die von der vorhandenen elektronischen Nockensteuerung verwendeten Art geändert werden.<br />
*'''PROFIBUS-Slave-ID:''' Die gewünschte PROFIBUS-Slave-ID muss mit der Software WINLOC 32 eingestellt werden, wenn diese nicht über den PROFIBUS-Master zugewiesen werden soll. Im Auslieferungszustand ist die PROFIBUS-Slave-ID auf 126 eingestellt.<br />
*'''Betriebs-Modi:''' In Verbindung mit einem PROFIBUS-Master muss dieser auf '''S7-Mode''' eingestellt sein. Im Auslieferungszustand ist der S7-Mode bereits eingestellt. <br />
*'''Logik:''' Wenn im Altgerät die Logikfunktion verwendet wird, muss diese im ROTARNOCK 100-PB noch freigeschaltet werden. Dafür wird ein Freischaltcode benötigt, der kostenpflichtig ist. '''Achtung:''' Der Freischaltcode für die Logikfunktion ist an die Serien-Nr. gebunden und kann daher nicht für andere elektronische Nockensteuerungen verwendet werden.<br />
<br />
==SPS Projekt==<br />
*'''GSD-Datei:''' Um das ROTARNOCK 100-PB in das Projekt einbinden zu können, muss die GSD-Datei [[#Weblinks|'''(R100.GSD)''']] in die Steuerung geladen werden.<br />
*'''AWL-Datei:''' Die im Projekt befindliche AWL-Datei, die im Datenbaustein abgebildet wird, muss durch eine für ROTARNOCK 100-PB passende AWL-Datei ersetzt werden. Dazu muss der [[Datenbausteingenerator]]2 verwendet werden.<br />
<br />
==Weblinks==<br />
*[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/ROTARNOCK%20100/German/ROTARNOCK_100.pdf Handbuch für das ROTARNOCK 100] (PDF-Datei)<br />
*[https://www.deutschmann.de/downloads/Support/Profibus/R100.GSD GSD-Datei für das ROTARNOCK 100-PB] <br />
*Handbuch [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/NSW%20mit%20Feldbus-CamControlWithFieldbusConnection/German/NSWmitFeldbus.pdf Nockensteuerungen mit Feldbusanbindung] (PDF-Datei)<br />
*Handbuch [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/L100,%20200,%20R80,%20100%20mit%20Feldbusanbindung-WithFieldbusConnection/German/L-R%20mit%20Feldbus_d.pdf ROTARNOCK 100 mit Feldbusanbindung] (PDF-Datei)</div>Reithhttps://wiki.deutschmann.de/index.php?title=Device_replacement_ROTARNOCK_-_PROFIBUS_(English)&diff=3349Device replacement ROTARNOCK - PROFIBUS (English)2017-12-18T09:31:32Z<p>Reith: /* Device Configuration */</p>
<hr />
<div>'''ROTARNOCK 1-PB''' und '''ROTARNOCK 2-PB''' can be replaced by '''ROTARNOCK 100-PB''' . As an 1:1 exchange is not possible, the following points have to be noted:<br />
<br />
==Device Configuration== <br />
The configuration has to be done with our software [[WINLOC 32 (English)|WINLOC 32]]-Basis-or Comfortversion. Herefore is needed a corresponding [[Programming cable]]. '''Note:''' If this programming cable may be used for a needed read out of the old device then this has to be checked separately. '''Attention:''' Für die Konfiguration muss ein echter COM-Port am PC vorhanden sein. Wenn kein echter COM-Port mehr am PC vorhanden ist, wird ein [[USB-to-RS232 converter]] benötigt.<br />
*'''Virtuelle Geberauflösung:''' Damit die Nockenwerte der vorhandenen elektronischen Nockensteuerung im neuen Datenbaustein wiederverwendet werden können, muss die virtuelle Geberauflösung auf den Wert der vorhandenen elektronischen Nockensteuerung geändert werden.<br />
*'''Art der Totzeitkompensation:''' Damit die Totzeiten der vorhandenen elektronischen Nockensteuerung im neuen Datenbaustein wiederverwendet werden können, muss die Art der Totzeit (Bitweise; Blockweise; ...) auf die von der vorhandenen elektronischen Nockensteuerung verwendeten Art geändert werden.<br />
*'''PROFIBUS-Slave-ID:''' Die gewünschte PROFIBUS-Slave-ID muss mit der Software WINLOC 32 eingestellt werden, wenn diese nicht über den PROFIBUS-Master zugewiesen werden soll. Im Auslieferungszustand ist die PROFIBUS-Slave-ID auf 126 eingestellt.<br />
*'''Betriebs-Modi:''' In Verbindung mit einem PROFIBUS-Master muss dieser auf '''S7-Mode''' eingestellt sein. Im Auslieferungszustand ist der S7-Mode bereits eingestellt. <br />
*'''Logik:''' Wenn im Altgerät die Logikfunktion verwendet wird, muss diese im ROTARNOCK 100-PB noch freigeschaltet werden. Dafür wird ein Freischaltcode benötigt, der kostenpflichtig ist. '''Achtung:''' Der Freischaltcode für die Logikfunktion ist an die Serien-Nr. gebunden und kann daher nicht für andere elektronische Nockensteuerungen verwendet werden.<br />
<br />
==SPS Projekt==<br />
*'''GSD-Datei:''' Um das ROTARNOCK 100-PB in das Projekt einbinden zu können, muss die GSD-Datei [[#Weblinks|'''(R100.GSD)''']] in die Steuerung geladen werden.<br />
*'''AWL-Datei:''' Die im Projekt befindliche AWL-Datei, die im Datenbaustein abgebildet wird, muss durch eine für ROTARNOCK 100-PB passende AWL-Datei ersetzt werden. Dazu muss der [[Datenbausteingenerator]]2 verwendet werden.<br />
<br />
==Weblinks==<br />
*[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/ROTARNOCK%20100/German/ROTARNOCK_100.pdf Handbuch für das ROTARNOCK 100] (PDF-Datei)<br />
*[https://www.deutschmann.de/downloads/Support/Profibus/R100.GSD GSD-Datei für das ROTARNOCK 100-PB] <br />
*Handbuch [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/NSW%20mit%20Feldbus-CamControlWithFieldbusConnection/German/NSWmitFeldbus.pdf Nockensteuerungen mit Feldbusanbindung] (PDF-Datei)<br />
*Handbuch [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/L100,%20200,%20R80,%20100%20mit%20Feldbusanbindung-WithFieldbusConnection/German/L-R%20mit%20Feldbus_d.pdf ROTARNOCK 100 mit Feldbusanbindung] (PDF-Datei)</div>Reithhttps://wiki.deutschmann.de/index.php?title=Device_replacement_ROTARNOCK_-_PROFIBUS_(English)&diff=3348Device replacement ROTARNOCK - PROFIBUS (English)2017-12-18T09:26:39Z<p>Reith: /* Device Configuration */</p>
<hr />
<div>'''ROTARNOCK 1-PB''' und '''ROTARNOCK 2-PB''' can be replaced by '''ROTARNOCK 100-PB''' . As an 1:1 exchange is not possible, the following points have to be noted:<br />
<br />
==Device Configuration== <br />
The configuration has to be done with our software [[WINLOC 32 (English)|WINLOC 32]]-Basis-or Comfortversion. Herefore is needed a corresponding [[Programming cable (English)|Programming cable]]. '''Note:''' If this programming cable may be used for a needed read out of the old device then this has to be checked separately. '''Attention:''' Für die Konfiguration muss ein echter COM-Port am PC vorhanden sein. Wenn kein echter COM-Port mehr am PC vorhanden ist, wird ein [[USB-RS232-Konverter]] benötigt.<br />
*'''Virtuelle Geberauflösung:''' Damit die Nockenwerte der vorhandenen elektronischen Nockensteuerung im neuen Datenbaustein wiederverwendet werden können, muss die virtuelle Geberauflösung auf den Wert der vorhandenen elektronischen Nockensteuerung geändert werden.<br />
*'''Art der Totzeitkompensation:''' Damit die Totzeiten der vorhandenen elektronischen Nockensteuerung im neuen Datenbaustein wiederverwendet werden können, muss die Art der Totzeit (Bitweise; Blockweise; ...) auf die von der vorhandenen elektronischen Nockensteuerung verwendeten Art geändert werden.<br />
*'''PROFIBUS-Slave-ID:''' Die gewünschte PROFIBUS-Slave-ID muss mit der Software WINLOC 32 eingestellt werden, wenn diese nicht über den PROFIBUS-Master zugewiesen werden soll. Im Auslieferungszustand ist die PROFIBUS-Slave-ID auf 126 eingestellt.<br />
*'''Betriebs-Modi:''' In Verbindung mit einem PROFIBUS-Master muss dieser auf '''S7-Mode''' eingestellt sein. Im Auslieferungszustand ist der S7-Mode bereits eingestellt. <br />
*'''Logik:''' Wenn im Altgerät die Logikfunktion verwendet wird, muss diese im ROTARNOCK 100-PB noch freigeschaltet werden. Dafür wird ein Freischaltcode benötigt, der kostenpflichtig ist. '''Achtung:''' Der Freischaltcode für die Logikfunktion ist an die Serien-Nr. gebunden und kann daher nicht für andere elektronische Nockensteuerungen verwendet werden.<br />
<br />
==SPS Projekt==<br />
*'''GSD-Datei:''' Um das ROTARNOCK 100-PB in das Projekt einbinden zu können, muss die GSD-Datei [[#Weblinks|'''(R100.GSD)''']] in die Steuerung geladen werden.<br />
*'''AWL-Datei:''' Die im Projekt befindliche AWL-Datei, die im Datenbaustein abgebildet wird, muss durch eine für ROTARNOCK 100-PB passende AWL-Datei ersetzt werden. Dazu muss der [[Datenbausteingenerator]]2 verwendet werden.<br />
<br />
==Weblinks==<br />
*[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/ROTARNOCK%20100/German/ROTARNOCK_100.pdf Handbuch für das ROTARNOCK 100] (PDF-Datei)<br />
*[https://www.deutschmann.de/downloads/Support/Profibus/R100.GSD GSD-Datei für das ROTARNOCK 100-PB] <br />
*Handbuch [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/NSW%20mit%20Feldbus-CamControlWithFieldbusConnection/German/NSWmitFeldbus.pdf Nockensteuerungen mit Feldbusanbindung] (PDF-Datei)<br />
*Handbuch [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/L100,%20200,%20R80,%20100%20mit%20Feldbusanbindung-WithFieldbusConnection/German/L-R%20mit%20Feldbus_d.pdf ROTARNOCK 100 mit Feldbusanbindung] (PDF-Datei)</div>Reithhttps://wiki.deutschmann.de/index.php?title=Device_replacement_ROTARNOCK_-_PROFIBUS_(English)&diff=3347Device replacement ROTARNOCK - PROFIBUS (English)2017-12-18T09:23:32Z<p>Reith: /* Device Configuration */</p>
<hr />
<div>'''ROTARNOCK 1-PB''' und '''ROTARNOCK 2-PB''' can be replaced by '''ROTARNOCK 100-PB''' . As an 1:1 exchange is not possible, the following points have to be noted:<br />
<br />
==Device Configuration== <br />
The configuration has to be done with our software [[WINLOC 32 (English)|WINLOC 32]]-Basis-or Comfortversion. Herefore is needed a corresponding [[Programming cable (English)|Programming cable]]. '''Hinweis:''' Ob dieses Programmierkabel auch für ein ggf. benötigtes Auslesen des Altgerätes verwendet werden kann, muss im jeweiligen Fall geprüft werden. '''Achtung:''' Für die Konfiguration muss ein echter COM-Port am PC vorhanden sein. Wenn kein echter COM-Port mehr am PC vorhanden ist, wird ein [[USB-RS232-Konverter]] benötigt.<br />
*'''Virtuelle Geberauflösung:''' Damit die Nockenwerte der vorhandenen elektronischen Nockensteuerung im neuen Datenbaustein wiederverwendet werden können, muss die virtuelle Geberauflösung auf den Wert der vorhandenen elektronischen Nockensteuerung geändert werden.<br />
*'''Art der Totzeitkompensation:''' Damit die Totzeiten der vorhandenen elektronischen Nockensteuerung im neuen Datenbaustein wiederverwendet werden können, muss die Art der Totzeit (Bitweise; Blockweise; ...) auf die von der vorhandenen elektronischen Nockensteuerung verwendeten Art geändert werden.<br />
*'''PROFIBUS-Slave-ID:''' Die gewünschte PROFIBUS-Slave-ID muss mit der Software WINLOC 32 eingestellt werden, wenn diese nicht über den PROFIBUS-Master zugewiesen werden soll. Im Auslieferungszustand ist die PROFIBUS-Slave-ID auf 126 eingestellt.<br />
*'''Betriebs-Modi:''' In Verbindung mit einem PROFIBUS-Master muss dieser auf '''S7-Mode''' eingestellt sein. Im Auslieferungszustand ist der S7-Mode bereits eingestellt. <br />
*'''Logik:''' Wenn im Altgerät die Logikfunktion verwendet wird, muss diese im ROTARNOCK 100-PB noch freigeschaltet werden. Dafür wird ein Freischaltcode benötigt, der kostenpflichtig ist. '''Achtung:''' Der Freischaltcode für die Logikfunktion ist an die Serien-Nr. gebunden und kann daher nicht für andere elektronische Nockensteuerungen verwendet werden.<br />
<br />
==SPS Projekt==<br />
*'''GSD-Datei:''' Um das ROTARNOCK 100-PB in das Projekt einbinden zu können, muss die GSD-Datei [[#Weblinks|'''(R100.GSD)''']] in die Steuerung geladen werden.<br />
*'''AWL-Datei:''' Die im Projekt befindliche AWL-Datei, die im Datenbaustein abgebildet wird, muss durch eine für ROTARNOCK 100-PB passende AWL-Datei ersetzt werden. Dazu muss der [[Datenbausteingenerator]]2 verwendet werden.<br />
<br />
==Weblinks==<br />
*[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/ROTARNOCK%20100/German/ROTARNOCK_100.pdf Handbuch für das ROTARNOCK 100] (PDF-Datei)<br />
*[https://www.deutschmann.de/downloads/Support/Profibus/R100.GSD GSD-Datei für das ROTARNOCK 100-PB] <br />
*Handbuch [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/NSW%20mit%20Feldbus-CamControlWithFieldbusConnection/German/NSWmitFeldbus.pdf Nockensteuerungen mit Feldbusanbindung] (PDF-Datei)<br />
*Handbuch [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/L100,%20200,%20R80,%20100%20mit%20Feldbusanbindung-WithFieldbusConnection/German/L-R%20mit%20Feldbus_d.pdf ROTARNOCK 100 mit Feldbusanbindung] (PDF-Datei)</div>Reithhttps://wiki.deutschmann.de/index.php?title=Device_replacement_ROTARNOCK_-_PROFIBUS_(English)&diff=3346Device replacement ROTARNOCK - PROFIBUS (English)2017-12-18T09:18:08Z<p>Reith: /* Device Configuration */</p>
<hr />
<div>'''ROTARNOCK 1-PB''' und '''ROTARNOCK 2-PB''' can be replaced by '''ROTARNOCK 100-PB''' . As an 1:1 exchange is not possible, the following points have to be noted:<br />
<br />
==Device Configuration== <br />
The configuration has to be done with our software [[WINLOC 32 (English)|WINLOC 32]]-Basis-or Comfortversion. Herefore is needed a corresponding [[Programming Cable (English)|Programming Cable]]. '''Hinweis:''' Ob dieses Programmierkabel auch für ein ggf. benötigtes Auslesen des Altgerätes verwendet werden kann, muss im jeweiligen Fall geprüft werden. '''Achtung:''' Für die Konfiguration muss ein echter COM-Port am PC vorhanden sein. Wenn kein echter COM-Port mehr am PC vorhanden ist, wird ein [[USB-RS232-Konverter]] benötigt.<br />
*'''Virtuelle Geberauflösung:''' Damit die Nockenwerte der vorhandenen elektronischen Nockensteuerung im neuen Datenbaustein wiederverwendet werden können, muss die virtuelle Geberauflösung auf den Wert der vorhandenen elektronischen Nockensteuerung geändert werden.<br />
*'''Art der Totzeitkompensation:''' Damit die Totzeiten der vorhandenen elektronischen Nockensteuerung im neuen Datenbaustein wiederverwendet werden können, muss die Art der Totzeit (Bitweise; Blockweise; ...) auf die von der vorhandenen elektronischen Nockensteuerung verwendeten Art geändert werden.<br />
*'''PROFIBUS-Slave-ID:''' Die gewünschte PROFIBUS-Slave-ID muss mit der Software WINLOC 32 eingestellt werden, wenn diese nicht über den PROFIBUS-Master zugewiesen werden soll. Im Auslieferungszustand ist die PROFIBUS-Slave-ID auf 126 eingestellt.<br />
*'''Betriebs-Modi:''' In Verbindung mit einem PROFIBUS-Master muss dieser auf '''S7-Mode''' eingestellt sein. Im Auslieferungszustand ist der S7-Mode bereits eingestellt. <br />
*'''Logik:''' Wenn im Altgerät die Logikfunktion verwendet wird, muss diese im ROTARNOCK 100-PB noch freigeschaltet werden. Dafür wird ein Freischaltcode benötigt, der kostenpflichtig ist. '''Achtung:''' Der Freischaltcode für die Logikfunktion ist an die Serien-Nr. gebunden und kann daher nicht für andere elektronische Nockensteuerungen verwendet werden.<br />
<br />
==SPS Projekt==<br />
*'''GSD-Datei:''' Um das ROTARNOCK 100-PB in das Projekt einbinden zu können, muss die GSD-Datei [[#Weblinks|'''(R100.GSD)''']] in die Steuerung geladen werden.<br />
*'''AWL-Datei:''' Die im Projekt befindliche AWL-Datei, die im Datenbaustein abgebildet wird, muss durch eine für ROTARNOCK 100-PB passende AWL-Datei ersetzt werden. Dazu muss der [[Datenbausteingenerator]]2 verwendet werden.<br />
<br />
==Weblinks==<br />
*[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/ROTARNOCK%20100/German/ROTARNOCK_100.pdf Handbuch für das ROTARNOCK 100] (PDF-Datei)<br />
*[https://www.deutschmann.de/downloads/Support/Profibus/R100.GSD GSD-Datei für das ROTARNOCK 100-PB] <br />
*Handbuch [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/NSW%20mit%20Feldbus-CamControlWithFieldbusConnection/German/NSWmitFeldbus.pdf Nockensteuerungen mit Feldbusanbindung] (PDF-Datei)<br />
*Handbuch [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/L100,%20200,%20R80,%20100%20mit%20Feldbusanbindung-WithFieldbusConnection/German/L-R%20mit%20Feldbus_d.pdf ROTARNOCK 100 mit Feldbusanbindung] (PDF-Datei)</div>Reithhttps://wiki.deutschmann.de/index.php?title=Device_replacement_ROTARNOCK_-_PROFIBUS_(English)&diff=3345Device replacement ROTARNOCK - PROFIBUS (English)2017-12-18T09:13:17Z<p>Reith: /* Device Configuration */</p>
<hr />
<div>'''ROTARNOCK 1-PB''' und '''ROTARNOCK 2-PB''' can be replaced by '''ROTARNOCK 100-PB''' . As an 1:1 exchange is not possible, the following points have to be noted:<br />
<br />
==Device Configuration== <br />
The configuration has to be done with our software [[WINLOC 32]]-Basis-oder Komfortversion durchgeführt werden. Daür wird ein entsprechendes [[Programmierkabel]] benötigt. '''Hinweis:''' Ob dieses Programmierkabel auch für ein ggf. benötigtes Auslesen des Altgerätes verwendet werden kann, muss im jeweiligen Fall geprüft werden. '''Achtung:''' Für die Konfiguration muss ein echter COM-Port am PC vorhanden sein. Wenn kein echter COM-Port mehr am PC vorhanden ist, wird ein [[USB-RS232-Konverter]] benötigt.<br />
*'''Virtuelle Geberauflösung:''' Damit die Nockenwerte der vorhandenen elektronischen Nockensteuerung im neuen Datenbaustein wiederverwendet werden können, muss die virtuelle Geberauflösung auf den Wert der vorhandenen elektronischen Nockensteuerung geändert werden.<br />
*'''Art der Totzeitkompensation:''' Damit die Totzeiten der vorhandenen elektronischen Nockensteuerung im neuen Datenbaustein wiederverwendet werden können, muss die Art der Totzeit (Bitweise; Blockweise; ...) auf die von der vorhandenen elektronischen Nockensteuerung verwendeten Art geändert werden.<br />
*'''PROFIBUS-Slave-ID:''' Die gewünschte PROFIBUS-Slave-ID muss mit der Software WINLOC 32 eingestellt werden, wenn diese nicht über den PROFIBUS-Master zugewiesen werden soll. Im Auslieferungszustand ist die PROFIBUS-Slave-ID auf 126 eingestellt.<br />
*'''Betriebs-Modi:''' In Verbindung mit einem PROFIBUS-Master muss dieser auf '''S7-Mode''' eingestellt sein. Im Auslieferungszustand ist der S7-Mode bereits eingestellt. <br />
*'''Logik:''' Wenn im Altgerät die Logikfunktion verwendet wird, muss diese im ROTARNOCK 100-PB noch freigeschaltet werden. Dafür wird ein Freischaltcode benötigt, der kostenpflichtig ist. '''Achtung:''' Der Freischaltcode für die Logikfunktion ist an die Serien-Nr. gebunden und kann daher nicht für andere elektronische Nockensteuerungen verwendet werden.<br />
<br />
==SPS Projekt==<br />
*'''GSD-Datei:''' Um das ROTARNOCK 100-PB in das Projekt einbinden zu können, muss die GSD-Datei [[#Weblinks|'''(R100.GSD)''']] in die Steuerung geladen werden.<br />
*'''AWL-Datei:''' Die im Projekt befindliche AWL-Datei, die im Datenbaustein abgebildet wird, muss durch eine für ROTARNOCK 100-PB passende AWL-Datei ersetzt werden. Dazu muss der [[Datenbausteingenerator]]2 verwendet werden.<br />
<br />
==Weblinks==<br />
*[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/ROTARNOCK%20100/German/ROTARNOCK_100.pdf Handbuch für das ROTARNOCK 100] (PDF-Datei)<br />
*[https://www.deutschmann.de/downloads/Support/Profibus/R100.GSD GSD-Datei für das ROTARNOCK 100-PB] <br />
*Handbuch [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/NSW%20mit%20Feldbus-CamControlWithFieldbusConnection/German/NSWmitFeldbus.pdf Nockensteuerungen mit Feldbusanbindung] (PDF-Datei)<br />
*Handbuch [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/L100,%20200,%20R80,%20100%20mit%20Feldbusanbindung-WithFieldbusConnection/German/L-R%20mit%20Feldbus_d.pdf ROTARNOCK 100 mit Feldbusanbindung] (PDF-Datei)</div>Reithhttps://wiki.deutschmann.de/index.php?title=Device_replacement_ROTARNOCK_-_PROFIBUS_(English)&diff=3344Device replacement ROTARNOCK - PROFIBUS (English)2017-12-18T09:11:14Z<p>Reith: /* Gerätekonfiguration */</p>
<hr />
<div>'''ROTARNOCK 1-PB''' und '''ROTARNOCK 2-PB''' can be replaced by '''ROTARNOCK 100-PB''' . As an 1:1 exchange is not possible, the following points have to be noted:<br />
<br />
==Device Configuration== <br />
Die Konfiguration muss mit der Software [[WINLOC 32]]-Basis-oder Komfortversion durchgeführt werden. Daür wird ein entsprechendes [[Programmierkabel]] benötigt. '''Hinweis:''' Ob dieses Programmierkabel auch für ein ggf. benötigtes Auslesen des Altgerätes verwendet werden kann, muss im jeweiligen Fall geprüft werden. '''Achtung:''' Für die Konfiguration muss ein echter COM-Port am PC vorhanden sein. Wenn kein echter COM-Port mehr am PC vorhanden ist, wird ein [[USB-RS232-Konverter]] benötigt.<br />
*'''Virtuelle Geberauflösung:''' Damit die Nockenwerte der vorhandenen elektronischen Nockensteuerung im neuen Datenbaustein wiederverwendet werden können, muss die virtuelle Geberauflösung auf den Wert der vorhandenen elektronischen Nockensteuerung geändert werden.<br />
*'''Art der Totzeitkompensation:''' Damit die Totzeiten der vorhandenen elektronischen Nockensteuerung im neuen Datenbaustein wiederverwendet werden können, muss die Art der Totzeit (Bitweise; Blockweise; ...) auf die von der vorhandenen elektronischen Nockensteuerung verwendeten Art geändert werden.<br />
*'''PROFIBUS-Slave-ID:''' Die gewünschte PROFIBUS-Slave-ID muss mit der Software WINLOC 32 eingestellt werden, wenn diese nicht über den PROFIBUS-Master zugewiesen werden soll. Im Auslieferungszustand ist die PROFIBUS-Slave-ID auf 126 eingestellt.<br />
*'''Betriebs-Modi:''' In Verbindung mit einem PROFIBUS-Master muss dieser auf '''S7-Mode''' eingestellt sein. Im Auslieferungszustand ist der S7-Mode bereits eingestellt. <br />
*'''Logik:''' Wenn im Altgerät die Logikfunktion verwendet wird, muss diese im ROTARNOCK 100-PB noch freigeschaltet werden. Dafür wird ein Freischaltcode benötigt, der kostenpflichtig ist. '''Achtung:''' Der Freischaltcode für die Logikfunktion ist an die Serien-Nr. gebunden und kann daher nicht für andere elektronische Nockensteuerungen verwendet werden.<br />
<br />
==SPS Projekt==<br />
*'''GSD-Datei:''' Um das ROTARNOCK 100-PB in das Projekt einbinden zu können, muss die GSD-Datei [[#Weblinks|'''(R100.GSD)''']] in die Steuerung geladen werden.<br />
*'''AWL-Datei:''' Die im Projekt befindliche AWL-Datei, die im Datenbaustein abgebildet wird, muss durch eine für ROTARNOCK 100-PB passende AWL-Datei ersetzt werden. Dazu muss der [[Datenbausteingenerator]]2 verwendet werden.<br />
<br />
==Weblinks==<br />
*[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/ROTARNOCK%20100/German/ROTARNOCK_100.pdf Handbuch für das ROTARNOCK 100] (PDF-Datei)<br />
*[https://www.deutschmann.de/downloads/Support/Profibus/R100.GSD GSD-Datei für das ROTARNOCK 100-PB] <br />
*Handbuch [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/NSW%20mit%20Feldbus-CamControlWithFieldbusConnection/German/NSWmitFeldbus.pdf Nockensteuerungen mit Feldbusanbindung] (PDF-Datei)<br />
*Handbuch [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/L100,%20200,%20R80,%20100%20mit%20Feldbusanbindung-WithFieldbusConnection/German/L-R%20mit%20Feldbus_d.pdf ROTARNOCK 100 mit Feldbusanbindung] (PDF-Datei)</div>Reithhttps://wiki.deutschmann.de/index.php?title=Device_replacement_ROTARNOCK_-_PROFIBUS_(English)&diff=3343Device replacement ROTARNOCK - PROFIBUS (English)2017-12-18T09:02:50Z<p>Reith: </p>
<hr />
<div>'''ROTARNOCK 1-PB''' und '''ROTARNOCK 2-PB''' can be replaced by '''ROTARNOCK 100-PB''' . As an 1:1 exchange is not possible, the following points have to be noted:<br />
<br />
==Gerätekonfiguration== <br />
Die Konfiguration muss mit der Software [[WINLOC 32]]-Basis-oder Komfortversion durchgeführt werden. Daür wird ein entsprechendes [[Programmierkabel]] benötigt. '''Hinweis:''' Ob dieses Programmierkabel auch für ein ggf. benötigtes Auslesen des Altgerätes verwendet werden kann, muss im jeweiligen Fall geprüft werden. '''Achtung:''' Für die Konfiguration muss ein echter COM-Port am PC vorhanden sein. Wenn kein echter COM-Port mehr am PC vorhanden ist, wird ein [[USB-RS232-Konverter]] benötigt.<br />
*'''Virtuelle Geberauflösung:''' Damit die Nockenwerte der vorhandenen elektronischen Nockensteuerung im neuen Datenbaustein wiederverwendet werden können, muss die virtuelle Geberauflösung auf den Wert der vorhandenen elektronischen Nockensteuerung geändert werden.<br />
*'''Art der Totzeitkompensation:''' Damit die Totzeiten der vorhandenen elektronischen Nockensteuerung im neuen Datenbaustein wiederverwendet werden können, muss die Art der Totzeit (Bitweise; Blockweise; ...) auf die von der vorhandenen elektronischen Nockensteuerung verwendeten Art geändert werden.<br />
*'''PROFIBUS-Slave-ID:''' Die gewünschte PROFIBUS-Slave-ID muss mit der Software WINLOC 32 eingestellt werden, wenn diese nicht über den PROFIBUS-Master zugewiesen werden soll. Im Auslieferungszustand ist die PROFIBUS-Slave-ID auf 126 eingestellt.<br />
*'''Betriebs-Modi:''' In Verbindung mit einem PROFIBUS-Master muss dieser auf '''S7-Mode''' eingestellt sein. Im Auslieferungszustand ist der S7-Mode bereits eingestellt. <br />
*'''Logik:''' Wenn im Altgerät die Logikfunktion verwendet wird, muss diese im ROTARNOCK 100-PB noch freigeschaltet werden. Dafür wird ein Freischaltcode benötigt, der kostenpflichtig ist. '''Achtung:''' Der Freischaltcode für die Logikfunktion ist an die Serien-Nr. gebunden und kann daher nicht für andere elektronische Nockensteuerungen verwendet werden.<br />
<br />
==SPS Projekt==<br />
*'''GSD-Datei:''' Um das ROTARNOCK 100-PB in das Projekt einbinden zu können, muss die GSD-Datei [[#Weblinks|'''(R100.GSD)''']] in die Steuerung geladen werden.<br />
*'''AWL-Datei:''' Die im Projekt befindliche AWL-Datei, die im Datenbaustein abgebildet wird, muss durch eine für ROTARNOCK 100-PB passende AWL-Datei ersetzt werden. Dazu muss der [[Datenbausteingenerator]]2 verwendet werden.<br />
<br />
==Weblinks==<br />
*[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/ROTARNOCK%20100/German/ROTARNOCK_100.pdf Handbuch für das ROTARNOCK 100] (PDF-Datei)<br />
*[https://www.deutschmann.de/downloads/Support/Profibus/R100.GSD GSD-Datei für das ROTARNOCK 100-PB] <br />
*Handbuch [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/NSW%20mit%20Feldbus-CamControlWithFieldbusConnection/German/NSWmitFeldbus.pdf Nockensteuerungen mit Feldbusanbindung] (PDF-Datei)<br />
*Handbuch [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/L100,%20200,%20R80,%20100%20mit%20Feldbusanbindung-WithFieldbusConnection/German/L-R%20mit%20Feldbus_d.pdf ROTARNOCK 100 mit Feldbusanbindung] (PDF-Datei)</div>Reithhttps://wiki.deutschmann.de/index.php?title=ROTARNOCK_100_(English)&diff=3342ROTARNOCK 100 (English)2017-12-15T09:42:35Z<p>Reith: </p>
<hr />
<div>[[Datei:ROTARNOCK 100.jpg|thumb|ROTARNOCK 100]]<br />
ROTARNOCK is a cam control integrated in the housing of an absolute encoder.<br />
== Configuration ==<br />
By factory setting '''all''' ROTARNOCK 100 Cam controls are configured as follows:<br />
*Virtual Encoder resolution: '''4096'''<br />
*Idle time: '''Bitwise'''<br />
This configuration set by default may be changed by using [[TERM 6 (English)|TERM 6]] or the software [[WINLOC 32 (English)|WINLOC 32]].<br />
== Programming ==<br />
ROTARNOCK 100 can be programmed by TERM 6 or [[TERM 24 (English)|TERM 24]] or the software WINLOC 32. In the PROFIBUS-Version the programming is done via PROFIBUS.<br />
<br />
== device versions ==<br />
=== ROTARNOCK 100 ===<br />
ROTARNOCK 100 features the serial RS232-interface '''or''' a RS485-([[DICNET (English)|DICNET]]) Interface. <br />
{| class="wikitable"<br />
|+versions<br />
|-<br />
! Interface !! protection class !! outputs !! Art.-No.<br />
|-<br />
| RS232 || IP54 || 16 || V3431<br />
|-<br />
| RS485 || IP54 || 16 || V3413<br />
|-<br />
| RS232 || IP65 || 16 || V3433<br />
|-<br />
| RS485 || IP65 || 16 || V3432<br />
|}<br />
At devices with a RS485-(DICNET) interface the DICNET-addresses have to be set via the 9 pol. D-Sub plug '''(for IP54)''' resp. set via the rotary switch '''(for IP65)'''. '''Only''' the DICNET-Addresses '''0 ... 15''' (decimal) are supported. <br /><br />
'''Note:''' At the '''first and the last''' device within DICNET has to be set the bus termination resistor. Therefore '''DICNET+''' has to be connected with '''R+''' and '''DICNET-''' has to be connected with '''R-'''. For the IP54-version this can be done directly in the 9 pol. D-Sub plug. For the IP65-version this has to be done in the mating plug to the 28 pol. round plug. <br />
=== ROTARNOCK 100-PB (PROFIBUS) ===<br />
ROTARNOCK 100-PB (PROFIBUS) is '''always''' PROFIBUS-Slave and contains the serial RS232-interface and a PROFIBUS-interface<br />
{| class="wikitable"<br />
|+Versions<br />
|-<br />
! Interface-Fieldbus !! Interface-serial !! protection class !! outputs !! Art.-No.<br />
|-<br />
| PROFIBUS || RS232 || IP54 || 16 + (32 software outputs)|| V3406<br />
|-<br />
| PROFIBUS || RS232 || IP65 || 12 + (36 Software outputs) || V3434<br />
|}<br />
For ROTARNOCK-100 two modes are selectable through WINLOC32 via the PROFIBUS-Interface.<br />
* '''S7-Modus''' (factory setting): For Operation at a Simatic S7 and for use of the [[data component simulator]].<br />
* '''Communication Profile Modus''': For Operation via [[#Weblinks|Communication profile for Deutschmann Cam Controls]].<br /><br />
The PROFIBUS-Address (Slave-ID) is set by default to '''126''' (decimal). The [[#Weblinks|'''GSD-file''' (R100.GSD)]] and a [[#Weblinks|'''S7-example project''']] are available for download on our homepage. Further Information regarding ROTARNOCK 100-PB may be found in the manuals [[#Weblinks|"Cam Controls with Fieldbus-Connection"]] und [[#Weblinks|"ROTARNOCK 100 with fieldbus-connection"]].<br />
*'''As replacement for ROTARNOCK 4-PB''': ROTARNOCK 100-PB has the Ident No.: '''3606h'''. If ROTARNOCK 100-PB should be used as replacement for '''ROTARNOCK 4-PB''', the Ident-No. can be changed in WINLOC 32 with the key combination '''"Strg + N"''' into the Ident No.: '''3231h'''. So there have to be done no changes in an existing project. '''Note:''' If the logic function is used for ROTARNOCK 4-PB, then this logic function has to be activated for ROTARNOCK 100-PB. Therefore is needed a chargeable release code. '''Attention:'''This release code is tied the serial-no. and can not be used for any other cam control. <br /><br />
*'''As replacement for ROTARNOCK 1-PB and 2-PB''': If ROTARNOCK 100-PB should be used as a replacement for '''ROTARNOCK 1-PB''' or as a replacement for '''ROTARNOCK 2-PB''' , the existing project has to be changed. All neccessary information maybe found under: [[Device replacement ROTARNOCK 1-PB and ROTARNOCK 2-PB (English)|Device replacement ROTARNOCK 1-PB and ROTARNOCK 2-PB]].<br />
<br />
=== ROTARNOCK 100-PN (PROFINET) ===<br />
ROTARNOCK 100-PN (PROFINET) ist '''always''' PROFINET-Slave and features a serial RS232-interface and a PROFINET-interface.<br />
{| class="wikitable"<br />
|+Version<br />
|-<br />
! Interface - Fieldbus !! Interface-serial !! Protection class !! Outputs !! Art.-No.<br />
|-<br />
| PROFINET || RS232 || IP65 || 12 + (32 software outputs)|| V3795<br />
|}<br />
The [[#Weblinks|'''GSDML-file''' (GSDML-V2.3-Deutschmann-ROTARNOCK 100-PN-20150317-160500.xml)]] and a [[#Weblinks|'''S7-example project''']] are available for download on our homepage.<br />
<br />
== Weblinks ==<br />
*[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/ROTARNOCK%20100/English/ROTARNOCK_100_e.pdf Manual for ROTARNOCK 100] (PDF-file)<br />
*[https://www.deutschmann.de/downloads/Support/Profibus/R100.GSD GSD-file for ROTARNOCK 100-PB] <br />
*[https://www.deutschmann.de/downloads/Support/Profinet/GSDML-ROTARNOCK100.zip GSDML-file for ROTARNOCK 100-PN]<br />
*[https://www.deutschmann.de/downloads/Support/S7/Nockenschaltwerk_CamSwitch/Nsw_v2_e.zip S7-example project PROFIBUS] (ZIP-file)<br />
*[https://www.deutschmann.de/downloads/Support/S7/Nockenschaltwerk_CamSwitch/R100-PN_example.zip S7-example project PROFINET] (ZIP-file)<br />
*Manual [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/DIVERS/Kommunikationsprofil/Kommunikationsprofil%20englisch/komm_profil_e.pdf Communication profile for Deutschmann cam controls] (PDF-file)<br />
*Manual [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/NSW%20mit%20Feldbus-CamControlWithFieldbusConnection/English/CamControlsWithFieldbusConnection.pdf Cam controls with fieldbus connection] (PDF-file)<br />
*Manual [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/L100,%20200,%20R80,%20100%20mit%20Feldbusanbindung-WithFieldbusConnection/English/L-R%20mit%20Feldbus-e.pdf ROTARNOCK 100 with fieldbus connection] (PDF-file)</div>Reithhttps://wiki.deutschmann.de/index.php?title=Device_replacement_ROTARNOCK_-_PROFIBUS_(English)&diff=3341Device replacement ROTARNOCK - PROFIBUS (English)2017-12-14T16:00:48Z<p>Reith: Die Seite wurde neu angelegt: „'''ROTARNOCK 1-PB''' und '''ROTARNOCK 2-PB''' können durch ein '''ROTARNOCK 100-PB''' ersetzt werden. Da aber ein 1:1 Austausch nicht möglich ist, müssen fo…“</p>
<hr />
<div>'''ROTARNOCK 1-PB''' und '''ROTARNOCK 2-PB''' können durch ein '''ROTARNOCK 100-PB''' ersetzt werden. Da aber ein 1:1 Austausch nicht möglich ist, müssen folgende Punkte dabei beachtet werden:<br />
<br />
==Gerätekonfiguration== <br />
Die Konfiguration muss mit der Software [[WINLOC 32]]-Basis-oder Komfortversion durchgeführt werden. Daür wird ein entsprechendes [[Programmierkabel]] benötigt. '''Hinweis:''' Ob dieses Programmierkabel auch für ein ggf. benötigtes Auslesen des Altgerätes verwendet werden kann, muss im jeweiligen Fall geprüft werden. '''Achtung:''' Für die Konfiguration muss ein echter COM-Port am PC vorhanden sein. Wenn kein echter COM-Port mehr am PC vorhanden ist, wird ein [[USB-RS232-Konverter]] benötigt.<br />
*'''Virtuelle Geberauflösung:''' Damit die Nockenwerte der vorhandenen elektronischen Nockensteuerung im neuen Datenbaustein wiederverwendet werden können, muss die virtuelle Geberauflösung auf den Wert der vorhandenen elektronischen Nockensteuerung geändert werden.<br />
*'''Art der Totzeitkompensation:''' Damit die Totzeiten der vorhandenen elektronischen Nockensteuerung im neuen Datenbaustein wiederverwendet werden können, muss die Art der Totzeit (Bitweise; Blockweise; ...) auf die von der vorhandenen elektronischen Nockensteuerung verwendeten Art geändert werden.<br />
*'''PROFIBUS-Slave-ID:''' Die gewünschte PROFIBUS-Slave-ID muss mit der Software WINLOC 32 eingestellt werden, wenn diese nicht über den PROFIBUS-Master zugewiesen werden soll. Im Auslieferungszustand ist die PROFIBUS-Slave-ID auf 126 eingestellt.<br />
*'''Betriebs-Modi:''' In Verbindung mit einem PROFIBUS-Master muss dieser auf '''S7-Mode''' eingestellt sein. Im Auslieferungszustand ist der S7-Mode bereits eingestellt. <br />
*'''Logik:''' Wenn im Altgerät die Logikfunktion verwendet wird, muss diese im ROTARNOCK 100-PB noch freigeschaltet werden. Dafür wird ein Freischaltcode benötigt, der kostenpflichtig ist. '''Achtung:''' Der Freischaltcode für die Logikfunktion ist an die Serien-Nr. gebunden und kann daher nicht für andere elektronische Nockensteuerungen verwendet werden.<br />
<br />
==SPS Projekt==<br />
*'''GSD-Datei:''' Um das ROTARNOCK 100-PB in das Projekt einbinden zu können, muss die GSD-Datei [[#Weblinks|'''(R100.GSD)''']] in die Steuerung geladen werden.<br />
*'''AWL-Datei:''' Die im Projekt befindliche AWL-Datei, die im Datenbaustein abgebildet wird, muss durch eine für ROTARNOCK 100-PB passende AWL-Datei ersetzt werden. Dazu muss der [[Datenbausteingenerator]]2 verwendet werden.<br />
<br />
==Weblinks==<br />
*[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/ROTARNOCK%20100/German/ROTARNOCK_100.pdf Handbuch für das ROTARNOCK 100] (PDF-Datei)<br />
*[https://www.deutschmann.de/downloads/Support/Profibus/R100.GSD GSD-Datei für das ROTARNOCK 100-PB] <br />
*Handbuch [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/NSW%20mit%20Feldbus-CamControlWithFieldbusConnection/German/NSWmitFeldbus.pdf Nockensteuerungen mit Feldbusanbindung] (PDF-Datei)<br />
*Handbuch [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/L100,%20200,%20R80,%20100%20mit%20Feldbusanbindung-WithFieldbusConnection/German/L-R%20mit%20Feldbus_d.pdf ROTARNOCK 100 mit Feldbusanbindung] (PDF-Datei)</div>Reithhttps://wiki.deutschmann.de/index.php?title=ROTARNOCK_100_(English)&diff=3340ROTARNOCK 100 (English)2017-12-14T15:58:41Z<p>Reith: </p>
<hr />
<div>[[Datei:ROTARNOCK 100.jpg|thumb|ROTARNOCK 100]]<br />
ROTARNOCK is a cam control integrated in the housing of an absolute encoder.<br />
== Configuration ==<br />
By factory setting '''all''' ROTARNOCK 100 Cam controls are configured as follows:<br />
*Virtual Encoder resolution: '''4096'''<br />
*Idle time: '''Bitwise'''<br />
This configuration set by default may be changed by using [[TERM 6 (English)|TERM 6]] or the software [[WINLOC 32 (English)|WINLOC 32]].<br />
== Programming ==<br />
ROTARNOCK 100 can be programmed by TERM 6 or [[TERM 24 (English)|TERM 24]] or the software WINLOC 32. In the PROFIBUS-Version the programming is done via PROFIBUS.<br />
<br />
== device versions ==<br />
=== ROTARNOCK 100 ===<br />
ROTARNOCK 100 features the serial RS232-interface '''or''' a RS485-([[DICNET (English)|DICNET]]) Interface. <br />
{| class="wikitable"<br />
|+versions<br />
|-<br />
! Interface !! protection class !! outputs !! Art.-No.<br />
|-<br />
| RS232 || IP54 || 16 || V3431<br />
|-<br />
| RS485 || IP54 || 16 || V3413<br />
|-<br />
| RS232 || IP65 || 16 || V3433<br />
|-<br />
| RS485 || IP65 || 16 || V3432<br />
|}<br />
At devices with a RS485-(DICNET) interface the DICNET-addresses have to be set via the 9 pol. D-Sub plug '''(for IP54)''' resp. set via the rotary switch '''(for IP65)'''. '''Only''' the DICNET-Addresses '''0 ... 15''' (decimal) are supported. <br /><br />
'''Note:''' At the '''first and the last''' device within DICNET has to be set the bus termination resistor. Therefore '''DICNET+''' has to be connected with '''R+''' and '''DICNET-''' has to be connected with '''R-'''. For the IP54-version this can be done directly in the 9 pol. D-Sub plug. For the IP65-version this has to be done in the mating plug to the 28 pol. round plug. <br />
=== ROTARNOCK 100-PB (PROFIBUS) ===<br />
ROTARNOCK 100-PB (PROFIBUS) is '''always''' PROFIBUS-Slave and contains the serial RS232-interface and a PROFIBUS-interface<br />
{| class="wikitable"<br />
|+Versions<br />
|-<br />
! Interface-Fieldbus !! Interface-serial !! protection class !! outputs !! Art.-No.<br />
|-<br />
| PROFIBUS || RS232 || IP54 || 16 + (32 software outputs)|| V3406<br />
|-<br />
| PROFIBUS || RS232 || IP65 || 12 + (36 Software outputs) || V3434<br />
|}<br />
For ROTARNOCK-100 two modes are selectable through WINLOC32 via the PROFIBUS-Interface.<br />
* '''S7-Modus''' (factory setting): For Operation at a Simatic S7 and for use of the [[data component simulator]].<br />
* '''Communication Profile Modus''': For Operation via [[#Weblinks|Communication profile for Deutschmann Cam Controls]].<br /><br />
The PROFIBUS-Address (Slave-ID) is set by default to '''126''' (decimal). The [[#Weblinks|'''GSD-file''' (R100.GSD)]] and a [[#Weblinks|'''S7-example project''']] are available for download on our homepage. Further Information regarding ROTARNOCK 100-PB may be found in the manuals [[#Weblinks|"Cam Controls with Fieldbus-Connection"]] und [[#Weblinks|"ROTARNOCK 100 with fieldbus-connection"]].<br />
*'''As replacement for ROTARNOCK 4-PB''': ROTARNOCK 100-PB has the Ident No.: '''3606h'''. If ROTARNOCK 100-PB should be used as replacement for '''ROTARNOCK 4-PB''', the Ident-No. can be changed in WINLOC 32 with the key combination '''"Strg + N"''' into the Ident No.: '''3231h'''. So there have to be done no changes in an existing project. '''Note:''' If the logic function is used for ROTARNOCK 4-PB, then this logic function has to be activated for ROTARNOCK 100-PB. Therefore is needed a chargeable release code. '''Attention:'''This release code is tied the serial-no. and can not be used for any other cam control. <br /><br />
*'''As replacement for ROTARNOCK 1-PB and 2-PB''': If ROTARNOCK 100-PB should be used as a replacement for '''ROTARNOCK 1-PB''' or as a replacement for '''ROTARNOCK 2-PB''' , the existing project has to be changed. All neccessary information maybe found under:[[Device_replacement_ROTARNOCK_1-PB and ROTARNOCK 2-PB_(English)|Device_replacement_ROTARNOCK_1-PB and ROTARNOCK 2-PB]].<br />
<br />
=== ROTARNOCK 100-PN (PROFINET) ===<br />
ROTARNOCK 100-PN (PROFINET) ist '''always''' PROFINET-Slave and features a serial RS232-interface and a PROFINET-interface.<br />
{| class="wikitable"<br />
|+Version<br />
|-<br />
! Interface - Fieldbus !! Interface-serial !! Protection class !! Outputs !! Art.-No.<br />
|-<br />
| PROFINET || RS232 || IP65 || 12 + (32 software outputs)|| V3795<br />
|}<br />
The [[#Weblinks|'''GSDML-file''' (GSDML-V2.3-Deutschmann-ROTARNOCK 100-PN-20150317-160500.xml)]] and a [[#Weblinks|'''S7-example project''']] are available for download on our homepage.<br />
<br />
== Weblinks ==<br />
*[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/ROTARNOCK%20100/English/ROTARNOCK_100_e.pdf Manual for ROTARNOCK 100] (PDF-file)<br />
*[https://www.deutschmann.de/downloads/Support/Profibus/R100.GSD GSD-file for ROTARNOCK 100-PB] <br />
*[https://www.deutschmann.de/downloads/Support/Profinet/GSDML-ROTARNOCK100.zip GSDML-file for ROTARNOCK 100-PN]<br />
*[https://www.deutschmann.de/downloads/Support/S7/Nockenschaltwerk_CamSwitch/Nsw_v2_e.zip S7-example project PROFIBUS] (ZIP-file)<br />
*[https://www.deutschmann.de/downloads/Support/S7/Nockenschaltwerk_CamSwitch/R100-PN_example.zip S7-example project PROFINET] (ZIP-file)<br />
*Manual [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/DIVERS/Kommunikationsprofil/Kommunikationsprofil%20englisch/komm_profil_e.pdf Communication profile for Deutschmann cam controls] (PDF-file)<br />
*Manual [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/NSW%20mit%20Feldbus-CamControlWithFieldbusConnection/English/CamControlsWithFieldbusConnection.pdf Cam controls with fieldbus connection] (PDF-file)<br />
*Manual [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/L100,%20200,%20R80,%20100%20mit%20Feldbusanbindung-WithFieldbusConnection/English/L-R%20mit%20Feldbus-e.pdf ROTARNOCK 100 with fieldbus connection] (PDF-file)</div>Reithhttps://wiki.deutschmann.de/index.php?title=ROTARNOCK_100_(English)&diff=3339ROTARNOCK 100 (English)2017-12-14T15:53:14Z<p>Reith: /* ROTARNOCK 100-PB (PROFIBUS) */</p>
<hr />
<div>[[Datei:ROTARNOCK 100.jpg|thumb|ROTARNOCK 100]]<br />
ROTARNOCK is a cam control integrated in the housing of an absolute encoder.<br />
== Configuration ==<br />
By factory setting '''all''' ROTARNOCK 100 Cam controls are configured as follows:<br />
*Virtual Encoder resolution: '''4096'''<br />
*Idle time: '''Bitwise'''<br />
This configuration set by default may be changed by using [[TERM 6 (English)|TERM 6]] or the software [[WINLOC 32 (English)|WINLOC 32]].<br />
== Programming ==<br />
ROTARNOCK 100 can be programmed by TERM 6 or [[TERM 24 (English)|TERM 24]] or the software WINLOC 32. In the PROFIBUS-Version the programming is done via PROFIBUS.<br />
<br />
== device versions ==<br />
=== ROTARNOCK 100 ===<br />
ROTARNOCK 100 features the serial RS232-interface '''or''' a RS485-([[DICNET (English)|DICNET]]) Interface. <br />
{| class="wikitable"<br />
|+versions<br />
|-<br />
! Interface !! protection class !! outputs !! Art.-No.<br />
|-<br />
| RS232 || IP54 || 16 || V3431<br />
|-<br />
| RS485 || IP54 || 16 || V3413<br />
|-<br />
| RS232 || IP65 || 16 || V3433<br />
|-<br />
| RS485 || IP65 || 16 || V3432<br />
|}<br />
At devices with a RS485-(DICNET) interface the DICNET-addresses have to be set via the 9 pol. D-Sub plug '''(for IP54)''' resp. set via the rotary switch '''(for IP65)'''. '''Only''' the DICNET-Addresses '''0 ... 15''' (decimal) are supported. <br /><br />
'''Note:''' At the '''first and the last''' device within DICNET has to be set the bus termination resistor. Therefore '''DICNET+''' has to be connected with '''R+''' and '''DICNET-''' has to be connected with '''R-'''. For the IP54-version this can be done directly in the 9 pol. D-Sub plug. For the IP65-version this has to be done in the mating plug to the 28 pol. round plug. <br />
=== ROTARNOCK 100-PB (PROFIBUS) ===<br />
ROTARNOCK 100-PB (PROFIBUS) is '''always''' PROFIBUS-Slave and contains the serial RS232-interface and a PROFIBUS-interface<br />
{| class="wikitable"<br />
|+Versions<br />
|-<br />
! Interface-Fieldbus !! Interface-serial !! protection class !! outputs !! Art.-No.<br />
|-<br />
| PROFIBUS || RS232 || IP54 || 16 + (32 software outputs)|| V3406<br />
|-<br />
| PROFIBUS || RS232 || IP65 || 12 + (36 Software outputs) || V3434<br />
|}<br />
For ROTARNOCK-100 two modes are selectable through WINLOC32 via the PROFIBUS-Interface.<br />
* '''S7-Modus''' (factory setting): For Operation at a Simatic S7 and for use of the [[data component simulator]].<br />
* '''Communication Profile Modus''': For Operation via [[#Weblinks|Communication profile for Deutschmann Cam Controls]].<br /><br />
The PROFIBUS-Address (Slave-ID) is set by default to '''126''' (decimal). The [[#Weblinks|'''GSD-file''' (R100.GSD)]] and a [[#Weblinks|'''S7-example project''']] are available for download on our homepage. Further Information regarding ROTARNOCK 100-PB may be found in the manuals [[#Weblinks|"Cam Controls with Fieldbus-Connection"]] und [[#Weblinks|"ROTARNOCK 100 with fieldbus-connection"]].<br />
*'''As replacement for ROTARNOCK 4-PB''': ROTARNOCK 100-PB has the Ident No.: '''3606h'''. If ROTARNOCK 100-PB should be used as replacement for '''ROTARNOCK 4-PB''', the Ident-No. can be changed in WINLOC 32 with the key combination '''"Strg + N"''' into the Ident No.: '''3231h'''. So there have to be done no changes in an existing project. '''Note:''' If the logic function is used for ROTARNOCK 4-PB, then this logic function has to be activated for ROTARNOCK 100-PB. Therefore is needed a chargeable release code. '''Attention:'''This release code is tied the serial-no. and can not be used for any other cam control. <br /><br />
*'''As replacement for ROTARNOCK 1-PB and 2-PB''': If ROTARNOCK 100-PB should be used as a replacement for '''ROTARNOCK 1-PB''' or as a replacement for '''ROTARNOCK 2-PB''' , the existing project has to be changed. All neccessary information maybe found under: [[Geräteaustausch ROTARNOCK 1-PB und ROTARNOCK 2-PB]].<br />
<br />
=== ROTARNOCK 100-PN (PROFINET) ===<br />
ROTARNOCK 100-PN (PROFINET) ist '''always''' PROFINET-Slave and features a serial RS232-interface and a PROFINET-interface.<br />
{| class="wikitable"<br />
|+Version<br />
|-<br />
! Interface - Fieldbus !! Interface-serial !! Protection class !! Outputs !! Art.-No.<br />
|-<br />
| PROFINET || RS232 || IP65 || 12 + (32 software outputs)|| V3795<br />
|}<br />
The [[#Weblinks|'''GSDML-file''' (GSDML-V2.3-Deutschmann-ROTARNOCK 100-PN-20150317-160500.xml)]] and a [[#Weblinks|'''S7-example project''']] are available for download on our homepage.<br />
<br />
== Weblinks ==<br />
*[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/ROTARNOCK%20100/English/ROTARNOCK_100_e.pdf Manual for ROTARNOCK 100] (PDF-file)<br />
*[https://www.deutschmann.de/downloads/Support/Profibus/R100.GSD GSD-file for ROTARNOCK 100-PB] <br />
*[https://www.deutschmann.de/downloads/Support/Profinet/GSDML-ROTARNOCK100.zip GSDML-file for ROTARNOCK 100-PN]<br />
*[https://www.deutschmann.de/downloads/Support/S7/Nockenschaltwerk_CamSwitch/Nsw_v2_e.zip S7-example project PROFIBUS] (ZIP-file)<br />
*[https://www.deutschmann.de/downloads/Support/S7/Nockenschaltwerk_CamSwitch/R100-PN_example.zip S7-example project PROFINET] (ZIP-file)<br />
*Manual [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/DIVERS/Kommunikationsprofil/Kommunikationsprofil%20englisch/komm_profil_e.pdf Communication profile for Deutschmann cam controls] (PDF-file)<br />
*Manual [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/NSW%20mit%20Feldbus-CamControlWithFieldbusConnection/English/CamControlsWithFieldbusConnection.pdf Cam controls with fieldbus connection] (PDF-file)<br />
*Manual [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/L100,%20200,%20R80,%20100%20mit%20Feldbusanbindung-WithFieldbusConnection/English/L-R%20mit%20Feldbus-e.pdf ROTARNOCK 100 with fieldbus connection] (PDF-file)</div>Reithhttps://wiki.deutschmann.de/index.php?title=ROTARNOCK_100_(English)&diff=3338ROTARNOCK 100 (English)2017-12-14T15:49:06Z<p>Reith: </p>
<hr />
<div>[[Datei:ROTARNOCK 100.jpg|thumb|ROTARNOCK 100]]<br />
ROTARNOCK is a cam control integrated in the housing of an absolute encoder.<br />
== Configuration ==<br />
By factory setting '''all''' ROTARNOCK 100 Cam controls are configured as follows:<br />
*Virtual Encoder resolution: '''4096'''<br />
*Idle time: '''Bitwise'''<br />
This configuration set by default may be changed by using [[TERM 6 (English)|TERM 6]] or the software [[WINLOC 32 (English)|WINLOC 32]].<br />
== Programming ==<br />
ROTARNOCK 100 can be programmed by TERM 6 or [[TERM 24 (English)|TERM 24]] or the software WINLOC 32. In the PROFIBUS-Version the programming is done via PROFIBUS.<br />
<br />
== device versions ==<br />
=== ROTARNOCK 100 ===<br />
ROTARNOCK 100 features the serial RS232-interface '''or''' a RS485-([[DICNET (English)|DICNET]]) Interface. <br />
{| class="wikitable"<br />
|+versions<br />
|-<br />
! Interface !! protection class !! outputs !! Art.-No.<br />
|-<br />
| RS232 || IP54 || 16 || V3431<br />
|-<br />
| RS485 || IP54 || 16 || V3413<br />
|-<br />
| RS232 || IP65 || 16 || V3433<br />
|-<br />
| RS485 || IP65 || 16 || V3432<br />
|}<br />
At devices with a RS485-(DICNET) interface the DICNET-addresses have to be set via the 9 pol. D-Sub plug '''(for IP54)''' resp. set via the rotary switch '''(for IP65)'''. '''Only''' the DICNET-Addresses '''0 ... 15''' (decimal) are supported. <br /><br />
'''Note:''' At the '''first and the last''' device within DICNET has to be set the bus termination resistor. Therefore '''DICNET+''' has to be connected with '''R+''' and '''DICNET-''' has to be connected with '''R-'''. For the IP54-version this can be done directly in the 9 pol. D-Sub plug. For the IP65-version this has to be done in the mating plug to the 28 pol. round plug. <br />
=== ROTARNOCK 100-PB (PROFIBUS) ===<br />
ROTARNOCK 100-PB (PROFIBUS) is '''always''' PROFIBUS-Slave and contains the serial RS232-interface and a PROFIBUS-interface<br />
{| class="wikitable"<br />
|+Versions<br />
|-<br />
! Interface-Fieldbus !! Interface-serial !! protection class !! outputs !! Art.-No.<br />
|-<br />
| PROFIBUS || RS232 || IP54 || 16 + (32 software outputs)|| V3406<br />
|-<br />
| PROFIBUS || RS232 || IP65 || 12 + (36 Software outputs) || V3434<br />
|}<br />
For ROTARNOCK-100 two modes are selectable through WINLOC32 via the PROFIBUS-Interface.<br />
* '''S7-Modus''' (factory setting): For Operation at a Simatic S7 and for use of the [[data component simulator]].<br />
* '''Communication Profile Modus''': For Operation via [[#Weblinks|Communication profile for Deutschmann Cam Controls]].<br /><br />
The PROFIBUS-Address (Slave-ID) is set by default to '''126''' (decimal). The [[#Weblinks|'''GSD-file''' (R100.GSD)]] and a [[#Weblinks|'''S7-example project''']] are available for download on our homepage. Further Information regarding ROTARNOCK 100-PB may be found in the manuals [[#Weblinks|"Cam Controls with Fieldbus-Connection"]] und [[#Weblinks|"ROTARNOCK 100 with fieldbus-connection"]].<br />
*'''As replacement for ROTARNOCK 4-PB''': ROTARNOCK 100-PB has the Ident No.: '''3606h'''. If ROTARNOCK 100-PB should be used as replacement for '''ROTARNOCK 4-PB''', the Ident-No. can be changed in WINLOC 32 with the key combination '''"Strg + N"''' into the Ident No.: '''3231h'''. So there have to be done no changes in an existing project. '''Note:''' If the logic function is used for ROTARNOCK 4-PB, then this logic function has to be activated for ROTARNOCK 100-PB. Therefore is needed a chargeable release code. '''Attention:'''This release code is tied the serial-no. and can not be used for any other cam control. <br /><br />
*'''As replacement for ROTARNOCK 1-PB and 2-PB''': If ROTARNOCK 100-PB should be used as a replacement for '''ROTARNOCK 1-PB''' or as a replacement for '''ROTARNOCK 2-PB''' , the existing project has to be changed.<br />
<br />
=== ROTARNOCK 100-PN (PROFINET) ===<br />
ROTARNOCK 100-PN (PROFINET) ist '''always''' PROFINET-Slave and features a serial RS232-interface and a PROFINET-interface.<br />
{| class="wikitable"<br />
|+Version<br />
|-<br />
! Interface - Fieldbus !! Interface-serial !! Protection class !! Outputs !! Art.-No.<br />
|-<br />
| PROFINET || RS232 || IP65 || 12 + (32 software outputs)|| V3795<br />
|}<br />
The [[#Weblinks|'''GSDML-file''' (GSDML-V2.3-Deutschmann-ROTARNOCK 100-PN-20150317-160500.xml)]] and a [[#Weblinks|'''S7-example project''']] are available for download on our homepage.<br />
<br />
== Weblinks ==<br />
*[https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/ROTARNOCK%20100/English/ROTARNOCK_100_e.pdf Manual for ROTARNOCK 100] (PDF-file)<br />
*[https://www.deutschmann.de/downloads/Support/Profibus/R100.GSD GSD-file for ROTARNOCK 100-PB] <br />
*[https://www.deutschmann.de/downloads/Support/Profinet/GSDML-ROTARNOCK100.zip GSDML-file for ROTARNOCK 100-PN]<br />
*[https://www.deutschmann.de/downloads/Support/S7/Nockenschaltwerk_CamSwitch/Nsw_v2_e.zip S7-example project PROFIBUS] (ZIP-file)<br />
*[https://www.deutschmann.de/downloads/Support/S7/Nockenschaltwerk_CamSwitch/R100-PN_example.zip S7-example project PROFINET] (ZIP-file)<br />
*Manual [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/DIVERS/Kommunikationsprofil/Kommunikationsprofil%20englisch/komm_profil_e.pdf Communication profile for Deutschmann cam controls] (PDF-file)<br />
*Manual [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/NSW%20mit%20Feldbus-CamControlWithFieldbusConnection/English/CamControlsWithFieldbusConnection.pdf Cam controls with fieldbus connection] (PDF-file)<br />
*Manual [https://www.deutschmann.de/downloads/Marketing/Anleitung-Instructions/Handbuecher-Manuals/Nockenschaltwerke%20-%20Cam%20Controls/L100,%20200,%20R80,%20100%20mit%20Feldbusanbindung-WithFieldbusConnection/English/L-R%20mit%20Feldbus-e.pdf ROTARNOCK 100 with fieldbus connection] (PDF-file)</div>Reithhttps://wiki.deutschmann.de/index.php?title=Device_Replacement_LOCON_24/48/64&diff=3219Device Replacement LOCON 24/48/642017-04-28T09:10:14Z<p>Reith: </p>
<hr />
<div>Depending on the version, LOCON 24, LOCON 48 and LOCON 64 as well as the corresponding PM-Versions may be replaced by a corresponding [[LOCON 24 (English)|LOCON 24]] (-PM) oder [[LOCON 48 (English)|LOCON 48]] (-PM) or [[LOCON 100 (English)|LOCON 100]] and an extension module [[LOCON 100 (English)#Erweiterungsmodul|LOCON 100-Out I/O32]] or [[LOCON 200 (English)|LOCON 200]] with a corresponding number of extension modules [[LOCON 200 (English)#Erweiterungsmodul|LOCON 200-Out I/O8]]. ('''Attention:''' For a configuration level step of more then '''8 pieces''' LOCON 200-Out I/O8 is needed in addition a [[LOCON 200 (English)#NT-Modul|NT-Module]]). <br />
In order to ensure a proper and fast replacement, we would need the following information and components:<br />
#The serial-no. or the article-no.(Vxxxx) of the old device has to be known in order to offer a corresponding new device. If the replacement would be done with a new cam control '''without''' control panel (LOCON 24-PM, LOCON 48-PM, LOCON 100 und LOCON 200) then for operation would be the need of [[TERM 6 (English)|TERM 6]] or [[TERM 24 (English)|TERM 24]] or [[WINLOC 32 (English)|WINLOC 32]]-Basic- or comfort version.<br />
#If TERM 6 or TERM 24 is already used, then we have to know the serial-no. of this devices, too, in order to check the compatibilty to the new device.<br />
#For the configuration and programming of a new device with WINLOC32-Basic-or-comfort Version would be needed a corresponding programming cable. '''Note:''' It has to be checked in every single case if this programming cable may be used also for a needed read out of the old device. <br />
#For the configuration of a new device, if needed, you have to use TERM 6 or die WINLOC 32-Basic-or comfort version. <br />
#For the configuration and programming with WINLOC 32-Basic-or-comfort Version, the PC is in need of a real COM-Port. If there exists no more real COM-Port at the PC, then a [[USB-to-RS232 converter]] has to be used.<br />
'''For a corresponding offer please let us know the serial-no. or the article-no. (Vxxxx) of the old device and, if used, the serial-no. of TERM 6 resp. TERM 24.'''</div>Reithhttps://wiki.deutschmann.de/index.php?title=Device_Replacement_LOCON_24/48/64&diff=3218Device Replacement LOCON 24/48/642017-04-28T08:52:09Z<p>Reith: </p>
<hr />
<div>Depending on the version, LOCON 24, LOCON 48 and LOCON 64 as well as the corresponding PM-Versions may be replaced by a corresponding [[LOCON 24 (English)|LOCON 24]] (-PM) oder [[LOCON 48 (English)|LOCON 48]] (-PM) or [[LOCON 100 (English)|LOCON 100]] and an extension module [[LOCON 100 (English)#Erweiterungsmodul|LOCON 100-Out I/O32]] or [[LOCON 200 (English)|LOCON 200]] with a corresponding number of extension modules [[LOCON 200 (English)#Erweiterungsmodul|LOCON 200-Out I/O8]]. ('''Attention:''' For a configuration level step of more then '''8 pieces''' LOCON 200-Out I/O8 is needed in addition a [[LOCON 200 (English)#NT-Modul|NT-Module]]). <br />
In order to ensure a proper and fast replacement, we would need the following information and components:<br />
#The serial-no. or the article-no.(Vxxxx) of the old device has to be known in order to offer a corresponding new device. If the replacement would be done with a new cam control '''without''' control panel (LOCON 24-PM, LOCON 48-PM, LOCON 100 und LOCON 200) then for operation would be the need of [[TERM 6 (English)|TERM 6]] or [[TERM 24 (English)|TERM 24]] or [[WINLOC 32 (English)|WINLOC 32]]-Basic- or comfort version.<br />
#If TERM 6 or TERM 24 is already used, then we have to know the serial-no. of this devices, too, in order to check the compatibilty to the new device.<br />
#For read-out of the old device and, if needed, the configuration and programming of a new device with WINLOC32-Basic-or-comfort Version would be needed a corresponding programming cable. '''Note:''' It has to be checked in every single case if this programming cable may be used also for a needed read out of the old device. <br />
#For the configuration of a new device, if needed, you have to use TERM 6 or die WINLOC 32-Basic-or comfort version. <br />
#For the configuration and programming with WINLOC 32-Basic-or-comfort Version, the PC is in need of a real COM-Port. If there exists no more real COM-Port at the PC, then a [[USB-to-RS232 converter]] has to be used.<br />
'''For a corresponding offer please let us know the serial-no. or the article-no. (Vxxxx) of the old device and, if used, the serial-no. of TERM 6 resp. TERM 24.'''</div>Reithhttps://wiki.deutschmann.de/index.php?title=Device_Replacement_LOCON_24/48/64&diff=3217Device Replacement LOCON 24/48/642017-04-28T08:51:26Z<p>Reith: </p>
<hr />
<div>Depending on the version, LOCON 24, LOCON 48 and LOCON 64 as well as the corresponding PM-Versions may be replaced by a corresponding [[LOCON 24 (English)|LOCON 24]] (-PM) oder [[LOCON 48 (English)|LOCON 48]] (-PM) or [[LOCON 100 (English)|LOCON 100]] and an extension module [[LOCON 100 (English)#Erweiterungsmodul|LOCON 100-Out I/O32]] or [[LOCON 200 (English)|LOCON 200]] with a corresponding number of extension modules [[LOCON 200 (English)#Erweiterungsmodul|LOCON 200-Out I/O8]]. ('''Attention:''' For a configuration level step of more then '''8 pieces''' LOCON 200-Out I/O8 is needed in addition a [[LOCON 200 (English)#NT-Modul|NT-Module]]. <br />
In order to ensure a proper and fast replacement, we would need the following information and components:<br />
#The serial-no. or the article-no.(Vxxxx) of the old device has to be known in order to offer a corresponding new device. If the replacement would be done with a new cam control '''without''' control panel (LOCON 24-PM, LOCON 48-PM, LOCON 100 und LOCON 200) then for operation would be the need of [[TERM 6 (English)|TERM 6]] or [[TERM 24 (English)|TERM 24]] or [[WINLOC 32 (English)|WINLOC 32]]-Basic- or comfort version.<br />
#If TERM 6 or TERM 24 is already used, then we have to know the serial-no. of this devices, too, in order to check the compatibilty to the new device.<br />
#For read-out of the old device and, if needed, the configuration and programming of a new device with WINLOC32-Basic-or-comfort Version would be needed a corresponding programming cable. '''Note:''' It has to be checked in every single case if this programming cable may be used also for a needed read out of the old device. <br />
#For the configuration of a new device, if needed, you have to use TERM 6 or die WINLOC 32-Basic-or comfort version. <br />
#For the configuration and programming with WINLOC 32-Basic-or-comfort Version, the PC is in need of a real COM-Port. If there exists no more real COM-Port at the PC, then a [[USB-to-RS232 converter]] has to be used.<br />
'''For a corresponding offer please let us know the serial-no. or the article-no. (Vxxxx) of the old device and, if used, the serial-no. of TERM 6 resp. TERM 24.'''</div>Reith