COMFILE CUWIN User manual

1
TOUCH CONTROLLE
R
CUWIN
User Manual

2
1.0 Introduction
The CUWIN combines a graphic display and touch interface with a high efficiency industrial
controller.
It is equipped with Microsoft Windows CE 5.0 Embedded, a stable operating system used in
many industrial touchscreen applications. Windows CE supports applications developed in
Microsoft Visual Studio 2005 or 2008 and other development tools able to create Windows CE
ARM executables. It can also run NSBasic scripts.
Developing for the CUWIN is similar to normal PC program development; anyone with
previous PC programming experience can develop CUWIN applications without difficulty. The
CUWIN supports the .NET Compact Framework (1.0, 2.0) that reduces development and
testing time by allowing the use of cross-platform .NET functions. If developing for the .Net
Framework, Visual Studio 2005 Standard and higher, or Visual Studio 2008 Professional and
higher must be used as these editions include the Smart Device Development Kit.
The CUWIN can also operate in IntelliLCD Mode, which allows the CUWIN to emulate an
IntelliLCD as a drop-in replacement. Existing IntelliLCD applications can upgrade to a CUWIN
today, and not lose functionality while the CUWIN native applications are developed.
The CUWIN offers RS232, RS485, and Ethernet for external communication. It can even
browse web sites using the internal browser, which is useful for displaying diagnostic data or
even remote control panels through a web interface.
Depending on which CUWIN features you choose to access, it can be used for anything from
a user interface panel to the main controller for your automation equipment.

3
1.1 Overview

4
The CUWIN has 3 RS-232 Ports (COM1~COM3) and 1 RS-485 port(COM1), and COM1 is
can be switched to RS-485 or RS-232.
There are 4 terminals for RS-485 Port. The first one if for plus, and the last one is for minus.
The second and third one is not used.

5
1.2 Dimensions
[CUWIN3500]

6
[CUWIN3200]

7
[CUWIN4300]

8
1.4 Panel Mounting
Mounting screws and brackets are provided with each CUWIN. They are designed to clamp
the CUWIN bezel against a front panel, with the rear portion of the device extending through a
panel cutout.
After assembling the brackets as shown below, insert the side hooks into the appropriate
mounting holes on the top and bottom of the device.
Then tighten the screws enough to hold the CUWIN securely against the front panel. Do not
over tighten, or you will risk damaging the CUWIN.

9
1.5 Hardware Specifications
Processor 32-bit RISC (ARM920T Core) - 266MHz
Memory RAM: 64MB, NAND Flash: 64MB, NOR Flash: 1MB
LCD CUWIN3200/3500 : 7” TFT, CUWIN4300 : 10.2” TFT
18-bit / 260k colors, 800 x 480 pixels, LED backlight
Touch Four wire resistive panel
Serial (2) RS232-only, (1) RS232/RS485 switchable
USB (1) host interface, (1) device interface
Storage SD card Flash memory slot (up to 2GB)
Sound Internal mono speaker, external 3.5mm stereo jack
Clock Internal realtime clock
Power DC 9V to 24V, 500mA
The Start Kit for each model includes a manual, CD, cables, and 1 GB SD Flash card. We
recommend a Start Kit for your initial development purchase, and the bare devices for later
production quantities.

10
2.0 Boot Modes
The CUWIN supports various boot modes which are selected with DIP switch settings.
Position Setting
1 Reserved
2 ON
IntelliLCD Mode 3 ON
2
2 ON
Auto-Run Mode 3 OFF
2 OFF
3
Boot Mode
Desktop Mode 3 OFF
Enable OFF
4 Drag and drop feature Disable ON
5 ON
9600 6 ON
5 ON
5
19200 6 OFF
5 OFF
38400 6 ON
5 OFF
6
RS232 Speed
115200 6 OFF
* Caution : If the drag-and-drop feature is enabled and the serial communication status
is busy, the touch-screen feature can suffer some troubles. We recommend that you
disable the drag-and-drop feature in normal situations.(Put the DIP Switch 4 to 'ON'
position to disable the feature)

11
IntelliLCD Mode
Graphics and text can be displayed on the LCD in response to commands received over the
RS232 port, and touchscreen events can be output through the RS232 port. In this mode, the
CUWIN precisely emulates an IntelliLCD. For more details, please refer to the IntelliLCD
product manual.
Auto-Run Mode
The CUWIN will boot and then automatically run a specific program immediately on startup.
The Windows CE desktop will not be displayed. This mode would be used in production,
when your application should be the only program executed by the device. If no auto-run
program is found in auto-run mode, the CUWIN will start in development mode.
2.1 Loading an Auto-run Application
1. Connect the CUWIN USB Device port (square B-style plug) to the development PC
(with ActiveSync installed), or insert an SD card into a reader on your development PC.
2. Copy the desired executable file to one of the locations below:
Flash Disk SD Card
\Flash Disk\AutoRun\ \Storage Card\AutoRun\
Copy the executable to the folder using
ActiveSync.
There should be only one *.EXE in the
folder.
The Flash storage area is restricted to a
total of 30MB, but actual available
space is under 3MB due to included
fonts and other files. If you require extra
space, you may delete the font folder if
those fonts will never be used. Rather
than delete the font folder, we
encourage the use of an SD memory
card for application storage.
If using ActiveSync, copy the
executable to the folder. If using an SD
card reader on the PC, copy to the
AutoRun folder on the SD Card.
If the AutoRun folder does not exist on
the SD Card, create it.
There should be only one *.EXE in the
folder.
The SD Card should be FAT formatted,
up to 2GB storage (no SDHC cards).
If there are executable files in both locations, only the program in the Flash Disk
is executed.
3. Make sure the boot mode DIP switches are set correctly to enable auto-run mode.
4. Cycle the CUWIN power supply. After the device has booted, the program in the auto-
run folder will be executed.

12
3.0 Development Environment
The CUWIN can execute Windows CE applications developed with Microsoft Visual Studio
2005. Developing for the CUWIN is similar to PC development.
Managed Code (.NET Compact Framework)
The CUWIN supports code developed for the .NET Compact Framework. Managed code can
be generated in Visual Basic .NET, Visual C#, etc.
Native Code
Application performance can be increased by developing native code instead of managed
code. However, the .NET Compact Framework supplies a wide range of useful functions, so
native code may require more time to develop. Developing native code requires installing the
correct SDK for the target hardware, in this case the CUWIN. Please refer to chapter 4-4 for
details regarding the installation of the correct SDK for developing native code. Native code
can be developed with tools such as Embedded Visual C++ 4.0, Visual Studio 2005 C++ and
Basic, etc.

13
3.1 Setting Up Visual Studio 2005
The following instructions are a guide to setting up Visual Studio 2005 and other necessary
files for CUWIN development. Please be aware that only Visual Studio 2005 Standard or
higher supports Smart Device Development. Visual Studio 2008 Professional and higher
can also be used, but this section will only show the procedures for Visual Studio 2005.
Getting Visual Studio
Visual Studio 2005 is a software development platform provided by Microsoft. If you wish to
use Visual Studio to develop native and managed code applications for the CUWIN, you will
need to purchase Visual Studio from Microsoft.
Files you will need
Visual Studio 2005 Standard or higher
If you do not have Visual Studio 2005 standard or higher, an evaluation
copy of Visual Studio 2005 Professional Edition is available for download
from Microsoft. This version can be installed and used for a period of 90
days, which should provide enough time to test several application
concepts on the CUWIN and determine whether to purchase a full Visual
Studio license.
Visual Studio 2005 Service Pack 1
This should be installed before developing applications for the CUWIN. If
your version of Visual Studio 2005 does not have Service Pack 1 installed,
locate the Service Pack on Microsoft's web site and install.
.NET Compact Framework 2.0 Service Pack 2
If you intend to develop managed code (.NET) applications for the
CUWIN, you should also locate and install the .NET Compact Framework
2.0 Service Pack 2.
CUWIN SDK for Visual Studio 2005 and EVC++ 4.0
The CUWIN SDK provides target platform settings in order to compile
programs for the CUWIN. This is available from the Comfile website at
http://www.cubloc.com/downloads/cuwin_sdk.msi
If you have any difficulty locating files on Microsoft's website, you can search for them using
the URL below:
http://www.microsoft.com/downloads/Search.aspx?displaylang=en

14
Setting up the Development Environment
If you have not purchased Visual Studio, you can install and test the 90-day trial version
described above.
1Locate and run the Visual Studio 2005 setup program, following all installation prompts.
Default options should be adequate, unless your system has special requirements.
2Locate and run the Visual Studio 2005 Service Pack 1 setup program, following all
installation prompts.
3Locate and run the .NET Compact Framework 2.0 Service Pack 2 installation file,
following all installation prompts.
4Locate and run the CUWIN SDK installation file, following all installation prompts.
If the above installations completed successfully, you should now have a working
development environment for the CUWIN.
To easily access the CUWIN during development for program testing and debugging, you
should also install ActiveSync, though it is not strictly required. If you do not wish to install
ActiveSync, your application can be placed in the AutoRun folder on an SD card using an
external reader, and it will be executed on startup if the DIP switch settings are correct. If you
wish to install ActiveSync, please refer to section 5.0 for installation instructions.

15
3.2 Example Visual Basic project
This example uses Visual Studio's automatic download and run feature over ActiveSync. If
you do not wish to use ActiveSync, the resulting executable files can be transferred to the
CUWIN using an SD card.
1. Run ‘Microsoft Visual Studio 2005’.
2. Choose “New Project” from the File menu.
3. Select “Windows CE 5.0” and “Windows Application”. Type the name of project
(“TestProgram1” in this example) and click “OK”.

16
4. A new blank project is created as shown below.
5. Drag a Button control from the toolbox to the middle of Form1.

17
6. Select the new button. Change the Text attribute from “Button1” to “Hello”.
7. Double-click the “Hello” button. Visual Studio will open a window to edit the code that
handles “Hello” button click events. Type 'MsgBox("Hello!!!")'

18
8. Set the target device.
(1) In the Solution Explorer, select the top-level item.
(2) Select “Target Device” and a list of possible devices will be displayed. Choose
Windows CE 5.0.

19
9. Click the Start Debugging icon as indicated below. This will build and publish the
program in debugging mode.
10. After a short delay, the program is transferred to the CUWIN and executed
(assuming a working ActiveSync connection).

20
Start Without Debugging
If you click the “Start Debugging” button, you can set breakpoints in the code and step
through the program. This will start up the debugging interface in Visual Studio, which adds
some overhead to the execution of the program. If you simply want to compile and execute
the program on the CUWIN for testing without starting the debugger, it is possible to configure
Visual Studio to do so with one click.
A “Start without debugging” button is not in the toolbar by default. You can add the button as
shown below:
1. Click Tools > Customize... on the menu bar.