Author Topic: New Hum Problem with 2.41  (Read 6029 times)

dj0qn

  • Hero Member
  • *****
  • Posts: 2060
    • View Profile
    • DJ0QN / K7DX
    • Email
New Hum Problem with 2.41
« on: 2011-07-13, 10:28:21 »
Just a heads-up: there is apparently a problem with firmware 2.41 that causes hum when the USB CAT is used.
This is the same or similar to the problem that occurred in firmware 2.35 and was fixed right away. See
http://www.remoterig.com/forum/index.php?topic=701.0 for that thread.

It is the same user that is having the problem. He is away today, but I will try to get more tests and details
from him before I leave on vacation this weekend. It appears so far to be identical to what he experienced
in 2.35, so he has downgraded to 2.39 for now until this is clarified or resolved.

73,
Mitch DJ0QN / K7DX

dj0qn

  • Hero Member
  • *****
  • Posts: 2060
    • View Profile
    • DJ0QN / K7DX
    • Email
Re: New Hum Problem with 2.41
« Reply #1 on: 2011-07-15, 18:00:37 »
I received a more complete description from the user: When the USB cable is removed from the RRC,
the hum problem disappears and the head works as it should.

This appears to be very similar or identical to the problem introduced in firmware 2.35 and fixed in 2.36.
So much so, that I assume that the developers have made the same error they made with 2.35 when
USB CAT was first introduced.

73,
Mitch DJ0QN / K7DX






rockyjones

  • Jr. Member
  • **
  • Posts: 50
    • View Profile
    • Email
Re: New Hum Problem with 2.41
« Reply #2 on: 2011-07-18, 20:35:45 »
I can confirm there is a hum problem with 2.41 and it isn't just tied to the USB port.  I don't use USB ports and when I loaded 2.41 on my 1258's I started to get reports of hum in the audio.  I backed down to 2.40 and no more hum.

Joe W4WT


Update:  Looks like I was wrong.  I apparently have an intermittent problem in the equipment that has just appeared causing my hum problem.  It just happened to quit when I downgraded the firmware.

 
« Last Edit: 2011-07-19, 18:08:44 by rockyjones »
W4WT

dj0qn

  • Hero Member
  • *****
  • Posts: 2060
    • View Profile
    • DJ0QN / K7DX
    • Email
Re: New Hum Problem with 2.41
« Reply #3 on: 2011-07-20, 11:36:52 »
I have managed to replicate the problem myself.

I am on vacation and set-up a portable RRC with TS-480 head that uses the USB COM port for CAT control.
When I connect to the same station that my other user does, after about 2 minutes I get a loud buzz (not
really a hum). When I pull the USB cable out, it goes away. Strangely, this problem does not occur with the
other station that I also use, only with this particular one, which has otherwise identical settings and hardware.

73,
Mitch DJ0QN / K7DX

dj0qn

  • Hero Member
  • *****
  • Posts: 2060
    • View Profile
    • DJ0QN / K7DX
    • Email
Re: New Hum Problem with 2.41
« Reply #4 on: 2011-07-25, 20:08:57 »
I have found another bug in 2.41:

The CAT on COM2 over USB is not "released" when the logging program is terminated.
For example, the program I use, TRX-manager, uses the COM2 over USB CAT with no
problem, but when I terminate the program and restart it, it can no longer access COM2.

The only way I can find to release it is to reboot the PC. 2.40 does not exhibit this
problem at all, I can terminate and restart the program as many times as I want, and it will
always use COM2 over USB without an error message.

73,
Mitch DJ0QN / K7DX

dj0qn

  • Hero Member
  • *****
  • Posts: 2060
    • View Profile
    • DJ0QN / K7DX
    • Email
Re: New Hum Problem with 2.41
« Reply #5 on: 2011-08-16, 15:04:59 »
Is there a timing when these issues will be fixed? I would like to implement using
COM1 on USB in some installations, but need to wait until this is fixed. I had
everyone downgrade in the meantime.

Thanks & 73,
Mitch DJ0QN / K7DX


Jan (Microbit)

  • Software Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 1799
    • View Profile
    • Email
Re: New Hum Problem with 2.41
« Reply #6 on: 2011-08-16, 18:20:36 »
Sorry for the slow response. We have had summer vacation and therefore not being able to answer as quick as wanted.

The "hum" problem can't be caused by the same issue as the one being present in 2.35, as the new ports don't have that faulty handling. That problem caused btw the RRC to reset endlessly. The USB bus is however being used much more now so that is at least a difference, though I don't see why it should cause something like that.

Also, the "Not being released" issue is hard to understand since the Com port driver is within Windows itself. It should not have something to do with the RRC. Yet you say that 2.40 didn't exhibit that problem. Hmm... What happens if you disconnect the RRC instead of restarting the PC? That should definitely make the port close.
Always include type of hard/software and version when asking for support.

dj0qn

  • Hero Member
  • *****
  • Posts: 2060
    • View Profile
    • DJ0QN / K7DX
    • Email
Re: New Hum Problem with 2.41
« Reply #7 on: 2011-08-16, 18:26:47 »
Hi Jan,

I know you guys were on vacation, as I was as well, so I have been patient ;-)

1) The buzz sound the same as it did in 2.35. I can send you an MP3 if you want.
It takes about 2 minutes to start after turning the TS-480 on. I was able to only
replicate it on one remote system, as was the other user. Not sure why only this
one remote system would cause a problem, I use two more identical installations
that apparently don't buzz when connected.

2) I would also think that Windows controls the release, but indeed unplugging, etc.
does not apparently make a difference. I was able to replicate this several times and
rebooted. It has been a while and I can try again, maybe the PC was not in a good
mood at the time ;-)

73,
Mitch DJ0QN / K7DX




Jan (Microbit)

  • Software Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 1799
    • View Profile
    • Email
Re: New Hum Problem with 2.41
« Reply #8 on: 2011-08-16, 18:34:00 »
Hi Jan,

I know you guys were on vacation, as I was as well, so I have been patient ;-)

1) The buzz sound the same as it did in 2.35. I can send you an MP3 if you want.
It takes about 2 minutes to start after turning the TS-480 on. I was able to only
replicate it on one remote system, as was the other user. Not sure why only this
one remote system would cause a problem, I use two more identical installations
that apparently don't buzz when connected.
You could connect a serial terminal to COM1 and see what the RRC does when it happens. Is it rebooting maybe? Or does it continue to work normally while still happily humming/buzzing its tune, hehe?
Always include type of hard/software and version when asking for support.

dj0qn

  • Hero Member
  • *****
  • Posts: 2060
    • View Profile
    • DJ0QN / K7DX
    • Email
Re: New Hum Problem with 2.41
« Reply #9 on: 2011-08-16, 18:36:18 »
It apparently continues to work. When you pull the USB cable out, the buzz goes
away and you can continue using the TS-480, albeit without CAT.

Jan (Microbit)

  • Software Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 1799
    • View Profile
    • Email
Re: New Hum Problem with 2.41
« Reply #10 on: 2011-08-17, 10:47:15 »
It apparently continues to work. When you pull the USB cable out, the buzz goes
away and you can continue using the TS-480, albeit without CAT.

Then the problem is not of the same sort which was in 2.35. Will take more investigation searching for its cause.
Always include type of hard/software and version when asking for support.

dj0qn

  • Hero Member
  • *****
  • Posts: 2060
    • View Profile
    • DJ0QN / K7DX
    • Email
Re: New Hum Problem with 2.41
« Reply #11 on: 2011-08-17, 10:49:35 »
That's true. With 2.35, you had to restart everything. I personally could not replicate the
problem with 2.35 that my user had, but this problem affects me as well.

Let me know if you need any further information.

73,
Mitch DJ0QN / K7DX

dj0qn

  • Hero Member
  • *****
  • Posts: 2060
    • View Profile
    • DJ0QN / K7DX
    • Email
Re: New Hum Problem with 2.41
« Reply #12 on: 2011-09-13, 17:20:20 »
Jan,

Have you been able to locate the cause of this problem? I really would like to
move the users over to the new firmware once this is resolved.

If you can't duplicate this, drop me a note offline. I can give you access to the
problem system, but we would have to define a specific time.

73,
Mitch DJ0QN / K7DX