the oSerailL object to pin 31. Don't I need some type of converter to
connect the TTL - level IO to a real RS232 port?
-GeorgeOrr
--- In oopic@yahoogroups.com, ooPIC Tech Support <dennis.clark@...> wrote:
>
> Have you tried connecting up directly to your PC and using a terminal
> emulator like Hyperterm or Teraterm? I use the object all the time and
> it works fine. Also - You are not sending the ASCII values you are
> sending the binary value of "31" with what you are doing there.
>
> DLC
>
> design.wonk wrote:
> > I only have to send. I am trying to control a Daisy MP3 player (open
> > source kit from Make Magazine) with the ooPIC using the Daisy's Simple
> > Serial Mode (see below). According to the docs for both devices, the
> > only thing I should have to do select track 1 would be something like:
> >
> > oSerialL MP3 = New oSerialL;
> >
> > // Init Values
> >
> > MP3.IOLineS = 31;
> > MP3.Baud = cv9600;
> >
> > Void main(Void){
> >
> > MP3.Value = 1;
> >
> > }
> >
> >
> > I an not sure if I am missing something.
> >
> >
> > Here is what the Daisy is looking for....
> >
> > SIMPLE SERIAL MODE
> > Jumpers: X only
> >
> > In this mode the player accepts one byte at a time over the serial
> > port, and depending on the
> > value of the byte will perform certain operations. The bytes are not
> > ascii, they are just pure
> > bytes. So sending an ascii "0" is actually sending a 0x30 (decimal
> > 48). Be careful in your code!
> >
> > If the byte is 0 to 180, it will play track 0 to 180.
> > If the byte is 192 to 255, it will set the volume.
> > Value 184 toggles pause on and off.
> > Value 183 turns looping mode on.
> > Value 182 turns looping mode off.
> > Value 181 is a kind of reset. It kills the present song and sets it to
> > "not pausing" mode.
> >
> >
> > --- In oopic@yahoogroups.com, "dan michaels" <oric_dan@> wrote:
> >
> >> --- In oopic@yahoogroups.com, "design.wonk" <design.wonk@> wrote:
> >>
> >> I believe oSerialL is the same as oSerialX on the previous versions
> >> of the oopic firmware, and it has some serious problems with use
> >> on "receive". Transmit works ok, but forget about using receive,
> >> unless hardware handshaking is employed.
> >>
> >> Dennis, this didn't get fixed on the new firmware, did it?
> >>
> >>
> >>
> >>
> >>
> >>> I am trying to use the oSerialL to communicate with a another
> >>>
> >> device, but don't understand the results that I am getting. In
doing
> >> dome debugging, it seems that the value of the oSerialL object is
all
> >> over the place, even if it is not attached to anything. If I do
> >> something like:
> >>
> >>> oSerialL MP3 = New oSerialL;
> >>>
> >>>
> >>> // Init Values
> >>>
> >>> MP3.IOLineS = 31;
> >>> MP3.Baud = cv9600;
> >>>
> >>> ...
> >>>
> >>> when I run this and open a dialog box, the value of the oSerialL
> >>> object constantly changes, even if nothing is attached to line 31.
> >>> What am I missing? If no data is being transmitted or received,
> >>> shouldn't the value of the object remain 0?
> >>>
> >>> thanks
> >>>
> >>>
> >
> >
> >
> > ------------------------------------
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> >
> >
>
> --
> ------------------------------------------------------
> Dennis Clark ooPIC Tech Support
> www.oopic.com
> ------------------------------------------------------
>
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/oopic/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/oopic/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:oopic-digest@yahoogroups.com
mailto:oopic-fullfeatured@yahoogroups.com
<*> To unsubscribe from this group, send an email to:
oopic-unsubscribe@yahoogroups.com
<*> Your use of Yahoo! Groups is subject to:
No comments:
Post a Comment