Clock Out Signal

[KeithH]

My first dabble in PIC programming was to create a Serial circuit with multiple PIC16F84A chips. I chained the PICs together and sent the same Serial Out data to every chip. I was able to light up any LED on PortA of any slave chip from one driver PIC using serout/serin.

I am now trying to send data to a bunch of 74HC4094 Shift registers instead.

I have not written any code as yet as I am trying to work out which pins to connect. the only one I am not sure about is how I get a clock signal from the PIC16F84A chip to provide the CK clock for the shift register. I have heared mention of using RA3 which has a real time clock connection or RA6 as it is used for serial programming (of the PIC I think though) or do i connect to the ClockOUT OCS2 pin as this is being used by my 4Mhz crystal....

Any ideas. Thanks in advance.

[skimask]

My first dabble in PIC programming was to create a Serial circuit with multiple PIC16F84A chips. I chained the PICs together and sent the same Serial Out data to every chip. I was able to light up any LED on PortA of any slave chip from one driver PIC using serout/serin.

I am now trying to send data to a bunch of 74HC4094 Shift registers instead.

I have not written any code as yet as I am trying to work out which pins to connect. the only one I am not sure about is how I get a clock signal from the PIC16F84A chip to provide the CK clock for the shift register. I have heared mention of using RA3 which has a real time clock connection or RA6 as it is used for serial programming (of the PIC I think though) or do i connect to the ClockOUT OCS2 pin as this is being used by my 4Mhz crystal....

Any ideas. Thanks in advance.

If you use OSC2 as an output, you won't have any control over it. It'll just run and run and run whether or not you've got data to shift or not.
Use SHIFTOUT. That way you can define both your clock and your data pin and have complete control over what they do, when they do it, and how they do it, and you can latch and enable the outputs with seperate pins on top of that. See the green book - section 5.76

[KeithH]

Use SHIFTOUT........ See the green book - section 5.76

It seems my green book is infact a light blue book.... so I don not have a section 5.76 nor the SHIFTOUT function. I only have SEROUT.

Has any one been able to drive a shift register (e.g. 74HC4094) from tha PIC chip using PicBasic? i.e. not PicBasic Pro?

I am not opposed to using Assembler or a.n.other compiler if needed, though I guess it is not something I can ask for recommendations here? I can't afford the extra £130 to get the pro compiler, even assuming I could trade it in that is. I wouldn't even know if I could get something to work with my EPIC programmer.

[dhouston]

MELabs has sample programs on their website for both PBP and PB.

• http://www.melabs.com/resources/samples.htm

There's one for ShiftIn/ShiftOut with PicBasic.

• http://www.melabs.com/resources/samples/pbc/shift.bas

[KeithH]

Thanks Dave and SKIMASK for your help. Things that may seem obvious once you know they are there are not easy to find without a little help.

I had already looked at shift.bas but wast not sure if shiftout was the correct method to start with.

Will there be much of an overhead using the shift.bas Shiftout function over the SHIFTOUT function in PBP?

[dhouston]

Will there be much of an overhead using the shift.bas Shiftout function over the SHIFTOUT function in PBP?

I've never tried to compare them in this way but my guess would be that PBP is slightly more efficient. However, this is a pretty simple operation so I doubt there's a huge difference. The real question is whether it, along with your other code, fits in the memory available.

[skimask]

I had already looked at shift.bas but wast not sure if shiftout was the correct method to start with.
Will there be much of an overhead using the shift.bas Shiftout function over the SHIFTOUT function in PBP?

I'd be willing to bet that the compiled SHIFTOUT command looks very similar to the shift.bas program, from a functional standpoint anyways (probably won't have the same labels, jumps, etc., but the flow would be almost identical).
As far as overhead goes, yes, there's overhead. 'cause when you're doing the shiftout, that's all your doing, is shifting out. You can't do anything else (unless you've got interrupts going for you).