@all
As I said I am here to get your experience before buying. I been without Sat equipment for over 5 years. No hurry, I can wait a little longer while you provide your experience. I want a receiver for every day TV use, no special project.
But yes if you read my post on Encryption Chat, to do some logging I was motivated to return and have a Sat system working now. But that has no importance on receiver selection. Unless some one show some light if any America Sat provider is on the list of any of the IKS Sharing providers.
A note on Cellular 5G, yes I know 5G generate noise in C-Band for most of the world. But in USA is worst. It is not just noise jumping from other frequencies. In USA, the FCC(Government) Re sold the lower part of C-BAND 3.7-4.0Gz, well 3.6-3.7 was already gone.
They convince the Sat community to liberate 3.7-4.0 Gz while the Government made them compensation payments. So we do have out of frequency noise jusy ;ike all fo you. But we also have 5G actually been transmitted at 3.7-4.0 Gz.
@EnoSat
You never reported me if you will consider that TBS5930 works on crazyscan/esb etc. Can it do blindscan, spectrum or FFTScan, I can only guess your silence means no.
@moonbase
Yes I have noted that "that the zgemma H11S has blind scan problems.". Message received. If I responded you about H11S was to show that it contradicts your comment on "..model that is not in the budget end of the market."
I know more money we spent more feature and quality received. And as you did ask, I too will love to know if there is a receiver that do most of todays transponders. even if it cost more. It will be our base line.
@mdkgr
Thanks for your suggestion. I have Laptops and PCs, no need for extra one. Except for PCI-E that I do not have on my PCs. The following is not to correct you but to clear those question you did make me.
About firmware. In general WIndows pack firmware or microfirmware inside Windows Driver. A windows user do not have to know about it.
In Linux firmware/microfirmware are separate thing from driver. We as OS users have to worry of having the needed firmware located in our Linux OS. But as Windows user when you install your driver most likely the firmware is added too to the OS.
About brick it yet with the firmware changes. It does not work like a firmware for a phone, where you can brick it.
There are a few devices that are packed with a generic USB Interface. So it can talk with Windows PC. But it does not have the code to function, in other words, the device will do nothing once it is hook because it is a blank black box.
So every time you powerof device or rehook USB, Windows see its VendorID+ProductID, it knows it has to send the firmware needed. After it device is reboot, usually with new VendorID+ProductID, And then the device works as expected. Now it has the code to do its function. It is a Live/temporary programing. Not like a Phone or Receiver that has a one time Fix Programing. Now Why manufacturers do such a thing!!! Well the device is cheaper because they do not have to include a Flash eMMC. All run from ram.
I show you, in linux it is easy to see a debug
Let say I am in Linux and I have no firmware on OS. So device do not work. This is what I find in USB.
Code:
Bus 002 Device 004: ID 04b4:8613 Cypress Semiconductor Corp. CY7C68013 EZ-USB FX2 USB 2.0 Development Kit
PC do not even know it is a dvb device. It recognized as a FX2 USB 2.0 Development Kit
Now let me install the firmware, in this case 2 of them: dvb-usb-dw2102.fw dvb-usb-p7500.fw
Now I hook USB and I see:
Code:
[ 279.933272] usb 2-1.1: new high-speed USB device number 7 using ehci-pci
[ 280.041845] usb 2-1.1: New USB device found, idVendor=04b4, idProduct=8613, bcdDevice=a0.01
[ 280.041852] usb 2-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 280.348098] usbtest 2-1.1:1.0: FX2 device
[ 280.348101] usbtest 2-1.1:1.0: high-speed {control bulk-in bulk-out} tests (+alt)
[ 280.348128] usbcore: registered new interface driver usbtest
[ 280.348129] systemd-udevd[19391]: Process '/sbin/fxload -D -I /lib/firmware/dvb-usb-p7500.fw.hex -t fx2 -m 0666' failed with exit code 255.
[ 280.554116] usb 2-1.1: USB disconnect, device number 7
[ 282.313267] usb 2-1.1: new high-speed USB device number 8 using ehci-pci
[ 282.422040] usb 2-1.1: config 1 interface 0 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 2
[ 282.422616] usb 2-1.1: New USB device found, idVendor=3034, idProduct=7500, bcdDevice= 0.00
[ 282.422622] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 282.422626] usb 2-1.1: Product: DVB-S USB
[ 282.422629] usb 2-1.1: Manufacturer: Prof Group
[ 282.720230] dvb-usb: found a 'Prof 7500 USB DVB-S2' in cold state, will try to load a firmware
[ 282.729989] dvb-usb: downloading firmware from file 'dvb-usb-p7500.fw'
[ 282.729991] dw2102: start downloading DW210X firmware
[ 282.845281] dvb-usb: found a 'Prof 7500 USB DVB-S2' in warm state.
[ 282.845532] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 282.845691] dvbdev: DVB: registering new adapter (Prof 7500 USB DVB-S2)
[ 282.845696] usb 2-1.1: media controller created
[ 282.975037] dvb-usb: MAC address: ff:ff:ff:ff:ff:ff
[ 282.975288] dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
[ 282.993191] stv090x_attach: Create New Internal Structure!
[ 282.993194] stv090x_setup: Initializing STV0903
[ 283.041257] stv090x_setup: Setting up initial values
[ 283.078335] stv090x_setup: Setting up Cut 2.0 initial values
[ 283.089197] stv090x_attach: Attaching STV0903 demodulator(1) Cut=0x20
[ 283.089203] dw2102: Found STV0900 @0x6a
[ 283.093358] stb6100_attach: Attaching STB6100
[ 283.093359] dw2102: Found STB6100 @0x60
[ 283.093543] dw2102: Attached STV0900+STB6100A!
[ 283.093549] usb 2-1.1: DVB: registering adapter 0 frontend 0 (STV090x Prof 7500)...
[ 283.093554] dvbdev: dvb_create_media_entity: media entity 'STV090x Prof 7500' registered.
[ 283.121269] Registered IR keymap rc-empty
[ 283.121382] rc rc0: Prof 7500 USB DVB-S2 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/rc/rc0
[ 283.121417] input: Prof 7500 USB DVB-S2 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/rc/rc0/input27
[ 283.121498] dvb-usb: schedule remote query interval to 150 msecs.
[ 283.121500] dvb-usb: Prof 7500 USB DVB-S2 successfully initialized and connected.
[ 283.121536] usbcore: registered new interface driver dw2102
See 1rst 6 line it is where
FX2 USB 2.0 Development Kit is detected.
In line7, with fxload -D -I /lib/firmware/dvb-usb-p7500.fw.hex I force the load of the 7500 firmware
Line 8 to the end, the normal process is performed. In fact Firmwares are re upload and dvb tuner, frontend, demuxers are initialaze.
At the end I endup with
Prof 7500 USB DVB-S2 successfully initialized and connected
Now you are correct, once I see if I can have a strong 8psk signal, I should re install old original windows driver from TBS. They are going to be about 5 years old because TBS now do not even recognize TBS5920 existence.
Why we need Spectrum? A guy like you most have a motorized sat antenna. You do not have to worry about manually align an antenna. God bless you. Now Spectrum Image is the most easy way to know you are manually pointing to a Satellite. The Satellite Spectrum is UNIQUE for each satellite. So just by a 2-3 second scan you can rapidly distinguish what satellite you are pointing. Plus if you see a Spike, it means there is a close by noise that is affecting your reception. So it is easyly just to use ONLY the Prof7500 for ONLY manual antenna adjust, while using regular driver for best reception, in the event that you are correct.