Documentation

Start with the safety model.

A short public guide to what SIMCAT does, what it does not do, and how to keep a lab session reversible.

Quick startSafety modelFAQ

Quick start

  1. Start the SIMCAT build from its own directory; do not overwrite a running install.
  2. Open the device list and select the reader you mean. No selection means no device I/O.
  3. Read the profile inventory. Treat discovery as a hint, not a connection.
  4. If you need to switch, enable the write gate explicitly and follow the confirmation flow.
  5. Read back the state and save the evidence. If anything is uncertain, stop.

Safety model

Read-only default. The app does not touch a device until you select a reader. The write gate is off by default.

One write surface. Profile enable/disable only. No delete, no download, no notification processing by default. The flow is stop → re-read → enable → re-read.

No silent fallback. If a selected reader disappears or a transport fails, the app reports it. It does not quietly switch to another path.

No auto-dial. WiFi Calling registration and dialing are separate. A lab downlink is not a two-way voice claim.

Secrets stay outside. Private keys, activation codes and raw authentication material belong in a restricted vault, not in the app directory or a public release.

Android notes

Current builds are debug-signed lab APKs. Use adb install -r -t and preserve app data. Do not clear app data or uninstall a working build without a backup. USB OTG, OMAPI and BLE behavior depends on the phone, reader and card.

Release notes

See Downloads / Release notes for the current UI11 summary and known open issues.

FAQ

Does SIMCAT need a cloud account?

No for local inventory. The current desktop service is loopback-only and does not require an account.

Can it fix my carrier’s WiFi Calling?

No. It is a lab tool. It can help you observe and test, but it does not guarantee a carrier-grade fix.

Can I run it on iOS or macOS?

Not yet. Both are reserved workspaces with a read-only direction. See the platform pages.

Where are the private keys?

Not here. Keys are kept in a separate restricted vault and are never part of the public site or normal release package.