I can see all 6 pages in the PDF:
Yes, after a looooooong time all pages now downloaded (maybe that is a bug in my browser, the internet here is super fast) . But unfortunatelly, no levels can be found?
I can see all 6 pages in the PDF:
Yes, after a looooooong time all pages now downloaded (maybe that is a bug in my browser, the internet here is super fast) . But unfortunatelly, no levels can be found?
Did you connect like this? Please check for shorts (Kurzschluss) you might have introduced when soldering the F-sockets.
I no longer have the amsat-downconverter, but the SNR was as good as with any other setup i used later. So if your SNR is not what it should be, (/and you connected everything right) there is definetely something kaput.
If you have a lnb with 2 ports, WB should carry 18V and 24/25MHz , NB should carry 14V.
73, Martin
Edit: I can't download the circuit diagram from the amsat wiki, i only get the first and last page, all others in between are blank.
But i have a copy of this on my HD, so if you experience the same, just ask . I will send you a copy. OTOH, there are no levels shown .
I just installed a fresh raspberry bullseye on my pi400 . Downloaded the QO-100 Transceiver Software. The installation exits with an error "Unmatched Dependencies". Hm...........
There is no need to install it on a raspberry at all. Here it is running on my linux desktop machine as well as on a raspberry pi400.
It even runs on Pi3B+ , but i never tested the performance . I'm quite sure it will also run on Odroid. Just do NOT download a ready made raspberry image with all that stuff preinstalled, if there is any (can't remember right now). Follow these instructions:
https://github.com/dj0abr/QO100_Transceiver
If you get lost, just ask.
73, Martin
oh2uds I have a gigablue Quad with 3 Tuners, i might use one of them for QO-100. It's running on OpenATV 6.3 , i could update it to what is needed. But I'm not sure if my old Quad will run smoothly on newer images. I suspect the newer images are made for newer receivers with more RAM and faster CPU's. Do you have any insight into this? Maybe even the Tuner from the Minitiouner will work in it, when the pinout is the same. Will try to find out. Thanks.
OE6MUE No need to click the </>Code button when you reply. Just click into the blank screen under the "Taskbar" to activate the cursor, then type ahead.
73, Martin
EDIT: Just updated to 7.0 . So am good to go.
<DISCLAIMER> My knowledge about FT-8 is very limited. I once was a member of a small team operating as TO5M from FP, Saint Pierre & Miquelon. My teammates showed me which button to push now and then to keep the program going. So i sat there for a few hours and watched the contacts coming in , filling the logbook. I haven't worked FT-8 from home (not beyond a few test-qso's). <DISCLAIMER>
While i agree with Ernst, PA1EJO, for the most part of his mentioned article, i disagree that FT-8 is a low power mode. If you need the extra 10dB to make a contact on shortwave, why not crank up the power to a kilowatt? Just set everything right to put out a clean signal, or - at least - try do do so. On satellite, you usually have a dish to add the missing dBs to your signal.
No, it is a LOW SIGNAL Mode.
Now that i said that, i really don't understand why most of the FT-8 signals i can see on the satellite are beacon level or even above. There is no real reason for that. Correct me if i'm wrong.
I suspect many FT-8 users on QO-100 just can not monitor their signal because they can not receive while they transmit. They will never know they triggered Leila, because their transmit cycle is longer than the warning signal coming from Leila. Even if they hear or see Leila, most people on QO-100 think "some 1D10T triggered Leila, but not me". <polemic on>This also applies to many SSBers.<polemic off>
Flamesuit on.
73, Martin
Hi,
ON7EQ JO11OC, according to his QSL-card on qrz.com
UA9FFF LO87IW
4X0SAT KL79LS
OR18HCC depends who the operator was
V55JAM is near WalfishBay , so should be easy to find using this tool:
https://k7fry.com/grid/?qth=JG77
but i think it's JG86
Hope this helps.
73, Martin
That is beyond my knowledge about programming, but tnx.
73, Martin
mkfifo longmynd_status_fifo
Yes, that's what i did.
I hoped it runs on my linux based gigablue receiver, but no joy, the architecture is very different. Maybe i should buy a octagon.... For now, I'm happy being able to run it on a headless raspberry3 and watch it via UDP on my linux machine. Will also try to run it on an old raspberry 1 (or is it a 2? ) to see if that works. Now , if someone could set up a remote ....
73, Martin
Trying to remote longmynd from the DJ0ABR QO-100 WEBSDR and a Pluto fails, while it woks when longmynd is started "normally".
Setup here: Raspberry Pi3 , Minitiouner, QO-100WEBSDR on Lubuntu 20.04.
73, Martin
Baris,
tnx for great info. I got this error:
pi@raspberrypi:~/longmynd $ ./longmynd -i 192.168.0.28 1234 -s longmynd_status_fifo -p h -r -1 -S 0.5 741500 1500
Flow: main
Status: Main Frequency=741500 KHz
Main Symbol Rate=1500 KSymbols/s
Using First Minitiouner detected on USB
Main TS output to IP=192.168.0.28:1234
Main Status output to FIFO=longmynd_status_fifo
Main refers to TOP F-Type
Polarisation Voltage Supply enabled: H, 18V
TS Timeout Disabled.
ERROR: Failed to open fifo longmynd_status_fifo (error: No such file or directory)
ERROR: fifo init
Flow: Main loop aborted, waiting for threads.
Flow: All threads accounted for. Exiting cleanly.
It seems, longmynd wants to write into a file, so i created fifo longmynd_status_fifo , is that the way to go? The start looks ok now:
pi@raspberrypi:~/longmynd $ ./longmynd -i 192.168.0.28 1234 -s longmynd_status_fifo -p h -r -1 -S 0.5 741500 1500
Flow: main
Status: Main Frequency=741500 KHz
Main Symbol Rate=1500 KSymbols/s
Using First Minitiouner detected on USB
Main TS output to IP=192.168.0.28:1234
Main Status output to FIFO=longmynd_status_fifo
Main refers to TOP F-Type
Polarisation Voltage Supply enabled: H, 18V
TS Timeout Disabled.
Status: opened fifo ok
Flow: FTDI init
Flow: FTDI USB init
Flow: FTDI set mpsse mode
Flow: FTDI USB init
Flow: FTDI set mpsse mode
Flow: FTDI setup io
Status: MPSSE Synched AA FA
Flow: FTDI nim reset
Flow: FTDI GPIO Write: pin 0 -> value 0
Flow: FTDI GPIO Write: pin 0 -> value 1
Flow: UDP Init
Flow: NIM init
Flow: STV0910 init
Flow: stv0910 init regs
Status: STV0910 MID = 0x51, DID = 0x20
Flow: STV0910 set MCLK
Flow: Setup equlaizers 1
Flow: Setup carrier loop 1
Flow: Setup timing loop 1
Flow: Tuner init
Flow: Tuner cal lowpass
Flow: Tuner set freq
Flow: Tuner set freq
Status: tuner:0, f_vco=0x2d41f0, icp=0x2, f=0x2eeee, n=0xc5,
rdiv=0x1, p=0x1, freq=741500, cfhf=2331
Flow: LNA init 1
Status: found new NIM with LNAs
Flow: LNA init 2
Status: found new NIM with LNAs
Flow: FTDI GPIO Write: pin 7 -> value 1
Flow: FTDI GPIO Write: pin 4 -> value 1
Flow: STV0910 start scan
But i don't see the stream on my vlc. What is the correct command to open the stream in vlc?
EDIT: udp://@:1234 . It works!
73,
Martin
An Attenuator about 10dB should do the trick. https://m0ukd.com/calculators/pi-attenuator-calculator/
Make a PI attenuator : 100 Ohm to Ground , (33+39=) 72 Ohm in series with the Signal , 100 Ohm to Ground
73, Martin
GM,
do you say you set up your 9700 for working with satellites, e.g. set TX to 432,200, set RX to 144.700 , interlock the VFO's so RX follows TX (and vice versa), then connect your 9700 to OmniRig and OmniRig messes this up? There are 3 .ini-Files for the 9700, one is named Ic9700-sat.ini . Use this.
Disclaimer: I have no IC-9700.
73, Martin
Maybe the BPF is too big a load for the internal oscillator, it prevents it from operating. I use a similar method to feed external 116MHz into my 2m transverter via a Resistor and a Cap. I leave the internal oscilator in place while i feed from external source, but the internal oscillator stops working when i do this. It resumes work when i unsolder the C and R combination.
73, Martin
Well, if they just qsy up 1 khz, the beacon will still be heard by qo-100, but in the clear. You can always check if the beacon is operational, even if your rx on 13cm is crappy or if you are out of range .
Now it is of interest what power and antenna they use. Maybe we hear a sidelobe.
The goonhilly websdr seems to have a strong carrier exactly on the upper beacon higher tone, thus can not resolve SK0EN/B . IS0GRB can.
73, Martin
Hello,
IIRC there are some lnb's with 2 tcxo's and 2 pll circuits onboard. Can anyone confirm this? Or was there 1 TCXO, but 2 PLL circuits. If the first applies, remove one tcxo for the use of NB Transponder and inject external 25MHz. Keep the other one installed for the DATV-Transponder.
73, Martin
Maybe some mixing?
I looked up info the moment i got the call right , but found their website stating "Not qrv yet". There is no info about the website admin or any mail address. Maybe the forum members from SM with contact to the beacon owner can shed a light on this.
Soundample here: DM4IM
I noticed a carrier buried under the higher tone of the upper beacon. Only audible when the tone pauses . After listening for a while it turned into morse and i noticed it was keying SK0EN/B JO99JX.
73, Martin
Well, there's the rub:
There is no wired ptt.
It's appreciated the manufacturer intented to make it easy to use, but this in turn creates a problem by not providing wired ptt.
The AMP HAS wired ptt and VOX, but the upconverter has no ptt in or out.
You need 100mW to trigger VOX. I'm pretty sure, with 100mW INput the Output on 13cm is more than 100mW. The amp max. drive is 80mW.
Thus , if you use it according to the manual, your options are:
Clean, but stuttering signal. The upconverter stutters because input level is low.
Clean but stuttering signal, because upconverter AND amp stutter, same as above.
Distorted signal without stutter, because you provide enough input power.
No signal at all, because you can not trigger VOX from a too low input level.
There may be a small power range where all is ok. But again, it is not clarified in the manual. Oh, i know , you must insert an attenuator between upconverter and amp. This is not stated in the manual, either. Just put everything together, you will be fine. NOT!
Look at the transponder. If I'd place bets which signals are coming from this brand, i'd win more often than loose.
Yes, i know, there are dirty signals coming from other brands, too. Some users care, some do not, others just don't know because nobody tells them so.
73, Martin