CirEdge
Login Request a quote
User Guide

Step-by-step setup and operation

This guide covers everything from the moment you unbox the CirEdge to when data starts flowing into your ERP. Each section is self-contained — use the table of contents on the left to jump to any step.

01 Get to know your device

CirEdge is a palm-sized industrial gateway in an aluminum enclosure. It mounts on a DIN rail inside the cabinet. Status LED on top, ports on the sides.

  • Ethernet (RJ45 ×1): Connection to the factory network. Gigabit, optional PoE.
  • USB-A ×2 + USB-C ×1: USB-C — file transfer to legacy machines in MSC mode. USB-A — backup/diagnostics.
  • 40-pin GPIO header: Read signals from legacy machine panel LEDs. 3.3 V tolerant — wire via optocoupler.
  • Power (5–24 V DC): Powered from cabinet supply or PoE.
  • Status LED: Blinking blue → awaiting cloud pairing. Solid blue → connected to cloud. Green → data flowing.

02 Cabinet installation

The device clips onto a standard 35 mm DIN rail inside any cabinet. The machine electrical cabinet is the ideal location — short cables, isolation, stable power.

  1. Pick a suitable empty slot on the DIN rail (about 90 mm).
  2. Place the device on the rail — hook the top edge first, then press down; the spring mechanism clamps.
  3. Connect the Ethernet cable to the machine network (CAT5e/CAT6).
  4. Connect power (use 24 V DC from the cabinet if available, otherwise PoE switch).
Isolate the machine ground from the device ground — use an isolated DC-DC converter if needed. Otherwise electromagnetic noise will cause issues.

03 First boot

On first boot the device gets an IP via DHCP. Find its local IP from your router or by inspecting the device LED, then connect to the web interface.

  1. Open http://<device-ip> in your browser — e.g. http://192.168.1.50
  2. On first boot a setup wizard opens — set the admin password (minimum 6 characters).
  3. After login the left menu sections become active: Files, Transfer, Machines, Cloud, etc.

04 Pair with the cloud

Pairing the device with the portal unlocks remote access, telemetry, notifications and the REST API. Pairing is one-time — a 24-character secure token is generated.

  1. Open the Cloud tab in the device web panel. A 24-character pairing code is generated automatically.
  2. Sign in to the portal (edge.cir.net.tr). Click "Add device" on the dashboard.
  3. Paste the code + give the device a name (e.g. "Shop 3 — Doosan 1").
  4. Pairing completes, the device appears online on your dashboard. The pairing code is now invalid; a permanent token is written to the device.

05 Add machines

A single CirEdge supports multiple machines. For Ethernet-connected machines, add them from the Machines page. There are 3 modes depending on the machine type.

Fanuc FOCAS (TCP)

For Fanuc controllers with FOCAS support. Enter the machine IP and port (default 8193). Select backend "libfwlib32" or "helper" (works on real machines).

Siemens Sinumerik OPC UA

For Sinumerik 840D / 828D controllers. Enter machine IP + port (default 4840) + OPC UA username/password. Backend: "opcua_client".

File transfer only

To send/receive files without live monitoring. Works over FTP/SMB — ideal for older machines.

06 Device discovery (network scan)

If you don't know what's online in a new shop, scan a subnet (e.g. 192.168.0.0/24) from the Discover page and list devices with open S7/Modbus/OPC UA ports.

  1. From the left menu "Discover" → enter subnet (CIDR format).
  2. Pick protocol presets — S7 (102), Modbus (502), OPC UA (4840), HTTP (80, 8080).
  3. From the result table, add the device as a machine in one click or make it a VPN tunnel target.

07 Define telemetry (PLC → Cloud)

To stream a PLC tag or GPIO signal to the portal, define a telemetry collector. Data flows to the portal automatically and is pullable via REST API.

  1. From the left menu "Telemetry" → "Add new collector".
  2. Enter protocol (Siemens S7 / OPC UA / Modbus) + tag name + read interval.
  3. Data lands in the portal Datapoint table within 1 second. To pull via REST API, generate an API token from the account page and query like:
curl -H "Authorization: Bearer cncbr_..." \
  https://edge.cir.net.tr/api/v1/devices/<slug>/datapoints

08 GPIO for legacy machine signals

On legacy machines without a network connection, you can read status info from panel LEDs or dry-contact outputs. Define pins on the GPIO page.

3.3 V max! For 12–24 V machine signals, an optocoupler (PC817, EL357) is mandatory. Direct wiring will burn the device. See the safety section on the GPIO page for details.
  1. Measure the machine LED (+/-) terminals — determine voltage level.
  2. Build the optocoupler circuit: machine LED → 4.7kΩ → optocoupler → device GPIO + GND.
  3. Open the "GPIO" page in the device web panel, enable the service.
  4. "Add pin" → signal name (e.g. "Spindle Active") + physical pin number + active-low + pull-up. Pin state appears in the live table.

09 Access from PC (Windows client)

Use the Windows client to access the factory-floor PLC from PC tools like TIA Portal, Step 7 or RSLogix as if locally connected.

  1. Download the client from the portal: Download client
  2. Account → API tokens → "Generate new token". The token is shown only once — copy it.
  3. Run the client + paste the token. The device list appears; connect to the relevant device. Now you can directly access the machine PLC IP from TIA Portal.
The client runs in the background in the tray. The same token covers multiple devices — pick which device to connect from the tray menu.

10 Troubleshooting

Most common issues and their solutions:

Device LED blinks but doesn't connect to the portal

Make sure the device has internet access — the cabinet firewall must allow outbound 443/tcp (edge.cir.net.tr). The System → Cloud tab in the device web panel shows the last error message.

PC client connects to the device but can't reach the PLC IP

Make sure you added the PLC IP:port to the device's Access targets table. The tunnel only allows whitelisted targets (security).

FOCAS connection error — "DLL not found"

If libfwlib32.so is not installed on the real machine side, run the install-focas-armhf.sh script (SSH into the device). Or select "helper" as backend — uses a 32-bit subprocess approach.

Fanuc doesn't see files in USB MSC mode

Filenames must be normalized to 8.3 format (e.g. POOL_42.NC). The device auto-normalizes but on some legacy Fanuc you need to manually refresh USB (from the Status page).

GPIO pin always reads the same value

Check the pull resistor setting — pull-up should be active for an optocoupler output. The active-low checkbox should be ticked (pin reads LOW while LED is on).

11 Frequently asked questions (FAQ)

Can multiple PCs connect to the same device?

Yes, each PC connects independently with its own API token. Simultaneous access to the same PLC IP is bounded by lock mechanisms in tools like TIA Portal (machine side).

Is anything saved to the cloud while the device is offline?

Telemetry data is buffered locally while the device is offline and sent to the portal when it comes back online. USB MSC mode works offline (device stays plugged into the machine); cloud connectivity is only for configuration and notifications.

Are multiple machines supported?

Yes — N machines from a single device (Ethernet-connected). USB MSC is single-machine only (physical constraint). Each machine is a separate entry with its own snapshot and telemetry collector.

How many GPIO pins are usable?

On the 40-pin header about 28 pins are usable (the rest are Power/GND). With an optocoupler + external PCB you can theoretically use all of them. In practice 8–12 signals is usually enough.

Can I get mobile notifications?

Currently email + REST API are supported. You can forward emails to your phone or set up push notifications via IFTTT/Zapier. A native mobile app is on the roadmap.

If the device fails, is data lost?

No. Telemetry data remains in the portal. The device configuration is also backed up in the portal — get a new device, pair with the same code, and the previous configuration is restored automatically.

Need help?

If you can't find an answer in the guide, reach out to our team. We usually respond the same day.

info@incirbilisim.com incirbilisim.com