Zed-FULL plus

Zed-FULL plus provides separate workflows for reading, identifying and cloning supported fixed-code and encrypted transponders. Identify the source key’s transponder family before choosing a compatible blank chip. Reading support does not mean every chip can be cloned. Philips, Texas and Megamos families require different chips and conditions; the manufacturer specifies an internet connection for Hitag2 cloning. Check the current transponder list, device software and application licence together.

Cloning one remote to another and registering a new remote to a vehicle are different operations. Manufacturer examples include Fiat remotes with 48 transponders and one, two or three buttons, plus Hitag2-based remotes. These applications use the appropriate IEA emulator remote. Appearance alone does not establish compatibility: check the transponder system, frequency and application. Supported remote resetting operations may require separate software packs and connection accessories.

Zed-FULL plus can prepare supported blank transponders for specific vehicle systems. Families such as PCF7935, PCF7936 and Texas 4D-60 use different preparation workflows. Pre-coding is not registration to the vehicle: the prepared key must subsequently be registered using the appropriate programming method. Supported blanks can therefore reduce the need to stock a separate prepared chip for every vehicle. Match the chip type and vehicle system in the manufacturer’s current list.

EEPROM and MCU applications work with data from the relevant immobiliser, ECU or BSI module. Supported systems may allow PIN calculation, pre-coded transponder preparation or working key data generation. The device displays application-specific module and board images. Connections vary by module; some operations require removal, soldering or a dedicated adapter. The PC software can also process supported binary or hex files. Verify the module type, wiring diagram and read data before continuing.

Zed-FULL plus offers key, remote, proximity key and card registration through the diagnostic socket on supported vehicles. Available PIN reading and key deletion functions depend on the vehicle system. A listed make and model does not imply support for every year or key scenario. Check the year range, operation columns and official PDF notes together. Gateway or application-specific cables may be needed in addition to the standard OBD2 cable. Follow the instructions for the selected vehicle.

The manufacturer describes additional functions for supported systems, including PIN calculation from keys or vehicle information, selected transponder resets and remote unlocking. Mercedes-Benz IR, BMW EWS/CAS and selected Fiat ECU applications do not share one connection layout. Software, key or processor type and accessories must be assessed for each operation. For example, ZFH-MBNEC is an adapter for supported Mercedes-Benz NEC key processors. Brand-level coverage does not imply support for every security system.

The 7-inch HD-TFT touch screen displays application menus, vehicle selections and instructions for supported workflows. EEPROM applications can show module and board images; transponder and remote operations can display relevant product information. Physical directional buttons, ESC and ENTER provide menu control. Transponder, card and Mercedes IR reading areas serve different purposes. A connection or antenna’s function should not be inferred solely from the shape on the front panel.

Alongside standalone applications, Zed-FULL plus offers functions that use a computer connection. USB supports driver installation, board updates, EEPROM files and supported online operations. The PC software requires a connected device and has limited functionality without internet access. Zed-NET supports credit loading and eligible activations. Main, transponder, OBD, remote and EEPROM boards and SD card content have separate update areas; check the relevant versions before an application.