Reply to thread

Message

<blockquote data-quote="satesco" data-source="post: 1160066" data-attributes="member: 297935">I did the first test with IQmonitor version 2.0.3.0 and was happy that the app found 12620 V each time. However, since I could not save it because of the error &quot;Is not a valid floating-point value,&quot; I then worked with version 1.0.2.8. The only problem after I found the frequency was being able to scan it manually. As it is between two muxes with strong signals, the app found it quite hard, maybe because the symbol rate is lower than the two. In this case, I decided to scan it manually with the same frequency, 12620.61 V. From this moment, I could lock it and use it to stream.(As you know, the decimals on freq are not set in stone, they can change depending on outside influences. In our case, the interference from the two closest ones makes it difficult to find and lock 12620 V).I did the same thing with EBSpro.Of course, as you know, you can only lock such a low symbol rate when the frequencies are so close with only 6983/6903 cards.Here is what I got yesterday with version 2.0.3.0 and the 6983 cards, and how I configured it with version 1.0.2.8; I chose step signal search 200.</blockquote>

[QUOTE="satesco, post: 1160066, member: 297935"] I did the first test with IQmonitor version 2.0.3.0 and was happy that the app found 12620 V each time. However, since I could not save it because of the error "Is not a valid floating-point value," I then worked with version 1.0.2.8. The only problem after I found the frequency was being able to scan it manually. As it is between two muxes with strong signals, the app found it quite hard, maybe because the symbol rate is lower than the two. In this case, I decided to scan it manually with the same frequency, 12620.[B]61[/B] V. From this moment, I could lock it and use it to stream. (As you know, the decimals on freq are not set in stone, they can change depending on outside influences. In our case, the interference from the two closest ones makes it difficult to find and lock 12620 V). I did the same thing with EBSpro. Of course, as you know, you can only lock such a low symbol rate when the frequencies are so close with only 6983/6903 cards. Here is what I got yesterday with version 2.0.3.0 and the 6983 cards, and how I configured it with version 1.0.2.8; I chose step signal search 200. [/QUOTE]

Verification