Using cli cmd does not generate PDFs
Hello, we are producing among other products O3 and O4 trailers. I need some information from experts in the use of VectoCMD. We are now about to implement VECTO in our homologation/documentation environment. We tested the manually started VECTO calculation and realized that the manually and the directory watched started way doesn’t really work for us because we have to produce more than 150 VECTO calculations per day.
We thought about a solution using VECTO as a background job which we would directly start as one job for one trailer so that we are able to calculate several trailers parallel e.g. on one or more server.
We started VECTOCMD via a batch file (and also manually) by using additional parameters.
We tested the vectocmd.exe via a batchfile with the following command:
T:\Projekte\2022_08_31-VECTOTrailer-0.9.0.2799\vectocmd.exe T:\Projekte\Beispiel_20230301\TEST_F8123456.xml
The TEST_F8123456
contained already the Tyre-XML-files!
vectocmd created the following files
TEST_F8123456.RSLT_MANUFACTURER.xml
TEST_F8123456.RSLT_CUSTOPMER.xml
but not the pdf-files.
It worked, but now we have a few questions using the vectocmd this way.
- Is there a detailed operating manual existing for the vectocmd program?
- it took at least 120 seconds to create the output files. This is quite long! Is there a way accelerate the run?
- is there a start ini-file existing which controls the output of the pdf-files, source- and target path? What's its name and where do we have to place it?
In a second step we also thought about the possibility to automate the hashing tool. Did one ever think about a way to automate the hashing-tool? We don’t really know if this would be necessary for us but it would be interesting to know if someone thought about a solution.
I really would appreciate if we could discuss this issues to find a way to start VECTO automatically and parallel and to talk about other aspects and experiences of the VECTO-automation.
Regards Franz