1
General discussion forum / Re: Modes 6 & 7 (CAT to COM2) doesn't support all CAT commands?
« on: 2023-11-23, 21:00:13 »Hi
When transferring kenwood CAT commands Remoterig does not interpret the messages it just use the ; (semicolon) which indicates the end of message to initiate transmission of a packet
73 de mike
Mike, Are you sure about this? I'm not seeing the same behavior between COM1 and COM2 on the RRC. For example, only the "native" CAT COM port will reply to CAT command inquiries such as "IF;" whereas the other COM port does not, even though it does provide CAT data, it doesn't provide the same. Another example is the S Meter or SWR meter values. I.e. it seems like RRC is doing some filtering, or at least how the "sharing" / interlacing of the CAT data between COM ports remotely (radio side) and locally (client side) seems to work. From what I can tell it only supports a subset of the Kenwood protocol. I've tried a multitude of settings as well and I don't think it's my configuration that's affecting this.
The thing is I would like to be able to output CAT data on COM 0 if possible (easy access to TTL) but here as well I only have a subset of CAT data available, probably due to how the "COM2 to COM1" functionality works?
If I were to make my own RJ12 6P6C cable and hook that up to a RS232 to TTL converter and feed the server (radio) side CAT data through COM0 I guess I could expect this through COM0 at the client (local) side as well?
I need to be able to access the CAT data through TTL while still having (ideally) access to CAT over USB locally at the client side.