http://www.opencircuits.com/api.php?action=feedcontributions&user=68.9.255.219&feedformat=atomOpenCircuits - User contributions [en]2024-03-28T14:28:53ZUser contributionsMediaWiki 1.34.2http://www.opencircuits.com/index.php?title=Sortof-Networked_RFID_Reader&diff=11414Sortof-Networked RFID Reader2007-11-25T17:46:27Z<p>68.9.255.219: Redirecting to RFID Reader</p>
<hr />
<div>#REDIRECT [[RFID Reader]]</div>68.9.255.219http://www.opencircuits.com/index.php?title=OpenCircuits:Community_portal&diff=11413OpenCircuits:Community portal2007-11-25T17:45:11Z<p>68.9.255.219: </p>
<hr />
<div>Welcome to Open Circuits.<br />
This is a good place to talk about Open Circuits, as a whole.<br />
<br />
We have {{NUMBEROFARTICLES}} articles now. Yay!<br />
<br />
== Anti-Vandalism Bot ==<br />
It is my opinion that this should be the top goal for this site to accomplish.<br />
<br />
: ''We recently updated the $wgSpamRegex ( http://www.mediawiki.org/wiki/Manu<br />
1000<br />
al:$wgSpamRegex ). It should block nearly all of the kinds of spam we've been seeing in the past. (Use [[Meta:Sandbox]] for testing). --[[User:DavidCary|DavidCary]] 08:46, 6 June 2007 (PDT)''<br />
::The problem is, that this is not a one time thing. It must be updated regulary, so it also works for new kinds of spam --SebDE<br />
<br />
Seeing a lot of stubborn spammers. Can we implement some kind of ip blocking mechanism?, that blocks repeated spam ip's for a week or so. Here's a list of known [[spammer ip]].<br />
:Blocking based on IPs might be usefull if it uses a maintained black or gray list, but the kind of IP blocking is used around here doesn't help much. --SebDE<br />
<br />
Disabling edits from users that aren't logged in might help a lot: http://www.mediawiki.org/wiki/Manual:Faq#How_can_I_prevent_editing_by_anonymous_users.3F --[[User:Mzandrew|Mzandrew]] 14:16, 8 September 2007 (PDT)<br />
:[[User:DavidCary|DavidCary]] wrote: "We want a system in a way that makes it very easy for anyone to help us." on his User Discussion page.<br />
:But it wouldn't hurt if the creation of new sites would be logged in users only. (Would reduce the need to delete certain articles over and over again) --SebDE<br />
<br />
Or if someone's not logged in, could we enable a captcha so that the spammers would at least have to do it manually?<br />
Here's the ReCAPTCHA extension for mediawiki sites: http://www.mediawiki.org/wiki/Extension:ReCAPTCHA<br />
There's also the ConfirmEdit extension. http://www.mediawiki.org/wiki/Extension:ConfirmEdit<br />
--[[User:Mzandrew|Mzandrew]] 13:38, 9 September 2007 (PDT)<br />
:That is way to overdesigned if you know what I mean. And just btw it is hell for accessibility. I would rather see the use other techniques like wgSpamRegex and the use of a maintained IP black list first before using such ugly things... --SebDE<br />
<br />
I have a whole bunch of PIC projects and things I think I can do to contribute to this Wiki, but the spam here is way way out of control. I'm looking at the change logs and I'm seeing 20 spam <br />
1000<br />
edits per day. I'm not so sure I want to contribute if my contributions are going to be destroyed in a matter or days. I think requiring a logon to make changes would cut out most of the spam. At this point, the problem is so bad that making things alittle harder for people to make changes is probably worth the benefits.<br />
<br />
Also, this isn't directly related to spam, but it would be nice if the site didn't put nofollow on all the URLs. I think more people would be willing to add project info pages to the wiki if they new it would make them more visable in search engines. The wiki is small enough at this point that if people start abusing this it would be easy to ban or delete their account( assuming the change is made to require a login to make edits)<br />
[[User:Mzoran|Mzoran]] 21:42, 14 October 2007 (PDT)<br />
<br />
== electrical mailing lists ==<br />
Yahoo claims they have<br />
[http://dir.groups.yahoo.com/dir/Science/Engineering/Electrical 1,831 electrical engineering mailing lists].<br />
What would be a good way of letting the people on those lists know about the Open Circuits wiki, without spamming them?<br />
--[[User:DavidCary|DavidCary]] 13:30, 31 May 2006 (PDT)<br />
<br />
* Publish cold fusion howto :-)<br />
* Send one email/week and only once per list. And be on topic, listen carefully for responses.<br />
[[User:Freqmax|Freqmax]] 16:24, 30 July 2007 (PDT)<br />
<br />
== about Open Circuits ==<br />
So, is there any connection between http://OpenCircuits.org/ , http://OpenCircuits.net/ , and this http://OpenCircuits.com/ wiki?<br />
--[[User:DavidCary|DavidCary]] 23:47, 13 June 2006 (PDT)<br />
<br />
No. There is no connection between any of http://opencircuits.com and the other websites listed.<br />
[[User:Chazegh|Chazegh]] 02:55, 18 June 2006 (PDT)<br />
== web rings ==<br />
Document an original microcontroller project and join a PIC webring, or AVR webring. 20 June 2006<br />
<br />
== audio electronics ==<br />
<br />
Is there some other wiki for people to talk about audio electronics?<br />
Or is this Open Circuits the best wiki for talking about things like<br />
''"[http://analog.com/ Analog Devices] AN-221: The Alexander current-feedback audio power amplifier"<br />
1000<br />
;'' by Mark Alexander<br />
?<br />
<br />
I think I would prefer to offload all the audio electronics controversies to some other wiki<br />
(but which one?).<br />
Still, it would be nice to have some "tips for high-power electronics" here.<br />
I imagine that tips page would list the various quirks of high-power MOSFETs, BJTs, TRIACs, and IGBTs,<br />
and (given a particular motor or speaker or other load)<br />
how to select one over the others,<br />
and various ways of working around those quirks.<br />
--[[User:65.70.89.241|65.70.89.241]] 07:17, 10 August 2006 (PDT)<br />
<br />
I just joined Open Circuits. I have been servicing and designing audio equipment for several years (Recording consoles a specialty) I hope you will have a section for audio electronics. I also work with video projection systems and theatrical lighting (stage struck at an early age) I play electric rock-blues guitar, so I also am interested in tube guitar amps (Marshall and Boogie). And there is a big difference in what a guitar player thinks an amp should do, and what a recording engineer wants an amp for. I think these are valid points for discussion.<br />
I've also got an interest in power supplies (my experience is mostly with linear, but I've started learning about switching designs). In fact that brings me to my question, I have some regulator designs based on the 723 that I'd like to share. How do I go about doing that? I built a replacement for a console /- 18V @6A supply when I couldn't find the original regulator devices. I used 723s with external series pass devices. The unit has been working for close to 10 years now, so I think the design is worth sharing. Is anyone interested? <br />
<br />
I also research discrete op amps like the Jensen 990. I've been working (on and off for years) on a clone of that using more modern, easily available parts and devices. Anyone else?<br />
Finally, in response to the first entry in this section, I too read that application note in Analog Devices Audio/Video Reference Manual. My copy is dated 1992. I've repaired a<br />
1000<br />
lot of amplifiers, but haven't built any. If anyone else is hip to this amp I'd like to hear about it. It is a very unique design. I also like the A75 amp design from Nelson Pass and Norman Thagard, and the Leach Amp by Marshall Leach. The last two are pretty normal as far as design goes, not as adventurous as the Alexander with its current-feedback approach.<br />
Aloha, RAF--[[User:66.8.194.185|66.8.194.185]] 14:04, 18 May 2007 (PDT)<br />
<br />
== automotive electronics ==<br />
<br />
Is there some other wiki for people to talk about automobile electronics?<br />
Or is this Open Circuits the best wiki for talking about things like<br />
[http://megamanual.com/ "experimental Do-It-Yourself programmable electronic fuel injection controller"]?<br />
Or should we just point people who want to talk ECUs (engine control units) to the <br />
[http://msefi.com/ MSEFI discussion forum],<br />
even though it sadly lacks a wiki?<br />
--[[User:DavidCary|DavidCary]] 22:36, 2 July 2007 (PDT)<br />
<br />
== inviting bloggers to open circuits ==<br />
<br />
=== how to connect a JTAG probe to a Nokia phone ===<br />
<br />
I'd like to invite bloggers such as GyrosGeier to edit OpenCircuits.<br />
Rather than just spamming him, I think he would be more inclined to help out<br />
if we answered one of his questions first -- such as<br />
[http://hogyros.de/?q=node/167 "If you have information on how to connect a JTAG probe to a Nokia phone, please let me know."]<br />
Maybe I should start a page on [[JTAG]]...<br />
--[[User:DavidCary|DavidCary]] 09:37, 22 September 2006 (PDT)<br />
<br />
The [http://hackedgadgets.com/ Hacked Gadgets blog also has a bunch of cool electronics].<br />
--[[User:DavidCary|DavidCary]] 11:58, 5 January 2007 (PST)<br />
<br />
== red links ==<br />
<br />
The default skin at OpenCircuits currently has "red links" = page exists, "dark red links" = page does not exist.<br />
<br />
I find that confusing. (But not as bad as the wiki that has some links black-on-white, indistinguishable from normal text).<br />
<br />
'''work-around''': Register (it's free, and you don't have to give any personal information), then choose the "preferences" link in the far upper-right corn<br />
1000<br />
er and then pick any other skin.<br />
<br />
The other skins have coloring that you may be more used to from other wiki: "blue links" = page exists, "red links" = page does not exist.<br />
<br />
--[[User:DavidCary|DavidCary]] 08:58, 18 December 2006 (PST)<br />
<br />
<br />
*** Guys, the red color on links is AwuFul, it brings ppl headaches.<br />
That's the only reason I cant participate ***<br />
<br />
--[[User:Takeda|Takeda]] 16:38, 29 September 2007 (PDT)<br />
<br />
== inviting people from other forums to open circuits ==<br />
<br />
Lots of people talk about circuits for LED lighting at<br />
http://candlepowerforums.com/<br />
.<br />
Perhaps we can talk some of them into contributing here -- perhaps using a page or two of Open Circuits as a FAQ for LEDs and drive circuits.<br />
<br />
== tool lists ==<br />
<br />
Should we have an entire page on "tools", and mention it on the main page?<br />
That risks listing *every* tool anyone has ever heard about,<br />
like the page at<br />
http://massmind.org/techref/tools.htm<br />
.<br />
Yes, I'm responsible for uglier bits on that page;<br />
I think the wide variety of oscilloscopes are particularly confusing.<br />
How could we cut through the confusion?<br />
<br />
I see the "techniques" page already has a list of software tools.<br />
Perhaps it would be nifty to have a short list of all the tools necessary for each technique?<br />
Then a beginner would have a better idea of what tools he really needs to get (rather than looking at a huge list of every tool, and wondering for each one, ''"Am I going to regret buying it when I see it gathering dust? Or am I going to regret not buying it when I need it during a midnight debug session?"'').<br />
<br />
--[[User:DavidCary|DavidCary]] 08:37, 24 January 2007 (PST)<br />
<br />
== Requests For Help ==<br />
Thanks for your help with the camcorder mic.<br />
<br />
== sample component ==<br />
<br />
What is the purpose of the [[Sample Component]] ?<br />
--[[User:DavidCary|DavidCary]] 16:27, 7 May 2007 (PDT)<br />
<br />
----<br />
<br />
<br />
== current surge and battery life ==<br />
<br />
Hi, <br />
<br />
currently my board is using a 3V battery, in every 40msec it will turn on its RF to communicate with the base <br />
1000<br />
station. I face a problem here is that my battery life is badly affected. Turning on the RF with cause a current surge. <br />
<br />
Will this surge affect my battery life? If I use a supercapacitor does it helps?<br />
<br />
-- [[User:203.120.164.208]] 04:14, 30 April 2007<br />
<br />
<br />
== MIDI electrical interface ==<br />
<br />
In my opinion, the MIDI interface got a lot of things right that too many later interfaces still trip over.<br />
<br />
* http://www.repairfaq.org/filipg/LINK/F_MIDI.html -- ASCII schematics<br />
* http://www.engadget.com/2005/08/30/how-to-control-csound-with-a-custom-midi-controller-hardware/ -- hand-sketched schematics<br />
* http://www.midi.org/about-midi/electrical.shtml "MIDI Electrical Specification Diagram</div>68.9.255.219http://www.opencircuits.com/index.php?title=Xbee_wireless_module&diff=11412Xbee wireless module2007-11-25T17:42:05Z<p>68.9.255.219: </p>
<hr />
<div>[[Image:Grey-bg-xbee.jpg]]<br />
<br />
<b>Description:</b><br> <br />
Xbee is a wireless communication module from [http://www.maxstream.net Maxstream] built to the 802.15.4 standard. By default it is configured from the factory to be a wireless serial line replacement. It can be programmed to do other functions like join [http://www.zigbee.org ZigBee] networks or transmit level changes of certain module I/O pins. <br />
<br />
There are two flavors of this module: Xbee and Xbee Pro. The pro version has an increased range:<br />
<br />
XBee<br />
*Indoor/Urban: up to 100’ (30 m)<br />
*Outdoor line-of-sight: up to 300’ (100 m)<br />
*TX Current: 45 mA (@3.3 V)<br />
*RX Current: 50 mA (@3.3 V)<br />
*Power-down Current: < 10 μA<br />
<br />
XBee-PRO<br />
*Indoor/Urban: up to 300’ (100 m)<br />
*Outdoor line-of-sight: up to 1 mile (1500 m)<br />
*TX Current: 215 mA (@3.3 V)<br />
*RX Current: 55 mA (@3.3 V)<br />
*Power-down Current: < 10 μA<br />
<br><br><br />
<br />
<b>Documents:</b><br><br />
[http://www.maxstream.net/products/xbee/datasheet_XBee_OEM_RF-Modules.pdf Datasheet] from [http://www.maxstream.net Maxstream]<br><br />
[http://www.maxstream.net/products/xbee/manual_xb_oem-rf-modules_802.15.4.pdf 804.15.2] mode of operation<br><br />
[http://www.maxstream.net/products/xbee/manual_xb_oem-rf-modules_zigbee.pdf ZigBee] mode of operation<br> <br><br />
<br />
<b>Footprints:</b><br><br />
<br />
The module is mounted on a mini-pcb with 2 10pin 2mm pitch headers. See the datasheet for more info.<br />
<br />
[http://www.sparkfun.com Sparkfun Electronics] now makes a [http://www.sparkfun.com/commerce/product_info.php?products_id=8276 breakoutboard] that converts the 2mm pitch pins into 0.1" pitch pins. They also sell [http://www.sparkfun.com/commerce/product_info.php?products_id=8272 2mm header sockets] to use in your projects.<br />
<br />
[[Category:Modules]]</div>68.9.255.219http://www.opencircuits.com/index.php?title=Main_Page&diff=11322Main Page2007-11-23T16:19:23Z<p>68.9.255.219: spam fix</p>
<hr />
<div>Open Circuits is a wiki for sharing [[open source electronics]] knowledge, schematics, board layouts, ports and parts libraries. This include open hardware [[Music Player]]s, [[atomic microscope]]s, [[PC]], [[PDA]] and [[Open Mobile Gadgets|mobile phone]]s, and [[battery|batteries]]. Please help us to build this resource by submitting your component descriptions, projects, techniques, and PCB footprints.<br />
<br />
== [[Projects]] ==<br />
Descriptions, instructions, board layouts, and other documentation for electronics projects and [[ideas]].<br />
<br />
== [[Components]] ==<br />
Lists of components, where to purchase them, how to use them.<br />
<br />
== [[Techniques]] ==<br />
How to do things.<br />
<br />
== [[PCB Footprints]] ==<br />
Don't reinvent the wheel. Known working open PCB footprints for various components.<br />
<br />
== help us make Open Circuits better ==<br />
<br />
[[We love volunteers]].<br />
<br />
<br />
__NOTOC__</div>68.9.255.219