How can I setup my mark file to select one or more of multiple objects to mark?
If you have an application where a single Marking Head must mark different parts within a mark session, you can either use WinMark Pro's ActiveX functions or the serial port automation to change from one mark file to the next ‘on the fly’. If you have a limited number of possible mark files to switch between (up to eight or sixteen) in a single mark session, you can layer all of the objects from the mark files into a single file, then program the automation to mark the correct layer depending on the status of the Marking Head’s input signals.
It is this layering scheme that will be explained here. A file containing three different layers will be created and then automated so that only one of the layers will be marked on each pass through the Mark Loop.
This file automation uses the Match Digital State (MDS) function available in WinMark Pro’s Event Builder (EB) automation tool to mark one of three different objects, depending on the input status of input bits IN1 and IN2. The three objects are all layered on top of each other, using the result of the MDS tests to determine which object will mark. The MDS function works by evaluating the status, high or low, of the input bit(s) defined against the required match values. The MDS assigns a value of FALSE to the selected object and property unless the status of the input bits matches the required pattern, in which case the MDS assigns a value of TRUE to the Target Object and Property.
Configure the Match Digital State layer marking automation as follows:
- 1. Open a new mark file.
- 2. Place three text objects on the Drawing Canvas. Give each text object a different caption so that the objects can be uniquely identified.
- 3. Click any blank area on the Drawing Canvas and select the ‘Automation’ property tab.
- 4. Click on the ellipsis button (‘…’) to the right of ‘On Before Mark Piece’ text box to open up the Event Builder window.
- 5. Click the ‘Add’ button to add a new command.
- 6. Click on the drop down arrow and select ‘MatchDigitalState’.
- 7. Set the ‘Timeout Msecs’ property (in the ‘Command Details’ section) to 100ms.
- 8. Set the ‘Input Bit 1’ state to ‘Clear – 0’.
- 9. Set the ‘Input Bit 2’ state to ‘Set – 1’.
- 10. In the ‘Target Object and Property’ frame, select the first of the three text objects as the Target Object, and select ‘Mark Object’ as the Target Property.
- 11. Follow steps 5 through 10 to add another Match Digital State command, but set the required input bit state to ‘Input Bit 1’ = ‘Set – 1’, set ‘Input Bit 2’ = ‘Clear – 0’, and select the second text object as the Target Object.
- 12. Follow steps 5 through 10 to add a third Match Digital State command, but set the required input bit state to ‘Input Bit 1’ = ‘Set – 1’, set ‘Input Bit 2’ = ‘Set – 1’, and select the third text object as the Target Object.
- 13. Click ‘OK’, then save the mark file by clicking on the Save icon, or selecting Save from the ‘File’ menu.
Note that the Timeout property of the MDS function determines how many milliseconds WinMark Pro will wait for the input levels to match the required values before returning a value of FALSE to the Target Object and Property. WinMark Pro will continuously check the status of the input(s) until the required levels are met or until the Timeout value expires. As soon as the input levels match the required values, the remaining timeout period is ignored and WinMark Pro advances to the next automation line.
This file is setup so that, provided the status of the input(s) used for the MDS commands are steady during the succession of MDS input evaluations, only one of the MDS commands will set it's target object and property to TRUE. This results in only one object being marked for each pass through the Mark Loop (see the Automation Flowchart found in the WinMark Pro Help menu). To mark each of the three objects in this example, WinMark Pro would have to execute three loops through the automation routine.
This file has been setup so that WinMark Pro goes through the Mark Loop just once in each mark session. Once the MDS automation works as desired, you can then add further automation and set up the mark file to go through the Mark Loop as many times as desired, using the basic automation scheme.
Is there a way to run two or more Marking Heads from one computer?
Yes.
No.
Well…you can run two or more Marking Heads from one PC if you want them all to mark exactly the same information at the same time (with one exception… see the Quasi Independent Operation details below). The ISA version of the Fiber Link Circuit Card (FLCC) supports a Master/Slave relationship between two cards installed in one PC, so that both cards share the same address, with one card being the Master and the other the Slave. In such an installation, the Master handles all Input/Output (I/O) interfacing as well as any communications from the Marking Head to WinMark Pro. The vector data that is sent to the card for transmission to the Marking Head is sent to the Slave card as well, thus the two Marking Heads mark the same information at the same time.
Note that this mode of operation is not supported by the PCI version of the Fiber Link Controller Card, or by the D/A card used with the SH Marking Head..
Master/Slave configuration limitations
- 1. This mode of operation is not currently supported on the PCI version of the FLCC, only on the ISA version.
- 2. Only the Master Marking Head may be configured for I/O automation with a PLC or other parts handling controller. The Master/Slave mode of operation depends on the fact that the Slave FLCC is prevented from reporting I/O status as well as Marking Head transmissions to WinMark Pro. This is necessary to prevent address conflicts within the computer. The one caveat to this limitation is the use of the FASI function (see below).
- 3. Both Marking Heads receive the same mark data at the same time. Use of the FASI function allows a way around this limitation as well.
The FLCC can be configured for Slave mode by soldering a jumper across pads 19 and 20 of unused connector location P1. (If you hold the FLCC so that the parts are facing you and the fiber optic connectors are to the right, the P1 location is in the upper left hand corner of the circuit card, with pins 1 and 2 on the left and pins 19 and 20 on the right.)
Once the card is jumpered for Slave mode, be sure to set the Master and Slave FLCCs dip switches to the same base address. Once that is done, WinMark Pro may be run, commanding both Marking Heads to mark the same image at the same time.
Quasi-independent operation of the Master/Slave configuration using FASI
A level of independence may be given to the Master/Slave configuration by using the FASI function to enable any, all, or none of the Marking Heads to mark. The following marking scenarios are supported by this method:
- · The Marking Heads may mark the same information, but it is necessary to disable one or more Marking Heads while marking continues on the other(s)
- · The Marking Heads must mark different information, but they don’t have to be marking at the same time.
- · If both Marking Heads are to be marking similar objects (the same style barcode, text, or other objects), then WinMark Pro can be set up to run the same file for both Marking Heads. If the files for each Marking Head must be unique, then the mark file could be set up with the objects layered, using the WinMark Pro MatchDigitalState automation (click here) to determine which layer is marked on each pass through the Mark Loop.
To set up the Master/Slave + FASI scheme:
1. Modify one of the two FLCC cards for Slave mode as described earlier. Make sure both cards are set to use the same base address.
2. Enable the FASI function on both Marking Heads by setting DIP Switch #6 on the FLCC to the ON position (see the Fast Acting Safety Interlock section in the Marking Head manual).
3. Wire a PLC output to IN3 on the Master Marking Head. (If the Marking Head is a Fenix or FH model, this must be wired to the I/O connectors on the Marking Head (or the Fenix rear panel), NOT to the FLCC. If the head is a DH model, the wiring goes to the FLCC IN3.) Whenever this signal is active, the Master Fenix’ lase will be enabled.
4. Wire another PLC output to the Slave Fenix IN3. Whenever this signal is active, the Slave Fenix’ lase will be enabled. Also route this signal to one of the unused inputs on the Master Fenix, for example, IN2. (This additional wiring is necessary because the Slave Fenix’ I/O status will not be reported in slave mode.)
5. Modify your VB code so that, once the ‘part in place’ bit is satisfied, the status of both IN2 (Slave enable) and IN3 (Master enable) are tested for acceptable values. (For example, if you only want one or the other Fenix to mark at any time, you’ll want to test to make sure that IN2 and IN3 aren’t both high or both low. Or, if there is a scenario where both might mark at once, you’ll want to test just to make sure both signals aren’t low.)
6. Reprogram your PLC so that, depending on which Fenix you want to fire on each mark, the new Fenix enable outputs used in steps 3 and 4 are set or cleared to select the proper Fenix prior to asserting the ‘part in place’ signal. Note that the Fenix requires no waiting period from the time IN3 goes active until the time the laser may fire, so you can set IN3, then immediately command the mark without having to wait for the laser to come up to power (as opposed to opening and closing the keyswitch, which takes five seconds before the laser is ready to fire).
[Back to Questions] [Top of Page] [Previous Page] [Next Page]