GUN4IR - The Ultimate 4 Points Lightgun System

Main > Lightguns

<< < (201/227) > >>

Ugo:

--- Quote from: pacooka on October 04, 2022, 07:29:41 am ---Found this Chinese supplier for the Camera, is this the right part?
https://www.chxchips.com/en/dfrobot_SEN0158.html

--- End quote ---

Yes, that's the right part number. How did you find this website?
Are you sure it's not a scam? Especially how it says it'll ship in 24hrs. lol

TapeWormInYourGut:
It's probably a valid supplier, but Chinese suppliers on Ebay usually estimate about 1 month shipping on products. It's probably 24 hours to ship it, but then 3-4 weeks to actually receive it.

RandyT:

--- Quote from: 1942 on September 22, 2022, 01:39:26 am ---I am wondering if the SDA and SCL on the teensy/micro need a 5v communication signal but the camera module only communicates using 3.3V? I have checked the output of the SDA and SCL without the camera connected with an oscilloscope and it is showing a peak to peak of 5.2V, but the camera only has 3.3 V.

Has anyone else been able to get a Wii camera to work as shown in the (attached) diagram? Or should there be a I2C bus voltage converter shield in between?

--- End quote ---

If you are seeing 5v+ on the data lines, you may have cooked the camera(s). Technically, the pull-ups to the 3.3v rail should provide the 3.3v high signal levels, but that diagram is a little spooky. Not because it won't work, but because of the possibility that the data pins on the MCU may not always be set to open-drain inputs with internal pull-ups disabled. This could happen if there is a code/programming issue, or user error (wiring to the wrong pin, etc.) Again, if you are seeing 5v on the data lines, this would seem to be the case as the only other way you should see that level is if your 3.3v rail isn't really 3.3v.

There's also the I2C V4 spec which calls out a 30% and 70% of VDD for the low and high levels respectively. 70% of 5v = 3.5v, so technically, delivering 3.3v to an 5v device may not be sufficient. However, at the end of the day, you are still just connected to an I/O pin of an MCU, so those rules should apply unless there is some additional circuitry which comes into play when the pins are used for serial communication. The only way to know is to look at the datasheet for the MCU and/or the carrier PCB.

JayBee:

--- Quote from: TimeCrisis on September 01, 2022, 02:50:51 pm ---@JayBee

can you not add a button on the gun like the arcadeguns mini button, it is much better as a reload button in time crisis than having it at the side.

--- End quote ---
The fully feature gun I am preparing will have a ton of easily accessible buttons, but I will also have a polling for users suggestions and wish list for the final design. I want it to be a lightgun perfectly tailored to everyone's need ;)

--- Quote from: 1942 on September 22, 2022, 01:39:26 am ---Hi all, I am trying to get a Wii IR camera to work with either a Teensy 2.0 or the Arduino Micro, but no luck so far. I have followed JB's instructions and have been able to get all buttons, LED colours, rumble and solenoid working using the test app. However the camera does not pick anything up either in the test screen or the calibration screen.

I have tried trouble shooting by doing the following:

Reflash the teensy board (done)
Tested continuity and all connections (done)
Try different teensy board (done)
Try an arduino micro board (done)
Try a different pullup resistor value (33K and 2K7) on the camera module. - done
Try a different camera module –pulled out of another Wiimote - done
Try another 3.3v supply to the camera in case there is not enough amps from the controller– done used a bench power supply
Try different LEDs - done, I even rigged up two Wii sensor bars in case the LEDs are dodgy or the wrong wavelength
Try on a different windows computer – done on windows 10 and windows 7
Tested the output of the crystal is 24Mhz – tested using oscilloscope ok
:banghead:

I am wondering if the SDA and SCL on the teensy/micro need a 5v communication signal but the camera module only communicates using 3.3V? I have checked the output of the SDA and SCL without the camera connected with an oscilloscope and it is showing a peak to peak of 5.2V, but the camera only has 3.3 V.

Has anyone else been able to get a Wii camera to work as shown in the (attached) diagram? Or should there be a I2C bus voltage converter shield in between?

Thanks,
Steve

--- End quote ---
Sorry for the late reply.
I2C is an active low type of signal, so it's working perfectly fine in 3.3v, 5v might damage the cam. Everything on the cam side has to be 3.3v, including the oscillator.
Please double check everything in the circuit, oscillator, continuity, shorts... as those cams are very sensitive to any small issues.
You can also join the Discord server, where we will be able to help you more easily.

--- Quote from: RandyT on October 05, 2022, 03:38:38 pm ---If you are seeing 5v+ on the data lines, you may have cooked the camera(s). Technically, the pull-ups to the 3.3v rail should provide the 3.3v high signal levels, but that diagram is a little spooky. Not because it won't work, but because of the possibility that the data pins on the MCU may not always be set to open-drain inputs with internal pull-ups disabled. This could happen if there is a code/programming issue, or user error (wiring to the wrong pin, etc.) Again, if you are seeing 5v on the data lines, this would seem to be the case as the only other way you should see that level is if your 3.3v rail isn't really 3.3v.

There's also the I2C V4 spec which calls out a 30% and 70% of VDD for the low and high levels respectively. 70% of 5v = 3.5v, so technically, delivering 3.3v to an 5v device may not be sufficient. However, at the end of the day, you are still just connected to an I/O pin of an MCU, so those rules should apply unless there is some additional circuitry which comes into play when the pins are used for serial communication. The only way to know is to look at the datasheet for the MCU and/or the carrier PCB.

--- End quote ---
By default (when not set up), those lines are always left as floating, so if the lines are properly pulled up to 3.3v with the resistors, they should always be on 3.3v, never 5v. Same when active as I2C, they aren't pulling up to anything, they are either floaty on state high (and rely on the external pullup), or pulled to gnd on state low, so that it works with any device voltage. The state high threshold on that MCU I think is between 1 and 2v.

RandyT:

--- Quote from: JayBee on October 05, 2022, 10:52:47 pm ---By default (when not set up), those lines are always left as floating, so if the lines are properly pulled up to 3.3v with the resistors, they should always be on 3.3v, never 5v. Same when active as I2C, they aren't pulling up to anything, they are either floaty on state high (and rely on the external pullup), or pulled to gnd on state low, so that it works with any device voltage. The state high threshold on that MCU I think is between 1 and 2v.

--- End quote ---

I understand all of that and suspected as much about the MCU levels. But there is a real-world situation which could end in a dead or damaged Wii camera every time.

What if a user has an Arduino lying around (who doesn't) which has been used previously for tinkering and has some other code present which has one of those pins set up as an output already and set to high level, or as an input with internal pullups enabled (pretty much common for a switch)? If they build the circuit first and then apply power to program the arduino, 5v will be connected to the data pins of the Wii camera.

So with that particular circuit, it is absolutely imperative that the board is programmed and verified to be working properly prior to attaching it to the rest of the circuit to avoid possible damage.

That's why I stated that it will work but was a little spooky.

Navigation

 Message Index

Go to full version