FD1 Client Protocol
 
Library Developer Home FD1 Client Protocol Home Concepts Reading Data Writing Data Protocol Defined Servers Connect & Authenticate Proxies & Tunnels
Webhooks Programming Support Logging Minor Facts State Facts Response Format How To Guides eCommerce Sites Custom Point of Sale Customer Access Bulk Downloads Major APIs / Endpoints All Endpoints Products Sales SalesBuilder Session Sale Capture General Purpose Data Capture Devices Barcode Scanners Eftpos IoT Sensors Power Outlets Printing Scales Security Cameras Purchasing / Supply Side Purchase Orders Invoices Invoice Payments Document Capture Rare APIs / Endpoints SSL Certificates API Key Management Diagnositics Server to Client Messages Overview Resources / Objects Purchase Order Invoice Payable Invoice Payment Product Supplier Location Sale Lines Sale Delivery Details Sales Price Maps Employees Carriers Payments Product Kits Department 1 Customers

FD1 Diagnositic Calls

The endpoints fd1.diag.... are used by Fieldpine internally to analyse and debug running systems. These calls are not available for public use and have additional requirements in order to be activated. Technically speaking, a different driver is selected to the standard FD1 driver when using these functions.

Support User A⤡
Support User B↔Support Server⇔SUT
(System Under Test)
Automated Tools⤢

Fd1.diag is used on the connection between the support server and the SUT. The 3 connections on the left use the related fd1.support protocol. fd1.diag is the technical commands, while fd1.support is the higher level abstractions

The remainder of this page is primarily for Fieldpine use only.

Binary Packet Format

Binary requests are wrapped in a DIAG Gnap packet and replies are returned in a DIAR Gnap packet

Field#DIAG / DIARDescription
110DIAG"rq"
111DIAR"rp"