gieschef/eqx

root repository for EQuipment eXchange project

eqx's Issues

defining EQX logo

... as an Idea ...

Attachement needs to be assigned to single calibration

In case of sending more than one calibration certificate as an attachment per sensor axis it is not defined for which calibration entry from the history the single certificate is assigned to. So no automatic linking to calibration history is possible for the certificates.

To make this possible the element Definition for the attachment sequence should be moved to the EqxCalHistoryEntry type, then it is still backward compatible because sensoraxis is extending EQXCalhistoryentry, but we gain the benefit of clear definition where the Attachement belongs to.

additional category 'SensorAssembly' needed

In Taskforcemeeting on 2019-11-13 it was decided to introduce a new category 'SensorAssembly' for more than one sensor packed as an assembly unit.
This could be for example multidimensional measurement unit like IR TRACC or similar Equipment.

New field selfdescriptive for version 1.6 needed

Boolean flag for ‚isSelfdescriptive‘ to mark digital sensors with Extended TEDS information

If this is set to true the recommendation for the DAS is to use operational information from sensor ( TEDS) and not from file.

additional values needed for sensorgroup category

additional categories needed to give a Chance for more detailed description of the Groups.
category to add : TESTBENCH

EQX application as Calibration Record

Hello everyone. I think EQX as a formal calibration record is a great application of the technology but has some additional nuances to consider, so I wrote the following user story to help guide discussion.

As an instrumentation quality manager, I'd like to use EQX to receive calibration information from sensor manufacturer or calibration labs. I'd like to be able to import an eqx file into my sensor database and know that it is a calibration record and not simply equipment being sent from a vendor or customer. I'd also like to have the option to scan a code on the calibration certificate to import the sensor.

With this in mind, can we consider some additional sensor fields to indicate that the record is an authoritative calibration, and a field for the lab accreditation information?

We have had success in encoding EQX files in QR codes, with a single sensor-axis fitting on 25mm square with a normal laser printer and decoded with a cheap android phone. I'd like to discuss standardizing this method and/or adding some code examples to this repo. For instance, in addition to the QR code, should we have standardized text above indicating the sensor SN and cal date, and the word "EQX" as a hint?