Pull "AreaServed" as a location area #8
Description
Is your feature request related to a problem? Please describe.
When polling for locations, i2ME does not use the "AreaServed" field of the MachineProductCfg.
This causes issues such as certain alerts for an area being missed, or data missing when running LFs, LDLs, or SBs.
Describe the solution you'd like
Either add"AreaServed" to "configLocationKeys" Progam.cs, line 109
or make "configLocationKeys" configurable via the config (With a default, of course)
Describe alternatives you've considered
Locations in the "AreaServed" could be moved to other parts of the MachineProductCfg file, but this does not apply when there is a large area served.
Additional context
Currently, i2ME when polling it's current locations finds 11 locations total:
USWI0455 USWI0777 USWI0775 USWI0441 USWI0723 USWI0455 USWI0575 USWI0346 USWI0733 USWI0237 USWI0380
However, with AreaServed, this would start at 147:
53002,53003,53004,53005,53006,53007,53008,53012,53016,53017,53018,53021,53022,53024,53027,53029,53032,53033,53034,53035,53036,53037,53038,53039,53040,53045,53046,53047,53048,53050,53051,53052,53056,53058,53059,53060,53064,53066,53069,53072,53074,53076,53078,53080,53086,53089,53090,53091,53092,53094,53095,53097,53098,53099,53103,53110,53114,53115,53118,53119,53120,53121,53122,53125,53127,53128,53129,53130,53132,53137,53138,53146,53147,53148,53149,53150,53151,53153,53154,53156,53157,53172,53176,53178,53183,53184,53186,53187,53188,53189,53190,53191,53195,53201,53202,53203,53204,53205,53206,53207,53208,53209,53210,53211,53212,53213,53214,53215,53216,53217,53218,53219,53220,53221,53222,53223,53224,53225,53226,53227,53228,53233,53234,53235,53237,53259,53263,53267,53268,53274,53278,53288,53290,53293,53295,53538,53549,53551,53557,53579,53585,53594,53916,53922,53933,53957,53963
and would cover my entire area.