Program download problem
On Wed, 3 May 2000, Hans Magnet wrote:
> Hi,
>
> I have had an intermittent problem with loading a program to my
> Stamp. The program load sometimes works and sometimes doesn't, and I
I have had some problems in the past where I had the stamp running in a
tight loop at startup. After loading the program and it starting its loop,
it was difficult to get it to program. Usually took ten or more trys to
regain control. I started putting a one second pause at the start of my
programs and the problem went away.
Just my .02,
Dale Harwood [noparse][[/noparse] N4VFF ]
internet> dale@h...
ax.25> n4vff@n4vff.#cha.tn.usa.noam
#include <std_disclaimer.h>
> Hi,
>
> I have had an intermittent problem with loading a program to my
> Stamp. The program load sometimes works and sometimes doesn't, and I
I have had some problems in the past where I had the stamp running in a
tight loop at startup. After loading the program and it starting its loop,
it was difficult to get it to program. Usually took ten or more trys to
regain control. I started putting a one second pause at the start of my
programs and the problem went away.
Just my .02,
Dale Harwood [noparse][[/noparse] N4VFF ]
internet> dale@h...
ax.25> n4vff@n4vff.#cha.tn.usa.noam
#include <std_disclaimer.h>
Comments
I have had an intermittent problem with loading a program to my
Stamp. The program load sometimes works and sometimes doesn't, and I
see no rational reason why it goes on strike, there appears to be no
consistency. This intermittent problem lasts from a few attempts to a
day. Quite frustrating when I am trying to write a program and need
to run it after a change!
I suspect the cause is something Windows 98 is doing with the Com1
port.
Does that seem likely?
My OS is Windows 98.
The Basic Stamp is BSIISX.
The Basic Stamp Editor is version 1.091 beta.
The settings are correct in the "Preferences" and "Editor Operations"
(BS2SX, Com1, and All or Current).
The cable connection is OK.
Sometimes it is not possible to load the program to the BSIISX.
When the problem occurs:
1) The signal gets from laptop to the BSIISX Basic Stamp, as it is
reset on giving the "run" command.
2) The signal also gets from the Stamp to the laptop as I see the
serout response in the debug window on the laptop screen at the same
time as it is shown on the instruments LCD screen.
3) The cable connecting Stamp and laptop is OK, as point 1), 2) and
the program was downloaded before and downloads after this problem
occurs.
The message when the problem occurs says as follows:
Basic Stamp IISX not responding on com 1
1. Check serial cable connection.
2. Check power supply.
In these cases there is a serial connection, connected properly, and
power is on (via a transformer).
The last time this problem occurred it lasted about 2 hours, but when
I returned from a coffee break it worked! Nothing had been changed
since the previous attempt, when it didn't work.
Thanx for your help,
Hans Magn
>Hi,
>
>I have had an intermittent problem with loading a program to my
>Stamp. The program load sometimes works and sometimes doesn't, and I
>see no rational reason why it goes on strike, there appears to be no
>consistency. This intermittent problem lasts from a few attempts to a
>day. Quite frustrating when I am trying to write a program and need
>to run it after a change!
>
>I suspect the cause is something Windows 98 is doing with the Com1
>port.
>Does that seem likely?
>
>My OS is Windows 98.
>The Basic Stamp is BSIISX.
>The Basic Stamp Editor is version 1.091 beta.
>The settings are correct in the "Preferences" and "Editor Operations"
>(BS2SX, Com1, and All or Current).
>The cable connection is OK.
>
>Sometimes it is not possible to load the program to the BSIISX.
>When the problem occurs:
>1) The signal gets from laptop to the BSIISX Basic Stamp, as it is
^^^^^^
>reset on giving the "run" command.
Hans -
There have been various reported problems with laptops as well as
laptops with Win 98, and even WIN 98 alone. Below are just some trouble
shooting thoughts, since there will have to be a process of elimination
before real debugging of the problem can occur.
Reported Problems
Some have to do with the power-save features
( [noparse][[/noparse]#1] comm port not being restored quickly enough,
[noparse][[/noparse]#2] some other power-save feature impacting timing),
and others seem to point to comm port voltages
( [noparse][[/noparse]#3] inherent lowered port voltages on some non-standard or older laptops
[noparse][[/noparse]#4] lowered voltages do to depleted or low battery resources)
Some have been said to reflect timing considerations of the port as controlled
by the operating system
( [noparse][[/noparse]#5] comm port settings in "control panel" area
[noparse][[/noparse]#6] comm board driver conflicts involving timing )
>2) The signal also gets from the Stamp to the laptop as I see the
>serout response in the debug window on the laptop screen at the same
>time as it is shown on the instruments LCD screen.
>3) The cable connecting Stamp and laptop is OK, as point 1), 2) and
>the program was downloaded before and downloads after this problem
>occurs.
Guaranteeing that a programming cable is "known good" (INCLUSIVE of
intermittant
wires on a home made cable) is highly important. Many problems end up back
here
after a long, exhaustive and fruitless troubleshooting process.
>
>The message when the problem occurs says as follows:
>
> Basic Stamp IISX not responding on com 1
> 1. Check serial cable connection.
> 2. Check power supply.
>
You might want to try com 2 (or some other port) if that is possible
on your computer. Sometimes this can provide additional information.
> In these cases there is a serial connection, connected properly, and
>power is on (via a transformer).
>
>The last time this problem occurred it lasted about 2 hours, but when
>I returned from a coffee break it worked! Nothing had been changed
>since the previous attempt, when it didn't work.
Sometimes this is just a matter of the battery peaking. Laptops (when online)
often only trickle charge. Turning the system off brings about a higher
charge
rate. Check your manual for details.
Additionally, there is the matter of power-save, in conjunction with
battery voltage.
In this case there may be a compound problem of delayed timing and battery
voltage.
>
> Thanx for your help,
I'm sure if you mention the name of your laptop, there may be others who have
personal experience, and may be able to assist further. That found above is
just
a general outline (with problem reference numbers) for further discussion.
Hope this helps
> Hans Magn
The laptop is a Siemens Scenic Mobile 360.
Regards,
Hans
--- In basicstamps@egroups.com, Bruce Bates <bvbates@m...> wrote:
> At 08:42 AM 5/3/00 -0000, Hans Magnet promulgated:
> >Hi,
> >
> >I have had an intermittent problem with loading a program to my
> >Stamp. The program load sometimes works and sometimes doesn't, and
I
> >see no rational reason why it goes on strike, there appears to be
no
> >consistency. This intermittent problem lasts from a few attempts
to a
> >day. Quite frustrating when I am trying to write a program and
need
> >to run it after a change!
> >
> >I suspect the cause is something Windows 98 is doing with the Com1
> >port.
> >Does that seem likely?
> >
> >My OS is Windows 98.
> >The Basic Stamp is BSIISX.
> >The Basic Stamp Editor is version 1.091 beta.
> >The settings are correct in the "Preferences" and "Editor
Operations"
> >(BS2SX, Com1, and All or Current).
> >The cable connection is OK.
> >
> >Sometimes it is not possible to load the program to the BSIISX.
> >When the problem occurs:
>
> >1) The signal gets from laptop to the BSIISX Basic Stamp, as it is
> ^^^^^^
> >reset on giving the "run" command.
>
> Hans -
>
> There have been various reported problems with laptops as well as
> laptops with Win 98, and even WIN 98 alone. Below are just some
trouble
> shooting thoughts, since there will have to be a process of
elimination
> before real debugging of the problem can occur.
>
> Reported Problems
>
> Some have to do with the power-save features
>
> ( [noparse][[/noparse]#1] comm port not being restored quickly enough,
> [noparse][[/noparse]#2] some other power-save feature impacting timing),
>
> and others seem to point to comm port voltages
>
> ( [noparse][[/noparse]#3] inherent lowered port voltages on some non-standard or older
laptops
> [noparse][[/noparse]#4] lowered voltages do to depleted or low battery resources)
>
> Some have been said to reflect timing considerations of the port as
controlled
> by the operating system
>
> ( [noparse][[/noparse]#5] comm port settings in "control panel" area
> [noparse][[/noparse]#6] comm board driver conflicts involving timing )
>
>
> >2) The signal also gets from the Stamp to the laptop as I see the
> >serout response in the debug window on the laptop screen at the
same
> >time as it is shown on the instruments LCD screen.
> >3) The cable connecting Stamp and laptop is OK, as point 1), 2)
and
> >the program was downloaded before and downloads after this problem
> >occurs.
>
> Guaranteeing that a programming cable is "known good" (INCLUSIVE of
> intermittant
> wires on a home made cable) is highly important. Many problems end
up back
> here
> after a long, exhaustive and fruitless troubleshooting process.
>
> >
> >The message when the problem occurs says as follows:
> >
> > Basic Stamp IISX not responding on com 1
> > 1. Check serial cable connection.
> > 2. Check power supply.
> >
>
> You might want to try com 2 (or some other port) if that is possible
> on your computer. Sometimes this can provide additional information.
>
> > In these cases there is a serial connection, connected properly,
and
> >power is on (via a transformer).
> >
> >The last time this problem occurred it lasted about 2 hours, but
when
> >I returned from a coffee break it worked! Nothing had been changed
> >since the previous attempt, when it didn't work.
>
> Sometimes this is just a matter of the battery peaking. Laptops
(when online)
> often only trickle charge. Turning the system off brings about a
higher
> charge
> rate. Check your manual for details.
>
> Additionally, there is the matter of power-save, in conjunction with
> battery voltage.
> In this case there may be a compound problem of delayed timing and
battery
> voltage.
>
> >
> > Thanx for your help,
>
> I'm sure if you mention the name of your laptop, there may be
others who have
> personal experience, and may be able to assist further. That found
above is
> just
> a general outline (with problem reference numbers) for further
discussion.
>
> Hope this helps
>
> > Hans Magn