Timeline for Monitor data sent to 74HC595
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Mar 31, 2016 at 10:22 | history | suggested | Greenonline | CC BY-SA 3.0 |
Removed thanks as per SE policy, inlined the link and other minor fixes
|
| Mar 31, 2016 at 10:11 | review | Suggested edits | |||
| S Mar 31, 2016 at 10:22 | |||||
| Mar 28, 2016 at 3:08 | vote | accept | Paul | ||
| S Mar 27, 2016 at 14:11 | history | edited | Paul | CC BY-SA 3.0 |
edited title
|
| Mar 27, 2016 at 13:40 | comment | added | joan | I had a look at wiringPi.shiftIn. It sets the clock to trigger a bit so it is not in fact any use as a monitor. A monitor needs to respond to the clock rather than control it. | |
| Mar 27, 2016 at 13:05 | answer | added | joan | timeline score: 0 | |
| Mar 27, 2016 at 13:05 | comment | added | Paul | Agreed, and the script I created to read the data (above) doesn't have any delay. Perhaps that's why I'm getting so many 0's. I feel like my script needs to sync with the clock on the 595 but that's where I get lost. | |
| Mar 27, 2016 at 12:48 | comment | added | joan | That's a 1000 bits per second which is luckily very slow in computer terms so you will be able to monitor the data quite easily. | |
| Mar 27, 2016 at 12:13 | comment | added | Paul | The Python code that sends data to the 595 uses a delay of .001 between each bit. I'm not entirely sure how to convert that to an actual data rate. | |
| Mar 27, 2016 at 10:54 | review | Suggested edits | |||
| S Mar 27, 2016 at 14:11 | |||||
| Mar 27, 2016 at 8:29 | comment | added | joan | What data rate are you trying to capture? I.e. how many times does the bit clock change per second? | |
| Mar 27, 2016 at 2:34 | history | edited | Paul | CC BY-SA 3.0 |
Grammer
|
| Mar 27, 2016 at 2:22 | review | First posts | |||
| Mar 27, 2016 at 10:54 | |||||
| Mar 27, 2016 at 2:17 | history | asked | Paul | CC BY-SA 3.0 |