开云体育

Log output of tinySA

Erik Kaashoek All Messages By This Member #786 As requested, inverse order (latest on top), generated by enabling the logging in tinySA.exe Scan of 100 points from 0 till 100MHz Send by tinySA: "<<" Received by tinySA: ">> "__" means CR/LF as sometimes multiple responses on one line <<VFO: 1__Output frequency: 483700483__ <<e <<x52? <<x65? >>o483700483 >>v1 <<x50? <<x61? <<x50? <<x47? <<x49? <<x51? <<x61? <<x143? <<x49? <<x60? <<x62? <<x57? <<x54? <<x58? <<x64? <<x60? <<x48? <<x70? <<x46? <<x60? <<x46? <<x50? <<x120? <<x47? <<x51? <<x46? <<x64? <<x53? <<x52? <<x55? <<x52? <<x52? <<x55? <<x50? <<x48? <<x51? <<x49? <<x145? <<x50? <<x52? <<x50? <<x50? <<x52? <<x49? <<x49? <<x51? <<x49? <<x53? <<x50? <<x61? <<x49? <<x52? <<x146? <<x53? <<x46? <<x52? <<x50? <<x56? <<x49? <<x55? <<x58? <<x56? <<x51? <<x50? <<x46? <<x50? <<x49? <<x147? <<x49? <<x47? <<x50? <<x50? <<x54? <<x65? <<x68? <<x50? <<x55? <<x51? <<x56? <<x56? <<x60? <<x60? <<x171? <<x59? <<x62? <<x80? <<x61? <<x50? <<x55? <<x74? <<x67? <<x53? <<x72? <<x57? <<x53? <<x61? <<x89? <<x195? <<b <<a VFO: -1__Steps: 100__ <<x29300? <<time pr step: 10__E >>m <<Output frequency: 433700000__Width: 10000__VFO: 1__Start: 433700433__Stop: 533700533__ >>t10 >>b533700533 << = 0__Parameter? 6 = 0__VFO: 1__Output frequency: 483700483__VFO: 0__ >>w1000 >>o433700000 <<Parameter? 5 >>p6 0 >>p5 0 ? -- HBTE Files section:?/g/HBTE/files Erik, PD0EK
Jerry Gaffke All Messages By This Member #787 Excellent, that's perfect!!! Jerry toggle quoted message Show quoted text On Wed, Jan 22, 2020 at 11:00 AM, <erik@...> wrote: As requested, inverse order (latest on top), generated by enabling the logging in tinySA.exe Scan of 100 points from 0 till 100MHz Send by tinySA: "<<" Received by tinySA: ">>
Jerry Gaffke All Messages By This Member #789 Erik, If that is not from the Jan 17 tinySA.ino currently in the files section, could you post the code it corresponds to? Though I may have all I need if the Jan 17 tinySA.ino file? was working well enough..? Here's few inconsistencies between that recent trace and the tinySA.ino code in the files section" The history you sent appears to be much less verbose than what should come out of tinySA.ino. Now using 'b' and 'e' instead of '{' and '}' around the sweep data. A bit of weirdness near the bottom, the "VFO:1" looks like the tinySA acknowledges a "V1" command between the "p6 0" and the "o433700000", but that "V1" command? was apparently never sent. << = 0__Parameter? 6 = 0__VFO: 1__Output frequency: 483700483__VFO: 0__ >>w1000 >>o433700000 <<Parameter? 5 >>p6 0 >>p5 0 Likewise and perhaps related, we get a "VFO: -1" acknowledgement right in the middle of the 'm' command acknowledgement. I see nothing in the source that would bring this on, even if we assume Serial.write() is totally out of sync with Serial.print() as seems to be the case with this Arduino stuff.. Jerry, KE7ER
Jerry Gaffke All Messages By This Member #790 I'm pretty far along with the Jan 17 tinySA.ino file. Will probably stick with it unless there's a significant reason to go with newer code. Hope to eventually be using the native RPi display, not the 2.8" TFT. Jerry toggle quoted message Show quoted text On Wed, Jan 22, 2020 at 01:53 PM, Jerry Gaffke wrote: If that is not from the Jan 17 tinySA.ino currently in the files section, could you post the code it corresponds to? Though I may have all I need if the Jan 17 tinySA.ino file? was working well enough..?
Erik Kaashoek All Messages By This Member #793 As the code it multi threaded things get "out of order" in the logging. The logging is wrong, should be {} -- HBTE Files section:?/g/HBTE/files Erik, PD0EK

Previous Topic Next Topic