Difference between revisions of "Ideas"

From OpenCircuits
Jump to navigation Jump to search
Line 65: Line 65:
  
 
-----
 
-----
 +
 +
== Multi PIO interface ==
 +
 +
I've been thinking about this idea for a while now, but I don't have the time, resources, or software coding expertise to see it into existence.  The concept is sort of like Arduino, but would ease several limitations such as I/O bandwidth and program size.  It could streamline embedded system development or make it possible for an old PC to to become the heart of very sophisticated projects.  It could have the following features:
 +
 +
* 64 (or some other arbitrary number) lines of I/O which can be configured as:
 +
** TTL input
 +
** TTL output
 +
** Analog input
 +
** Analog output
 +
** PWM output
 +
* Multiple design versions (sharing a common code/design base):
 +
** USB
 +
** SPI
 +
** PCI
 +
** I<sub>2</sub>C
 +
* Fully open design/source - both hardware, and software
 +
* Built from easily accessible (and preferably inexpensive) parts
 +
* APIs for a variety of programming/scripting languages
 +
(Please expand this list if you have an idea!)
 +
 +
 +
There are a number of microcontrollers that could do the task with very few support components.  Determining which one is right for the job would take a bit of reflection.
 +
 +
It would have hundreds of applications, and have enough I/O to perform several of them at once.  It could be used to collect input and turn switches on and off for a simple home control system or run a model train set.  It could be used to create software implementations of obscure communications protocols (such as [http://en.wikipedia.org/wiki/Wiegand_protocol Wiegand]).  It could be used to build very complex robots.
  
 
[[Category:Ideas]]
 
[[Category:Ideas]]
  
 
{{Stub}}
 
{{Stub}}

Revision as of 23:03, 11 June 2009

Ideas before they become OC projects:

  • Portable Context Device
  • Open power connector for mobile phones, PDAs and laptops. (Wikipedia lists a variety of connectors -- or were you looking for an AC power connector? What sort of specification do you want?)
  • "Open Source Disability Gadgets: DIY for PWD" [1] "Gear and software for people with disabilities is usually provided through charity or from medical supply companies. It's hard or impossible to repair it, or get anyone to repair it. We need to hack the model for accessibility tools! With a culture of open source designs, Instructables, wikis, and blogs, we can start an international movement."

open design laptop

-- OCZ has an open design customizable laptop here. --BlueFusion

How do I make a laptop with 2 independent internal disk drives (so I can do RAID 1)? --DavidCary 21:31, 5 September 2008 (PDT)

better data cable ideas

  • Open data cable. Random good ideas: "One under-appreciated attribute is that the moving parts of the connector are on the cable side, not the system side; when the connector begins to show some wear and tear, the cable is thrown away, not the PC (or printer, or disk drive, or camera)." -- Michael Teener [2] ... Many popular data cables also include power (Power over Ethernet, FireWire -- but not the iLink variant, USB)... What voltage? extra-low voltage [3]? ... Is it better to have the same connector on both ends of the cable, or have different connectors? Same connector allows peer-to-peer arbitrary mesh; different connectors afford/suggest a tree topology ... putting 2 connectors on every device, "upstream" and "downstream", allows linear daisy-chaining; 3 identical connectors allow any arbitrary-dimensional topology ... the round pins vs. flat blades (vs. other connector shapes) controversy[4] ... optical isolation (like MIDI hardware) seems like a good idea ...
  • When someone trips over the cable, destruction of the fixed socket is unacceptable -- but is it better to destroy the cable, or to let the cable pop out -- like MagSafe? ... twisted pair for power, and twisted pair for data ... Some data line codes (such as the one used for USB) are designed to work even when the twisted pair is accidentally twisted an extra half-twist; is it worth arranging things so the entire plug can be plugged in with an extra half-twist with no problems (like automobile keys) ? ... What's this I hear about non-contact power pads?


"What we would like to see is one cable that carries audio, video and power to or from whatever device you need to use. It needs to be small, it needs to have tremendous bandwidth (perhaps using fiber optics), and it needs to be smart enough not to ruin anything you plug it into. ... Please, someone round up all the consumer electronics manufacturers, and somehow make them all use the same connectors." -- Gizmodo.

Some commenters on Gizmodo have some interesting ideas:

  • wireless for all data, wires only for power
  • use a standard power connector -- Green Plug
  • fiber
  • "something can be really good new, but how many tests have there been which rate performance over time? Especially with in-wall installations, this may be a very serious issue."
  • "You can already do everything on a CAT5e cable network ... the next version of the PoE spec is supposed to allow for 56 watts of power per cable, which is more than enough for hard drives and such."
  • "You already have it, its called FireWire."
  • "we already had one cable for everything. It was coax. It was used for audio, video, even networking. But then people wanted better. The that pretty much messed everything up. Stop wanting more and you'll be fine."

A few commenters on Gizmodo seem to think it is impossible or unfeasible.

  • "If it does all of that at the same time, it will need to somehow send and receive data at the same time- is that possible?"
  • "This whole concept is ridiculous..."
  • "There's money to be made in chaos."
  • "some cables need a lot of pins and some don't and it would be silly to have a 24 pin connector for USB for instance, and it would be costly to have cables that have lots of pointless wires in it."
  • "power inside the transmission cable? thats just asking for interference."

Related:

Understanding how cables fail might help us design better ones:

LaTeX circuit diagramme markup

Hello, I've just joined!
I've just started using PmWiki as a "MyWiki" (home CMS/PIM offline personal desktop intranet wiki)(I've decided to call it a "MyWiki" rather than keep reeling off a description!)
One of my main objectives in using this is to write up my electronics degree notes and sort of build my own encyclopaedia. Naturally, that means you have to use LaTex (haven't quite got MathML or jsMath to do as their told, but they work well enough for the meantime); and use of GraphViz is on the agenda for making block diagrammes, flowcharts; and (I hope!) making bode plots, smith charts, simulated 'scope readings, and what I'd really like is to make actual analogue circuits just by markup. I'm only just learning Java, and my PHP knowledge is pretty rank. Does anyone share my interest and want to set up a team to work on this problem? I think it'd be a great addition to this wiki as well!
cheers! 212.159.117.182 04:28, 29 November 2008 (PST)

That sounds like a great idea. I see that Wikipedia's "WikiProject Electronics" is taking a few small steps in that direction. Have you seen Wikipedia: WikiProject Electronics#Drawing circuits and Wikipedia: WikiProject Electronics/Programs ? And the Techniques#Software_design_tools already available? --DavidCary 19:54, 14 December 2008 (PST)


Multi PIO interface

I've been thinking about this idea for a while now, but I don't have the time, resources, or software coding expertise to see it into existence. The concept is sort of like Arduino, but would ease several limitations such as I/O bandwidth and program size. It could streamline embedded system development or make it possible for an old PC to to become the heart of very sophisticated projects. It could have the following features:

  • 64 (or some other arbitrary number) lines of I/O which can be configured as:
    • TTL input
    • TTL output
    • Analog input
    • Analog output
    • PWM output
  • Multiple design versions (sharing a common code/design base):
    • USB
    • SPI
    • PCI
    • I2C
  • Fully open design/source - both hardware, and software
  • Built from easily accessible (and preferably inexpensive) parts
  • APIs for a variety of programming/scripting languages

(Please expand this list if you have an idea!)


There are a number of microcontrollers that could do the task with very few support components. Determining which one is right for the job would take a bit of reflection.

It would have hundreds of applications, and have enough I/O to perform several of them at once. It could be used to collect input and turn switches on and off for a simple home control system or run a model train set. It could be used to create software implementations of obscure communications protocols (such as Wiegand). It could be used to build very complex robots.