Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - w4tx

Pages: [1]
1
General discussion / Re: Uppgrade from 1.0.24 to 1.1.2
« on: 2011-03-04, 21:01:31 »
Roland,

I don't want to hijack this thread, but thought you would want some feedback on 1.1.3 beta.

Remote Rig RRC Client has been working perfectly on a XP SP 3 laptop. Just bought a netbook with Win 7 Starter. RRC Client installed with no errors but the virtual serial port would not work with HRD. Worked on it for 2 days with no luck.  I just saw your 1.1.3 beta above and tried it. The Win7 netbook is working perfectly now! 

Thanks es 73,

Doc - W4TX

2
Good news!!

The latest software versions (v2.27 for the RRC-1258 and v1.0.22 for the PC-Client) have completely corrected the problem with the virtual serial port used for HRD. It is now functioning very well. The audio is also very solid.

Thank you for your efforts!

73 - Doc - W4TX

3
This morning, I made COM2 inactive on the PC Client and RRC-1258 Mk II, and activated COM0. I kept the CT-62 cabled connected to COM2 knowing the COM0 data would also be on COM2.

The result was exactly the same as my last post. Both 38,400 and 9,600 baud was tried.

Any ideas would be appreciated.

73 - Doc - W4TX

4
Installed the PC-Client 1.0.12 beta that was just released.

HRD will now connect with the radio (Yeah!!). However, it is very unstable. The frequency displayed on HRD jumps all over various bands. Also, when the frequency on the radio is changed manually at the radio, HRD does not reflect the frequency change. Various buttons and sliders on the HRD display are randomly changing.

I can change modes from USB to LSB and the radio will respond to the mode change but the change is not reflected on the HRD screen.

The PC-Client software (1.0.12) was installed on a laptop running XP and a desktop running Vista. Both computers behaved identically.

73 - Doc - W4TX

5
Problem solved!!!!!!!!!!!

The audio settings were on quality 2 Linear 16 kHz.

Changing to quality 0 A law 8 kHz made the receive audio work properly. Transmit audio and PTT still working.

It was in the PC Client configuration on the website but I overlooked it.

The only problem left is getting HRD to connect to the radio which is in another thread.

73 - Doc - W4TX

6
Hi Guy,

I went back through the manual and it actually shows cabling for the FT-897 that goes from the CAT port on the radio to the TTL jack on the RemoteRig box. I made up a cable and set the parameters for the box and the PC-Client but I still can not get HRD to connect to the radio via the virtual UPD port.

At this point I have nothing else to try that I can think of. I will wait for a software update and hope that fixes the problem.

73 and thanks for the ideas and help - Doc - W4TX

7
Hi Guy,

Are you referring to the TTL jack (COM0) being 0 to 5 volt logic levels versus the RS-232 levels on COM2? If so then it should be fine. The Yaesu FT-857 CAT jack is 0 to 5 volt logic levels. The CT-62 cable has a level converter built in. By eliminating the CT-62 cable, I'll have TTL levels from the Yaesu CAT jack to the TTL jack on the RemoteRig.

If the protocol difference is something else, please let me know.

Thanks and 73 - Doc - W4TX

8
I have connected an RS-232 monitor on COM2 of the RRC-1258 MkII. While trying to connect HRD through the virtual UDP port, there is no activity at all on any of the data or handshake lines.

I also installed the RRC Client and HRD on a desktop computer running Vista. I had the same result as the XP laptop AND the XP netbook.

I may next eliminate the CT-62 and connect the Yaesu CAT directly into COM0, the TTL jack.

73 - Doc - W4TX

9
Hi Roland,

Changing the speaker back to the internal sound card of the laptop did not produce any sound.

The RRC logging program was run, as you requested, and emailed.

Thank you for you help.  I look forward to the new release next week.

73 - Doc - W4TX

10
Hi Guy,

Changing to virtual UDP port COM2 did not work. I'm sure that is the proper port to use, since the CT-62 is plugged into COM2 on the RemoteRig box. So I'll look at the RX and TX data pins next.

73 - Doc - W4TX

11
The laptop is running XP.

73,

Doc - W4TX

12
Hi Guy,

You are correct with the setup except one thing. And, I think that is the problem. I have the virtual upd port 0 set up, not port 2. But the CT-62 is plugged on to COM2. I will change that and report back.


Thanks and 73!

Doc - W4TX

13
Thanks for the tip Guy.

HRD does connect to the radio when directly connected with the CT-62 cable and a USB to serial converter.

73 - Doc, W4TX

14
New RRC1258MkII with firmware updated to v2.21

New RRC-Micro PC-Client v1.0.10 32 bit

Rig is a Yaesu FT-897

CAT cable is a Yaesu CT-62 connected to COM2 of the RRC1258MkII. COM2 is set to mode 3 - char timeout. Speed is 9600. JMP-3 is installed inside the RRC-1258MkII.

HRD is the latest version 5 beta. It sees the virtual port but will not work at any baud rate. The CAT speed at the radio is 9600.

From reading another post, I uninstalled HRD and the PC-Client. I made sure all virtual COM ports were removed, then re-installed the PC-Client and HRD. The UDP virtual port is the lowest (COM3), and the only one on the laptop. But, still no connection. I also tried a second laptop with the same result. Both laptops are running Windows XP, fully updated.

This is being tested on a local LAN using the default ports. No router or internet connection is used at this point.

Any ideas for more things to check and test would be appreciated.

73 - Doc, W4TX

15
New RRC1258MkII with firmware updated to v2.21

New RRC-Micro PC-Client v1.0.10 32 bit

Rig is a Yaesu FT-897

CAT cable is a Yaesu CT-62 connected to COM2 of the RRC1258MkII.

The 3.5mm stereo cable from the radio to the SP jack on the RemoteRig has been tested and the radio receive volume is at the 11 o'clock position.

The headphone hooked to the PC-client USB dongle/sound card has been tested.

The PC-client will start a SIP connection. The yellow led on the mic/aux connector is lit. The green activity led on the ethernet jack is showing activity. The PTT button on the PC-client keys the radio. Microphone audio on the PC-client modulates the transmitter.

The receive audio slider on the PC-client application is mid-range. The PC-client has the microbit 1254 chosen as the receive audio device.There is absolutely no receive audio. No noise or anything in the headphones.

I have tried changing the receive audio device to the laptop sound card, but no receive audio will come from the laptop speakers either.

This is being tested on a local LAN using the default ports. No router or internet connection is used at this point.

Any ideas for more things to check and test would be appreciated.

73 - Doc, W4TX

Pages: [1]