CHIRP

Hello dear,
I just received my new FT-4XE.
When I used chirp I had to use FT4-XR to read the data.
I noticed that you blocked the FT-4XR on the 6.25khz channel.
So I took ft4.py and removed the restriction from this step.
However, I be sure that it is an XE europe since it is written behind and the monitoring button is set by default on the 1750hz unlike the XR which is on monitoring by default.

Hope this is useful to you:

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "chirp\wxui\clone.py", line 66, in run
File "C:\Users\xxx\Yeasu FT4X\ft4.py", line 750, in sync_out
raise errors.RadioError("Failed to communicate with radio: %s" % e)
chirp.errors.RadioError: Failed to communicate with radio: Incorrect ID read from radio.
[2023-05-25 04:09:14,947] chirp.wxui.clone - DEBUG: Showing pre_upload prompt
[2023-05-25 04:09:17,471] chirp.wxui.clone - DEBUG: Setting flag for prompt pre_upload
[2023-05-25 04:09:17,471] chirp.wxui.clone - DEBUG: Opening serial 'COM19' after upload prompt
[2023-05-25 04:09:17,472] chirp.wxui.clone - DEBUG: Serial opened: Serial(port='COM19', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=0.25, xonxoff=False, rtscts=False, dsrdtr=False) (rts=True dtr=True)
[2023-05-25 04:09:17,549] chirp.loaded.ft4 - WARNING: ID suspect. Expected000: 49 46 54 2d 33 35 52 00 IFT-35R.
008: 00 56 31 30 30 00 00 .V100...
, Received:000: 49 46 54 2d 33 35 52 00 IFT-35R.
008: 00 56 31 30 30 00 00 .V100...