Problem Reading COM port - RRC-Micro

[HerbNZ0F]

I'm setting up my FT-857 to use with the RRC-Micro application.  I have successfully gotten the audio to work in both directions and can send it CAT commands, but I'm not receiving any CAT info back from the radio, i.e. it's unable to read the frequency which prevents HRD from starting.  I found another CAT control app that lets me send commands and have confirmed that works, but nothing seems to be coming back the other direction on the COM port.   I have a hunch it may be the aftermarket CT-62 cable I have so I've ordered a genuine Yaesu CT-62 cable, but want to be sure I haven't done something stupid in my setup. 

The CT-62 is connected to the RRC-Radio at COM2 and then plugged into the CAT port on the FT-857.  There are no other CAT devices connected and COM1 on the RRC-Radio is not connected to anything.   I've confirmed that the Radio is set to 9600 baud and have also tried 4800 and 38400.

The FT-857 remote head is connected to the radio - the only connections to the RRC-Radio are the mic, the speaker input from the headphone out of the FT-857 control head and COM2 to CAT on the 857.  If I remove the head and connect COM0, the radio powers itself on and off continuously as soon as RRC-Micro connects.

My other configuration info is below.

Thanks
Herb NZ0F

RRC-Radio Settings:
COM0 baudrate   64000
COM0 data bits   8
COM0 stop bits   1
COM0 parity   0
COM0 Program mode 3 char timeout   2
Use USB Com Port as COM0   0
COM1 mode   0
COM1 baudrate   9600
COM1 data bits   8
COM1 stop bits   2
COM1 parity   0
COM1 rts/cts   0
COM1 terminator (hex)   00
Use USB Com Port as COM1   0
COM2 mode   4
COM2 baudrate   9600
COM2 data bits   8
COM2 stop bits   2
COM2 parity   0
COM2 terminator (hex)   00
Use USB Com Port as COM2   0
COM3 mode (USB-COMFSK)   10
UDP cmd port   5063
UDP audio port   5062
SIP port   5061
Web server port   80
Telnet server port   23

RRC-Micro Settings:
COM 0 and 1 are set to inactive
COM 2 is set to Mode 3, COM2, no terminator, 40ms timeout.

[sm2o]

Hi

I assume you have set Program mode to 3 and activate the connection via the "connect" button at the status page. But I guess you have right about the problem, Pirat CAT interfaces which is powered from the com port doesn't work. I must be the orginal CT-62 or a version with a MAX232 chip which is powered from the radio or external power, otherwise it will not work.

73 de mike

[HerbNZ0F]

Your assumptions are correct.  All this points to the cable as the likely culprit as it does not have the MAX232 chip in it - it has some other chip.   The new cable is supposed to arrive tomorrow so we'll see what happens then.

Thanks for the quick reply
Herb NZ0F

[HerbNZ0F]

The cable I ordered arrived today and appears to be an authentic Yaesu cable based on the packaging.  However, upon closer inspection, it uses a ADM202E chip instead of the desired MAX232 chip.  Perhaps Yaesu has changed their design.

I will continue to hunt for a CT-62 with a MAX232 chip, but are there any other work-arounds that anybody can suggest?

Thanks
Herb NZ0F

[sm2o]

It's OK with ADM202E also it's the same as MAX232

/mike

[HerbNZ0F]

Well, if the cable isn't the problem, I guess I'm back to sorting out a configuration issue.  Can you review the configuration info I originally posted to see if anything is out of place?  Both the RRC-Radio and RRC-Micro are in program Mode 3.  COM 0 and 1 are inactive in RRC-Micro.  COM2 in RRC-Micro is used for CAT commands. As I indicated earlier, I am able to send commands, but not able to read the frequency or any other info from the radio.  I have used this radio with HRD previously, so I don't think there's any issue with the radio.

Thanks for your help on this.
Herb NZ0F

[HerbNZ0F]

Further clarification on my configuration - in the RRC-Radio, I'm using Mode 3 under the Radio Settings and Mode 4 for COM2 under the Serial settings.  COM1 in the Serial Settings in the RRC-Radio is inactive.

Thanks
Herb NZ0F

[HerbNZ0F]

Still struggling with this issue. Can anyone offer some suggestions?

Thanks
Herb NZ0F

[sm2o]

for 857 you should set com 2 to mode 3, 857 uses the old Yaesu protocol.

/mike

[HerbNZ0F]

In the RRC-Micro or the RRC-radio?  Per the info I provided originally, I'm already using mode 3 in the RRC Micro.
Thanks

[sm2o]

The same mode must be used in both ends, the same protocol is transferred all the way

/mike

[HerbNZ0F]

Tried that. Still not working. I notice on the Status page that I am getting a UDP Command Error(0). Is that another symptom of this problem, or does that point to some other issue that may be causing the problem?

Thanks
Herb NZ0F

[Jan (Microbit)]

"UDP Command Error(0)" means that the serial data between the RRC and the RRC-Micro isn't working. It could either be some firewall blocking it, faulty wiring, wrong baudrate, etc. To rule out it being firewall related you could swap the UDP cmd port and UDP audio port in both ends since audio is working. Though one might suspect it is more likely some of the other reasons in your case.

[sm2o]

I have tested to control the radio from here, and it answer that it's set to 162.550 MHz Narrow FM. Probably the radio is left in memory mode.

/mike

[dj0qn]

Make sure that you are NOT using port 5060 for UDP. You likely have a newer RRC set with the
new 13000 port numbers, but this is the type of problem that occurred using 5060 before the change.

I mention this in my networking checklist that I send upon request to assist in installing on networks.

73,
Mitch DJ0QN / K7DX