> Do you have any ideas for dealing
> with driver failure?
Seeing as how you're using MS's serial driver, nope. There *is* some kind of goofy interaction between VEE & the serial driver. Otherwise we wouldn't see the kinds of problems we do with RS-232 (IOW, it's not hard to cause the driver to get messed up - constant redefinition of buffer size will do it). These are probably localized in IO Libs. I think I do remember that some of these issues have been cleaned up lately. Specifically, the phony 811 error - I think.
There are at least two other options (besides rebooting): You can use the MS Comm control to do IO instead of Direct IO transactions. I use the IO control fairly regularly and I've never experienced any problems with it. There are also a variety of other serial controls you can use as well though I've never had the need for anything more than that provided by MS.
Another option, though not very desirable in VEE, is to use the serial API directly. It's not pretty, but it's doable. I've never experienced any problems with this method either, though it is much more difficult than using the control (no matter what language you're using).
There may be other options (like using a replacement serial driver for instance), but anything along that line may require abandoning Direct IO transactions too.
When you use Direct IO, you're going: VEE->IO Libs->API->driver->API->IO Libs->VEE. There are even some layers within this general structure. I usually say the best bet to fix problems in this case is to start peeling away some layers.
-SHAWN-
> with driver failure?
Seeing as how you're using MS's serial driver, nope. There *is* some kind of goofy interaction between VEE & the serial driver. Otherwise we wouldn't see the kinds of problems we do with RS-232 (IOW, it's not hard to cause the driver to get messed up - constant redefinition of buffer size will do it). These are probably localized in IO Libs. I think I do remember that some of these issues have been cleaned up lately. Specifically, the phony 811 error - I think.
There are at least two other options (besides rebooting): You can use the MS Comm control to do IO instead of Direct IO transactions. I use the IO control fairly regularly and I've never experienced any problems with it. There are also a variety of other serial controls you can use as well though I've never had the need for anything more than that provided by MS.
Another option, though not very desirable in VEE, is to use the serial API directly. It's not pretty, but it's doable. I've never experienced any problems with this method either, though it is much more difficult than using the control (no matter what language you're using).
There may be other options (like using a replacement serial driver for instance), but anything along that line may require abandoning Direct IO transactions too.
When you use Direct IO, you're going: VEE->IO Libs->API->driver->API->IO Libs->VEE. There are even some layers within this general structure. I usually say the best bet to fix problems in this case is to start peeling away some layers.
-SHAWN-
Sean, one question comes to mind: What are you using to create the
RS485 data? The IOLIBs for VEE do create RS232 data, and they do of
course create GPIB/HPIB data, but that's all.
--
Gregg C Levine gregg.drwho8@gmail.com
"This signature was once found posting rude
messages in English in the Moscow subway."
You might also want to supply us with more information to add to this issue.
On 2/20/06, Sean Watson <sean.watson@cmp.cpii.com> wrote:
> Hi Everyone,
>
> I have a VEE Pro program in which I query a moderately large number(10-20)
> of different units over an RS-485 communications line. Between these units
> there are two or three different I/O objects with varied settings (8-bit
> word, no parity; 7-bit word, no parity and 7-bit word, even parity). To send
> to these units, I create an array of all the units to send to and use a loop
> to cycle through all of them repeatedly.
>
> What I am finding is that this will work for some amount of time, anywhere
> between 12 and 48 hours but will inevitably cause VEE to freeze at a Direct
> I/O object. After this freeze, VEE must be totally shut down and will lock
> up in the same way any other time a Direct I/O object is used until the
> computer has been restarted.
>
> I was wondering if anyone has encountered something similar in the past or
> have any ideas as to why this keeps happening. Any help is greatly
> appreciated.
> ---
> You are currently subscribed to vrf as: gregg.drwho8@gmail.com
> To subscribe send a blank email request to "join-vrf@lists.it.agilent.com".
> To unsubscribe send a blank email to
> "leave-vrf@it.lists.it.agilent.com".
> To send messages to this mailing list, email "vrf@agilent.com".
> If you need help with the mailing list send a message to
> "owner-vrf@it.lists.it.agilent.com".
> Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe send a blank email request to "join-vrf@lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
Sean, one question comes to mind: What are you using to create the
RS485 data? The IOLIBs for VEE do create RS232 data, and they do of
course create GPIB/HPIB data, but that's all.
--
Gregg C Levine gregg.drwho8@gmail.com
"This signature was once found posting rude
messages in English in the Moscow subway."
You might also want to supply us with more information to add to this issue.
On 2/20/06, Sean Watson <sean.watson@cmp.cpii.com> wrote:
> Hi Everyone,
>
> I have a VEE Pro program in which I query a moderately large number(10-20)
> of different units over an RS-485 communications line. Between these units
> there are two or three different I/O objects with varied settings (8-bit
> word, no parity; 7-bit word, no parity and 7-bit word, even parity). To send
> to these units, I create an array of all the units to send to and use a loop
> to cycle through all of them repeatedly.
>
> What I am finding is that this will work for some amount of time, anywhere
> between 12 and 48 hours but will inevitably cause VEE to freeze at a Direct
> I/O object. After this freeze, VEE must be totally shut down and will lock
> up in the same way any other time a Direct I/O object is used until the
> computer has been restarted.
>
> I was wondering if anyone has encountered something similar in the past or
> have any ideas as to why this keeps happening. Any help is greatly
> appreciated.
> ---
> You are currently subscribed to vrf as: gregg.drwho8@gmail.com
> To subscribe send a blank email request to "join-vrf@lists.it.agilent.com".
> To unsubscribe send a blank email to
> "leave-vrf@it.lists.it.agilent.com".
> To send messages to this mailing list, email "vrf@agilent.com".
> If you need help with the mailing list send a message to
> "owner-vrf@it.lists.it.agilent.com".
> Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe send a blank email request to "join-vrf@lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
I don't believe that there is any difference between the data created
for RS-232 and RS-485, the difference seems to be hardware related
rather than in the actual data sent.
The answer to your question, however is that I am using VEE itself to
translate the data for sending. I just have a message in the form of
(header byte)(address byte)(command byte)(parameter byte)(end
byte)(check byte) and am pointing VEE to the RS-485 card I am using.
To Shawn Fessenden:
Thankyou for your insight! Do you have any ideas for dealing with driver
failure? And is it likely for them to fail in every instance of the
program running?
-----Original Message-----
From: Gregg Levine [mailto:gregg.drwho8@gmail.com]
Sent: Monday, February 20, 2006 13:33
To: VRF
Subject: Re: [vrf] Crash at Direct I/O
Hello!
Sean, one question comes to mind: What are you using to create the
RS485 data? The IOLIBs for VEE do create RS232 data, and they do of
course create GPIB/HPIB data, but that's all.
--
Gregg C Levine gregg.drwho8@gmail.com
"This signature was once found posting rude messages in English in the
Moscow subway."
You might also want to supply us with more information to add to this
issue.
On 2/20/06, Sean Watson <sean.watson@cmp.cpii.com> wrote:
> Hi Everyone,
>
> I have a VEE Pro program in which I query a moderately large
> number(10-20) of different units over an RS-485 communications line.
> Between these units there are two or three different I/O objects with
> varied settings (8-bit word, no parity; 7-bit word, no parity and
> 7-bit word, even parity). To send to these units, I create an array of
> all the units to send to and use a loop to cycle through all of them
repeatedly.
>
> What I am finding is that this will work for some amount of time,
> anywhere between 12 and 48 hours but will inevitably cause VEE to
> freeze at a Direct I/O object. After this freeze, VEE must be totally
> shut down and will lock up in the same way any other time a Direct I/O
> object is used until the computer has been restarted.
>
> I was wondering if anyone has encountered something similar in the
> past or have any ideas as to why this keeps happening. Any help is
> greatly appreciated.
> ---
> You are currently subscribed to vrf as: gregg.drwho8@gmail.com To
> subscribe send a blank email request to
"join-vrf@lists.it.agilent.com".
> To unsubscribe send a blank email to
> "leave-vrf@it.lists.it.agilent.com".
> To send messages to this mailing list, email "vrf@agilent.com".
> If you need help with the mailing list send a message to
> "owner-vrf@it.lists.it.agilent.com".
> Search the "unofficial vrf archive" at
"www.oswegosw.com/vrf_archive/".
---
You are currently subscribed to vrf as: sean.watson@cmp.cpii.com To
subscribe send a blank email request to "join-vrf@lists.it.agilent.com".
To unsubscribe send a blank email to
"leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to
"owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe send a blank email request to "join-vrf@lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
I don't believe that there is any difference between the data created
for RS-232 and RS-485, the difference seems to be hardware related
rather than in the actual data sent.
The answer to your question, however is that I am using VEE itself to
translate the data for sending. I just have a message in the form of
(header byte)(address byte)(command byte)(parameter byte)(end
byte)(check byte) and am pointing VEE to the RS-485 card I am using.
To Shawn Fessenden:
Thankyou for your insight! Do you have any ideas for dealing with driver
failure? And is it likely for them to fail in every instance of the
program running?
-----Original Message-----
From: Gregg Levine [mailto:gregg.drwho8@gmail.com]
Sent: Monday, February 20, 2006 13:33
To: VRF
Subject: Re: [vrf] Crash at Direct I/O
Hello!
Sean, one question comes to mind: What are you using to create the
RS485 data? The IOLIBs for VEE do create RS232 data, and they do of
course create GPIB/HPIB data, but that's all.
--
Gregg C Levine gregg.drwho8@gmail.com
"This signature was once found posting rude messages in English in the
Moscow subway."
You might also want to supply us with more information to add to this
issue.
On 2/20/06, Sean Watson <sean.watson@cmp.cpii.com> wrote:
> Hi Everyone,
>
> I have a VEE Pro program in which I query a moderately large
> number(10-20) of different units over an RS-485 communications line.
> Between these units there are two or three different I/O objects with
> varied settings (8-bit word, no parity; 7-bit word, no parity and
> 7-bit word, even parity). To send to these units, I create an array of
> all the units to send to and use a loop to cycle through all of them
repeatedly.
>
> What I am finding is that this will work for some amount of time,
> anywhere between 12 and 48 hours but will inevitably cause VEE to
> freeze at a Direct I/O object. After this freeze, VEE must be totally
> shut down and will lock up in the same way any other time a Direct I/O
> object is used until the computer has been restarted.
>
> I was wondering if anyone has encountered something similar in the
> past or have any ideas as to why this keeps happening. Any help is
> greatly appreciated.
> ---
> You are currently subscribed to vrf as: gregg.drwho8@gmail.com To
> subscribe send a blank email request to
"join-vrf@lists.it.agilent.com".
> To unsubscribe send a blank email to
> "leave-vrf@it.lists.it.agilent.com".
> To send messages to this mailing list, email "vrf@agilent.com".
> If you need help with the mailing list send a message to
> "owner-vrf@it.lists.it.agilent.com".
> Search the "unofficial vrf archive" at
"www.oswegosw.com/vrf_archive/".
---
You are currently subscribed to vrf as: sean.watson@cmp.cpii.com To
subscribe send a blank email request to "join-vrf@lists.it.agilent.com".
To unsubscribe send a blank email to
"leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to
"owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe send a blank email request to "join-vrf@lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
I'm pretty sure that's a decent method.
http://www.oswegosw.com/SearchVRF.php?st=%22blank%20line%22
> but I'm concerned about the
> possibility that I might encounter
> blank lines that don't include both.
If you'll be sucking text from Mac or 'NIX you will. Any Windows software
that doesn't do
(in that order) however is broken and needs to be
fixed.
-SHAWN-
---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe send a blank email request to "join-vrf@lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
I'm pretty sure that's a decent method.
http://www.oswegosw.com/SearchVRF.php?st=%22blank%20line%22
> but I'm concerned about the
> possibility that I might encounter
> blank lines that don't include both.
If you'll be sucking text from Mac or 'NIX you will. Any Windows software
that doesn't do
(in that order) however is broken and needs to be
fixed.
-SHAWN-
---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe send a blank email request to "join-vrf@lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
Â
I have a VEE Pro program in which I query a moderately large number(10-20) of different units over an RS-485 communications line. Between these units there are two or three different I/O objects with varied settings (8-bit word, no parity; 7-bit word, no parity and 7-bit word, even parity). To send to these units, I create an array of all the units to send to and use a loop to cycle through all of them repeatedly.
Â
What I am finding is that this will work for some amount of time, anywhere between 12 and 48 hours but will inevitably cause VEE to freeze at a Direct I/O object. After this freeze, VEE must be totally shut down and will lock up in the same way any other time a Direct I/O object is used until the computer has been restarted.
Â
I was wondering if anyone has encountered something similar in the past or have any ideas as to why this keeps happening. Any help is greatly appreciated.
---
To subscribe send a blank email request to "join-vrf@lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
Â
I have a VEE Pro program in which I query a moderately large number(10-20) of different units over an RS-485 communications line. Between these units there are two or three different I/O objects with varied settings (8-bit word, no parity; 7-bit word, no parity and 7-bit word, even parity). To send to these units, I create an array of all the units to send to and use a loop to cycle through all of them repeatedly.
Â
What I am finding is that this will work for some amount of time, anywhere between 12 and 48 hours but will inevitably cause VEE to freeze at a Direct I/O object. After this freeze, VEE must be totally shut down and will lock up in the same way any other time a Direct I/O object is used until the computer has been restarted.
Â
I was wondering if anyone has encountered something similar in the past or have any ideas as to why this keeps happening. Any help is greatly appreciated.
---
To subscribe send a blank email request to "join-vrf@lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
Sean, one question comes to mind: What are you using to create the
RS485 data? The IOLIBs for VEE do create RS232 data, and they do of course create GPIB/HPIB data, but that's all.
--
Gregg C Levine gregg.drwho8@gmail.com
"This signature was once found posting rude messages in English in the Moscow subway."
You might also want to supply us with more information to add to this issue.
On 2/20/06, Sean Watson <sean.watson@cmp.cpii.com> wrote:
> Hi Everyone,
>
> I have a VEE Pro program in which I query a moderately large
> number(10-20) of different units over an RS-485 communications line.
> Between these units there are two or three different I/O objects with
> varied settings (8-bit word, no parity; 7-bit word, no parity and
> 7-bit word, even parity). To send to these units, I create an array of
> all the units to send to and use a loop to cycle through all of them repeatedly.
>
> What I am finding is that this will work for some amount of time,
> anywhere between 12 and 48 hours but will inevitably cause VEE to
> freeze at a Direct I/O object. After this freeze, VEE must be totally
> shut down and will lock up in the same way any other time a Direct I/O
> object is used until the computer has been restarted.
>
> I was wondering if anyone has encountered something similar in the
> past or have any ideas as to why this keeps happening. Any help is
> greatly appreciated.
> ---
> You are currently subscribed to vrf as: gregg.drwho8@gmail.com To
> subscribe send a blank email request to "join-vrf@lists.it.agilent.com".
> To unsubscribe send a blank email to
> "leave-vrf@it.lists.it.agilent.com".
> To send messages to this mailing list, email "vrf@agilent.com".
> If you need help with the mailing list send a message to
> "owner-vrf@it.lists.it.agilent.com".
> Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
---
To subscribe send a blank email request to "join-vrf@lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
Sean, one question comes to mind: What are you using to create the
RS485 data? The IOLIBs for VEE do create RS232 data, and they do of course create GPIB/HPIB data, but that's all.
--
Gregg C Levine gregg.drwho8@gmail.com
"This signature was once found posting rude messages in English in the Moscow subway."
You might also want to supply us with more information to add to this issue.
On 2/20/06, Sean Watson <sean.watson@cmp.cpii.com> wrote:
> Hi Everyone,
>
> I have a VEE Pro program in which I query a moderately large
> number(10-20) of different units over an RS-485 communications line.
> Between these units there are two or three different I/O objects with
> varied settings (8-bit word, no parity; 7-bit word, no parity and
> 7-bit word, even parity). To send to these units, I create an array of
> all the units to send to and use a loop to cycle through all of them repeatedly.
>
> What I am finding is that this will work for some amount of time,
> anywhere between 12 and 48 hours but will inevitably cause VEE to
> freeze at a Direct I/O object. After this freeze, VEE must be totally
> shut down and will lock up in the same way any other time a Direct I/O
> object is used until the computer has been restarted.
>
> I was wondering if anyone has encountered something similar in the
> past or have any ideas as to why this keeps happening. Any help is
> greatly appreciated.
> ---
> You are currently subscribed to vrf as: gregg.drwho8@gmail.com To
> subscribe send a blank email request to "join-vrf@lists.it.agilent.com".
> To unsubscribe send a blank email to
> "leave-vrf@it.lists.it.agilent.com".
> To send messages to this mailing list, email "vrf@agilent.com".
> If you need help with the mailing list send a message to
> "owner-vrf@it.lists.it.agilent.com".
> Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
---
To subscribe send a blank email request to "join-vrf@lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
> past
Kind of. What I saw was that after hundreds of thousands of IO errors on RS-232 that VEE would reset - all variables would be deleted and the program began over again. The solution was to automatically reboot the computer after N errors. Login was handled automatically and the program was restarted in this instance. It picked up exactly where it left off and no data loss occurred.
The symptoms you describe seem to be indicative of a driver problem (on any flavor of NT anyway). When drivers fail, they must be unloaded, reloaded and reinitialized to clear up the problem. Depending on the driver, this may be possible without rebooting, though VEE would most probably have to be restarted.
-SHAWN-
> past
Kind of. What I saw was that after hundreds of thousands of IO errors on RS-232 that VEE would reset - all variables would be deleted and the program began over again. The solution was to automatically reboot the computer after N errors. Login was handled automatically and the program was restarted in this instance. It picked up exactly where it left off and no data loss occurred.
The symptoms you describe seem to be indicative of a driver problem (on any flavor of NT anyway). When drivers fail, they must be unloaded, reloaded and reinitialized to clear up the problem. Depending on the driver, this may be possible without rebooting, though VEE would most probably have to be restarted.
-SHAWN-
I don't believe that there is any difference between the data created for RS-232 and RS-485, the difference seems to be hardware related rather than in the actual data sent.
The answer to your question, however is that I am using VEE itself to translate the data for sending. I just have a message in the form of (header byte)(address byte)(command byte)(parameter byte)(end byte)(check byte) and am pointing VEE to the RS-485 card I am using.
To Shawn Fessenden:
Thankyou for your insight! Do you have any ideas for dealing with driver failure? And is it likely for them to fail in every instance of the program running?
-----Original Message-----
From: Gregg Levine [mailto:gregg.drwho8@gmail.com]
Sent: Monday, February 20, 2006 13:33
To: VRF
Subject: Re: [vrf] Crash at Direct I/O
Hello!
Sean, one question comes to mind: What are you using to create the
RS485 data? The IOLIBs for VEE do create RS232 data, and they do of course create GPIB/HPIB data, but that's all.
--
Gregg C Levine gregg.drwho8@gmail.com
"This signature was once found posting rude messages in English in the Moscow subway."
You might also want to supply us with more information to add to this issue.
On 2/20/06, Sean Watson <sean.watson@cmp.cpii.com> wrote:
> Hi Everyone,
>
> I have a VEE Pro program in which I query a moderately large
> number(10-20) of different units over an RS-485 communications line.
> Between these units there are two or three different I/O objects with
> varied settings (8-bit word, no parity; 7-bit word, no parity and
> 7-bit word, even parity). To send to these units, I create an array of
> all the units to send to and use a loop to cycle through all of them
repeatedly.
>
> What I am finding is that this will work for some amount of time,
> anywhere between 12 and 48 hours but will inevitably cause VEE to
> freeze at a Direct I/O object. After this freeze, VEE must be totally
> shut down and will lock up in the same way any other time a Direct I/O
> object is used until the computer has been restarted.
>
> I was wondering if anyone has encountered something similar in the
> past or have any ideas as to why this keeps happening. Any help is
> greatly appreciated.
> ---
> You are currently subscribed to vrf as: gregg.drwho8@gmail.com To
> subscribe send a blank email request to
"join-vrf@lists.it.agilent.com".
> To unsubscribe send a blank email to
> "leave-vrf@it.lists.it.agilent.com".
> To send messages to this mailing list, email "vrf@agilent.com".
> If you need help with the mailing list send a message to
> "owner-vrf@it.lists.it.agilent.com".
> Search the "unofficial vrf archive" at
"www.oswegosw.com/vrf_archive/".
---
You are currently subscribed to vrf as: sean.watson@cmp.cpii.com To subscribe send a blank email request to "join-vrf@lists.it.agilent.com".
To unsubscribe send a blank email to
"leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
---
To subscribe send a blank email request to "join-vrf@lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
I don't believe that there is any difference between the data created for RS-232 and RS-485, the difference seems to be hardware related rather than in the actual data sent.
The answer to your question, however is that I am using VEE itself to translate the data for sending. I just have a message in the form of (header byte)(address byte)(command byte)(parameter byte)(end byte)(check byte) and am pointing VEE to the RS-485 card I am using.
To Shawn Fessenden:
Thankyou for your insight! Do you have any ideas for dealing with driver failure? And is it likely for them to fail in every instance of the program running?
-----Original Message-----
From: Gregg Levine [mailto:gregg.drwho8@gmail.com]
Sent: Monday, February 20, 2006 13:33
To: VRF
Subject: Re: [vrf] Crash at Direct I/O
Hello!
Sean, one question comes to mind: What are you using to create the
RS485 data? The IOLIBs for VEE do create RS232 data, and they do of course create GPIB/HPIB data, but that's all.
--
Gregg C Levine gregg.drwho8@gmail.com
"This signature was once found posting rude messages in English in the Moscow subway."
You might also want to supply us with more information to add to this issue.
On 2/20/06, Sean Watson <sean.watson@cmp.cpii.com> wrote:
> Hi Everyone,
>
> I have a VEE Pro program in which I query a moderately large
> number(10-20) of different units over an RS-485 communications line.
> Between these units there are two or three different I/O objects with
> varied settings (8-bit word, no parity; 7-bit word, no parity and
> 7-bit word, even parity). To send to these units, I create an array of
> all the units to send to and use a loop to cycle through all of them
repeatedly.
>
> What I am finding is that this will work for some amount of time,
> anywhere between 12 and 48 hours but will inevitably cause VEE to
> freeze at a Direct I/O object. After this freeze, VEE must be totally
> shut down and will lock up in the same way any other time a Direct I/O
> object is used until the computer has been restarted.
>
> I was wondering if anyone has encountered something similar in the
> past or have any ideas as to why this keeps happening. Any help is
> greatly appreciated.
> ---
> You are currently subscribed to vrf as: gregg.drwho8@gmail.com To
> subscribe send a blank email request to
"join-vrf@lists.it.agilent.com".
> To unsubscribe send a blank email to
> "leave-vrf@it.lists.it.agilent.com".
> To send messages to this mailing list, email "vrf@agilent.com".
> If you need help with the mailing list send a message to
> "owner-vrf@it.lists.it.agilent.com".
> Search the "unofficial vrf archive" at
"www.oswegosw.com/vrf_archive/".
---
You are currently subscribed to vrf as: sean.watson@cmp.cpii.com To subscribe send a blank email request to "join-vrf@lists.it.agilent.com".
To unsubscribe send a blank email to
"leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
---
To subscribe send a blank email request to "join-vrf@lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
> with driver failure?
Seeing as how you're using MS's serial driver, nope. There *is* some kind of goofy interaction between VEE & the serial driver. Otherwise we wouldn't see the kinds of problems we do with RS-232 (IOW, it's not hard to cause the driver to get messed up - constant redefinition of buffer size will do it). These are probably localized in IO Libs. I think I do remember that some of these issues have been cleaned up lately. Specifically, the phony 811 error - I think.
There are at least two other options (besides rebooting): You can use the MS Comm control to do IO instead of Direct IO transactions. I use the IO control fairly regularly and I've never experienced any problems with it. There are also a variety of other serial controls you can use as well though I've never had the need for anything more than that provided by MS.
Another option, though not very desirable in VEE, is to use the serial API directly. It's not pretty, but it's doable. I've never experienced any problems with this method either, though it is much more difficult than using the control (no matter what language you're using).
There may be other options (like using a replacement serial driver for instance), but anything along that line may require abandoning Direct IO transactions too.
When you use Direct IO, you're going: VEE->IO Libs->API->driver->API->IO Libs->VEE. There are even some layers within this general structure. I usually say the best bet to fix problems in this case is to start peeling away some layers.
-SHAWN-