Shop OBEX P1 Docs P2 Docs Learn Events
How to make basic stamp 2 codes and labview 8 under stand each other? — Parallax Forums

How to make basic stamp 2 codes and labview 8 under stand each other?

isador85isador85 Posts: 2
edited 2008-01-12 21:59 in BASIC Stamp
I'm a student, currently doing my final proj. I'm doing a vision controlled robot using Labview 8 which control its movements and vision.Basic Stamp 2 is the program·the motor movement which have the transmitter and receiver part that is going to be link to labview 8.

This was given to us by our teacher. I hv run the transmitter and receiver program for basic stamp2.
However, when i run the Labview part, the motor did not move to desired directions, Forward, backward,right,left, only can exit the program.When our teacher ran the program to demonstrate to us in his lab it was fine but when we ran it in our lab, it failed. This was the original program that·we ran.We modified programs too but preserving the original one.


Please do check the ·files that i attached.Maybe you can help me as well as others.It 's 7 wks left to my dateline but can be extended desperately nd the solution or suggestion from u ppl.I will attached some more files·in future.Pls·help me.·jumpin.gif
·

attachment.php?attachmentid=73734
File Attachment :
DYNAMIC_PRJ[noparse][[/noparse]1].doc · 76KB (application/octet-stream) This file has been downloaded 6 time(s).

File Attachment :
TP-omnirobot-reciever original.bs2.doc · 26KB (application/octet-stream) This file has been downloaded 7 time(s).

File Attachment :
'TP-omnirobot-transmitter original.BS2.doc · 26KB (application/octet-stream) This file has been downloaded 4 time(s).
p700776-1.gif
35B

Comments

  • FranklinFranklin Posts: 4,747
    edited 2008-01-11 03:57
    Didn't you ask this same question yesterday? What did people say to the other question? ATTACH your code directly from the bs2 file so if someone would want to they could load it into the editor.

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    - Stephen
  • Chris SavageChris Savage Parallax Engineering Posts: 14,406
    edited 2008-01-11 20:48
    Franklin said...
    Didn't you ask this same question yesterday? What did people say to the other question? ATTACH your code directly from the bs2 file so if someone would want to they could load it into the editor.
    The duplicate posts were removed...Please follow up on your question in this thread.

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    Chris Savage
    Parallax Tech Support
  • Shawn LoweShawn Lowe Posts: 635
    edited 2008-01-12 15:22
    My suggestion would be isolate each part of the project. Start with the BS program, and verify it works. Since the labview program worked for your teacher, it may just be a communications problem, but you wont know if you don't verify the Basic stamp portion.

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    Shawn Lowe


    Maybe I should have waited to do that......
  • Bruce BatesBruce Bates Posts: 3,045
    edited 2008-01-12 15:52
    isador85 -

    All I can offer are generalizations and recollections from others who have had difficulties making Labview and PBASIC "talk" to one another. I know nothing about Labview.

    First, as I remember, there are certain Labview routines, subroutines, drivers, or whatever they are called, which must be included in your Labview package to permit asynchronous serial communication. This is the ONLY way that Labview can successfully "speak" to a PBASIC Stamp.

    Second, since Labview would seem to be the "host" in this arrangement, you will have to ensure that whatever baud rate and communication parameters (parity, bits, etc.) that are used by Labview are incorporated in the BAUDMODE used in the PBASIC program. Failure to do this will bring the entire project to an abrupt HALT.

    Third, over time I've noticed that most difficulties seemed to have been at the Labview end, and since you were provided with the PBASIC programs, that would lend some credence to this line of thinking. About the only things I can imagine which might change in the PBASIC program(s) are the pin port assignments. Thus, I'd investigate the Labview end before I spent too much time on the PBASIC end.

    Finally, by placing the following as the beginning statement of each of the PBASIC programs, you will know if they are even being entered. I'm not sure you have that assurance now. If these DEBUG (test) messages are NOT displayed, then you know for sure that you need to look at the Labview end, since the PBASIC programs are not even beginning execution.

    In the transmitter program:

    DEBUG "Tx Entered"

    In the receiver program:

    DEBUG "Rx Entered"

    Try those suggestions, and let us know how you make out.

    Regards,

    Bruce Bates

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
  • KatyBriKatyBri Posts: 171
    edited 2008-01-12 21:59
    When I was working, I built several large laboratory testing systems using LabView and microprocessors. During the development stages of these projects, if I had problems, it was usually do to incorrect communications settings or incorrect cabling.

    The nice part of LabView is·it is self-contained and does not depend upon resources on the target machine, and creates the code for you. The own side it is expensive.
Sign In or Register to comment.