Shop OBEX P1 Docs P2 Docs Learn Events
Say It Module GUI/Comm - not connecting. — Parallax Forums

Say It Module GUI/Comm - not connecting.

xanatosxanatos Posts: 1,120
edited 2010-04-19 00:10 in General Discussion
The GUI cannot see the Board of Education with the Say It module in it.· The response on connection attempts is:

"Could not detect device connected to "COM5".
The operation completed successfully"

If I start up the Stamp Editor V2.4.2 and Run > Identify on COM5 it sees the stamp just fine, and I can load code to it.· I quit the editor and retry the Say It GUI and get the same error message again.

I am running Windows XP SP3 on a Sony Vaio.· I have verified that no terminal windows or other serial-port hogging programs are running.· I have verified voltage and available current at the supply, and measured voltage actually at the Vss/Vdd pins; I have verified that the proper pin insertion exists on the BoE board's X1 header (looks exactly like the photo in the SI Module's PDF manual).· I have nothing else connected to the stamp (and remember that the Stamp Editor DOES see the stamp on COM5).· I have tried selecting the other listed COM ports (4 and 3) and get the same results.· I have cycled power to the board and quit/restarted the GUI.

I have exhausted all options I am aware of at the moment.· Has anyone on here successfully connected from a WinXP machine?

Lastly - if the USB to Serial converter I am using for the stamp editor works just fine there, is there any chance that it would not work on the Say It GUI for some reason?· Is there some difference in the communication protocol?

Thanks for any info - anxious to get the Say It module listening soon!

Dave


·

Comments

  • FranklinFranklin Posts: 4,747
    edited 2009-08-29 04:51
    What do you have programed in the stamp? Could you attach that code here?

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    - Stephen
  • xanatosxanatos Posts: 1,120
    edited 2009-08-29 13:19
    I've tried several things, although, like the editor, it does not make any difference what is in the stamp in order for the editor to see the serial connection to the stamp. Despite this I have loaded the code for programming the Say It module, a blank template, and even a quick code I wrote setting all the pins to inputs just to be sure. And as I suspected, none made any difference. The issue seems to be that the GUI simply cannot see the connection to the stamp, or cannot see the stamp itself, but the stamp code editor, using the exact same physical hardware, can and does, just fine. I even tried a different BS2 just for the heck of it... Same results. I believe, at this point, anyway, that either there is a problem with the GUI, or that there exists an incompatibility between the GUI and windows XP on my system. I also am thinking that since this is brand new, and probably only a handful have been sold so far, that not a lot of people on here have actually got hands-on experience with this item, so I may be SOL for a while...

    Thanks for any ideas.

    Dave
  • WhitWhit Posts: 4,191
    edited 2009-08-30 12:28
    Dave,

    Luckily you are only out of luck until Parallax is open on Monday - I know Tech Support can give you a hand.

    You are probably right about most folks not having any experience with this - unless maybe Mike Green, PhiPi or Beau have played with it.

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    Whit+


    "We keep moving forward, opening new doors, and doing new things, because we're curious and curiosity keeps leading us down new paths." - Walt Disney
  • xanatosxanatos Posts: 1,120
    edited 2009-08-31 18:47
    I'm travelling today, but yes, you're right... I'm just so NOT in the habit of relying on tech support that I actually don't even think of it as an option unless someone, like you, reminds me!!! smile.gif the one experience I have had with Parallax TS was excellent, which is in stark contrast with most all other tech support in which I so often discover that their TS people don't know anything more than what was on their website... usually less! Parallax offers so much on their site and this forum that those are usually the only places I ever need to go! But thanks for reminding me about Parallax TS - they really ARE good.

    Dave
  • btshil2000btshil2000 Posts: 3
    edited 2009-09-11 10:58
    Hi,
    I am experiencing the same connection issues (and error message) on a Windows Vista PC and Windows 7 PC.
    I am also unable to make the Basic Stamp code work. It is as if the Stamp and/or PC is completely unaware of the Say It Module.
    The red LED never comes on.

    Has anyone been able to troubleshoot or workaround the issue?
    Thanks.

    BT

    Post Edited (btshil2000) : 9/12/2009 2:58:58 AM GMT
  • JDJD Posts: 570
    edited 2009-09-17 15:22
    Xanatos,

    Can you confirm which BASIC Stamp 2 you are using with the GUI?

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    Respectfully,


    Joshua Donelson
    www.parallax.com
  • xanatosxanatos Posts: 1,120
    edited 2009-09-17 16:38
    Hi there,

    Still travelling so I don't have my full compliment of hardware resources - but I do have the development environment with me! It's like American Express - I never leave home w/o it! smile.gif

    I have tried with both a regular BS2 and a BS2SX (and the demo code worked on both when loaded in with the stamp editor - and with the stamp-appropriate mods to the code) but the GUI works with neither. I also loaded the GUI on a second computer and obtained identical results.

    I won't be able to do a lot of testing until I return from my travels, but I can do some simple stuff if you need, as I do have my USB2Ser cable, the dev board and power supply, and of course, my laptop.

    Dave
  • Mike2545Mike2545 Posts: 433
    edited 2009-10-16 02:01
    I am having the same issue. Did you get yours to work?

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    Mike2545

    This message sent to you on 100% recycled electrons.
  • xanatosxanatos Posts: 1,120
    edited 2009-10-16 21:41
    Hi,



    Nothing yet.· I heard from a tech on this a few times, but I was travelling all over teh place and hadn't the real time or proper stuff to test any of the things he asked me to.· Basically the only thing I've heard from anyone is one guy who dug up some ancient old tower he had with a serial port card in it, and that worked.· Other than that, I know of at least three other folks who have been unable to get the programming GUI to work.· The unit DOES run the demo program which loads just fine with the Basic Stamp editor, but the GUI seems DOA from everything I've observed so far.· I'm really VERY surprised that this is happening - Parallax has always had some outstanding products that have worked (for me, anyway) FLAWLESSLY every time.· Let me know if you find anything.

    Dave
  • Mike2545Mike2545 Posts: 433
    edited 2009-10-16 22:14
    The demo program I am using does not work for me...

    ' {$STAMP BS2}
' {$PBASIC 2.5}

' COM Parameters
COM_RX              PIN   0   ' rx pin
COM_TX              PIN   2   ' tx pin
COM_SPEED           CON   84  ' baud 9600

' Protocol Command
CMD_BREAK           CON   "b" ' abort recog or ping
CMD_SLEEP           CON   "s" ' go to power down
CMD_KNOB            CON   "k" ' set si knob <1>
CMD_LEVEL           CON   "v" ' set sd level <1>
CMD_LANGUAGE        CON   "l" ' set si language <1>
CMD_TIMEOUT         CON   "o" ' set timeout <1>
CMD_RECOG_SI        CON   "i" ' do si recog from ws <1>
CMD_RECOG_SD        CON   "d" ' do sd recog at group <1> (0 = trigger mixed si/sd)

' Protocol Status
STS_AWAKEN          CON   "w" ' back from power down mode
STS_ERROR           CON   "e" ' signal error code <1-2>
STS_INVALID         CON   "v" ' invalid command or argument
STS_TIMEOUT         CON   "t" ' timeout expired
STS_INTERR          CON   "i" ' back from aborted recognition (see 'break')
STS_SUCCESS         CON   "o" ' no errors status
STS_RESULT          CON   "r" ' recognised sd command <1> - training similar to sd <1>
STS_SIMILAR         CON   "s" ' recognised si <1> (in mixed si/sd) - training similar to si <1>

' Protocol arguments are in the range 0x40 (-1) TO 0x60 (+31) inclusive
ARG_MIN             CON   64 ' 0x40
ARG_MAX             CON   96 ' 0x60
ARG_ZERO            CON   65 ' 0x41

ARG_ACK             CON   32 ' 0x20    'TO READ more status arguments

'Groups and Commands
'§G >
'§G + GROUP_%2!-2d!            CON   %2!d!    '(Command count: %3!d!)
'§C >
'§C + G%2!d!_%4!-32s! CON   %5!d!
'§C ^ %0
'§G ^

RES_ERROR           CON 255
RES_TIMEOUT         CON 254
RES_COMMFAIL        CON 253
RES_BUILTIN         CON 32


'Robot Constant

VRLED               PIN   4

'Global Variable

VRA                 VAR   Byte
VRA1                VAR   Byte
VRGROUP             VAR   Byte
VRCOMMAND           VAR   Byte

' Main Start
Restart:
  LOW VRLED
  VRGROUP = 0

  DEBUG CR, "Setting up VRbot... "
  'Wake up or stop recognition
  GOSUB VR_Wakeup
  DEBUG "awake... "

  'Set SI Language
'§L :   VRA1 = %1!d!
  GOSUB VR_SetLanguage
  DEBUG "language ", DEC VRA1, "... "

  'Set 5 seconds timeout
  VRA1 = 5
  GOSUB VR_SetTimeout
  DEBUG "timeout ", DEC VRA1, "... "

  DEBUG CR, "VRbot ready!"

VR_Loop:
  DEBUG CR, "VRbot in group ", DEC VRGROUP, " waiting for command... "
  LOW VRLED
  PAUSE 150
  IF VRGROUP > 0 THEN HIGH VRLED
  VRA1 = VRGROUP
  GOSUB VR_RecognizeSD
  '-- handle errors or timeout
  IF VRA1 = RES_ERROR THEN
    DEBUG "error"
    'try again in the same group
    GOTO VR_Loop
  ENDIF
  IF VRA1 = RES_TIMEOUT THEN
    DEBUG "timed out"
    VRGROUP = 0 ' back to trigger
    GOTO VR_Loop
  ENDIF
  IF VRA1 = RES_COMMFAIL THEN
    DEBUG "comm failed"
    'resync and try again
    GOSUB VR_Wakeup
    GOTO VR_Loop
  ENDIF
  '-- got a command
  VRCOMMAND = VRA1

  IF VRCOMMAND <= RES_BUILTIN THEN GOSUB VR_Action
  GOTO VR_Loop

VR_Action:
  DEBUG "got ", DEC VRCOMMAND
'§G >   SELECT VRGROUP
'§G :
'§G +     CASE GROUP_%2!d!
'§C >       SELECT VRCOMMAND
'§C +         CASE G%2!d!_%4!s!
'§C :          PAUSE 0 '-- write your code here
'§C ^ %0
'§G ^       ENDSELECT
'§G >   ENDSELECT
  RETURN

'=== VR Routines ===

' Wake up:
VR_Wakeup:
  TOGGLE VRLED
  VRA = CMD_BREAK
  SEROUT COM_TX, COM_SPEED, [noparse][[/noparse]VRA]
  SERIN COM_RX, COM_SPEED, 1000, VR_Wakeup, [noparse][[/noparse]VRA]
  IF (VRA <> STS_SUCCESS) THEN GOTO VR_Wakeup
  LOW VRLED
  RETURN

' Inputs:
'   VRA1 = language index (0 = english, ...)
VR_SetLanguage:
  VRA = CMD_LANGUAGE
  SEROUT COM_TX, COM_SPEED, [noparse][[/noparse]VRA]
  VRA1 = VRA1 + ARG_ZERO
  SEROUT COM_TX, COM_SPEED, [noparse][[/noparse]VRA1]
  SERIN COM_RX, COM_SPEED, 200, VR_CommFailed, [noparse][[/noparse]VRA]
  VRA1 = VRA1 - ARG_ZERO
  'IF (VRA <> STS_SUCCESS) THEN GOTO VR_Wakeup
  RETURN

' Inputs:
'   VRA1 = timeout (in ms, 0=forever, 255=default)
VR_SetTimeout:
  VRA = CMD_TIMEOUT
  SEROUT COM_TX, COM_SPEED, [noparse][[/noparse]VRA]
  VRA1 = VRA1 + ARG_ZERO
  SEROUT COM_TX, COM_SPEED, [noparse][[/noparse]VRA1]
  SERIN COM_RX, COM_SPEED, 200, VR_CommFailed, [noparse][[/noparse]VRA]
  VRA1 = VRA1 - ARG_ZERO
  'IF (VRA <> STS_SUCCESS) THEN GOTO VR_Wakeup
  RETURN

' Inputs:
'   VRA1 = SI knob (0=loosest, 2=normal, 4=tightest)
VR_SetKnob:
  VRA = CMD_KNOB
  SEROUT COM_TX, COM_SPEED, [noparse][[/noparse]VRA]
  VRA1 = VRA1 + ARG_ZERO
  SEROUT COM_TX, COM_SPEED, [noparse][[/noparse]VRA1]
  SERIN COM_RX, COM_SPEED, 200, VR_CommFailed, [noparse][[/noparse]VRA]
  VRA1 = VRA1 - ARG_ZERO
  'IF (VRA <> STS_SUCCESS) THEN GOTO VR_Wakeup
  RETURN

' Inputs:
'   VRA1 = SD level (1=easy, 2=default, 5=hard)
VR_SetLevel:
  VRA = CMD_LEVEL
  SEROUT COM_TX, COM_SPEED, [noparse][[/noparse]VRA]
  VRA1 = VRA1 + ARG_ZERO
  SEROUT COM_TX, COM_SPEED, [noparse][[/noparse]VRA1]
  SERIN COM_RX, COM_SPEED, 200, VR_CommFailed, [noparse][[/noparse]VRA]
  VRA1 = VRA1 - ARG_ZERO
  'IF (VRA <> STS_SUCCESS) THEN GOTO VR_Wakeup
  RETURN

' Inputs:
'   VRA1 = wordset (0=trigger)
' Ouputs:
'   VRA1 = result (0-31=word, 32..=builtin, 253=comm err, 254=timeout, 255=error)
VR_RecognizeSI:
  VRA = CMD_RECOG_SI
  GOTO VR_Recognize0
VR_RecognizeSD:
  VRA = CMD_RECOG_SD
VR_Recognize0:
  SEROUT COM_TX, COM_SPEED, [noparse][[/noparse]VRA]
  ' send Group/WS
  VRA1 = VRA1 + ARG_ZERO
  SEROUT COM_TX, COM_SPEED, [noparse][[/noparse]VRA1]
  ' wait for answer
  SERIN COM_RX, COM_SPEED, 6000, VR_CommFailed, [noparse][[/noparse]VRA]
  IF VRA = STS_RESULT THEN
    ' send ack
    VRA = ARG_ACK
    SEROUT COM_TX, COM_SPEED, [noparse][[/noparse]VRA]
    ' wait for recognised command code
    SERIN COM_RX, COM_SPEED, 200, VR_CommFailed, [noparse][[/noparse]VRA1]
    VRA1 = VRA1 - ARG_ZERO
  ELSEIF VRA = STS_SIMILAR THEN
    ' send ack
    VRA = ARG_ACK
    SEROUT COM_TX, COM_SPEED, [noparse][[/noparse]VRA]
    ' wait for recognised command code
    SERIN COM_RX, COM_SPEED, 200, VR_CommFailed, [noparse][[/noparse]VRA1]
    VRA1 = VRA1 - ARG_ZERO + RES_BUILTIN
  ELSEIF VRA = STS_TIMEOUT THEN
    VRA1 = RES_TIMEOUT
  ELSE
    VRA1 = RES_ERROR
  ENDIF
  RETURN

VR_CommFailed:
  VRA1 = RES_COMMFAIL
  RETURN



    It gets to DEBUG CR, "Setting up VRbot... "
    and flashes the LED on the Sat it module...any ideas??

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    Mike2545

    This message sent to you on 100% recycled electrons.
  • Mike2545Mike2545 Posts: 433
    edited 2009-10-17 13:26
    I got the module to respond well to the program, and switched from a serial cable on a USB/Serial hub to a serial port on the computer, now I get the "Could Not Enter Control Mode" error. I don't see that in the troubleshooting guide...

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    Mike2545

    This message sent to you on 100% recycled electrons.
  • Mike2545Mike2545 Posts: 433
    edited 2009-10-19 23:57
    Any thoughts on how to get it to enter the control mode? I have tried contacting Joshua Donelson with no help from tech support on this one other than "Check your power supply." Which I have done, thank you Josh.

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    Mike2545

    This message sent to you on 100% recycled electrons.
  • xanatosxanatos Posts: 1,120
    edited 2009-10-20 00:24
    I have no clue - and haven't really had the time to work on it. I was pushing the possibility of voice control for a project I am doing for a client, but given the current status of this item, I've abandoned that push until a product becomes available somewhere that actually works (and is cost effective, unlike the VR Stamp). When/if I start trying to get this item to work again, I'll be sure to post, but until then I'm pretty much writing this item off as a no go. I have not seen any burning desire on the part of Tech Support to get these things working either.

    Dave
  • AvzalothAvzaloth Posts: 1
    edited 2010-04-19 00:10
    Hi.

    I'm using the say it module and I had the same problem "could not enter control mode"...
    I got a similar problem with the ultrasonic sensor because the debug terminal did not recogniced it.
    Even I used other two laptops and the problem was the same.

    I only changed the pin I was using and my ultrasonic sensor worked normally. So just by changing the pins I was using my say it module worked normally.
    So I was wondering why these pins get "crazy" sometimes.


    Note. I'm using the board of education and the BS2.

    Angel Calder
Sign In or Register to comment.