Poking fun at a guy's fixation with you being on/off the thread. oncle is very sarcastic. Funny when it is about others.Is that even relevant?
Poking fun at a guy's fixation with you being on/off the thread. oncle is very sarcastic. Funny when it is about others.Is that even relevant?

I was referring to the USB cable.The problem is what part of the Wii U is going to receive the signal? You can tell the sensor bar to turn on and off ... but the sensor bar actually senses nothing.

Ah,I was referring to the USB cable.

I don't know if the Wii U can detect signals coming through the sensor bar port...Ah,
Okay, that makes sense then. Receiving information is a little more complicated than sending but receiving through USB is definitely far more possible than the sensor bar![]()
Ah,
Okay, that makes sense then. Receiving information is a little more complicated than sending but receiving through USB is definitely far more possible than the sensor bar![]()
For reading a terminal in a debug propose it's really enough.you can only bitbang data out with the sensor bar port, very slowly.
In contradiction to its name, there was no kind of sensors inside the sensor bar. The bar was only embedded with five infrared LEDs on each side edge, inside the black acryl plastic cover. These five LEDs are connected in series and supplied with about 7.3 V direct current voltage from the Wii main unit. It is not that we examined it closely; but there seemed to be no modulation in light, with the LEDs simply lit all the time.

My mistake, I misunderstood the question.Maxternal -- First of all, I commend you and others who are persistently working on this interesting project.
I have several questions:
Is it possible to decrypt vWii system menu file 00000017.app (taken directly from /title/00000001/00000002/content folder) using your ancast image decrypter?
And since I dont want to install IOS254 on my vWii, is it possible to use the option bootmii=0 for nswitch to load armboot.bin from ancast image decrypter (i.e. first replacing armboot.c in the nswitch with the content of such armboot.bin and recompile nswitch)?
The reason I want to decrypt this system menu file is to see whether I could make the rebooter feature in my WiiLauncher application (see https://code.google.com/p/wiilauncher/) to work with vWii (currently it works for Wii).
Thanks.

Yeah, that definitely should work by just replacing armboot.c like you said and then changing the /title/00000001/00000200/content/00000003.app file it it pre-loads from NAND to the /title/00000001/00000002/content/00000017.app file for the system menu.Maxternal -- First of all, I commend you and others who are persistently working on this interesting project.
I have several questions:
Is it possible to decrypt vWii system menu file 00000017.app (taken directly from /title/00000001/00000002/content folder) using your ancast image decrypter?
And since I dont want to install IOS254 on my vWii, is it possible to use the option bootmii=0 for nswitch to load armboot.bin from ancast image decrypter (i.e. first replacing armboot.c in the nswitch with the content of such armboot.bin and recompile nswitch)?
The reason I want to decrypt this system menu file is to see whether I could make the rebooter feature in my WiiLauncher application (see https://code.google.com/p/wiilauncher/) to work with vWii (currently it works for Wii).
Thanks.
Yeah, that definitely should work by just replacing armboot.c like you said and then changing the /title/00000001/00000200/content/00000003.app file it it pre-loads from NAND to the /title/00000001/00000002/content/00000017.app file for the system menu.
As far as the rebooter, I've only played with resetting to the vWii menu a little bit but maybe you'd know better than I how to get it to load the IOS80 back again when exiting the MINI-mod (armboot) to be able to get back to the system menu. I'm willing to help with whatever I can, though. Let me know how things go with that.
I hope people won't try to plug their sensor bar to an usb port with a resistorJust a few more words considering the lolserial.
It's probably not needed to convert the sensor bar signal to the rs232 voltage levels.
The rs232 V24 standard basically says that the idle voltage should be between -3 and -12V and the other voltage between +3V and +12V.
A Voltage between -3V and +3V is basically invalid and could be used to detect a "no connection".
Those voltages aren't used in digital circuits that usually work on 5V or 3V3. For that reason, the RS232 V24 signals are first connected to a line driver chip that converts the voltages. Such a well known chip is the MAX232 from maxims semiconductors.
Usually, such a line driver chip only considers 2 different states. A voltage lower than 0.6V is seen as idle and a voltage higher than this treshold is seen as a signal.
As the sensor bar voltage is between 7 - 12V, that's more than enough for most line driver chips. If you switch it off, it probably won't show you 0.6V or more. You might terminate the sensor bar output with a 1K resistor to prevent noise to reach the 0.6V level.
So, basically, all you might need is just a 1K resistor and the cable of a sensor bar. It all depends if the common (GND) or the positive (12V) terminal is switched. If they leave the 12V on and switch the GND you will need an opto isolator between your sensor bar output and your serial input.
The speed that can be achieved depends upon the speed of the bitbanging software and the maximum speed the hardware can follow. Digital signals are never 100% square and usually have a hyperbolic shape. If you switch off and on the signal 2 fast, it might not swing below and above the 0.6V level that most line drivers use as treshold between mark and space.
Take special attention to the word most. Not all are alike, and some really need the negative voltage.

I think he was saying a MAX232 chip for the conversion AND the resistor to eliminate some noise.I hope people won't try to plug their sensor bar to an usb port with a resistor
I have no motherboard with "classic" serial port, I prefer be safe and convert signals the "right" way with a max.
But I don't understand how you reach the -3V/-12V low level of a common serial port from a 0V-7V with only a resistor ? 0 - 7V works without adaptation ?

Go to Sven's twitter. He posted a picture of a device hooked into Wii U usb port. Part of this?Maxternal post: 4928150 said:Meh, or I could always just get something like this already made for me
http://www.aliexpress.com/item/NI5L...013999999870&gclid=CLWa7Z_D6rwCFSXl7AodnwYAqw
Yes, should work perfectlyMeh, or I could always just get something like this already made for me
http://www.aliexpress.com/item/NI5L...013999999870&gclid=CLWa7Z_D6rwCFSXl7AodnwYAqw
Yeah, all I know is that the discussion brought this to my mind. http://twitpic.com/bjklgkI was talking about connecting it to a serial port, not an usb port. If you don't have a serial port on your pc you can use an usb to serial converter. Ftdi and prolific are 2 brands that make chipsets and dongles for this purpose. prolific is found in all kind of brands of such devices. A serial port is usually a db9 male connector. It has RXD on pin 2 and GND on pin 5.
A max232 converts from TTL to RS232 V24. The output from the sensorbar isn't exactly TTL (5V) it's higher.
You don't need the -3V to -12V voltage on most serial ports. Thats why I said you could get away with just a resistor. In worst case, it won't work, but you won't damage anything as the sensor bar output voltage will never exceed 12V.
Some usb to serial dongle are terminated on wires instead of a DB9 connector.
Those usually expect TTL 5V or 3V3 signals, and the signals are inverted compared to the RS232 V24 signal levels.
So we are talking about the same thingI was talking about connecting it to a serial port, not an usb port. If you don't have a serial port on your pc you can use an usb to serial converter. Ftdi and prolific are 2 brands that make chipsets and dongles for this purpose. prolific is found in all kind of brands of such devices. A serial port is usually a db9 male connector. It has RXD on pin 2 and GND on pin 5.
A max232 converts from TTL to RS232 V24. The output from the sensorbar isn't exactly TTL (5V) it's higher.
You don't need the -3V to -12V voltage on most serial ports. Thats why I said you could get away with just a resistor. In worst case, it won't work, but you won't damage anything as the sensor bar output voltage will never exceed 12V.
Some usb to serial dongle are terminated on wires instead of a DB9 connector.
Those usually expect TTL 5V or 3V3 signals, and the signals are inverted compared to the RS232 V24 signal levels.
Doesn't seem to be this...Yeah, all I know is that the discussion brought this to my mind. http://twitpic.com/bjklgk