Error Message in CLI

[esteamed]

I am running xilo FC, Had to purchase a replacement fc to troubleshoot an issue I was having with quad not arming. Loaded my program into the CLI that I have been using forever got all these errors:
###ERROR IN resource: INVALID RESOURCE NAME: 'CAMERA_CONTROL'###
# set osd_warn_batt_not_full = OFF
###ERROR IN set: INVALID NAME: osd_warn_batt_not_full = OFF###
# set osd_warn_core_temp = OFF
###ERROR IN set: INVALID NAME: osd_warn_core_temp = OFF###
# rateprofile 4
###ERROR IN rateprofile: RATE PROFILE OUTSIDE OF [0..3]###
# rateprofile 5
###ERROR IN rateprofile: RATE PROFILE OUTSIDE OF [0..3]###
# save
###ERROR IN save: ERRORS WERE DETECTED - PLEASE REVIEW BEFORE CONTINUING###
###ERROR IN save: PLEASE FIX ERRORS THEN 'SAVE'###

Background: The drone is run in my classroom by students who can't fly well so I have changed the throttle limit to help handle the power, thought this might be an issue? I run between 12 and 18 of the same drone with the same program for each one, I have not received this error before and I don't understand why the new fc would be giving me this error.

Tried: The second replacement fc does the same thing. Tried flashing the board again, still see error. Put in old board reloaded program, no error (just wont arm but beeps are all there and motors run when connected to BF:

# set throttle_limit_type = SCALE
throttle_limit_type set to SCALE
# set throttle_limit_percent = 50
throttle_limit_percent set to 50

 

[VolatusDrones]

Since you said its a program you have been using forever I believe Betaflight may have updated some of their older parameters in a newer version. While I am not 100% sure, I had something similar happen to me in the recent switch to iNav 6.0. In a wing FC i had used consistently for months, I updated the firmware to find a bunch of old parameters to be removed and the new version did not know what to do with the extra CLI inputs and gives them an error. I believe there is a resource that lets you paste older iNav CLI in to be changed to the new version, though I'm not sure something exists for BF code. Not a perfect answer but if you can downgrade the BF configurator it may fix this problem.