NawapoC 4.1 All you need to know and Some Troubleshooting Answers -- Eye In The Sky

[ Show ]

Support VoyForums

[ Shrink ]

VoyForums Announcement: Programming and providing support for this service has been a labor of love since 1997. We are one of the few services online who values our users' privacy, and have never sold your information. We have even fought hard to defend your privacy in legal cases; however, we've done it with almost no financial support -- paying out of pocket to continue providing the service. Due to the issues imposed on us by advertisers, we also stopped hosting most ads on the forums many years ago. We hope you appreciate our efforts.

Show your support by donating any amount. (Note: We are still technically a for-profit company, so your contribution is not tax-deductible.) PayPal Acct: Feedback:

Donate to VoyForums (PayPal):

[ Login ] [ Contact Forum Admin ] [ Main index ] [ Post a new message ] [ Search | Check update time | Archives: 1 ]

[ Next Thread | Previous Thread | Next Message | Previous Message ]

Date Posted: 23:38:40 02/24/02 Sun
Author: Zargon
Subject: NawapoC 4.1 All you need to know and Some Troubleshooting Answers

====================================================================
====================================================================

NAwapo version 12.4.1 (pfg version 0.3)

====================================================================
====================================================================

*** Scroll Down For Troubleshooting ***

NAwapo provides CAM-less AVR support for Bell ExpressVu and for
Dishnetwork systems. If the AVR includes a serial EEPROM, 24LC128
or larger, then NAwapo can be configured to adapt automatically to
public key changes.

Kudos and Konspiracies
=======================

NAwapo is the collective product of the direct and indirect efforts
of a great many people. Special recognition goes to Wapo and Obiwan
for the original base code, to the many, many contributors at
ID-discussions, and especially to Roybillybob for his talents and
perseverance which helped make NAwapo a reality. Thanks also to
www.dsk-online.net for supporting the effort.

On the other hand, there are those individuals out there that would
take credit for that which they did not do. Ordinarily, it would be
just a sad plea for attention, but when a dealer is involved, it is
something far different. The proprietors of Three Stars Satellite
may deserve your pity, but not your trust, and definitely not your
money, at least in the opinion of this author.

Caveat Emptor
==============

This software originally was developed as a "proof of concept" that
the lowly AVR3 (with EEPROM) was capable of processing public key
changes and handling the MECM messages. This software is still
experimental. The poor AT90S8515 (the processor used by the AVR) is
being pushed to the limits of its ability, especially to decode the
Dishnetwork stream. Brief blackouts or freezes may occur at random
times, and longer blackouts or freezes may occur during any key
change. If NAwapo works for you, that's great. If not, well, keep
in mind that it is experimental.

Some Notes on Blackouts
========================

In order to decode the video keys for the receiver, NAwapo needs to
stay synchronized with the series of MECM messages imbedded in the
satellite signal. If NAwapo gets out of step, then blackouts or
freezing of the video images (depending on the receiver model) will
occur.

A smart card needs to do the same thing, but the smart card can
resynchronize in less than a second. NAwapo needs approximately 25
seconds to decode an MECM message. As a consequence, if and when a
blackout or freeze occurs, it may take up to 40 seconds for NAwapo
to recover.

Most of the time NAwapo does a good enough job keeping up with the
MECM messages. However, not all channels us the same MECM stream.
In particular, it has been observed that channels on the satellite
at 61.5W use a different stream of MECM messages than do channels on
119W or 110W. Switching to or from such channels will result in
a blackout while NAwapo adapts to the new MECM message sequence.

Also, while tuned to a preview channel, a music channel, or while in
the guide (without picture-in-picture), no MECM messages are sent to
NAwapo. Upon switching back to a normal subscription video channel
can result in a blackout while NAwapo recovers. (The blackout may
not be immediate, either. It can be delayed by 30 seconds or so.)

When the public keys are changed, NAwapo refocuses all of its
efforts on decoding EMM messages to discover the new keys. Decoding
EMM messages uses exactly the same process as MECM messages, so at
least 25 seconds are needed to "roll" the keys. Moreover, since not
every EMM message will contain the new keys, NAwapo may need to sift
though several EMM messages to learn the new keys.

Typically, NAwapo will take 60 to 120 seconds to discover new public
keys then 30 to 90 seconds to resynchronize with the MECM messages.

Revision History
=================

* 12.4.1 -- Move post-RSA-decryption code to be inside the interrupt
handler. Handle alternate RSA decryption method for
EMM's. Rearrange a lot of code. Use the UART for
incoming data. Correct error in status flag handling.
Trim 2 seconds off RSA decryption. Package NAwapo as a
jEEPers *.PFG file.

* 12.3 -- Fix a potential stack overflow condition. Restructure
how processing status is maintained and how it is
reported to the receiver. Add a demonstration program
for generating customized configuration files. Remove
manually configurable .EEP file.

* 12.2 -- Minor rearrangement of data and of code to reduce
blackouts and freezes on Dishnetwork. Fix error
introduced in 12.1a regarding CAM status for BEV setup.

* 12.1a -- Interim release intended to decrease the likelihood of
blackouts or freezes on Dishnetwork.

* 12.1 -- Add MECM support thereby adding support for Dishnetwork.

* 12 -- Initial release. Support for Bell ExpressVu only.

Prerequisites
==============

You will need the following:

* An AVR3. If the AVR includes the so-called "autoroll chip," then
NAwapo can automatically adapt to public key changes. (The chip
is an external serial EEPROM -- the 24LC128 or 24LC256 is an
appropriate device.) An "autoroll jumper" (between pins 10 and
12 or pins 11 and 14, depending on the style of AT90S8515 used)
is not required.

* jEEPers version 2.0.7 or later.

* Your receiver's box key. This is a 16-digit hexadecimal number
unique to your equipment.

* Your receiver's IRD number. This is the receivers serial number,
usually of the form R 00 1122 3344 - 55.

Installation Instructions
==========================

1. Place the NAwapoC.4.1.PFG file in the same directory where
jEEPers DX 2.0.7 (or higher version) is installed.

First Time Usage
=================

1. Start up jEEPers DX 2.0.7 (or higher version).

2. Select NAwapoC4a for the Program selection.

3. If your AVR includes an external serial EEPROM, 24LC128 or larger
memory, then from the jEEPers menu bar, select I2C EEPROM. In
the pull-down menu that appears, select Write NAwapoCx(24LC128).
It will take jEEPers a few minutes to load the serial EEPROM.
(You may skip this step if your AVR's serial EEPROM is already
loaded with the 24LC128.HEX file from any prior release of
NAwapo.)

You have a choice to make. You may select a single provider, either
Dishnetwork or Express Vu, and be able to specify up to five tier
ranges, or you may select both providers and be limited to a single
tier range for each one.

4. In the Network field, select a provider, either Dish, Express Vu,
or Both.

5. Hit the Get button to obtain the current values for the public
key fields, Key 0, Key 1, Aux 0, and Aux 1.

6. In the IRD # field, enter your receiver's CA ID (which you can
get from the satellite's receiver System Information menu
screen). Ignore the dash and two digits following the dash when
entering the CA ID.

7. Optionally, in the CAM ID field enter any valid smartcard CA ID.

8. In the Box Key field, enter the box key for your receiver.

9. Optionally, edit the Min and Max Tier settings. If you selected
Both as your Network setting, the first tier pair is for
Dishnetwork, and the second is for Express Vu. If you are using
a Dishplayer on Dishnetwork, you may want to try the following
min/max tier selections:

0001 / 03FF,
08FC / 0A28,
04F2 / 06EA,
7E00 / FE00,
and 7E00 / FE00.

10. Optionally, change the Time Zone setting.

12. Optionally, change the Zip Code field.

13. Hit the Full Monty button.

Resolving Common Problems
==========================

Problem: I do not get any PTV functions on Express Vu.

Resolution: Select Both for the Network selection in jEEPers.

Problem: When I put the AVR in the receiver, I get a message
telling me the smart card is not valid for this receiver.

Resolution: The IRD number is incorrect in the AVR's
configuration.

Problem: When I put the AVR in the receiver, I get a message
telling me the smart card is not inserted correctly.

Resolution: In jEEPers, use the Full Monty fucntion to
completely reconfigure the AVR. If the problem persists,
try unplugged the receiver and disconnecting the satellite
cable before inserting the AVR.

Problem: All I get are the preview channels. Most channels are
listed in red in the program guide.

Resolution: Either (a) your network setting is not correct
(e.g. Dish when it should be Express Vu), or (b) the min and
max tier ranges are incorrect (e.g. FFFF / FFFF instead of
the more typical 0001 / 7FFF).

Problem: All I get are the preview channels. The program guide
shows all channels as open.

Resolution: This can be a problem either with the public keys
or with the box key. Reduce the number of possibilities by
using jEEPers to manually loading the current public keys
onto the AVR.

Problem: All I get are the preview channels. The program guide
shows all channels as open, and the public keys are correct.

Resolution: The box key is incorrect in the AVR's configuration.

Problem: Everything seems to work until the public keys change.
Then it goes blank.

Resolution: If the problem persists for more than two minutes,
then it means either the AVR does not have a serial EEPROM
installed or the serial EEPROM is not correctly loaded with
the data needed by NAwapo. Use jEEPers to load the serial
EEPROM. (Instruction #3 in the "First Time Usage" section.)

Problem: Sometimes when switching between channels or going from
the guide back to a channel, the screen will go blank for 30
seconds or so.

Resolution: Read the "Some Notes on Blackouts" section.

Problem: Sometimes it works great, but other times it blacks out
or freezes or puts up error messages. It may recover by itself
in a few seconds. Changing channels may help. Often I need to
reset the receiver to get it going again.

Resolution: Read the "Caveat Emptor" section, especially the final
two sentences.

[ Next Thread | Previous Thread | Next Message | Previous Message ]