AMS mapping generally doesn't work and definitely not like BL intended

[synman]

needs a full revamp based on learnings to date on how ams mappings should work.

• available mapping entries are based on the filaments loaded in BS when the model is sliced
• a mapping value of -1 means no AMS spool is selected for that filament entry
• populated values correspond to the AMS slot # (base 0) for that filament entry
• mapping entries are plate specific

[synman]

one easy work around for this is to use the overwrite feature BL added to BS recently....