Hi

I have checked the forum on ProgDVB SS1 CI device error and advice from SiLencer was to select it on load - well even in the latest 5.12.3 its not specifically in the ProgDVB Select card list - IS IT!

Why not? Surely using the correct words rather than call it 'something else' - who cares - technotrend hardware mpeg whatever - CALL IT TECHNISAT SS1 CI"

This is just lazy haphazard programming and a damn nuisance to users!!

Selecting of any other than BDA device on install time was only available with the former installer.
Prog now changed to a new installer, that surely has some other benefits, but seems to not allow enough selection options there.
As ProgDVB can handle more than one device these days, this should not really matter.
You can select the SS1 (or any other device), after ProgDVB is started.
The CI is a standard component of the SS1 / premium design, does not require anything special to install, same as e.g. the HW IR remote for those.
That's all part of the SS1 device and firmware.

SkyStar 1 is a trademark and the original name of the first model of this card, originally branded Technisat. And all versions, that and all the following, were made by Technotrend, but sold under a variety of brands and names, including their own.
That's why we are collecting all that revisions under a common name, SS1

However, you're using a free product.
So there's no lazy or damn or anything similar related with it.
PLEASE let's all keep cool...

Hi,
Ok fair enough! A very prompt reply from moderators too

I must admit to being quite surprised that the version of ProgDVB I was running 4.56.2 had a problem with my SS1 via settings/start SS1 hard mode device. As my SS1 is running perfect on its own software version which still now is v2.4.1.0
Latest SS1 software is v2.421 I am not sure what is new here or if this is necessary for good operation of ProgDVB?? Please explain if you know??

I think I am very competent with my PC, so since you guy's as moderators say you have no problem with running SS1 how come the public have problems - with settings start device SS1??

It is quite easy to see if the SS data programme is running in task manager and shut it down, before load or start Prog DVB. So I don't think this is general ProgDVB/SS1 users problem here!

As (also) regards my post on autostarts - is there anything else running that you know of whch could be causing a problem with SS1 starting in ProgDVB using settings/start device window?? In this regard how is it possible for user to capture and attach any logs to their posts that would help the moderators with problem solving - I do not see attachment tab here??

Also - as you say - ProgDVB is a free programme therefore what is your suggestion of the ultimate ProgDVB version to run with SS1??

Maybe there is some good tricks by using particular version of SS1 driver with particular version of ProgDVB??

I will now load latest ProgDVB and see if it can start SS1 - when finished I will reply with result, eh?

Please answer re most suitable soft versions/driver etc as per your experience with SS1 etc as requested here.

cheers

Hi,

Sorry to report this is another disaster!

On restart computer and load newly installed ProgDVB 5.12.4 =

1. "ProgDVB loading unhandled exception - object reference not set to instance of an object" Why is this??

2. Then "ProgDVB Engine - device not started" maybe ok as device has not been selected yet?

3. Then "ProgDVBNet - ProgDVB has encountered a problem and needs to close - we are very sorry for inconvenience"
SEND ERROR TO MICROSOFT - YES I DID!

OK moderators - why is this? Which logs do you want and how can I find and attach them to forum post; please?

cheers Ken

Hi,
OK; maybe some progress - I have dumped the 5.12.4 and now start to reload the 4.56.2 - as this is what at least would run before, but not start SS1 card.

Now I see on load that the device box of ProgDVB4.56.2 says SS1 hard mode needs Technotrend x2 driver - this is good info!! I did not see before - but maybe as in interim I have reloaded Dot Net 2x.

However, I am happy with my Skystar v2.410 driver. All the transponders have been scanned and I would prefer to keep it!

So what do I do now??

OK some revelation here - what I am trying to do; IN FACT; is use my Skystar 1 to scan the channels into ProgDVB so that I can use this cannel list and change the device to my Telemann sm200dpa. I have had the Telemann working in 4.56.2 but for some strange reason, using the Skystar to scan, it would only pickup 2 channels on Optus D1. ie. TV1 and TV2 (+sky encrypted). I need the channels for TV3, Stratos, ParliamentTV, C4, TV6 Sport, and Sport extra. So at present I only have 2 channels out of possible 9 FTA - which can work with telemann. Any advice please - and/or link to other forum posts of use here to solve either the limited search of Skystar in ProgDVB 4.56.2 using SS1, or how to get NZ channel list complete for ProgDVB to use Telemann sm200dpa??

I see ProgDVB offers strong promotion of Rust's module on the Prog website - also I have had some help from Rust directly. So my problem to date has been that I need a channel list for ProgDVB for the Telemann card?

Also from your site links I have DL the Fastfinder and Skygrabber - these I tried to load but allways errors and cannot start due to SS1 cannot start with ProgDVB and therefore as these programs use prog engine they cannot start also?

So is all this because of no Technotrend 2 x driver loaded??
Please explain all??? Maybe I have to load the Technotrend diver - but I like the SS1 driver now???? So here is a big worry eh??

I would like also to be able to manually load the channels to ProgDVB but using the New folder and add channels all looks very complicated - I have tried to add TV3 - and I viwed the ProgDVB channel pages for TV1 and TV2 which were scanned by SS1 but so far I fail to get TV3 from my setting of this new channel.

I have also the channel lists in SS1 (program files/Technisat Skystar 1 CI/List ) but this appears to be in format of .lst which I don't know how to convert, if possible, to .dvb format for ProDVB. Also I have mytheatre channel list scanned with HVR4000 but also this is in format of Channels.mdb - is any of this of any use, or is there a better way to get up to date channel list for ProgDVB for NZ which will work with ProgDVB device then set ProgDVB to Telemann "Transport Stream"??

cheers Ken

First of all, no idea on the Telemann, sorry.

Regarding SS1 drivers, the version numbers I am using are those of the TT software and driver packets.
TT 2.17, 2.19 and 2.19h are proven to work with ALL ProgDVB versions I have installed, even some vintage 3.x.

Starting trouble may result from two main causes, either badly behaving switches (mainly some DiSEqC and relevant settings), or a worn out capacitor on the SS1.
That one would be the only classical one, almost in the middle of the PCB, 330 µF 25V or 35V. It's part of the voltage converter, and it must be a low ESR type.
330µF often is NOT enough, 25 volts surely aren't.

Indeed, some other software may have less trouble, to start the card even with a weak capacitor, due to either different firmware or possibly timing.
Startup timings must have been changed recently, AFAIK.
The special firmware version is necessary, as it has some non public 3rd party patch.

On older ProgDVB versions, you can reload the frmware from device list, by starting the device once more, similar to many other older DVB applications for the SS1. In most cases, this helps at once.
Also possible on engine one or older versions, to play back a short sequence, then retrigger a station.

But even then, in most cases the real cause would be the capacitor.
And there is another aspect, not ProgDVB related, driver behaviour on all versions I know:
The voltage converter first time starts with low voltage state (for vertical), but will be reset to high (horizontal) after switching off the tuner.
This gives a techznical difference between first (after boot) and any other device start.
Also happens with any other DVB software I have tested recently.

Did not yet find the time, to test ProgDVB 5.12.4 or 4.88.4 here. DVB machine and device are busy for other important tasks ATM...