Show Posts
Pages: [1]
1  Using Arduino / Project Guidance / Linear Light Sensor some help with planning and understanding on: February 22, 2014, 04:08:22 pm
I'm trying to setup the IX503 linear light sensor (Datasheet attached).  This is the first attempt at using a digital sensor that outputs more then one data value at a time. So would like some help making sure I do it right. At $3 a piece I bought a few extra just in case I mess up. Any help would be appreciated.

Question 1
Looking at the circuit I notice it requires electrolytic capacitors. I've never used them before and am reading about them. I'm unsure what makes them required over a ceramic or tantalum capacitor that is rated to the capacitance and can handle the prescribed voltage. I know not all capacitance materials are equal (Mica / Quartz can be more stable over a broad temperature etc.) but I don't know the advantage of an electrolytic capacitor.  Especially at such a low capacitance (10 uF / 22 uF) as their main use seems to be easily scaling to large capacitance values.

Question 2
The white sheet makes it seem like the RSSW pin should be set to ground if I want Internal RS depending on how I want my out going pulses to be. The thing I don't get is why would I choose to have the RS External? Those pulses look hella weird so I don't get why I would even consider doing that. The default configuration circuit also seems to have it disabled so ... ya ... why would I want signals like in the external mode?

Question 3
Looking at the ROG clock it seems to be just used for a single pulse to trigger a read from the chip. Is that correct? Or do I need a 1 MHZ clock on it also? White paper confuses me a bit on that. If I have to trigger it myself will a simple PIN ON -> PIN OFF cycle do it?

Question 4
I think this IC might only read (Light or No Light) as I didn't notice it said B/W on it at first. If so it will still work for my application but didn't notice that in the datasheet at first ... is that what it looks like to everyone else? As looking at the mosfet in the circuit .. that would be a pure digital signal with no voltage difference ... just On / Off if I set it up like that. Is that correct?

Looking at a few other CCD's that are like $8 a piece ... they seem to vary the voltage and not have the mosfet there ... so ya : / think that is correct.

2  Products / Arduino Due / Problem installing Due driver on: January 23, 2013, 04:22:02 am
Just got my Due and excited to start but after following the exact instructions at http://arduino.cc/en/Guide/ArduinoDue I'm unable to install the driver.

The issue is when I redirect to the folder with the drivers I get an error "Windows was unable to install your Arduino Prog. Port". Looking at the driver file I assume the driver it needs is Arduino USBSerial since none of the others seem like they would work based on their names but unsure how to install that driver specifically.

Windows 7 which it is confirmed to work with so I'm unsure what to do.
3  Products / Arduino Due / Re: Motion Capture with Due on: December 26, 2012, 04:23:46 pm
I understand it gives a number that is mapped between two values. That's how most electronic sensor's work even if they have to be ADC'd first.

Absolute orientation is using the angle values to calculate an actual vector direction in your reference space. So how does 'up' change from 1 point to another (or forward or whatever direction). It is important to have that information so rotation information can be calculated on the PC. A lot of the whitepapers I read like the gyro's only outputs angular velocity not angular position. If the IMU's output the actual orientation then that makes everything really easy for that. I have ordered a few parts to play around with to make sure I can get 1 sensor working correctly at the specs I want before I do several. I was just inquiring on what to expect in that regard.
4  Products / Arduino Due / Motion Capture with Due on: December 26, 2012, 03:38:37 pm
I'm thinking it should be possible but i have only basic arduino experience (few wireless sensor projects but that's it). Arduino is just going to organize the data each frame and send it over wifi to a PC that will do all the heavy lifting. 14 bytes per vector component with the sensors I plan on using which we will round to 16 bytes since I might pad the values in memory should be 16 x 6 = 96 bytes per sensor x 18 sensors x 60 fps x 8 bits per byte = ~830k bits per second (103.7k bytes per second). Seems well within the range of a xbee. Is that reasonable with a Due and Xbee combo?

Thing is at my work we use Magnetometers and Accelerometers to calculate orientation but motion capture suits in the industry seem to do accelerometer and gyroscopes which confuses me since you need a calibrated reference to work with a gyroscope (I think) because it just reads changes in rotation not absolute rotation (unless I'm not understanding something by reading the white pages on different ones). Anyone who worked with a accelerometer and gyroscope able to explain to me how you get absolute orientation using that combo? I have some parts in the mail so I could probably answer the question myself in a week or so but always like hearing from people that know a bit more than me.

Pages: [1]