I have recently being messing around with shiftin and shiftout examples, but i was wondering how do you take the digiatal input readings (using 8 switches) from a 4021 (shiftin) to the arduio and shiftout (with a 595) to 8 leds?
I know for the shiftout i can get rid of the set binary values because i am wanting to output the values from the shiftin switches on the 4021. I am just not sure how to combine the 2 bits of code to be able to read each individual switch and shiftin and then shiftout to each individual LED.
The shiftin example code i have being using is:
int latchPin = 8;
int dataPin = 9;
int clockPin = 7;
void setup() {
Serial.begin(9600); // start serial
pinMode(latchPin, OUTPUT); // setup pin modes
pinMode(clockPin, OUTPUT);
pinMode(dataPin, INPUT);
}
void loop()
{
// Pulse the latch pin
digitalWrite(latchPin, HIGH);
delayMicroseconds(20);
digitalWrite(latchPin, LOW);
for (int i=0; i<8; i++)
{
// read data
delay(5);
int temp = digitalRead(dataPin);
Serial.print(temp);
// trigger next input (LOW -> HIGH)
digitalWrite(clockPin, HIGH);
delayMicroseconds(2);
digitalWrite(clockPin, LOW);
delayMicroseconds(2);
}
Serial.println();
delay(50);
}
Basically, once the ShiftIn has been carried out each bit of an 8 bit variable will hold a value corresponding to whether the associated button/switch was closed. That variable can be shifted out and the corresponding LED will be turned on. Is that what you are trying to do ?
yeah basically shifting in the 8bit switches and shifting out to 8bit Leds. I am just trying to understand how both work together and to minimise wires for a project later on eg. instead of having 8 wires for each individual bit i would have 3 for clock, latch and data etc. if that makes sense.
The principle really is simple. Read an 8 bit byte from 1 shift register and output it to a second one.
Like this switchVar1 = shiftIn(dataPin1, clockPin1);After that the variable switchVar1 holds the state of the buttons. ThenshiftOut(dataPin2, clockPin2, MSBFIRST, switchVar1);
I still don't really get this. There is that many examples of code out there they are all different and confusing as hell.
Its ok saying use this tutorial, i have probably seen them all but still can't get any further with simple stuff. There seems to be more on shifting out data to led examples but not so much on shifting in using hardware.
If shifting in is suppose to be as easy as the one in the reference, why is the tutorial code one big mess with having to include the shiftIn function at the bottom of the code? i know you need it to use the shiftin function its just messy and confusing
apologies for stressing out ha. It is kinda crazy when arduino has a massive online community yet i still find it difficult to
progress when tutorials work, yet its hard to relate it and modify to what you need.
I will give it a try in a bit and see how i get on.
Quite possibly, but that's the documentation in place on the official web site, still crap, just for a different reason.
Yeah I know it's a voluntary and community thing, nobody is getting paid to write documentation. But AFAIK there is nobody looking after this stuff and they will not delegate to people who may be willing to do so (if indeed anyone is :)). The "cap on the clock line" is a classic example, we've been on about that for years, it could be fixed in 5 minutes.
How many tutorials use Serial.flush() in the old way? How many tutorials use a constant of 5000 to get an analogue value when on a Due it should be 3300? And now I gather we're talking about a new analog API.
This will get worse as the libraries evolve and the board types increase.
This will get worse as the libraries evolve and the board types increase.
Or until they open the documentation up for a wider community to edit. SurferTim has been successful in getting some documentation corrected. But, I think he's bribing someone.
kh602:
I still don't really get this. There is that many examples of code out there they are all different and confusing as hell.
Its ok saying use this tutorial, i have probably seen them all but still can't get any further with simple stuff. There seems to be more on shifting out data to led examples but not so much on shifting in using hardware.
If shifting in is suppose to be as easy as the one in the reference, why is the tutorial code one big mess with having to include the shiftIn function at the bottom of the code? i know you need it to use the shiftin function its just messy and confusing
I wondered the exact same thing....
Shiftin/shiftout is all you really need, you could forgo and simply use digital write to do the shifting yourself (but it's slower unless you mess with the bit registers directly)
It works toggling leds with mom tactile switches however, the 8th par input (pin 1 of the 4021 to switch) doesnt seem to be toggling Q0 (pin 15 output on 595) led on/off. All the other switches with leds turn off/on but not this one switch and led. I have tied the tac switches high so the leds are always on for now until it is pushed then it is off.
another question i have, providing i can sort that other switch and led out is, is there away of making the leds latch on and off rather than momentary?
Using the 74HC165, shiftIn sets the clock pin high before reading from the output pin, and this makes it skip the first input pin, and instead read pins 2-8, and a value from the serial data input.
I don't have time right now to check on the 4021 signal polarities but maybe that's at the heart of your problem.
