Merge setting a short exposure before the frame rate when exporting a camera profile

A tower's scan grid belongs to that tower, not to the repo: the copy here
had already drifted from the one Staeffelsberg actually uses.

Before the next deploy to Staeffelsberg, move its grid out of the project
folder (scripts/tower-config move) - deploy.sh syncs with --delete and
would otherwise remove the file its config.ini points at.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

scripts/export_camera_profile.py

@@ -56,6 +56,11 @@ except ImportError:
 # about half the time, with no lost frames measured on either computer.
 # Binning goes to 1 vertical-first (the horizontal minimum depends on it), and
 # Width/Height ask for more than any sensor so the clamp lands on the maximum.
+# The exposure the camera already holds caps its frame rate too, so a short
+# fixed exposure is written before the rate, and auto-exposure is turned back
+# on afterwards. Without it, tower 111's camera, left at 3.5 s by the old
+# profile's 9 s auto limit, got a 'standard' profile clamped to 0.28 fps. A dry
+# run writes nothing, so its frame rate still reflects the old exposure.
 # The per-frame chunk data is what the keep rule reads; each item must be
 # enabled before chunk mode itself, which locks them.
 _RAW_COMMON = [
@@ -69,6 +74,8 @@ _RAW_COMMON = [
     ("Height",                     100000),
     ("PixelFormat",                "BayerRG12p"),
     ("DeviceLinkThroughputLimit",  250000000),
+    ("ExposureAuto",               "Off"),       # so the short exposure below sticks
+    ("ExposureTime",               1000.0),      # before the rate: see the note above
     ("AcquisitionFrameRateEnable", True),
     ("AcquisitionFrameRate",       1000.0),      # clamped to the camera's maximum
     ("ChunkModeActive",            False),