Shop OBEX P1 Docs P2 Docs Learn Events
serial communications with BS2 — Parallax Forums

serial communications with BS2

ArchiverArchiver Posts: 46,084
edited 2002-02-11 19:57 in General Discussion
I'm attempting to intercept the serial data that comes back to the
BS2 debug window that's supported by the Basic stamp editor (v1.3).
I'm using the MSComm ActiveX control in VB6 pro.

The BS2 debug window receives data with settings of 9600 baud, parity
none, data bits 8. When I configure the MSComm control with these
same parameters, I see no input. However, when I slow the baud rate
down to 1200 baud (on the control), I can detect data transmissions
at the same frequency as the debug window. However, the data received
is bogus and the MSComm control detects an input buffer length of 0
bytes.

Is it necessary to enable some sort of handshaking in order to
establish receive-only communications with the BS2? (Any tips or
examples appreciated!)

Thanks!

Comments

  • ArchiverArchiver Posts: 46,084
    edited 2002-02-11 03:36
    It is not necessary to setup any handshaking. I did this a while back and
    used a VB6 program I wrote. I cannot remember specifics as it was about
    1yr ago, sorry. Check your parameters again in the VB program. Sounds
    like you have something configured incorrectly.

    Brian
  • ArchiverArchiver Posts: 46,084
    edited 2002-02-11 04:40
    I've come across this before. Set the control for no handshaking.

    If you can see the data in the terminal windows or in Hypterterminal then
    the data is there!

    Regards,

    Tony Wells
    Original Message
    From: "donnmoidaho" <donnmo@l...>
    To: <basicstamps@yahoogroups.com>
    Sent: Monday, February 11, 2002 2:17 AM
    Subject: [noparse][[/noparse]basicstamps] serial communications with BS2


    > I'm attempting to intercept the serial data that comes back to the
    > BS2 debug window that's supported by the Basic stamp editor (v1.3).
    > I'm using the MSComm ActiveX control in VB6 pro.
    >
    > The BS2 debug window receives data with settings of 9600 baud, parity
    > none, data bits 8. When I configure the MSComm control with these
    > same parameters, I see no input. However, when I slow the baud rate
    > down to 1200 baud (on the control), I can detect data transmissions
    > at the same frequency as the debug window. However, the data received
    > is bogus and the MSComm control detects an input buffer length of 0
    > bytes.
    >
    > Is it necessary to enable some sort of handshaking in order to
    > establish receive-only communications with the BS2? (Any tips or
    > examples appreciated!)
    >
    > Thanks!
    >
    >
    > To UNSUBSCRIBE, just send mail to:
    > basicstamps-unsubscribe@yahoogroups.com
    > from the same email address that you subscribed. Text in the Subject and
    Body of the message will be ignored.
    >
    >
    > Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
    >
    >
    >
  • ArchiverArchiver Posts: 46,084
    edited 2002-02-11 07:12
    The control is set for no handshaking. (I've tried the handshaking
    options as well but with no benefit.)

    Any thoughts re. a logical way to troubleshoot using the control?

    Thanks!
    --- In basicstamps@y..., <tony.wells@a...> wrote:
    > I've come across this before. Set the control for no handshaking.
    >
    > If you can see the data in the terminal windows or in
    Hypterterminal then
    > the data is there!
    >
    > Regards,
    >
    > Tony Wells
    >
    >
    Original Message
    > From: "donnmoidaho" <donnmo@l...>
    > To: <basicstamps@y...>
    > Sent: Monday, February 11, 2002 2:17 AM
    > Subject: [noparse][[/noparse]basicstamps] serial communications with BS2
    >
    >
    > > I'm attempting to intercept the serial data that comes back to the
    > > BS2 debug window that's supported by the Basic stamp editor
    (v1.3).
    > > I'm using the MSComm ActiveX control in VB6 pro.
    > >
    > > The BS2 debug window receives data with settings of 9600 baud,
    parity
    > > none, data bits 8. When I configure the MSComm control with these
    > > same parameters, I see no input. However, when I slow the baud
    rate
    > > down to 1200 baud (on the control), I can detect data
    transmissions
    > > at the same frequency as the debug window. However, the data
    received
    > > is bogus and the MSComm control detects an input buffer length of
    0
    > > bytes.
    > >
    > > Is it necessary to enable some sort of handshaking in order to
    > > establish receive-only communications with the BS2? (Any tips or
    > > examples appreciated!)
    > >
    > > Thanks!
    > >
    > >
    > > To UNSUBSCRIBE, just send mail to:
    > > basicstamps-unsubscribe@y...
    > > from the same email address that you subscribed. Text in the
    Subject and
    > Body of the message will be ignored.
    > >
    > >
    > > Your use of Yahoo! Groups is subject to
    http://docs.yahoo.com/info/terms/
    > >
    > >
    > >
  • ArchiverArchiver Posts: 46,084
    edited 2002-02-11 07:15
    I've checked the VB parameters and attempted various permutations and
    combinations but with no success.

    Do you remember anything unique about the behaviour of the control in
    the program that you'd written? (Were you receiving data through the
    OnComm event?) Any hints or tips re. a logical or methodical approach
    to debugging appreciated.

    Thanks!

    --- In basicstamps@y..., Brian Gracia <bgracia@t...> wrote:
    > It is not necessary to setup any handshaking. I did this a while
    back and
    > used a VB6 program I wrote. I cannot remember specifics as it was
    about
    > 1yr ago, sorry. Check your parameters again in the VB program.
    Sounds
    > like you have something configured incorrectly.
    >
    > Brian
  • ArchiverArchiver Posts: 46,084
    edited 2002-02-11 09:45
    I confess I can't remember the control settings but I suggest the following
    /questions diagnostics which I would do when interfacing any PC to a device.

    1. Does the program definately output data to the stamp terminal window?

    2. Can you see the same output in Hyperterminal?

    3. If you unplug the cable can you still see data coming out of the stamp on
    the TX pin?

    If the answer to all three questions is yes, then it must be the
    control/your program. If so, can you let us have sight of your VB code - I
    might be able to spot something.

    Regards,

    Tony Wells
    Original Message
    From: "donnmoidaho" <donnmo@l...>
    To: <basicstamps@yahoogroups.com>
    Sent: Monday, February 11, 2002 7:15 AM
    Subject: [noparse][[/noparse]basicstamps] Re: serial communications with BS2


    > I've checked the VB parameters and attempted various permutations and
    > combinations but with no success.
    >
    > Do you remember anything unique about the behaviour of the control in
    > the program that you'd written? (Were you receiving data through the
    > OnComm event?) Any hints or tips re. a logical or methodical approach
    > to debugging appreciated.
    >
    > Thanks!
    >
    > --- In basicstamps@y..., Brian Gracia <bgracia@t...> wrote:
    > > It is not necessary to setup any handshaking. I did this a while
    > back and
    > > used a VB6 program I wrote. I cannot remember specifics as it was
    > about
    > > 1yr ago, sorry. Check your parameters again in the VB program.
    > Sounds
    > > like you have something configured incorrectly.
    > >
    > > Brian
    >
    >
    > To UNSUBSCRIBE, just send mail to:
    > basicstamps-unsubscribe@yahoogroups.com
    > from the same email address that you subscribed. Text in the Subject and
    Body of the message will be ignored.
    >
    >
    > Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
    >
    >
    >
  • ArchiverArchiver Posts: 46,084
    edited 2002-02-11 13:45
    From: "donnmoidaho" <donnmo@l...>

    > I've checked the VB parameters and attempted various permutations
    and
    > combinations but with no success.
    >
    > Do you remember anything unique about the behaviour of the control
    in
    > the program that you'd written? (Were you receiving data through the
    > OnComm event?) Any hints or tips re. a logical or methodical
    approach
    > to debugging appreciated.

    Try deleting the communication control off of the form and putting a
    "fresh" copy on with the parameters set to no handshaking. I've
    written several VB6 apps with serial port stuff and this cured a
    problem I had with one of them.

    Good luck,

    Tim
  • ArchiverArchiver Posts: 46,084
    edited 2002-02-11 19:57
    If you haven't done so already, check the 'input mode' property. The VB6
    documentation says that it applies only to input, but it also specifies what
    may be applied to output. You need this set to 1 for binary or 0 for text.

    Chris


    I'm attempting to intercept the serial data that comes back to the
    BS2 debug window that's supported by the Basic stamp editor (v1.3).
    I'm using the MSComm ActiveX control in VB6 pro.

    The BS2 debug window receives data with settings of 9600 baud, parity
    none, data bits 8. When I configure the MSComm control with these
    same parameters, I see no input. However, when I slow the baud rate
    down to 1200 baud (on the control), I can detect data transmissions
    at the same frequency as the debug window. However, the data received
    is bogus and the MSComm control detects an input buffer length of 0
    bytes.

    Is it necessary to enable some sort of handshaking in order to
    establish receive-only communications with the BS2? (Any tips or
    examples appreciated!)

    Thanks!
Sign In or Register to comment.