Hi Chuck, some comments below:
On 02/10/2016 14:13, Chuck Yahrling wrote: > After reading about the recent rework of MSK144 I built 7139 and tried > monitoring on 6M. I was presented with 50276 (OOB) which made sense, > and 40M 7076 which did not, as selections in the pull-down box. No > other frequencies were offered. I understand I could populate them > manually. So I presume the lack of band options in the box is for > developer convenience at this point. Working frequencies for most modes above 30MHz are region dependent so we cannot set default frequencies in WSJT-X that are correct for everyone. Rather than introducing region parameters we make the setting of working frequencies easily changeable by the operator in "Settings->Frequencies". You can set frequencies for all modes on a band by leaving the mode blank and you can set mode specific frequencies by assigning the mode and the frequency. That aside you can set any frequency on the WSJT-X main window by typing the frequency in, in MHz, into the edit field of the band drop down. WSJT-X does not care what frequency you use but it will highlight frequencies that are far away from any pre-set working frequency with a red background and out -of-band indication. > > I was able to use the pull-down box to switch to 40M, but could not > switch back to 50276. Rather, it paused on 50276 then reverted back to > 40M. When I changed band at the rig it did track several band changes > OK. The frequency input is in MHz so you must type 50.276 - note the decimal point. > > At some point I got a red-colored answer notification in the TX > window. This seems odd as I did not try or have any tx enabled. Was > simply monitoring to see what the fast graph might tell me. It only > appeared once, and might have popped up when I listened on 40M to see > if anything at all came through. SNIP attached. The current MSK144 decoder is undergoing enhancements to allow continuous near real time decoding. This requires a lot of CPU resources. The latest variant uses multiple CPU cores to spread the work load. This multi core capability is not currently available to Mac users due to an unfortunate constraint that is out of our hands. The new indication on the left hand side of the status bar is showing maximum CPU resources as a percentage and a red background if it is deemed too high a load for successful operation. You must reduce the FTol bandwidth if your machine is indicating too high a CPU usage, in the worst case with slower CPUs you may not be able to enable real time MSK144 decoding. Obviously do not attempt other high resource utilization activities while using MSK144 like streaming video content. > > So is this entry on the TX window a normal feature when running > MSK144? Was not reproducible. I did have VHF/UHF/Microwave features > box checked The "Settings->Advanced->MSK 144 Realtime decode" check box turns on the feature to continuously scan received audio for decodes without the user having to identify and click on reflections seen on the horizontal waterfall display. > > I checked the web for band allocations and saw meteor scatter > suggested for 50.300 to 50.400MHz at > http://www.geekshed.co.uk/getting-started-in-meteor-scatter-ms/ > Listened and tuned that range for a while with no further odd events. > > Is there a suggested MSK144 watering hole on 6M? Random MS activity is often done by calling on an agreed frequency and listening up a few kHz for replies, using "CQ NNN <callsign> <grid>" where NNN is the kHz Rx frequency on the same band. WSJT-X directly supports this mode of random MS operation except that for now it appears to be disabled for MSK144, I expect it will be restored when things settle down a bit more. In the US the Ping Jockey instant messaging service is used for coordinating a lot of activity. Elsewhere the ON4KST chat boards are also used. > > K3 in digital mode on 6M Moxon at 25 feet AGL. Windows 7 Intel Dual > core at 3.0GHz. If you BIOS has an option to enable "Hyper-Threading" make sure it is on as that doubles the CPU multi-threading capability. Modern CPUs have that always on but some older ones need to have it enabled since earlier operating systems could not utilize it correctly. Please do not cross post messages across multiple mailing lists, it is poor netiquette (https://en.wikipedia.org/wiki/Crossposting) and it makes it difficult for others to find replies and for those that answer queries to reply consistently. 73 Bill G4WJS. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
