50 likes | 66 Views
DRAFT. Leica 3D Disto Measures – Projects – Records. Potential Software Architecture A - E. D) HMI 1: End-user application done by Leica. E) HMI 2..n: End-user application done by 3 rd party developer. C) Public API layer: API for 3 rd party providing access to both core functions.
E N D
DRAFT Leica 3D Disto Measures – Projects – Records
Potential Software Architecture A - E D) HMI 1: End-user application done by Leica E) HMI 2..n: End-user application done by 3rd party developer C) Public API layer: API for 3rd party providing access to both core functions Basic SW Layer B) 3D Disto Library: direct Interface to 3D Disto A) CORE Vanilla, Area etc.: Graebert CAD engine, produces DWG or IFC files
A) CORE • Graebert CAD engine, produces DWG or IFC files • ‘CORE’ (“Vanilla”) runs under OS Microsoft (desktop + mobile) • Ares will work on a MAC • Android (still under construction, target: autumn 2012)
B) 3D Disto Library • Direct Interface to Leica 3D Disto • Has to include access to a basic viewfinder functionality to allow usage of camera and system steering • Has to include at least the GSI functions of today (not necessarily in the same format, might be also in a binary style), maybe more • Base: The “3D Disto Library” in C# runs under .NET / Mono (linux)Can potentially being ported under Monodroid.Mac ? (open decision)
Overview, Potential Results Running under Win (7, 8, RT) + Android Leica HMICAD inside Sitemaster(or 3rd party)Software3D Disto inside C) “Glueing” things together A) Graebert Core (e.g. Vanilla) CAD: SketchData Exchange (DWG, IFC) B) 3D Disto Library 3D Disto viewing and steering Scan engineMath