In the 2070 world, users can use either a 2070 with a 1b/1E CPU, 2070 with 1C CPU, ASC/3-RM or Cobalt-RM, each with a different I/O map. When users change or upgrade the controllers, whatever I/O map they started with, continues to get downloaded to the newer controller. I've had several controllers go into flash when a different type controller is placed in the field and the DB is downloaded, either through central command or field download request. This is a safety issue, and needs to be addressed. A radio button on the central /upload/download selection screen would be the easiest solution in my opinion. On a remote download request, blocking the I/O map download would be safer.