Reply to thread

Message: <blockquote data-quote="Kotik" data-source="post: 1198556" data-attributes="member: 89825">Got news from TBS,This is what he says:"Hi KotikThanks for your detail feedback ,the problem still the DVB soft .As our card just a device we just accpet command why DVBDream works this is because when you use goto Diseqc command it do not send lock message to our driver it wait your dish finished the move then send command to lock .for other soft once send the diseqc to move the dish then send command to lock our card will lock it immediately .ThanksKind Regardssteven"As you can see as per TBS it is a DVB application issue and I cannot blame them, lets be honest, the most compatible way for any DVB card would be to 1st stop the channel, then send the GoToX command, then calculate a delay based on satellite position distance and only after this delay issue a lock command to the tuner. This would solve the issues I am having for both SkyStarHD2 and TBS 6902. So I got two options left:1. Add a static delay after the GoToX command.2. Implement a hardware relay switch that would turn off the LNB during motor movement.I like the second solution more cause keep in mind that channel switching will be much faster than with the first solution. But it requires from me to disassemble my motor, something that I have done in the past with an older motor that I had but it is a difficult task and it also requires to fine tune the dish again after I am done with the modification. I am also afraid regarding the LNB On/Off power switching, it is something untested and as so has its own risks. But it is by far the best solution regarding TBS 6902 (this solution would not work for SkyStart HD2 since SkyStar HD2 would still time out while trying to Lock On).The second solution is universal, but in its basic and static form of xxx amounts of delay between motor movement command and tune lock commands it will require a high amount of delay if u want to be able to switch between satellites that are far apart. In any case I would love to try the 2nd solution since this will save me from spending time at my roof, it is getting cold here <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile    :)" loading="lazy" data-shortname=":)" />.[USER=82144]@mm1352000[/USER] I got a couple of questions:1. Do we send a STOP tune command to the tuner before we initiate motor movement? I am asking cause if we don't send one and delay the next tune command then as u can imagine we will run into the same issue but with different frequencies this time, the result will be the tuner trying to re-lock to the previous channel while the dish is moving and we still didn't instruct new tuning details.2. How would u suggest implementing dynamic delays based on position distances? What I mean here is that if I always Store 19.2E to position 1 and 13.0E to position 2 and I know that I need 2 seconds to move from 1 to 2 and vice versa where in the code would I have to input these delays? Is it at the same code that u pointed me to?Thanx in advance.</blockquote>

Verification