Hi Scott,
Possible, but not too probable, or would your scenario be able to show up only after several dozens of successful (!) communications with that particular device?
Unfortunately, I do not know yet what was the last successful operation, because it is a complicatwed environment and I had no chance yet to get in and install the development kit rather than the runtime version.
Thomas
-------- Original Message --------
Subject: RE: vrf Different Hang-Up (28-Sep-2001 16:47)
From: scott_morrison@Agilent.com
To: tv@huber-online.com
> By any chance have you noted any correlation between these 'hangups' and
> read statements in your code? I've run into similar problems reading data
> from VNAs where I had the read format fouled up. The only way I could
> recover was to use the task manager. Then, of course, fix the read
> statement.
>
> Scott Morrison
> (707) 577-3521
> Fax: 577-4942
>
>
>
> -----Original Message-----
> From: tv@huber-online.com [mailto:tv@huber-online.com]
> Sent: Friday, September 28, 2001 2:35 AM
> To: vrf@lvld.agilent.com
> Subject: vrf Different Hang-Up
>
>
> Hi everybody,
>
> I wrote a software which takes measured values form different instruments
> on
> one RS485 bus that I access via serial COM port and a full-automatic
> RS232/485 converter. Everything worked perfectly, I added one after the
> other component, and of course the program grew larger all the time.
>
> Since I added another component that talks MODBUS RTU (binary, not ASCII,
> like all the other ones), I have an effect that although everything works
> happily for a while (up to 45min), suddenly the program freezes and does
> not
> do anything anymore. It has to be closed with the task manager, rest of the
> PC is still ok.
>
> It is a WIN NT PC, the interpreter is VEE 5.01 runtime.
>
> Any ideas, did anybody see the same before? Is there anybody else who also
> talks several completely different communication forms (BINARY plus ASCII)
> on the same bus and has no problems?
>
> Help would be very much appreciated.
>
> Best Regards
>
> Dipl.-Ing. Thomas Vauderwange
> - UNISTAT Service & Software -
> Address:
> Tel. ++49 781 9603 253 Peter Huber Kltemaschinenbau
> GmbH
> Fax ++49 781 57211 Werner-von-Siemens-Strasse 1
> e-Mail: tv@huber-online.com D-77656 Offenburg GERMANY
> travelling: tv@service.huber-online.com
>
> PLEASE DO QUOTE THE SERIAL NUMBER OF MACHINES IN ALL YOUR COMMUNICATIONS.
>
> ---------------------------------------------------------------------
> 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".
> ---------------------------------------------------------------------
>
> To: tv@huber-online.com
> vrf@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".
---------------------------------------------------------------------
trace read that hungup the prog. My error was something like telling VEE to
read a 401pt trace while the inst was only sending a 201pt trace. Actually
it was worse than that, the data format itself was specified incorrectly in
the read statement so VEE did what it could with the data coming at it from
the inst.
Scott Morrison
(707) 577-3521
Fax: 577-4942
-----Original Message-----
From: tv@huber-online.com [mailto:tv@huber-online.com]
Sent: Friday, September 28, 2001 8:29 AM
To: vrf@lvld.agilent.com
Subject: Re-2: vrf Different Hang-Up
Hi Scott,
Possible, but not too probable, or would your scenario be able to show up
only after several dozens of successful (!) communications with that
particular device?
Unfortunately, I do not know yet what was the last successful operation,
because it is a complicatwed environment and I had no chance yet to get in
and install the development kit rather than the runtime version.
Thomas
-------- Original Message --------
Subject: RE: vrf Different Hang-Up (28-Sep-2001 16:47)
From: scott_morrison@Agilent.com
To: tv@huber-online.com
> By any chance have you noted any correlation between these 'hangups' and
> read statements in your code? I've run into similar problems reading data
> from VNAs where I had the read format fouled up. The only way I could
> recover was to use the task manager. Then, of course, fix the read
> statement.
>
> Scott Morrison
> (707) 577-3521
> Fax: 577-4942
>
>
>
> -----Original Message-----
> From: tv@huber-online.com [mailto:tv@huber-online.com]
> Sent: Friday, September 28, 2001 2:35 AM
> To: vrf@lvld.agilent.com
> Subject: vrf Different Hang-Up
>
>
> Hi everybody,
>
> I wrote a software which takes measured values form different instruments
> on
> one RS485 bus that I access via serial COM port and a full-automatic
> RS232/485 converter. Everything worked perfectly, I added one after the
> other component, and of course the program grew larger all the time.
>
> Since I added another component that talks MODBUS RTU (binary, not ASCII,
> like all the other ones), I have an effect that although everything works
> happily for a while (up to 45min), suddenly the program freezes and does
> not
> do anything anymore. It has to be closed with the task manager, rest of
the
> PC is still ok.
>
> It is a WIN NT PC, the interpreter is VEE 5.01 runtime.
>
> Any ideas, did anybody see the same before? Is there anybody else who also
> talks several completely different communication forms (BINARY plus ASCII)
> on the same bus and has no problems?
>
> Help would be very much appreciated.
>
> Best Regards
>
> Dipl.-Ing. Thomas Vauderwange
> - UNISTAT Service & Software -
> Address:
> Tel. ++49 781 9603 253 Peter Huber Kltemaschinenbau
> GmbH
> Fax ++49 781 57211 Werner-von-Siemens-Strasse 1
> e-Mail: tv@huber-online.com D-77656 Offenburg GERMANY
> travelling: tv@service.huber-online.com
>
> PLEASE DO QUOTE THE SERIAL NUMBER OF MACHINES IN ALL YOUR COMMUNICATIONS.
>
> ---------------------------------------------------------------------
> 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".
> ---------------------------------------------------------------------
>
> To: tv@huber-online.com
> vrf@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".
---------------------------------------------------------------------
---------------------------------------------------------------------
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".
---------------------------------------------------------------------