Intermittent receiver connection on CrazybeeF4FR

[avsaase]

I just flashed Emuflight 0.1.0 on the CrazybeeF4FR flight controller in my Eachine Trashcan, but I'm having trouble with the connection to my X9D+ 2019 after binding in FRSKY_X (D16) mode.

Directly after flashing I went to the CLI and bound with frsky_bind. After power cycling, the connection keeps constantly dropping and recovering every second or so, with my radio giving "Telemetry lost"/"Telemetry recovered"/"RSSI critical" warnings. In the Receiver tab, I see the minimum Throttle position going from 885 tot 1000 (the channel minimum), so I think it was bound correctly.

I have already tried binding with telemetry ON and OFF, but this doesn't make a difference. Flashing back to Betaflight also solves the issue, so I suspect its not a hardware issue.

Any suggestions? Below is a diff all

# 

# diff all

# version
# EmuFlight / CRAZYBEEF4FR (C4FR) 0.1.0 Sep 16 2019 / 22:02:00 (3956d2f50) MSP API: 1.40

board_name 
manufacturer_id 
mcu_id 003d000b3239511334393435
signature 

# reset configuration to default settings
defaults nosave

# name

# resources

# mixer

# servo

# servo mix


# feature

# beeper

# beacon

# map

# serial

# led

# color

# mode_color

# aux

# adjrange

# rxrange

# vtx

# rxfail

# master
set frsky_spi_tx_id = 173,146
set frsky_spi_offset = -56
set frsky_spi_bind_hop_data = 6,74,144,214,49,119,189,24,94,164,234,69,139,209,44,114,184,19,89,159,229,64,136,204,39,109,179,14,84,154,224,59,129,199,34,104,174,9,79,149,219,54,124,194,29,99,169,255,255,255
set frsky_x_rx_num = 8

# profile
profile 0


# profile
profile 1


# profile
profile 2


# restore original profile selection
profile 0

# rateprofile
rateprofile 0


# rateprofile
rateprofile 1


# rateprofile
rateprofile 2


# rateprofile
rateprofile 3


# rateprofile
rateprofile 4


# rateprofile
rateprofile 5


# restore original rateprofile selection
rateprofile 0

# save configuration
save
# 

[avsaase]

I'm sorry, this obviously should have been posted in EmuFlight, not EmuConfigurator. Can it be moved? However, flashing with 0.2.12rc2 seems to have solved my issue. Thanks!