PTT and COM port issues

[coss...@gmail.com]

I am trying to use my USB comports with my Rigexpert interfaces. I have both a Ti5 and Plus versions. Nothing I have tried so far can make FreeDV recognise any of the four ports I have. Couple this to the failure of the system to recognise my Icom 756 under the Hamlib option and it has me pulling my hair out. VOX doesn't seem to be an option as my audio is fed to the 756 via the ACC socket.Every other digi mode program, such as MixW, MMSSTV, JT65HF and Fldigi work.

I don't really want to have to delve into the inner workings of my computer. I am running 0.97.0 Beta. All my virtual COM ports are .10 or greater and other devices are using the lower ports. Has anyone managed a work around using virtual ports? I must admit that I am stumped.  I have FreeDV running on XPPro and Win7 Pro.

Ian

[Steve]

I tried my Linux freedv and when I selected Icom 756 I saw some debug text fly by that I had selected a Icom 756 (326)

Where 326 jibes with the Hamlib Icom 756 rig type.  The default CI-V address should be 0x50 hex according to the rig manual.

I noticed in the .FreeDV config file that it says I have selected "RigName=54"  Whatever the hell that is.

I counted down 55 lines on the dialog and it said Icom 756, so I put in the first rig and it said 0, so I think the RigName has nothing to do with anything other than the dropdown location of your rigname.

So, that aside, I looked at the hamlib software and it does in fact use address 0x50 for an Icom 756.

{ RIG_MODEL_IC756, 0x50 }

So anyway, this means that freedv will send CI-V commands to any rig listening on address 0x50.

That means you need to check your rig to see what the CI-V settings are.  If in fact the address is set to 0x50, then that only leaves one other thing, the baud rate.

Since Freedv doesn't control the baudrate, I suspect the hamlib software does some sort of probe. One speed after the next, and hope the rig talks back to you.

Maybe change the baud rate from the default "auto" on the rig to "19200".  If that doesn't work, hell try "1200", anyway try them all and see what happens.

That's all I know :-)

[Bob & Jane]

Ian -

 

I don't have the same radio as you.

 

This may not address the issue you have, but try changing the DTR/RTS values at the bottom of the COM Port window.

 

I have half-duplex checked at the top.

Use Hamlib NOT CHECKED. My comments in this E-mail only apply to using a PTT serial port, not Hamlib.

Use Serial Port CHECKED.

ONLY use DTR checked (not Use RTS)

BOTH DTR=+V and RTS=+V checked.

 

 

Also does you radio/serial port combo work with other programs - for example DigiPan? If so, it would seem to me that as long as you had the same COM Port information set in FreeDV, FreeDV should work.

 

 

Let us know if you get this resolved.

 

 

Bob, WB8ILI

 

 

[coss...@gmail.com]

Thanks for your ideas folks. The serial ports run OK with all other digimodes that I use which run OK.MixW, Digipan, MMRTTY, MMSSTV, JT65HF, FLDIGI ETC

If I select COM1, or COM2 which are "Real" hard  wired serial  ports  don't get the error message "Couldn't open Serial Port"

I am beginning to wonder if it's something to do with something I read about some programs not running on serial ports higher than 10 Problem is that most of my lower ports are in use.

If I do finally crack it, I know that I have my 756 baud rate set to 9k6 so there maybe another issue at that time.r  Any other ideas welcome of course.

tnx and 73.

Ian

[coss...@gmail.com]

Well, I was correct in my thoughts that it might be ports of 10 and above that was the problem. I found four spare ports below 10, moved the four ports required by MixW down, restarted the machine and this time there was no error message the 756 went to tx when the PTT button was pressed and all I have to do now is to carefully set the levels. I bought a Skype type USB headset and now only waiting for a usb soundcard.

I also have an old Yaesu 757GX which is permanently connected to my standalone CODEC/Modem.

thanks for your interest folks, problem solved I hope.

Ian

On Thursday, 18 December 2014 23:02:13 UTC, coss...@gmail.com wrote:

[jdow]

Would the person doing the Windows coding care to have some code that enumerates
all the serial ports installed on the machine with enough information the
program can then open them as the user requests and also presents some friendly
names for the ports? The friendly names are such as ATEN USB Serial (COM 20).
Optionally the code can also test if the port is busy or not. This gets rid of
the idiot COM 1 through COM (ridiculous) sort of menu scheme. I know *I* an
heartily annoyed by that COM 1 sort of menu bushwah. It's better suited to
traditional 'ix code. (Modern 'ix code can also enumerate using "lsusb" as a
model. I am sure there is equivalent for the tty devices. If not there damn well
should be.)

I can either provide it or the coder in question can find a version of it on
Code Project.

{^_^} Joanne/W6MKU

> --
> You received this message because you are subscribed to the Google Groups
> "digitalvoice" group.
> To unsubscribe from this group and stop receiving emails from it, send an email
> to digitalvoice...@googlegroups.com
> <mailto:digitalvoice...@googlegroups.com>.
> To post to this group, send email to digita...@googlegroups.com
> <mailto:digita...@googlegroups.com>.
> Visit this group at http://groups.google.com/group/digitalvoice.
> For more options, visit https://groups.google.com/d/optout.