03-05-2013 08:20 AM
Hi ThiCop
Yes, I have some more info. All the info I received is under the map ''received from testo''. The code is in source/main 3. In the files I received from Testo there is an HTML document that is the Manuel from the dll files.
The excel we did not use. We just used it as a guideline to assist with the HTML file to see the arguments and the sequence Testo programmed it in VBA.
In attachment is the latest code.
So do you think that I maybe have to take the testo readout out of the timed loop? Or in the simple vi the while loop?
Thank for the help. Together we will hopefully find the solution.
Greets
Vincent
03-05-2013 10:00 AM
Do you mean the .chm document instead of .html?
Which is currently your "main VI".
The functions might require that a user actively/periodically calls/runs one of them.
I saw something like this being done through the timer in the excel macro.
However, seeing that I did not develop the dll, I am not a 100% sure that this is how it was meant to be used.
This should be mentioned somewhere in the help.
03-05-2013 10:14 PM
Yes that is the one. I can not find any info about a timer in the help.
I just see info about all the separate functions.
The main function in mainbis3
I see you are from Belgium. Myself I am from Belgium too so if you like I visit you with the Testo if that can be of any help.
Much thanks!!!
Greets
Vincent
03-06-2013 03:25 AM
Hello Vincent,
Visiting with the Testo will not be a solution.
In this main code I saw a few things that should for sure be changed:
- If an error condition appears in your code, then you do not seem to be "handling" it.
Example: Your IO loop can keep on running even if you have errors in one of your DLL's.
- Your block diagram is extremely big.
Always try to compact you screen to one "normal screen".
If this is not possible, then make it only scrollable in one direction (top-bottom or left-right).
This is for sure possible with the code you currently have available.
Regarding the timer:
I saw this in the macro.
Was everything that was done in the macro clear to you?
Have you asked testo how you should do the communication with the device?
They are the manufacturers of the device, so they should be able to provide you with more information than I currently can. (I only have the info that you provide to me)
03-08-2013 07:46 AM
Hi ThiCop
I am working on the code to make it smaller. I am creating all functions to subvi's so it will fit a screen. This is indeed something I still have to do. My background is not really IT so I am already happy that it is working and that I understand it. So to answer on you question, no I don't know completely what is happening in the macro. I have just read the description of every function in the help file, than checked the macro for the arguments and try to get some communication. I can read in this help that we first have to establish the communication with the testo open and then we go to the other functions. We did not succeed in the start and stop pump so we left these functions out.
Like I sad my background is electromechanical and not really IT but I am willing to learn and try. Hopefully we get there.
I did not receive more info from Testo than this. But I can always sent theme an email.
Thanks!!!!!!!
Vincent
03-08-2013 08:13 AM
Hello Vincent,
What I would like you to check with them is the following:
- Do you continuously have to send a command to keep the USB-communication going?
If yes, then
a) Which commands can serve this purpose?
b) How frequently do these commands have to performed/sent?
03-10-2013 11:31 PM
Hi ThiCop
I have sent the questions to Testo and received an answer straightaway.
There is no timeout or special command required.
They mention that we can not read in the values quicker that once a second. I have tried to rum the main VI with the timed loop programmed so that it will update only every 2 seconds but the problem still exists than.
I have paste the email in the word document attached.
Thanks for the effort!!!
Greets
Vincent
03-11-2013 05:23 AM
Hello Vincent,
Thank you for the fast reply!
Can you share your latest code (probably you already made some changes to the previous code) with the latest errors?
Then I can adapt it or show you where to adapt it for further troubleshooting.
03-11-2013 08:27 AM
Hi ThiCop
Once again you don't know how much I appreciate it that you help me thinking in the good direction.
I started making some changes in order to make the code fit in one screen. This is not finished. What did you mean with the comment that I shout connect the error's on the dll's? Do you mean that I have to connect the error box and put this in my front panel so I can see what error is showing?
I did not do that yet.
I removed also the DAQ modules. This is because I am abroad for the moment and I can not test the complete program on my laptop. When I come home and I install the new code on the PC that I use for this program I just put back the DAQ modules.
The name of the new program is mainbis3b
Greets
Vincent
03-13-2013 07:49 AM
Hello Vincent,
Can it be that the Testo Toolbox (that contains the DLL) is missing from the zip-files?
I'm currently at another pc (work pc instead of home pc), then the one I was before and I seem to have downloaded the wrong dll.
Can you add a post that summarizes which things I should absolutely install on my pc to get it to work?
Also I would advise you to use a LabVIEW project to organise all your files.
This will make the overview of the project as a whole way easier/cleaner.