I have tried several configurations on using both PWM and SPI from encoder to controller, and get no data from the encoders.

This is similar to https://forum.basecamelectronics.com/index.php?p=/discussion/comment/9520#Comment_9520, which appears to be unresolved.

I bought this https://www.iflight-rc.com/index.php?route=product/product&product_id=233&search=8028 kit. Which has the AS5048A encoder and the SimpleBGC 32 Extended controller ( https://www.iflight-rc.com/index.php?route=product/product&path=25_95&product_id=276 ). I have updated the board to '2.63 b0 Extended + ENCODERS' from GUI v2.63 b0.

For PWM I hook up to the v+, gnd, and rc-p/fc-p/fc-r on the controller using stock included harnesses

For SPI I hook up to the three SPI ports built into the controller using stock included harnesses

Here is the debug for the PWM connection (skip autodetection checked or unchecked):
----------------------------------
Device s/n: 01239f8b8584d442ee, MCU s/n: 38363020015734591b002000
Firmware ver.: 2.63 b0, board ver.:3.6
error:2
assert_line: 0
assert_file:
COM errors: 3
Encoder[ROLL] type: AS5048A,B (PWM)
read errors: 7175
Encoder[PITCH] type: AS5048A,B (PWM)
read errors: 7178
Encoder[YAW] type: AS5048A,B (PWM)
read errors: 7175
DRIVERS STATE: OTW=0, DRV_FAULT=1
TIME SLOTS FREE (us): 1:516, 2:522, 3:206, 4:460, 5:273, 6:266, 7:524, 8:278, 9:525, 10:529,
TEMPERATURE (C): MCU=34, IMU=25, F.IMU=33, DRIVERS=0, ROLL_M=0, PITCH_M=0, YAW_M=0,
I2C errors: 1; by device: 0x68=1;
-----------------------------------

The debug trace for SPI with skip autodetection checked is the same.

The debug trace for SPI with skip autodetection checked does not show read errors or any problems.

On the monitoring tab: In all cases (PWM, SPI, skip autodetection checked or unchecked) the ENC_RAW_R, ENC_RAW_P, and ENC_RAW_Y show value of 0. Various other monitors show reasonable values.

-----------------------------------------------------------------------------------------------------------

Since at least one other person is seeing this I suspect its not simply a rare defect. I need to get this resolved or Ill have to return the controller and find another solution.