Digital lock help

[DTVismybitch]

I just installed a digital lock on a Dish 2800 receiver. The receiver worked fine before i did it, it woorkd fine after i did it and it still works fine, but only when I replace teh jumper on the digital lock board. If the jumper is in place and the #1 and 2 switch are both set to "off" the receiver gets channel 101 fine. As soon as I take jumper off it and then move switch 2 to the "on" position, which is what I am supposed to do for a HYNIX chip, it works for 5 seconds ad then I get the "tere has been a serious problem detected with your receiver". The receiver has not been ecm'ed, I have a location ID that IS NOT 0000001, or whatever it is. I have a remote address of "1" though, I am not sure if that is bad or good. I installed digital lock version 3.5 that i got from mydigitalglobe. Can anyone help me out please, it makes no sense.

[Chapster99]

Ummmm....you're NOT supposed to play with those switches. For HYNIX, switch 1 is set to OFF, switch 2 is set to ON. They stay that way always. To unlock TSOP, simply put the jumper back on. I hope your IRD is not toast....

The following is from a 'How_to' lock install guide...

"Prior to soldering the Digital Lock 3.5 to your IRD, you must take the time to set it up properly for your receiver model and TSOP. If you do not, you may damage your receiver !"

[DTVismybitch]

I have that exact walk through, I have attached the lock as shown in it. The walkthrough states to "never install the losk with both switches in the ON position" because that could kill the receiver. My receiver is not toast at all. It powers up fine and it works with the cards fine too, however as soon as i take the jumper off it gies me the "There ia serious probl wit your receiver" after about 2 minutes, someimes 20 seconds. i unplug IRD for 20 second and then it does it again. I have hooked my j-tag up to it and ran the TSOP write test while i is locked to make sure that it is locked and won't accept any writing, it passed with flying colours. I tried it 5 times, and all 5 times it gave me a nag at a certain address saying it couldn't write to it. So it is installed correctly. But what is wrong with this "there is a serious problem with your receiver" NAG, it is only supposed to show up wen charlie ECM's th receiver and that is not the case. Any ideas.

[Chapster99]

What are you using as a 'card'? Plastic, Atmega, AVR, Emu?

[DTVismybitch]

plastic card, ROM 3 and ROM 10. As soon as the jumper is removed or the button #2 is pushed to "on" position it gives that stupid nag as if I was using an Atmega card. Pretty annoying. I let the system run all night long on channel 101 with the button #2 in "off" position and the jumper on just to see if it would give the same nag but it didn't. I am confused. I will need to try a diferent lock I think and maybe one for 2700. after that I am moving on to a different lock.

[t160hq]

But what is wrong with this "there is a serious problem with your receiver" NAG, it is only supposed to show up wen charlie ECM's th receiver and that is not the case. Any ideas.

There is another serious error nag from the orginal TSOP lock days. When the WE pin was kept at a constant logic high. It activates without being sent from charlie.

It happens when the TSOP WE line is disconnected or has a constant logic high.

Since it woks unlocked the WE connections should be ok. You may have a bad IC on the lock. Or wrong connection to the other lines into the lock. Might check to see if they miswired or mislabeled the wires on the lock.

t160hq

[Darnat]

"But what is wrong with this "there is a serious problem with your receiver" NAG, it is only supposed to show up wen charlie ECM's th receiver and that is not the case. Any ideas. "

This is not true this nag can be sent by your provider anytime they want,not just when they send an ECM.

[DTVismybitch]

Just curious but could the problem be that I am using a software version that does not work with a TSOP lock yet. I have 767P or P767, whatever it is. I was told that maybe anolder firmware will fix it. Could this be true or is it definitely the TSOP lock itsef, because it it hooked up properly. Thanks.

[Darnat]

Have not heard of any f/w being able to beat the lock as of yet....anyways if you want to just flash another version onto the tsop ,(keeping a back-up of what you have now,of course)try it,it might answer a few of your questions.

[t160hq]

The 301-010 is the only box I know of to have a firmware version related lock problem. I think you may just have a bad lock. May not happen often but every once and a while a defective IC makes it past the QC checks.

t160hq