Category Archives: Feldman Project

Phil 8.9.2010

7:30 – 10:00 VISIBILITY

  • When checking over the query logs this morning, found that Paul O. Had spent most of Friday using VISIBILITY. He made 133 queries in 9 or so hours, spending most of his time on the LOTR and cars examples
  • Went over status of PPM with Dong. We’re going to aim for Wednesday to walk through the new changes.

10:00 – 3:30 FP

  • Working on reading the sensors. They seem to be working well. Working on calibration code – done
  • Making a bi-linear normalizing, since there seems to be a big difference between pushing up on a sensor and pushing down.
  • Update graphics to show new axis

Phil 8.6.2010

7:30 – 11:30 VISIBILITY

  • Meeting with Trish and Chris
    • Tabs in Financial Entry should read “Year 1″, Year 2”, “Year 3” etc., to avoid confusion between appropriation year and budget year
    • Still not starting FY in October
    • Whenever a reported obligation out outlay is less than 99.9% of the (calculated) goal (currently not visible), a dialog with Trish’s questions should come up. There is shared data between obligation and outlay reports for a given month.
    • Dialog should be smart enough to know if an obligation or outlay value is not applicable in a dialog, since one or the other or both may be under the estimate.
  • Responded to Paul O’s questions about how to interact with the report builder.
  • Went over the meeting results with Dong, and gave him Trish’s “5 questions”.
  • Went over the rough layout of the visibility system with Kiel.

11:30 – 3:30 FP

  • Working on fingers. Building the ServoMotorController class. Done.
  • Had to wait for the servoController class to initialize before getting the handle to the motors.
  • Had to initialize and engage all axis in the ServoController. I could do this inside the ServoMotorController.
  • Need to adjust speeds and ramps for the servos

Phil 8.5.2010

7:30 – 12:00 VISIBILITY

  • Sent off CATWALK memo
  • There is some demo activity on VISIBILITY, so we’ll how that develops
  • walked through PPM with Dong
  • Burned a new disk for demo tomorrow

12:00 – 3:30FP

  • Added step-to-angle conversion to StepperController
  • Couldn’t get the servo motors to move. After looking closely, I realized Tom had flipped the plugs on the controller header, so the motors were wired backwards. Fixed. Next is to try talking to the fingers in code.
  • Added “home” command to let the fingers and other motors reset.

Feldman Project Strain Guage Calibration

  • At first I noticed there was a strange thing where the voltage wasn’t constant.  I think this was simply because I was moving the tester because once I found a better positioning for the probes it seemed to stop.
  • Finger 2 needed its strain gauges reversed due to the fact that you want low sensitivity and need to up the offset.  The way it was set up it was balancing to the bottom end and it couldn’t be fixed because the offset was all the way up while gravity was forcing the voltage down.  Anything fighting gravity need to have negative offset up positive offset down unless you want it to be ultra sensitive by turning the gain up.  Even in that case I think this orientation is still better.
  • It is possible when interacting with the elevation to accidentally move the wrist.  I don’t think this was because of loss of holding torque but because the linkage isn’t connected to the motor tightly enough.
  • Overall sensors seem to have very good response range. Fingers are pretty sensitive even with gain all the way down but still in good range of force.  Elevation is the hardest to move but
  • Displacement for each sensor goes as follows
  1. Finger 1: up = negative, down = positive
  2. Finger 2: up = negative, down = positive
  3. Wrist: forward = negative, back = positive
  4. Azimuth: right =negative, left = positive
  5. Elevation: up = negative, down = positive
  • I don’t think we need to shield the wires at the moment but once the motors are moving instead of just holding we might find it necessary.  It is going to be hard to tell though because motion will probably cause fluctuations in general.

Phil 8.4.2010

7:30 – 9:30 – VISIBILITY

  • Made and account for Paul O. and sent him an email describing VISIBILITY
  • Sent Clift a writeup describing my understanding of the Paul O. project.

9:30 – 2:30FP

  • Going to start with holding torque on the wrist and then work on talking to the fingers
  • Got all the motors working, and moving to a home position
  • Built a servo motor controller class, but still trying to figure out how to deal with up to 8 axis.

2:30 – 4:00 OH/Savage Mill

  • Meeting with Larry and Steve to go over the new space

4:00 – 5:00 VISIBILITY

  • Put together CD for Brian WRT CATWALK billing

Strain Guages

  • Attached 10 strain gauges
  • Wired all but 2 “hardest” ones(can only strain my eyes like that for so long)
  • Tested horizontal axis strain gauges.  Need to turn gain all the way up to get significant readings, however, there was not nearly as much leverage as there wil be with the whole arm attached.
  • More testing tomorrow and if all goes well seal it with epoxy

Phil 7.9.2010

7:30 – 11:30 VISIBILITY

  • Responded to Yonald’s email. Tentative meeting is Tuesday at 2:00
  • Sent of an OZONE ping to see about getting VISIBILITY OZONE-blessed
  • Printed out the OZONE overview to bring here
  • Reading OZONE doc
  • Burned new PPM to disk

11:30 – 3:30 – FP

  • Brought in the KF prototype
  • Wiring up motors (Documentation is here: http://www.phidgets.com/documentation/Phidgets/1063.pdf).
    • Stepper motor wire pairs are (red/blue) and (green/black). Wired up as A/red, B/blue, C/green, D/black
    • Wrist Motor number = 92693
    • Top finger is servo 0
    • Bottom finger is servo 1
    • Azimuth is 92795 – might want to reverse wiring
    • Need to move pivot point in on wrist linkage

Phil 7.8.2010

7:30 – 1:30 VISIBILITY

  • Deployed the new network data source and Greek icons.
  • Beat on the SSL problem for a while
  • Sent Yonald C a note about networking, he wants to set up a meeting/demo for next week
  • Modified the network generator so that it outputs status and lat/long
  • Walked through Dong’s changes. Test and burn a new disk
  • Gave Mike some Tasks
    • Adda “New Widget” Button to the Wap and the Status panel. It should create a query of the form “SELECT foo, LAT, LONG WHERE (foo = ‘bar’ AND lat = 13.72 AND lon = 48.28) OR (foo = ‘baz AND lat = 12.38 AND lon = 43.7)”. The equalities in the parentheses’ define a selection on the map. If you want to get fancy, dragging a rectangle to select would be pretty cool too. This makes all the graphical components behave in the same way.
    • Bug Fixes for AdvancedQueryWidget
      • The status display gets confused with blank rows
      • Sometimes names don’t show up in the status pane after they have been selected. Let’s say I have two columns – name and status. If I select name, the names don’t show. If I then select status, the status’ show. Selecting name again now shows names
      • With the new data set, the attraction forces are two high, and the nodes bounce around until the settings are adjusted. Can you look into adding a threshold clamp that keeps that from happening?
      • Are the force settings saved when the panel is saved? They need to be.

1:30 – 3:30 FP

  • Making new, stronger linkages – done

Phil 7.6.2010

7:30 – 1:30 VISIBILITY

  • SSL for Firefox is misbehaving. Waiting for that to be fixed. All the deployed apps are working fine though
  • Catching up with Dong. Looks like I’ll demo the version installed last week
  • Working on the “Sailor” display
  • Burning a new Vis disk
  • Power failed at Columbia, went to the client. Spent a few hours doing the newest Visibility deploy. Since my certs were misbehaving, the svn transfer trick didn’t work any more. Joe set me up with a remote disk which works very nicely.

1:30 – 3:30 FP

  • Reinforced the azimuth component of the main support so the strain gauges should work better
  • Added the base
  • Discovered that the arms that come off the large motors are not strong enough to grip the shaft. Part of this is that there is no standard drill bit that corresponds to 8mm, so the holes for the shaft were too large. Wound up having to order a metric drill set from McMaster. You would think that Harbor Freight would have that, but nope.

Phil 7.1.2010

7:30 –  12:00 VISIBILITY

  • Deployed the new PPM, but the server was having SSL problems. Joe got that fixed, but in a semi-related side issue, the meeting was postponed
  • Rolled Mike’s changes into the new deployment package.
  • Tried restarting my computer to see if that’s what causes my out of memory exception. No joy. Going to try deleting the projects and reloading them. Wow! That worked. WTF?
    • Setting the project up as a server app again – let’s see what that does…
    • Changed the .flexProperties to make this a server project: <flexProperties flexServerType=”64″ serverContextRoot=”” serverRoot=”C:/Program Files/Apache Software Foundation/Tomcat 6.0/webapps/VisDashViewer” serverRootURL=”https://127.0.0.1/VisDashViewer&#8221; toolCompile=”true” useServerFlexSDK=”false” version=”1″/> – still working…
    • Changed the output folder: C:Program FilesApache Software FoundationTomcat 6.0webappsVisibility3 – still working
    • Enabled HTML wrapper – still works.
    • Chalk it up to a FlexBuilder unreproducible result.
  • Virtually attending Aaron’s presentation

12:00 – 3:30 FP

  • Mounting fingers
  • Building armrest

More Wheatstone Bridge Notes

  • Wheatstone bridges tested and working.  The 5th one had a loose connection on the positive signal line but is working now.
  • Made a slight error  in orientation.  The Amplifier is actually in the reverse order of the bridges.  The bridges go E+,S-, S+, E- and the  amplifier is E-, S+, S-, E+.  Tis means you have to cross the connections.
  • All terminals are wired and ready to be attached to strain gauges and amplifiers.
  • Best to position it so Amps are on the left side of the bridge, where ever we end up placing it on the unit.  This allows you to have testers in your left hand, while making calibration adjustments with your right.  Doing this in reverse is annoying to say the least.

Wheatstone Bridges complete

  • Completed 5 wheatstone bridges.
  • The connection go from left to right with the side of four on the bottom: SG 1 connection A, SG 1 connection B, SG 2 connection A, SG2 connection B, E+, S+, S-, E-.
  • Ran out of space on the last one so I had to put it on the other side the connections are still in the exact same order as the bottom, its not mirrored.  It is a little messy compared to others but hopefully it works.
  • Still need to wire the terminals but the hard parts done.

Phil 6.29.2010

7:30 – 11:00 VISIBILITY

  • Verified PPM meeting with Trish for 9:00 Thursday
  • Script runner for Querylog is working fine
  • Looked some more for the source of my memory problems. I’m thinking that it might have to do with where I’ve put the images folder. Sent a note to Mike asking him to try it out in his environment.
  • Burned a new copy for Scripting

11:00 – 4:00 FP

  • Adding the wrist actuator and possibly the fingers
  • Got everything up to the finger mounts installed. Next will be the fingers and the base.
  • KF System with linkages and finger mounts

Feldman Project Wheatstone Bridges

  • Using resistors which are significantly higher then the resistance of the strain gauges, makes the bridge not able to be balanced.
  • Using resistors which are significantly lower then the resistance of the strain gauges, makes the bridge to sensitive.
  • If we ever have a reason to needs something to be ultra sensitive, 1k ohm resistors would be good otherwise, stick with 1.3k ohm.
  • 5 more Wheatstone bridges in production.  Need more 8 prong terminals and 4 prong connectors to  complete them (which I’ll get tomorrow).

Phil 6.28.2010

7:30 – 4:00 VISIBILITY

  • Sent Trish a note to reschedule meeting from Friday to Thursday. After getting to the office, it looks as though the meeting was already scheduled for Thursday 0900.
  • Went over the change requests with Dong
  • Chasing the bug that clears out the interval_minutes when scripts are run manually. It looks like the issue is when a script is updated, interval minutes is blown away. Fixed.
  • Was looking at Mike’s changes to the network widget, and made the suggestion that rather than selecting single lines in the table, that we use the name field (either in the chart or the selected line on the grid) to create a query that preserves the networking information, along the lines of:
    • select `Name`, `souRce`, `targeT`, `icon`, `text` where (Name = ‘Jason’ or souRce = ‘Jason’ or targeT = ‘Jason’) or (Name = ‘Mary’ or souRce = ‘Mary’ or targeT = ‘Mary’) or (Name = ‘Mark’ or souRce = ‘Mark’ or targeT = ‘Mark’)
    • This gets us away from having to deal with the uid as the means by which we determine what rows we’re getting and allows for a network-based drilldown into the data.
    • Maybe this means that instead of having the query be added to the data page, that we build the query in the network view using a “new widget” button like for the other charts.
  • Pulling slideshow off into its own SWC. I’m pulling a lot out of vis2, so if anyone does any work in there, please let me know!
    • Having huge memory leak problems compiling the app now that I’m including the slideshow library.  Compiles fine with maven.
    • Interestingly, the swc compiled using maven is 2781kb, while the flexbuilder version is 2783 kb.

Need to order