Vertex Programming Software Download

by Loc Q Nguyen & Murali Madhanagopal

Download FFFF - Fast Floating Fractal Fun for free. FFFF is the fastest Win32/OSX/Linux/IRIX Mandelbrot generator. Features OpenGL, realtime zoom, SSE/AltiVec QuadPixel, SSE2/3DNow! Get to know Microsoft researchers and engineers who are tackling complex problems across a wide range of disciplines. Visit the Microsoft Emeritus Researchers page to learn about those who have made significant contributions to the field of computer science during their years at Microsoft and throughout their career. The Yaesu brand is well known among ham radio aficionados and is synonymous with premium quality ham radios. From stationary multi-feature communications equipment to portable devices, YAESU has consistently represented the best in communications equipment to the world's top DX'ers for over half a century.


Vertex Radio Programming Software Download

In this paper, Intel Graphics refers to the Intel® Graphics Media Accelerator (Intel® GMA) graphics core. Built into the chipset and integrated into the motherboard, the graphics core shares the system memory with the operating system to keep the system performance at a very low cost. Intel Graphics addresses a wide range of graphics usages in mainstream personal computers. Since it is integrated into the motherboard, Intel Graphics consumes much less power than a discrete graphics card does. It is however powerful enough to allow users to perform expensive 3D graphics processing. The goal of this document is to list the set of OpenGL Extensions supported in Intel® 4 Series Express Chipsets for a quick reference. Developers who write 3D applications on OpenGL may refer to this document for a complete list of extensions supported in an Intel chipset.

For Intel chipset naming convention, please refer to the whitepaper “Quick Reference Guide to Intel Graphics” [1].

Supported OpenGL Extensions

Intel® 4 Series Express Chipsets support OpenGL version 2.0 and some extensions from OpenGL 2.1 (Pixel Buffer Objects) and OpenGL 3.0 (Frame Buffer Objects, floating point textures and half float pixels).

The table below summarizes the OpenGL extensions supported by Intel® 4 Series Express Chipsets and future chipsets. A brief description of each extension is also included in the table for reference. For a full detailed description of these extensions, readers are encouraged to check OpenGL Extension Registry official website. [2].
Note that each extension consists of multiple words. These words are connected each other by underscores. The first word usually starts with GL (core OpenGL) or WGL for Win32 system dependent. The second word indicates the company that developed that extension (e.g., ARB for Architecture Review Board, EXT for Extensions agreed by multiple vendors, INTEL for Intel Corporation, etc). The following words (usually not with capital letters) indicate the extension name.

Vertex Vx-160 Programming Software Download

In the reference table, the first column specifies the extension; the second column provides a brief description of the extension; the third column shows the first driver version for Windows* XP/Vista that the extension is supported. For example, for the extension GL_ARB_point_sprite, the first version of driver in Windows XP* that supports this extension is 14.36; and the first version of driver in Windows Vista* that supports this extension is 15.11. Drivers will support all extensions supported by a previous version of the driver. All extensions supported in 15.11 will be supported by default in 15.14. Same is the case with Windows XP drivers, 14.38 will support all extensions supported by 14.36. Also, 14.x means all driver versions of Windows XP support the extension. 15. x means all Windows Vista driver versions support this extension.

API Support

OpenGL API Support

Windows Vista Driver

Windows XP Driver

OpenGL 1.5



OpenGL 2.0



OpenGL 2.1




GLSL Support

GLSL (Open GL Shading language) is high level shading language which enables user to use a C like programming language to control the graphics pipe line for vertex and fragment operations. GLSL supports C programming constructs like branches, loops, if-else, while, break and continue.

GLSL Support

Windows Vista Driver

Windows XP Driver

GLSL 1.1



GLSL 1.2



ARB Extensions

OpenGL ARB extension

Brief description

ARB Extensions available on all driver versions (14.x and 15.x)


Allows multiple texture objects to be bound at the same time with separate blend modes and map coordinates


Adds an interface for transferring data to and from the OpenGL pipeline


Define an area of a window to be saved in memory for quick restores.


Provides a mechanism to anti alias all GL primitives:points, lines, polygons, bitmaps, and images. Currently supports only MAX_SAMPLE=1. MAX_SAMPLE=4 will be supported in future releases


Provides a mechanism to antialias all GL primitives: points, lines, polygons, bitmaps, and images.


Texture environment function ADD


Provides a new texture generation scheme for cube map textures..


Allow an application to determine which WGL extensions are supported by a device.


Provide the capability to query pixel format attributes and to choose from the list of supported formats.


Allow preprocessing of image data in background.


Allow an application to render to non visible rendering buffers (pixel buffers).


Allows OpenGL applications to use compressed texture images


Defines an additional texture clamping algorithm


Supports additional geometric characteristics of points.


Allows programmable texture combiner operations


Provides capabilities to use the texture color from other texture units as sources to the COMBINE_ARB environment function.


Adds new operation to the texture combiner operations.


Extends the set of texture wrap modes to include an image twice the size with a mirror image


Define a new texture environment function ADD.


Produces Boolean texture value, used to implement shadow maps


Provides a set of functions to directly set the current raster position in window coordinates


Provides a method for defining vertex program instruction sequences for vertex programs


Provides a method for defining fragment program instruction sequences for fragment programs.


Provides interface to cache vertex array data in memory buffer objects


Used to query the number of pixels drawn by a primitive operation.


Adds a new texture target that supports 2D textures.

ARB Extensions available from drivers 14.36 and 15.11


Provides functions for creating shader objects and program objects, for compiling shader objects etc.


Adds programmable vertex level processing to OpenGL


Adds functionality to define fragment shader objects.


Indicated open gl shading language is supported.


Supports relaxing Open GL power-of-two size restrictions across all texture targets


Allow applications to replace the existing texture coordinates with point sprite texture coordinates.


Extends ARB_fragment_program and ARB_fragment_shader to allow multiple output colors


Permits buffer objects to be used not only with vertex array data, but also with pixel data.

ARB Extensions available from drivers 14.38 and 15.13


Adds pixel formats or visuals with floating-point RGBA color components.


Adds pixel formats with floating-point RGBA color components.


Adds texture internal formats with 16- and 32-bit floating-point components.


Allows draw/read pixel data in 16-bit floating point format. Apply to DrawPixel ()/ReadPixel () as well as to texture creation functions and filter/color map functions.

Vendor and EXT Extensions

Vendor and EXT extension

Brief description

Vendor Extensions available on all driver versions (14.x and 15.x)


Provide a reverse order alternative to image format RGBA.


Provide formats which match memory layout of Windows DIBs.


Add a constant color in blending equations to increase blending capability.


Define a function that allows independent setting of the RGB and alpha blend factors for blending operations.


Increase the blending capability by defining two new blending equations.


Add two blending equations which produce the difference of its left and right hand sides.


Provide an option for not requiring clip volume clipping for primitives.


Define an interface so that static vertex array can be cached or precompiled.


Include an explicit per-vertex fog coordinate to be used in fog computations.


Provide support for packed pixels in memory.


Allow the normal vector to rescale after being multiplied by the inverse model view matrix.


Add a second color to rasterization.


Allow maximum and minimum wrapping of stencil values.


Add more texture compression functionality for S3TC format.


Define a new texture environment function ADD.


Define a new texture environment function COMBINE_EXT.


Provide a general mechanism for supporting anisotropic texture filtering schemes.


Introduce a new texture wrap mode that uses a texture map twice as large at the original image.


Provide two new texture coordinate generation modes.


Allow an application to control the periodicity of color buffer swaps.


Changes depth value of polygons by an offset


Supports various resolution of color component in texture images


Provides 3 dimensional texture mapping


Allows redefining existing portion of a texture image Fable lost chapters pc download.


Defines methods to load texture images directly from framebuffer


Allows naming of texture objects


Imposes constraints on texture level of images


Allows definition of multiple geometry primitives


Allows methods to derive entire mipmap array values


Texture coordinate clamping algorithm


Provides additional geometric characterization of points


Additional blending equation provided


Defines new depth texture format


New vertex rendering instructions


Specifies RGB components for secondary color


Handles multiple list of vertices in one call


Alias of GL_EXT_multi_draw_arrays


Provides a way to change the mipmap computations


Provide four additional blending factors to have special effects.


Adds new operation to texture combiner operations.


Add new texture target to support 2D textures


Allows usage of points than quads


Allows support of all binary texture comparison functions


Allows two sided stencil testing and all related stencil operations


Specifies texture data in compressed s3TC format


Additional texture compression support for FXT1 format


Used to find which WGL extensions are supported

Vendor Extensions available from drivers 14.38 and 15.13


Allows changes to stencil format


Introduces separate RGB and alpha blend values


Define a simple interface for drawing to rendering destinations.

Vendor Extensions available from drivers 14.38 and 15.13


Add new uncompressed and compressed color texture formats with sRGB components.

Pixel Buffer Object and Frame Buffer Object Support

OpenGL uses a pipelined architecture; each unit needs data from previous section to complete its job. The vertex data and pixel data are processed through the pipeline, combined and written to the frame buffer for display. Rasterization is the process which combines geometry and pixel data and writes as a fragment. Fragment is an object containing depth, width, color, points and other information necessary for display. Each fragment maps to a pixel in the screen. A frame buffer is a set of buffers containing color, depth, stencil and accumulation buffers. However this frame buffer is windows system provided and managed by the operating system.

Frame Buffer Object (FBO)

The GL_EXT_framebuffer_object extension defines an interface that allows rendering to one or more off screen frame buffers other than the default frame buffer provided to OGL by the operating system. The introduction of these newly defined rendering destinations, referred to as frame buffer-attachable images, provide the functionality that allows:

  • Off screen rendering without the window’s size limitation
  • Direct rendering to textures without the necessity to use glCopyTexImage()
  • Rendering to multiple locations with the use of fragment shaders
  • Rendering to the stencil and depth logical buffers with the use of the newly introduced renderbuffer object.

FBO is supported by Intel 4 series chipsets in Vista (15.11) and XP (14.36) graphics drivers.

Pixel Buffer Object (PBO)

Pixel Buffer Object expands vertex buffer object to store both vertex and pixel data. ARB_vertex_buffer_object is the extension to support vertex buffers. Vertex Buffer objects (VBO) are actually created, when a glBindBuffer() function is called for the first time for a given buffer name.
The 2 pixel path functions affected by PBO are:

  • glDrawPixels() - draws pixels from PBO directly to the frame buffer
  • glReadPixels() - Reads pixels directly from the frame buffer and write the data into PBO.

Two main groups of functions, affected by PBO are:

  • glTexImage*D() – Used to transfer texture from the user memory to the OGL-managed memory
  • glGetTexImage() – Used to transfer texture to the user memory

PBO introduces 2 new targets for binding buffer objects – GL_PIXEL_PACK_BUFFER_ARB and GL_PIXEL_UNPACK_BUFFER_ARB. glReadPixels() and glGetTexImage() are pack pixel functions, whereas glDrawPixels() and glTexImage*D() are unpack operations.
PBO is supported by Intel® 4 Series Express Chipsets in Vista (15.11) and XP (14.36) graphics drivers.

Vertex Vx-261 Programming Software Download

Examples of Using OpenGL extensions

In this section, two examples show how OpenGL extensions can be used.

Using GL_EXT_abgr

The first example illustrates the use of the extension GL_EXT_abgr.

GL_EXT_abgr extends the list of color formats in order to fit big-endian machines. In this format, the pixel color data consists of four components: alpha, blue, green, red, and these components are stored in this order. The color of a pixel is the combination of blue, green and red. The alpha component is the degree of color transparency. Each component has a value between 0 and 255. The alpha value 0 means full transparency, 255 means opaque, and a value between 0 and 255 means some degree of transparency between full transparency and opaque.

A function, called CreateImages, is used to create four images which have ABGR format. The first image is a red square with a degree of transparency (0x80 in this example). The second image is a green square with the same degree of transparency. The third image is a blue square with the same degree of transparency. The last image is a brown square with the same degree of transparency; the brown color is a combination of green and red components.

The function called RenderScene is used to draw the above images. In this function, the API call glDrawPixels is used to render the images. Note that in glDrawPixels, the format GL_ABGR is used to draw the image.

The main program starts by checking whether or not the extension GL_EXT_abgr is supported in the current GPU. If it is not supported, the program simply exits; otherwise, it creates the above images in the ABGR formats and renders them.

If the graphics hardware supports GL_EXT_abgr, the result is shown in the picture below. The overlap sections of the four squares have different colors because of the transparency effect of the squares.

Using OpenGL shading language

In this section, we show an example of using OpenGL shading language.

The code below shows how the application uses the vertex shader and fragment shader. The source code of vertex and fragment shaders are first loaded with the API glShaderSourceARB, then they are compiled with glCompileShaderARB to create shader objects. These shader objects are attached to a program object called g_program. A program object is an OpenGL data structure object that contains all shader objects used a specific task. The compiled shader objects are then linked with glLinkProgramARB.

The function called RenderShadedCube is used to render a rotated cube in three dimensions. It defines the eight vertices of a cube. The cube has six square faces, and each face consists of four vertices. In each square face, four vertices have four different colors. The API call glUseProgramObjectARB tells the compiler to install a program object’s executable code.

The main program starts by checking the OpenGL version supported by the GPU. Since GLSL becomes part of OpenGL starting version 2.0, we can query the shading version if OpenGL version is greater or equal to 2.0. If the OpenGL version is 1.x then we may check the four extensions for GLSL which determines whether or not the current GPU can run GLSL or not. If GLSL is not supported, the program simply exits; otherwise, it renders the rotated cube using the predifined vertex and grament shaders.

Finally, the source code of the vertex shader is shown below. Note that it is written in OpenGL shading language, a high-level procedural language.

Similarly, the source code of the fragment shader is shown below.

We ran this program on a computer equipped with the Intel® 4 Series Express Chipset. A rotated cube is rendered as the result. Note that the shading color on each cube face is the result from the shaders.


Today, Intel Graphics represents a large volume of deployed graphics hardware in the consumer graphics market segment. Since the number of OpenGL applications continues to grow, this article serves as a quick reference for developers who implement OpenGL applications on Intel® 4 Series Express Chipsets. Intel also offers tools to help developers to optimize their applications for Intel® Graphics Technology such as Intel® VTune Performance Analyzer [3], Intel® Graphics Performance Analyzers [4], Intel® Graphics Media Accelerator Driver [5], etc.


  1. Quick Reference Guide To Intel Integrated Graphics

Vertex Programming Software Download

About the Authors

Vertex 160 Programming Software Download

Loc Q Nguyen received his M.B.A. from the University of Dallas, Texas. He holds a Master’s degree in Electrical Engineering from McGill University, Canada and a Bachelor's in Electrical Engineering from École Polytechnique, Université de Montréal, Canada. He is currently an Application Engineer with Software and Services Group at Intel Corporation.

Murali Madhanagopalreceived his M.S. in Computer Information Systems from Texas A&M University, College Station and his bachelor’s degree in Computer Engineering from College Of Engineering Guindy, Anna University, India. He is currently a Graphics Architect with Visual Computing Group at Intel Corporation; working with ISV’s to enable Intel graphics features on their products.

CHIRP is a free, open-source tool for programming your amateur radio. It supports a large number of manufacturers and models, as well as provides a way to interface with multiple data sources and formats.

To get started:

Vertex Ce82 Programming Software Download

  1. Download CHIRP for your platform
  2. Check out the 'How_To_Get_Help' page, and the rest of the Documentation.
  3. Join the mailing list!
  4. Be sure to review the FAQ.
In case you ran into a problem with Chirp:

Vertex Vx 3200 Programming Software Download

  1. Before you open a new ticket, you might want to consult the documentation. On the right side of this web page, you will find some links to the Wiki. It contains good input for many re-occuring issues.
  2. Also, please perform a search through all open and closed issues. Maybe someone else had the same problem before, and a solution is already available.
  3. If your problem is about how to use Chirp with an already supported radio, then you should ask that question in the mailing list.
  4. Once you have looked through the Wiki and searched all open/closed issues, you can open a new ticket (did you ask on the mailing list?). There, you may file a bug report, request a new feature, or request the implementation of a new radio. Please be detailed and follow the instructions in 'How To Report Issues'.

If you are a vendor and want to have your radio supported by chirp, please see InformationForVendors

Supported Radio Models¶

  • AR-F3 (use Baofeng UV-82III)
  • AR-F8 (use Wouxun KG-UV8D)
  • DJ-175T
  • DJ-596T
  • DJ-G7EG
  • DR-03T
  • DR-06T
  • DR-135T
  • DR-235T
  • DR-435T
  • A-5R
  • A-8S
  • AT-778UV
  • AT-5888UV
  • OBLTR-8R
  • TERMN-8R
  • AR-5
  • AR-6
  • AR-7 (use Radtel T18)
  • BST-2100 (use Baofeng BF-888)
  • 997-S (Foscam Digital Technologies) (use UV-5R)
  • B-580T (use UV-5R)
  • BF-88E (use BF-888S)
  • BF-666S/777S/888S
  • BF-9100 (use BF/T1)
  • BF-A58, BF-A58S
  • BF-C2/C5 (use BF-888S)
  • BF-E500S (use UV-5R)
  • BF-F8, F8+ (use UV-5R)
  • BF-F8+III (use Radioddity UV-5RX3)
  • BF-F8HP (3 power levels)
  • BF-F8X3 (use BF-A58S)
  • BF-F9 (use UV-5R)
  • BF-F9V2+ (use BF-F8HP)
  • BF-F11 (use BF-A58S)
  • BF-H6 (use TIDRADIO TD-H6)
  • BF-R3 (use Radioddity UV-5RX3)
  • BF-R5 Mini (use BF-888S)
  • BF-S5 Plus (use UV-82III)
  • BF-T1
  • BF-UV9R+HP (use UV-82WP)
  • BF-UV10R (use BF-F8HP 3 power levels)
  • BF-UVF10 (use BF-A58S)
  • BF-UVB2+ (use UV-5R)
  • BF-V9 (use BF-888)
  • BF-V85 (use UV-B5)
  • BF-X9 (use Radioddity UV-5RX3)
  • F-11 (Import Communications)
  • FF-12P (use UV-5R)
  • GT-1 (use BF-888S)
  • GT-3, GT-3 MK II (use UV-5R)
  • GT-3TP (use BF-F8HP)
  • GT-3WP
  • GT-5 (use UV-82)
  • GT-5TP (use UV-82HP)
  • Mini (use BF-T1)
  • UV-3R
  • UV-5R and variants (2 power levels)
  • UV-5R HTQ (use BF-F8HP)
  • UV-5R MK4, MK5 (use BF-F8HP)
  • UV-5R V2+, UV-5R2 (use UV-5R)
  • UV-5R+ (use BF-F8HP)
  • UV-5R++ (use UV-5R)
  • UV-5R7W (use BF-F8HP)
  • UV-5RA, UV-5RA+, UV-5RAX, UV-5RAX+ (use UV-5R)
  • UV-5RB (use UV-5R)
  • UV-5RC, UV-5RC, UV-5RCX+ (use UV-5R)
  • UV-5RD (use UV-5R)
  • UV-5RE, UV-5RE+ (use UV-5R)
  • UV-5RG, RK, RQ, RS, RT, RU (use UV-5R)
  • UV-5RHP (use BF-F8HP)
  • UV-5RIII (use Radioddity UV-5RX3)
  • UV-5RM HP (use BF-F8HP)
  • UV-5RTP (use BF-F8HP)
  • UV-5RWP (use UV-82WP)
  • UV-5RX3 (use Radioddity UV-5RX3)
  • UV-5S, 5X (use UV-5R)
  • UV-5XP
  • UV-6
  • UV-6R
  • UV-8R (use UV-82HP)
  • UV-9R/9R PLUS/9R ERA
  • UV-9S (use Radioddity UV-5RX3)
  • UV-9X+ (use UV-82HP)
  • UV-10R (use UV-5R)
  • UV-59T (use Radioddity UV-5RX3)
  • UV-82/82C/82L/82X
  • UV-82HP/82DX/82HX (3 power levels)
  • UV-82III (1 x PTT)
  • UV-82III (2 x PTT) (use Radioddity UV-82X3)
  • UV-82T (use Radioddity UV-82X3)
  • UV-82WP
  • UV-82X3 (use Radioddity UV-82X3)
  • UV-920 (use UV-5R)
  • UV-B2 (use UV-82)
  • UV-B2+, B3+ (use UV-5R)
  • UV-B5, B6
  • UV-S9 (tri-power: use BF-F8HP)
  • UV-S9/S9T (tri-band: use Radioddity UV-5RX3)
  • UV-X9 (use UV-82HP)
  • BJ-218 (Variant of Luiton LT-725uv)
  • BJ-318 (use Baojie BJ-218)
  • BJ-9900
  • BJ-UV55
  • X3+
  • GMRS-50X1
  • GMRS-V1
  • MURS-V1
  • UV-2501
  • UV-2501+220
  • UV-25X2
  • UV-25X4
  • UV-5001
  • UV-50X2
  • UV-50X3
  • UV-5X3
  • UV-85 (use Baofeng UV-5R)
  • UV-87 (use TYT TH-UV88)
  • Micron UV (Variant of Anytone AT-778UV)
  • ESY-88 (Variant of Baofeng BF-888s)
  • FD-150A
  • FD-160A
  • FD-268A, B
  • FD-288A, B
  • FD-450A
  • FD-460A, UH
  • GV-8S
  • GV-9S
  • BJ-218 (Variant of Luiton LT-725uv)
  • HT-5RX3 (use Radioddity UV-5RX3)
  • HT-U222 (use Retevis RT22)
  • RS-UV3
  • IC-80AD
  • IC-91, IC-92AD
  • IC-208H
  • IC-746
  • IC-910H
  • IC-2100H
  • IC-2200H
  • IC-2300H
  • IC-2720H
  • IC-2730A
  • IC-2820H
  • IC-7000
  • IC-7100
  • IC-7200
  • IC-E90
  • IC-P7
  • IC-Q7A
  • IC-T70
  • IC-T7H
  • IC-T8A
  • IC-T90
  • IC-V82, IC-U82
  • IC-V86
  • IC-W32A, E
  • ID-31A
  • ID-51, ID-51+
  • ID-80H
  • ID-800H
  • ID-880H
  • ID-RPx000V/RP2x
  • HR-2040 (use Anytone AT-5888UB)
  • KT-980HP (Variant of Baofeng UV-5R)
  • JT220M
  • JT270M, MH
  • JT2705M (Variant of Waccom Mini 8900)
  • JT-6188 Mini (Variant of QYT KT8900)
  • JT-6188 Plus (Variant of Waccom Mini 8900)
  • TH-D7, TH-D7G
  • TH-D72
  • TH-F6
  • TH-F7
  • TH-G71
  • TH-K2
  • TK-260/270/272/278
  • TK-260G/270G/272G/278G
  • TK-360/370/372/378
  • TK-360G/370G/372G/378G/388G
  • TK-760/762/768
  • TK-760G/762G/768G
  • TK-860/862/868
  • TK-860G/862G/868G
  • TK-7102/8102/7108/8108
  • TK-2180/3180/7180/8180
  • TM-271
  • TM-281
  • TM-471
  • TM-D700
  • TM-D710, TM-D710G
  • TM-G707
  • TM-V7
  • TM-V71
  • TS-480HX/SAT
  • TS-590S/SG
  • TS-850
  • TS-2000
  • IP-620
  • NC-630A
  • LE-C2 (Variant of Baofeng BF-C2)
  • VV-898, VV-898S, VV-898E
  • LT-316 (Variant of Retevis RT22)
  • LT-580 VHF, UHF
  • LT-588UV (Variant of QYT KT8900)
  • LT-725UV
  • LT-898UV (Variant of Leixen VV-898)
  • MR-UV1 (use TYT TH-UV88)
  • DBR2500 (Variant of Anytone AT-778UV)
  • UV-5R-3
  • UV-7RX (use Retevis RT6)
  • OTG Radio v1
  • MT-700
  • (see Baofeng)
  • DB-50M (use Anytone AT-5888UV)
  • DB-750X (use Anytone AT-5888UV)
  • PX-2R (UHF)
  • PX-777
  • PX-888K
  • KT980+ (same as KT-8900D)
  • KT5800
  • KT7900D
  • KT8900 (same as KT-8900)
  • KT8900R
  • KT8900D
  • KT-8R
  • KT-UV980 (Variant of Waccom Mini 8900)
R&L Electronics
  • UV-5R 3 band (use Radioddity UV-5RX3)
  • DB25 (Variant of QYT KT8900D)
  • GA-2S
  • GA-5S
  • GA-510
  • QB25
  • R2
  • UV-5R EX
  • UV-5RX3
  • UV-82X3
  • RT-10 (use Retevis RT22)
  • T18
  • H777
  • H777 (FRS) (use Retevis H777 Plus)
  • H777 Plus
  • RT1
  • RT5 with 2 power levels (use Baofeng UV-5R)
  • RT5 with 3 power levels (variant of Baofeng BF-F8HP)
  • RT5R, RT5RV (Variants of Baofeng UV-5R)
  • RT6
  • RT21
  • RT22
  • RT22
  • RT23
  • RT24
  • RT26
  • RT622
  • RT85
  • RT95 (Variant of Anytone AT-778UV)
  • RT-B6 (use Baofeng UV-B5)
Rugged Radios
  • RH5R, RH5R-V2 (use Baofeng UV-5R)
  • RH5X (Variant of Baofeng BF-A58)
  • GT-3TP (use Baofeng BF-F8HP)
  • GT-890 (Variant of QYT KT8900)
Standard Horizon
  • (see Yaesu)
  • KT8900D (Variant of QYT KT7900D)
  • MTR01 (use Radioddity R2)
  • TD-Q8A
  • TI-F8+ (Variant of the Baofeng BF-F8HP)
  • TW-325
  • UV-5R Pro (Variant of the Baofeng BF-F8HP)
  • UV-82 Pro
  • BF-F8TD (use TD-UV5R TriPower)
  • TD-UV5R TriPower
  • TD-H6
  • TD-M8
  • UV-985 (use Baofeng UV-5R)
  • TH-350
  • TH-7800
  • TH-9000 (each 144, 220, 440)
  • TH-9800
  • TH-UV3R, TH-UV3R-25
  • TH-UV8000D/E
  • TH-UV88
  • TH-UVF1
  • TH-UVF8D
  • UV-E5, UV-E5 MK II (use Baofeng UV-5R)
Vertex Standard
  • (see Yaesu)
  • MINI-8900
  • KD-C1 (Variant of Retevis RT22)
  • KG-816/818
  • KG-UV2D (use KG-UVD1P)
  • KG-UV3D (use KG-UVD1P)
  • KG-UV5D (use KG-UVD1P)
  • KG-UV6D/UV6X
  • KG-UV7D (use KG-UV6)
  • KG-UV8D
  • KG-UV8D Plus
  • KG-UV8E
  • KG-UV8T
  • KG-UV9D Plus
  • KG-UV9P (use KG-UV9D Plus)
  • KG-UVD1P
  • FT-1D
  • FT-2D
  • FT-3D
  • FT-4VR
  • FT-4XE, R
  • FT-25R
  • FT-50R
  • FT-60R
  • FT-65E, R
  • FT-70D
  • FT-90R
  • FT-450D
  • FT-817/ND
  • FT-818/ND
  • FT-857/D
  • FT-897
  • FT-1500M
  • FT-1802M
  • FT-2800M
  • FT-1900R/2900M
  • FT-7100M
  • FT-7800/7900
  • FT-8100
  • FT-8800
  • FT-8900
  • FTM-350
  • FTM-3100 (use FTM-3200D selection)
  • FTM-3200D
  • VX-2R
  • VX-3R
  • VX-5R
  • VX-6, 6R
  • VX-7R
  • VX-8, 8R, 8D, 8G
  • VX-170
  • VXA-700
  • YC-M04VUS (Variant of Anytone AT-778UV)
  • BJ-218 (Variant of Luiton LT-725uv)
  • MP-300 (Variant of QYT KT8900)
  • MP-380 (use QYT KT8900D)
  • MP-800 (use TYT TH-9800)
  • ZT-V8, V8A, V8A+ (use Baofeng UV-R5)
  • ZT-X6 (Variant of Retevis RT22)

Note that not all functionality is supported on all radio models. Not all models and variants are listed here. For a more complete view of everything supported, as well as which features are supported for which model, take a look at overview of supported features for the latest build.

Note that radios marked as 'variant' are supported via a Aliasing_for_radio_clones feature.

Other Data Sources¶

File Formats
  • Comma Separated Values (.csv)
  • Comma Separated Values generated by RT Systems (.csv)
  • EVE for Yaesu VX-5 (.eve)
  • Kenwood HMK format (.hmk)
  • Kenwood commercial ITM format (.itm)
  • Icom Data Files (.icf)
  • ARRL TravelPlus (.tpe)
  • VX5 Commander Files (.vx5)
  • VX7 Commander Files (.vx7)