Se to, the comport is set correct, as well as your
Connect it all ( COM-portcable/USB-cable,
Powersupply) and insert your Penta
in the cardreader, cardcontactpads
facing the readercontacts.
(This info is for programming the Penta Vr3
for Conax)
Start Winexplorer Version 4.5
Goto File > * open script *
Click on the card tab and click * Execute script *
Then find the file> Penta3_C_N_X.bin
(it will automatically ask for this)
Now the update will run and can easily take around 5 min.
Thats it !!
You can if you wish highlight what’s written and copy/paste it to some
txt-file for later study, eg. comparation with the example given below, how an
update should look like.
Now you need to program file2 (mostly an update file with new MKeys)
Start Winexplorer Version 4.5
Goto File> open script
Find the Penta3_C_N_X_AU.xvb
Click on the card tab and click * Execute script *
Then find the file> Penta3_C_N_X_AU.bin
(it will automatically ask for this)
Now the update will run.
Thats it !!
You can if you wish highlight what’s written and copy/paste it to some
txt-file for later study, eg. comparation with the example given below, how an
update should look like.
After that, you must upgrade the pentacard
Vr3 with conax
3.03/2.01 soft
Start Winexplorer Version 4.5
Goto File> open script
Find the P.N.T3.camfix.xvb
Click on the card tab and click * Execute script *
then find the file>
P.N.T3.camfix.bin
(it will automatically ask for this)
NOTE: The name of the above mentioned files might change, but I hope
the idea is clear!
The author of these lines personally never
had the slightest problems in programming a Penta,
actually it always did work the very first time when ever having given it an
attempt, unless the crd was inserted upside down in
the programmer, which also happend 
, but also this is indicated by a
responce from Winexplorer
that a reset didn't occure and so ones attention is
immediately drawn to the fact that one did make a mistake !
Whilst though playing around with the Penta and Winexplorer, lots of failures where provocated,
more or less intentionally, so below there is a collection.
There are so many reasons why you don't succed, so
many traps and possible failures.
I've seen ppl who forgot to power up their
It is impossible to mention all the possible failures and some users faults
which often are basic ones, like forgetting to apply correct power to their
Setting a wrong COM port though is indicated with, that one doesn’t get a
reset.
Also the current Penta Vr3 doesn't by default work on
all CAMs, it is made for the Conax
4.0 CAM and will also work on embedded up to date CAMs
(firmware), but remember to apply a CAM fix to your card, f.ex
for a 3.03 CAM IF you use a such..
So here we go..thoughts and
tips..:
IF you don't use a V 4.0 Conax CAM, you have to apply
the
Then the Penta will work..you program that fix, after you have programmed your crd with the penta Vr3 file(s).
You can apply that fix anytime, even if and when you are using a 4.0
Answer yourself the following questions:
Are you sure you use the correct updatefiles to the
correct type of Penta card?
The files for Vr2 and Vr3 are different..
First thing is to check if the ATR is correct, se
below..
Does it look like IF the crd is programmed, eg. do you get a 90 00 at the end of each TX-string when
programming?..
Have a look at the script when it runs and store it for studying afterwards..
Have you set your
The nominal X-tal frequency is
3.579545MHz, popularily mentioned
either as (more correct) 3.58MHz, sometimes mentioned (more incorrect) as 3.57
MHz.
Never use an Elvis (Adteknik v 3.4/3.5 programmer)
IF you have a cheap
You can use any
Have you ever earlier programmed any crd in that
programmer you just used in modus 3.58MHz, f.ex. a
BC, Titanium or any other PIC crd,
where only the eeprom had to be programmed/updated?
One more fast tip when you failed several times to program your card..
Unpack all the files again from the zip into
another dir and WRITEPROTECT the winexplorer.ini!
That's the first step to success..BUT
note, you can only do this right away, IF and when you
use COM1, which is set as default in that ini.
IF you want to use another comport you have
to alter that setting first, THEN writeprotect it afterwards..all this has to be
done BEFORE you tickle winexplorer.exe
Then try it all again but open winexplorer by opening
it and then load the file, not by clicking at the xvb-file!
This is important the very first time, if you earlier fumbled around with
other/newer versions
of Winexplorer as your PC does *remember* the last
Winexplorer.exe you have used and if you in the meantime have programmed other
cards then a Penta using another version of Winexplorer you will automatically start this (wrong)
version when clicking on any xvb-file which then will
open that latest in use version of Winexplorer..also be aware of to power on your
You can't use other versions of Winexplorer then Winexplorer 4.5 (the one supplied by the Penta team) as it is, unless you use the winexplorer.ini as
it is supplied by the Pentacrew and even there there might be some differences so you have to use the 4.5
version supplied not to get further probs and to be
on the safe side..
Though I have to mention, I have used newer versions of Winexplore
(f.ex.5.0) to Program a Penta and I had no problems,
the above is just mentioned for less experienced ppl
to use the originally supplied version 4.5, as the ini
does fit.
If you
are in doubt, what cardversion you have, you can
always try the VR2 files but here you also have to load the Mr. Fix it files,
containing the current in use OP-key as well as always the CAM 3.03 fix.
Notice you get an 90 00 when programming, as in the
below following example!
Executing Script: Script File:
Trying to reset card...
Reset Successful
RX ATR : 3B 24 00 30 42 30 30
The file size is 7052
TX Data : C3 77 00 00 56
RX Data : 77
TX Data : 49 7D 37 FF 1E 5A 16 77 BB A3 91 F5 6B 02 B1 48
C3 BE 4D 1D 8A DB 92 2E 84 29 09 4C 15 E7 DF 9A
71 D0 97 45 CD 1A 91 1C 92 0E FB
68 4C E7 77 D6
2B 72 7D 89 C8 35 0D 86 87 F8 7F BB AC 62 8A 82
E1 F0 1C 19 05 40 51 E7 52 AA DF 32 6A 18 CE 1E
20 AD FD 95 02 87
RX Data : 90 00
TX Data : C3 77 00 00 56
RX Data : 77
TX Data : 0D 7C B7 D7 A5 7D E1 62 44 19 1E 80 8D BA 3D 82
74 33 82 D1 66 1E D7 2C 78 ED 99 8E DF BD 2B A8
E3 36 75 DB B6 70 04 FF 6A A4 A1 B5 00 9A AC 60
0F E5 4C BA 85 5A EC 1F 33 1D 6F 8F AA 76 AF 92
67 00 AF B5 8F DB 2F FE 7A 61 49 07 8A F0 90 01
D2 EC B8 10 40 F3
RX Data : 90 00
TX Data : C3 77 00 00 56
RX Data : 77
TX Data : 14 37 74 8F 49 A8 9F 73 60 2B C9 62 41 90 87 7F
A1 C8 9D 9D EA 87 AD 6C
95 8D 6F DA 96 F9 94 5D
3C 35 5E 57 AE 8A D9 20 88 80 DE 06 BC 28 FC E6
99 57 F2 FC 99 A6 8B C8 86 05 D3 0E 3F 04 39 61
0E 6E 9E FA C5 66 E2 4B F3 02 DD CC 67 29 A0 19
35 31 56 DF C3 0A
RX Data : 90 00
The above example is only the upstart of the update, NOT the complet update, just to give an example.
You can see it all AFTER you have programmed and then you even can highlight it
and copy/paste to a txt file. (f.ex)
IF you don't have the 90 00 at all RXD data (as shown
above)you haven't pressed anything inside that crd of yours, meaning the card is in the same state re contents
as before you tried to program it!
Remember to use the Penta3.xvb and the Penta3.bin, as well as the
P.N.T3CAMfix.bin and xvb if you don't use a 4.0
Thing also is, that winexplorer.ini is easily damaged, as every single time you
use it, there is something written to it which might f*ck it up, so the most
important thing is to make that file writeprotect
right after you have unzipped the files and before you use Winexplorer..you do so by rightclicking
on that file and alter the *properties*.
Also your programmer just might need other settings in the ini
re ResetDelay,ByteDelay and
even probably xBytetimeout, this depends on that
programmer you use AND your PC..IF you had used a
simple
Anyway, have a look at the winexplorer.ini, it should look at the [MRU] (end of
the ini) totally empty and there should be absolutely
nothing written there..
Here is the ini as it should look like, compare with
the one you have:
[Serial Settings]
Device=com2:
BaudRate=9600
ResetBaudRate=9600
ResetDelay=4 00
ByteDelay=100
Parity=1
StopBits=2
ByteConvention=1
FlushBefore Write=1
RxByteTimeout=500
[Misc Settings]
LogTransactions=0
PromptLogName=1
StepMode=0
DisplayUSW=0& lt; br>DisplayHexUSW=1
DisplayFuse=0
DisplayHexFuse=1
[Advanced]
Ign oreTimeouts=0
ResetMode=1
ResetAfterTimeout=1
[MRU]
The comport setting you have to alter of course to which port you use..I do use for certain reasons com 2 (Infinity USB
Phoenix)
So, give this all some thought, I'm sure you'll succed..most important thing is the ini
is as shown above and it is writeprotected and..the ATR
is essential too when running Winexplorer, when the ATR isn't corret, something is
wrong..
The ATR on a blank just received Penta
is:
ATR: 3B 05 42 4C 41 4E 4B
Convention: DIRECT
Protocol: T=0
Historical Bytes: 42 4C 41 4E 4B
B L A N
K
After programming it successfully for the first time it HAS to be:
3B 24 00 30 42 30 30
This means, when you reprogram a card you earlier programmed, you should have
the above (new) ATR as a *base*.
So what is the first thing to do?
Try to analyze the ATR of your card..you do so by clicking on that magnifier glass on
the top bar of Winexplorer saying: *Analyze a cards ATR* all this AFTER you have writeprotected
the *fresh* ini.
Note, that when writeprotecting the ini you'll get an errormsg re the
system can't write to the ini..ignore
that, just continue...
Good luck...
Do you use
Windows XP?
I guess you do!
Then the following might be of interest!
No matter what you do, no
matter how clever you are you can't beat the *system*..the
*system* being Billyboy..and
in this case not our mutual friend, but Billy Gates!
So much has happend during the years of using Winexplorer, I almost forgot to mention the following..
No matter what you do, it might be your PC when you are using XP that does
prevent you from programming a Penta using Winexplorer!
Thing is, Windows XP and comports is a very bad thing..there always are problems with this!
Ppls PCs are different re COM ports, even when run
the very and exact same version of XP.
I too had earlier problems with this when using a normal
The moment I moved to one of my other PCs @work running Win98, there was
absolutely no prob in using Winexplorer,
when trying to do so on the XP-PC, it simply didn't work..a crd couldn't get programmed by use
of Winexplorer.
The
Mind you, Winexplorer is quite a bit older then XP..
There is a solution to this and this is the last resort, if you run XP and
can't get it to work together with Winexplorer and
your Penta, a solution I used and which did the trick..
Get yourself a USB > RS 232 converter, which consists of a cable with an USB
plug in one end and a DB9 serial in the other..the DB-serial usually has built in electronics and
mostly even one or two LEDs.
This thingy comes with software which does enable a so called *virtuel COMport* usually COM4.
Connect it to an USB output on your PC and the other end to your
Think about it, this well may be the solution to the problems some of you have..
Just one remark re all the tips and tricks, even when I myself have
contributed..
PCs are strange creatures and have a life of their own.
Only ppl with less experience ever will believe
a *do this and than do that* kind of tip will work 100% on their system,
because it does work on the authors system!
If I write this and that works for me, don't believe it will work for YOU..and vice versa..there are too many differences in PCs even when
running the exact same updated and latest version of the same OS!
Especially XP and COMports are a chapter for themselves..all this FIFO stuff
and diff. chips used make all the difference, believe me, I've had my fair
share of problems during the years with lots of diff. IF's
NOT working at my place..
Everybody else praising this and that programmer, let me have a go and
I never was surprised it absolutely didn't work in my set-up..
Did I have a special one?? Absolutely NOT..
Couldn't I find out to install and run that high praised thingy??
Absolutely NOT!
One example is the so much praised Elvis..
Well, of course it works at my place too, but it is unreliable and
doesn't work *always*..sometimes it even can't find
the COM-port!
Now can anybody be happy using a such device??
Thousands of ppl are happy and have
absolutely no prob in using it..
So what..it doesn't
work reliable here, it doesn't work reliable on a lot of ppls
machines I know personally, so why recommend it then? I don’t !!
Why calling it the 8th worldwonder?
IT IS NOT!
Same goes for
VX4fun..nice programmer, working most of
the time but still I can’t recommend it and of course it can’t be set into
The only ones so far I can highly recommend are the products from WBE-electronics who really have done a pro job in developping their stuff..and more important, their soft works,..all the time..not
only at my place..
The Infinity USB, the Infinity USB Phoenix, the Phoenix USB, the normal
Phoenix/SM they sell at a very cheap price (DKK 199)
are all working to perfection...
So let me say it once again..to
hell with the ELVIS!
Love his songs, but he should had stuck to them and kept his fingers
off programmers :-/
And..so far I didn't hear of anybody who NOT could
program their Penta sooner or later, after some minor
upstart problems.
In most cases it was wrong set ups (COM port), wrong winexplorer.ini, faulty
programmer, PS not set correctly for the programme, wrong files used or similar faults related to the programmer..
This again gives a pattern, some programmers are better then others, meaning
that even the recommended Cryptik does depend on
certain things..you se Power
Supplies are a strange thing, the voltage they supply is depending on so many
factors -unless one does use a higher priced stabilized one-, the load that
they have to supply and most important this also is influenced by their
*nominal* current value they are desigend for..
Never use f.ex a 1A one for a interface that one
draws 100mA current, because in that case the voltage supplied without load
when set to 12VDC, might well be at least 18VDC and the onboard (Interface) stabilzer might get an overload..
Far too tricky..and only for
ppl with some technical knowledge re all this..
Solution again..the Infinity
USB Phoenix or any other USB device, NOT using a PS 
The
following parameters have influence on programming your card,
answer yourself the following questions when analyzing the problems you
encountered.
1.What programmer do I use? (exact type..is it approved for
programming a Penta)
2.Which settings in my programmer (3.58MHz) ?
3.Did I set it in *
4.What Power-Supply/settings (eg.
voltage/current) do I
use? Is it a correct one/settings correct?
5.What
6.What OS am I using in my PC?
Here finally
one of the insidences that occured lately..
Some guy
couldn’t program his card and nothing did help..and then it showed up he made a classical and
earlier mentioned mistake..he
didn’t use a
He ALSO
used wrong/old files..so
what can you expect then??? L
Our
friend did use an Infinity USB, and not an Infinity USB Phoenix, so no wonder the card couldn't get programmed.
It is impossible to mention all the
crazy things ppl can do when trying to program their
card.
Using a NOT suitable programmer is just one of them..
REMEMBER, you have to use a
No fear Pentacardsellers, this is NOT about programming Basicards but a very short explanation, why the
*Reset* and the *correct *ATR* is so importnat and what it means..explained in a language even little Per from SE does
understand..
Now why
did I always mention the most important start of any successfull
programming is a *Reset* and the *correct* ATR, and
what does this mean..
Most of
you of course will already know, but there are also ppl
around using f.ex. Winexplorer
and programming a Penta for the very first time..so here it is..
Whenever
you use Winexplorer, with the correct script to
program your Penta via a Phoenix IF, Winexplorer throws a command at your card which first does
say:
*Hello,
are you there*?
*YES!*
from the card which
is equal to a *Reset*
Next
thing is the card is asked via Winexplorer/Phoenix:
*What is
your name*
and
hereto a blank, just received Penta should answer:
* My name
is blank Penta*
this is
the ATR which in this case is:
*3B 05 42 4C
41 4E 4B *
If you
earlier have programmed your card it should answer:
*My name
is Penta* (
this
still is the ATR but in this case in computerlanguage it is:
3B 24 00
30 42 30 30
The responce (ATR) is depending on
the type of card and the above examples are for the Penta,
though the ATR of the programmed Penta
is equal to the original blue Media Highway cards from Canal Digital and have to..because the card has to be
recognized by the receiver later, where here it is the receiver asking:
*Hello,
are you there*?
and
*What is
your name*
and..your receiver only wants to talk
further to your card and enable descrambling eg. first recognizing your card as a pal, when the feedback/returnanswer is as it should be..
That's
the reason why your script won't communicate with a crd
with a wrong responce..your crd is not a pal of that script incase
it doesn't answer back in the way the script does expect..
Sorry for
the long explanation, but it is to my nephew *little Per* in SE..
A word
about programmers...
Even when
using authorised
An
example is the low-priced and normally well working Cryptic
Some ppl reportet they couldn’t program their Penta
with it.
In all cases it turned out to be a problem with the
Power Supply they used.
When set to 12VDC, no way to get the card
programmed, when set to 9VDC it worked without any problem.
Of course a such
mysterious failure should never occure - and it
doesn’t when f.ex. using a
product from WBE -, because on-board of even the Cryptic, there is a
5VDC voltagestabilzer and all voltages between at least 9VDC and 12VDC should get converted
safely down to 5 VDC operating voltage...
Somehow this programmer though has a problem
there...
This
treatise can never be finished, because there is no limit to how silly ppl can act – and this includes me too! - when programming
their cards..their is no limit..only ones own imagination
is the limit..everything is
possible, every silly fault can be done by myself and others at a moment of
less concentration.. Therfor let’s finish this now,
otherwise countless of sides could be added..
There is
a lesson to be learned here!
I think it has been mentioned before...whenever one doesn't get a picture and
one is convinced having programmed the card correctly, one has to step a
channel up or down, AFTER one has waited sufficent
time for an update and not gotten a picture..actually the key has been stored within the
*normal* time of receiving an update, but the channel simply didn't clear.
This is very common and I had the very same lots of times, so whenever one is is doubt, step one channel up or down and IF this channels
is within that package (CD) one will get a picture..
Even if all the dumps from the update
show everything is OK, the card is (looks) programmed correctly and
looks OK and no picture occures, my advice then still is: *Just wait for an
update*..
Admitted, I had forgotten to drawn attention to, that updates not always result
in a picture, but the up/down trick has to be used..
Next time, when they swap OP-keys and you wait for an update don't think
instantly the have killed the SA used..just
step up and down by remote and most likely a picture will pop up...even
original cards can behave the same way sometimes..mind you that shitty IRD is
a *computer*..and we all know how reliable these are! 
