Latest posts from “adafruit industries” board.

How to work together?

clxwgs — Fri, 30 Jul 2010 22:43:07 -0400

I can have some different sensors worked separately.
Now,I need to make them work at the same time.
For example,I want to driver the motors while read the encoder(count the circles the motors run) together.
I can only use the two sensors in turn instead,but they cannot work well.What should I do to improve the program?
Thanks.

Re: plastic enclosures

franklin97355 — Fri, 30 Jul 2010 21:41:51 -0400

Is this really cost prohibitive under a certain number of units?

The answer is it depends on where the cost becomes prohibitive to you. Even at $50 for the mold I wouldn't buy just one.

Re: New XBees configurable, but don't respond in terminal

robodude666 — Fri, 30 Jul 2010 21:28:41 -0400

Hey guys,

Played around with CoolTerm a bit. Got it working, I think. It seems I need to enable RTS. Also, you don't hit enter after the +++ command. Then just wait 5-10 seconds and the AT___ commands seem to work fine. Epic Win.

Now to figure out why the two won't communicate.

They're both in ID 1337. One is MY 1 and DL 2, other is MY 2 DL 1. Is this a correct setup for a Point To Point configuration?

Re: Arduino Xbee Sensor Project - Need Help Please!

erexx — Fri, 30 Jul 2010 19:39:09 -0400

The code I need might be in here somewhere.
This reads ph to lcd and alot of other sensor data.

I only need the code that will read the voltages into valid ph values in hyperterminal.
Again if anybody can parse exactly what I need out of this I would be very grateful.

Code: Select all: /* pHduino.pde - pHduino firmware for Arduino. Copyright (c) 2009 Carlos A. Neves http://code.google.com/p/phduino This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see . Author: Carlos A. Neves */ #include "WProgram.h" #include #include "pHduino.h" #include "float2string.h" #include "commandline.h" #include "string.h" #include "stdlib.h" #include //#include "freemem.h" // Creates the LCD instance LiquidCrystal lcd(PH_LCD_RS_PIN, PH_LCD_RW_PIN, PH_LCD_E_PIN, PH_LCD_D4_PIN, PH_LCD_D5_PIN, PH_LCD_D6_PIN, PH_LCD_D7_PIN); // ordinary variables char myStr[16]; int val_E; int val_R; int val_T; float E; float R; float T; float pH; int i; unsigned long ul; float f, f2; unsigned long int my_timer0; unsigned long int my_timer; boolean pH_alarm_status = false; // struct of parameters struct myRec_T{ unsigned int magic_number; boolean start_flag; unsigned int time_between_acquisitions_ms; boolean temperature_sensor_flag; float temperature_constant_celcius; boolean pH_alarm_flag; float pH_inf; float pH_sup; } myRec; void parameters_reset(void){ myRec.magic_number = MAGIC_NUMBER; myRec.start_flag = true; myRec.time_between_acquisitions_ms = PH_INITIAL_TIME_BETWEEN_ACQUISITIONS_MS; myRec.temperature_sensor_flag = true; myRec.temperature_constant_celcius = PH_TEMPERATURE_VALUE_INITIAL_CELCIUS; myRec.pH_alarm_flag = false; myRec.pH_inf = 0.0; myRec.pH_sup = 14.0; eeprom_write_block(&myRec, (void *)0, sizeof(myRec)); } void setup(void){ // Init serial port Serial.begin(115200); // setup LED, button, and buzzer pinMode(PH_LED_PIN, OUTPUT); pinMode(PH_BUTTON_CTRL_PIN, INPUT); pinMode(PH_BUZZER_PIN, OUTPUT); // initialize LED and buzzer digitalWrite(PH_LED_PIN, LOW); digitalWrite(PH_BUZZER_PIN, LOW); // begin LCD lcd.begin(16, 2); lcd.clear(); lcd.noCursor(); lcd.home(); lcd.display(); // Initial messagens. digitalWrite(PH_BUZZER_PIN, HIGH); delay(200); digitalWrite(PH_BUZZER_PIN, LOW); digitalWrite(PH_LED_PIN, HIGH); lcd.setCursor(0,0); lcd.print("pHduino"); lcd.setCursor(0,1); lcd.print(PH_PHDUINO_VERSION); delay(2000); digitalWrite(PH_LED_PIN, LOW); // read parameters from EEPROM eeprom_read_block(&myRec, (void *)0, sizeof(myRec)); // check for empty memory or different data block if (myRec.magic_number != MAGIC_NUMBER){ parameters_reset(); } lcd.clear(); // Free memory check //Serial.println(availableMemory()); } void process_data(void){ digitalWrite(PH_LED_PIN, HIGH); // print temperature // Obs.: You can operate the pHduino without a temperature sensor. // In this case, you need setup a temperature value // and comment the readADC and calc lines. if (myRec.temperature_sensor_flag == true){ val_T = readADC(PH_TEMP_ADC_PIN, PH_TIME_ADC_READINGS_MICROSECONS); T = 100 * val_T * 5.0 / 1024; } else { T = myRec.temperature_constant_celcius; // celcius temperature to operates without a temperature sensor. } floatToString(myStr, T, 1); lcd.setCursor(0,0); lcd.print(myStr); lcd.print((char)223); // degree symbol lcd.print("C "); //Serial.print(val_T, DEC); //Serial.print(" "); Serial.print(myStr); Serial.print(" "); val_R = readADC(PH_REF_ADC_PIN, PH_TIME_ADC_READINGS_MICROSECONS); R = PH_GAIN_STAGE2_REF * (val_R * 5.0 / 1024); //floatToString(myStr, R, 3); //lcd.setCursor(0,0); //lcd.print(myStr); //lcd.print((char)223); // degree symbol //lcd.print("C "); //Serial.print(val_T, DEC); //Serial.print(" "); //Serial.print(myStr); //Serial.print(" "); // print ADC value and voltage of electrochemical potential val_E = readADC(PH_PH_ADC_PIN, PH_TIME_ADC_READINGS_MICROSECONS); E = -1 * ((val_E * 5.0 / 1024) - R) / PH_GAIN_STAGE1_PH; //floatToString(myStr, E, 3); lcd.setCursor(0, 1); lcd.print((int)(E*1000), DEC); // mili volts lcd.print("mV "); lcd.setCursor(8, 1); lcd.print("AD:"); lcd.print(val_E, DEC); lcd.print(" "); Serial.print(val_E); Serial.print(" "); Serial.print((int)(E*1000), DEC); // mili volts Serial.print(" "); // print pH // delta_pH = -(F/(2.303*R*T))*delta_E // // where, // gas constant R = 8.31451 J * K^-1 * mol^-1 // Kelvin temperature T = celcius temperature plus 273.15 K // Faraday constant F = 96485 C pH = (float)((-5038.8 * E / (273.15 + T)) + 7.0); floatToString(myStr, pH, 2); lcd.setCursor(8, 0); lcd.print("pH:"); lcd.print(myStr); lcd.print(" "); Serial.print(myStr); Serial.print(" "); // print alarm signal if (myRec.pH_alarm_flag == true){ Serial.print(1, DEC); Serial.print(" "); if ((pH < myRec.pH_inf) || (pH > myRec.pH_sup)){ Serial.print(1, DEC); pH_alarm_status = true; lcd.setCursor(7, 0); lcd.print("*"); } else{ Serial.print(0, DEC); pH_alarm_status = false; lcd.setCursor(7, 0); lcd.print(" "); } } else{ Serial.print(0, DEC); Serial.print(" "); Serial.print(0, DEC); pH_alarm_status = false; } Serial.println(); if (pH_alarm_status == false){ digitalWrite(PH_LED_PIN, LOW); } else{ digitalWrite(PH_BUZZER_PIN, HIGH); delay(100); digitalWrite(PH_BUZZER_PIN, LOW); } } void process_cmd(void){ if (process_command_line() == 1){ // cmd if (strcmp(cmd_str, "cmd") == 0){ Serial.println(cmd_parm_str); // cmd phduino on|off if (strcmp(cmd_parm[0], "phduino") == 0){ if (strcmp(cmd_parm[1], "start") == 0){ myRec.start_flag = true; digitalWrite(PH_BUZZER_PIN, HIGH); delay(200); digitalWrite(PH_BUZZER_PIN, LOW); } if (strcmp(cmd_parm[1], "stop") == 0){ myRec.start_flag = false; lcd.clear(); digitalWrite(PH_BUZZER_PIN, HIGH); delay(200); digitalWrite(PH_BUZZER_PIN, LOW); } } // cmd interval_ms INT if ((cmd_n_parms > 1) && (strcmp(cmd_parm[0], "interval_ms") == 0)){ ul = atol(cmd_parm[1]); if (ul > 0){ myRec.time_between_acquisitions_ms = ul; my_timer0 = millis(); // reset the timer } } // cmd set_temp_sensor on|off if (strcmp(cmd_parm[0], "set_temp_sensor") == 0){ if (strcmp(cmd_parm[1], "on") == 0){ myRec.temperature_sensor_flag = true; } if (strcmp(cmd_parm[1], "off") == 0){ myRec.temperature_sensor_flag = false; } } // cmd set_temp FLOAT if (strcmp(cmd_parm[0], "set_temp") == 0){ f = (float)atof(cmd_parm[1]); if ((f >= 0.0) && (f <= 100.0)){ myRec.temperature_constant_celcius = f; } else{ Serial.println("Error: Temperature range from 0.0 to 100.0"); } } // set pH alarm range if (strcmp(cmd_parm[0], "set_ph_alarm") == 0){ f = (float)atof(cmd_parm[1]); f2 = (float)atof(cmd_parm[2]); if ((f >= 0.0) && (f <= 14.0) && (f2 >= 0.0) && (f2 <= 14.0) && (f2 > f)){ myRec.pH_inf = f; myRec.pH_sup = f2; } else{ Serial.println("Error: pH range from 0.0 to 14.0"); } } // pH alarm if (strcmp(cmd_parm[0], "ph_alarm") == 0){ if (strcmp(cmd_parm[1], "on") == 0){ myRec.pH_alarm_flag = true; } if (strcmp(cmd_parm[1], "off") == 0){ myRec.pH_alarm_flag = false; digitalWrite(PH_LED_PIN, LOW); lcd.setCursor(7, 0); lcd.print(" "); } } // reset parameters if (strcmp(cmd_parm[0], "reset") == 0){ parameters_reset(); } // cmd help if (strcmp(cmd_parm[0], "help") == 0){ Serial.println("cmd help"); Serial.println("cmd phduino start|stop"); Serial.println("cmd interval_ms INT"); Serial.println("cmd set_temp_sensor on|off"); Serial.println("cmd set_temp FLOAT"); Serial.println("cmd set_ph_alarm TEMP_INF TEMP_SUP"); Serial.println("cmd ph_alarm on|off"); Serial.println("cmd reset"); } // save parameters eeprom_write_block(&myRec, (void *)0, sizeof(myRec)); } } } void loop(void){ my_timer = millis(); if ((my_timer-my_timer0) > myRec.time_between_acquisitions_ms){ // reset the timer my_timer0 = my_timer; if (myRec.start_flag == true){ process_data(); } } process_cmd(); }

Re: Help with CV/Gate and Yamaha CS-5

E:pp:ik — Fri, 30 Jul 2010 19:34:21 -0400

At the very least you'll have that!

Re: Generate ICMP Packets

bbunk — Fri, 30 Jul 2010 19:25:57 -0400

ICMP's are broadcast packets. To generate a custom packet type, typically you will need a raw socket. Good luck!

Re: Help with CV/Gate and Yamaha CS-5

LoGiCa — Fri, 30 Jul 2010 18:04:01 -0400

Great, thanks for the help. I will experiment

Mint tin amp

youeatwaffles — Fri, 30 Jul 2010 18:00:02 -0400

I want to make the make magazine mint tin amp, but all I have is a chip that says opa2132pa
it says "High Speed FET-Input TI Op amps" on the package, can this be substituted for the LM386N-3 on the plans? thanks here is the link http://www.make-digital.com/make/vol04?folio=131#pg133

New XBees configurable, but don't respond in terminal

robodude666 — Fri, 30 Jul 2010 17:54:35 -0400

Hey guys,

I got my order for two XBees, an XBee Adapter Kit and the Parallax USB Adapter from Adafruit today. Assembled it all, and now I'm trying to get the little bees to work.

I'm working in Windows 7, as X-CTU is windows-only. I have the USB adapter plugged in, and it's visible as COM3 (I had the drivers previously installed from using my Arduino on it). The Green and Yellow LEDs are solid on the right side, and on the left side the red LED is constantly blinking. In X-CTU, I can run the Test / Query and a modem of type XB24 is found running a firmware of 10E6. The Modem Configuration works fine as well; I can read and write, as well as upload the latest firmware. I set both XBees to a PAN ID of 1337. XBee A was setup with MY of 1 and DL of 2, whilst XBee B was setup with MY of 2 and DL of 1. In both cases, the modem parameters were successfully written to the XBee.

Everything is fine... up to here. When I open up a terminal (I tried Cool Term, TeraTerm, Putty, and X-CTU's Terminal) I always get.. nothing. I can type +++ or AT and hit enter all I want, but I never receive an OK in return. The LEDs remain in the same state (Green + Yellow solid, Red blinking).

I tried the USB Adapter on both my Windows 7 machine, as well as my iMac running Mac OS X 10.6.4. I'm using the default 9600 buad, no flow control, 8-bit with no parity and 1 stop bit in every terminal I tried. I've read and played along with the XBee pages on ladyada's site several times, but no dice...

Any ideas? Did I do something incorrectly? I can configure the modules just fine, and they're seen by X-CTU... I just can't talk to them via a terminal. I also tried both XBee modules with the USB Adapter, so the chance of it being a bad Bee is low I think.

Cheers,
-robodude666

Re: What?

rj44319 — Fri, 30 Jul 2010 17:53:18 -0400

The problem was the lib. I downloaded....
I took the lib. from another computer and it was fine...
the one i downloaded version 10c. Has any one reported problems with it?

Zero search script for adafruit motor shield

Antiklesys — Fri, 30 Jul 2010 17:20:20 -0400

Posting my Zero Search script, works like a charm. It reads from a digital sensor, at the moment using a magnetic sensor on my motors.
It centers the motor zero in the middle of the sensor.

http://www.megaupload.com/?d=49DFJJ01

plastic enclosures

stbtrax — Fri, 30 Jul 2010 17:16:33 -0400

I am wondering how much it costs to make those plastic enclosures like the arduino one adafruit sells.
What kindof costs can be expected assuming I have the design ready? i.e. molding tooling, injecting. Is this really cost prohibitive under a certain number of units?

Re: Help with CV/Gate and Yamaha CS-5

E:pp:ik — Fri, 30 Jul 2010 17:01:45 -0400

Basically yes. The x0xb0x will act as this go-between. The midi data coming in is binary and the x0xb0x converts it to voltages which it uses internally and also sends out via the cv/gate jacks out back.

It just so happens that Yamaha and a few other companies at that time chose a different method to interpret how an octave would be tuned. The "standard" most synths (including the x0x) use is 1.0 V / octave. You're going to hear a shift in those notes because the CS-5 sees an octave as 1.2V as opposed to 1.0 (0.1 V / semitone x 12 notes in that octave = 1.2).

Technically speaking the CS-5 is incompatible in this arrangement. I can't recall how it interprets the gate either (i.e. note on/off) but you may find that there's an issue there too. There are several variants on how that works as well. You may end up still needing a converter to get this all to work the way you'd expect it to. Midi -> CV /Gate for the Yamaha spec or voltage and trigger converter to keep it all in tune and triggering properly as you slave it to your sequencer.

Re: Dimensions of the DS1307 breakout board

adafruit — Fri, 30 Jul 2010 16:52:55 -0400

did you click on Download Source?

Dimensions of the DS1307 breakout board

ohnoezitasploded — Fri, 30 Jul 2010 16:01:43 -0400

Hi All,
I'm looking at the DS1307 breakout board, but I'm pretty constrained for space in the project I have in mind. What are the dimensions of the board.

By the way, I tried to download the schematics from the github site, but the files appear to be corrupted-- neither the Eagle files nor the picture would open on my machine (Win7 64 with Eagle 5.10, if it matters).

Thanks!
Max

Re: What?

ChuckM — Fri, 30 Jul 2010 15:58:25 -0400

To answer your specific question, the string 'NULL' was not defined.

Unlike some languages the notion of 'NULL' is not a standard part of the C language, rather its a convention used by the libraries. Typically it will become defined when some include file needs it and they have protected themselves from this error by adding the code:

Code: Select all: #ifndef NULL #define NULL (void *)0 #endif

Or some such (this particular usage comes from include files on Linux but others have it as well).

You can put the above code at the top of your file before you include anything if you'd like to ensure that NULL is defined.

--Chuck

Re: Help with CV/Gate and Yamaha CS-5

LoGiCa — Fri, 30 Jul 2010 15:46:21 -0400

Thanks for the reply E:pp:ik.

Am I right in saying that MIDI data I send to the Xoxbox will generate note voltages. I haven't used anything like this before so apologies if I am incorrect.

Re: What?

rj44319 — Fri, 30 Jul 2010 15:32:07 -0400

I will post the code tonight....one more thing....the code compiles on another computer just fine....

Re: EAGLE library "invalid data"

adafruit — Fri, 30 Jul 2010 15:31:01 -0400

read the topic "Eagle Part Library" about 20 threads down?

EAGLE library "invalid data"

jmsaavedra — Fri, 30 Jul 2010 15:08:35 -0400

Hi all -

I'm trying to import the Adafruit Eagle library, and for some reason Eagle doesn't like it. It's telling me "invalid data in file". I've got the .lbr in the same directory as all the other .lbr's, and I'm using EAGLE 5.10.0

Any suggestions... I'm no EAGLE pro, just an amateur, so please excuse me if I'm doing something obviously wrong...

Thanks in advance!

Re: Help with CV/Gate and Yamaha CS-5

E:pp:ik — Fri, 30 Jul 2010 15:07:59 -0400

These old Yamahas use a Hz (0.1V / semitone)/Octave set up so while you can connect the x0x to it, the notes won't match. If you want to connect it though it would be the following:

x0xb0x CV Out --> CS-5 Control Volt IN
x0xb0x Gate Out --> CS-5 Trigger IN

Re: Can't bike fast enough?

arduwino — Fri, 30 Jul 2010 14:20:39 -0400

For the whole circle you need about 20 Hz.

Not sure where this number comes from. Many 8mm movies were made at 16 fps. And you don't need even that rate for a static image.

The persistance of vision effect is subject to many variables ranging from image contrast and ambient lighting to the viewer.

Re: Power supply issue

guest — Fri, 30 Jul 2010 14:06:45 -0400

do you have your meter set to ac or dc voltage
the capacitors should only have dc voltage

otherwise double check the diodes are facing the right way
and press your probes into the point you are measuring
sometimes the flux from soldering keeps it from contacting

Re: IceTube Clock display goes out after a minute

adafruit — Fri, 30 Jul 2010 13:57:03 -0400

you can post clear photos of your kit PCB top and bottom, we can look for errors that could cause this!

Re: Can't bike fast enough?

Dave — Fri, 30 Jul 2010 13:49:59 -0400

I still don't understand.
Can you just tell me what's wrong with the thoughts and calculations I did ?

Help with CV/Gate and Yamaha CS-5

LoGiCa — Fri, 30 Jul 2010 13:35:10 -0400

Hi guys, could someone with some experience controlling analog synths with the Xoxbox CV/Gate tell me what I need to plug in where on the Yamaha CS-5.

Thanks in advance

Re: Arduino Xbee Sensor Project - Need Help Please!

erexx — Fri, 30 Jul 2010 13:34:06 -0400

I have done this.
The output in hyperterminal is not accurate at all but its better than garbage.
The code I am using is a generic averaging code for a temp sensor by Jeff Gray and Dave Millis.
I need to covert the mah to ph but I dont know how to plug in the equation.

With the current code I get this result in Hyperterminal:
0 = ph 7
36 = ph 4
0 = ph 10

I found some ph convertion code here: http://www.emesystems.com/OL2ph.htm

Code: Select all: Here is the first cut on how to program it on the Basic Stamp: This assumes that the output of the pH electrode is exactly 0 volts at pH7, and that it has a Nernst slope of exactly 59.16 mV per pH unit: pHloop: DO GOSUB ADread ' return millivolts, mV, not shown pH = mV ** 55405 ' stamp's way to multiply times 700/828 (see below) pH = pH - 845 ' 845 is the 1 volt offset, times 700/828 pH = 700 - pH ' adjusts to pH 7.00 at 1 volt input, decreasing in acid DEBUG REP "-"\pH.bit14,DEC abs (pH/100),".".DEC2 abs pH ' display with decimal point xx.xx LOOP

The code I am currently using. I need a valid voltage to ph equation to replace the averaging one.

Code: Select all: /* Analog Average - Rolling Buffer * Jeff Gray - 2008 * ------------------ * Averaging Code, modified from Dave Millis example */ int average[100]; byte counter = 0; void setup() { Serial.begin(9600); } void loop() { // read the value from the sensor int inAn = analogRead(0); average[counter] = inAn; byte c; int total = 0; for(c = 0;c<100;c++){ total += average[c]; } int averaged = total / 100; Serial.println(averaged); counter = (counter + 1) % 100; }

Re: Reducing Values from FSR's idle pressure reading

Zener — Fri, 30 Jul 2010 13:19:15 -0400

I agree that the solution will be mechanical not electrical/software. Do you have a force vs. resistance graph for the sensor you are using? This should help you understand what is happening. My previous limited experience with FSR's is that if you leave a significant force applied all the time (like your floor tiles) then their response will change over time. Basically, they don't like that. However, you could get away with it by having some calibration routine I suppose. But that is a bit of a seperate issue at this point, since you don't have it working at all yet. Good luck.

Re: IceTube Clock display goes out after a minute

AudiTTchick — Fri, 30 Jul 2010 13:00:39 -0400

Hello,

Yes If the coin cell is not in the clock it works with out a problem but as soon as it goes in it fades out after bit of time elapses.

Erica

Power supply issue

docdigital — Fri, 30 Jul 2010 12:59:37 -0400

Hi ,

I begun today soldering my power supply and already run into a problem of not getting any voltage across the 2 capacitors C4 and C5.

I have the 10 volt on the plug and from there on 10 volts at the beginning of the diode rectifier circuit but after that nothing whatsoever

Everything is correctly soldered, polarity seems in order, cant see any cold solders, so i am a bit stomped.

Could it be that i fried those Diodes already? If i am not mistaken they should be pretty robust, How can i test them properly? they seem to work when i test for continuity, 1 direction (.630), but nothing in the other direction.

BTW, i am following the instructions on the site to the letter, so i cant go on with the work untill i fixed this

Re: IceTube Clock display goes out after a minute

adafruit — Fri, 30 Jul 2010 12:48:25 -0400

yes we split your topic - you may or may not have the same problem and it only confuses the situation to respond to an existing and solved thread.

if you dont have the coin cell in, it works fine?

Re: IceTube Clock display goes out after a minute

AudiTTchick — Fri, 30 Jul 2010 12:44:27 -0400

Hi,

Thats weird I wanted this post to be a reply to the other one but it got out on its own. hmmmm....
Yes the coin cell is inserted correctly and it as soon as it comes on it beeps and fades out after a bit of time. It may be the same issue that the other person is having..

Erica

Re: multiple power switches

adafruit — Fri, 30 Jul 2010 11:30:08 -0400

hmm yes the github project could have really benefitted from PSTs
the best thing you can do is go to the HW store and get some 3 prong plugs and wire up each one so that they work with an extension cord. then swap in the PST's and connect them to a outlet strip
one of the nice things about the PST is that it prods one in the right direction by requiring a proper plug instead of just wires dont forget to bolt ground to the outside of the metal case!

Re: IceTube Clock display goes out after a minute

adafruit — Fri, 30 Jul 2010 11:25:20 -0400

does it turn off immediately? are you putting the coin cell in the right way?

IceTube Clock display goes out after a minute

AudiTTchick — Fri, 30 Jul 2010 11:23:08 -0400

Hi,

I am having the same problem with mine if I have the button cell in the clock turns off but without it works like a charm. What do I have to replace exactly and with what?? Sorry it may be in the text and I might have missed it.

Erica

Re: The charger blows in my hands

zed82 — Fri, 30 Jul 2010 11:06:01 -0400

thank you.
Do you need my adress?

PIR Sensor - Image citation

Frodob — Fri, 30 Jul 2010 10:46:31 -0400

I was reading your (great) PIR "How to Use.." page, and followed the link to the Glolab site, and found the image you needed a citation for on their focusing devices page ( http://www.glolab.com/focusdevices/focus.html ). A modified version is also on the PIR page you link to at Glolab.

Edit: Also on the NYU page (http://itp.nyu.edu/physcomp/sensors/Rep ... aRedSensor)

Re: What?

arduwino — Fri, 30 Jul 2010 10:45:12 -0400

Likely because the other code includes the appropriate headers.

Since we have no idea what code you are talking about, we can't offer any more specific advice.

Re: What?

rj44319 — Fri, 30 Jul 2010 10:36:34 -0400

well it compiles on another set of code.....?

Re: back panel layout

misjah — Fri, 30 Jul 2010 10:28:31 -0400

thanx, I'll find somebody that uses autocad to convert it or whatever is needed.

Re: Stepper/Servo/Motor Shield Questions

arduwino — Fri, 30 Jul 2010 10:28:06 -0400

It comes as a kit, you'll need basic soldering skills to assemble it. You can build it with "stacking headers". Pin usage is detailed in the FAQ and in a sticky at the top of this forum.

Stepper/Servo/Motor Shield Questions

SimplicityGuy — Fri, 30 Jul 2010 10:05:42 -0400

I have a question about the stepper/servo/motor shield. I'm curious, which pins on the arduino are used to run this shield? For instance, if I want to use this shield in conjunction with an LCD and some buttons, would I be able to? Unfortunately there was no information about passthrough pins or which pins were used by the shield.

Additionally, does this come assembled, or unassembled? If unassembled, would it be possible to add pass through headers to this shield?

Re: multiple power switches

ahdavidson — Fri, 30 Jul 2010 09:59:19 -0400

Thanks for the pointer to the GitHub project (the comments are the most educational part about that post) and the advice about not using a common neutral.

AC power is one of the reasons I bought three of the Power Switch Relays. I would like not to kill my students, just inspire them!

Re: Mating connector for PF35T-48L4 stepper motor?

arduwino — Fri, 30 Jul 2010 09:03:20 -0400

I usually cut them off and use the screw terminals on the stepper controller. But if you need a more convenient disconnect and can't find the mating connector, you might want to just replace the whole thing with a matched M/F pair.

Re: super-cheap pick-and-place device with ~1 mil accuracy

bootstrap — Fri, 30 Jul 2010 07:52:50 -0400

I'm looking for parts to build a couple of the super-cheap pick-and-place devices that I described previously in this thread. The linear bearings and shafts are easy enough to find, but where to find a few of the parts isn't obvious to me. Anyone know where I can find:

#1: vacuum pick-up head : It would be great if the head included a switch that toggles the vacuum on and off each time the tip presses down on something. This way the vacuum would turn on when the tip pressed down against the top of the component to pick it up, then turn off when the tip pressed the component down onto the PCB.

#2: linear track end blocks : I thought I'd find these, but so far no luck. These are simply thick metal plates (or cast equivalents) that have two 15mm~25mm round holes 50mm ~ 100mm apart to plug round linear rails into. Obviously I can get this machined up pretty easily, but better if I can buy off the shelf.

#3: PCB stand : This is just a sturdy adjustable frame that can hold any size PCB ~25mm above the tabletop. I'll attach teflon feet so it can easily slide around on the tabletop.

I guess that's it. Most of the rest is easy to find (loose linear bearings, linear bearings in pillow blocks, round shaft for linear rails, etc)... or something that clearly needs to be machined custom (the templates).

Re: Solar minty boost questions

arduwino — Fri, 30 Jul 2010 07:28:22 -0400

Has anyone tried any of the flexible/rollable solar panels with this?

Not with a minty-boost, but I've experimented with a flexible solar panel for backpacking.

The theoretical advantages of a flexible panel for this application are the light weight and low-bulk. But, as Adafruit says, the lower efficiency means that you will need a larger panel to get the same power output as you would with a good quality rigid panel such as the one Adafruit sells. If you are attaching this to your pack so you can charge while on the trail, the larger size means it is more susceptible to snagging on branches or damage from leaning your pack against a tree. You will also need to attach them to some sort of backing material for to protect the cells. This will cut into the weight advantage.

Re: What?

arduwino — Fri, 30 Jul 2010 06:44:23 -0400

Looks like you are missing one of the standard header files.
Beyond that, it is hard to say. You haven't given us much info to work with.

Re: Reducing Values from FSR's idle pressure reading

arduwino — Fri, 30 Jul 2010 06:04:50 -0400

Your static load is using up 90% of the dynamic range of the sensor. You can do things to reduce the static load the easiest would be to use larger bumpers to spread the load over a larger area.

From there, you can fine tune the range using the "map()" function to re-scale the analog values. http://arduino.cc/en/Reference/Map

Re: Ethernet shield issues

bswift5528 — Fri, 30 Jul 2010 04:36:51 -0400

This thread has been helpful! I don't know if you guys ever resolved your problem, but for me, the problem with the Java errors in LEDColorPicker.pde only really exists in the javascript line, because it's more than 1024 chars (I think). I solved the problem by splitting it into 2 strings. Works perfectly after that. I'm using Arduino-0018.

After that, I get a bunch of the following errors on compile that look like:

Code: Select all: /Users/bjswift/Documents/Arduino/libraries/NewSoftSerial/NewSoftSerial.h: In member function 'void AF_XPort::begin(uint16_t)': /Users/bjswift/Documents/Arduino/libraries/NewSoftSerial/NewSoftSerial.h:74: error: 'void NewSoftSerial::setTX(uint8_t)' is private /Users/bjswift/Documents/Arduino/libraries/AF_XPort/AF_XPort.cpp:27: error: within this context /Users/bjswift/Documents/Arduino/libraries/NewSoftSerial/NewSoftSerial.h:75: error: 'void NewSoftSerial::setRX(uint8_t)' is private /Users/bjswift/Documents/Arduino/libraries/AF_XPort/AF_XPort.cpp:28: error: within this context

Ok...there's a great note on these errors here. Well, assuming there were other changes in NewSoftSerial from version 9 that he's saying to use, I just went with the newest version but moved the lines in the header declaring 'setRX' and 'setTX' as private methods into the public methods block. The NSS author seems to think this is fine.

Also, this bit from another thread seems like it may be important to set Connect Mode to D4 on the XPort server settings. Doesn't matter to me. I can get it to work for either C4 or D4. Don't know the difference, either, so there's that.

Re: super-cheap pick-and-place device with ~1 mil accuracy

bootstrap — Fri, 30 Jul 2010 03:52:21 -0400

mikeselectricstuff wrote:
bootstrap wrote:
mikeselectricstuff wrote:webcams are cheap - maybe just have a second upward-facing one to measure the relative alignment of the package alignment to the pads, then use this to correct the placement on the overhead one.

I'm not sure I understand the purpose. Are you trying to avoid the hole-array and rectangle templates? Or what? The scheme I described only has 1 webcam and is extremely accurate, so I must be missing something about your intention or line of reasoning. Please explain more completely.

Yes - to avoid the need for a template for every different footprint, and any need for accurate mechanics, e.g. to avoid rotation & drift issues between the template and the placement position.The templates will only work on BGAS, not with parts like QFNs which have no bumps.

The scheme I mentioned does not require a template for every different footprint. It only requires one template (area) for every pitch. For example, every BGA component with 1mm pitch is handled by a single "hole-array" with ~32 x 32 (or maybe 40 x 40) holes with 1mm pitch. No matter how many solderballs a given 1mm pitch BGA component has, we place it in the upper-left corner of the 1mm "hole-array". Yes, this still requires about 8 templates for BGAs, but not the hundreds or thousands of templates that would be required to support every BGA pattern.

What "rotation and drift issues" between template and placement position? Unless I'm missing something, the only precision that is needed is repeatability of the endpoints in the X-axis stage. When you move the X-axis stage all the way to the right, then to the left, then back to the right - that stage must end up exactly where it was the first time --- relative to the pick-and-place device (but NOT to the templates or PCB). In fact, that's the main beauty and attraction of this scheme (unless I'm missing/mistaking something important)... that nothing needs to be "measured" (by encoders). All that matters is, as long as the "full-left" position is always 50mm (actually, ANY distance) from the "full-right" position - the device places the component exactly. Yes, the component must not rotate on the vacuum pick-up tool, but why would that happen? Even pick-and-place machines with fancy encoders and upward-looking cameras move the component (real fast) between the upward-looking camera and final placement position. If THAT doesn't cause "rotate or drift" problems, why would anything about the configuration of this device?

However, I don't think the above is the kind of "rotation or drift" you mean. To attempt to expose the source of the misunderstanding (either you or me), let me make a statement that seems perfectly correct to me, but may seem totally insane to you. If this is what happens, we need to focus on this example more carefully to figure out who is making a mental mistake.

I claim the following. In step #9 we take a still image of the template where the BGA component was located a few seconds before. At this point, we know the BGA component is exactly 50mm to the right (along the X-axis) from the center of the still image we just took. We know this because that's exactly how far the X-axis stage moves when we move it to its "extreme left" or "extreme right" position. The image has also exactly captured the rotation of the BGA component relative to the X and Y axes, which are aligned with the rows and columns of pixels in the image.

Now, I claim the PCB can be removed from the teflon sheet, taken outside into your back yard and thrown around like a frisbee for a few minutes, then brought back inside and securely taped down to the teflon sheet again in an entirely different location and rotation compared to its original position and rotation on the teflon sheet. Now we perform the rest of the steps (step #10 to the end).

My claim is, the BGA component will be placed perfectly. My guess is, you think the enormous "drift and rotation" errors caused by grossly moving and rotating the PCB will screw up the process. Does this sum up our assumptions?

Let me try to explain why I take my [seemingly insane] position. When we move and rotate the PCB around in step #10 to make the still image of the holes in the "hole-array" lie on top of the video image of the BGA pads on the PCB, we must rotate the PCB (presumably by rotating the teflon sheet) until the X-axis of the "hole-array" is exactly aligned with the X-axis of the BGA pads on the PCB... otherwise their images would not align and correspond. The webcam has not rotated relative to the X-axis stage, so the PCB is now rotationally aligned in the exact same way (at the exact same angle) as the "hole-array" was previously... otherwise the two images would not align. Right?

Furthermore once the still and video images are aligned, we know the BGA component is exactly 50mm to the right (along the X-axis) of the webcam, because that's simply the way the device is assembled. Thus, when we move that stage 50mm back to its "extreme left" position, the BGA component is precisely located over the BGA pads on the PCB (that the video image was just displaying).

I know that's a long-winded description, but I hope it captures the point I'm trying to make. To me, the logic of this description seems solid and bullet proof (that is, lacking any logical/rational errors). Frankly, I was surprised when I first came to this conclusion, and suspicious of my conclusion until I had tried to find a fault in the logic. On a simple intuitive basis it doesn't seem possible to achieve something like this with no encoders, and in fact, no known distances at all (the X-axis stage can move any distance... 50mm is just convenient, but 48.53243mm is just as good), no alignment of the PCB with the X-axis stage, and only 1 webcam. What I think makes this work is that the steps of the described process make "certain repeatability of extreme-left and extreme-right positions" substitute for linear encoders. Seems like all we needed was a 2 position linear encoder to make this work. Well, that plus the pixels of the webcam being on the order of 0.0005" to 0.0010" on the PCB. So in a manner of speaking, the webcam plays the role of our 2-axis optical encoder - when combined with the described process.

Or so I still believe... until you set me straight?

You also seem to think this device doesn't work on QFNs and iLCCs (which are also QFNs, essentially). I'm not sure why you think this, unless you didn't understand what those square and rectangular cutout "templates" were for. These are the templates for QFNs any similar package.

The nice thing about QFNs is - your technique works (assuming the outline of the physical package is aligned with the component pads/contacts). We can assume this because the component pads/contacts run to the edge of the physical package. This eliminates the possibility of offset or rotation between the physical package and the pads/contacts.

Therefore, to place a QFN component, you simply drop it into the appropriate size square/rectangular hole/cutout "template", then perform all the steps described for the BGA. The only difference is, when you align the still and video images on your LCD monitor, you are aligning the still image of the square/rectangle template with the outer edges of the QFN component pads/contacts on the PCB. The principle is exactly the same. No need for "bumps", we only need the "outline".

If you're concerned about potentially needing a large number of square/rectangular cutout templates, note that technically and in fact we only need one large square cutout large enough to fit the largest QFN package into. We simply shove the QFN into the upper-left corner of this large square cutout "template", then align the still image of that upper-left corner of the "template" with the ends of the QFN pads/contacts its top-side and left-side in the video image. However, I'm pretty sure that we can machine (?or punch?) all existing QFN sizes in a reasonably modest size area of the SMT template plate. Again, I envision only one template plate to support all BGA and QFN components, plus a few others (like 0603, 0402, 0201, etc).

Okay, did I convince you? If not, tell me where I went wrong.