Welcome, Guest
Username: Password: Remember me
*****PLEASE, CHECK ALL PREVIOUS TOPICS, BEFORE CREATING A NEW ONE! DUPLICATED TOPICS WILL BE DELETED!*****

TOPIC: ColibriDDC @ Skimmer Server

ColibriDDC @ Skimmer Server 04 Jan 2016 08:32 #1

Hi, I purchased a ColibriDDC a couple of weeks ago but I’m unable to get it properly running with Skimmer Server. With the ExpertSDR2 Software, the ColibriDDC runs properly. So a hardware issue appears to be excluded.

Although the Skimmer Server reports “SDR Receiver OK”, in 95% of the cases nothing happens. The number of Decoders remains at 0, no spots. Occasionally it happens that a few spots are sent (I didn’t checked the reasonableness) but at the latest when I restart everything, the ColibriDDC @ Skimmer Server refuses to work again. To avoid from questions:
• Yes, the ColibriDDC is properly found in the network, its IP address is correctly listed in the ColibriDDC_settings.ini file.
• Yes, the additional DLLs from the ColibriDDC_SkimSrv.zip archive are installed.
• Yes, the latest MS VC++ Distributable Package is installed.
• Yes, I tried on several machines from Windows XP 32 Bit up to Windows 7 64 Bit. The result is the same everywhere.
• Yes, I tested during times of maximum activity on the band (e.g. CQ WW DX contest).

I did a funny test: I ran my TX on a dummy load, sending a CQ loop. The ColibriDDC was in the next room, with just a few centimeter wire as “antenna”. With the ExpertSDR2 Software, I see and hear an empty band with exactly one S9 signal: My CQ loop. Now I shut down the ExpertSDR2 Software and started the Skimmer Server. Result: Nothing. No decoders. No spot. After several tries with shutdown and restart in any imaginable initialization order, I finally got a spot on the correct frequency: N4NZI. The bad news is: The CQ loop ran with my call sign DL8WAA.

Another funny finding: Skimmer Server always reports "SDR Receiver OK", even if there is no ColibriDDC connected to the network.

What’s wrong? Was somebody faced with the same issues? Is there nevertheless a hardware problem? I appreciate any help.
The administrator has disabled public write access.

ColibriDDC @ Skimmer Server 07 Dec 2016 08:43 #2

  • DF1LON
  • DF1LON's Avatar
  • OFFLINE
  • Posts: 11
  • Thank you received: 3
My ColibriDDC took a rest for a couple of month because I had to rearrange my station. This also includes setting up a new PC with Win10. The ExpertSDR2 software (now with Version 1.1.3 RC9) is working fine, with one small expection: if I search for the ColibriDDC receivers the list remains empty. After I set a fixed IP the ExpertSDR2 software is working fine.

Now I wanted to give the CW skimmer server a new try: BUT I experience the same problems as DL8WAA. Even with ColibriDDC turned off the Skimmer Server reports "SDR Receiver OK".

I checked with WireShark if I could see any UDP broadcast packets on port 50001. There are NONE! This means that the automatic discovery function will not work. Neither in ExpertSDR2 nor in Skimmer Server. (just for verification. If I power on ExpertSDR2 I see a lot of traffic, so the port is not blocked by any firewall)

So I entered the values by my own in the ColibriDDC_settings.ini. But everytime I power on the Skimmer Server, the ColibriDDC.dll writes default values in the ini-file
[ColibriDDC]
serial=@ByteArray()
address=@ByteArray()
port=32
attenuator=true

Any idea why the ColibriDDC is not sending any discovery packets?
Any idea why I can not enter manuall settings into the ColibriDDC_settings.ini?

73 de Lars
The administrator has disabled public write access.

ColibriDDC @ Skimmer Server 08 Dec 2016 09:58 #3

  • DF1LON
  • DF1LON's Avatar
  • OFFLINE
  • Posts: 11
  • Thank you received: 3
I did some further investigation on this issue.

I first thought that the ColibirDDC itselft would send broadcast packets as soon as the device is powered. Now I learned that the whole ExpertSDR Search Function is triggered by the ExpertSDR2 software. ExpertSDR2 sends out a broadcast packet on 255.255.255.255 with destination port 50001.

Now I have disabled all Firewall functionality, launched Wireshark and put a filter on UDP port 50001. BUT, there is NO traffic! When I click on Search I would expect to see a broadcast packet. But there is none. Firewall is already deactivated.

Any idea where this data might get lost?
The administrator has disabled public write access.

ColibriDDC @ Skimmer Server 09 Dec 2016 10:57 #4

  • VassiL
  • VassiL's Avatar
  • OFFLINE
  • Разработчик SDR-техники, Developer of SDR
  • Posts: 1299
  • Thank you received: 248
To DF1LON,
You should not switch off firewall, you should add the software to firewall list. Because if you switch off firewall it will block the software packets any way.
Василий, Vasily,
Expert Electronics
The administrator has disabled public write access.

ColibriDDC @ Skimmer Server 12 Dec 2016 08:54 #5

  • DF1LON
  • DF1LON's Avatar
  • OFFLINE
  • Posts: 11
  • Thank you received: 3
The firewall is always switched on. Windows did automatically add rules for the ExpertSDR2 software. I double checked the firewall settings: All UDP and TCP traffic for ExpertSDR2 is allowed. I just switched it off to see if it will make any difference. But it does not.

Just for fun, I installed ExpertSDR2 on an old Netbook. The notebook does not have enough CPU power to run the program smoothly, but the ExpertSDR2 software is able to search and to find the ColibriDDC receiver. On the other PC, where "Found receiver" is not working, I can see with wireshark the UDP broadcast packets send from the Netbook.

Now I have a Netbook which can find the ColibriDDC and my PC which can not find the ColibriDDC in automatic mode.

The command "netstat" lists a lot of used TCP and UDP ports, but no application is listening on TCP/UDP port 50001. So I do not see any reason why the outgoing UDP broadcast packet on 50001 is not send out.
The administrator has disabled public write access.

ColibriDDC @ Skimmer Server 12 Dec 2016 11:56 #6

  • DF1LON
  • DF1LON's Avatar
  • OFFLINE
  • Posts: 11
  • Thank you received: 3
Problem is solft :so_happy:

The problem was the port binding/routing of the IP packets. On my PC I added some time ago a local loopback adapter. So my PC has 3 different routes for the broadcast packet:
255.255.255.255  255.255.255.255   On-link    127.0.0.1        331
255.255.255.255  255.255.255.255   On-link    169.254.1.224    281
255.255.255.255  255.255.255.255   On-link    192.168.0.11     281
because the local loopback and the "real networkadapter" have the same metric, all packets were send to the local loopback adapter.

After disabeling the local loopback adpater
255.255.255.255  255.255.255.255   On-link    127.0.0.1      331
255.255.255.255  255.255.255.255   On-link    192.168.0.11   281
all broadcast packets are send to the correct network card.
The administrator has disabled public write access.
The following user(s) said Thank You: VassiL
Time to create page: 0.060 seconds