Gunze Mice & Touchpads Driver

Node:Top,Next:General Information,Previous:(dir),Up:(dir)

Behringer U-control Uca202 Driver for Windows 7 32 bit, Windows 7 64 bit, Windows 10, 8, XP. Uploaded on 4/11/2019, downloaded 3494 times, receiving a 96/100. Check out the How to install Behringer UMC404HD drivers on Windows 10 page at Sweetwater — the world's leading music technology and instrument retailer! China Gunze 100-025 / Gunze 170-3140 / Gunze 170-2971 / Gunze 170-2950 Touch Panel Screen Glass Membrane, Find details and Price about China Gunze 100-025, Gunze 170-3140 from Gunze 100-025 / Gunze 170-3140 / Gunze 170-2971 / Gunze 170-2950 Touch Panel Screen Glass Membrane - Milestone Touch Co., Ltd. We prepared decubitus ulcers on diabetic mice. After debriding the ulcers, we implanted CGSs (diameter 8 mm) impregnated with normal saline solution (NSS) or bFGF solution (7, 14, 28 or 50 µg/cm 2). At 1 and 2 weeks after implantation, the mice were sacrificed and tissue specimens were obtained.

This file documents Gunzets, support software for Gunze touch panelsunder Linux and XFree86.

  • General Information:
  • Bugs:
  • Device Support:
  • XFree Configuration:
  • Usb Driver:
Node:General Information,Next:Bugs,Previous:Top,Up:Top

The package supports Gunze touch panels under Linux and XFree86. Supported panels are the serial, PS/2, and USB devices. The serial andPS/2 devices are supported by means of an X module, xf86Gunze. Supportfor USB comes as a kernel module that emulates the PS/2 protocol, soyou still need the xf86Gunze module.

The latest version of this driver can be downloaded from:

The latest source tree can be accessed from my CVS server, instructionsare available at http://ar.linux.it/software/#cvs . The package name to use is gunzets. The latest CVS snapshotcan also be downloaded from ftp://ar.linux.it/pub/gunzets .

Node:Bugs,Next:Device Support,Previous:General Information,Up:Top

The following bugs are currently known:

  • Debouncing is only supported for XFree 4.0 (not 3.3.6).
  • A bounce event breaks smoothing processing
  • Support for multi-screen operation is not supported.
Node:Device Support,Next:XFree Configuration,Previous:Bugs,Up:Top

To run the serial or PS/2 devices you only need the information inthis section. To run the USB device you also need to load the kernelmodule, described under See Usb Driver, later in this file.

Support for all three device flavors is implemented by means ofxf86Gunze.c, a module for XFree86.

The driver has been used under XFree86 version 3.3.6 and version 4.0.1.

In order to use the touch screen in X, you should install in yoursystem the 'xf86Gunze' module, part of this distribution.

The compiled module (xf86Gunze.so for XFree86 3.3 orgunze_drv.o for XFree86 4.0) should go in the moduledirectory of your X server, usually /usr/X11R6/lib/modules forXFree86 3.3 or /usr/X11R6/lib/modules/input for XFree86 4.0. When the file is in place, a proper XF86Config will arrange forits loading.

In order to compile the module for different version of the XFree86systems you need access the source tree and compile using therecommands:

The 'location of source' above should be the full path name to thedirectory called 'xc' after you uncompress the source tar file.

Both XFREE33SOURCE and XFREE40SOURCE can be definedin your environment. Also, calling make without arguments willcompile both modules.

Gunze Mice & Touchpads Driver Windows 7

To compile gunzets you'll most likely need to compile X first(by issuing make World and waiting a huge lot of time). A freshlyuncompressed source tree lacks the proper header files for compilationto succeed; since one of the errors happens inside an X header, youcan only fix it by compiling X first).

Node:XFree Configuration,Next:Usb Driver,Previous:Device Support,Up:Top
  • XFree 3.3:
  • XFree 4.0:
  • Generic X Configuration:
  • Text Console:
  • Calibration:
  • XFree Tools:
Node:XFree 3.3,Next:XFree 4.0,Previous:XFree Configuration,Up:XFree Configuration

Gunze Mice & Touchpads Drivers

Gunze mice & touchpads driver printer

XFree 3.3

In order to use a Gunze device with XFree 3.3 you need to add thefollowing two sections to your XF86Config (the example below showsall the options available for the module, but most of them areoptional, see below for details):

The meaning of the individual options is the following:

DeviceName 'touchscreen'
The device name is an identifier string chosen by the user. It is mandatory.
Port '/dev/ttyS0'
The hardware channel used to read input data. The line ismandatory. It can be a serial port, a PS/2 port (/dev/psaux)or the USB entry point (/dev/gunzets).
DeviceType Serial
Optional specification of the device type. It is used toselect the protocol used by the port. Possible values are(case-insensitive): 'serial', 'ps2' (or 'ps/2') and 'usb'. Ifthe information is not present in the configuration file, thefile name is used to guess the device type. Such guess willwork under Linux but may fail under other operating systems.
Speed 9600
Speed of the serial connection. Only used for serial devices,the value defaults to 9600. Only valid values are 9600 and19200.
CalibrationFile '/etc/gunzets.calib'
Optional specification of the calibration file. The default is/etc/gunzets.calib as shown. The format of the calibrationfile is specified later in this documents.
Smoothness 9
The smoothness value is used to smooth out movements. It isonly meaningful for motion and drag events. Allowed values arein the range 0 to 50. If you want to do handwriting, you'll needto disable smoothness processing (i.e., set it to 0).
TappingDelay 0
Optional selection of tapping mode. By default (tapping delay set to 0), any touchevent is reported as a button press. In tapping mode the firsttouch event is used to move the pointer, and button press isonly reported when the user taps on the device. If the delay,measured in milliseconds, between pen-up and pen-down is greaterthan the selected value, the pen-down even is considered motion. I personallyprefer tapping mode when testing the device, as it allows meto use the common point-and-click semantics instead ofclick-only; this is especially true if your touchscreen is notplaced over the image but in side of it (as you guess, I do that).
DebugLevel 0
Any debug level greater than 0 tells the driver to spitinformative messages. The greater the number, the higher themessage rate. Messages go to the usual X error channel(stderr, normally connected to the text console used to fireX).
Res12Bit
The boolean option states whether your panelreports data with 12 bits of resolution (i.e., as numbersin the 0-4095 range). The default, when no option isspecified, is 10 bits (0-1023). 12-bit support is implemented by discarding the lowest two bits,and has been contributed by Atsushi Nemoto.
AlwaysCore
The input device is a 'core' input device (like the mainpointer device - the mouse or equivalent). If the directiveis not specified, the touch screen acts as an auxiliary inputdevice, and applications may individually request to use it.
Node:XFree 4.0,Next:Generic X Configuration,Previous:XFree 3.3,Up:XFree Configuration

XFree 4.0

In order to use a Gunze device with XFree 4.0 you need to add anInputDevicesection to your XF86Config. The following example showshow it looks like. The options that are shown commented are notimplemented in this version of the module, and are ignoredif specified.

Moreover, you need to add an InputDevice line in theServerLayout section. After the addition,the section will most likely look like this:

Note that if your system has no mouse device, you can removethe InputDevice 'Mouse1' line and add 'CorePointer'to the touch screen line.

The meaning of individual options is as follows:


Identifier 'Touchscreen0'
The identifier string is mandatory, and appears, literally, inthe InputDevice directive within the ServerLayoutsection that is usually found at the end of the configuration file.
Driver 'gunze'
The name of the driver is mandatory. It is used to load theassociated module. In this case the file gunze_drv.o.
Option 'Device' '/dev/ttyS0'
The device name is mandatory. It states where input data iscollected from. It can be a serial port, a ps2 port or theUSB device created by the gunzets device driver.
Option 'DeviceType' 'serial'
The device type specification is not currently supported. Ifthe option is present it is ignored. The actual device type isretrieved from the device name: any device name thatincludes the string 'tty' is assumed to be a serial port,other devices are assumed to speak the PS/2 protocol.
Option 'BaudRate' '9600'
The transmission rate for serial ports. It defaults to 9600and is ignored for non-serial input devices.
Option 'CalibrationFile' '/etc/gunzets.calib'
The option is not currently implemented.
Option 'Smoothness' '9'
The smoothness of the pointer. The default value is 9. The greaterthe value the smoother the motion. If you need to do handwritingor similar 'fast' interaction, you should set the smoothness to 0.
Option 'TappingDelay' '0'
Optional selection of tapping mode. By default (tapping delay set to 0), any touchevent is reported as a button press. In tapping mode the firsttouch event is used to move the pointer, and button press isonly reported when the user taps on the device. If the delay,measured in milliseconds, between pen-up and pen-down is greaterthan the selected value, the pen-down even is considered motion. I personallyprefer tapping mode when testing the device, as it allows meto use the common point-and-click semantics instead ofclick-only; this is especially true if your touchscreen is notplaced over the image but in side of it (as you guess, I do that).
Option 'JitterDelay' '50'
The debouncing time lapse, measured in milliseconds. If a pen-down event occurs immediately after pen-up (within thistime lapse), then both events are discarded. Debouncing hasbeen contributed by Chris Howe <chris@howeville.com>, and defaultsto 50ms.
Option 'DebugLevel' '0'
The level of messages spit out by the driver. The directiveis optional and it defaults to 0.
Option 'Res12Bit' 'False'
The boolean option states whether your panelreports data with 12 bits of resolution (i.e., as numbersin the 0-4095 range). The default is 10 bits (0-1023). 12-bit support is implemented by discarding the lowest two bits,and has been contributed by Atsushi Nemoto.
Option 'SendCoreEvents'
The directive instructs X to use the touch screen as a coreinput device (like the main mouse). This module can currentlyonly work as a core device.
Node:Generic X Configuration,Next:Text Console,Previous:XFree 4.0,Up:XFree Configuration

Generic X Configuration

Please note that with both version 3.3 and 4.0 of XFree you can stilluse a normal mouse together with the touch panel. While XFree 4.0can use the touch screen as its only pointer device, version 3.3of the X server can't do that. If you have no other pointer and don't want X to choke on theconfiguration file, you can use a trick like this one:

Where /dev/fifo is just a plain unused fifo ('mknod /dev/fifo p')

If, when calling startx, it fails with a message ofInvalid Subsection Name, please check the previous errorlines, as they explain what is wrong. They usually look like:

The messages are pretty clear, if your are careful in reading them (I amnot that careful, and lose half an hour in trying to figure out whatwas wrong).

Node:Text Console,Next:Calibration,Previous:Generic X Configuration,Up:XFree Configuration

Text Console

Use of the touch screen on the text console is not supported, and Idon't think it ever will (although I made it work under gpm some timeago, I no longer maintain gpm).

Node:Calibration,Next:XFree Tools,Previous:Text Console,Up:XFree Configuration

Calibration

To calibrate the touch panel, run the gunzets_calib script, under X. It has been tested with both XFree86 version 3.3.6 and version 4.0. To calibrate pass the device name on the command line of the program:

The program needs to find gunzets_control in the command search path(it uses the control program to turn off the touchscreen in X, so thecalibrator can read input data).

In order to calibrate you'll need to move the mouse pointer first. Youcan do that with the warp command (see below) if no other pointeris available on the system. While I could use the touch panel to thisaim, and delay turning it off, I didn't think of it and don't want tore-test it all. The next release will be better in this respect (too).

Node:XFree Tools,Previous:Calibration,Up:XFree Configuration

XFree Tools

The package includes two tools that work by connecting with the X server:

gunzets_control
The program accepts on, off or info asargument. It turns the touchscreen off, turns it on, or reportsinformation about active input devices. The program needs toconnect to an X server.
warp
The program moves the mouse pointer. It can be used to movethe mouse when there is no active mouse. It accepts a seriesof letters on the command line: each uppercase N, S, W, Emoves the pointer by 100 pixels to the north, south, west,east. Each lowercase n, s, w, e moves the pointer by 10pixels.
Node:Usb Driver,Previous:XFree Configuration,Up:Top

This driver has been developed and tested with Linux-2.4.0 and workswith Linux-2.2.18 as well.

Input data is made available through an entry point in /dev (usingdevfs if available) (FIXME: devfs support is not yet implemented) orthrough the input engine (the input.o module) (FIXME: input support isnot yet implemented). By default it uses its own /dev entry point,dynamically allocated from the misc device driver.

  • Quick Start:
  • Compiling and loading:
  • Unloading:
  • Installing:
  • Accessing data:
  • Usb Calibration:
Node:Quick Start,Next:Compiling and loading,Previous:Usb Driver,Up:Usb Driver

Quick Start

If all of your modules are in place, you can just invoke

and read the section about X support, above.

If you want to use the input mechanism (currently unimplemented), adduse_input=1 to the gunzets_load command line.

Node:Compiling and loading,Next:Unloading,Previous:Quick Start,Up:Usb Driver

Compiling and loading

In order to successfully load the module you need to have thefollowing facilities compiled in your kernel or loaded as modules:

  • usb generic support (usbcore.o)
  • a usb host controller driver (usb-ohci.o o usb-uhci.o)
  • support for misc devices like the ps2 mouse (misc.o)
  • the input mechanism (input.o)

To compile the driver just make. If your 2.4 or 2.2 kernel headersare not available from /usr/src/linux/include then specify KERNELDIRto point to your kernel source directory, either on the make commandline or in the environment. For example:

Gunze Mice & Touchpads Driver

To load the driver, use insmod:

To use the input mechanism, specify it on the command line:

To automatically create the entry point in /dev (needed if you are notusing the input mechanism) run the gunzets_load script instead:

Node:Unloading,Next:Installing,Previous:Compiling and loading,Up:Usb Driver

Unloading

You can unload the module only after disconnecting the touch panel,otherwise the rmmod program will return 'Device Busy' even if noapplication is using the pane, because the USB mechanism is using it.

Node:Installing,Next:Accessing data,Previous:Unloading,Up:Usb Driver

Installing

To install the module to the proper places you can run makeinstall. You may also wish to copy gunzets_load from/usr/local/bin to /etc/rc.d/init.d or /etc/init.dand create a proper symbolic link for automatic load at boot.

Node:Accessing data,Next:Usb Calibration,Previous:Installing,Up:Usb Driver

Accessing data

Data read from the touch screen is available as raw data returnedin PS/2 format in the file /dev/gunzets. You can use the sameXFree driver described above for serial and PS/2 devices withthis driver.

Gunze mice & touchpads driver windows 7Node:Usb Calibration,Previous:Accessing data,Up:Usb Driver

Usb Calibration

To calibrate the touch panel, run the 'gunzets_calib' script, under X. See Calibration.

  • XFree Configuration
  • Usb Driver
>>Home>>Magazine>> This page

>>500+ other articles are available in our archive

German Air ForceWW I, WW II and Modern Colours

Examples of World War II camouflage schemes as prescribed by RLM:

Pre-war splinter scheme61/62/63over 65
Very early fighter biplanes, experimental aircraft63 overall
Two-green splinter scheme - all aircraft except seaplanes until the nedof 1939, later mostly bombers, transports and ground attack a/c70/71 over 65
Sea scheme - seaplanes72/73 over 65
Fighters, until ca. end of 193970/71 over 65
Fighters, French campaign and Battle of Britainmany different, but often70/02 over 65
Standard two-tone grey scheme, fighters 1941-194474/75 over 76
3-tone desert scheme - aircraft of the African campaign79/80 over 78
2-tone 'Tunisian' desert scheme79(brown) over 78
Late-war schemes, fighters, 1944-1945many different combinations of colours from the80-series, i.e.81/82 over 76,82/83 over 76,81/82 over'84',82/83 over '84', etc.
Nightfighter scheme75/76

Publications helpful for assembling RLM part of the chart heve beenTheOfficial Monogram Panting Guide to German Aircraft 1939-45 andLate-WarLuftwaffe Fighter Camouflage by Brett Green published at www.hyperscale.com.

Examples of post-war camouflage schemes

Sabre CL13B Mk.5 1957-Green/Dk grey/Lt blue
Sabre CL13B Mk.6, F-84F, F-86K, Fiat G-91, Alpha Jet 1960's-RAL 6014/7012/7001
F-104F/G, F-4F 1972- RAL 6014/7012/9006
RF-4E, F-104G late, Tornado RAL 6003/7021/FS.34079 overall
F-4F 1980 standard A Top: RAL 7012/7037/7009 Under: 7036/7001(later 7030)
F-4F 1980 standard B Top: RAL 7012/7039/7009/7037 Under:7030/7035
F-4F 1990 standard Top: RAL Top:7000/7001 Under: FS.35237/36375
Alpha Jet standard 1983 RAL 7021/FS.34079 overall
MiG-29 FS.35237/36320/36375 Nose cone close to RAL 7012
Early tranports RAL 6014/7012/7001
C-160 Transall, Do 28 RAL 6014/7012/9006/2005
C-160, Do 28 modern RAL 7021/6003/FS.34079 overall
This chart has been last revised in September 2006
1914-1918
Colour nameCommentFSHumbrolTamiyaXtracolorPolly SRevellGunze SangyoModel Master
DunkelgrünTopside colour, used until ca. 1917Hu:30X:X241
RotbraunTopside colour, used until ca. 1917 Hu:160
DunkelviolettTopside colour, used until ca. 1917Hu:107X:X242
OlivegrünTopside colour on Fokker aircraftHu:108
BlauTopside colourHu:109
GraublauSea aircraftHu:87
GraubrunSea aircraftHu:98
GrauviolettSea aircraft4*Hu:25 + 2*Hu:153 + 3*Hu:64
BlauPrinted fabric 'polygon' pattern2*Hu:34 + 1*Hu:25
GrünPrinted fabric 'polygon' patternHu:80
LichtbraunPrinted fabric 'polygon' patternHu:119
LichtgrünPrinted fabric 'polygon' patternHu:90
GelbbraunPrinted fabric 'polygon' patternHu:62
GraublauPrinted fabric 'polygon' pattern5*Hu:28 + 1*Hu:25
DunkelviolettPrinted fabric 'polygon' pattern8*Hu:98 + 2*Hu:10 + 2*Hu:107
LichtblauPrinted fabric 'polygon' pattern4*Hu:34 + 1*Hu:25
GraugrünPrinted fabric 'polygon' patternHu:95
GraublauPrinted fabric 'polygon' pattern7*Hu:28 + 1*Hu:153 + 1*Hu:64
GelbPrinted fabric 'polygon' patternHu:103
Licht graublauPrinted fabric 'polygon' pattern7*Hu:28 + 1*Hu:25
GrauviolettPrinted fabric 'polygon' pattern6*Hu:34 + 4*Hu:25 + 2*Hu:153 + 2*Hu:64
RosePrinted fabric 'polygon' pattern5*Hu:28 + 1*Hu:153
Underside blueX:X243
1935-1945, RLMStandard
Colour nameCommentFSHumbrolTamiyaXtracolorPolly SRevellGunze SangyoModel Master
RLM 01 SilberFS:17178Hu:191X:X216
RLM 02 GrauInterior colour, alos used as overall colour on prototypesFS:34159(36165, 24226)34*Hu:29 + 13*Hu:25 + 12*Hu:34 + 2*Hu:82 (4*Hu:168 + 1*Hu:75 + 1*Hu:92 +1*Hu:10, Hu:92)1*T:XF-22 + 1*T:XF-49 (T:XF-22)X:X201P:PCG83 GS:H70
RLM 04 GelbIdentification markingsFS:33538Hu:154X:X213 (markings)GS:H413
RLM 05 ElfenbeinFS:33798
(33618)
RLM 09 Gelbgrün
RLM 21 WeissMarkings / winter camouflageFS:37886 (37880,37875)6*Hu:34 + 4*Hu:41
RLM 22 Schwarz Markings / night camouflageFS:37038Hu:33
RLM 23 RotMarkingsFS:31304(31302)X:X217 GS:H414
RLM 24 DunkelblauMarkingsFS:35053X:X218
RLM 25 HellgrünFS:34090
(34241)
RLM 26 BraunFS:30109
RLM 27 GelbMarkingsFS:33637 (33655,33591)
RLM 61 DunkelbraunPre-war splinter schemeFS:30040 (30109,30117)29*Hu:60 + 9*Hu:99 + 7*Hu:33 + 4*Hu:34 (8*Hu:10 + 2*Hu:33)T:X-09+blackX:X219 GS:H406
RLM 62 GrünPre-war splinter schemeFS:34159(34128)6*Hu:76 + 2*Hu:151T:XF-65X:X220 P:PCG706
RLM 63 HellgrauPre-war splinter scheme. Also used for overall shcemes. Some sources claimthat this and RLM 02 are the same colourFS:36375 (36373, 36314)5*Hu:34 + 1*Hu:156 + 1*Hu:64T:XF-25 X:X221P:PCG711
RLM 65 HellblauLower surfacesFS:35352(35414, 25526) 1*Hu:115 + 1*Hu:34 (Hu:65)T:XF-23 X:X202P:PCG701 GS:H67
RLM 66 Schwartzgrau Cockpit interiors from mid-war onwardsFS:37030 (36081)Hu:92 (Hu:32)X:X203GS:H416
RLM 70 Schwartzgrun Wartime splinter schemeFS:34052(34050) 25*Hu:2 + 14*Hu:34 + 12*Hu:60 + 9*Hu:15 (Hu:91, 5*Hu:75 + 1*Hu:91 +1*Hu:108)
1*T:XF-62 + 1*T:XF-49 (T:XF-27, T:XF-13)X:X204 P:PCG86 GS:H65
RLM 71 DunkelgrunWartime splinter schemeFS:34083(34079, 34102) Hu:116 (Hu:30)T:XF-61 X:X205P:PCG87 GS:H64
RLM 72 GrunWartime splinter scheme on sea aircraftFS:37030(34056)6*Hu:91 + 2*Hu:189 + 1*Hu:3X:X222
RLM 73 GrunWartime splinter scheme on sea aircraftFS:36081 (34092)Hu:149X:X223 (X:X129)
RLM 74 GraugrünTop camouflage on fighter aircraft from 1941. Also referred to asDunkelgrau.FS:36081(36086)Hu:108 (91*Hu:27 + 2*Hu:29 + 1*Hu:34 + 1*Hu:109, Hu:27)7*T:XF-27 + 3*T:XF-19X:X206 (X:X129) P:PCG84 9*GS:H68 + 1*GS:H64 (GS:H068)
RLM 75 GrauviolettTop camouflage on fighter aircraft from 1941. Also referred to asMittelgrau.FS:26132(26122)16*Hu:34 + 7*Hu:33 + 3*Hu:70 + 2*Hu:29 (4*Hu:106 + 1*Hu:98)T:XF-54+51? X:X207 (X:X390)P:PCG707 GS:H69 + a hint of red (GS:H069)
RLM 76 LichtblauLower surfaces on fighter a/c. Also used extensively for night fightersFS:36473,(35622, 35414) 60*Hu:103 + 6*Hu:25 + 1*Hu:34 (175, 2*Hu:76 + 1*Hu:34, 1*Hu:87 + 1*Hu:34)6*T:XF-23 + 4*T:XF-2X:X208P:PCG88 1*GS:H67 + 1*GS:H332 (H417, 1*GS:H314 + 1*GS:H334)
RLM 77 LichtgrauFS:364939*Hu:34 + 2*Hu:28 + 1*Hu:156X:X214 P:PCG85?
RLM 78 HimmelblauLower surfaces of mediterranean schem.FS:35352(35414)67*Hu:34 + 10*Hu:109 + 4*Hu:94 + 1*Hu:25 (5*Hu:4 + 3*Hu:115 + 3*Hu:65)X:X214 P:PCG85?GS:H418
RLM 79 SandbraunMediterranean schemeFS:33448 (33434)40*Hu:24 + 37*Hu:73 + 17*Hu:150 (4*Hu:154 + 3*Hu:94 + 1*Hu:34)X:X209 P:PCG708
RLM 79a SandgelbAnother variant of RLM 79FS:30219(30215)Hu:62 X:X224GS:H66
RLM 80 OlivegrünBlotches in mediterranean schemeFS:34079 (34052)14*Hu:80 + 3*Hu:25 + 2*Hu:33 + 1*Hu:34 (3*Hu:91 + 2*Hu:75 + 2*Hu:108)T:XF-58?X:X215 P:PCG709 GS:H420
RLM 81 BraunviolettLate-war topside camouflageFS:30045(34087, 30118, 34088)3*Hu:150 + 2*Hu:33 (3*Hu:163 + 4*Hu:108 + 3*Hu:33, 85%*Hu:173 + 9%*Hu:153 + 6%*Hu:85, Hu:155)T:XF-62?/13?X:X210 GS:H421 (GS:H304)
RLM 82 LichtgrünLate-war topside camouflage. Often confused with 83FS:340966*Hu:116 + 6*Hu:177 + 1*Hu:163 (105)T:XF-27?/61?X:X212 GS:H422
RLM 83 DunkelgrünLate-war topside camouflage. Often confused with 82FS:34138,3408366*Hu:3 + 26*Hu:15 + 5*Hu:60 + 1*Hu:24 (Hu:116, 4*Hu:117 + 1*Hu:81)T:XF-26X:X211P:PF51 GS:H423
RLM '84' (?)
Yellow-Green
Used towards end of the war. Designation RLM 84 is speculatory.FS:34554
Light Green-GreyUsed towards end of the war on lower surfaces of fighter a/cFS:34583(34672)T:XF-21X:X007GS:H74
Red PrimerPrimer colourFS:31310
1956-
Colour nameCommentFSHumbrolTamiyaXtracolorPolly SRevellGunze SangyoModel Master
RAL 1002 SandgelbFS:10260Rev:11 Sand yellow
RAL 1007 Chrome YellowFS:33538Hu:188/154 Insignia yellow
RAL 1026Hu:194 Rev:312 Fluorescent yellow
RAL 1028Hu:197 Rev:310 Lufthansa yellow
RAL 2004Hu:18 Rev:30 Orange
RAL 2005 LeuchtorangeHu:192 Dayglo orange?X:X253
RAL 3000Bright redFS:21105Hu:60(19) Rev:330
RAL 3004Hu:20/107 Rev:331 Crimson
RAL 3022 Salmon pink
RAL 3026Hu:209 Rev:332 Fire orange
RAL 5008 GraublauX:X264 Rev:351
RAL 5013Hu:198 Rev:350 Lufthansa blue
RAL 5014 Pigeon blueFS:35488Hu:157
RAL 6003 OlivegrunFS:34102Hu:86 X:X261 Rev:361
RAL 6014 GelbolivFS:24064Hu:155 X:X251
RAL 6020 Chrome greenFS:34079Hu:116(195) Rev:363 Dark Green
RAL 7000 Squirrel greyFS:35237Hu:145 Rev:57 Medium Grey
RAL 7001 SilbergrauFS:36375Hu:64/127 X:X255 Rev:374
RAL 7005 Mouse greyHu:140 Rev:47
RAL 7009 GrungrauHu:(116)91 X:X256 Rev:67
RAL 7011 Iron greyFS:36118Hu:125
RAL 7012 BasaltgrauFS:26152Hu:(27)79 X:X254 Rev:77
RAL 7013 Brown greyHu:98Rev:46
RAL 7021 SchwartzgrunX:X262 Rev:9
RAL 7023 DunkelgrauHu:141 Concrete greyX:X263
RAL 7030 SteingrauX:X257 Rev:75(162)
RAL 7031Hu:27 Rev:79 Sea Grey
RAL 7032 Pebble greyFS:36408Rev:70
RAL 7035 LichtgrauFS:35630Hu:196 X:X260 Rev:371
RAL 7037 StaubraunHu:106X:X258
RAL 7038 Agate greyHu:183 Rev:372
RAL 7039 QaurzgrauHu:92X:X259
RAL 7042 Traffic grey A FS:36270Hu:167
RAL 8017 BrownHu:10
RAL 8023Leather brownHu:62 Rev:85
RAL 9001 CreamFS:37886Hu:34 X:X252 Rev:5
RAL 9005 Jet blackFS:37038Hu:21/85 Rev:7
RAL 9006 White aluminium FS:17178Hu:56
RAL 9010Hu:22/130 Rev:4 White (gloss?)
RAL 9011Hu:33 Rev:8 Black (matt?)
Back to main article

n


This page:
Has been last updated:
The URL of the page is:
Downloaded at:


© Copyright 1997-2006 by IPMSStockholm and the Community Members. All Rights Reserved.
The layout and graphics of this site, HTML and program code are© Copyright 1997-2006 Martin Waligorski. Used by permission.
Terms of use:This site is an interactive community of enthusiasts interested inthe art of scale modelling of aircraft, armor, figures, spacecraftand similar subjetcs. All material within this site is protected undercopyright, and may only be reproduced for personal use. Youmust contact the Author(s) and/orEditor for permission to use any material on this sitefor any purpose other than private use.