Martin,
Thanks for your response - you're serial0 suggestion is a good one. Now if it was only possible for an application's user to specify which port to use for "event" driven input.
Barrie
"Martn Castillejos, Juan Carlos" wrote:
> Hi all,
>
> >From my point of view, including vee.io in the vee file is an upgrade, although it may not work in all cases. This avoid searching vee.io file into the computer for some defined interfaces.
>
> An additional way to use this, it is to select all equipment as serial0 interface in the vee.io included in the vee file itself, that is all as "not live". In this case it is necessary to ask before executing the main part of the program which is the port number for every connected equipment. Or maybe generate a txt (for example interfaces.txt) information file that could be more flexible and readable for the operator. In this file, port numbers can be changed before execute vee and it can be stored always in the same directory than the vee. In that way it is very easy to codify that has to be read it at the same time global variables are declared and other init functions executed.
>
> In both ways (manually by the operator or by and additional file) can be obtained the correct numbers of ports. Supposing they are known, each Direct I/O object needs to be feed (and activated before executed!) with its good value.
>
> Set all equipment in serial0 means "not live" and vee program does not crash at startup.
>
> -----Mensaje original-----
> De: Barrie Walden [mailto:bwalden@whoi.edu]
> Enviado el: mircoles, 10 de julio de 2002 17:46
> CC: Vee Reflector (E-mail)
> Asunto: Re: vrf Vee6 and pointing to the desired vee.io file
>
> I have never figured out how vee.io is supposed to work. Every time I
> try using the standard I/O capabilities, I get into trouble. Mark's
> message and "home" explanation helps but there are still problems. The
> applications I write are intended to run on computers I never see and
> certainly don't get to configure. The operator is expected to plug
> sensors into available serial ports, turn on the application, enter some
> port assignment information and collect data. When I write the code, I
> have no idea what ports are physically present on the target machine and
> I don't know which ones the operator will choose to use. Inevitably,
> when its really important, my application will refuse to load because
> some port used during development is not available on the target.
>
> Vee 6.01 seems to have flexibility in how port allocation and
> configuration can be handled but I haven't come up with the right
> combination. I want my application to load and then provide the
> operator with the ability to designate and configure the serial ports he
> has chosen for use with the available sensors. How is this supposed to
> be done?
>
> Barrie
> whoi
---------------------------------------------------------------------
This is the "vrf" maillist, managed by Majordomo. To send messages to
this maillist, just email to "vrf@lvld.agilent.com". Subscriptions and
unsubscriptions are done through the address "vrf-request@lvld.agilent.com".
If you need details, just send a message containing the text "help"
to "vrf-request@lvld.agilent.com".
---------------------------------------------------------------------
Thanks for your response - you're serial0 suggestion is a good one. Now if it was only possible for an application's user to specify which port to use for "event" driven input.
Barrie
"Martn Castillejos, Juan Carlos" wrote:
> Hi all,
>
> >From my point of view, including vee.io in the vee file is an upgrade, although it may not work in all cases. This avoid searching vee.io file into the computer for some defined interfaces.
>
> An additional way to use this, it is to select all equipment as serial0 interface in the vee.io included in the vee file itself, that is all as "not live". In this case it is necessary to ask before executing the main part of the program which is the port number for every connected equipment. Or maybe generate a txt (for example interfaces.txt) information file that could be more flexible and readable for the operator. In this file, port numbers can be changed before execute vee and it can be stored always in the same directory than the vee. In that way it is very easy to codify that has to be read it at the same time global variables are declared and other init functions executed.
>
> In both ways (manually by the operator or by and additional file) can be obtained the correct numbers of ports. Supposing they are known, each Direct I/O object needs to be feed (and activated before executed!) with its good value.
>
> Set all equipment in serial0 means "not live" and vee program does not crash at startup.
>
> -----Mensaje original-----
> De: Barrie Walden [mailto:bwalden@whoi.edu]
> Enviado el: mircoles, 10 de julio de 2002 17:46
> CC: Vee Reflector (E-mail)
> Asunto: Re: vrf Vee6 and pointing to the desired vee.io file
>
> I have never figured out how vee.io is supposed to work. Every time I
> try using the standard I/O capabilities, I get into trouble. Mark's
> message and "home" explanation helps but there are still problems. The
> applications I write are intended to run on computers I never see and
> certainly don't get to configure. The operator is expected to plug
> sensors into available serial ports, turn on the application, enter some
> port assignment information and collect data. When I write the code, I
> have no idea what ports are physically present on the target machine and
> I don't know which ones the operator will choose to use. Inevitably,
> when its really important, my application will refuse to load because
> some port used during development is not available on the target.
>
> Vee 6.01 seems to have flexibility in how port allocation and
> configuration can be handled but I haven't come up with the right
> combination. I want my application to load and then provide the
> operator with the ability to designate and configure the serial ports he
> has chosen for use with the available sensors. How is this supposed to
> be done?
>
> Barrie
> whoi
---------------------------------------------------------------------
This is the "vrf" maillist, managed by Majordomo. To send messages to
this maillist, just email to "vrf@lvld.agilent.com". Subscriptions and
unsubscriptions are done through the address "vrf-request@lvld.agilent.com".
If you need details, just send a message containing the text "help"
to "vrf-request@lvld.agilent.com".
---------------------------------------------------------------------
about "driver for this device not found, add it now?" I jump through it's
hoops and the program is fine after I save the IO settings. I'm running
Win2k, XP, NT, Win95 and 98.
-----Original Message-----
From: Wills, Mark [mailto:MWills@tycoelectronics.com]
Sent: Wednesday, July 10, 2002 7:55 AM
To: Vee Reflector (E-mail)
Subject: vrf Vee6 and pointing to the desired vee.io file
Hi All,
This seems like a bit of a rant but bear with me and hopefully it will help
others to avoid the time wasting that I endured thanks to another VEE
"enhancement" !!
After putting it off for some time we have finally upgraded to Agilent vee6
Pro and immediately the fun started.
Having converted a test program in vee5 to vee6 and copied the vee.io file
to C:program files AgilentVEE Pro 6.0 directory , I expected to be able
to simply fire up vee6 and run it, however, the vee.io file was not found.
I soon discovered that vee 6 was in fact looking for this file under
C:Documents and Settings"logged on username"Local SettingsApplication
DataAgilent (we are running WIN 2000) I read the VEE help manuals and to my
surprise this is correct and would mean that every logged on user would have
to have the vee.io file copied into their respective document and settings
filepath, unlike previous versions of vee where the vee.io file was held in
the vee installation directory. This seems ludicrous as if one assumed that
any logged on user should be using the same vee.io file and a change to this
file occurred it would means copying it to each users filepath, and if one
was missed that user would be running the wrong vee.io file.
There are from what I can see two ways around this problem.
1. Use a shortcut to the program in question using the -veeio command to
specify the path of the vee.io file, eg
Target: "C:Program FilesAgilentVEE Pro RunTime 6.0veerun.exe" -veeio
"c:My Veeio Filevee.io""c:MyVeeProgram.vee"
Start in: "C:Program FilesAgilentVEE Pro RunTime 6.0"
This could be a problem should the shortcut inadvertently become deleted as
if there was no support staff around a test operative wouldn't necessarily
know what to do to fix the problem.
2. Add a windows system variable HOME pointing to the desired vee.io file
Further reading in the Vee help manual mentions the ability to set a
variable HOME specifying the filepath of the vee.io file and which once set
means that any logged on user or for any vee file executed directly from
explorer the same vee.io file is used, just like in the good old days, no
special shortcut set-up is necessary. The Vee help manual unfortunately
omits the essential pieces of information regarding the HOME variable, how
to set it up, where to set it up and what type of variable is it?
I assumed that this must be a windows variable but still I wasn't sure how
to set it and after speaking to our IT department discovered the answer,
although there are different methods for setting it dependant on the
operating system in use.
For WIN 95/98 :-
a) Open a DOS window and type "set /?" this shows the format of system
variables
b) Type "set" this shows all of the current system variables that are set
c) Type "set HOME=C:Program FilesAgilentVEE Pro 6.0" where HONE is the
system global followed by the vee.io filepath
d) Restart the PC for the change to take effect
For WIN 2000
a) Right-click My Computer > Properties > Advanced > Environment Variables
b) Add HOME as a system variable with the filepath to the desired vee.io
file
SPECIAL POINTS
1) I checked with our IT department first to see whether or not adding this
global would in any way impact on windows or any other programs installed
and as this global does not previously exist until you add it means that it
wasn't previously used and therefore shouldn't be a problem.
2) I have vee5 and vee6 installed on my machine and it would appear that
having set this HOME global to point to the vee.io file in the C:Program
FilesAgilentVEE Pro 6.0 directory, vee5 also now looks for it there and
not in its own installation directory C:Program FilesHewlett-PackardVEE
5.0.
The fact that vee6 can save the vee.io file in the compiled version of the
software is a good thing, if a third party is to be sent some test software
there is no need to also send out the vee.io file which previously was the
case and mean that if you hadn't been sent the vee.io file then you either
couldn't run the software or you had to configure your IO config by hand
(could be time consuming).
As far as being able to allow different logged users to use different vee.io
files I could only see that this would be useful if the test stand in
question was multi-purpose and then as each user logged on they would use
their respective instrument settings. On the whole from my experience, most
test stands are configured for a single purpose and remain static and
therefore would always use the same vee.io file irrespective of who is
logged on to the stand at the time. The ability to allow the former would
surely be the exception as opposed to the rule.
What are other peoples views on this and have the same problems mentioned
here been encountered by anyone else?
Regards,
Mark Wills
Principal ATE Engineer
Wireless Automotive System Group
> * E-mail: mwills@tycoelectronics.com
> * Phone: +44 (0)1908 574209 (direct line)
> * Phone: +44 (0)1908 574200 (switchboard)
> * Fax: +44 (0)1908 574300 (fax)
>
Tyco Electronics UK Limited M/A-COM Division
Featherstone Road
Wolverton Mill
Milton Keynes
MK12 5EW
Creating chaos out of order !
---------------------------------------------------------------------
This is the "vrf" maillist, managed by Majordomo. To send messages to
this maillist, just email to "vrf@lvld.agilent.com". Subscriptions and
unsubscriptions are done through the address "vrf-request@lvld.agilent.com".
If you need details, just send a message containing the text "help"
to "vrf-request@lvld.agilent.com".
---------------------------------------------------------------------
---------------------------------------------------------------------
This is the "vrf" maillist, managed by Majordomo. To send messages to
this maillist, just email to "vrf@lvld.agilent.com". Subscriptions and
unsubscriptions are done through the address "vrf-request@lvld.agilent.com".
If you need details, just send a message containing the text "help"
to "vrf-request@lvld.agilent.com".
---------------------------------------------------------------------