EU intercom

CAME / BPT TST01 Proximity Cards Explained (RF/64)

Security ID Systems ·

The CAME / BPT TST01 proximity card uses a proprietary RF/64 ASK Manchester encoding scheme — a 32-bit read-only format in the EM-Marin family that is electrically distinct from standard EM4100, which is why off-the-shelf read-write tools and generic T5577 blanks almost universally fail on it. If you manage a gate or intercom installation built around this credential and need additional cards, the only reliable path is a CAME TST01 compatible card produced on an RF/64-class read IC matched to the original field parameters.

CAME, BPT and Italian Gate and Intercom Access

CAME S.p.A. is an Italian manufacturer of gate automation, barriers, and building access equipment with a substantial installed base across Europe and the Middle East. BPT (Building Products & Technologies) was a complementary brand within the CAME group, producing video door entry and intercom panels that share the same credential ecosystem. In practice, a TST01 card issued for a BPT intercom panel and one issued for a CAME gate controller are the same physical credential — the two product lines converged on a common proximity format decades ago.

Because CAME and BPT installations are common in apartment blocks, gated communities, and commercial premises across Italy, Spain, France, and the UK, the demand for replacement or additional credentials is steady. Property managers and facilities teams frequently find themselves needing five or ten extra cards for new tenants or staff, without access to the original installer or the system programming interface. That is precisely the scenario our intercom and residential entry credential supply chain is built to address.

CAME gate controllers also appear in HOA-managed communities and private estates, often running in parallel with perimeter barriers from sister brands. Managers handling that kind of mixed estate will recognise the credential compatibility challenge: the same card may need to work at both the pedestrian intercom and the vehicle gate. Understanding the underlying format is therefore not an academic exercise — it determines whether a replacement card will work across the whole installation.

The TST01 RF/64 Format — and Why It Is Not EM4100

Standard EM4100 — the workhorse of 125 kHz low-frequency proximity — encodes a 40-bit payload (eight bits of version/facility data plus a 32-bit ID) using Manchester encoding at a 64-clock-cycle-per-bit rate derived from the carrier. RF/64 is superficially similar: it operates at 125 kHz, uses ASK (amplitude shift keying) modulation, and encodes in Manchester. The difference lies in the precise bit-clock ratio and framing structure. RF/64 chips use a slightly different preamble sequence and bit-period timing that causes most EM4100-targeting reader ICs to either misread the data or return no read at all.

The CAME TST01 carries a 32-bit unique identifier programmed at wafer level and locked against subsequent write operations. That read-only characteristic is not a security measure in the cryptographic sense — it simply means the chip has no reprogrammable EEPROM. The ID is fixed, permanent, and cannot be altered in the field. For the access controller, this means enrollment is a one-time bind of physical credential to system record; for the credential supplier, it means each card must be produced with the correct ID burned in during manufacture rather than written post-production with a field programmer.

Consulting our proximity card frequencies and standards glossary gives a broader map of how RF/64 sits within the EM-Marin family alongside variants like EM4450 and FDX-A. The short version: EM-Marin-family chips share a physical heritage but diverge in their communication protocol layers, and those differences are significant enough that tool compatibility cannot be assumed across the family.

The TST01 format occupies a niche that only a small number of specialist suppliers can address. Most mainstream credential distributors stock only the high-volume LF formats — EM4100, HID H10301, and a few MIFARE UID variants — and have no supply chain for RF/64-class inlay stock. That installed-reader lock-in is the practical reason facilities managers find TST01 replacements so difficult to source through ordinary channels, and why working with a supplier that holds RF/64 inlay stock is the only path to a compatible credential without replacing the reader hardware.

Why Standard Read-Write Tools Fail on RF/64

Most handheld read-write devices on the market are tuned to recognise a specific set of popular protocols: EM4100, HID H10301 26-bit, and a handful of MIFARE UID patterns. They apply a fixed decode algorithm when a card enters the field. When a TST01 is presented, the reader IC detects carrier modulation and begins decoding — but the RF/64 bit-clock and preamble do not match the EM4100 template. The device either reports a read error, returns a garbled ID, or misidentifies the card as a different format entirely.

Even when an ordinary read-write tool appears to record a value from a TST01, writing that value to a standard T5577 blank rarely produces a working credential. T5577 chips can be configured to emulate several protocols, but the configuration options do not include RF/64 framing. The result is a blank that broadcasts a signal the CAME controller cannot interpret. This is a fundamental incompatibility at the protocol layer, not a matter of tuning or configuration — there is no documented universal T5577 mapping for RF/64. Producing a working TST01 replacement therefore requires a blank built on an RF/64-class read IC, not a generic write-once LF blank.

This gap is exactly why TST01 sits in a high-difficulty format tier. Facilities managers who have tried kiosk copying services or bought generic EM4100 blanks online will already know the result. For those still in the diagnostic phase, our card format identification guide covers how to confirm which protocol a credential is actually using before ordering replacements. It also explains why two cards that look identical and both read at 125 kHz can be entirely incompatible at the protocol level.

A further complication is that CAME has used more than one proximity format across its product history. Cards from different CAME product generations may look visually similar but carry entirely different protocol signatures. Confirming the exact format before ordering — not assuming all CAME cards are TST01 — prevents the wasted cost of receiving a production batch that does not match the installed readers. Our format verification step, which takes place before any production begins, resolves this uncertainty.

Producing a Compatible CAME TST01 Card

A reliable replacement for a TST01 installation starts with sourcing inlay stock built on an RF/64-class read IC — not a T5577, not a generic EM4100 rewritable blank, but a chip whose silicon is designed to speak the RF/64 protocol natively. The 32-bit ID from the original credential must be read accurately before the original card is lost or damaged; once it is, new cards can be manufactured with that ID burned in at production. Multiple cards carrying the same ID are all valid credentials on a system where the ID is the access token, which is the standard operating model for CAME controllers.

Our came tst01 card compatible offering covers exactly this workflow. Customers send us a working original — or in the case of an enrolled-card-only situation, the precise 32-bit decimal or hexadecimal ID from the system administrator's enrollment log — and we produce cards on matched inlay stock. Standard card format is ISO CR-80 (standard credit card dimensions, 0.76 mm), with key fob formats available on request for installations where the fob form factor is preferred.

Gate and barrier installations that use CAME alongside other European automation brands — FAAC, BFT, Nice, Hörmann — sometimes run more than one credential format across the same estate. Our gate transponder card compatible range covers the broader European gate credential landscape. For gate and HOA fob replacements across mixed-brand estates, confirming the specific format on each reader before ordering is the step that prevents wasted cost. Our format verification process handles that confirmation before production begins.

Managers handling multi-tenant buildings where residents need individual credentials will find the per-card identification workflow practical: each resident's existing card ID is logged, and replacement or additional cards are produced to that exact specification. There is no requirement to re-enroll at the controller, and no interruption to access for other residents while new cards are manufactured. For broader context on the supply relationship between compatible credentials and the OEM-issued originals, our compatible vs genuine access cards buyer's guide explains the distinction and its practical implications for facilities procurement.

Ordering: Send a Sample for Format Verification

Because RF/64 sits outside the common LF protocol set, we require a working original card or a confirmed system-side ID record before producing any batch. This protects both parties: it ensures the ICs we select are matched to the actual protocol in your installation, and it prevents the common scenario where a card that looks like a TST01 is actually a different CAME credential variant. CAME has used more than one proximity format across its product history, and visual inspection alone is not a reliable format indicator.

For straightforward single-site orders — a property manager needing five replacement cards for a residential gate — the sample-and-return workflow is fast. We read the original, confirm the format and ID, produce the cards, and return the original with the new cards in the same shipment. For larger multi-site procurement, we can work from system enrollment logs if the administrator can export the enrolled 32-bit IDs directly, removing the need to ship physical cards for each site.

Facilities teams managing European-specification gate and intercom estates that also include 125 kHz LF proximity credentials from other manufacturers should note that format diversity is the norm across this segment. Each brand may use a different LF protocol, and a single estate can easily run two or three distinct formats simultaneously. Our apartment and multifamily building access credential supply service is designed around exactly this complexity, covering format identification, compatible production, and multi-site batch fulfillment from a single point of contact. To discuss a specific installation, contact our team with the credential type and quantity.

Managers sourcing across European gate brands may also find our gate access proximity card compatible range useful, particularly for mixed estates where BFT or FAAC barriers share the same access list as CAME equipment. In all cases, the format verification step ensures production begins only when the target protocol is confirmed.

Security ID Systems is an independent manufacturer and supplier of compatible access-control credentials and is not affiliated with, authorized by, or endorsed by CAME S.p.A. or BPT.

CAME TST01 (RF/64) vs Standard EM4100 — Protocol Comparison

ParameterCAME TST01 (RF/64)Standard EM4100Notes
Carrier frequency125 kHz125 kHzBoth LF; coil geometry similar
ModulationASK ManchesterASK ManchesterSame modulation type
Bit-clock ratioRF/64 (variant)RF/64 standardTiming differences cause misread on cross-protocol ICs
Preamble structureRF/64 framingEM4100 9-bit headerIncompatible decode templates
ID payload32 bits, read-only40 bits (8 + 32)TST01 omits version/facility byte
Field reprogrammabilityNone (factory-locked)None (ROM chip) / T5577 emulationTST01 original is non-writable; T5577 emulation of RF/64 is not universally supported
Compatible IC for replacementRF/64-class read ICT5577 or EM4100 ROMDo not substitute T5577 for RF/64 blanks

Frequently asked questions

What format is a CAME TST01 card?

The CAME TST01 uses RF/64 ASK Manchester encoding — a variant in the EM-Marin family that operates at 125 kHz but uses a different bit-clock ratio and preamble structure from standard EM4100. The card carries a factory-programmed 32-bit read-only ID and cannot be reprogrammed in the field. This protocol distinction is why standard read-write tools and T5577 blanks do not reliably reproduce TST01 credentials.

Is BPT the same as CAME?

BPT (Building Products and Technologies) was a brand within the CAME group, focused on video door entry and intercom panels. For proximity credential purposes, BPT and CAME installations use the same TST01 format, so a card produced for a CAME gate controller and one issued for a BPT intercom panel are interchangeable credentials at the protocol level.

Why will my TST01 card not copy on a standard read-write device?

Standard handheld read-write devices are tuned to decode EM4100 and a small number of related protocols. RF/64 uses a different preamble and bit-timing structure that the EM4100 decode algorithm cannot parse correctly, so the device either returns an error or records garbled data. Writing that data to a T5577 blank produces a credential the CAME controller cannot read, because T5577 firmware does not include a native RF/64 emulation mode.

What is RF/64 ASK Manchester?

RF/64 is a 125 kHz proximity protocol in the EM-Marin family that uses amplitude shift keying (ASK) with Manchester line encoding at a 64-carrier-cycle bit period. It shares the carrier frequency and modulation class with EM4100 but differs in its framing and bit-clock parameters. Those differences are significant enough that reader ICs designed for EM4100 will not reliably decode RF/64 data.

Can a CAME TST01 card be replaced?

Yes — a compatible CAME TST01 card can be produced on RF/64-class inlay stock with the original 32-bit ID burned in at manufacture. The replacement credential works on the existing CAME controller without any system re-enrollment, because the controller recognises the ID, not the physical card. The original card or a confirmed system-side ID record is required before production.

Do I need to re-program the CAME controller to use a compatible TST01 card?

No re-enrollment is required, provided the replacement card carries the same 32-bit ID as the original. CAME access controllers match credential IDs against their enrolled list; any card presenting the correct ID — regardless of which supplier produced it — will be granted the access level assigned to that ID in the system.

Where can I get compatible CAME TST01 cards if my installer no longer supplies them?

Security ID Systems produces compatible CAME TST01 cards on matched RF/64-class inlay stock. The process requires a working original card or the 32-bit ID from the system enrollment log. Standard format is ISO CR-80 card; key fob format is available on request. Contact our team with your credential details and required quantity to begin the format verification step.

Are all CAME proximity cards the same format?

No. CAME has used more than one proximity format across its product history. TST01 is one specific format using RF/64 encoding, but other CAME cards may use different protocols. Visual inspection alone is not a reliable way to confirm the format — our format verification step identifies the exact protocol before any production batch is started, ensuring the correct inlay stock is used.

Request a quote

Can't find your format? Email the specialists.

Send the part number printed on your card or a photo of the reader. We confirm compatibility before you order — and we cover the specialist formats nobody else lists.