BS2 and BSX in a TAB BYORK

Started by chicoisl July 29, 2004
Hello,

I am working with the TAB BYORK, I have both a BS2 and a BX24. I
have programmed the BS2 for use of the IR, CDS and motors through the
onboard PIC16C505. I would like to do the same with the BX24. I am
currently learning how to use the shiftin and shiftout functions with
the BX24 and my confusion lies with how to "talk" to the PIC505.
With the BS2 you "RobotSend" behavior1 to activate the IR's and
then "RobotSendRecieve" to get values back. Is the approach the same
for the BX24?

Any links, help, hints to resources concerning this issue would be
wonderful.
ThankYOU
MattB




MattB,

I looked at the schematics for your project. Looks
like the PIC16C505 acts as a slave microprocessor.
ShiftIn & ShiftOut occurs with pins 19 & 20.

I'm betting that "RobotSend" and "RobotSendRecieve"
are really subroutines. Based on what is sent out,
the PIC knows what to measure and sends it back. Note
that the programmed microcontroller (BS2 or BX24)
controls the rate with the clock pin.

Try a google on I2C (Inter Integrated Circuit) for
further explanation on this method of communication.
Note that the BasicX is MSB first, so you may need to
FlipBits if data is transfered LSB first for BS2.
Very important is how you define your clock pin BEFORE
you ShiftIn & ShiftOut. I am sure that it relates to
'pre' & 'post'...

On another note....

This board has been quiet since Frank Manning left. I
saw one mention of a BX24 Beta version. Other than
that, NetMedia has been unusually quiet.

What is going on out there? I realize that full
disclosure is not possible, but can you throw us a
bone?? i.e. (1) BasicX will be supported in it's
current form. (2) The new version is SOOO
state-of-the-art that NetMedia hasn't had time for
anything else.

Thanks,
Thad

--- chicoisl <> wrote:

> Hello,
>
> I am working with the TAB BYORK, I have both a BS2
> and a BX24. I
> have programmed the BS2 for use of the IR, CDS and
> motors through the
> onboard PIC16C505. I would like to do the same with
> the BX24. I am
> currently learning how to use the shiftin and
> shiftout functions with
> the BX24 and my confusion lies with how to "talk" to
> the PIC505.
> With the BS2 you "RobotSend" behavior1 to activate
> the IR's and
> then "RobotSendRecieve" to get values back. Is the
> approach the same
> for the BX24?
>
> Any links, help, hints to resources concerning this
> issue would be
> wonderful.
> ThankYOU
> MattB >
>


__________________________________




Thad,

Thankyou for your reply...

Yep, im using pin 19 as the clock and pin 20 as then data, these
are labeled SC and SC in the BYORK schematic.

Yep, in BS2 language robotsend and robotsendrecieve are indeed
subroutines that call the shiftin and shiftout commands. Inside
these routines the positition (high or low) of the clock pin is
defined and the when the pin changes form high to low the data is
read --This is the part I am having trouble duplicating in BX24
language.

Yep, i will need to flip the bits, the BX24's shiftout command sends
the Most Significant bit firs. --Its the 'pre' (samble before clock
pulse in BS2) and 'post' (sample before 2nd clock pulse in BS2) that
I dont know how to duplicate in BX24 language.

Check my newest post for some more thoughts on this subject.

Cheers
mattB > I looked at the schematics for your project. Looks
> like the PIC16C505 acts as a slave microprocessor.
> ShiftIn & ShiftOut occurs with pins 19 & 20.
>
> I'm betting that "RobotSend" and "RobotSendRecieve"
> are really subroutines. Based on what is sent out,
> the PIC knows what to measure and sends it back. Note
> that the programmed microcontroller (BS2 or BX24)
> controls the rate with the clock pin.
>
> Try a google on I2C (Inter Integrated Circuit) for
> further explanation on this method of communication.
> Note that the BasicX is MSB first, so you may need to
> FlipBits if data is transfered LSB first for BS2.
> Very important is how you define your clock pin BEFORE
> you ShiftIn & ShiftOut. I am sure that it relates to
> 'pre' & 'post'...
> Thanks,
> Thad
>