Monthly Archives: January 2011

Thomas.DeVito 1.20.2011

Computer controlled amplifier:

We need 5k ohm digital potentiometers, more of those amplifier kits, and an i2c multiplexer to route the signal.  The other chips will be useful when we want to make every thing smaller.  The steps are limited but with the right configuration of resistors, I should be able to get the range we want.

I am going to have to double check the sizes to make sure they are all workable.  There may also through pin versions of the circuits.  Surface mounting isn’t too hard but it does mean that you need a PCB.

Strain gauge durability:
The BTP-5 strips have best spacing between the terminals.

Things I need to buy:

  • Fine soldering tip
  • Fine solder
  • Flux

Dong Shin 01.20.2011

  • PPM Changes
    • continue working on Financial Status
      • added Summary to FinancialStatusDataGrid
      • added FinancialStatusData.as
      • added DateItemRenderer – use dateFormat string to format, currently DD-MMM-YY and MMM-YY
      • modified CurrencyItemRenderer to handle Summary Data
      • layout is almost finished

Phil 1.20.2011

7:30 – 4:00 VISIBILITY

  • Pinged Kristie C. about a followup demo. We’re trying to schedule something for next week either here or at S2F
  • Pinged Anne about scheduling a + meeting
  • Testing Dong’s update. If everything works, I’ll roll it in this afternoon. Looks good.
  • Working on Project Tracker
    • Added ProjectInfoObject
    • Added EntryInfoObject
    • Added HistoryInfoObject
    • Added StatusInfoObject
    • Added TypeInfoObject
    • Abstracted RemotObject DB creation into base class, cleverly named ‘BaseObject’

Mike 1.19.2011

  • Finished entering in data for the sample report
  • Continued putting the framework together by adding in the module loading code and creating an example application that loads a module and creates instances of the classes loaded

Phil 1.19.2011

7:30 – 4:30 VISIBILITY

  • Got a big delivery of FP stuff yesterday. Brought it in along with the tweezers and ruler.
  • Project creation today
    • Added Menus
    • Added Project Panel
    • Added States

Thomas.DeVito 1.18.2011

Strain Gauge Durability Problem:

  • The optimal solution is to get more of the backed silicone strain gauges.  However these are a bit expensive ranging between $8-10 each.  If we didn’t have such excess of naked strain gauges, this might be a better option.
  • Another type of strain gauge is the foil type.  This type may be worth experimenting with before the productization stage because they are much less sensitive.  With our current strain gauges, I have to turn the amplifiers almost as low as they will go in order to get a good range of force.  One potential drawback is that, although I may be able to get a better range with this type, it may come at the cost of a higher dead zone.  These are approximately $27 for 5 which is still way more expensive then using our excess supply.
  • Since the main problem comes from the gold strands breaking, the most cost effective solution for more durability, is to use bondable terminal pads.  These are are essentially the same thing the backed strain gauges are attached to.  With these, I should be able to isolate the delicate parts from the strain of the heavier sensor wires, by having better anchoring points on the side of where the strain gauge is attached to the metal.  It may also be possible, to mount the gauges directly on the isolator and make a packaged gauge like the ones we have.  Doing this might also help dull the sensitivity the same way the backed ones do eliminating our potential need for foil type.
  • Some documentation on these terminals can be found here: http://www.omega.com/Pressure/pdf/Bridge_Completion_Resistors_RES.pdf
  • I need proper measurements to determine which ones to get. I think it should be about the same size the prepackaged ones we already have.  I don’t think having smaller spacing would be very solder friendly.

Formula for strain gauge Gauge Factor.  Just found this, might come in handy.

GF=frac{Delta R/R_G}{epsilon}
ΔR is the change in resistance caused by strain,
RG is the resistance of the undeformed gauge, and
ε is strain.

Phil 1.18.2011

8:30 – 4:30 VISIBILITY

  • Larry needs a VISIBILITY architecture diagram? Yep. Working on that. Done.
  • Sent Christine a snapshot of my User Settings
  • More work on the project tracker. Finished login.

Mike 1.18.2011

  • Working on porting all of my sandbox and other segregated code in to several mavenized projects that are shared on SVN and making example apps for parts of the code:
    • Started with the basic ones stuff, the logging screens, config loading, and data handling stuff
    • Added styles and skinning code + example app
  • Got an email from Alan with new report data, working on hardcoding that in to a quad chart prototype

Christine 01.17.2011

My adventures in the world of Windows continues.

  • Ended up getting a windows laptop. Spend day configuring (and re-configuring) it. After getting FGM environment set up, I was able to successfully run MavenAssist without the funky errors I was receiving on the other laptop.
  • Before testing AirFileImageAppMaven, I took a look at the configuration and user settings tab in Maven Assist. I notice that my slashes are combined. Ex: Under Configuration, Maven Home is C:Applicationsmvn3.0.2bin/mvn.bat. And under my path, all Java’s jre6 directories are using forward slashes (unix-like), and all of the other directories use backslashes.
    Along those same lines, under User Settings, the path to my Settings.xml file is using a combination of both backward and forward slashes (poking around, I found that in UserSettings.java there is no check to see if OS is Win or Mac & automatically it appends conf/settings.xml, which explains this forward slash). I also clicked ‘Validate’ to see if it would work and received “Java Session 1.6 is invalid!” I’m sure it’s the wonkiness of these slashes.
    So for the Win users out there, why would this slash change be happening? Is there someplace specific I need to check/modify?
  • That being said, and not being sure about the forward/backward slash bit, I still gave the AirFileImageAppMaven a go. Fail. Figured it has to do with the slash issue, but I wanted to check it either way. When I went to set the POM file I got a “Error on Line 1 of document: Premature end of file. Nested exception” and Eclipse was showing a NullPointerException.

Phil 1.17.2011

8:30 – 4:30 VISIBILITY

  • Helped Mike with getting Dong’s Data Manager to compile
  • ProjectTrackLite
    • Flex client project is up and running
    • Java server poject is started and compiling
    • Getting the user remote object to behave. Ran into some trouble geting the amf messagebrokjer to behave. The most important thing seems to have been that the blaze jhar files wer not dependencies in the pom. After some tweaking, that seems to have gotten the instance successfully deployed by Tomcat and is working.
    • Getting the improved config manager working. Done. All you have to do now to access a value in the setupModel.xml file is run the ConfigLoader and add a listener (and function) for the values you want to watch.

Thomas.DeVito 1.14.2011

Repairing the hand

  • Attached strain gauges to the bottom side.  Will start wiring on Monday.

Learning Electronics:

  • I am about halfway through the book now.
  • Multiplexer was the word I was looking for the other day when we were talking about the i2c bus.  I was surprised that the bus did not need a multiplexer in the diagrams I saw.  I think the reason a multiplexer is not needed is because there is a small one inside the i2c slave devices controller.
  • Finished chapter on numbering systems, Binary Arithematic, and Boolean algebra.  This was mostly review of things I learned in COSC 101.  There are some techniques in the boolean algebra section which you can use to simplify the amount of comparisons needed to reach a desired result.  In electronics this means getting from A to B with less transistors.  In programming this could be useful in making the program run more efficiently.

Other Experimentation:

  • Assembled another bridge to test the circuit board type strain gauges.
  • Attached the second one to the test stick.  The glue we are using is made to work with this type of strain gauge and for whatever reason seemed to dry much fast while in contact with the insulator used.
  • Soldering wire to the leads is a bit tricky but is a much less delicate process then trying to wrap the unpackaged strain gauges around the wire.
  • Was worried that these strain gauges would be less sensitive but it seems that they are just as sensitive and that they play better with gain and offset adjustments better(more consistent results).
  • Seems very durable.  I pulled on the wires harder then I would ever intentionally pull on them and they did not budge.  No need to put a think layer of epoxy on it,  only a small amount of glue would be needed to insulate the connection to prevent shorts.
  • One side of the stick was already insulated the other was not.  I did not add any insulation to the side that didn’t have it and it seems fine.
  • Since we don’t have many of these stain gauges,  I still plan to use the standard type for this prototype.  However, if I have to repair this one again, as well as future pr0totypes,  I would like to use these prepackaged strain gauges due to their ease of application, increased durability, and greater aesthetic value(no big glob of epoxy needed).  There are many sites that sell versions of these but the ones we have are really nice because they have big leads that are easy to solder to.  If you can remember where you got them from tell me, otherwise I will try to find something equivalent.
  • This test stick will be used for experiments with the tactile/audio feedback system once I get the amplifiers and usb-i2c device sometime next week.

I think Clift forgot about me…. 😦  Hopefully he will come to the lunch Christina planned next Tuesday.  Its no big deal, gives me some time to read this book so I can ask more complicated questions.

Dong Shin 01.14.2011

  • PPM Changes
    • changed the way Create New User window comes up. It now comes from PPM Main instead of UserManagementPanel
    • working on EdiableTableDataGrid….
    • created TableDataDataGrid for editing, removed old datagrid
  • checked in DataManager to svn://fgmdev.com/trunk/Sandbox_folders/DONG_SANDBOX/DataManager
    • DataManager – parent pom
    • DataManagerClient – Flex client
    • DataManagerServer – Java Server

Christine 11.13.2011

  • Continued setting up win machine
  • Receiving weird error message in Eclipse: “The Maven Integration requires that Eclipse be running in a JDK, because a number of Maven core plugins are using jars from the JDK. Please make sure the -vm option in eclipse.ini is pointing to a JDK and verify that Installed JRE’s are also using JDK installs.” Then in the console window I’m told “Eclipse is running on a JRE but a JDK is required.” And I know for certain that the latest JDK is installed and set in the path.
  • One solution is to add a -vm argument to the Eclipse.ini file. That didn’t make a difference.
  • Another solution was to be sure Maven is not set up under C:Program Files b/c the space between ‘program’ and ‘files’ can cause an issue with Eclipse on windows. Next step is to remove all of the sw for the dev. environment from “Program Files” and place within a non-spaced directory.