Difference between revisions of "Bulletin-board"

From Wiki at Neela Nurseries
Jump to: navigation, search
(^ New Section)
m (^ New Section)
Line 215: Line 215:
  
  
 +
 +
=== [[#top|^]] to edit ConfigTable dot csv ===
  
  

Revision as of 20:18, 3 May 2019

Neela Nurseries bulletin board
Quick posts to share


Computer tower case search


^ Common Microcontroller Peripherals


^ HP laptop model 15-ac133ds


^ Olimex products - dev boards and programmers and adapters

https://www.olimex.com/Products/Components/Connectors/MICRO-USB-OTG-ADAPTER/


^ APHIS Contact Information

APHIS-Seattle Inspection Station<Seattle.Inspection.Station@aphis.usda.gov>	Wed, Oct 31, 2018 at 4:29 AM
To: "ariliriswebmaster@gmail.com" <ariliriswebmaster@gmail.com>
Reply | Reply to all | Forward | Print | Delete | Show original

Hello,

A seed shipment of yours just arrived at the Seattle Plant Inspection Station from Denmark. Please send a list showing the botanical names of all seeds in this shipment, including species. The list also needs to show the country of origin of all seeds. Thank you.

 

Regards,

 

Steve Zoelle

Plant Health Safeguarding Specialist

SeaTac PIS

USDA APHIS PPQ           

SeaTac, WA 98148

Cell Phone – 206-960-0931

Office – 206-878-6607

Main Office – 206-878-6600


^ helleborine orchid and others


^ Desert and succulent plants






^ New Section

Materials to gather:

    [ ]  AG04 sensor module with correct ID resistor
    [ ]  printed barcode of text string "AG04"
    


At the tester:

Dev sessions on GWN Sensor tester:

To perform development work on the Gas Platform Sensor Tester, host alta-gwn-sensor.veris.com, a necessary first step is to open a terminal window like Xterm and do the following steps:

   $ gd1

   $ sudo link-to-dev

   $ ls -l

The first command is a local "directory bookmarking" shortcut to change directories to the Sensor Tester's share directory. The GWN Sensor Tester reads a couple of run-time config files from this directory.

The second command is a name of a local script, which redirects a Unix-style symbolic link to point from Production tester's version of the gas sensors ConfigTable.csv file to the present branch version of this file. By present branch I mean the 2019 Q1, Q2 branch in which we're extending the code to support new refrigerant sensors AG05 and AG06, and the new dual-gas sensor AG04.

The third command above give a long format directory listing. I use this to confirm that the symlink points to the branch ConfigTable.csv file as opposed to Production's version of the file in the share directory itself.

When finished with a development session at the test station, use the following commands to point the symlink back to Production ConfigTable.csv:

   $ gd1

   $ sudo link-to-production

   $ ls -l

If you have left the original terminal window open and at the working directory of the station's /usr/local/share/gas_platform or similar, there's no need to invoke the local bookmarker alias named `gd1`.


To Test AG04 Stub Function

To test the AG04 calibration function, which is as of 2019-05-03 only a stub, you will need on hand the AG04 bar code to read at the station, and an AG04 sensor module with correct ID resistor. If by chance the sample AG04 module(s) you can obtain have an incorrect ID resistance, see notes further in this step about how to edit ConfigTable.csv to temporarily reflect the found ID resistance in a given sensor module type.

To test the stub function on the production floor host alta-gwn-sensor.veris.com, open a terminal window and use the local shortcut `gd20` to go to the directory of the Unified Tester branch for 2019 new sensors:

  $ gd20


After this step, start the GUI by typing:

  $ ./gas-platform-unified-tester


Note: the <TAB> key pressed during typing of a program name or filename will auto-complete the name, as soon as the typed part is unique among files in the current directory.

Once the GUI main window appears, there will be some scrolling text output in the parent or controlling terminal window of the GUI. This is normal, and it means also that the GUI is ready to receive a top level part number from the bar code reader attached to the host PC. Use the page taped above the ventilation hood's sliding front door, to scan "AG04" among the five or six codes there.

Confirm that "AG04" appears in the main window's upper line edit box. If there's an unknown part number scanned, this line edit will show the brief message "Unknown type".

Once the part number AG04 is accepted, seat the sensor module in the fixture and close the lid. When the lid is closed, the GUI will take a resistance reading across appropriate test points of the sensor module, and will indicate whether a correct matching ID is detected.


If all is working at this point the main window's 'start' button will become enabled, text turning full black from grey in color. Click the start button once. Now note the messages which appear in the controlling terminal. There will be a lot of informational and diagnostics messages. At some point in the first twenty seconds or so, there will appear a line or two of text indicating "STUB ROUTINE FOR AG04 SENSORS". When you get this far, you're poised to start making code additions to the new calibrating routine.


^ to edit ConfigTable dot csv

- STEP -

- STEP -