I now have four skimmers running and synching with SSDR thanks to Bridge 1.0.1. However I am having problems getting WriteLog to properly synch under all situations.
When I first start Bridge it switches WriteLog to the band of my active Slice as expected (Slice A, IQ 1). If I then click on a decoded call in Skimmer for that active slice then Bridge properly synchs WriteLog which fills in the frequency and call of the selected station.
Now if I click on a decoded call in another Skimmer window that is not currently the active slice, Bridge recognizes the change and properly indicates the active slice and nicely mutes the other slices in SSDR - HOWEVER WriteLog is NOT getting the band change sync or filling in the station call and such upon switching active slices.
Looking more closely I believe Bridge is synching WriteLog only for the Slice associated with IQ 1.
- Bob, W1RE
Been using Skimmer with SDR-Bridge since yesterday and I can't get away from it!
Maybe this was addressed already and I overlooked it -- Skimmer Server won't launch when SDR-Bridge activates. Each time I try to select that option under the <Skimmer> <Server> tab in SDR-Bridge, it un-checks when re-staring SDR-Bridge. So far, I have not seen Skimmer Server auto-launch with SDR-Bridge.
Ed, in skimmer what hardware type setting should I be on; "softrock"? In the skimmer freq box it always says the same freq and If I open a new slice for 20m the skimmer freq gives some 40m freq, even though the IQ data says its the correct 20m freq....
Strangely, when importing exported N1MM logs into Writelog, they come out inverted, with the oldest QSO being at the wrong end of the log. Adding a new QSO doesn't look to good at the new position right below the oldest QSO, hi.
I see that writelog is your preferred log to be fully integrated with sdrbridge
Are you interested in integrating other logging software ?
WriteLog is preferred because it is the only logger currently available that offers features that go beyond CAT control. I will be integrating other loggers as they develop more advanced API interfaces.
In the mean time SDR-Bridge is compatible with CAT. Use CAT to connect with your logger, and SDR-Bridge to synchronize with Skimmer. They work well together.
73 Ed W2RF
Thanks for pointing out Log4Me. I wasn't aware of it but went through the manuals and videos yesterday. It look like a VERY nice general purpose logging program. Lots of features and very well thought out. It looks like you can even set it up to start other programs like SSDR and SDR-Bridge. One click and everything is up and running. Have you tried that?
For reference the Manual, User community (forum), and download at: http://www.pisto.it/wordpress/log4om-en/
If Ed decides to integrate it with SDR-Bridge I'll probably switch. Although it is free, I'd be happy to donate if I use it.
Regards, Al / NN4ZZ
al (at) nn4zz (dot) com
Then, after a little while of tuning around in one of the slices and maybe going back and forth between two slices, an frequency offset develops between the Flex and what is displayed in the skimmer panel and where the green pointer is pointing... The skew is small, like 50Hz but it never seems to go away. Also, I noticed if I use the mouse wheel vs. the Flex control, to change the freq in the slice, the skimmer freq does not change.... Great product Ed, thanks, Ciao, Dennis, k0eoo
This past CQ-WPX I spent a lot of time wringing out the WriteLog program using 2 skimmers, SDR-bridge, VE7CC client and SSDR all married together. The experience was night and day in favor of WriteLog over N1MM. The interface, even driving a 6300 (which only has one SCU and a very simple antenna switch) was not SO2R but damn close to it for stations that intend to run single op assisted category. The operation was flawless, fast and completely predictable. The only real flaw I found was the way the RIT works especially with the FlexControl in SSDR. It takes one button press to turn RIT on (good) but 4 button presses to turn it off (bad) and the state of the RIT is not practically displayed in the slice flag. The other thing that worked the best was to have multi-band antennas, like a tri-bander, not a bunch of single band antennas controlled by coax switches. That approach might be possible if we had some way to automatically control the switches via BCD. I've had that going with the F5K but my station is in a bit of a transition so playing with that again may require a more robust BCD solution.
Frankly I think it's totally reasonable to support authors who are committed to supporting Flex radio and SSDR (W5XD/writelog) and to eschew those who consider us barely an also ran and not worth their time to improve our contest experience. (N1MM) I wrote a couple of blog posts about my experience with writelog/skimmer/sdr-bridge.ve7cc/ssdr/flex6300 over on sdr-w9oy,blogspot.com
Writelog is a contest program although it has some advantages like the band map. Writelog ve7cc and skimmer all communicate meaning a skimmer spot that is not on the bandmap or in ve7cc can be entered into the logbook. It does not use CAT but telnet which is more robust and faster in terms of connectivity.
N1MM had horrible connectivity to Flex when I was working with it. Flex F5K has some specific issues because it has only one transmitter that needs to seamlessly follow 2 receivers as the focus changes. This is the issue I needed to be addressed, as well as a means to change focus as you switched between bands. The best N1MM could do was treat the radio as 2VFO not 2 radio. The biggest issue I had was the brick wall the N1MM coders had against opening up the CAT library to better serve Flex CAT. I'm sure your K3 runs like a drewam with the K3 because EVERY JOT AND TITTLE OF THE K3 CAT LIBRARY WAS LOVINGLY CODED TO TIGHTLY INTEGRATE. I respectfully contacted the coders to see what we could get and basically was told to go pound sand. I get the distinct impression from that crowd they do not want SDR to succeed in the contest arena, or at least are unwilling to lift a finger to better interface with us. I finally lost interest in N1MM because it became clear it would never tightly integrate with PSDR. Writelog/ve7cc client/sdr-bridge/skimmer/ssdr/dax/SCAT/DDUTIL all pretty tightly integrate
The other thing I didn't like is there was little insight into management of virtual ports and virtual audio. It was all about real com ports, LPT ports for keyer inputs and sound cards. I had my F5K set up so I could run 2 streams of RF to 2 amplifiers to 2 coax switches all of which were addressable by BCD, which meant every thing would band follow the 2 receivers and all I had to do was hit the key or stomp the foot switch and the transmitter would address the correct amp/antenna for that band with the correct drive. N1MM was way too klugey to do this reliably. Using DDUTIL and the Flex control I had full control of over 16 functions of the radio including keyer memories and macros. So for example if I had 2 high beams and a low fixed Caribbean tribander I could simply press a button on the Flex control and automatically switch the amp from the high beam to the tribander and back. plus I could tell the system to listen on separate rx antennas because the F5K's antenna switch logic was so strong. I think Gerald himself might have designed that switch. To do that I merely modified some ameritron antenna switches to understand BCD using a LPT port and a couple $19 circuit boards and DDUTIL. No way in hell you gonna do all that with a K3, but with the prudent application of the F5K it was all possible. All of that was lost on the N1MM crowd. They were too busy peeing in their boot over roofing filters so pardon me if I'm less than impressed with the N1MM folks
To quote from an email I wrote to a ham friend several months ago:
"After a bunch of research and program trials, I chose the DXLab suite for my general logging. The logging program is called DxKeeper.
· It uses the Microsoft database engine underneath. It is very robust and fairly portable (not unique to one app). It also allows standard SQL queries which are great for filtering the logbook.
· It connects well with LoTW and eQSL as well as handling traditional paper QSL’s (which I do not use).
· The author, Dave, AA6YQ, is on the ARRL LoTW committee. He is actively updating the suite and is very active on the DxLab Yahoo group (https://groups.yahoo.com/neo/groups/dxlab/info ).
· The other programs in the suite are useful. Particularly, SpotCollector which aggregates the data from up to four DX clusters and keeps its own database of all the spots. This database also uses the Microsoft database engine and has the associated great filtering capabilities. SpotCollector, like the other apps in the suite, is well integrated with DXKeeper.
· The programs use LotW and eQSL callsign databases so that all log entries and spots are marked for their online logging participation. I find this particularly useful since I tend to favor QSO’s with LoTW participants.
· The suite has other apps for rig control, propagation predictions, callsign lookup, etc. They are all well integrated with each other."
The rig control program, Commander, seems to work well with the A and B slices of the 6700 (through a COM port).
The 1.0.4 version of SDR-Bridge has been tested with n1mm+ beta 0.18.3415 connected to SmartSDR via CAT. The combination appears to work except for focus return. (The old n1mm version works and supports focus return.)
Feel free to share experiences and/or problems using SDR-Bridge with SmartSDR CAT and n1mm versions. However please bear in mind that SDR-Bridge is not supported in n1mm or n1mm+ configurations.
73 Ed W2RF
This conversation is no longer open for comments or replies.
This conversation is no longer open for comments or replies.
- 4398 Conversations
- 1185 Followers
- 2496 Conversations
- 509 Followers
- 3004 Conversations
- 748 Followers
- 683 Conversations
- 138 Followers
- 2460 Conversations
- 719 Followers