> Issue: > CHIRP can write channels that contain separate RX and TX values (as > provided by the CPS or imported data) to the radio, and the radio operates > correctly. > > But when reading the radio back into CHIRP, any memory channel that was > originally programmed as a true split (separate RX and TX, not > offset-based) is shown as a completely empty row in the memory table. > > Standard simplex channels and offset-based repeater channels are read back > correctly.
CHIRP has no way to know whether or not you want to see a particular channel as TX/RX or RX+offset. The radio doesn't store a difference so it has to go based on the heuristic we have in the code (which is <70MHz means RX+offset). Thus, it's not an "issue" so much as a matter of (your) preference. CHIRP is an abstraction, which provides a common interface to program dissimilar radios. That means it _will_ behave consistently to its own model, and will _not_ behave exactly like each radio and/or its OEM software. However, if you want the OEM-like experience, you can use View->Use TX Frequency Workflow to change the UI to behave the other way on any radio regardless of how the values are stored in memory. This effectively makes CHIRP's UI always take TX/RX frequencies and it translates it to whatever the radio requires (basically the opposite of it forcing everything to RX+offset below a 70MHz split). --Dan _______________________________________________ Users mailing list [email protected] https://lists.chirpmyradio.com/postorius/lists/users.lists.chirpmyradio.com To unsubscribe, send an email to [email protected] To report this email as off-topic, please email [email protected] List archives: https://lists.chirpmyradio.com/hyperkitty/list/[email protected]/
