Overview
FieldServer is Chipkin’s legacy and specialty gateway platform for protocol-conversion work. It remains relevant where a project depends on older field interfaces, niche industrial protocols, or installed designs that are not yet a fit for QuickServer.
FieldServer and QuickServer both solve protocol-conversion problems, but they are positioned differently. QuickServer is the preferred starting point for new projects. FieldServer remains important when the required device family, utility, or deployment pattern lives in the legacy platform.
FieldServer vs QuickServer
| Aspect | FieldServer | QuickServer |
|---|---|---|
| Platform role | Legacy and specialty protocol coverage | Current-generation platform for new projects |
| Protocol breadth | Broadest coverage, including niche drivers | Focused on common and growing protocol coverage |
| Configuration style | CSV-driven workflow | Web UI plus CSV workflow |
| Typical use | Brownfield retrofits and specialty integrations | New deployments and standardized platform work |
[!TIP] Start with QuickServer for new work. Move to FieldServer when the required protocol or brownfield constraint is not yet covered on QuickServer.
Common Support Tasks
- Discover the gateway on the local subnet.
- Upload configuration revisions.
- Change IP settings.
- Generate diagnostics for support review.
- Update firmware or recover from an unusable build.
Toolbox Workflow
FieldServer Toolbox is the standard discovery and connectivity utility for both FieldServer and QuickServer hardware. It is most useful during initial commissioning, adapter selection checks, and first-line network troubleshooting.
Use FieldServer Toolbox Connectivity Troubleshooting when discovery fails or browser handoff does not work cleanly.