Repost of PSC Question]
Archiver
Posts: 46,084
As requested, here's the reposting of my PSC question. I've ordered a
couple to try out since the posting and they are in transit as I write.
So an answer now would be very timely [noparse]:)[/noparse]
Andy
>>>
I very much like the idea of the PSC and looked up the spec which says
it works by accepting multi-byte sequence serial commands. However I
have a coupla dumb questions.
I presume these are "async" data bytes, with start and stop bits? If
so, is there any need to send the commands as a continuous stream of
bytes, or can the bytes be entered individually (e.g. from a terminal
keyboard or similar {at the correct TTL levels of course} for say
manual off-cpu testing)
with long delays of up to several seconds between bytes. Again, if yes,
is there any form of "time-out" which cancels a command if the delay is
too long? What happens if a command is sent to a different
device/address before a command sequence is completed?
Andy
couple to try out since the posting and they are in transit as I write.
So an answer now would be very timely [noparse]:)[/noparse]
Andy
>>>
I very much like the idea of the PSC and looked up the spec which says
it works by accepting multi-byte sequence serial commands. However I
have a coupla dumb questions.
I presume these are "async" data bytes, with start and stop bits? If
so, is there any need to send the commands as a continuous stream of
bytes, or can the bytes be entered individually (e.g. from a terminal
keyboard or similar {at the correct TTL levels of course} for say
manual off-cpu testing)
with long delays of up to several seconds between bytes. Again, if yes,
is there any form of "time-out" which cancels a command if the delay is
too long? What happens if a command is sent to a different
device/address before a command sequence is completed?
Andy
Comments
to deal with is
-- level (RS-232 to TTL for the PSC)
-- sending numeric values
There are ASCII characters in the command string, but there are numeric
values as well and sending them from a standard terminal program is not
really very practical (anything below 32 [noparse][[/noparse]space] or above 127). It
might be easier to send commands to a BASIC Stamp which them translates
and passes them on to the PSC.
-- Jon Williams
-- Applications Engineer, Parallax
-- Dallas Office
Original Message
From: Andy Reichert [noparse]/noparse]mailto:[url=http://forums.parallaxinc.com/group/basicstamps/post?postID=XKlrtkMUW2dV7HQh3a1pGLdoj7eRA-uu4kMaEbo7SYr50yifORuFoNUsispRBPlpoOSqz6OOG7X8E7HEiw]andy_r@i...[/url
Sent: Thursday, April 22, 2004 3:04 PM
To: basicstamps@yahoogroups.com
Subject: [noparse][[/noparse]basicstamps] Repost of PSC Question]
As requested, here's the reposting of my PSC question. I've ordered a
couple to try out since the posting and they are in transit as I write.
So an answer now would be very timely [noparse]:)[/noparse]
Andy
>>>
I very much like the idea of the PSC and looked up the spec which says
it works by accepting multi-byte sequence serial commands. However I
have a coupla dumb questions.
I presume these are "async" data bytes, with start and stop bits? If
so, is there any need to send the commands as a continuous stream of
bytes, or can the bytes be entered individually (e.g. from a terminal
keyboard or similar {at the correct TTL levels of course} for say
manual off-cpu testing) with long delays of up to several seconds
between bytes. Again, if yes, is there any form of "time-out" which
cancels a command if the delay is too long? What happens if a command
is sent to a different device/address before a command sequence is
completed?
Andy