1284P Data Logger

GoForSmoke asked about a '1284P board that could be plugged into the place of a '1284P chip but have a uSD socket on it. That tweaked my interest, so I've come with this: a 5V to 12V powered board that can go into a 1284 socket, 3.3V regulator to run the board at 3.3V, 8 MHz crystal, uSD socket, and L and Power Light, with a header to connect an FTDI Basic for code downloading. SMD legs on the bottom for inserting into a 0.6" wide socket, altho the board itself is wider than that.

Whatcha think?





"That tweaked my interest"

Got to watch out for that 'tweaking'. :wink:

How will it be used?

.

For logging data, not sure what he had in mind. '1284P has 32 IO, so using 4 for SPI leaves 28 IO with 8 of them analog capable, could do a lot.

Jack Christensen made a serial data logger board a while back.
Maybe his software can be canablized to work with this board.

Edit:
What pins are you selecting?

.
.

For surface mount pins on the bottom of the board, these kinds of pins for plugging into a socket


Or just plain 0.025" square pins for use with a solderless breadboard

Last post of the evening for me, g'night.

I like the machined version.

Congrats on >40,000, your work here is very much appreciated!
.

Thanks!
I was looking for the link to forum stats to see where I stood, but can't find it.
Your links on useful tips & tools have been pretty well read, lots of neat ideas there.
You should post your aquarium pump vacuum pick-up tool too.

CrossRoads:
Thanks!
I was looking for the link to forum stats to see where I stood, but can't find it.
Your links on useful tips & tools have been pretty well read, lots of neat ideas there.
You should post your aquarium pump vacuum pick-up tool too.

http://forum.arduino.cc/index.php?action=stats

Thanks Qdeathstar.

I'm trying to shape a non-programmer menu-driven-interactive task-running system capable of running automation approach programs. I don't want it to be too simple or too hard so I can't leave it to thee easy solutions, still working on that.

The user interaction is to be through a terminal emulator or serial monitor. It needs to keep a system log. User needs to be able to see how it's running, the user sets tasks running and the log is the run/debug trace. User needs to be able to make other reports as well. The system will need SD. More files, more buffers, needs more RAM. More RAM means room to store user names for running tasks and more room for more tasks.

More pins lets it do more projects more easily. A 1284 has room to grow.

The system will take care of the non-blocking and other code details, that will all be canned. Setups and links between tasks will be by the user from menu choices and formatted key entry only. I wrote and fixed a lot of business and "expert" code back in the age of text screens, if you let garbage in you get garbage out so filtering is SOP.

The task choices need to cover IO drivers and process tasks. Buttons, sensors, multiplex, 1-wire, I2C, SPI and likely down to apps for the buses, serial text and file... for non-programmers... some is ready, more is close, what's more important is room in flash for lots of devices and wiring to become task choices.

Processes... still working on how flexible the user choices should be. Somewhere there needs to be triggers, repeats and modes. I'm trying to keep variables contained, user shouldn't have to think them up.

Beyond that project, imo serious automation from home level on up needs to keep an operations log if only for when something goes wrong. There's 100's of other uses for big storage but that's number one.

The socket compatibility is to allow it to plug in to existing 1284 boards, some should work. And who do I know that already makes such boards?

No room for 5V operation? It does look packed. Do you have a ballpark on price?

I could make it 5V, but would need to extend the card where the uSD socket is to make room for 5V/3.3V level converter circuitry. I'll play with that some more, maybe Wednesday night, have ice hockey tonight and fencing Tuesday.
I won't price it up until the design is complete as the parts and board size and stencil size drive the cost.

The 5V would be for 24MHz operation, but this is future and maybe for me. You went from kicking around to ready to roll in no time!

Yeah, I get inspired sometimes and the stuff just pops out. I guess the way music does for some folks.

Ok, here it is for 5V operation. Had to make the board a little longer to fit a 74HC4050 for the 5V to 3.3V buffering.
Even got a DTR_EN solder jumper in there.



You must be well grounded, RWP backwards is....

I'll check the layers on that, it was on the bottom for a bit, thought I had moved it to the top.

Not your initials, PWR reversed?

Ah, yes, PWR is RWP flipped.

Any other requests for changes? If not, I'll get some ordered.

Ah, yes, PWR is RWP flipped.

Hence the "well grounded" is not just about your EE skill.

Right now? Just for interest?

I'm still running XP, my internet security is broke so bad I can't use my Paypal or banking. I could work through a buddy of mine out here though. The socket pins will breadboard too, right?

Want to try one at 24MHz? I get > 120KHz loop() frequency running just a few tasks; 32 bit loop counter, status led and button and some kind of trivial process.

Long ago when I was cutting my programming teeth the way was to gather data and then process it. When you can process data as you gather it, you beat "the way" whether it's sensor reads, file records or keystrokes. The more cycles I have between data inputs, the more processing I can do between inputs.

Using the otherwise lost time between inputs can eliminate some or all post-processes and the time they need to run. SD complements that immensely. So you see where the bitchin clock can really count?

Jumper between FTDI 5V and controller 5V?
Or maybe a removable 0 ohm SMD resistor.

Edit:
Shouldn't that be K&RWP ?

.