File Types

Currently Fieldscorer4Android imports and exports using a comma-separated file format(.CSV).
Data is stored in an sqlite database file format, which can be access and modified using and external editor if necessary.
All image files are stored in the JPEG file format. Quality is dependant upon the camera built into the device.

Trait Files

Trait Files are currently the recommended way to set up trait information. A trait file can be imported to quickly set validation, date stamping, and other conditions for a trait to affect how they operate within the application.
A typical trait file has the following format:

TraitName TraitValRule DataType AutoProgressFieldLength IsDaysTrait DateStamp TraitUnits Connection
DTF 30..120 I 1 TRUE TRUE Days
TagColour Red,Green,Blue S 3 FALSE TRUE Colour

The trait dialog

The traits dialog is use to activate, add and edit traits.

Traits from the current trial file will be displayed in the list and can be selected for scoring or viewing using the checkboxes next to the traits. Read only traits can be used to display a trait value during scoring to be skipped during progression. Selecting a trait for scoring will add it to the scoring screen so that it can be edited for each plot.

The Add button on the traits dialog will bring up the full list of all traits currently in the database across all trial files. There are four options for adding traits.

  • New - Add a new trait that is not in the full list
  • Instance - Create a new instance of a selected trait to add to the current trial appended with an instance number
  • Select - Add the currently selected trait to the current trial
  • Today - Create a new instance of a selected trait to add to the current trial appended with the date

To edit a trait select the trait to edit so it becomes highlighted and select edit. See trait details below for more information about the options for editing traits.

Trait Details

Each trait contains additional information which will affect how trait scoring occurs.

  • Trait Name - The Name of the trait as it will appear when scoring. Traits are considered the same if the name lacks a space, is a different case, or has a double underscore separator. ie. plant height = PlantHeight = PlantHeight__2
  • Validation - Rule for validating data when it is entered. For numeric traits use range with a double dot separator eg."1..9" or "0.3..15.6". For String traits use a comma separated list eg. "Red,Green,Blue". NA will always be accepted as a valid value. Validation is optional, therefore leaving a blank value will accept any value that matches the data type.
  • Data Type - String, Integer, Decimal, Boolean or Photo
  • Progression Minimum length - the number of characters accepted before a progression to the next trait is triggered. Ie. For a trait between 1 and 9, a value of 1 would be set because the scores are 1 character long. Traits with no value will not auto progress.
  • Date Stamp - Store a date value every time the trait value is changes
  • Is days trait - For traits that calculate the number of days since planting or January 1. Eg. Days to Flower
  • Units - Units of trait to be displayed on the trait dialog
  • Connection - Connection settings for paired bluetooth devices. Some devices (height gauges) only require the MAC Address, whereas some devices (scales) may require start, end and poll strings.
    • Device Name - Device Name as per bluetooth connection pairing
    • MAC Address - MAC address of paired device. This is used when connection.
    • Start String - Prefix characters of a valid value (stable weight). Eg "+" or "S S" or "N"
    • End String - Suffix characters of a valid value. eg "g" or "kg" or "m"
    • Poll String - Space separated list of characters to send to get a valid value. For control characters use standard abbreviations .(eg "ESC P CR LF")
    • Specific - For custom features

Bluetooth Connections

There are two options in Fieldscorer for Bluetooth input. You can either make a device that works like a Bluetooth keyboard (or build your own android keyboard app) which adds a new line character at the end of each score, or you can connect a device using Bluetooth SPP and use the inbuilt connection options.

To use Bluetooth SPP, first pair the device outside of Fieldscorer using the Android settings Bluetooth menu.

Bluetooth Pairing

In Fieldscorer, import and open a trial file, go to the traits menu and add a new trait to use for scoring the Bluetooth (or edit if you already have it). Select the data type that best suits the trait and set validation if you like. Progression Min Length is usually not required for Bluetooth traits as the application will skip when it receives a stable input from the Bluetooth connection.

Add Trait Dialog

To set up the Bluetooth connection settings press the connection button to open the connection settings dialog.

If Bluetooth is switched on and you have paired devices they should show up in the device name list. If you press the device name button the list will be displayed. Once selected the MAC Address will be populated and which is what will actually be used when connecting. For a Bluetooth barcode scanner, no other settings should be required.

Connection Settings

For more complicated connections the input may need to be processed and output may need to be sent.

The start string and end string are the prefix for determine a stable string.
For example.
For a set of scales with continuous output, the start string might be “SS” and the end string might be “kg”.
The Bluetooth input might be:
S D + 3.345 kg
S D + 4.235 kg
S S + 5.065 kg
So the input would be ignored until it received the input “S S + 5.065 kg” was received, a + or - minus is removed by default but it can be added to the start string if necessary. If neither input is set then and input from the Bluetooth connection would be considered stable and would be added as a trait value as it came from the input.

Poll string is used to send a space separated list of characters to the paired device as an output. So the string “ESC P CR LF” sends the characters escape, P, carriage return and line feed to the device, which is a common poll string for many scales to print the value from a set of scales.

The “Specific” field if for customised functions as requested by users.