Results 1 to 10 of 10

Thread: BS2-SX Load problems...

  1. #1

    Default BS2-SX Load problems...

    I keep getting "BASIC STAMP IISX DETECTED BUT NOT RESPONDING ON COM3.
    CHECK POWER SUPPLY".

    When I write a simple project made up of several short programs (say
    0-4) it works. But when I add a more complex program to the list of
    programs it has to run it gives me the message you see above.

    Frustrating!

    Further... when I run the more complex program by itself as program
    zero, it seems to work fine.

    What gives?

    Ross
    Last edited by ForumTools; 10-02-2010 at 08:08 PM. Reason: Forum Migration

  2. #2

    Default

    I had the exact same problem!
    Assuming you are using the windows software you need to tell the
    software which stamp you are using.

    On the menu : File Edit Run Help
    click "Edit"
    Click "Preferences"
    Click "Editor Operation"
    Under " Stamp Mode and Ports"
    "Default Stamp Mode:" Change the selection from "BS2" to "BS2SX"
    Click "OK"

    Now if you click the "ID" or "RUN" Buttons they should work!


    David Burleson
    dburlesn@v...


    --- In basicstamps@egroups.com, rossfree@m... wrote:
    > I keep getting "BASIC STAMP IISX DETECTED BUT NOT RESPONDING ON
    COM3.
    > CHECK POWER SUPPLY".
    >
    > When I write a simple project made up of several short programs
    (say
    > 0-4) it works. But when I add a more complex program to the list of
    > programs it has to run it gives me the message you see above.
    >
    > Frustrating!
    >
    > Further... when I run the more complex program by itself as program
    > zero, it seems to work fine.
    >
    > What gives?
    >
    > Ross
    Last edited by ForumTools; 10-02-2010 at 08:08 PM. Reason: Forum Migration

  3. #3

    Default

    Thanks David but no good. I had the SX preference checked off early
    on. Thanks for trying!

    Anyone else??? The search is still on! :-)

    Ross


    --- In basicstamps@egroups.com, "David Burleson" <dburlesn@v...>
    wrote:
    > I had the exact same problem!
    > Assuming you are using the windows software you need to tell the
    > software which stamp you are using.
    >
    > On the menu : File Edit Run Help
    > click "Edit"
    > Click "Preferences"
    > Click "Editor Operation"
    > Under " Stamp Mode and Ports"
    > "Default Stamp Mode:" Change the selection from "BS2" to "BS2SX"
    > Click "OK"
    >
    > Now if you click the "ID" or "RUN" Buttons they should work!
    >
    >
    > David Burleson
    > dburlesn@v...
    >
    >
    > --- In basicstamps@egroups.com, rossfree@m... wrote:
    > > I keep getting "BASIC STAMP IISX DETECTED BUT NOT RESPONDING ON
    > COM3.
    > > CHECK POWER SUPPLY".
    > >
    > > When I write a simple project made up of several short programs
    > (say
    > > 0-4) it works. But when I add a more complex program to the list
    of
    > > programs it has to run it gives me the message you see above.
    > >
    > > Frustrating!
    > >
    > > Further... when I run the more complex program by itself as
    program
    > > zero, it seems to work fine.
    > >
    > > What gives?
    > >
    > > Ross
    Last edited by ForumTools; 10-02-2010 at 08:08 PM. Reason: Forum Migration

  4. #4

    Default

    OK,
    What does your code look like?
    You can override the preference setting from within your code with the
    $STAMP directive.
    Near the top place a comment that reads:

    '{$STAMP BS2SX}

    OR of it is for a project consisting of multiple files use:

    '{STAMP BS2SX,file1,file2,...,file7}


    Hope this works.


    David

    ----- Original Message -----
    From: <rossfree@m...>
    To: <basicstamps@egroups.com>
    Sent: Saturday, August 26, 2000 7:37 AM
    Subject: [basicstamps] Re: BS2-SX Load problems...


    > Thanks David but no good. I had the SX preference checked off early
    > on. Thanks for trying!
    >
    > Anyone else??? The search is still on! :-)
    >
    > Ross
    >
    >
    Last edited by ForumTools; 10-02-2010 at 08:08 PM. Reason: Forum Migration

  5. #5

    Default

    >I keep getting "BASIC STAMP IISX DETECTED BUT NOT RESPONDING ON COM3.
    >CHECK POWER SUPPLY".
    >When I write a simple project made up of several short programs (say
    >0-4) it works. But when I add a more complex program to the list of
    >programs it has to run it gives me the message you see above.
    >Frustrating!
    >Further... when I run the more complex program by itself as program
    >zero, it seems to work fine.
    >What gives?
    >Ross

    Hi Ross,

    Low battery? A marginal power supply could do strange things especially
    with the BS2sx because of its larger power drain. Loose cable?

    At what point does the run fail, that is, does it even get part way
    through, or does it fail right at the beginning? The timing of the
    handshaking between the stamp and stampw.exe is quite touchy. The
    operating system might get in the way. Turn off any other stuff that might
    check the serial port. Turn off as many TSRs as you can to streamline the
    operating system.

    As a workaround, set the editor preferences to send only the "current
    program". Then, you should be able to run the programs one at a time into
    your stamp. Does that work?

    -- Tracy Allen
    Electronically Monitored Ecosystems
    http://www.emesystems.com
    Last edited by ForumTools; 10-02-2010 at 08:08 PM. Reason: Forum Migration

  6. #6

    Default

    Thanks for the reply David...

    Been there, done that. The code for the stamp is there.

    Any other ideas?

    Ross


    --- In basicstamps@egroups.com, "David Burleson" <dburlesn@v...>
    wrote:
    > OK,
    > What does your code look like?
    > You can override the preference setting from within your code with
    the
    > $STAMP directive.
    > Near the top place a comment that reads:
    >
    > '{$STAMP BS2SX}
    >
    > OR of it is for a project consisting of multiple files use:
    >
    > '{STAMP BS2SX,file1,file2,...,file7}
    >
    >
    > Hope this works.
    >
    >
    > David
    >
    > ----- Original Message -----
    > From: <rossfree@m...>
    > To: <basicstamps@egroups.com>
    > Sent: Saturday, August 26, 2000 7:37 AM
    > Subject: [basicstamps] Re: BS2-SX Load problems...
    >
    >
    > > Thanks David but no good. I had the SX preference checked off
    early
    > > on. Thanks for trying!
    > >
    > > Anyone else??? The search is still on! :-)
    > >
    > > Ross
    > >
    > >
    Last edited by ForumTools; 10-02-2010 at 08:08 PM. Reason: Forum Migration

  7. #7

    Default

    Thanks Tracy... all good ideas.

    I am currently using a 9VAC power supply. I've used two different
    supplies and gotten the same message. I have 450ma available to me.
    Unless the supply is very dirty (noisy), and I have a nice fat cap to
    handle that, I don't think the supply is the problem.

    I suspect the operating system and handshaking as you suggest. I have
    not tried loading the programs one at a time. Good suggestion. But if
    the project consists of several programs, will one overwrite the
    other if they are not loaded all at the same time? I still
    think 'BS2'. :-)

    The project I've been trying to run consists of several place holder
    programs (to be filled as I progress in my project) and a fairly
    large keypad program. So the first several programs are 'pop in...
    yep I made it in... pop out to the next program'. I would have the
    display indicate that I did in fact make it from one program to the
    next, then move on. The first SX project I wrote did nothing more
    than that. Program 0 - 4, each in turn, would consist of a display
    instruction, then a run (the next program number) instruction.

    It worked fine. Once that was done, I started filling in one of the
    place holder programs with real stuff... my keypad program. It quit
    working. So I ran the keypad program as a stand alone SX program.
    Program 0 became the keypad program. It ran. Go figure!

    I would say it's a problem that must be related to my own computer,
    except that I had the same problems with an old laptop I was using as
    well. The same problems!

    You asked when the program would quit loading. I haven't actually
    thought to watch. But it seems to stop when it hits the big one...
    the keypad program. The others seem to make it through.

    I will check for TSR's and also try loading the programs one at a
    time... I'd still like more clarification on that one. Does it in
    fact add programs to the project currently stored on the chip or does
    it erase the programs there and replace it with the program you are
    storing? HMMMMM???

    I've got to keep going... need to finish this project! HELP!

    Thanks again!!!

    Ross




    --- In basicstamps@egroups.com, Tracy Allen <emesys@c...> wrote:
    > >I keep getting "BASIC STAMP IISX DETECTED BUT NOT RESPONDING ON
    COM3.
    > >CHECK POWER SUPPLY".
    > >When I write a simple project made up of several short programs
    (say
    > >0-4) it works. But when I add a more complex program to the list
    of
    > >programs it has to run it gives me the message you see above.
    > >Frustrating!
    > >Further... when I run the more complex program by itself as
    program
    > >zero, it seems to work fine.
    > >What gives?
    > >Ross
    >
    > Hi Ross,
    >
    > Low battery? A marginal power supply could do strange things
    especially
    > with the BS2sx because of its larger power drain. Loose cable?
    >
    > At what point does the run fail, that is, does it even get part way
    > through, or does it fail right at the beginning? The timing of the
    > handshaking between the stamp and stampw.exe is quite touchy. The
    > operating system might get in the way. Turn off any other stuff
    that might
    > check the serial port. Turn off as many TSRs as you can to
    streamline the
    > operating system.
    >
    > As a workaround, set the editor preferences to send only
    the "current
    > program". Then, you should be able to run the programs one at a
    time into
    > your stamp. Does that work?
    >
    > -- Tracy Allen
    > Electronically Monitored Ecosystems
    > http://www.emesystems.com
    Last edited by ForumTools; 10-02-2010 at 08:08 PM. Reason: Forum Migration

  8. #8

    Default

    Well,
    Did it ever work?
    Have you isolated the com port? instead of Com3 try Com1 or Com2
    Preferably one that doesn't share an IRQ with another device.Like a modem
    What is your power supply?
    If a battery, is it low?
    What operating system.
    I normally use Windows 2000 Professional, or 2000 Advanced Server.
    Neither work with my stamp software.
    I have to reboot to Windows 98 to program my stamp.

    Good Luck,

    David B.

    ----- Original Message -----
    From: <rossfree@m...>
    To: <basicstamps@egroups.com>
    Sent: Saturday, August 26, 2000 9:36 PM
    Subject: [basicstamps] Re: BS2-SX Load problems...


    > Thanks for the reply David...
    >
    > Been there, done that. The code for the stamp is there.
    >
    > Any other ideas?
    >
    > Ross
    >
    >
    > --- In basicstamps@egroups.com, "David Burleson" <dburlesn@v...>
    > wrote:
    > > OK,
    > > What does your code look like?
    > > You can override the preference setting from within your code with
    > the
    > > $STAMP directive.
    > > Near the top place a comment that reads:
    > >
    > > '{$STAMP BS2SX}
    > >
    > > OR of it is for a project consisting of multiple files use:
    > >
    > > '{STAMP BS2SX,file1,file2,...,file7}
    > >
    > >
    > > Hope this works.
    > >
    > >
    > > David
    > >
    > > ----- Original Message -----
    > > From: <rossfree@m...>
    > > To: <basicstamps@egroups.com>
    > > Sent: Saturday, August 26, 2000 7:37 AM
    > > Subject: [basicstamps] Re: BS2-SX Load problems...
    > >
    > >
    > > > Thanks David but no good. I had the SX preference checked off
    > early
    > > > on. Thanks for trying!
    > > >
    > > > Anyone else??? The search is still on! :-)
    > > >
    > > > Ross
    > > >
    > > >
    >
    >
    >
    Last edited by ForumTools; 10-02-2010 at 08:08 PM. Reason: Forum Migration

  9. #9

    Default

    >I have
    >not tried loading the programs one at a time. Good suggestion. But if
    >the project consists of several programs, will one overwrite the
    >other if they are not loaded all at the same time? I still
    >think 'BS2'. :-)

    Hi again Ross,

    As you know, each BS2SX project consists of up to 8 programs, specified by
    the $STAMP directive at the head of the the file0.bsx program:
    '{$STAMP BS2SX, file1, file2,...,file7}
    Each of those programs nameed in the directive is uniquely associated with
    one of the program banks in the 'SX. You can elect to run one program at a
    time, by choosing the "current" option on the editor operation tab. When
    you have a current program in front on the screen, and RUN it, then only
    that program is loaded into the corresponding bank in the BS2SX. None of
    the other banks are affected.

    For example, if you elect to run only program number 2, then only that
    program is sent. It replaces the current contents of program bank number 2.
    Banks 0, 1, and 3 to 7 are not changed. You can step one by one through
    the programs that are part of a project and run them individually. The
    effect is the same as if you had RUN them all at once under the "all"
    option. (BTW, in the DOS software (STAMP2SX.EXE), the bank-at-a-time method
    is the only option and has to be done manually.)

    There is also a "modified" option that RUNs only those programs that have
    been modified since your last run. The "modified" option has no way of
    knowing what is already programmed into the BS2SX chip, so when you first
    load an existing project into the STAMP2W.EXE environment, the "modified"
    option will send _all_ the programs when you first RUN one of them.

    When you RUN a multi-bank project, the program action for each bank is
    quite independent of the others. From the PC-->BS2SX point of view, the
    RUN consists of independent banks. The PC resets the BS2SX before
    transmitting the data, and the programming header includes the number of
    the bank that is being targeted by the current RUN. The action is the
    same, whether you are running one program of a project under the "current"
    option, or several programs of a project under the "all" or "modified"
    options.

    The programming protocol requires handshake data to bounce back from the
    BS2SX very fast, and that is where some operating systems get tripped up.
    If the outgoing and incoming characters go onto some kind of OS queue, and
    are not serviced in time, then you will see that awful ""BASIC STAMP IISX
    DETECTED BUT NOT RESPONDING ON COMn". At least that is my theory. I have
    been lobbying Parallax to relax that timing. It is now about 18
    milliseconds to timeout, but it seems to me there would be a lot less
    problems with bloated OS's if it were relaxed to 80 or 100 milliseconds.
    Then I think I could even run it on my Mac under softwindows, which buffers
    the serial data on a 50 millisecond clock.

    I hope that clarifies a little how the BS2SX options work. I do not know
    how it relates to what you are seeing, but the timing is tight. It sounds
    like you might be close, so have a go at those TSRs and serial port setups.

    -- Tracy Allen
    Electronically Monitored Ecosystems
    http://www.emesystems.com
    Last edited by ForumTools; 10-02-2010 at 08:08 PM. Reason: Forum Migration

  10. #10

    Default

    Hi Tracy,

    It works! I have been able to run each program individually with
    STAMPWIN. Thankyou!

    I just got this in from STAMPTECH. I haven't tried it but it fits the
    profile I'm working in.

    Thanks again Tracy and all who have tried to help!!!

    Ross

    see below...

    Hello (from stamp tech),


    One way to solve this problem might be to put a debug command in the
    first
    program. What happens is, that when you put a debug command in 3rd
    program, it runs the programs and stops when it comes to the debug
    command
    and the stamp says where is the rest of the program while its trying
    to
    open the debug window. So to get around this you need to put in a
    debug
    statement in the first program, then the whole program will run. If
    you
    have any more questions please feel free to e-mail us.


    At 12:31 PM 8/26/00 -0400, you wrote:
    >Hey folks,
    >
    >I keep getting "BASIC STAMP IISX DETECTED BUT NOT RESPONDING ON COM3.
    >CHECK POWER SUPPLY".
    >
    >When I write a simple project made up of several short programs (say
    >0-4) it works. But when I add a more complex program to the list of
    >programs it has to run it gives me the message you see above.
    >
    >Frustrating!
    >
    >Further... when I run the more complex program by itself as program
    >zero, it seems to work fine.
    >
    >What gives?
    >
    >os: win98 AMD K6 500
    >Stampw_v1_096.exe
    >
    >I have set the program preferences to SX , default com port to AUTO
    and
    >download mode to ALL.
    >
    >A copy of the program (that won't load) is attached (2 files). The
    program
    >is incomplete but tokenizes ok and should work.
    >
    >Help please! Thank you.
    >
    >Ross
    >


    --- In basicstamps@egroups.com, Tracy Allen <emesys@c...> wrote:
    > >I have
    > >not tried loading the programs one at a time. Good suggestion. But
    if
    > >the project consists of several programs, will one overwrite the
    > >other if they are not loaded all at the same time? I still
    > >think 'BS2'. :-)
    >
    > Hi again Ross,
    >
    > As you know, each BS2SX project consists of up to 8 programs,
    specified by
    > the $STAMP directive at the head of the the file0.bsx program:
    > '{$STAMP BS2SX, file1, file2,...,file7}
    > Each of those programs nameed in the directive is uniquely
    associated with
    > one of the program banks in the 'SX. You can elect to run one
    program at a
    > time, by choosing the "current" option on the editor operation
    tab. When
    > you have a current program in front on the screen, and RUN it, then
    only
    > that program is loaded into the corresponding bank in the BS2SX.
    None of
    > the other banks are affected.
    >
    > For example, if you elect to run only program number 2, then only
    that
    > program is sent. It replaces the current contents of program bank
    number 2.
    > Banks 0, 1, and 3 to 7 are not changed. You can step one by one
    through
    > the programs that are part of a project and run them individually.
    The
    > effect is the same as if you had RUN them all at once under
    the "all"
    > option. (BTW, in the DOS software (STAMP2SX.EXE), the bank-at-a-
    time method
    > is the only option and has to be done manually.)
    >
    > There is also a "modified" option that RUNs only those programs
    that have
    > been modified since your last run. The "modified" option has no
    way of
    > knowing what is already programmed into the BS2SX chip, so when you
    first
    > load an existing project into the STAMP2W.EXE environment,
    the "modified"
    > option will send _all_ the programs when you first RUN one of
    them.
    >
    > When you RUN a multi-bank project, the program action for each bank
    is
    > quite independent of the others. From the PC-->BS2SX point of
    view, the
    > RUN consists of independent banks. The PC resets the BS2SX before
    > transmitting the data, and the programming header includes the
    number of
    > the bank that is being targeted by the current RUN. The action is
    the
    > same, whether you are running one program of a project under
    the "current"
    > option, or several programs of a project under the "all"
    or "modified"
    > options.
    >
    > The programming protocol requires handshake data to bounce back
    from the
    > BS2SX very fast, and that is where some operating systems get
    tripped up.
    > If the outgoing and incoming characters go onto some kind of OS
    queue, and
    > are not serviced in time, then you will see that awful ""BASIC
    STAMP IISX
    > DETECTED BUT NOT RESPONDING ON COMn". At least that is my theory.
    I have
    > been lobbying Parallax to relax that timing. It is now about 18
    > milliseconds to timeout, but it seems to me there would be a lot
    less
    > problems with bloated OS's if it were relaxed to 80 or 100
    milliseconds.
    > Then I think I could even run it on my Mac under softwindows, which
    buffers
    > the serial data on a 50 millisecond clock.
    >
    > I hope that clarifies a little how the BS2SX options work. I do
    not know
    > how it relates to what you are seeing, but the timing is tight. It
    sounds
    > like you might be close, so have a go at those TSRs and serial port
    setups.
    >
    > -- Tracy Allen
    > Electronically Monitored Ecosystems
    > http://www.emesystems.com
    Last edited by ForumTools; 10-02-2010 at 08:08 PM. Reason: Forum Migration

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts