Junk Events kept in DAQ status after changing the number of configured ROCs

[vbe9cs]

Bug Description
After running a pedestal scan on the backplane with two ROCS installed when you attempt to run a scan with only one installed, pftool will say there are lots of errors with your data, however if you run this again it will no longer give you any issues. Note: this also happens when going from one installed ROC to two installed ROCS as well. may be related to the event occupancy of two as show in screenshots

To Reproduce:
Steps to reproduce the behavior:

1. After compiling pflib with newest version, powercycle backend
2. Go into pflpgbt and check the OPTO.FULLSTATUS
3. OPTO.RESET and the run FULLSTATUS again
4. If the FULLSTATUS output is agreeable (consult wiki), then go to GENERAL and run GENERAL.STANDARD_HCAL
5. Exit pflpgbt and run pftool with whatever correct .yaml file you use to configure it for 1 ROC.
6. RESET and DISABLE the DAQ, HARDRESET both the ECON and the ROC
7. Set the correct ROC(s) to RUNMODE Y, load the correct ECON .yaml config file and also set it to RUNMODE Y.
8. Go to TASKS.SETUP and run the PHASE_WORD_ALIGN and ALIGN_ECON_LPGBT commands
9. Go to the DAQ, SETUP and then set STANDARD and CONFIG commands with all of the defaults
10. Enable the DAQ with DAQ.SETUP.ENABLE (N for both options) and exit to EXPERT
11. EXPERT.FAST_CONTROL.SW_L1A and then return to DAQ
12. Once you have done all of this the status should be fine to take a PEDESTAL run
13. Powercycle your setup again, but then attach more ROC (s)
14. Repeat steps 2-11, however now your status should have the 0x51 size value for ECON0.QUICKSPY even though you have 2 or more ROCS attached.
15. Attempt to run PEDESTAL run and recieve pictured below errors, that then work if you take another run.

Expected behavior
We should either have no need to do a second pedestal run, or we should have a built in function to run a pedestal run whenever these settings get changed by enabling more or less ROCS attached to the backplane.

Terminal Print Out
For reference see the following screenshots before and after taking a bad pedestal run (and how this run "fixes" the settings)

Pre error filled run:

Post error filled run:

Please note that this run works with no errors and gives us reasonable data.

Environment:

• Rogue Bittware setup
• Firmware version: ldmxfw-dualtarget-zcu-102-20260512
• pflib version: 3.10.0

Additional context
all 4 backplane sections have a ROC plugged in, unsure how that could be affecting things. However this issue has been ran into while moving around 1 ROC on different HGCROC ports.

[tomeichlersmith]

Last week, with the EcalSMM, I observed a ECON0.NEXT_EVENT_SIZE: 0x0 after a 100 event pedestal run which was the first pedestal run after rebooting the computer to reset the firmware. Unsure how this relates, but I didn't want to forget it.