On 26/04/2014 09:57, Chuck Forsberg WA7KGX wrote: Hi Chuck, > After running the delelopment wsjtx with tracing > I found my 756PRO unable to operate normally > on some of my favorite frequencies I've had in > the Icom's memory for some time. I'm sorry that you are having problems. What exactly is the problem you are describing?
I don't understand why you are running the special version with diagnostic tracing for more than the quick tests I asked you to carry out. I though I'd made it quite clear that I had also supplied you with a normally configured version built for you operating system with the same changes in which you can use for normal operations. As soon as I an confirm correct behaviour with your rigs I will commit the changes to the repository so all will benefit. At that time you can choose to build a new version and indeed switch off the options if you don't want them. For now I appreciate any help in sorting out any issues. > > I had to poke around a bit to restore normal operation. > I don't recall exactly what I did but I did use buttons > I normally have no use for. I use an IC756 (non-pro) on a daily basic with WSJT-X which is very similar to the IC756Pro in CAT control but suffer no such disabling effects. For your issue report to be of use you really need to try and help the community by describing the problem in such a way that it can be diagnosed. > > Could we make the default to change frequencies explicitly > rather than using VFO switching and split operation? > It only takes about 20 milliseconds to send a new frequency command. > Chuck, as I have said several time before to you, there is a configuration option in the WSJT-X program to either disable split operation completely or to use "emulated" split mode that does exactly what you are describing above. Setting the defaults to cripple the features of a piece of software just because you as an individual think that they are of no use in your usage pattern is hardly going to progress the communities usage of WSJT-X. Frankly I am disappointed with the whole experience of trying to help you with the issues you have reported, you raise what appear to be significant defects and I am trying my best to resolve them but you seem to have a strong agenda to have all changes discarded so you can go back to a prior state where you had everything working to your satisfaction. It is very hard to put in effort against such responses, for example at the moment I have borrowed an FT-857 from a fellow operator to investigate the problem you have with your FT817 (the FT-857 is the nearest I can get and is a very similar CAT protocol). Today I am going to forego operating time to make up a CAT control lead and spend what will be probably several hours debugging Hamlib with that rig. Hopefully any FT-817 or FT-857 users of WSJT-X and indeed the whole gamut of software users that indirectly use Hamlib through other products may appreciate the future more correct behaviour once the defects have been tracked down and removed. This is a developers mailing list and we are, I think, gathered here to move the WSJT programs forward. I see forward as easier to use for even the most non-technical operators. If we all took the approach that defects on the way to better functionality are not worth the trouble then we would still be communicating over distance via telegraph wires or even smoke signals. Apologies to Joe all for what may be seen as a flame e-mail. 73 Bill G4WJS. ------------------------------------------------------------------------------ Start Your Social Network Today - Download eXo Platform Build your Enterprise Intranet with eXo Platform Software Java Based Open Source Intranet - Social, Extensible, Cloud Ready Get Started Now And Turn Your Intranet Into A Collaboration Platform http://p.sf.net/sfu/ExoPlatform _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
