Release Notes for WinMark Pro version 6.1.0.6789

 

This file contains the latest release notes for WinMark Pro, version 6.1.0, build 6789.

 

OPERATING SYSTEM:

 

WinMark Pro version 6 software (WinMark_Setup 6789_ECO.EXE) is intended for use only with Microsoft® Windows® 7, Vista, XP, and 2000, operating systems. WinMark Pro version 6.0 is compatible with all SYNRAD FH Flyer Marking Heads and Fenix Flyer Laser Markers.

 

WinMark Pro version 6.0.0.6789 software is NOT tested for compatibility with FH Series Index and Tracker Marking Heads and is NOT intended for use with marking heads using an ISA-bus Fiber Link Controller Card (FLCC).

 

 

WinMark Pro Requirements:

Windows® 7, Vista, XP, or 2000 Operating Systems

16-MB RAM

30-MB of free hard drive space

One CD-ROM drive

Two open USB ports (one for USB Hardlock device, one for Flyer communications)

 

See the Microsoft website for a list of minimum hardware requirements for your particular OS.

 

 

INSTALLATION:

WinMark Pro version 6 software must be installed before connecting and powering the FH Flyer Marking Head. Version 6 automatically loads the correct device drivers during installation. If WinMark Pro is not installed first, the Windows operating system will arbitrarily assign a USB driver that is NOT compatible with Flyer’s USB port protocols.

 

Exit all programs and turn off any antivirus software before beginning the WinMark Pro installation process.

 

 

UPGRADING:

Before upgrading WinMark Pro version 6 software, remove power from the Flyer head or disconnect the USB cable. If the head is still active, the Window’s Operating System will NOT update Flyer’s USB driver to the latest version.

 

 

IMPORTANT INSTALLATION NOTES:

With Microsoft Windows 7, Vista, XP, and 2000 operating systems, programs must be installed or uninstalled by an individual with Administrator privileges. Because of this behavior, WinMark Pro’s registry access permissions are initially set to Administrator by the WinMark installer when it sets the startup language. The installer does not support different access levels for registry keys so these must be changed by the program. It is therefore necessary to run WinMark Pro once as an Administrator before other, more restricted, users can run the program.

 

WinMark Pro v6 is a Microsoft .NET Framework-based application. During installation, WinMark Pro v6 will install .NET Framework files onto your computer, if they do not currently exist. If WinMark Pro is un-installed, .NET files are not removed, because these files may now be used by other applications installed after the original WinMark installation.

 

WinMark Pro’s Flyer USB Device Driver does not currently support 64-bit computers. To operate Flyer/Fenix Flyer heads, you must install WinMark Pro on a 32-bit computer.

 

To install WinMark Pro on Windows 7 or Windows Vista operating systems, right-click the WinMark_Setup 6789_ECO.EXE file and choose “Run as Administrator...”. After installation on Windows Vista, you may still be required to log on as the Administrator in order to perform certain functions like file importation or saving custom date code formats.

--------------------------------------------------------------------------------------------

 

Version 6.1.0.6789

Released 8/2/2010

 

 

Version 6.0.0.6660

Released 5/28/2010

 

 

Version 6.0.0.6654

Released 03/23/2010

Version 6 adds the following new features:

·         WinMark Pro now a Microsoft .NET Framework-based application

·         Added UID/Composite 2D Code generation

·         Added Radial Marking capability

·         Added Banner Tracking capability

·         Added inverted TrueType text function

·         Added ”No-Lens” marking capability

·         Added alphabetical “Sort” function to right-click Flyer Filestore menu

·         Added ability to set negative Pline Start Delay values for Flyer/Fenix Flyer heads

·         Added property to abort marking from I/O input

·         Fixed problem were arc segments were not displayed/marked properly if arc length greater than 360 degrees.

 

 

Miscellaneous issues:

---

Description of GetSystemStatus method:

short GetSystemStatus(CString pBuf)          

Returns pBuf: A ‘//” delimited string containing the WinMark Pro version number, the Hardlock driver version number, and the USB driver version number. The function returns a short integer, which contains the length of pBuf.

 

---

Description of Firmware Download method:

short FirmwareDownload(CString FileName)

Filename is the location of the firmware upgrade on the local machine such as C:\Program Files\Synrad\WinMark\Update_2-82.fhz

Returns a short int:

 

0 = Failed

1 = Success

 

On successful upgrades, Firmware download will return a few seconds before Flyer is re-started. Reconnection to the ActiveX app can occur in two manners: (1) for USB connections, a FlyerConnectNotification Event will fire and connection to the ActiveX app will be reestablished (see ReconnectControl below) or (2) for Ethernet reconnection polling with 1 second delays using ReconnectControl (see below).

 

Ethernet Example:

Private Sub btnFirmwareUpgrade_Click_1(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles btnFirmwareUpgrade.Click

        Dim synerr As Short

        lblStatus.Text = "Status: Firmware Upgrade in Progress. Please Wait"

        synerr = mh.FirmwareDownload("C:\Program Files\Synrad\WinMark\Update_2-82.fhz")

        If synerr < 1 Then

            lblStatus.Text = "Status: Firmware Upgrade FAILED"

        Else

            lblStatus.Text = "Status: Disconnected"

            Do

                synerr = mh.ReconnectControl()

                System.Threading.Thread.Sleep(1000)

            Loop While synerr = 0

            lblStatus.Text = "Status: Connected"

        End If

    End Sub

---

 

Description of ReconnectControl method:

short ReconnectControl(void) 

A method that reinstantiates the ActiveX control. This is useful when connection is lost with the marking head (reboots or pulled-out cables)

Returns a short int:

 

0 = Failed

1 = Success

 

**NOTE for USB connections this should be used ONLY in conjunction with the mh_FlyerConnectNotification method. For example:

 

VB Sample

Private Sub mh_FlyerConnectNotification(ByVal Index As Short, ByVal bConnecting As Short) Handles mh.FlyerConnectNotification

                If bConnecting Then

            mh.ReconnectControl() 

            //Your code here

        Else

            // Your code here

        End If

    End Sub

 

For Ethernet connections, FlyerConnectNotifications do not fire, so the ReconnectControl method can be used anywhere in the user code.

 

---

WinMark Pro v6 .NET ActiveX Events will not work when compiled using Visual Basic 6.0 or below. To run a VB executable file containing Events, re-compile your source code using Microsoft Visual Studio 2003 or above. Refer to the Microsoft web site for details.

 

---

Mark Count property and Tracking: When tracking with FH Flyer, the value assigned to the Mark Count property (on the Marking tab for the Drawing object) will vary depending on whether you are operating Flyer in WinMark control mode or Stand-alone control mode. Under WinMark control, set Mark Count = 1 to track continuously as directed by input automation. In Stand-alone control, set Mark Count = 0 in order to track continuously.

 

---

All ActiveX control methods must use inches as the unit of measure; program your calling program to calculate the conversion to inches from other units of measure. Unpredictable object placement may result if the Show Units Type property in the mark file is set to millimeters or centimeters.

 

---

Linked objects in serialized arrays do not work. This is handled with a message and an error.

 

---

For best results when marking bitmap (raster) images, set a Resolution value that corresponds to 100–150% of the spot size generated by the selected focusing lens. For example, a 200mm lens with a spot size of 0.011” is capable of marking approximately 100 discrete dots per inch.

 

Generally, set Resolution equal to 200–300 when using an 80mm lens; 150–225 for a 125mm lens; 100–150 for a 200mm lens; and 50–75 when marking with a 370mm lens.

 

After changing Resolution and/or resizing the image, test mark the bitmap image. Use the Color Reduction Method property (Format tab) to change the color reduction algorithm as required. This change is performed on the original image, which is stored by WinMark during importation. Note that the screen display does not necessarily indicate the improved mark quality, so test marks are required.

 

---

When serializing text strings containing lower case letters, the text string may shift up when lower case letters with descenders (g, j, p, q, s, y) are marked. This occurs because the Fixed To Position property defaults to "Center". Set the text Fixed To Position property to "Top Left", "Top Middle", or "Top Right" for best results.

 

---

Some Adobe Illustrator version 7.0 .AI or .EPS files may not import properly. If this occurs, save the file as a version 5.0/5.5 (or lower) .AI or .EPS file and then re-import into WinMark Pro. Alternatively, you may Copy (or Drag) from Illustrator and Paste (or Drop) into WinMark Pro.

 

---

Some AutoDesk AutoCAD version 14 .DWG or .DXF files may not import properly. If this occurs, save the file as a version R12 .DWG or .DXF file and then re-import into WinMark Pro. Alternatively, you may Copy (or Drag) from AutoCAD and Paste (or Drop) into WinMark Pro.

 

---

WinMark Pro’s File Import Filters do not support AutoCAD 2000 or later file formats. Choose “Save As” (DWG) or “Export” (DXF) and then choose to create the drawing as an R12 version. Alternatively, you may Copy (or Drag) from AutoCAD and Paste (or Drop) into WinMark Pro.

 

---

Using ActiveX, Automation (Inputs/Outputs), and Tracking: When controlling Tracking using ActiveX control methods, do not place Input automation in the mark file. Instead, perform any input automation functions within the ActiveX control program. By doing this, your control program is in charge of pre-mark and post-mark automation; WinMark’s MarkDrawing control method only maintains control of the operating system long enough to control laser on/off commands during the actual marking process. Performing input automation within the mark file may prevent the ActiveX control program from regaining control of the operating system once the MarkDrawing command is called.

 

---

Using WinMark Pro or WinMark Launcher, Automation (Inputs/Outputs), and Tracking: When controlling Tracking using WinMark Pro or WinMark Launcher, do not use the Wait Digital Before Piece property on the Automation tab. This property is reserved for Tracker input functions (part sensor on IN0 and encoder inputs on IN1/IN2). Automation using Event Builder commands or other input/output commands on the Automation tab works as expected.

 

---

Text Height set on Format tab does not match Object Height shown in Object Transformations dialog box. For TrueType fonts, the Text Height value corresponds to the uppercase cap height of the font. The Object Transformations Object Height is the sum of the uppercase cap height plus the space above and below provided for ascenders and descenders. Note that Stroke font heights are variable (depending on the designer) and do not strictly conform to this description.