What's new

Naomi Pi 'WiPi Netbooter' - compatible with Pi 3&4

I’m using OpenJVS, no physical i/o board, with your AIO V6 image file. The analog controls seem to work with Naomi 1 games and Club Kart (which is a Naomi 2 game). However, when I try any initial d game, it fails. I go back to Crazy Taxi and that works.
 
OK, gotcha, and do you have the card reader emulator enabled and in auto mode? Also, are you using an RS485 adaptor that has the FTDI chipset or another?
 
Last edited:
Could you try changing the card emulator to manual then netboot the game, you'll obviously get a card reader r/w error on start up but then go into the service menu and see if the JVS IO is detected or not, just testing a theory that the card emulator script is interfering with openjvs
 
Could you try changing the card emulator to manual then netboot the game, you'll obviously get a card reader r/w error on start up but then go into the service menu and see if the JVS IO is detected or not, just testing a theory that the card emulator script is interfering with openjvs
You’re absolutely correct on your theory!
Went into service via the controller, which is also a good sign. Verified analog controls working!
682A52B8-A1C4-474D-80D3-D4F51098EECD.jpeg1EE8F74B-FACC-4252-914C-1B574DB5DB0D.jpeg
 
I think maybe the chipset of your adaptor isn't FTDI even though that's what you bought, I have a udev rule that looks for FTDI and assigns a link called COM1 that points to the correct /dev/ttyUSB port - that way the openjvs config file doesn't need to be changed. Then I run a script that follows the link if it exists and assigns the first other /dev/ttyUSB it finds for the card emulator. So it's likely that the card emulator is crashing openjvs by grabbing the port it's using. You can manually override it by changing the value in /sbin/piforce/webforce.py, it's at the bottom in the else emuport statement, change the port to /dev/ttyUSB1 and see if that fixes it
 
Going back to Initial D 3, I noticed that after 30 min of attract mode (idle) the io gets dropped and this displays:
299B72B8-7D86-4C62-93CE-BDEA3E825AE8.jpeg
COM. Error occured
Between Naomi BD AND I/o bd.

Is this normal?
 
I think maybe the chipset of your adaptor isn't FTDI even though that's what you bought, I have a udev rule that looks for FTDI and assigns a link called COM1 that points to the correct /dev/ttyUSB port - that way the openjvs config file doesn't need to be changed. Then I run a script that follows the link if it exists and assigns the first other /dev/ttyUSB it finds for the card emulator. So it's likely that the card emulator is crashing openjvs by grabbing the port it's using. You can manually override it by changing the value in /sbin/piforce/webforce.py, it's at the bottom in the else emuport statement, change the port to /dev/ttyUSB1 and see if that fixes it
I ended up with the same adapter that I’ve seen on the forums and unfortunately got the same results.

After @mathewbeall explained to me that this is common, I ended up rebooting the pi, then netbooting Initial D 3 and it finally worked! He says that error comes up 1 out of 4 times. However, I noticed that the error:
COM. Error occured
Between Naomi BD AND I/o bd.
comes up after about 30 min during game play. I use a playstation 4 controller. However, there are the rs232, openjvs, and the card reader all plugged in at the same time and being powered by the naomi 2. We were wondering when the power drops it disconnects the openjvs i/o connection?

@mathewbeall was thinking of adding a powered usb to help keep stability with the pi?

Any clues on why it’s dropping?
 

Attachments

  • B231C67C-EBAE-433B-9B8E-AC4D88D87252.jpeg
    B231C67C-EBAE-433B-9B8E-AC4D88D87252.jpeg
    173.4 KB · Views: 121
  • 47CE6D81-97AA-4C5C-A3F3-FD88F22C279B.jpeg
    47CE6D81-97AA-4C5C-A3F3-FD88F22C279B.jpeg
    158.4 KB · Views: 120
  • 93E36A20-D3B2-4412-96B0-3ADD4C1785B1.jpeg
    93E36A20-D3B2-4412-96B0-3ADD4C1785B1.jpeg
    287.1 KB · Views: 112
  • A92EC01A-157C-4019-BC31-FA583248B4D2.jpeg
    A92EC01A-157C-4019-BC31-FA583248B4D2.jpeg
    173.6 KB · Views: 121
  • 0218F84B-40E1-49CA-87CD-C9039E53B0C0.jpeg
    0218F84B-40E1-49CA-87CD-C9039E53B0C0.jpeg
    178.8 KB · Views: 120
  • 2FB2130F-8A9C-48FE-A21B-3467B2802649.jpeg
    2FB2130F-8A9C-48FE-A21B-3467B2802649.jpeg
    124.6 KB · Views: 119
Last edited:
I would like to add a oled to mine and mount it on my control panel so it needs to be able to be separate from the pi using a long cable
Can someone recommend what to get to make this happen?
Thanks
 
Do you mean a small touchscreen LCD? should be as simple as a ribbon cable extender to run from the GPIO although the supported screens for WiPi use SPI and I'm not sure what the maximum cable length you can go to. Other option is you keep it attached to the Pi and extend whatever other cables you need to.

If you want to try an extension cable, this should do the trick: https://www.ebay.co.uk/itm/272698894047

If I got totally the wrong end of the stick and you meant an LED/LCD/OLED display screen or similar just use HDMI
 
@kuze
Yes they are not the best at all - just tried one - awful
Is a regular LCD screen still supported?
If so which one would be best to use to attach the Rpi and fit nice in a case
Thanks
 
I ended up with the same adapter that I’ve seen on the forums and unfortunately got the same results.

After @mathewbeall explained to me that this is common, I ended up rebooting the pi, then netbooting Initial D 3 and it finally worked! He says that error comes up 1 out of 4 times. However, I noticed that the error:
COM. Error occured
Between Naomi BD AND I/o bd.
comes up after about 30 min during game play. I use a playstation 4 controller. However, there are the rs232, openjvs, and the card reader all plugged in at the same time and being powered by the naomi 2. We were wondering when the power drops it disconnects the openjvs i/o connection?

@mathewbeall was thinking of adding a powered usb to help keep stability with the pi?

Any clues on why it’s dropping?

UPDATE: Unless I'm missing something, OpenJVS communication for the I/O will be dropped on Initial D Arcade games if using anything under Raspberry Pi 4.

I tried using the same 5.1V 3.2A that powered the Pi 4 on the Pi 3, with a USB-C to Micro USB adapter, but the com. error showed up after 30 min.
 
Back
Top