[hpsdr] Metis/Mercury Bandscope Data (EP=4)

[Phil Harman]

Doug,

I've checked the Metis code and it does have the wideband data on/off 
command included exactly the same as implemented in Hermes.

However,  checking with Wireshark I see  packets with the 
("\xef\xfe\x01\x04") header and full of zeros.

It's late here so only time for a quick look over the code but on the face 
of it I can't see the reason why the on/off command is not working.

I'll investigate further.

There is no (intentional) keep-alive command.   If I set a break point  in 
the KK code then Metis/Hermes continues to send data.  The Tx and Rx paths 
in the FPGA code run completely independently with only C&C data being sent 
between the two paths.

In fact this can be a nuance since a crash of the PC code generally requires 
a power cycle of the FPGA in order to stop it sending data and the PC to run 
Discovery correctly.

73 Phil...VK6PH


-----Original Message----- 
From: Doug Adams
Sent: Tuesday, March 4, 2014 3:35 AM
To: hpsdr at lists.openhpsdr.org
Subject: Re: [hpsdr] Metis/Mercury Bandscope Data (EP=4)

***** High Performance Software Defined Radio Discussion List *****

Phil

After a good deal of testing I think the problem of Bandscope data always 
being sent from Metis/Mercury may be a firmware issue.

Here's what has been done so far, all on a MAC (with a lot of help from Chen 
W7AY):

1. confirmed with Wireshark that I am sending a start command with 0x01 (I/Q 
only) and no other Start commands
2. re-downloaded the firmware files from OpenHPSDR web site
3. erased and re-burned both the Metis and Mercury firmware (using Flynn)
4. using a simple Panadapter program from W7AY, confirmed sending 0x01 works 
for Hermes (firmware v2.4, actually an ANAN-10), only I/Q data is sent
5. using the same Panadapter program with Metis/Mercury sending 0x01, both 
I/Q and Bandscope data are sent (firmware v2.6b & v3.4)
6. confirmed the presence of Bandscope data with WireShark 
("\xef\xfe\x01\x04")

I downloaded the latest Kiss Konsole to my Windows 7 PC. Running it to the 
same Metis/Mercury I can see in Wireshark that even though I never select 
Wideband data, KK sends a Start w/0x03 and Bandscope data is being sent (as 
you would expect). I did not (yet) try changing and recompiling KK to use 
the 0x01 command.

While doing this testing Chen and I also discovered that Metis/Mercury seems 
to stop sending I/Q data after some period of time if no data is being 
returned to Metis/Mercury. Interestingly, Bandscope Data does not stop. We 
were able to ascertain that if we send it something every few seconds it 
continues forever. Hermes does not react this way. Without the "keep alive" 
packets that we send, Hermes will continue sending I/Q data indefinitely.

We would be happy to do more testing but can't think of what else to do. It 
seems that both of the issues we are seeing are unique to Metis/Mercury.

Thank you for your help,

Doug - K3TZR
douglas.adams at me.com






_______________________________________________
HPSDR Discussion List
To post msg: hpsdr at openhpsdr.org
Subscription help: 
http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org
HPSDR web page: http://openhpsdr.org
Archives: http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/ 


---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com


 1393938352.0