Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping
Hi Manu, I was able to resolve my rotor problem by making the following changes in the stb6100, stb0899 and mantis sources: uX replaced by unitX_t.. Since I am running the drivers on 64-bit machine my guess is that is a 64-bit pointer size thing. Unfortunately it is painful to restore my rotor settings after loosing them and I cannot tell you at the moment which change made the difference. Thanks for your help, Simeon - Original Message From: Manu Abraham [EMAIL PROTECTED] To: Simeon Simeonov [EMAIL PROTECTED] Cc: linux-dvb@linuxtv.org Sent: Monday, March 3, 2008 3:52:29 AM Subject: Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping Simeon Simeonov wrote: I am using mythtv and here is the sequence of commands: Without repeat: DiSEqCDevTree: Changing LNB voltage to 13V DiSEqCDevTree: Rotor - Goto Stored Position 2 DiSEqCDevTree: Sending DiSEqC Command: e0 31 6b 2 DiSEqCDevTree: Changing to DiSEqC switch port 1/4 DiSEqCDevTree: Sending DiSEqC Command: e0 10 38 f0 With repeat: DiSEqCDevTree: Changing LNB voltage to 13V DiSEqCDevTree: Rotor - Goto Stored Position 2 DiSEqCDevTree: Sending DiSEqC Command: e0 31 6b 2 DiSEqCDevTree: Changing to DiSEqC switch port 1/4 DiSEqCDevTree: Sending DiSEqC Command: e0 10 38 f0 DiSEqCDevTree: Repeat DiSEqC Command: e1 10 38 f0 In fact, looks really confusing to me. The diseqc commands just go out as it is, through the FIFO. I don't see anything that which changes the commands, but if it was working with another card, it should be working with this card too (i had some doubts, but when you said it worked with some other card, then i don't see the issue in here with the diseqc part. The FiFO either works or not) - Original Message From: Manu Abraham [EMAIL PROTECTED] To: Simeon Simeonov [EMAIL PROTECTED] Cc: linux-dvb@linuxtv.org Sent: Sunday, March 2, 2008 2:38:51 PM Subject: Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping Simeon Simeonov wrote: Hi Manu, I am attaching two gzipped logs. They are supposed to tune to the same frequency using the tip of Mantis tree. The difference between the two are that in the GOOD log no repeat command is used and in the BAD log one repeat for the switch is issued. The initial position of my rotor is about 20 deg east from the target rotor position. Using the tunning without the repeats the rotor goes all the way through and tunes successfully - GOOD log. When repeat command is included in the diseqc sequence the rotor goes about 10 degrees to the west and stops as if it has reached the desired position. The BAD log corresponds to that. When I tried to move to any other rotor stored position I find that that all of the memorized in the rotor positions are shifted. My guess is that for some reason the rotor stops, stores current position as the target one and then re-calculates all of them. But I do not see anything like that in the log file. The only thing I see is that after the third byte in the diseqc repeat command fifo get full and sending the next byte has to wait for one cycle. The same sequences work just fine with my 102g card and the v4l drivers. Can you please try to get the DiSEqC strings that you are sending (from the application) in these 2 cases ? * Without repeat * With repeat Regards, Manu Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping
Simeon Simeonov wrote: Hi Manu, I was able to resolve my rotor problem by making the following changes in the stb6100, stb0899 and mantis sources: uX replaced by unitX_t.. Some points: 1. The change to stb6100 should in no way matter for the rotor. 2. u* is kernel data types and uint*_t are POSIX data types. In fact this shouldn't matter AFAICT, since both are explicit datatypes. The only difference in there that can make a difference would be long I think, greping for long, the only thing that comes to my mind is stb0899_wait_diseqc_fifo_empty(), where you will see the error as stb0899_wait_diseqc_fifo_empty: timed out !! (do you see this error, in your logs ?) But that also shouldn't matter, since there the timeout what's provided there isn't quite large Also this doesn't come into picture, with your u* to uint* change. .. thinking .. Since I am running the drivers on 64-bit machine my guess is that is a 64-bit pointer size thing. Unfortunately it is painful to restore my rotor settings after loosing them and I cannot tell you at the moment which change made the difference. Also, considering that since almost everyone else has this working, maybe it has to be specific to your setup/machine. Regards, Manu Thanks for your help, Simeon - Original Message From: Manu Abraham [EMAIL PROTECTED] To: Simeon Simeonov [EMAIL PROTECTED] Cc: linux-dvb@linuxtv.org Sent: Monday, March 3, 2008 3:52:29 AM Subject: Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping Simeon Simeonov wrote: I am using mythtv and here is the sequence of commands: Without repeat: DiSEqCDevTree: Changing LNB voltage to 13V DiSEqCDevTree: Rotor - Goto Stored Position 2 DiSEqCDevTree: Sending DiSEqC Command: e0 31 6b 2 DiSEqCDevTree: Changing to DiSEqC switch port 1/4 DiSEqCDevTree: Sending DiSEqC Command: e0 10 38 f0 With repeat: DiSEqCDevTree: Changing LNB voltage to 13V DiSEqCDevTree: Rotor - Goto Stored Position 2 DiSEqCDevTree: Sending DiSEqC Command: e0 31 6b 2 DiSEqCDevTree: Changing to DiSEqC switch port 1/4 DiSEqCDevTree: Sending DiSEqC Command: e0 10 38 f0 DiSEqCDevTree: Repeat DiSEqC Command: e1 10 38 f0 In fact, looks really confusing to me. The diseqc commands just go out as it is, through the FIFO. I don't see anything that which changes the commands, but if it was working with another card, it should be working with this card too (i had some doubts, but when you said it worked with some other card, then i don't see the issue in here with the diseqc part. The FiFO either works or not) - Original Message From: Manu Abraham [EMAIL PROTECTED] To: Simeon Simeonov [EMAIL PROTECTED] Cc: linux-dvb@linuxtv.org Sent: Sunday, March 2, 2008 2:38:51 PM Subject: Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping Simeon Simeonov wrote: Hi Manu, I am attaching two gzipped logs. They are supposed to tune to the same frequency using the tip of Mantis tree. The difference between the two are that in the GOOD log no repeat command is used and in the BAD log one repeat for the switch is issued. The initial position of my rotor is about 20 deg east from the target rotor position. Using the tunning without the repeats the rotor goes all the way through and tunes successfully - GOOD log. When repeat command is included in the diseqc sequence the rotor goes about 10 degrees to the west and stops as if it has reached the desired position. The BAD log corresponds to that. When I tried to move to any other rotor stored position I find that that all of the memorized in the rotor positions are shifted. My guess is that for some reason the rotor stops, stores current position as the target one and then re-calculates all of them. But I do not see anything like that in the log file. The only thing I see is that after the third byte in the diseqc repeat command fifo get full and sending the next byte has to wait for one cycle. The same sequences work just fine with my 102g card and the v4l drivers. Can you please try to get the DiSEqC strings that you are sending (from the application) in these 2 cases ? * Without repeat * With repeat Regards, Manu Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping
Simeon Simeonov wrote: I am using mythtv and here is the sequence of commands: Without repeat: DiSEqCDevTree: Changing LNB voltage to 13V DiSEqCDevTree: Rotor - Goto Stored Position 2 DiSEqCDevTree: Sending DiSEqC Command: e0 31 6b 2 DiSEqCDevTree: Changing to DiSEqC switch port 1/4 DiSEqCDevTree: Sending DiSEqC Command: e0 10 38 f0 With repeat: DiSEqCDevTree: Changing LNB voltage to 13V DiSEqCDevTree: Rotor - Goto Stored Position 2 DiSEqCDevTree: Sending DiSEqC Command: e0 31 6b 2 DiSEqCDevTree: Changing to DiSEqC switch port 1/4 DiSEqCDevTree: Sending DiSEqC Command: e0 10 38 f0 DiSEqCDevTree: Repeat DiSEqC Command: e1 10 38 f0 In fact, looks really confusing to me. The diseqc commands just go out as it is, through the FIFO. I don't see anything that which changes the commands, but if it was working with another card, it should be working with this card too (i had some doubts, but when you said it worked with some other card, then i don't see the issue in here with the diseqc part. The FiFO either works or not) - Original Message From: Manu Abraham [EMAIL PROTECTED] To: Simeon Simeonov [EMAIL PROTECTED] Cc: linux-dvb@linuxtv.org Sent: Sunday, March 2, 2008 2:38:51 PM Subject: Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping Simeon Simeonov wrote: Hi Manu, I am attaching two gzipped logs. They are supposed to tune to the same frequency using the tip of Mantis tree. The difference between the two are that in the GOOD log no repeat command is used and in the BAD log one repeat for the switch is issued. The initial position of my rotor is about 20 deg east from the target rotor position. Using the tunning without the repeats the rotor goes all the way through and tunes successfully - GOOD log. When repeat command is included in the diseqc sequence the rotor goes about 10 degrees to the west and stops as if it has reached the desired position. The BAD log corresponds to that. When I tried to move to any other rotor stored position I find that that all of the memorized in the rotor positions are shifted. My guess is that for some reason the rotor stops, stores current position as the target one and then re-calculates all of them. But I do not see anything like that in the log file. The only thing I see is that after the third byte in the diseqc repeat command fifo get full and sending the next byte has to wait for one cycle. The same sequences work just fine with my 102g card and the v4l drivers. Can you please try to get the DiSEqC strings that you are sending (from the application) in these 2 cases ? * Without repeat * With repeat Regards, Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping
Seppo Ingalsuo wrote:
Manu Abraham wrote:
Seppo Ingalsuo wrote:
Simeon Simeonov wrote:
Did you try changing line 250 in mantis_dvb.c to:
if (!lnbp21_attach(mantis-fe, mantis-adapter,
LNBP21_PCL, LNBP21_ISEL)) {
I tried mantis-a9ecd19a37c9. Without the change success in
positioning was about 0% similarly as with multiproto-0448e5a6d8a6.
After this change the success in zapping between different satellite
positions increased to about 40% so it looks now promising and vdr
satellite channels are usable with some patience :^)
You mean the LNBP21 attach line improved things for you by 40% ?
Now I've run original multiproto-8db34ae061ed driver for a day. It
achives about similar success (my guess 40%) in driving my positioner
motor as the edited mantis tree driver. As far as I understand the code
the lnbp21_attach in ttpci/budget-ci.c is different from Simeon's
proposed attach command for mantis. = I hope my comments are not
confusing the development.
Excluding driving/commanding the motor, the current multiproto driver
works well in DVB-S/DVB-S2 (and 2xDVB-T) zapping.
BR,
Seppo
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping
Simeon Simeonov wrote: Hi Manu, I am attaching two gzipped logs. They are supposed to tune to the same frequency using the tip of Mantis tree. The difference between the two are that in the GOOD log no repeat command is used and in the BAD log one repeat for the switch is issued. The initial position of my rotor is about 20 deg east from the target rotor position. Using the tunning without the repeats the rotor goes all the way through and tunes successfully - GOOD log. When repeat command is included in the diseqc sequence the rotor goes about 10 degrees to the west and stops as if it has reached the desired position. The BAD log corresponds to that. When I tried to move to any other rotor stored position I find that that all of the memorized in the rotor positions are shifted. My guess is that for some reason the rotor stops, stores current position as the target one and then re-calculates all of them. But I do not see anything like that in the log file. The only thing I see is that after the third byte in the diseqc repeat command fifo get full and sending the next byte has to wait for one cycle. The same sequences work just fine with my 102g card and the v4l drivers. Can you please try to get the DiSEqC strings that you are sending (from the application) in these 2 cases ? * Without repeat * With repeat Regards, Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping
I am using mythtv and here is the sequence of commands: Without repeat: DiSEqCDevTree: Changing LNB voltage to 13V DiSEqCDevTree: Rotor - Goto Stored Position 2 DiSEqCDevTree: Sending DiSEqC Command: e0 31 6b 2 DiSEqCDevTree: Changing to DiSEqC switch port 1/4 DiSEqCDevTree: Sending DiSEqC Command: e0 10 38 f0 With repeat: DiSEqCDevTree: Changing LNB voltage to 13V DiSEqCDevTree: Rotor - Goto Stored Position 2 DiSEqCDevTree: Sending DiSEqC Command: e0 31 6b 2 DiSEqCDevTree: Changing to DiSEqC switch port 1/4 DiSEqCDevTree: Sending DiSEqC Command: e0 10 38 f0 DiSEqCDevTree: Repeat DiSEqC Command: e1 10 38 f0 - Original Message From: Manu Abraham [EMAIL PROTECTED] To: Simeon Simeonov [EMAIL PROTECTED] Cc: linux-dvb@linuxtv.org Sent: Sunday, March 2, 2008 2:38:51 PM Subject: Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping Simeon Simeonov wrote: Hi Manu, I am attaching two gzipped logs. They are supposed to tune to the same frequency using the tip of Mantis tree. The difference between the two are that in the GOOD log no repeat command is used and in the BAD log one repeat for the switch is issued. The initial position of my rotor is about 20 deg east from the target rotor position. Using the tunning without the repeats the rotor goes all the way through and tunes successfully - GOOD log. When repeat command is included in the diseqc sequence the rotor goes about 10 degrees to the west and stops as if it has reached the desired position. The BAD log corresponds to that. When I tried to move to any other rotor stored position I find that that all of the memorized in the rotor positions are shifted. My guess is that for some reason the rotor stops, stores current position as the target one and then re-calculates all of them. But I do not see anything like that in the log file. The only thing I see is that after the third byte in the diseqc repeat command fifo get full and sending the next byte has to wait for one cycle. The same sequences work just fine with my 102g card and the v4l drivers. Can you please try to get the DiSEqC strings that you are sending (from the application) in these 2 cases ? * Without repeat * With repeat Regards, Manu Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping
Manu Abraham wrote:
Seppo Ingalsuo wrote:
Simeon Simeonov wrote:
Did you try changing line 250 in mantis_dvb.c to:
if (!lnbp21_attach(mantis-fe, mantis-adapter,
LNBP21_PCL, LNBP21_ISEL)) {
I tried mantis-a9ecd19a37c9. Without the change success in
positioning was about 0% similarly as with multiproto-0448e5a6d8a6.
After this change the success in zapping between different satellite
positions increased to about 40% so it looks now promising and vdr
satellite channels are usable with some patience :^)
You mean the LNBP21 attach line improved things for you by 40% ?
Yes, the LNBP21_PCL and LNBP21_ISEL additions did the improvement. By
40% I mean that about 4/10 zappings between channels in different
satellite positions are succesfull. Without this change it was very rare
to get the dish to move, the success rate was 1/10.
If you can really identify what is really unreliable, that itself
will be a help
to fix the issue, in most cases.
Compared to my old DVB-S card this DVB-S2 card is too unreliable for my
family to use it. There is one possible issue with vdr rotor plugin. It
would help in my case if it would set always high LNB voltage before
sending gotox command and keep it for estimated time of movent (based on
about 0.9 seconds/degree speed) before setting the voltage for the tuned
channel. The motor movement with low LNB voltage is very slow especially
in winter and I'm not absolutely sure that the failure is due to
corrupted diseqc gotox command or just too low voltage to get the motor
running. The old DVB-S card was also driving the dish at slow speed with
low LNB voltage but I need to hack the rotor code to rule out this
theory. I need to check also the LNB cable that connects to the PC that
it is still OK.
Which DVB-S2 multiproto driver tree should I follow for latest
development for TT S2-3200 (/Skystar HD)?
For the SAA7146 based cards, use the multiproto tree, for the Mantis
based
cards, use the mantis tree.
OK, thanks. It seems there is now 10min fresh new code to try!
BR,
Seppo
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping
Simeon Simeonov wrote:
Did you try changing line 250 in mantis_dvb.c to:
if (!lnbp21_attach(mantis-fe, mantis-adapter, LNBP21_PCL,
LNBP21_ISEL)) {
I tried mantis-a9ecd19a37c9. Without the change success in positioning
was about 0% similarly as with multiproto-0448e5a6d8a6. After this
change the success in zapping between different satellite positions
increased to about 40% so it looks now promising and vdr satellite
channels are usable with some patience :^)
Is there some kind of soft-diseqc bit timing used with this DVB-S2 card
or driver SW (I didn't yet look at the source) or why is the operation
so unreliable? I had to use command duplication in vdr-rotor plugin with
my old card but with that it was about 100% reliable.
Which DVB-S2 multiproto driver tree should I follow for latest
development for TT S2-3200 (/Skystar HD)?
Cheers,
Seppo
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping
Seppo Ingalsuo wrote:
Simeon Simeonov wrote:
Did you try changing line 250 in mantis_dvb.c to:
if (!lnbp21_attach(mantis-fe, mantis-adapter, LNBP21_PCL,
LNBP21_ISEL)) {
I tried mantis-a9ecd19a37c9. Without the change success in positioning
was about 0% similarly as with multiproto-0448e5a6d8a6. After this
change the success in zapping between different satellite positions
increased to about 40% so it looks now promising and vdr satellite
channels are usable with some patience :^)
You mean the LNBP21 attach line improved things for you by 40% ?
Is there some kind of soft-diseqc bit timing used with this DVB-S2 card
or driver SW (I didn't yet look at the source) or why is the operation
so unreliable? I had to use command duplication in vdr-rotor plugin with
my old card but with that it was about 100% reliable.
If you can really identify what is really unreliable, that itself will
be a help
to fix the issue, in most cases.
Which DVB-S2 multiproto driver tree should I follow for latest
development for TT S2-3200 (/Skystar HD)?
For the SAA7146 based cards, use the multiproto tree, for the Mantis based
cards, use the mantis tree.
Regards,
Manu
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping
Simeon Simeonov wrote: With 72e81184fb9f I get lock 5/10 times of the times and with a9ecd19a37c9 9/10 times. But with 72e81184fb9f I couldn't get neither my rotor nor diseqc switch to work as opposed to the tip where both work with some problems - sending more than 2 diseqc messages messes up my rotor. You are using the Technisat HD2 or the VP-1041 ? if you are using the HD2, changeset 7280 alone adds support for the HD2, so in this case you will need to manually add support for the same. In either of the case, i guess you have some sort of diseqc issue, but then have you tried with the LNBP21 attach change ? Regards, Manu - Original Message From: Manu Abraham [EMAIL PROTECTED] To: Simeon Simeonov [EMAIL PROTECTED] Cc: linux-dvb@linuxtv.org Sent: Thursday, February 28, 2008 1:29:55 AM Subject: Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping Simeon Simeonov wrote: I don't know if is the same but with the latest mantis tree I get 100% success. Reverting to changeset mantis-100d4b009238 (which I think corresponds to multiproto 7200) I do NOT any locks on the same transponder. For the mantis tree, please test this changeset: 727572e81184fb9f as head Please test how that looks in comparison to tip changeset 7282a9ecd19a37c9 Regards, Manu Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping
I am using VP-1041 with the lnb21_attach changes to the ISEL and PCL bit settings. At the moemnt I have no clue why I am having this diseqc issue. I also checked the logs and I see from time to time diseqc_fifo_full messages but there is no correlation with the problem. For example I have not seen these messages for the last two days but sending more than 2 diseqc messages re-programs my rotor. - Original Message From: Manu Abraham [EMAIL PROTECTED] To: Simeon Simeonov [EMAIL PROTECTED] Cc: linux-dvb@linuxtv.org Sent: Friday, February 29, 2008 3:20:39 PM Subject: Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping Simeon Simeonov wrote: With 72e81184fb9f I get lock 5/10 times of the times and with a9ecd19a37c9 9/10 times. But with 72e81184fb9f I couldn't get neither my rotor nor diseqc switch to work as opposed to the tip where both work with some problems - sending more than 2 diseqc messages messes up my rotor. You are using the Technisat HD2 or the VP-1041 ? if you are using the HD2, changeset 7280 alone adds support for the HD2, so in this case you will need to manually add support for the same. In either of the case, i guess you have some sort of diseqc issue, but then have you tried with the LNBP21 attach change ? Regards, Manu - Original Message From: Manu Abraham [EMAIL PROTECTED] To: Simeon Simeonov [EMAIL PROTECTED] Cc: linux-dvb@linuxtv.org Sent: Thursday, February 28, 2008 1:29:55 AM Subject: Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping Simeon Simeonov wrote: I don't know if is the same but with the latest mantis tree I get 100% success. Reverting to changeset mantis-100d4b009238 (which I think corresponds to multiproto 7200) I do NOT any locks on the same transponder. For the mantis tree, please test this changeset: 727572e81184fb9f as head Please test how that looks in comparison to tip changeset 7282a9ecd19a37c9 Regards, Manu Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping
Simeon Simeonov wrote: I am using VP-1041 with the lnb21_attach changes to the ISEL and PCL bit settings. At the moemnt I have no clue why I am having this diseqc issue. I also checked the logs and I see from time to time diseqc_fifo_full messages but there is no correlation with the problem. Did you mean the timed out !! message from stb0899_wait_diseqc_fifo_empty() ? (stb0899_drv.c, line #686, Trying to understand the problem that you are facing) Regards, Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping
Yes, ocasionally I see the message from stb0899_wait_diseqc_fifo_empty() but trying to increase the time in the call did not help. So I am not sure if my problem is related to that message. - Original Message From: Manu Abraham [EMAIL PROTECTED] To: Simeon Simeonov [EMAIL PROTECTED] Cc: linux-dvb@linuxtv.org Sent: Friday, February 29, 2008 3:40:05 PM Subject: Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping Simeon Simeonov wrote: I am using VP-1041 with the lnb21_attach changes to the ISEL and PCL bit settings. At the moemnt I have no clue why I am having this diseqc issue. I also checked the logs and I see from time to time diseqc_fifo_full messages but there is no correlation with the problem. Did you mean the timed out !! message from stb0899_wait_diseqc_fifo_empty() ? (stb0899_drv.c, line #686, Trying to understand the problem that you are facing) Regards, Manu Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping
Simeon Simeonov wrote: I don't know if is the same but with the latest mantis tree I get 100% success. Reverting to changeset mantis-100d4b009238 (which I think corresponds to multiproto 7200) I do NOT any locks on the same transponder. For the mantis tree, please test this changeset: 7275 72e81184fb9f as head Please test how that looks in comparison to tip changeset 7282 a9ecd19a37c9 Regards, Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping
Oliver Bardenheier (obardenh) wrote: Seppo, You should use the group-mailer linux-dvb@linuxtv.org Sorry Olivier, I didn't mean to send you personal email! I still have the same problem and I'm not familiar with various DVB driver sources discussed here (hg-tree, mantis). As I suppose I have the same issue as discussed in this thread, how do I retrieve an older version of the driver for TT S2-3200 that would work? BR, Seppo regards Oliver -Original Message- From: Seppo Ingalsuo [mailto:[EMAIL PROTECTED] Sent: Donnerstag, 28. Februar 2008 07:08 To: Oliver Bardenheier (obardenh) Subject: Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping Oliver Bardenheier (obardenh) wrote: I can confirm that current hg-tree breaks SkyStarHD. Mostly unusable, many transponders not working. I changed back to 45eec532cefa and everything is working fine. I'm using multiproto-74c6c2ee613b grabbed yesterday and I was able to see only BBC World from Astra 19.2E. Other channels I tried to zap to didn't work. Also there seemed to be problems in driving reliably diseqc positioner (that the old TT budget-s handled fine). It was my first experience with brand new TT S2-3200 and vdr 1.5.16 with Reinhard's H.264 patch set. BR, Seppo ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping
No problem, :-) You just check out the tree via the webpage: http://jusst.de/hg/multiproto then click on the needed changeset http://jusst.de/hg/multiproto/rev/0448e5a6d8a6 and download the bzip with the complete changeset http://jusst.de/hg/multiproto/archive/0448e5a6d8a6.tar.bz2 The rest is routine :-) Oliver -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Seppo Ingalsuo Sent: Donnerstag, 28. Februar 2008 16:53 To: linux-dvb@linuxtv.org Subject: Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping Oliver Bardenheier (obardenh) wrote: Seppo, You should use the group-mailer linux-dvb@linuxtv.org Sorry Olivier, I didn't mean to send you personal email! I still have the same problem and I'm not familiar with various DVB driver sources discussed here (hg-tree, mantis). As I suppose I have the same issue as discussed in this thread, how do I retrieve an older version of the driver for TT S2-3200 that would work? BR, Seppo regards Oliver -Original Message- From: Seppo Ingalsuo [mailto:[EMAIL PROTECTED] Sent: Donnerstag, 28. Februar 2008 07:08 To: Oliver Bardenheier (obardenh) Subject: Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping Oliver Bardenheier (obardenh) wrote: I can confirm that current hg-tree breaks SkyStarHD. Mostly unusable, many transponders not working. I changed back to 45eec532cefa and everything is working fine. I'm using multiproto-74c6c2ee613b grabbed yesterday and I was able to see only BBC World from Astra 19.2E. Other channels I tried to zap to didn't work. Also there seemed to be problems in driving reliably diseqc positioner (that the old TT budget-s handled fine). It was my first experience with brand new TT S2-3200 and vdr 1.5.16 with Reinhard's H.264 patch set. BR, Seppo ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping
Hello, I think this page is very useful, because it explains the procedure quite well (also tells you about modified scan and zap): http://www.linuxtv.org/wiki/index.php/Multiproto Regards Oliver Bardenheier (obardenh) wrote: No problem, :-) You just check out the tree via the webpage: http://jusst.de/hg/multiproto then click on the needed changeset http://jusst.de/hg/multiproto/rev/0448e5a6d8a6 and download the bzip with the complete changeset http://jusst.de/hg/multiproto/archive/0448e5a6d8a6.tar.bz2 The rest is routine :-) Oliver -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Seppo Ingalsuo Sent: Donnerstag, 28. Februar 2008 16:53 To: linux-dvb@linuxtv.org Subject: Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping Oliver Bardenheier (obardenh) wrote: Seppo, You should use the group-mailer linux-dvb@linuxtv.org Sorry Olivier, I didn't mean to send you personal email! I still have the same problem and I'm not familiar with various DVB driver sources discussed here (hg-tree, mantis). As I suppose I have the same issue as discussed in this thread, how do I retrieve an older version of the driver for TT S2-3200 that would work? BR, Seppo regards Oliver -Original Message- From: Seppo Ingalsuo [mailto:[EMAIL PROTECTED] Sent: Donnerstag, 28. Februar 2008 07:08 To: Oliver Bardenheier (obardenh) Subject: Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping Oliver Bardenheier (obardenh) wrote: I can confirm that current hg-tree breaks SkyStarHD. Mostly unusable, many transponders not working. I changed back to 45eec532cefa and everything is working fine. I'm using multiproto-74c6c2ee613b grabbed yesterday and I was able to see only BBC World from Astra 19.2E. Other channels I tried to zap to didn't work. Also there seemed to be problems in driving reliably diseqc positioner (that the old TT budget-s handled fine). It was my first experience with brand new TT S2-3200 and vdr 1.5.16 with Reinhard's H.264 patch set. BR, Seppo ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping
Oliver Bardenheier (obardenh) wrote: No problem, :-) You just check out the tree via the webpage: http://jusst.de/hg/multiproto then click on the needed changeset http://jusst.de/hg/multiproto/rev/0448e5a6d8a6 and download the bzip with the complete changeset http://jusst.de/hg/multiproto/archive/0448e5a6d8a6.tar.bz2 The rest is routine :-) Thanks! It works now (almost), zapping in Astra 19.2E works now very well. ... But diseqc positioner commands (GotoX from vdr rotor plugin) seem to not get through with 100% reliability. Changing to use diseqc.conf seemed to help a bit but I haven't been able to convince the motor to turn to 28.2E at all. BR, Seppo ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping
Vangelis Nonas wrote: I think this page is very useful, because it explains the procedure quite well (also tells you about modified scan and zap): http://www.linuxtv.org/wiki/index.php/Multiproto Thanks for this as well! Modified scan zap would have been next in my question list :^) BR, Seppo ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping
I have for vp-1041: 72e81184fb9f work with SR=22000, hi SR work with frequency offset ~+6 MHz for SR 44948 a9ecd19a37c9 work with SR 44948 ok but both have trouble, from time to time long wait for lock, from time to time faster lock... I can't find dependence... I use vdr-1.5.14+h264 patch, test dvb-s only. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping
... But diseqc positioner commands (GotoX from vdr rotor plugin) seem to
not get through with 100% reliability. Changing to use diseqc.conf
seemed to help a bit but I haven't been able to convince the motor to
turn to 28.2E at all.
Did you try changing line 250 in mantis_dvb.c to:
if (!lnbp21_attach(mantis-fe, mantis-adapter, LNBP21_PCL,
LNBP21_ISEL)) {
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping
With 72e81184fb9f I get lock 5/10 times of the times and with a9ecd19a37c9 9/10 times. But with 72e81184fb9f I couldn't get neither my rotor nor diseqc switch to work as opposed to the tip where both work with some problems - sending more than 2 diseqc messages messes up my rotor. - Original Message From: Manu Abraham [EMAIL PROTECTED] To: Simeon Simeonov [EMAIL PROTECTED] Cc: linux-dvb@linuxtv.org Sent: Thursday, February 28, 2008 1:29:55 AM Subject: Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping Simeon Simeonov wrote: I don't know if is the same but with the latest mantis tree I get 100% success. Reverting to changeset mantis-100d4b009238 (which I think corresponds to multiproto 7200) I do NOT any locks on the same transponder. For the mantis tree, please test this changeset: 727572e81184fb9f as head Please test how that looks in comparison to tip changeset 7282a9ecd19a37c9 Regards, Manu Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping
I can confirm that current hg-tree breaks SkyStarHD. Mostly unusable, many transponders not working. I changed back to 45eec532cefa and everything is working fine. regards Oliver -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Manu Abraham Sent: Dienstag, 26. Februar 2008 22:45 To: linux-dvb@linuxtv.org Subject: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping Vangelis Nonas wrote: Hello, Here is the output of hg log|head -n 5 for two different directories (multiproto and multiproto_7200) for multiproto: changeset: 7205:9bdb997e38b5 tag: tip user:Manu Abraham [EMAIL PROTECTED] date:Sun Feb 24 02:10:56 2008 +0400 summary: We can now reduce the debug levels, just need to look at errors only. for multiproto_7200: changeset: 7200:45eec532cefa tag: tip parent: 7095:a577a5dbc93d parent: 7199:0448e5a6d8a6 user:Manu Abraham [EMAIL PROTECTED] So I guess I was referring to 7200 and not to 7201. I am very positive about the results because I have tested it many times. It is just that it is 7200 instead of 7201. So as a concluesion, 7200 behaves better than 7205. My corrected little table follows below just for clarification. Ok, fine this is very much possible. Can other STB0899 users (all of them) verify this result, such that i can revert back the changes ? Changeset Verbose channels 7200 12152 7200 22105 7200 52081 7205 11760 7205 21608 7205 51578 I apologise for the confusion, I may have caused. No worries, don't apologise, this is all a part of the testing phase. Thanks, Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping
Oliver Bardenheier (obardenh) wrote: I can confirm that current hg-tree breaks SkyStarHD. Mostly unusable, many transponders not working. I changed back to 45eec532cefa and everything is working fine. Thanks for the verification. Regards, Manu regards Oliver -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Manu Abraham Sent: Dienstag, 26. Februar 2008 22:45 To: linux-dvb@linuxtv.org Subject: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping Vangelis Nonas wrote: Hello, Here is the output of hg log|head -n 5 for two different directories (multiproto and multiproto_7200) for multiproto: changeset: 7205:9bdb997e38b5 tag: tip user:Manu Abraham [EMAIL PROTECTED] date:Sun Feb 24 02:10:56 2008 +0400 summary: We can now reduce the debug levels, just need to look at errors only. for multiproto_7200: changeset: 7200:45eec532cefa tag: tip parent: 7095:a577a5dbc93d parent: 7199:0448e5a6d8a6 user:Manu Abraham [EMAIL PROTECTED] So I guess I was referring to 7200 and not to 7201. I am very positive about the results because I have tested it many times. It is just that it is 7200 instead of 7201. So as a concluesion, 7200 behaves better than 7205. My corrected little table follows below just for clarification. Ok, fine this is very much possible. Can other STB0899 users (all of them) verify this result, such that i can revert back the changes ? Changeset Verbose channels 7200 12152 7200 22105 7200 52081 7205 11760 7205 21608 7205 51578 I apologise for the confusion, I may have caused. No worries, don't apologise, this is all a part of the testing phase. Thanks, Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping
I don't know if is the same but with the latest mantis tree I get 100% success. Reverting to changeset mantis-100d4b009238 (which I think corresponds to multiproto 7200) I do NOT any locks on the same transponder. - Original Message From: Manu Abraham [EMAIL PROTECTED] To: linux-dvb@linuxtv.org Sent: Tuesday, February 26, 2008 1:44:37 PM Subject: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping Vangelis Nonas wrote: Hello, Here is the output of hg log|head -n 5 for two different directories (multiproto and multiproto_7200) for multiproto: changeset: 7205:9bdb997e38b5 tag: tip user:Manu Abraham [EMAIL PROTECTED] date:Sun Feb 24 02:10:56 2008 +0400 summary: We can now reduce the debug levels, just need to look at errors only. for multiproto_7200: changeset: 7200:45eec532cefa tag: tip parent: 7095:a577a5dbc93d parent: 7199:0448e5a6d8a6 user:Manu Abraham [EMAIL PROTECTED] So I guess I was referring to 7200 and not to 7201. I am very positive about the results because I have tested it many times. It is just that it is 7200 instead of 7201. So as a concluesion, 7200 behaves better than 7205. My corrected little table follows below just for clarification. Ok, fine this is very much possible. Can other STB0899 users (all of them) verify this result, such that i can revert back the changes ? Changeset Verbose channels 7200 12152 7200 22105 7200 52081 7205 11760 7205 21608 7205 51578 I apologise for the confusion, I may have caused. No worries, don't apologise, this is all a part of the testing phase. Thanks, Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping
Seppo, You should use the group-mailer linux-dvb@linuxtv.org regards Oliver -Original Message- From: Seppo Ingalsuo [mailto:[EMAIL PROTECTED] Sent: Donnerstag, 28. Februar 2008 07:08 To: Oliver Bardenheier (obardenh) Subject: Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping Oliver Bardenheier (obardenh) wrote: I can confirm that current hg-tree breaks SkyStarHD. Mostly unusable, many transponders not working. I changed back to 45eec532cefa and everything is working fine. I'm using multiproto-74c6c2ee613b grabbed yesterday and I was able to see only BBC World from Astra 19.2E. Other channels I tried to zap to didn't work. Also there seemed to be problems in driving reliably diseqc positioner (that the old TT budget-s handled fine). It was my first experience with brand new TT S2-3200 and vdr 1.5.16 with Reinhard's H.264 patch set. BR, Seppo ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
