Thread: Dashboard Port Decoder
View Single Post
  #32   Spotlight this post!  
Unread 03-03-2006, 23:05
whytheheckme's Avatar
whytheheckme whytheheckme is offline
Registered User
AKA: Jacob Komar
no team
  
Join Date: Feb 2006
Rookie Year: 2005
Location: Providence, RI
Posts: 1,320
whytheheckme has a reputation beyond reputewhytheheckme has a reputation beyond reputewhytheheckme has a reputation beyond reputewhytheheckme has a reputation beyond reputewhytheheckme has a reputation beyond reputewhytheheckme has a reputation beyond reputewhytheheckme has a reputation beyond reputewhytheheckme has a reputation beyond reputewhytheheckme has a reputation beyond reputewhytheheckme has a reputation beyond reputewhytheheckme has a reputation beyond repute
Send a message via ICQ to whytheheckme Send a message via AIM to whytheheckme Send a message via MSN to whytheheckme Send a message via Yahoo to whytheheckme
Re: Dashboard Port Decoder
After a day's work on this, this is how far I got.

The Basic Stamp can see the dashboard port, because it doesn't get hung on the 255,255. My problem now is capturing the correct packets. Do I need to name the input varibles the same as they are in the specification sheet? Even if they do, the one that I care about, Switches_A, doesn't pass bit0, which is just p1_trig. Does anyone see any syntax errors?

Just remove the .txt at the end of the file name to get the bs2.

Jacob Komar
Attached Files
File Type: txt innew3.bs2.txt (1.4 KB, 23 views)