Posts by supwiddiss

  • Nagravision

    I would share details in private. You don't want to mess with iks for dn in the US. Period. Search satscams. A clever name.
    PV, biss, I think tb (director). Unlike Eurpoe I don't believe there are any card based subscriptions here.

  • Bricked receiver. Need RS232 methods assistance methods.

    Quote from lme

    Agreed.

    tnap is a more reliable image, with of course few hiccups as everyone. I had hard times to reprogram my remote as the others images have it.

    This kind of ate me this evening. I can't say it's more reliable than anything. It surely is stripped down. And looking into it. You see hints of softcam but installing one is quite difficult. I have streamers. Roku, Fire Cube. Kodi is installed, YouTube.
    I purchased a satellite receiver for satellite reception. The streamers can use Bluetooth keyboard and mice. Tons more easy than pecking a RCU plus the fact it is going to wear out soon enough from normal use. An image like PurE2 is packed full of crap. And Open Blackhole is stripped to the tits. It only lasted long enough to deem it's a POS image.
    OpenATV is great because, as you know, you can turn on a receiver and config it. And a 3 year old can use the RCU. And the wifey. Because someone was actually thinking. Since we rely on remote to use everything TV related these days. What brain trust decides to make even a seasoned user stress out trying to make sense why they may map a remote the way they do.
    Make it so the remote control closely as possible mirrors a television remote control. Just like Dish and DirecTV does. For chrissakes! Lol!
    I don't give a crap. Hit the TV store and pick a brand. Grab the remote. They all resemble each other in functionality.
    Slap in PurE2, what else?.....PLI. What a trip.

    Some things make sense. TNAP is tweaked to work the way it does because EB is able to work with the tuner/demodulator manufacturer.
    At the time. I was able to contact Edision who contacted Availink. And received several different tuner drivers to try out and report back.
    That was a pleasant response. But the others who use outdated components discontinued years ago with closed source code and limited documentation to build a receiver. Because there are piles and piles of them for a buck or 2 apiece. They suck.
    "We have a box, and a hunderd of them. They cost this much. The online brochure is right here. We don't know crap about them. And don;t really care to. As long as we sell them. If they break, we can warranty them. Maybe. Oh! You have your choice of tuners for them. Take your pick. We can't tell you anything about them except they plug inside of the receiver".
    Pretty crappy business practice. And pees me off immensely.
    I love my local photography and computer stores. The guys and gals there not only are enthusiasts who know the equipment they sell. But can show you up front what makes one more cooler than the other. And tell you why. And if you end up buying something from them, that's even better for them.
    kirk out.

  • Bricked receiver. Need RS232 methods assistance methods.

    Quote from lme

    So, from what you described, I take it that openatv image is not to be trusted anymore...

    Absolutely not the case. if they would put the Services option in Signal Finder. Probably a few other things. It would be my primary image again.
    European folks don't realize much of C Band. Dish size limits would be my reasoning. But if feed hunting and using a great blindscan capable receiver is important. The TNAP dev. took a pretty good receiver and actually put a bit of elbow grease into making it very cool to use.
    If the importance of 2 MHz transponder spacing and the chance of missing a pile of them in scanning for feeds, wild hauls. Or times where a flyaway might be put up to broadcast an event, etc. If not relying on published and seldom updated transponder lists and reports is your game. Well. I think you get it.

  • A discussion for the sponsor WOS

    Quote from abu baniaz

    It is not the receiver that facilitates the blindscan, it is the tuner. The new Vu tuners do not blind scan, the old tuners blind scan. The Ultimo 4K can accept the old tuner. Think of it like ISA and PCI slots on a motherboard. Just duck duck go the receiver images and compare the tuner slots.


    You could always get a USB tuner. Sundtek's are the best supported. I am pretty sure they do blind scan, someone will have to confirm.

    Oh. Some confusion. I thoroughly understand the tuner construction.
    The L-Band tuner that receives and discriminates the L.O. frequencies passes those signals to the demodulator (Avialink AVL6XXX for ex.).
    The tuner is controlled by the demodulator which is controlled by the MCU (Broadcom, etc.).

    Let me do an analogy so we don't have a back and forth session.
    If you take the Edision Osmio4k. It has an Avialink AVL6261 demodulator in its soldered-in tuner module.
    And the receiver blindscans brilliantly.

    Take the same receiver and if there was a way to put the horribly advertised and "blindscan" capable Zgemma H7.xx variety with the demod. it has and pyt it in the mio. Even with the correct .ko modules.
    It ain't gonna' scan.

    But if you are hinting that no VU+ receiver with the plethora of plug in tuners out there do poor jobs of blindscanning for feed hunting, etc.
    Screw it then. Because here. You cannot rely on satellite charts and .xml generators or Lyngsat for the latest transponder finds.

  • A discussion for the sponsor WOS

    Quote from abu baniaz

    The only recent highend Vu+ that is going to be able to perform blindscan is the Ultimo 4K. It also has the old style connection on motherboard so that you can use the older tuners from the Uno, Ultimo, Solo SE, Solo SE2, Duo2. Solo 4K also has the legacy connector.


    Duo 4K, Duo 4K SE, Uno 4K, Uno 4k SE only have the FBC/MTSIF connections.

    Thank you. Looked up the acronyms and came up with tuners for MTSIF connectors are only for terrestrial/cable tuners.
    I'm only interested in satellite. DVB-S, S2, S2X tuners.
    Perhaps I could be mistaken.

    FBC is confusing. Is that a type of port specifically for full band capture tuners. Or as hinted in the OBH forums from a search.

    “fbc style” “pcie style” connection).

    Would the fbc label actuallly be a pcie port? Standardized as in pc's. Where a third party tuner could also be used.
    Or is it a proprietary VU+ connector and pinouts?

    They label their tuners. And Abu, you mentioned the Ultimo 4k which is what caught my eye. And the fact that it can blindscan.
    But with what tuner ("Of my choice"). And how well would it perform versus another in a comparative test?
    And of course. If in the test. What tuner/demod. chip is in them?
    A screenshot of the webif Box info tells all.

    Perhaps Broadcom STB chipsets are outdated. Rumored that they are getting out of the FTA market.
    Octagon caught my interest as well as Gigablue.
    And TBS has been a very serious option.

  • A discussion for the sponsor WOS

    I have been seriously considering one of the VU+ receivers for quite awhile. I've even contacted World of Satellite by email.

    There seems to be a lack of details in the pluggable tuner selections. And I would ask of the staff or forum members if they could provide a bit of information.
    Number one is the numerous pluggable tuners offered for the different receivers. I am not sure if VU+ has engineered a standard socketing scheme so that many different tuners will fit in their receivers. Or not.

    With blindscanning being very important. And discovering that FBC tuners will not allow a receiver to perform them. Those tuners are out of the selection.

    World of Satellite. I have asked you for detailed information for the different tuners offered for your higher end VU+ satellite receivers. Numerous times. To no avail.

    Even your Octagon SF8008 receiver specifications section lists the tuner/demodulator as:

    DVB-S2X: Silabs Si2166-D60 & RDA5815m
    Probably a perfectly performing tuner for blindscanning, considering Silabs track record. Or as in the Edision Os Mio4k, an Avialink AVL6261. An excellent tuner for the purpose.

    It appears as if your specifications pages are printed straight from the manufactures supplied literature.
    The main chipset types. Broadcom. Are listed. But nothing on what is contained in A vs B tuner selections.

    In an Enigma 2 receiver it is easy enough to find the box information. And surely you folks must have a few laying around in operation.
    In the box information it should display exactly what tuenr/demodulator chips are in the pluggable tuner currently installed in them.

    You have to agree that some very important details are missing. And something that WOS staff should readily be able to tell a potential customer.

    The cost of a higher end receiver and shipping. Plus duties and the fact that by the time I received one from you. The return policy would have expired.
    Possibly with deficiencies such as poor or no blindscanning being discovered upon delivery.

    Perhaps users of different VU+ receivers. The VU+ Duo 4k SE catching my eye. With "My Choice of Tuners". Making the incorrect choice being on my shoulders.

    Could some of you guys reply with what model number, type of tuner chipsets are in the tuner you have. Please. FBC is out 100%,
    And your opinion of the blindscanning performance. Better if you have a different brand of receiver to compare with. Again. Please.

    One last thing if I may. What exactly is the purpose of the TPM chip in the VU+ receivers? Others don't seem to have a need for one.
    This puzzles me something fierce.

    I appreciate World of Satellite reading this post to see if in the future more detailed information could be supplied in a receiver or peripheral's specifications.
    It would clear up an issue I have of being a big warehouse with boxes and boxes ready to ship. But not knowing anything of the product you vend.

  • Bricked receiver. Need RS232 methods assistance methods.

    For the Os Mio4k only.
    Just an addition from tinkering around.
    The TNAP E2 image has had the drivers tweaked through the developers hard work with Edision and far surpasses any of the drivers included in other image versions. By far.

    I do not particularly like or dislike the TNAP images. I just don't prefer. Just flashed ver. 5. It's nice. Just kind of stripped down.
    One thing for sure. A blindscan of most satellites turns up more transponders than you can believe.
    And on the newest NOAAPORT tp on 121W 4020V. A data only sat.
    I could never get a solid lock on it. Usually it appeared as if it wasn't even there.
    In TNAP it locks solid. And closely spaced frequency tp's scan in brilliantly.

    Okay. If you use OpenViX. Maybe you would like to try this. Phenomenal results for blindscans.
    Full backup your current ViX image.
    Take the attached AVL6261 driver (extract it first on your pc) and replace the existing one through FTP to the Mio.
    Before you do though, rename the existing one to something like:
    avl6261.ko to avl6261.ko.bak
    Set permissions to 755.
    Reboot the box.

    The path to the tuner drivers is:

    /lib/modules/5.15.0/extra

    Try blindscanning a sat that charts show more tp's. than you were able to scan in before the change. Wow!
    If you have an Os Mio4k+. You could take the TNAP drivers from the same path and try inserting them in a ViX image the same way.
    Just make sure you know what you're doing. In the webif, box info. It will tell you all you need to know.
    Happy hunting, Mr. Vick.

    avl6261.zip

  • my sat dishes

    So you mean even if you have 100 hectares you can only have a maximum size dish over there? That kinda sucks.
    No knock-knocks over here if you don't have a HOA.


    500.jpg


    Meanwhile. On this side of the pond.....
    131W-45W sweep with DISEqC 1.2 control. C & ku. 12' or however many meters and fractions of.
    I think this dude took a bit of dishagra on the trip over there. Because look at all of your babies! lol!!
    Joking...

  • Bricked receiver. Need RS232 methods assistance methods.

    Jens,
    That's what is making me go nuts. Figuring there must be a command to replace the incorrect splash with the correct one.
    Tried both USB ports with the right splash installer as well as an older smaller file size emmc image as someone suggested.
    Still not seeing any signs of USB anything.
    I was hoping the bolt manual would tell something of 'put' or 'replace' or even splash create splash file.

  • Bricked receiver. Need RS232 methods assistance methods.

    I have a console. Was able to ctrl+c to break boot.
    Found a message telling me I need a new version of the boot image.
    The Edision boot image is mush smaller and is the intended one than the one that got written.

    Not concentrating on the failure. Only the fix. Please. If we can zero in on that.

    I have searched the world over for a BOLT bootloader manual.
    In putty I know the ctrl+c shows I do have keyboard and TX from my pc.
    But typing the first thing you try, help, gives no text in putty of the characters. Perhaps another terminal program?

    Attached are the osmio4k USB files. In them the images are renamed .bmp so you can see the issue.
    The incorrect and unintended one is probably just too big for the nor flash. But at least it didn't kill it.
    The normal and ctrl+c boot text is attached.
    Of interest is further down where I'm told to use a different boot image file and it shows the file as being HD in pixels versus the factory boot image only 720 X 576 pixels.

    Going for an Ibuprofen break. A well needed one at that. With the little bit of humo(u)r I have left. Should I have asked if we could "Zed: in on the fix?
    kirk out

  • Bricked receiver. Need RS232 methods assistance methods.

    Actually the FTDI serial adapter was used with my Titanium Satellite ASC1 dish mover. To send and receive programming data for satellite names and positions. Too bad it was discontinued. Anyway. It worked so good on the mover's RS232 port to my pc. I kind of got interested in USB over I.P.
    Lo and behold there is a slick Linux application from Virtual Hub named vhusbd. And a client for Windows. I think other os also.
    Launch the server app on my router with the cable attached to it and the mover. And on my pc a new device , the FTDI com port pops up in dev. mgr.
    Bang! Full control of the mover to send and receive sat. data. Off topic. And you're right although if I do recall. A real serial port is the best way to go. But I do believe unless software settings allow it. RX is RX and TX is TX on DB9 ports. And if for example a pc to pc connection is needed you need a crossover cable. Versus a modem (remember them!) or other peripheral where a straight thru cable will work, as their ports are already wired with the TX/RX crossed.
    But hey I could be wrong. RIght now I'm even doubting my skills installing a pip squeak piece of software. A bit in arms here. Without the earrings and the makeup!! haha

  • Bricked receiver. Need RS232 methods assistance methods.

  • Bricked receiver. Need RS232 methods assistance methods.

    Hey Mr. Jens!
    Yeah. Stressful it is here. Using the old Zgemma H7 right now. It was used as a client and was doing well. Hate not having blindscan.
    I searched and saw you did dive a bit into serial flashing in the past. I was going to bug you on it but you beat me to it.

    There's a link attached that maybe you can look at and say ......hmmmmm!
    I found it very interesting.
    My FTDI cable died so I just received a couple today. Tested and working in a quick loopback test.

    Let's carve one thing in stone so it's 100% clear. I think I've been pretty thorough.

    1) Flashed the factory Edision boot logo file that Openatv hijacked with theirs. Hijacked meaning it showed on boot in every slot no matter what image I chose.

    2) The file, I had used before at least twice. Not much to it as far as content. It was sent to a freshly formatted USB and inserted in the receiver.
    It booted, 'boot' showed on the display and then 'flsh'. The process took just a few seconds. It finished and the receiver rebooted.
    The Edision logo then showed on every boot before the image splash screen. One any slot with an image.

    And stayed that way until I once again flashed Openatv to any slot. Then it's boot logo hijacked the receiver again.

    3) This time. Same procedure. Freshly formatted genuine Sandisk 2GB USB. FAT32. Sent the osmio4k folder to it. The rest is stated above.
    Except on the following boot. 'boot',. Then the progress counter made it to 50 and hung forever.
    Powered it down. Pulled the USB. Powered it on. Nothing. Nothing at all.

    3) Tried another USB with the same file. Tried lo load an image. 'boot'never displayed.
    Waited and waited for something to happen. Nada, zip, zilch, zingo. AKA: &8@%.

    So everyone with try another USB, etc. suggestions. Not working. And apparently I'm not the only one these things happen to.
    But. A revelation.
    I was able to find data activity on my oscilloscope, The same as I may do when flashing custom firmware on a router.

    Jens. Of all of the things I do regularly. I have never Jtagged anything. Don't even have a programmer. All so far is using serial protocol.
    I was targeting the Edision receiver with its serial port. I thought 'what about Zgemma?'.
    After a few days of surfing the net. COntacting Edision.gr. No help from them.
    "Kindly" suggested they contact China. As most of their receivers have RS232 ports. And the user manual states its usage.
    Nothing further. "It's for pulling logs" finally after a few back and forths.
    "Well dammit, give me the procedure for pulling logs then". Proper inquiry? Without the dammit.

    Thoughts of pulling the boot flash. A Winbond chip I've seen on motherboards and have revived dead pc's, laptops before.
    "The unzipped image files contains hints of emmc this and that". Do I pull the emmc flash and see if massaging it after a bit of Neo learning Jujitsu?
    I hate reballing chips.

    My feeble mind tell me that perhaps the USB was corrupted.

    And by comparison of image files versus the Edison logo file. Only really the boot image is on the USB. And the bootloader saw it and spewed it in with no checksum, error detection. "Oh, it's just a pretty picture.....mmmkay".
    And if finding it in the receiver and doing a dump, comparing it with the one in my file. Finding the culprit.

    Broadcom is using a beast named Bolt in it's stb's. And In the attached link. Wondering what you think. Tomorrow will tell something after I fashion up a serial connection.

    https://github.com/filipnet/dvb-receiver-recovery