Rıza KorkusuzTechnical Support
← Back to Portfolio
Interactive simulator · Schematic view

Troubleshooting Path Simulator

One animated solar site that ties the portfolio together. Pick a fault, watch it break the data chain, then follow the support path in the same order every time: modem, logger, RS-485 and meter, production. Each step shows the check, what the technician sees, the finding, and the guide or tool that covers it.

Ticket triagePing & DNSLocal buffering & backfillRS-485 / ModbusExpected vs actualData cleaning

Independent prototype with synthetic data Sites, tickets and numbers are fictional and match the sample data in Relay Desk and PulseAssist. Generic equipment only: no vendor wiring, terminal maps or real site data.

See the same tickets on a realistic tracker farm: open the Solar Farm Simulator →

Simulator

SiteOak-12 (sample)
Local time12:30
PortalOnline
Logger buffer0 records
Power vs expected— kW

Tip: select any component in the diagram to see what it does.

Why the same order every time

Support walks the chain backwards from the portal. Each stop answers one question, costs nothing but a few minutes at the desk, and rules out everything upstream of it before anyone talks about a truck roll.

  1. Modem / connectivityIs the site talking at all? Last check-in, signal, registration, ping to the modem. If the path is down, nothing downstream can be judged from the portal.
  2. LoggerIs the logger alive, polling and stamping the right time? Is data waiting in its local buffer? A buffered outage becomes a backfill, not a gap.
  3. RS-485 / meterDoes every device answer its poll? Address, serial settings, polarity and termination explain most silent devices. Meter and inverter totals should agree.
  4. ProductionOnly now judge the number: actual vs the stored expected-energy target, weather, per-inverter and per-string comparison. Soiling, shade, an inverter fault or a string down each leave a different pattern.

Everything this simulator pulls together

Each link of the chain points to a page or tool already in the portfolio.

TriageRelay DeskSample ticket queue. NW-1842 “Oak-12 production looks low” uses the same modem → logger → RS-485 → production order. DiagnosticsPulseAssistMonitoring support lab: alarms, check-ins and expected-vs-actual views for synthetic sites. ModemNetworks roadmapIP, ICMP, DNS and TCP: what a failed ping or lookup actually tells you. ModemWindows CMD guideping, nslookup, tracert and w32tm with output you can read at the desk. LoggerEdge node & bufferingWhy local storage turns an outage into an ordered backfill instead of lost telemetry. RS-485Raspberry Pi labsModbus RTU meter reader, outage-proof buffer and uptime monitor, all with synthetic data. HardwareHardware troubleshootingModem, logger, RS-485, meter and inverter fault cards with escalation triggers. ProductionSolar monitoring desk guideScoping the ticket, reading alarms and judging production before dispatch. DataData cleaning pipelineDuplicates, gaps, CT-ratio errors and spikes flagged before data reaches a report. NetworkWireshark & NmapWhen ping is not enough: handshakes, resets and open ports on the wire.

Scope

This is an independent portfolio prototype built with synthetic data. The site, devices, tickets and values are fictional, and the diagram is a generic teaching model, not a schematic of any real plant or product. Remote support checks shown here are desk checks: anything inside an energized enclosure is for qualified field staff following the manufacturer’s documentation and the site’s safety procedures.