next »

[Td]

Dont install the 47 cap.
its for the wasabi modchip not for the infectus.
If INFECTUS or OSCAR could enlighten us on that matter,before someone blows up their wii.

Well, first we'd have to figure out what point on Infectus corresponds to K on the Wasabi.  My guess is the cap is just used to remove noise from the data lines/stabilize the FPGA.

Edit: Looked at the datasheet and install diagrams for Wasabi and Infectus. Line K on the Wasabi I believe is pin 22, which is a programmable output. So it completely depends on how Infectus has programmed their Actel chip. Currently, it seems Pin 22 (which I think is G on the infectus) is being used for Region patching, as Infectus pointed out earlier.

It may be a completely different problem all together as well.

[Td]

My Wii's drive wasn't powering on at all with the 1.1 dat. Just seemed like the D2C chip crashed and was stuck. Wouldnt accept a disk, didn't make any noise or anything.. Flash back the original wasabus.dat and the drive sprung back to life with the exact same issues as before.

Decided to rewire it for the 13 wire install just to make sure everything was still workin', and it just booted a backup on the first try. Also to note: The Wii drive turned on as soon as the Wii turned on using the 13 wire mod. It took up to 6-7 seconds to turn on after the Wii turned on for the drive to start up using the wasabus.dat and 9-wire install.

I guess i'll wait for another beta version before I go back to the 9-wire install for more testing.

[krayziexploiter]

The cap is to reset the chip on bootup. It connects the k point to ground for a split second while charging and then stops conducting.

[Infectus]

XMOD: have you an ntsc console?

Td: If you connect a led between Y - SX , is it turned on or always off ?  (not remember where's + and - )


Don't put any capacitor some where!!

[XMOD]

 

XMOD: have you an ntsc console?
Td: If you connect a led between Y - SX , is it turned on or always off ?  (not remember where's + and - )

Hi
my console is  a pal version!
i ve connect led between y & sx it's always off...

[Infectus]

Have you change polarity in your led?

[XMOD]

Have you change polarity in your led?

Yes and i've test with multimeter  0v!

very strange now i ve 1.9v on 5v point of my infectus.i think i've broke something!!
need to solder 5v point on the square before resistors & composant with N on it!

ok i ve found my probleme  the 2 little composant seem to be dead i've solder a wire for bypass problem !


edit: sorry for my english....

my wii work nice without infectus but when i connect it
the drive always  won't boot & the led doesn't work!
 i'm returm to the 1st state!

[3lix0r]

I'm just trying to understand if there are issues with this setup or are there just a few people having an issue. I'd like to try this method if there are no issues.

Thanks,
lix

[Td]

I'm just trying to understand if there are issues with this setup or are there just a few people having an issue. I'd like to try this method if there are no issues.

Thanks,
lix

At this point, it seems only myself and XMOD have tested it outside of Team Infectus, and we didn't have much luck . So either we're both fools or something else is up. If you don't want to be a beta tester, I'd wait until some more people come forward with a working install before giving it a try. But on the other hand, the more people that try it out, the faster we can determine if it's the firmware or installation.

[The danis]

You right by that Td.

i have has try it out but whit out of lock  But i think that the fireware is one of the problems.

The diagram I you sure that N, M and U that is not should be install on the chip in stedt on PBC

But on ting i dont understand  is if Infuctus team had it work on the ons wii..
Then it should work on others wii as well wiht the same Actel chip A3P060 

Well my Wii is a PAL 

I try out to solder them on chip tomorrow a test it out 

[Berny_AB]

on wasabi FW are many bugs that need to corrected and than the Firmware has to be ported to Infectus (Argon) Hardware

for each Hardware and Actel Chipset it is needed to make a own port

So on Beta firmwares it's normal to have some bug's left - no body is perfekt

I Saw them at work myselfe and they are working very hard on it - just give them the time they need

Don't worry if they don't answer as fast as you wish them to answer - they read the treads and if find a solution and they have time they will answer

[Infectus]

Yesterday we have try many different drive (d2c) and only one is working (with wasabi too).

Probably, you like us, have a drive not compatible.

Today we'll release a version where a led is turned on when the drive probably is not working with wasabus.

[XMOD]

HI
for your test:
detail about my wii not compatible with wasabus beta

pal 3.2E
D2C   n°747P1003
D1A   n°746P678F

infectus 1 A3P060

[krayziexploiter]

Just for clarification....D2C drives that aren't working with wasabi mostly come back to life after resetting the chip or leting it stay on for a while. After that it works fune untill you completely power off the drive. Probably a syncing issue. Maybe too much noise on wires.

[NBlack]

Hi!

Im having troubles with infectus2 060 and Wasabus FW.

D2C-D1A
2 installations without success. The modchip program well (first normal and then flash).

I not use bridges because is PAL but i connect and not run.

I forget something?

Thanks a lot