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 - W1AN

Pages: [1]
I'm currently setting up another K3/0 (non-mini) twin system and experienced ground loop or noise ingress through the interconnecting mic cable. I've determined I could eliminate the noise by using a 600/600 ohm transformer directly at the rear mic jack on the K3/0 to supply the RRC control. This might have been my final solution but you cannot pass DC mic bias through a transformer if you need to use a condenser mic. My initial setup is thru the front K3/0 8 pin connector using the Heil Proset with a much lower audio level.

Close inspection of 2 of the "factory" AUX/MIC cables show no conformity to the schematic provided in the manual! The cables provided are lengthy CAT5/6 4 pair cable with short breakouts at the end with the PTT RCA connector and 1/8" mic connector. This factory cable is unshielded. Wires used for mic audio and mic return are from separate pairs, not from one twisted pair. Consequently, shielding is close to non-existent. PTT wiring is similar. Making up my own cables with longer shielded wires connected to a very short piece of CAT 5/6 at the RJ45 work much better! Leaving a long length of exposed mic wire is not good practice. This may work OK with high level signals and the majority of installs, but is a no-no for low level mic signals. A shielded piece of CAT 5/6 might also work for a starting point. If you are experiencing noise ingress you may wish to look at the cables.

73, John W1AN

I am also the owner of several Idiom Press RotorEZ Yaesu and Hygain versions. I also have had lockup problems. Maybe excerpts from my comments to Idiom Press may offer ideas for those who have already invested and built these into your controllers.

Idiom Press:
Hi, I am the owner of several RotorEZ units for both Hygain and Yaesu controllers. It is a well known that the communications may appear to lockup or quit for whatever reason. This is awful for remote operation. It would be good for newer versions to recognize a lockup and restart but that would require some coding and would not correct the many now in use.
In my experimentation with local com ports and remote serial over ip ports, either or both, RTS and DTR are invoked when the port is accessed. DTR is almost always active when the port is active for rotor control and quickly shuts off when the port is inactive. This could be used to reset/power the processor on every remote access. It could also be used to switch the mains power through a relay. Power savings being a side benefit.

...An optical coupler could be used to reset the processor but it would probably be easier to just interrupt the DC supply. If there is no remote operation everything will still work locally.

...You can use a solid state optical switch*.

Best regards,

John Spigel, W1AN

*Note: DTR from DB9 pin 4 through a 1K resistor, optical switch and LED to pin 5 ground. Switch needs to handle the max DC current needed for the RotorEZ. Consider using a Toshiba TLP227G for the Yaesu DXA version but current needs to be measured for others.

OK, I've got it working. The original problem was that the Microbit Setup Manager only installed partly correct. The RRC1258 virtual ports worked correctly. The other virtual ports for the webswitch, etc., did not. Uninstalling MSM and reinstalling twice did the trick. The windows installer complained there was a missing dll that caused the error when trying to configure the serial ports. I did nothing differently. I guess Windows7 eventually figured out how to load and register the dll. I am a happy camper.
73, John W1AN

Configuration, RRC 1258 / Microbit Virtual Com Ports Usable?
« on: 2015-03-13, 17:05:20 »
I'm trying to configure Microbit Virtual Com ports. Microbit virtual com ports 2, 4, 5 and the RRC1258 Com ports 6, 7, 8, 9. appear in device manager in Win7. I understand what the RRC1258 ports are and use them, but don't know much about the Microbit virtual ports.  If they could be configured for generic serial over ip they would be quite useful, but I cannot figure how to access the configuration. Windows 7 says they are "in use". And after an uninstall they reappear!

Any info on this  would be appreciated.
73, John W1AN

General discussion forum / Re: Random Keying of the K3
« on: 2015-02-27, 21:16:47 »
On my unit I replaced the PTT jumper on the configuration header with 2 diodes in series to prevent PTT when the RRC-R is not powered and the K3 is operated locally. This may help.
73, John W1AN

I've completed the RRC installation into the K3/0. COM2 and the LAN connection were extended to the rear and the Paddle and CW key jacks were brought out from the RJ45 I/O connector. Short cables were made and used. The AUX connector is for optional PC CW keying from RS232 DTR using a Y cable from COM1. The ACC connector is for future use. The only internal wiring connection made to the K3/0 is for the 12V at the rear 12VDC connector. There is a future place for a WiFi antenna, but presently I use the WiFi in my laptop connecting the two LAN ports with a crossover cable and a bridge configuration in Win7.

The sheet metal was designed with the free software available from Front Panel Express.  I selected a black anodize finish. The 90 degree bends in the sheet metal were done on a vise.  Duct tape was used to protect the aluminum along with small sheets of aluminum on each side while bends were made.

Future plans include a redesign to include a pico-itx or nano-itx PC motherboard for CAT and contest software. The board will be small enough to mount on top of the RRC inside the K3/0. They are just a little too pricey at this time.

If anyone is interested in the panel design, I will provide. You can edit as needed.

73, John W1AN

OK, I see COM2 on RRC control side is parallel with TTL control side. That is why there is no change in configuration between K3/0 and K3/0 mini. COM2 is likely dedicated for I/O control (on/off) and handshake as well, most likely.

I tried a parallel Y connection for PC RS232 CAT at the radio end on COM2 and it works flawlessly there for hours,  so I thought there was a possibility to pass PC CAT data thru on COM2 at the control end.

73, John W1AN

Thanks, I'll give it a go!
OK, a followup. With the K3/0 mini, the TTL connection is used on the control RRC and COM2 is used for radio RRC. I tried to test PC CAT control with a straight thru RS232 cable on COM2 on the control RRC. Is COM2 not available for PC to radio control in this configuration? I tried multiple serial port settings and a null modem cable as well with no luck. I would think pass thru of CAT data COM2 to COM2 might work with some combination of settings.
73, John W1AN

When using the K3/0 Mini, COM2 is empty at the local RRC. Is there a configuration option that lets you use COM2 for local CAT?
73, John W1AN

Hardware, Cabling, Installations / Re: Com Ports
« on: 2015-01-23, 21:53:37 »
OK, that is what I needed Mike and Mitch. All the pieces about ports are starting to make sense. Digging in a little deeper and I may figure out how CW and FSK keying talk. It's a mystery until then.

I've several 4 port serial servers. With the Microbit provided virtual serial over ethernet driver they work well on Win 7. Thank you!

73, John, W1AN

Hardware, Cabling, Installations / Re: Com Ports
« on: 2015-01-22, 18:41:18 »
Mitch that does help. In addition is the TTL-TTL another pass thru port? And is it free to use, possibly at a fixed baud rate if not needed otherwise? TTL to RS232 converters would be needed of course, but these items are inexpensive on-line. I just need to drop the TTL 8V to 5V with a resistor and 5V zener. Good for rotor control, etc.

Also is the FSK keying generated off the TTL side of the USB chip inside the control unit? Just wondering about latency. It's great that you have the 5 Bit, 45.5 baud working off usb but is this another TTL pass thru to the RRC-Radio unit to I/O?

The K3 and other radios can take CW and PTT off DTR and RTS eliminating the need for a second PC serial connection and, as you know, software for FSK RTTY can be generated from another serial COM port from TxD and RTS. I will most likely stick with the standard USB approach. I'm just looking at options for an additional communication path and trying to get a better understanding of how all this fits together.

73, John W1AN

There's another approach for the less adventurous. In the image the two sheet metal tabs either side of the RRC opening fold back at 90 degrees to support the RRC inside so the circuit card is able to slide out. You can bring out all the connectors to the rear of the K3/0 and add the I/O paddle, Straight Key, and PC keying jacks. The sheet metal extends to the left rear edge allowing the unused holes to be used. No drilling or changes to the K3 internals is needed. This method is for those who want the option to keep the K3/0 and RRC-C intact. Short interconnecting cables will be needed. Of course you could later dig in a little deeper and wire all internal to the K3/0 if you like a cleaner appearance.

I've just ordered the sheet metal for my K3/0. It should arrive in a few days. I'll post photos of the completed install when done.
73, John W1AN

Hardware, Cabling, Installations / Com Ports
« on: 2015-01-21, 22:39:35 »
I'm confused about how the COM ports are defined. Digging through all the forum pages and docs only confuses me more.

I see COM0, COM1, COM2, COM3 mentioned in the docs and forum.

There is also a TTL to TTL pass thru for TS480, etc. Is this COM0 or something else? Can this port be redirected to COM1 or COM2? or from COM1, COM2, etc

Are COM1 and COM2 direct pass through ports? With software redirection in the setup?

Is COM0 an internal pass thru port with redirection from COM1 COM2 and TTL USB-COM?

Where is COM3? Is this port a virtual port from the USB on the RRC-C to RRC-R I/O and COM2?

In my K3 Twin setup is the TTL port available for a pass thru? Is the baud rate fixed or open?

A functional diagram would be helpful.
73, John W1AN

I'm sure others have thoughts on this but I'm sure it can be done with some patience and planning to pass the wiring in and out of the case to connect between the rear of the K3/0 and the RRC control connectors. You don't want to destroy the value of your K3/0, so you would do your best to mount everything on and through the removable rear plate which can be replaced or home brewed. This can become somewhat of a project but it can reduce some of the rats nest of wires.

My thought is to redesign the RRC Control PCB to provide on board headers for all connections and provide a cable kit so that it can be embedded. Collaboration with Elecraft could result in a kit to include mating headers and replace some K3/0 sheet metal. For the K3/0 mini an extension box similar in size to the K3/0 with rear panel connections could be supplied. The best plan in my view would be to redesign the sheet metal so that you could also mount a mini-itx motherboard inside as well. There is room! You would have a great system that would go in your carry-on bag!

73, John W1AN

I am using the K3/0 Twin configuration and would like to use the TTL connection on the control unit for PC to Radio CAT to free up COM1 for a pass through for other devices. It appears I should be able to do this with one of the DB9 Serial to TTL devices using the MAX2323, or a USB to TTL converter.  Also, optionally I would like to use the TTL on the control unit for FSK with a level converter from RS232 TxD instead of the USB input. Also is it possible to change the usb port to an RS232 with a TTL converter? Any possibilities here?
73, John W1AN

Pages: [1]