Individual path for Q-DAS file(s)

[[No...]]

Does anybody know how the individual path settings for Q-DAS files under Resources -> Name for output files go together with the output path in QDASCONV.CON?

Does one override the other? If so, which one has priority? And if the individual path is in effect, which type of output file(s) (DFD, DFX, DFQ) is written? This setting looks a bit contradictory to me. Has anyone already used it an can enlighten me?

I'm looking for a way to have a Q-DAS file of ALL measured chracteristics written to a seperate path whenever needed, but only temporarily. I don't want to change my usual Q-DAS output settings in QDASCOV.CON. Is that possible somehow?

Edited Thursday at 02:06 PM

[[Ma...]]

As i tested - that Name for output files is only for path - file name is default as program name.

Perhaps QDASCONV can solve file name, but i have a workaround with BATCH file to do my things.

For us we use DFQ - it's all in one file - DFD and DFX should be separate files i think

Edited Thursday at 04:04 PM

[[Sv...]]

These are all settings in qdasconv.con, where you specify whether it's dfq, dfd+dfx. As Martin says, everything is contained in dfq, and dfd and dfx are divided into attributes and results. The path is also set there and is valid. If you want to do it temporarily, I would make a copy of the file, change it, and then restore the original later.

[[No...]]

Maybe I need to describe in more detail what I intend to do.

Up until now I have two destinations Calypso results are fed to: One is a QS-Stat system with automatic upload service to a QDAS database (this is for our serial production), the other one is a CAQ system where we do our first sample inspections. While the CAQ needs all the characteristics, the QDAS system only takes a narrowed down selection of results. 

Today the data for the CAQ system is read from the compact protocol and the protocols are written to individual paths. The QDAS data  on the other hand is written the usual way (with settings in QDASCONV.CON) to DFD/DFX files, which are then transferred to the database by the QDAS upload service and deleted afterwards.

Now, in the near future our CAQ system will change and the new system can no longer read results from the compact protocol, but needs a QDAS file. So now I'm looking for a way to generate a seperate QDAS file in a different location with ALL charcteristics, and WITHOUT disturbing the normal data transfer to the QDAS system in any way.

I can not just grab the files written by the normal QDAS output: They do not contain all the data needed and are continuously fetched and then deleted by the upload service. Meddling with this workflow would severely disturb our production process.

Edited 4 hours ago

[[Sv...]]

I don't think that will work. We had a specialist training course for QDAS from Zeiss. It was conducted by Robert Disser, an absolute top expert in PiWeb and QDAS; he might be able to help you.