bda driver testing

This is the place where beta releases of the application or modules are made available. Only download if you're willing to cooperate in resolving any problems

bda driver testing

Postby SmartDVB » Sun Oct 03, 2010 12:20 am

Hello,

I need some testers for a new bda driver which i'm currently developing. Especially users with cards which previously would not work correctly with the current bda driver. Just drop me a note and i'll send you the driver. It's beta so feedback is appreciated (you can email me at jackjavo hotmail).
jack
SmartDVB
Site Admin
 
Posts: 616
Joined: Sun Feb 01, 2009 5:18 am

Re: bda driver testing

Postby mdpa » Wed Feb 09, 2011 12:30 am

22:56:24 7516 - SetTuner() 11439000, H, 8250000 LOF:9750000 22Khz:0
22:56:24 7516 - TWINHAN_SetLNB()
22:56:24 7516 - GetTickCount before BDASetTuner 3851875
22:56:24 7531 - GetTickCount before tune_request 3851890
22:56:24 7531 - tune_request 1 3851890
22:56:24 7531 - tune_request 2 3851890
22:56:24 7531 - Modulation used 20
22:56:24 7531 - tune_request 3 3851890
22:56:24 7531 - GetTickCount before put_tunerequest 3851890
22:56:25 7891 - GetTickCount after put_tunerequest 3852250
22:56:25 7906 - tune_request 4 3852265
22:56:25 7906 - GetTickCount after tune_request 3852265
22:56:25 7906 - BDASetTuner Using locktime 5000
22:56:25 7906 - signalocked true breaking
22:56:25 7906 - actual time 0
22:56:25 7906 - Slept 0
22:56:25 7906 - Status: Locked
22:56:25 7906 - GetTickCount after BDASetTuner 3852265
22:57:09 51875 - In SendDiseqc
22:57:09 51875 - SendDiseqc() E0 31 6B 12 Len:4
22:57:09 51875 - twinhan_send_diseqc(<E0 31 6B 12 >, 4)
22:59:11 174531 -
22:59:11 174547 - SetTuner() 12688000, H, 30000000 LOF:10600000 22Khz:1
22:59:11 174547 - TWINHAN_SetLNB()
22:59:11 174547 - GetTickCount before BDASetTuner 4018906
22:59:11 174547 - GetTickCount before tune_request 4018906
22:59:11 174547 - tune_request 1 4018906
22:59:11 174547 - tune_request 2 4018906
22:59:11 174547 - Modulation used 20
22:59:11 174547 - tune_request 3 4018906
22:59:11 174547 - GetTickCount before put_tunerequest 4018906
22:59:12 174984 - GetTickCount after put_tunerequest 4019343
22:59:12 174984 - tune_request 4 4019343
22:59:12 174984 - GetTickCount after tune_request 4019343
22:59:12 174984 - BDASetTuner Using locktime 2000
22:59:12 174984 - signalocked true breaking
22:59:12 174984 - actual time 0
22:59:12 174984 - Slept 0
22:59:12 174984 - Status: Locked
22:59:12 174984 - GetTickCount after BDASetTuner 4019343
22:59:31 193953 -
22:59:31 193953 - SetTuner() 12647000, H, 30000000 LOF:10600000 22Khz:1
22:59:31 193953 - TWINHAN_SetLNB()
22:59:31 193953 - GetTickCount before BDASetTuner 4038312
22:59:31 193953 - GetTickCount before tune_request 4038312
22:59:31 193953 - tune_request 1 4038312
22:59:31 193953 - tune_request 2 4038312
22:59:31 193953 - Modulation used 20
22:59:31 193953 - tune_request 3 4038312
22:59:31 193953 - GetTickCount before put_tunerequest 4038312
22:59:31 194391 - GetTickCount after put_tunerequest 4038750
22:59:31 194391 - tune_request 4 4038750
22:59:31 194406 - GetTickCount after tune_request 4038765
22:59:31 194406 - BDASetTuner Using locktime 5000
22:59:31 194406 - signalocked true breaking
22:59:31 194406 - actual time 0
22:59:31 194406 - Slept 0
22:59:31 194406 - Status: Locked
22:59:31 194406 - GetTickCount after BDASetTuner 4038765
22:59:44 207625 -
22:59:44 207625 - SetTuner() 11439000, H, 8250000 LOF:9750000 22Khz:0
22:59:44 207625 - TWINHAN_SetLNB()
22:59:44 207625 - GetTickCount before BDASetTuner 4051984
22:59:44 207641 - GetTickCount before tune_request 4052000
22:59:44 207641 - tune_request 1 4052000
22:59:44 207641 - tune_request 2 4052000
22:59:44 207641 - Modulation used 20
22:59:44 207641 - tune_request 3 4052000
22:59:44 207641 - GetTickCount before put_tunerequest 4052000
22:59:46 209391 - GetTickCount after put_tunerequest 4053750
22:59:46 209391 - tune_request 4 4053750
22:59:46 209391 - GetTickCount after tune_request 4053750
22:59:46 209391 - BDASetTuner Using locktime 5000
22:59:46 209391 - signalocked true breaking
22:59:46 209391 - actual time 0
22:59:46 209391 - Slept 0
22:59:46 209391 - Status: Locked
22:59:46 209391 - GetTickCount after BDASetTuner 4053750

positioner stays on 36°E Eutelsat W4/W7
1)tune on channel 9 11439000, H, 8250000 ----> OK
2) channel scan on 39°E Hellas Sat 2 12688000, H, 30000000 ----> OK (motor moves)
3) tune on Kanal 3 of the same sat 12647000, H, 30000000 ----> OK
4) tune on 36°E Eutelsat W4/W7 channel 9 again ----> NOK (22Khz:0 ???)

MDPA
(SMARTDVB is the best free software at this moment)
mdpa
 
Posts: 7
Joined: Mon Feb 07, 2011 6:57 pm

Re: bda driver testing

Postby SmartDVB » Thu Feb 10, 2011 3:50 pm

Hi. Thanks for reporthing this. I think this is an oversight from my part (which should not happen if you have send diseqc on each channel change turned on) where i forgot to let sat changes from the scanner tripple down to the channel tuning part, should be fixed in next release. Btw you should not use this beta version of bda.dev anymore as the latest 0.2.1 betas also include fixes in bda.dev..
SmartDVB
Site Admin
 
Posts: 616
Joined: Sun Feb 01, 2009 5:18 am

Re: bda driver testing

Postby mdpa » Thu Feb 10, 2011 11:06 pm

Sorry, I thought that this bda.dev (148KB) was the latest). With bda.dev (159KB) that came with the install, this problem dit not occur
mdpa
 
Posts: 7
Joined: Mon Feb 07, 2011 6:57 pm

Re: bda driver testing

Postby mdpa » Fri Feb 11, 2011 12:05 am

Actually this problem still occurs Sometimes. The motor does the move, but there is no level indication. Simply scan the current transponder resolves the situation. If I don't do thiss, I have to close the program with this details:

Problem signature:
Problem Event Name: APPCRASH
Application Name: SmartDVB.exe
Application Version: 0.2.1.0
Application Timestamp: 4d396515
Fault Module Name: StackHash_4387
Fault Module Version: 6.1.7600.16385
Fault Module Timestamp: 4a5bdadb
Exception Code: c0000374
Exception Offset: 000c283b
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 2067
Additional Information 1: 4387
Additional Information 2: 43878b20f6500b1126965c92d11364e4
Additional Information 3: c0cb
Additional Information 4: c0cb5b2db90c6295d61e887ee3c68b6f
mdpa
 
Posts: 7
Joined: Mon Feb 07, 2011 6:57 pm

Re: bda driver testing

Postby mdpa » Sun Feb 27, 2011 1:01 pm

This problem only exists in win 7 32-bit.
In win XP no problem in switching sats
mdpa
 
Posts: 7
Joined: Mon Feb 07, 2011 6:57 pm

Re: bda driver testing

Postby mdpa » Tue Mar 01, 2011 10:36 pm

And this problem seems not to happen anymore after the following setting:
tools->settings->Diseqc:mark
Check for signal existence on positioner move and retune if no signal (time interval: 3000)
mdpa
 
Posts: 7
Joined: Mon Feb 07, 2011 6:57 pm

Re: bda driver testing

Postby SmartDVB » Wed Mar 02, 2011 2:09 pm

hmm how odd, maybe it's some kind of driver issue. I will try to review the code in any case thanks...
SmartDVB
Site Admin
 
Posts: 616
Joined: Sun Feb 01, 2009 5:18 am


Return to Beta Testing

Who is online

Users browsing this forum: No registered users and 1 guest

cron