Posted 4/23/2008 06:23 (#363583 - in reply to #363066) Subject: Update...
We've done some testing, and it looks like we might be getting setup files written for fields and products, and we'll soon know about fertilizer Rx's. Should know on seeding Rx's later today.
However, I'm not quite sure that we will be able to make the Voyager export work with EASi Rx. We're still bouncing around options. The issue we are having is that every time we define a grower, farm, and field on the card, a new internal voyager identifier is generated. When that card is loaded into the monitor, the card is synchronized with the data that is already in the monitor. So, if your grower has exported his full setup into the monitor, he might have "Home Farm, Field 1" already defined, and it's internal number 147 (as an example). Then you publish a seeding Rx for him, creating the same "Home Farm, Field 1", but as a new entry onto the blank card, it gets ID 195 (as an example). Then your grower loads your new card into his monitor, and 195 is not in his monitor, so your version of the "Home Farm, Field 1" now gets loaded in ADDITION to his own version of "Home Farm, Field 1" that is already in the monitor. So, he'll have two Home Farms, with one Field 1 in each farm. If your grower hunts around and finds the right Field 1... the one with the Rx, he'll log his as-applied data to that field. Then when he unloads the card back into his AFS software, he'll now get the second Home Farm and Field 1, with the as-applied logged to a different Field 1 than he originally created. None of this is a good.
Summary... the AFS hardware was really designed to be tied to a single software source as a "master" copy. It is not well suited to having service providers generate Rx's that need to be merged into a set of grower supplied setup information, w/o the merge occuring within that "master" source. This is not unlike the GS1/GS2 architecture before the GS2 winter bundle was released, except the Deere hardware operated only off of the farms/fields on the currently inserted card. There wasn't the issue of merging into an existing set of farms/fields embedded within the monitor.
Clear as mud?
We are looking for ways around this. For instance, if your grower gave you his card as a "template", then maybe we could match your names to those that are already on his card, and create the new card with his ID's (use his 147 instead of creating the new 195). Or maybe we can find a way to just add Rx's directly onto his card? Or maybe your grower doesn't care about his own AFS desktop system for reading the as-applied data back, and he's willing to erase his monitor and just use the card that your create for him (the Deere scenario)? There are probably more options that will pop-up as we bounce it around with people that are more familiar with the AFS platforms.
In the mean time, we'll keep testing setup and Rx files that we create, as all else is a moot point if those don't work :)