Alert.png

Notice: This page contains information for the legacy Phidget21 Library.

Phidget21 is out of support. Bugfixes may be considered on a case by case basis.

Phidget21 does not support VINT Phidgets, or new USB Phidgets released after 2020. We maintain a selection of legacy devices for sale that are supported in Phidget21.

We recommend that new projects be developed against the Phidget22 Library.


Click on the 2phidget22.jpg button in the menu bar to go to the Phidget22 version of this page.

Alert.png

User:Cora

From Phidgets Legacy Support

Links

My Sandbox and Notes

Documentation Log - Language Pages Casting Roles - All Templates - All Files (Uploads)

Support Hall of Shame

To be rolled into Application Guides and Primers (i.e. content extracted and then pages deleted):

To Be Done

App Guides

  1. Web Server on the SBC
  2. GoTo Mount for Camera or Telescope
  3. Portable Sensor Kit
  4. Controlling a DC Motor

Background Priorities:

  1. Clean up sentence above uses of Using a Phidget in Code General
  2. Language - Python - Mac OS
    • And other Mac OS sections on language pages
  3. Language - C/C++
  4. Clean up Links to General API
  5. Code Snippets for:
  6. Check device API pages - no pseudo code
  7. Commit
    • Android HelloWorld x 2
    • C HelloWorld
    • Java HelloWorld
    • Python HelloWorld
  8. Figure out licenses

And, ongoing:

Completed

Newly Done:

  1. Cleaned wiki of link references to Phidget Webservice, replaced by Phidget WebService
  2. Data Logging With a Thermocouple
  3. Temperature Sensor Primer#Emissivity (And associated Trac bug report)

Last Week:

  1. Language - Python - Code Snippets
  2. Language - Python - Linux section
  3. OS - Android
  4. Language - Android Java
  5. All old (red) Manual Installation links redirected to Windows Page
  6. OS - OS X - Structure, with content suggestions

Older:

  1. Phidget WebService
  2. OS - Windows - Structure and content suggestions
  3. Language - Java - Linux section
  4. Template:ExamplePseudocode Change to Hello World - Java Page
  1. Language - MATLAB
  2. OS - Phidget SBC
  3. 1072 0 - Getting Started
  1. Weather Station
  2. Simple Spatial Experiments
  3. Web Page on the SBC
  4. Use Phidgets Wirelessly with the SBC

Software Flow

Don't get lost!

  1. Getting Started for Device
  2. Pick Your Operating System
  3. Pick Your Language
  4. Examples, run and build
  5. Learn about General Phidget Programming
  6. Device Specific Pseudocode in API
  7. Code Snippets / Hello World pseudocode on Language Pages
  8. Write Your Own Code

Outreach

Edgy - Dependable - Accessible

"It's normal and cool to want to play, or build seriously"

- Mini robots driven by phone - Save money automating energy - Explore science with your kids or class - Do it exactly the way you want, customizing

Currently, how are gyros, accelerometers, GPS, etc used on phones for cool things? Maybe spy via Arduino + Android books? (These seem like hobby projects - we are more serious)

Strengths of Arduino:

  • They have Shields
    • Solution: VINT can probably improve our third-party interest if we expose the HW comm API?
  • They appear as not-for-profit
    • Solution: Whatever. They're in it for the money. Make it clear we're in it for the customer! And, for the coolness and fun factor.
  • Strong Community, which comes from open source, and being hard to use so people feel like they're learning
    • Solution: This will probably be helped by exposing the HW API comm in VINT, in which case we are open enough for third-party add ons
    • Solution: Primers! People will learn that way. Maybe mesh primers with app guides so that people can learn hands-on.
  • They have multiple O'Rielly books, magazines, Evil Genius books
    • Solution: Man oh man do we need some rad app guides.
    • Solution: More beginner stuff (physics classes, physical computing, experiments)
    • Solution: Phidgets are not just about learning, they are about building real, useable, durable systems (a photo book? a video tour?)

Strengths of Sparkfun:

  • Custom - Almost Digikey-level modularity
    • Solution: Basic hardware with lots of different versions for different needs
  • Scrappy and edgy
    • Solution: Hipsters can't ride long distances in tight blue jeans. We have endurance.
    • Solution: More creative, scrappy kits ('robot in a can')? Or maybe not.
    • Solution: More humour and wit in our writing for application guides
    • Solution: We can be more in touch with colleges and communities
    • Solution: Expose good relationships with our mfg community, help relationships to be built with others there
  • Strong Community, which comes from their staff diversity and connections to colleges

Strengths of National Instruments:

  • Dependability
    • Solution: Advertise our calibration and spec confirmation methods
    • Solution: Show many real-world uses
    • Solution: VINT can maybe interface with third-party sensors?
  • Market themselves as 'industry solution leaders' (white papers, trend predictions)
    • Solution: Don't do this. You're not the expert unless you're -really- the expert, and NI is not the expert, they're just another company.
    • Solution: Make it clear that we think the customer knows best. They know their systems the best, their requirements the best. We just help them.

Our possible additional strengths:

  • Expose our entire product development and mfg process
    • Allow and help our partners (i.e. China) to make new relationships directly with our customers
    • Share ideas and manufacturing/design experience with China to make new products and add some Sparkfun-like agility to customer needs
      • Make this an iterative process so we have some control and they have some learning and we don't suffer the three-hour-woodchipper effect

Random Software Mess

High-Level Pages

Guidelines and Goals

Primer Primer High-level philosophy for primer construction
Software Example Design What examples should contain, exceptions for different languages
Internal - Code Example Guidelines Formatting, style, variable naming conventions, interaction philosophy
Internal - Software Wiki Structure Guidelines A more formal layout of the structure and flow between Software pages
Application Guide² Guide to the Application Guides
Application Guides Internal list of most guides and some structure

Strawmen and Templates

Product Related Pages

Device List

Product Page - Template Base for Product stubs

Them Templates

General

Template:ContentNeeded Red box and bold
Template:ProblemSolution Red and bold text
Template:KnownIssues The tech support catch-all at the bottom of stubs

For Language Specific Pages

Language List

Template:LanguageSupport Full API, etc notes, support section at top
Template:UsingAPhidgetInCodeGeneral Introduction to how to write code (open, etc)
Template:ExampleCodeReasons Why you want to start with example code
Template:ExamplePseudocodeLogic For logic-only languages
Template:ExamplePseudocode For event and logic based languages

For Specific Device Pages

Device List

Template:RFIDPseudocode RFID pseudocode for API
Template:InterfaceKitPseudocode Interface Kit pseudocode for API
Template:UsingAPhidgetInCodeSpecific Sections before device specific API on product page

To Be Deleted

Nothing right now

Retrieved from "https://www.phidgets.com/docs21/index.php?title=User:Cora&oldid=18757"