View Full Version : Troubleshooting CEMU
heyiou
01-11-2009, 06:54 PM
Hey guys, been out of the loop for a couple years, been reading like crazy, sorted through all the diagrams and posts about wiring for CEMU, but I'm having an issue that I'm hoping for a little help on.
I have a 301-013 with a single chip emu setup. Flashed the TSOP, flashed the 2313, got it all wired up. No matter what I do I get the "Smartcard is not inserted correctly" error. I'm pretty sure I've got it wired up right in the cardslot pins (after studing conflicting diagrams). My question is how do you tell which part is not working? Is there a way to verify the connection from the IRD to the 2313 is working? I get the DNASP to show up as 102 REV 10C. So I would assume that this means the connection from the IRD to the 2313 is ok, right? I do not get a S 0000 00 0000 number which I know means CEMU is not communicating with the IRD. I am running a short cable from the IRD to the 2313 but a fairly long cable from the 2313 to the serial port on my computer. Is there a length limit on the serial cable? and what would that be if so? Are there other numbers to check for troubleshooting purposes? maybe something I should be seeing in CEMU or on the IRD system info?
smilingjack
01-11-2009, 07:34 PM
I got 6' and a 6' extension and it work OK
The number of the dish bin set-up should number the IRD #
.
Most likley it the program.
get a book disk set up
get the new set-up for DJGPP
install DJGPP
copy the new modlue1
and run DJGPP
save the cemu.exe to the folder
run
agarnet
01-11-2009, 07:49 PM
Is there a way to verify the connection from the IRD to the 2313 is working? I get the DNASP to show up as 102 REV 10C. So I would assume that this means the connection from the IRD to the 2313 is ok, right?
If you get the card revision on the IRD info screen then yes, the 2313 is communicating with the receiver. So connections form the emulator to the IRD are good.
I do not get a S 0000 00 0000 number which I know means CEMU is not communicating with the IRD.
If you don't see your card number then there could be a physical problem with the hardware ( somewhere between Pc and emulator board) or a software problem. Here's some things to verify:
1) make sure the com port is set correctly in the cemu.ini or cemu.cnf file ( depending on the version of cemu that you are using )
2) check the wiring on the emulator board on the side that connects to the PC
3) check the end connections between the PC and emulator board. By the way Ive seen it work with over 20' of wire
4) PC com port may be too slow ( Could be Pc is really old ~486, the com ports on some new P4 PC's don't work with CEMU, some add-on PCI cards don't work, some USB to serial adapters don't work,... ). If it's slow communication, you can usually tell by what is displayed on the PC screen.
What do you see on the PC screen when you try to run CEMU ?
heyiou
01-11-2009, 08:33 PM
Ok, well, in CEMU it goes to the IDEA0 and IDEA1 lines and that's it, just like it's not even hooked up. INI settings were right. Newer PC so I dont think speed is a prob. HEre's some more details, maybe I'm missing something simple.
Flashed TSOP with the 301-013 Joker files.
CEMU version tried both cemu1.3.44fb_4-19-2008 and Cemu2.10iAR (not sure what the difference is). Used the Cemu_1.34_1.94_Module_1_101608.TXT and the posted update (which I just added to the module 1 file, could not find a section to replace).
My IRD is at p344.
HArdware id of DALC-N
Bootstrap DALC
DNASP 102 REV 10C
Single chip emu
I thought I had the right one chip flash for the 2313 but since it's getting the DNASP to show it should be ok right? or could that still be wrong?
Wiring looks like this, shortened the cabling to <1 ft to count that out, was about 20 ft.
DB9->2313
-----
2->19
3->17
5->10
I assume the 2313 to IRD is ok since DNASP shows.
Thanks for the help, you guys rock.
smilingjack
01-11-2009, 09:26 PM
It the software mode
just load 1.3.4 That I posted
get the files (the base file) from CEMU for DJGPP
and the module1 correction I posted
run DJGPP
take the cemu.exe from there and put it on you floppy disk
.
Their are 6 different version of CEMU, stay with the same numbers, the other won't work
duffybno1
01-12-2009, 12:00 AM
make sure you have a good dish.bin
koolit
01-12-2009, 02:10 AM
make sure you have a good dish.bin
good response!!!
I have multiple 301.013 (single) using internal max/mel running on cemu 1.3.44 and 2.10iAR. All running on private infos and current firmware is at P452. The max length of cat5 cable on one of them is approx 92 ft. long.
DNASP 102 REV 10C ... means you got the correct Atmel Flash. Don't forget to insert a dummy card.
Your max/mel is communicating with PC otherwise you'll get the dreaded "Error 019" on screen. Try to disconnect the serial port to verify!
I wonder if you used Gendt08 properly to match IRD and S Cam.
But anyway, Charlie just sent ECM at 3:00pm PST and cemu and FTA's are currently down:(
Good Luck.
agarnet
01-12-2009, 04:07 AM
It could also be the flash on your Atmel. There are a couple of types of code for the Atmel: inverting for use with the max 232 and non-inverting like the one you need for your single chip setup. The ATR is written the same in both codes, so I believe the receiver would still display the DNASP 102 REV 10C even if you have the wrong code on the Atmel. What flash did you use ?
Here's a 102 10C single chip hex that works :
:020000020000FC
:100000000CC022C021C01895189518951895189500
:1000100018951895189518951895479AF8940027EB
:100020000BBF05BFD0E0C0E60993C03EE8F3D03077
:10003000D8F30DED02BB00E201BB00EC07BB00E70B
:100040000DBF00E00EBFC79800E70DBF00E00EBF78
:10005000839BFECFF89400EC0BBF789490E2CCD059
:10006000EAE6F2E02BE1C8953196002D99D0D9F758
:100070000FED0DBF00E00EBFBCD060D009935ED085
:1000800009935CD00993402E442029F0242D56D0AA
:1000900009932A95E1F752D00993242D04E0200F0B
:1000A000422EA7D00991ABD02A95E1F7A2D05ED01D
:1000B00009935CD009935AD00993402E442029F02B
:1000C000242D54D009932A95E1F750D00993242D7B
:1000D00004E0200F422E8DD0099103D02A95E1F73C
:1000E000C7CF2F93809BFECF889A98E085D000C021
:1000F000909800C000C0000028E0882794E07CD0E1
:100100000000001FC8F00000909A00C0891F817095
:100110002A95A1F794E070D000C0879558F00000B0
:10012000909A00C096E068D0000000C0909A88982D
:100130002F9108959098F6CF9098E8CF2F93809BB9
:10014000FECF8099FECF96E09A95F1F701E099E015
:100150009A95F1F780B38695001FC8F7009599E04E
:100160009A95F1F7809BFECF2F910895B59901C024
:10017000FDCF97E09A95F1F7000000E89AE09A9594
:10018000F1F70000000096B3990F990F990F0795AA
:10019000A8F700959AE09A95F1F7B599FECF0895E2
:1001A0002F93889A90EF28D0909800C000C0F02E2E
:1001B00028E0882795E720D000C0001FC0F000008D
:1001C000909A00C0891F81702A95A1F796E714D0F4
:1001D000879558F00000909A00C098E70DD0000075
:1001E000909A88982F912A9508959098F6CF909894
:1001F000E9CFC0E6D0E008959A95F1F708952F93DE
:10020000C79A9AE09A95F1F788E0079558F00000B0
:10021000C79A0000000099E000009A95F1F78A95CE
:10022000A1F70AC0C7980000000099E000009A9565
:10023000F1F78A9551F700C0C79899E0DDDF2F915B
:100240000895FF920795FF1C0795FF1C0795FF1C5B
:100250000795FF1C0795FF1C0795FF1C0795FF1CC2
:100260000795FF1C0F2DFF9008953FFF9500FF910C
:100270008171FF4700444E41535031303220526566
:060280007631304314004A
:00000001FF
heyiou
01-12-2009, 05:19 PM
Thanks for all the help. I did something and now I'm not even getting the DNASP so I'm going to try another 2313 and actually build the 2 chip setup.
heyiou
01-16-2009, 04:08 PM
Ok, had a bad chip, still have the one chip setup, flashed it with the hex posted above, everything is communicating as should be as far as IRD to chip to emu goes, but I only get a couple REALLY boring stations, like 100, 101 and a couple others. Lots of red channels, lots of green, some white, and have to dial-in pay for PPV. I'm going to do some searching on here, but I'm going to assume that this is .bin file problem. If I used a TSOP flash from the files section, it should have the public keys programmed into the IRD right? Or does that still need changed somewhere? Hmmm, no wait, if it were a keys problem I wouldn't get any video at all right?
gizmolite
01-16-2009, 04:33 PM
if you have video then your setup is ok...sounds like your problem now is expired tier dates or your tier ranges are wrong....update you bin..........
heyiou
01-17-2009, 01:38 AM
Ok first, thanks for all the help, I've got to be real close. Here's where I'm at...
I've tried to patch my dish.bin with Nagraedit and Mr Tierworks, and I've also tried project mayhem. The original .bin is 8k but after I patch it it's 18k. When I start up cemu I get some errors...page fault, SIGSEGV or something. If I delete the dish.bin and copy old.bin to dish.bin cemu will start up with no errors but I'm back to the expired tiers problem. None of these programs seem to like the dish.bin that comes on the boot floppy. When they try to detect the type of bin this one always comes up as unknown and looks to be 20k where the bn103 is 18k.
I'm sure I'm missing one critical part, but what is it?
Does the .bin from the boot floppy not work? Does a bin need to be 8k after patching?
Also, looking back thru these post...someone mentioned gentd08...i did not use that...that the problem?
heyiou
01-17-2009, 03:49 AM
Ok, was trying to use Nagraedit 5.2 which does not support rom10's. Ah ha, so got Nagraedit 4.1 and we'll see how it goes now.
koolit
01-17-2009, 03:50 AM
Yes, dish.bin is 8KB.
I assumed you're using public infos. First off, make sure the IRD TSOP matched the public SCam on dish.bin
Create Cemu tiers patch using MrTierworks or any rom 10 tier updater utilities of your own preference.
Open dish.bin using NagraEdit 4.1 and choose Rom 10.
Under tools, select clean card then clean tiers and PPV.
Then patch with newly created *.ep10. Save image as dish.bin but make sure to select "All Files" under File Type before hitting Save.
Hope this helps.
heyiou
01-17-2009, 05:15 AM
Thanks to everyone, I'm golden now. Once I got the Nagraedit version thing figured out it was downhill from there. I'm still getting freezing even with the new module1 from the 13th. Is there something I need to update or is that just Charlie playin his games tonight?
vBulletin® v3.8.4, Copyright ©2000-2009, Jelsoft Enterprises Ltd.