Professional Documents
Culture Documents
Dukane: Dukane Ethernet/Ip To Iqlinq Converter
Dukane: Dukane Ethernet/Ip To Iqlinq Converter
Document Overview
EtherNet/IP is an implementation of the CIP (Common Industrial Protocol) over Ethernet using a
TCP/IP network. EtherNet/IP (referred to here as EIP) is supported natively on many modern
Allen-Bradley PLCs. iQLinQ (referred to here as IQL) is a proprietary serial protocol developed
by Dukane I.A.S. for controlling the iQ series of ultrasonic generators. The EIP/IQL Converter
acts as a bridge between the two protocols and greatly decreases the programming effort
needed to control an iQ generator from a PLC. The programmer interacts with the iQ over
EtherNet/IP, needing no knowledge of the iQLinQ protocol details.
Some models of iQ Generators have built in EIP support, there is no need for the EIP/IQL
converter product. In these generators, the PLC interface is identical to the EIP/IQL converter.
This document will provide the controls engineer with a detailed description of the EIP/IQL
converter. It assumes the reader has a general understanding of TCP/IP networks and
PLC/PAC programming. Some basic EIP information is given throughout the document, consult
www.odva.org for more.
Table of Contents
1. EIP/IQL Converter Overview .......................................................................................................4
1.1 Capabilities .............................................................................................................................. 4
1.2 Performance ............................................................................................................................ 5
1.3 Physical Properties .................................................................................................................. 5
Table1-1: EIP/IQL Converter Physical Interfaces ........................................................................... 5
2. Getting Started ...........................................................................................................................6
2.1 Setting up the AOI .................................................................................................................... 6
3. Configuring the EIP/IQL Converter...............................................................................................9
3.1 Command Line Interface ......................................................................................................... 9
Table 3-1: EIP/IQL Converter Configuration Commands ............................................................. 9
3.2 Configuration Options ........................................................................................................... 11
3.2.1 Network Settings ............................................................................................................ 11
3.2.2 iQLinQ Settings ............................................................................................................... 12
4. Configuring the iQ Generator .................................................................................................... 13
5. Configuring the PLC for Implicit (I/O) Messaging ........................................................................ 14
5.1 Implicit Message Assembly Definition ................................................................................... 15
Table 5-1: Probe Input Assembly Byte Map ............................................................................. 15
Table 5-2: Probe Input Assembly with MPC Byte Map ............................................................. 15
Table 5-3: System Status Output Bit Mask Definition ............................................................... 16
Table 5-4: Error Status Bit Mask Definition .............................................................................. 19
Table 5-5: Cycle Part Status Bit Mask Definition....................................................................... 21
Table 5-6: Generator State Index Definition ............................................................................ 21
Table 5-7: Probe Output Assembly Byte Map .......................................................................... 23
Table 5-8: Probe Output Assembly with MPC Byte Map .......................................................... 25
5.2 Configuring Allen Bradley PLCs for Implicit Messaging .......................................................... 28
5.3 Configuring Omron PLCs for Implicit Messaging .................................................................... 31
1.1 Capabilities
The EIP/IQL Converter provides for status and control of iQ Series Probe generators in an easy-to-
implement package for automation. Over the network, an EtherNet/IP master/scanner enabled PLC/PAC
(referred to as PLCs for the remainder of this document) can read various status bits and real time
operating values, start ultrasonic welding cycles, ultrasonic test cycles, and read and make changes to
process control parameters (if attached to a properly optioned iQ model).
The capabilities of the EIP/IQL converter are dependent upon the iQ model it is attached to. Other factors
like Mother Board (abbreviated to MB in this document) and Front Panel (abbreviated FP in this
document) firmware versions also affect the capabilities of the system. For example, the PLC will not be
able to use weld control parameters (weld time, weld energy) unless the iQ it is controlling has been
purchased with those options.
Select models also support local storage of process setup parameters and the ability to switch between
those stored setups via EIP. This removes the requirement for the PLC logic to push down new
parameters for each weld. These same models also support switching of probe selection via EIP when
paired with a Multi-Probe Controller (MPC) controller (if equipped).
Multi-Probe Controller (MPC) control over EIP is only supported by MB firmware versions v3.11.05 and
greater (this feature was added in v1.05 of the EIP/IQL converter). For generators with firmware versions
less than v3.11.05, hard digital I/O signals (available on the generators “System Status” connectors) must
be used to drive the Remote Setup Bits on the generator inputs and monitor status of the MPC system.
See the iQ generator user manual for details. Any generator with v3.00.00 or greater can be upgraded to
v3.11.05 (or greater).
Loading, storing, and switching setups is supported over EIP only in EIP/IQL v1.05 and greater when
paired with MB firmware v3.11.05 and greater. Using firmware versions earlier than that, the PLC must
store any settings and apply them when appropriate (for example, when switching MPC probes).
iQ Series Press generators are generally supported by the EIP/IQL converter box, this includes the iQ ES
Blank Front Panel, iQ ES Color LCD Front Panel, and the iQ LE Graphic Front Panel models (when
connected to a press). Please contact Dukane for information regarding limited press support.
The EIP/IQL converter requires the iQ generator to have MB firmware version of v2.62 or greater. iQ MB
firmware version v2.64 and greater support locking the Front Panel interface (if present) from making any
local changes. This feature is also generally available via a hard digital input on the System Inputs
connector (model dependent).
EIP/IQL converter firmware version v1.01 or greater is needed to support Omron PLCs and “auto stop”
functionality over the EIP Implicit Connection.
The EIP/IQL converter does NOT support the optional EtherNet/IP Address Conflict Detection (ACD),
QuickConnect, or SNMP features. The converter supports a single exclusive owner connection.
1.2 Performance
The minimum supported RPI is 10ms, and can be increased from there in 10ms increments. Using the
largest RPI acceptable for your application is a good way to reduce EIP network congestion and ensure
reliable operation. The data throughput bottleneck in the system is the RS232/IQL side of the converter,
with a best case update time of about 15ms. Higher RPI times reduce the load on the PLC and increasing
the setting may allow more EIP devices to be controlled (in the case of bandwidth bound system) by the
PLC.
Given the two communication loops (EIP side and IQL side), worst case delay is 25ms. Worst case jitter
is also in the range of 25ms in this scenario.
An iQ LS generator with MB firmware v3.10.00 or greater, paired with an EIP/IQL converter with firmware
v1.01 or greater, will yield the best performance as the RS232 baud rate of 115,200 bps is supported.
iQ LS-E models yield even better performance due to a 250,000 bps internal serial connection to the MB.
iQ Auto Plus models yield the best performance, with zero serial communication overhead due to the EIP
feature being implemented directly on the MB itself.
Generators without Time or Energy options purchased will also have slightly poorer IQL loop time due to
some specific limitations in the IQL protocol. More IQL messages need to be exchanged than with “full
featured” models. iQ Auto Plus models would not suffer this degradation.
2. Getting Started
The very first thing to do when setting up your PLC project is to determine if you application requires the
ability to set and read process control parameters. You will need this ability if you intend the generator
to control the duration of the weld, this is called “iQ System Control”. If you intend to control the
duration of the weld via your PLC logic itself, this is called “Automation Control”. Note that the lowest
tier of generator options does not support “iQ System Control” and require the PLC to control the
duration of the ultrasonic output. There is much less base logic setup needed for “Automation Control”,
and if you do not need “iQ System Control” it will save work. “Automation Control” only requires that
an Implicit Connection be setup, no Explicit Messaging is required, see Section 5 and the provided
“Automation Control” demo application.
If you do require Explicit Messaging for parameter exchange, the provided RsLogix 5000 “System
Control” demo application provides a good starting place, its use is HIGHLY recommended if you are
using an AB PLC. This recommendation is especially strong if you intend on controlling multiple
generators from the same logic program. The demo contains a UDT (User Defined Type) called
“IQ_PROBE_UDT” that represents all of the information that can be exchanged between the PLC and
generator. It also includes an AOI (Add-On Instruction) called “iQ_PROBE_MPC_AOI” that handles all of
the logic required for Explicit Messaging.
multiple AOI calls, each configured with their own set of parameters (Implicit Message / IO Connection
Path, “iQ_PROBE_UDT” instance, MESSAGE tags, and the below described ancillary function calls. See
the demo for examples).
Other requirements to use the AOI are a GSV instruction to provide module status to the AOI and CPS
instructions to synchronously copy the UDT’s input and output memory to the Implicit Connection’s
input and output memory. The CPS instruction for the input must immediately precede the AOI in the
logic. The CPS for the output should happen only once per logic loop, after the AOI and any external
logic has updated its values. The members of the UDT and logic of the AOI are extensively commented,
please refer to them while reading the remainder of this document.
The UDT parameter of the AOI provides the interface between the generator and your PLC logic. The
UDT contains several sub-UDT’s that represent the data sent and received in an Explicit Message (the
size and ordering of the members of the sub-UDT’s is critical and MUST match the ordering in the
Explicit Message themselves). There are also several DINT’s that provide message and connection
control and status.
The “connection ready” BOOL of the UDT indicates that the IQL connection to the generator is ready and
that the AOI has populated the UDT with parameter data from Explicit Message “gets”. The Implicit
connection is also usable in this state. The AOI will clear the memory used for the Output Assembly
when this bit is not set. This bit will clear while the AOI is performing a “get all” due to a “setup
refreshed” or change in setup number. The AOI uses the “Clear Setup Refreshed” bit of the Output
Assembly for the “setup refreshed” handshake mechanism. External logic should not overwrite this bit.
The “get_assembly_msk” member is a bit masked DINT, with a bit-per-assembly defined. A rising edge
on one of these bits will cause a “Get_Attribute_Single” message for that assembly to be sent. The
corresponding sub-UDT will be populated with the results if the corresponding bit in the
“get_done_msk” is set. If the corresponding bit in the “get_err_msk” is set, the message failed and the
contents of the sub-UDT are not updated. These “done” and “error” masks are cleared upon the start of
new Explicit Message.
Similarly, there is a “set_assembly_msk” member that does the same for “Set_Attribute_Single”
messages with corresponding “set_done_msk” and “set_err_msk”. Upon a failed “set”, the AOI will
automatically issue a “get” for that assembly, thereby repopulating the sub-UDT of concern. The AOI
will not issue any “set”s upon it own logic, all “set”s must originate from external logic.
The AOI will automatically retrieve the results of a Test Scan upon completion. The Test Scan Result is
cleared upon a rising edge of the “Run Test Scan” bit of the output assembly. Once the Test Scan is
completed, the AOI issues a “get” for the “Test Scan Result Assembly”, a non-zero value indicates
success and the optimal frequency to be used for the Free Run Frequency parameter. The AOI does NOT
automatically apply this setting, as it is typical to provide a human user with the option to apply the
result or not. This logic is left external to the AOI.
The user interacts with the EIP/IQL converter via a command line interface (CLI) using a terminal
emulator program such as HyperTerminal or TeraTerm (recommended) over the serial port. Using the
CLI, the user can issue commands to the device, such as changing settings and displaying status
information, over a text console command prompt.
The Auto Plus, and other iQ models with built in Ethernet/IP, may also have a RS232 serial connection
that can be used to configure the settings pertinent to Ethernet/IP. These serial connections support both
IQL operation and the CLI, they operate at the same 57600 bps as the EIP/IQL converter. However,
these connections default to “IQL mode” and require the ESC key to be held in the terminal emulator in
order to activate the Command Line Interface. Alternatively, a convenient PC based application is
available to change these settings via the USB connection, contact your salesman for details.
Commands are issued by typing the name of the command into the terminal emulator program and hitting
the “Enter” key. For example, to display a list of available commands, you would type “help” (without the
quotes), hit the enter key, and a screen similar to the following should be displayed.
The “EIP>” on the left side of the screen indicates that the module is ready to take a command. If the
prompt is not visible hit the Enter key without typing a command, this will elicit a blank prompt. If this does
not work, check your power and serial connections and the serial port configuration of your PC.
All commands are case sensitive and in lower case (“Help”, “HELP”, “HeLp” are not the same as “help”).
The up and down arrow keys will cycle through your command history. The left and right arrow keys will
move the edit position of your cursor. The “Backspace” key will remove characters (the “Delete” key is not
supported!). The “Enter” key submits the command to be processed.
A “1” in the “DHCP” row indicates that DHCP is enabled; a “0” would indicate that it is disabled.
These settings are changed by running the “net” command with a parameter of “edit”, by typing “net
edit” (“net” SPACE “edit” without quotes) and hitting Enter. This will display the list of settings, one line
at a time (one setting per line) with the ability to edit the values individually using the “Backspace” key to
delete characters, and the left/right arrow keys to navigate within the value. The “Enter” key accepts the
value and moves on to the next setting. Once a value is accepted there is no way to “backup”, you must
re-run the “net edit” command. Once all values are accepted, they will automatically be saved to non-
volatile memory in the EIP/IQL converter. The “net reset” command will restore all network settings to
their factory defaults.
By default, DHCP is enabled and will acquire the IP address, network mask, and default gateway settings
from the DHCP server on the network every time it powers up. When DHCP support is enabled, the other
network settings listed by the “net” command are ignored. If a DHCP server cannot be contacted, the
EIP/IQL converter uses the AUTO-IP protocol to generate these settings (addresses in the range of
169.254.XXX.XXX indicate an AUTO-IP assigned address). The current network addresses can be
viewed by using the “net” command.
If the EIP/IQL converter acquires an IP address from DHCP, the converter (along with its IP address) will
be visible from a PC running RSLinx on the same network subnet. However, this IP address might be
different every time the EIP/IQL converter requests one from the DHCP server, so this address should not
be used as a hardcoded value in PLC program logic.
While convenient in a corporate network environment, DHCP is not practical for an EtherNet/IP network
unless the DHCP server is tightly controlled. Once the user disables DHCP, the EIP/IQL converter will
use the static addresses listed/edited with the “net” command. Please note these settings as they will be
required during the PLC configuration phase, with DHCP disabled, this static IP will be hardcoded into
PLC program logic and I/O configuration. Sections 4 and 6 will cover these settings.
The only settings pertinent to the iQLinQ interface concern the baud rate of the serial port, this is
accesses by using the “net edit” command. By default, iQ ultrasonic generators run their J4
“Configuration” serial port at 57600 bps. The EIP/IQL converter also uses 57600 bps by default on its “iQ
LinQ” port. The user should not have a reason to change the default baud rate unless there are problems
connecting to a generator (run the “iql” terminal command to get the IQL connection state).
EIP/IQL converter firmware v1.01 introduced an automatic baud rate upgrade mechanism when
connected to an iQ generator with MB firmware v3.10.00 or greater. The EIP/IQL converter will increase
the baud rate to 115200 bps from 57600 bps when connected to a qualifying unit only if the “IQL BAUD
RATE” setting is default (57600 bps) and the “BAUD UPDATE” setting is 1 (default). The user should only
disable the “BAUD UPDATE” setting (via the ‘env edit” command) if communication problems arise. If the
generator has MB firmware less than v3.10.00, the “BAUD UPDATE” setting is not significant. A reboot of
the EIP/IQL converter may be required to apply any changes to the baud rate settings.
iQ LS character LCD front panel models (model numbers: XXHBXXX-XB, XXHBXXX-XE, XXVBXXX-XB,
and XXVBXXX-XE (‘X’ denotes any character)) must be placed into “External Control Mode” or “Serial
Control Mode” in order for the EIP/IQL converter to work properly. Under certain conditions, the EIP/IQL
converter can detect this condition and will turn on the “FAULT” LED and set the IQL_ERROR bit in the IO
data of the EIP connection, use the TUI “iql” command to get more information on the current IQL
connection.
The iQ LS-E models must have their network settings configured via the “INFO” -> “ADVANCED
SETTINGS” menu.
The Auto Plus models must have their network settings configured via the Auto Plus PC configuration
utility.
The EIP/IQL converter has a minimum RPI of 10ms. EIP networks with many nodes and low RPI’s should
consider using a managed switch with IGMP snooping, which lowers the networking burden of the
individual nodes as compared to a standard unmanaged “dumb” switch. The controls engineer should
consult the “EtherNet/IP Infrastructure Guidelines” document provided on the ODVA website before
choosing a network switch. As a rule of thumb, networks with 10 or more total nodes (including the PLC
and HMI) or control networks integrated into enterprise networks should use a managed switch with IGMP
snooping.
The input assembly represents the iQ generator’s outputs, these are read only values. The input
assembly is constructed from an array of DINTs (32 bit elements).
The output assembly represents the iQ generator’s inputs, these are write only values. The output
assembly is constructed from an array of DINTS. Zero’s should be written to all unspecified bits, future
firmware versions may use these bits and this will ensure backward compatibility to existing PLC logic.
The PLC must be configured to use a specific input assembly and a specific output assembly, different
input/output assembly pairs yield different features. For example, the weld process parameter setup
and MPC probe selection feature is enabled by selecting input/output assemblies that support those
features. These features are not available when a different input/output assembly pair is used when
configuring the connection.
0 System Status Outputs See below for System Status Output Bit Mask Definition
1 System Error Status See below for Error Status Bit Mask Definition
Index representing the current state of the generator. See below for
Generator State Index Definition. Note that not all of these values
2 Generator State
are significant to every generator model; many are applicable to
Press Generators only. They are included here for completeness.
5 Real-Time Power The current driven power of the stack in units of 0.1 W
See below for Cycle Part Status Bit Mask Definition (not updated for
7 Cycle Part Status
a test cycle)
Total Weld Time of the last cycle, units of mS (not updated for a test
8 Cycle Weld Time
cycle or continuous cycles for MB versions less than v3.00)
Peak Weld Power of last cycle, units of 0.1W (not updated for a test
9 Cycle Weld Peak Power
cycle)
Total Weld Energy of last cycle, units of 0.1J (not updated for a test
10 Cycle Weld Energy
cycle)
11 RESERVED RESERVED, ignore.
Note that this assembly is only valid for an Implicit Connection when paired with the Probe Output
Assembly (instance number 102 / 0x66).
0 System Status Outputs See below for System Status Output Bit Mask Definition
1 System Error Status See below for Error Status Bit Mask Definition
Index representing the current state of the generator. See below for
Generator State Index Definition. Note that not all of these values
2 Generator State
are significant to every generator model; many are applicable to
Press Generators only. They are included here for completeness.
5 Real-Time Power The current driven power of the stack in units of 0.1 W
See below for Cycle Part Status Bit Mask Definition (not updated for
7 Cycle Part Status
a test cycle)
Total Weld Time of the last cycle, units of mS (not updated for a test
8 Cycle Weld Time
cycle or continuous cycles for MB versions less than v3.00)
Peak Weld Power of last cycle, units of 0.1W (not updated for a test
9 Cycle Weld Peak Power
cycle)
Total Weld Energy of last cycle, units of 0.1J (not updated for a test
10 Cycle Weld Energy
cycle)
PROG_STATUS_1 Reflects the state of the generator’s Programmable Status Output 1, if equipped.
Input_Assembly[0].0 Added in EIP/IQL v1.05, available since initial release of iQ Auto Plus and iQ LS-E.
0x00000001 Available on all v3.00.00+ MB firmware.
PROG_STATUS_2 Reflects the state of the generator’s Programmable Status Output 1, if equipped.
Input_Assembly[0].1 Added in EIP/IQL v1.05, available since initial release of iQ Auto Plus and iQ LS-E.
0x00000002 Available on all v3.00.00+ MB firmware.
GOOD_PART Part Status Output associated with Process Limits. When the cycle parameters
Input_Assembly[0].2 recorded during the previous welding cycle do not exceed the programmed suspect or
0x00000004 bad part limit, it is a GOOD PART.
BAD_PART Part Status Output associated with Process Limits. BAD PART occurs when the cycle
Input_Assembly[0].3 parameters recorded during the previous cycle are outside the programmed bad parts
0x00000008 limit
SUSPECT_PART Part Status Output associated with Process Limits. SUSPECT PART occurs when the
Input_Assembly[0].4 cycle parameters recorded during the previous cycle are outside the programmed
0x00000010 suspect part limits.
TRIGGER_STATUS
The Trigger has been made (only significant for probe generators when using Trigger-
Input_Assembly[0].6
by-Power).
0x00000040
AVERAGE_OVERLOAD
Power from ultrasonic stack sent to the part exceeds the generator’s power rating for
Input_Assembly[0].7
the given amplitude.
0x00000080
PEAK_OVERLOAD
Currents internal to the generator exceeded a safe range. This usually indicates a bad
Input_Assembly[0].8
stack/transducer or abusive weld cycle conditions.
0x00000100
CURRENT_LOOP_FAULT
A remote analog input card is present and it is outside of its 4-20 mA current loop
Input_Assembly[0].9
range.
0x00000200
US_STATUS
Ultrasound voltage is actively being produced. The system is actively delivering
Input_Assembly[0].10
ultrasonic power to the attached load.
0x00000400
IN_HOLD
Input_Assembly[0].11 The generator is in the “Hold” phase of the cycle
0x00000800
POWER_OK
Input_Assembly[0].12 The AC power line voltage is within acceptable limits.
0x00001000
READY
The generator is able to start producing ultrasound voltage. Output signal will activate
Input_Assembly[0].13
only when the system is ready to activate ultrasound or begin a weld cycle.
0x00002000
There was a fault during the last cycle, this will self clear when another cycle starts.
ANYFAULT
Generator faults that will activate the Any Fault: Overload(Average, Peak or
Input_Assembly[0].14
Frequency), Over temperature fault, System Power Fault. Over temperature and
0x00004000
system power faults are not clearable user-clearable and reset themselves once the
fault condition subsides. Anyfault will also be set when an analog remote control card
is present and enabled and the 4-20ma signal is out of range.
The generator is ONLINE and can start a welding cycle and activate the ultrasound
ONLINE output when READY status is asserted. On iQ Auto and iQ Auto Plus model, this bit
Input_Assembly[0].16 reflects the state of the “Enable In” input. On other iQ models, ONLINE is controlled
0x00010000 via buttons on the unit’s Front Panel (and do not have an input on the System Status
Input connector).
TOP_OF_STROKE
(Press only) activates when the press/thruster head is at the top of its cycle stroke
Input_Assembly[0].17
position.
0x00020000
E-STOP_ACTIVE (v3.00.00 MB firmware and above, if equipped with proper hardware) The generator is
Input_Assembly[0].18 “E-Stopped”, E-Stop is available on press models and iQ LS and LS-E models
0x00040000 equipped with a Remote Amplitude Option card.
IN_CYCLE
Input_Assembly[0].19 The generator is not idle and is running a cycle.
0x00080000
IN_AFTER_BURST The generator is in the “After-Burst” phase of the cycle. In some applications the
Input_Assembly[0].20 welded part can stick to the horn as it is retracted from the work piece. Afterburst
0x00100000 prevents this by sending a short burst of ultrasound on the upstroke.
Input_Assembly[0].21
Reserved, ignore.
0x00200000
MPC_READY The MPC controller has finished switching probes and is ready to receive ultrasound
Input_Assembly[0].22 power. Added in EIP/IQL v1.05, available since initial release of iQ Auto Plus and iQ
0x00400000 LS-E. Available on all v3.00.00+ MB firmware.
SETUP_REFRESHED The EIP/IQL converter has finished it’s collection of process control parameters from
Input_Assembly[0].23 the EMB, “Get_Attribute_Single” explicit request will contain valid data. Added in
0x00800000 EIP/IQL v1.05, available since initial release of iQ Auto Plus and iQ LS-E.
UNRECOVERABLE_ERROR
A fault exists that cannot be cleared. Rebooting the generator may clear the fault, if
Input_Assembly[0].24
not please contact Dukane Customer Service.
0x01000000
Supported in iQ Auto Plus v4.01.00 firmware and greater. This indicates that the
CYCLE_START_REJECT
generator received a request to start a cycle, but rejected it for one reason or another.
Input_Assembly[0].25
Typically the reason can be deduced by looking at the Error Status or double checking
0x02000000
Weld Control parameter values.
If set, the EIP/IQL converter has established IQL communication with the generator.
IQL_READY
The data in the Input Assembly is now valid for consumption by the PLC, and the data
Input_Assembly[0].31
in the Output Assembly will now be consumed by the EIP/IQL converter. When this bit
0x80000000
is cleared, the “IQL FAULT” indicator LED will be lit.
Internal Error
An unrecoverable internal error has occurred. Any of these bits being set should be
Input_Assembly[1].0-3
considered a major alarm, sonics will not restart.
0x0000000F
Frequency Overload
(Frequency Lock Failed)
The generator was unable to lock on to the proper ultrasonic frequency of the stack.
Input_Assembly[1].4
0x00000010
Frequency Overload
(Frequency Lock Lost)
The generator was not able to maintain lock on the proper ultrasonic frequency.
Input_Assembly[1].5
0x00000020
Peak Overload (Positive) Currents internal to the generator exceeded a safe range. This usually indicates a bad
Input_Assembly[1].6 stack/transducer or abusive weld cycle conditions. There is no special significance to
0x00000040 “Positive” or “Negative”.
Peak Overload (Negative) Currents internal to the generator exceeded a safe range. This usually indicates a bad
Input_Assembly[1].7 stack/transducer or abusive weld cycle conditions. There is no special significance to
0x00000080 “Positive” or “Negative”.
Average Overload
The ultrasonic power output exceeded the generator’s power rating for the given
Input_Assembly[1].8
amplitude.
0x00000100
Current Loop
Input_Assembly[1].9 A remote analog input card is present and it is out of its 4-20 mA current loop range.
0x00000200
Power Not OK
The AC power line voltage is NOT within acceptable limits. This should be considered
Input_Assembly[1].10
a major alarm, sonics will not restart.
0x00000400
Over Temperature The internal temperatures of the generator are not within acceptable limits. This
Input_Assembly[1].11 should be considered a major alarm; sonics will not restart until the generator has
0x00000800 cooled down.
Over Amplitude Fault This bit will be set if the generator observes the Actual Amplitude to be over 100% in
Input_Assembly[1].12 any Fixed Pulse Width Operating mode. This bit was previously defined as “FORCED
0x00001000 SHUTDOWN” but was never used.
Trigger Failed
The last weld cycle timed-out before the trigger condition was reached. In the case of
Input_Assembly[1].13
a probe generator, only “Trigger-by-Power” is supported.
0x00002000
Trigger Lost Early (non-EPR Press only) The force sensitive trigger switch was made then lost within
Input_Assembly[1].14 100ms.
0x00004000
Latched-On-Bad-Part
Input_Assembly[1].16 The “Latch On Bad Part” feature is enabled and active.
0x00010000
There is an error in IQL communication, either the iQ does not have the proper
firmware revision, it has not been placed in “external control” mode (if required,
IQL_ERROR
implementation is specific to front panel model specific), or there is some other
Input_Assembly[1].31
unrecoverable error. When this bit is set, the “IQL FAULT” indicator LED will be lit. If
0x80000000
both the IQL_READY and IQL_ERROR bits are set, the command line “iql” command
accessible via the EIP/IQL config port will provide more information.
GOOD Part
Input_Assembly[7].0 No Process Limits were violated during the last cycle.
0x00000001
BAD Part
Input_Assembly[7].1 A Bad Limit was violated during the last cycle
0x00000002
Suspect Part
Input_Assembly[7].2 A Suspect Limit was violated during the last cycle
0x00000004
The Generator is in cycle, waiting on the event that will trigger the start of
3 Pre-PreTrigger
sonics before starting the weld cycle. (Press Only).
The Generator is in cycle, has met the trigger condition and is waiting on
5 Trigger Delay the “Trigger Delay” condition to be met before starting sonics and the
weld cycle (Press Only, mutually exclusive to PreTrigger).
The Generator is in cycle, has shut down sonics and performing a hold
10 Dynamic Hold
operation after weld cycle has completed (Press Only).
The Generator is in cycle, has shut down sonics and performing a hold
11 Static Hold operation with no motion after weld cycle has completed (Servo Press
Only).
The Generator has completed the weld cycle and is wating a period of
12 AfterBurst Delay
time before the AfterBurst sonics activation occurs.
The Generator has completed the weld cycle and is running sonics for
13 AfterBurst Duration
the AfterBurst feature.
The Generator is running sonics and performing a stack scan, this is only
14 PreWeld Scan available in certain Frequency Control Mode settings. This is also the
state for a “Test Scan”.
The “Clear Error”, “Auto Stop”, “Run Continuously”, and “Run Test” bits are “level triggered” or
“maintained” inputs. The “Run Weld” bit is a rising edge triggered (a “zero-to-one” transition) or
“momentary” input. The minimum duration of the bit assertions is two RPI periods; however, the proper
means of activating these inputs entails monitoring the Input Assembly for feedback indicating they can be
cleared. For example, it would be safe to deactivate the “Run Weld” bit once the Generator State DINT
leaves “IDLE” or an “In-Cycle” bit goes active.
The “Auto Stop” bit (added with EIP/IQL converter firmware v1.01) is useful to prematurely stop a
controlled weld started by either the “Run Weld” bit here, or the hard auto in signal of the System Inputs
found on J2.
All of the above mentioned bits are mutually exclusive, only one may be active at a time. The EIP/IQL
convert enforces a priority with these bits. “Clear Error” has the highest priority, and a ‘1’ there will cause
all other bits to be interpreted as ‘0’. If “Clear Error” is ‘0’, “Auto Stop” has the next highest priority. A
“Clear Error” or “Auto Stop” during a cycle will shut down ultrasound power. In this event, the rest of the
bits must be cleared to ‘0’ before setting to ‘1’ for them to be honored by the EIP/IQL converter. For the
example of using Auto Stop” while running a controlled cycle, a “0x02 to 0x20 to 0x02” sequence of
values will NOT restart sonics. A “0x02 to 0x20 to 0x00 to 0x02” sequence must be used (each value
must be held a minimum of 2 RPI periods).
The “Run Weld” is only significant when the EIP/IQL converter is connected to an iQ generator with the
“iQ System Control” (weld by time and energy) options purchased and a weld controlling parameter has
been enabled. To use a controlled weld, at least “Weld Time” of the “Probe Process Setup Assembly”
must be non-zero. Therefore, using the “Run Weld” bit requires implementation of EIP Explicit Messages
outlined later in this document. The “Run Continuous” bit will only work when all weld controlling
parameters are not used. See the “Probe Process Setup Assembly” description for more details.
The “Front Panel Lock Out” feature was added in v1.05 of the EIP/IQL converter, and has been available
since initial release of the built in support for the iQ LS-E and iQ Auto Plus models. A value of “00” for
these bits will fall back to the “Front Panel Lock Out” support provided by the explicit IO Control Assembly.
When these bits are non-zero, the “Front Panel Lock Out” support in the IO Control Assembly is ignored.
A value of “01” will disable the feature completely, the FP will not be locked out over EIP or by the hard
System Status Inputs (if equipped). A value of “10” will allow the FP lockout to be controlled via the hard
System Status Inputs (if equipped). A value of “11” will force the FP lockout feature to be enabled.
The “Clear Setup Refreshed” bit was added in v1.05 of the EIP/IQL converter, and has been available
since initial release of the built in support for the iQ LS-E and iQ Auto Plus models. This bit is used in
conjunction with Input_Assembly[0].23 (“Setup_Refreshed”) status bit to form a handshake between the
EIP/IQL converter and the PLC. The a rising edge of the “Setup_Refreshed” status bit informs the PLC
that it should perform an explicit “get” on all pertinent assemblies because a value in one (or all) of them
has changed. This will keep the PLC’s version of the generator setup coherent with the generator.
Setting this “Clear Setup Refreshed” bit tells the EIP/IQL converter to clear the “Setup_Refreshed” bit so
that a subsequent rising edge can be detected and acted upon. THIS BIT MUST NOT BE ALTERED BY
EXTERNAL LOGIC!!!
The “Run Test Scan” bit will initiate a low amplitude scan of the ultrasonic stack. This procedure will
determine the best Free-Run Frequency setting for optimal start up of the stack. Once completed, the
scan result is available in the Test Scan Result Assembly. A non-zero value indicates a successful scan
and the optimal frequency to be used for the Free Run Frequency parameter. The RsLogix demo AOI
will automatically retrieve the test scan result at the end of the test scan.
The “On-The-Fly-Amplitude-Enable” bit is independent of the other bits and can be set or cleared at any
time. The generator has only one weld amplitude setpoint, the EIP/IQL converter exposes access to this
value here in the Output assembly and in the “Probe Regulation Setup Assembly”. Using both
simultaneously is discouraged and confusing. Note that if the “On-The-Fly-Amplitude-Enable” bit is
enabled then cleared, the generator will maintain the last “on the fly” value in the Input Assembly, it will
not automatically revert to the value in the “Probe Regulation Setup Assembly” explicit message. If
amplitude on-the-fly is enabled, the “Weld Amplitude” field of the “Probe Regulation Setup Assembly” is
ignored on a “Set Attribute Single” and is filled in with the on-the-fly value in the reply to “Get Attribute
Single” explicit message request. NOTE: A “Remote Amplitude” 4-20mA input card will dictate the
amplitude regardless of any settings from EIP if the generator is in “Remote Amplitude Mode” and not “iQ
System Amplitude Mode”, If you are having trouble with setting amplitude via EIP, and the generator has
this option card installed, please check these settings from the Front Panel interface. This setting is not
alterable over EIP.
When changing Amplitude on-the-fly, note that the change is not instantaneous. The amplitude changes
at a rate equal to that used during Ramp Up at cycle start. The Ramp Up rate is calculated by dividing the
Weld Amplitude by the Ramp Up time.
For example, starting with 100% Weld Amplitude and a Ramp Up Time setting of 150ms, would yield a
rate of:
100%
RampRate 0.667 %
150ms ms
Changing from that starting 100% setpoint to 20% would therefore require:
(100% 20%)
RampTime 120ms
0.6667 % ms
Changing again from 20% to 60% will only take half as much time because the amplitude is only changing
half as much. The Ramp Rate does not change during a cycle. However, if the cycle were to start at 20%
then the change to 100% will take much longer:
(100% 20%)
RampTime 600ms
20% 150ms
If low starting amplitude with a quick on-the-fly response is required, try shortening the Ramp Up Time.
For example, say empirical testing has shown that a horn/stack handles a 100% 150ms Ramp Up nicely,
in order to have the same Ramp Rate with a 20% amplitude start, the Ramp Up Time would have to be
reduced to 30ms. WARNING: Using exceedingly low Ramp Up Times with high amplitude setpoints may
damage the horn/stack or the generator (particularly if the Free Run Frequency is set far from the
Operating Frequency).
Remember that the Ramp Rate is always re-calculated by the generator at cycle start and is not able to
change until the next cycle. This rate is used to change the amplitude setpoint on-the-fly at a known-safe
rate. If PLC logic varies the amplitude setpoint throughout a cycle, it must reset to the desired starting
amplitude every cycle to yield predictable on-the-fly rates of change.
This assembly provides for setup and MPC probe switching. This assembly can be used to switch setups
even if the MPC controller option has not been purchased. Individual control of setups and probes is
provided for the most flexible configuration and eased setup maintenance when multiple probes are
intended to run identical setups.
See the Probe Output Assembly Byte Map for descriptions of the “EIP Status Inputs” and “Amplitude
Setpoint” fields, they have identical behavior in this assembly.
The “Setup Number” field is the tells the iQ which locally stored setup to use on the new weld cycle. This
feature is only functional when connected to a MB with firmware greater than v3.11.00. Acceptable
values are 1 to 16, values outside that range are ignored. For example, a switch from setup 12 to 0, will
result in setup 12 being used, no setup switch will occur. Probe_Input_with_MPC_Assembly[11] reflects
the currently active setup.
Switching setups causes the EIP/IQL converter to recollect (aka “refresh”) all process control parameters
from the generator, The SETUP_REFRESHED bit (Probe_Input_with_MPC_Assembly[11].23) reflects the
progress of this procedure, no Explicit “Get_Attribute_Single” messages should be sent until this bit is set,
else parameters from the previous setup will be in the response. The “refresh” procedure uses a fair
amount of serial throughput, and if done while a weld cycle is running, will affect the real time response of
changes to bits in the “EIP Input Status” field (and the entire Input Assembly).
From the factory all setups contain the default values and switching between them will not show any
difference in weld behavior. It only makes sense to switch setups with this field if non-default values have
been applied and saved via explicit messages, or a FP interface. See Section 6 on Explicit Messaging
(and specifically Table 6-8) for more details.
The “Probe Number” field is used to select the MPC output to which ultrasonic power will be routed. This
feature is only functional when connected to a MB with firmware greater than v3.11.00, and optioned with
an MPC controller. Values of 1 to 16 are permitted, values outside of that range will be ignored. For
example, a switch from probe 4 to 24 will be ignored, and probe 4 will still be selected.
Probe_Input_with_MPC_Assembly[12] reflects the currently active probe. The “MPC_READY” bit in the
Input Assembly (reflects the ready status of the MPC controller itself, not the generator as a whole) must
be monitored before activating ultrasound after an MPC probe switch.
Now you need to configure the new module using IP address you set in the EIP/IQL converter and the
following info:
Connection Parameters:
NOTE: Starting with EIP/IQL Converter firmware v1.02, the assembly number ranges have been changed
from the 300’s (found in v1.00 and v1.01), to the 100’s to be compatible with Schneider/Modicon PLCs.
Firmware v1.02 does still support the “legacy” 300’s range assembly numbers, so that it is compatible with
existing installations. However, all new installations should use the 100’s range, as found in the v1.02
demo’s on the CD shipped with the EIP/IQL converter. The 300’s range should be considered
DEPRECATED.
NOTE: EIP/IQL converter firmware version v1.00 has a bug that will not allow a proper connection if the
“Use Unicast Connection over EtherNet/IP” option is checked under the “Connection” tab of the above
screen shot. Firmware v1.01 corrects this issue. This checkbox is not present in RsLogix 5000 v17 and
older. It is checked by default in v18 and newer. If your EIP/IQL converter firmware is v1.00, either
contact Dukane for updated firmware (recommended) or uncheck this option. The “Use Unicast
Connection over EtherNet/IP” option can significantly reduce network loading in situations where there are
many EtherNet/IP devices, the devices are running on a non-segregated general purpose network (NOT
RECOMMENDED), or a hub/half duplex switch is used (also NOT RECOMMENDED). If multicast IO
connections must be used, consider using network switches specifically designed for industrial control
networks (IGMP snooping support).
Start the “Network Configurator” application. First, you must install the EDS file associated with the
EIP/IQL converter, see “110-4644_20130416a.eds” (at the time of this writing), by selecting the “EDS File”
menu and then the “Install…” submenu. Browse to the EDS file to install it. Select “No” if prompted to
install the associated icon file. Now the tools are ready to use the EIP/IQL converter, and an entry for it
should appear in the tree of device on the left side of the application under “EtherNet/IP
Hardware”/”Vendor”/”Dukane Corporation”/”EIP/IQL Converter”.
Next add your PLC and an EIP/IQL converter by double clicking the devices in the tree, or drag-dropping
them to the “network” pane on the right.
Now change the IP addresses for each device to match your network by right clicking on each icon and
selecting the “Change Node Address…” menu item. NOTE: This does not change the actual IP address of
the PLC or EIP/IQL converter (that is done in CX-Programmer and via the EIP/IQL converter’s “config”
port, see section 3 of this document), this only changes the address within the network setup, and they
must match the IP addresses of the devices themselves. It is helpful at this point to have the proper IP
addresses already programmed into the devices.
Next, the data tags for the implicit input and output assemblies must be created. This is done by double
clicking on the PLC icon in the right hand pane.
Click the “New…” button to create both input and output tags.
Note that the name given here is the same tag name your PLC logic must use to access the data. Click
the “Regist” button to accept the changes, then the “Close” button to complete (as the application expects
you to enter more than one tag). Repeat the same procedure for the output assembly data tag. If you are
connecting multiple EIP/IQL converter boxes to one network, you must create multiple input/output tag
pairs, one for each EIP/IQL converter box.
There should now be an entry in both the “In – Consume” and “Out – Produce” tabs of the “Tag Sets” tab,
you should now have a valid “Tag Set”. Now select the “Connections” tab, click stylized “down arrow”
button to register the EIP/IQL converter device. Your screen should now look like this:
Double click the IP address that represents the EIP/IQL converter, select the “iQ_Probe_Input” tag on the
input connection dropdown menu and the “iQ_Probe_Output” tag for the output. Ensure “Probe I/O” is
selected for the “Connection I/O Type:” field. If these are not available, the EDS file installation is not
correct. RPI can be set as low as 10ms.
Click “Regist” then click “Close”. The connection tab should now look like:
Click “OK”. You are now ready to connect and download the network configuration. Do this by selecting
the “Network” -> “Connect…” menu item, select the interface then the “network”, hit OK. Right click on the
PLC, and select “Synchronize Entity” from the context menu. Repeat for the EIP/IQL converter, if there
are no errors then everything is set up correctly. Now download the network configuration to the PLC by
selecting the “Network” -> “Download” menu item. If everything completes without error, you can close
“Network Configurator”.
Start CX-Programmer. Open an existing project or start a new one (some familiarity with CX-Programmer
is implied here…). You need to create new global “Symbols” that correlate to the “Tag Set” created in
“Network Configurator”. The Symbols must have the same names as displayed in the “Network
Configurator”: iQ_Probe_Input and iQ_Probe_Output in our running example. You must check the “Net.
Variable” check box and select the appropriate input/output radio button. Select a DINT as the data type,
and click the “Advanced Settings…” button to make it an array of the correct size. Give the tags addresses
appropriate for your PLC (needs to be in the “Data Link Area”). Repeat this for both the input and output
assemblies.
Once this is setup, you can go online and download the program to the PLC. Once the PLC is running,
open “Watch” window and add iQ_Probe_Input[4] and iQ_Probe_Output[0]. If all has gone well (and the
generator is connected, powered up, and configured correctly), changing the value of iQ_Probe_Output[0]
to 1 should start a continuous weld cycle and show a changing value for iQ_Probe_Input[4], “Real Time
Operating Frequency”. PLC program logic can now directly access the implicit connection data as if it
was local I/O.
The connection status should be monitored continually and unconditionally by the PLC logic. When the
module status is not “connected” the PLC logic should zero all data in both the Input and Output Assembly
memory locations. This ensures known safe output values when the EIP/IQL converter obtains a
connection from the PLC. It also ensures that a zero-to-one transition of the IQL_READY bit will not be
missed due to stagnant input data still present from a prior connection. The PLC logic needs to maintain
three states with respect to the end-to-end PLC-to-iQ connection: disconnected, not-ready, running.
The PLC logic must monitor the module connection status. This “Disconnected” state should be
entered any time that the PLC indicates the EIP/IQL converter’s module status is not “connected”.
Disconnected In this state the PLC logic should zero both the Input and Output Assembly data. Once the PLC
indicates that the EIP/IQL converter’s module status is “connected”, the PLC logic should transition
to the “Not Ready” state outlined next.
In the “Not Ready” state, the EIP/IQL converter has accepted the controller’s EIP connection, but
has not yet made an IQL connection to the iQ generator. The data in the Input Assembly is not yet
valid (cleared/zero’d by the EIP/IQL converter until an IQL connection is made) and the data in the
Output Assembly has not been passed to the iQ generator (the PLC logic should ensure the Output
Assembly data is cleared/zero’d in this state). The logic should monitor the IQL_READY bit in the
System Status Output register of the Input Assembly. Once this bit is set, the PLC should
transition to the “Running” state outlined next. The module connection status also needs to be
Not Ready
continually and unconditionally monitored in this state, the logic should transition to the
“Disconnected” state outlined above if the module status is not “connected”.
NOTE: The IQL_READY bit may be set as soon as an EIP connection is established. This is the
case when the generator and EIP/IQL converter are powered on before the controller can make a
connection. Therefore, this “Not Ready” state may be very brief. Conversely, the “Not Ready”
state may exist for extended periods of time, for example in the case of an ESTOP circuit removing
AC power from the iQ generator or a RS232 cable failure.
In the “Running” state, the EIP/IQL converter has made connections to both the PLC and the iQ
generator. This is the state where normal operation takes place, I/O data is valid and Explicit
Messages will be processed. This is the only state where the Output Assembly data is permitted to
Running be non-zero. Both the PLC connection indication and IQL_READY bit must be continually and
unconditionally monitored in this state to ensure proper detection of connection loss. The PLC
logic is to transition to the “Disconnected” state outlined previously if the module status that is not
“connected”, the “Not Ready” state should be entered if the IQL_READY bit returns to zero.
Attribute name
used in GSV, refer
to example.
Module status
codes are displayed
in HEX format.
PLC Logic example using the GSV Instruction from the demo application:
The provided demo PLC and HMI applications implement these concepts; please see their source code
for more details.
EtherNet/IP explicit messaging is meant to transmit infrequent, non-realtime parameter data. The EIP/IQL
converter supports “Assemblies” to be written and read via explicit messaging. All values are written or
read at once, they are transferred as a complete block of data. Therefore the each parameter value within
the assembly data must be valid at the time of a explicit message write. Note that not every parameter
value needs to or will change with every message, only that they ALL must be valid. The initial values
used by the PLC/HMI program (upon power up or reconnection (transition from the “Not Ready” into the
“Connected” state), see Section 6 of this document) should be pulled from the generator with a series of
explicit message reads.
Explicit message “writes” are accomplished using “Set_Attribute_Single” service code, and “reads” are
done with “Get_Attribute_Single” service code. The format/data layout of each assembly is fixed and
identical whether writing or reading. The EIP/IQL converter will return an EIP level error to the PLC if a
parameter value written is not valid, however reads should always succeed. Reads should be serviced by
the EIP/IQL converter as soon as they receive the request, 1-2 ms turnaround. Writes must be passed
down to the MB over the serial port when they are received. This delays the turnaround time of write to
roughly 12-20 ms.
Changes to parameters made via Explicit Messages are not automatically saved. For generator firmware
versions less than v3.00, explicit messages are not permitted while sonics are running and will result in an
error at the EIP level. For firmware versions v3.00 and up, Explicit Messages are permitted during the
weld cycle; the new values are used upon the start of the next cycle.
Some Assemblies accessed via Explicit Messages are only significant when the EIP/IQL converter is
connected to an iQ generator with the “iQ System Control” (weld by time and energy) options purchased.
These include the Probe Process Setup, Probe Process Limit, and Probe Trigger-By-Power Assemblies.
For assemblies containing bit-masked values, all unspecified bits should be ignored on reads and written
zero on writes, future firmware versions may use these bits and this will ensure backward compatibility
to existing PLC logic.
The Probe Process Setup Assembly is only to be used when the EIP/IQL converter is connected to an iQ
generator with the “iQ System Control” (weld by time and energy) options purchased, else any “set” of the
Probe Process Setup Assembly will fail resulting in error code 0x09 “Invalid Attribute Value”. A value of
zero in any field will disable the feature. NOTE: in order for the “Run Continuous” bit of the Output
Assembly to be honored, all weld controlling values must be set to zero. In order for the “Run Weld” bit of
the Output Assembly to be honored, at least “Weld Time” must be non-zero.
The Probe Process Limit Assembly is only to be used when the EIP/IQL converter is connected to an iQ
generator with the “iQ System Control” (weld by time and energy) options purchased, else any “set” of the
Probe Process Limit Assembly will fail resulting in error code 0x09 “Invalid Attribute Value”. Any limit can
be individually disabled by setting its value to zero.
0 – Disabled
0 DINT Trigger By Power Enable
1 – Enabled
The Probe Trigger-By-Power Assembly is only to be used when the EIP/IQL converter is connected to an
iQ generator with the “iQ System Control” (weld by time and energy) options purchased, else any “set” of
the Probe Trigger-By-Power Assembly will fail resulting in error code 0x09 “Invalid Attribute Value”. Also,
Trigger-By-Power does not work with ultrasonic weld cycles started with the “Run Continuous” bit, weld
control parameters and the “Run Weld” bit must be used.
The “Auto-In Mode” bits control the functionality of the Auto_In signal present on the System Status Inputs
(J2). A value of 0x00 will disable the input, a value of 0x01 will put it in “maintained” mode (requiring
activation throughout the entire cycle), a value of 0x10 will put it in “momentary” mode (requiring activation
for 5 msec). Note that “momentary” mode will only start a cycle if there is a weld controlling parameter set
(at least weld time MUST be set).
The “FP Lockout” bit is analogous to the System Status Input available on J2 of the generator. This bit is
only significant with MB Firmware versions v2.64 and greater. Setting this bit to ‘1’ will lock out the front
panel interface, preventing any changes to any parameters from being made there.
FREQ_CTRL_MODE_FIXED_SWEEP 0x03
FREQ_CTRL_MODE_FORCED_FREQ 0x04
FREQ_CTRL_MODE_PRESCAN 0x05
FREQ_CTRL_MODE_FREQ_TRACK 0x06
The Frequency Sweep Amplitude parameter is in units of whole
percentages and only significant in
FREQ_CTRL_MODE_SWEEP,
FREQ_CTRL_MODE_FIXED_SWEEP, and
FREQ_CTRL_MODE_PRESCAN Frequency control modes. At
sonics-start, the generator will ramp amplitude to this
parameter value. This amplitude will be held for the duration of
the sweep. The fixed sweep and prescan modes will interpret
this parameter value as a percentage of maximum pulse width,
delivering a fixed pulse width throughout the sweep duration.
4 DINT Sweep Amplitude
The standard sweep mode will interpret this parameter value as
a percentage of maximum amplitude, causing the generator to
modulate pulse width to obtain regulated amplitude throughout
the sweep duration.
The Frequency Sweep Amplitude parameter value must be
between 1 and 20%. Using an unreasonably high sweep
amplitude may damage the ultrasonic stack.
The rate of amplitude ramp is dictated by
PARAM_AMPLITUDE_SETPOINT divided by
PARAM_RAMP_UP_TIME.
The Advanced Frequency Control parameters should be considered “expert settings” and used with
extreme caution. Incorrect values may damage or destroy the welding equipment.
Destination Setup Setup number to copy to. Values of 1 to 16 are permitted, all
1 DINT
Number others will result in an error.
Available only in v1.05 and greater EIP/IQL converter firmware and v3.11.05 MB firmware. This is a
WRITE ONLY assembly, reads will result in error.
The below screenshots demonstrate the setup for the “Probe Regulation” assembly MSG instructions.
Note that the “Class” and “Attribute” fields will remain the same for every different Assembly definition.
Also note that the “Instance” fields will vary for every different assembly definition. Please see the above
tables for each Assembly definition, each containing the Instance number, total size, and byte mapping.
Note that the “Path” setting on the “Communication” tab of the MSG setup needs to reference the proper
Implicit Message Connection. So it makes sense to set that up (follow Section 5) before configuring any
MSG commands or tags.
In the case of the “iQ_PROBE_MPC_AOI” AOI usage, a preconfigured MSG instruction tag needs to be
instantiated for both the ‘get’ and ‘set’ case. These tags MUST be a controller scope, and each
“iQ_PROBE_UDT” MUST reference individual pairs of distinct tags. Only the “Service Code”, “Class”,
“Attribute”, and “Destination/Source Element” settings are significant when initially configuring these tags.
The “Instance” and “Length” are filled out programmatically by the AOI depending upon what request it is
making. For ‘get’, the “Destination Element” MUST point to the “get_buf[0]” element of the associated
“iQ_PROBE_UDT”. For ‘set’, the “Source Element” MUST point to the “set_buf[0]” element of the
associated “iQ_PROBE_UDT”. The “Path” setting MUST point to the proper Implicit Message
Connection.
NOTE: BE sure to check the “Path” of each MSG instruction/tag is properly associated with the correct
Implicit Message Connection. This is especially important in the case of controlling multiple generators
simultaneously by the same logic program,
See the demo application for examples of Explicit Messaging used in PLC logic.
The boot-loader always runs as soon as power is applied. It is accessed using a terminal interface just
like the module configuration procedure over a serial connection to the “Config” port. The boot-loader
serial port setup is fixed at 115200 bps, 8 data bits, no parity bit, and 1 stop bit with no hardware or
software flow control.
To access the boot-loader, connect the serial cable to the “Config” port of the EIP/IQL converter with the
power off. Press and hold the “ESC” key from you terminal emulator program (TeraTerm or
HyperTerminal), apply power to the EIP/IQL converter. You should see a screen similar to the following
and the “FAULT” LED should be blinking slowly (once per second). Release the “ESC” key. If the boot-
loader does not detect 5 consecutive “ESC” characters at 115200 bps within the first second of power up
it will run the application code, this is the boot sequence that happens during normal operation. The baud
rates used on the config port by the boot-loader (baud rate: 115200) and application (baud rate: 57600)
are intentionally different to reduce the chance of accidentally entering the boot-loader during normal
operation/use of app TUI.
The user interface to the boot-loader is identical to the EIP/IQL configuration procedure. Commands are
issued by typing the name of the command into the terminal emulator program and hitting the “Enter” key.
For example, to display a list of available commands, you would type “help” (without the quotes), hit the
enter key. All commands are case sensitive and in lower case (“Help”, “HELP”, “HeLp” are not the same
as “help”). The up and down arrow keys will cycle through your command history. The left and right
arrow keys will move the edit position of your cursor. The “Backspace” key will remove characters (the
“Delete” key is not supported!). The “Enter” key submits the command to be processed.
The firmware update procedure starts by erasing all saved settings and the entire EIP/IQL application
code. Then a “HEX” file containing the application binary file (IQL_EIP_APP) is sent to the module using
the “XMODEM” protocol.
Once the “Waiting for HEX file download via XMODEM...” line is displayed, the boot-loader is waiting for
your terminal emulator program to initiate the XMODEM download. In TeraTerm this is accomplished
through the “File->Transfer->XMODEM->Send…” menu sequence, browse to the HEX file and hit the “OK”
button to start the transfer. In HyperTerminal, an XMODEM transfer is accomplished through the
Transfer->Send File… menu sequence and selecting “Xmodem” from the “Protocol” drop down list, browse
to the HEX file and hit the “Send” button. The “FAULT” LED on the EIP/IQL converter should blink rapidly
during the XMODEM transfer.
Once the transfer has completed successfully, the firmware has been updated. Remove and reapply
power to the EIP/IQL converter, change your baud rate setting to 57600 bps and ensure you can reach
the command prompt of the newly updated application.
If the XMODEM transfer fails or stalls, or the “FAULT” LED stops blinking rapidly, you will need to restart
the procedure.
9. Getting Help
Dukane Sales Engineers are readily available to help with common issues customers face when first
starting an EIP enabled project. For the quickest assistance, please provide the outputs for the “env”,
“iql”, and “eip” TUI commands (see Section 3) in your initial communications, either by copy/pasting
text from your terminal emulator, or taking screen shots. These three commands usually provide
enough information to overcome any issues.
DOCUMENT INFO:
DATE: 3/7/2011
ECN: 8204
DRAWN: MJD
CHECKED: MJD
APPROVED: MJD
ENGINEER: MJD
REVISION INFO: