Jump to content

Dropcheck

Members
  • Content Count

    1,652
  • Joined

  • Last visited

Community Reputation

1,187 Excellent

2 Followers

About Dropcheck

  • Rank
    Stargunner

Contact / Social Media

Profile Information

  • Gender
    Female
  • Location
    Stigler, OK

Recent Profile Visitors

17,366 profile views
  1. Yes. Although I don't know if you can completely blame the 1088XEL SIO. There's also some other issues with the Fujinet regardless of what Atari computer you connect it too. Right now if you turn off the Fujinet using its own power switch, you often lose the pass through of SIO signals. So if for some reason the Fujinet is not playing nice with other SIO devices in your chain, you're only option is to completely physically disconnect it from the chain. They are working on a fix for that as I understand.
  2. The SIO-Aux only exposes 5 of the 12 needed signals for the Fujinet. It's not a simple cut and paste operation. You definitely would not like esthetics either inside or outside. Your best bet would be to use the external version of the Fujinet with a short SIO cable.
  3. Unfortunately the Fujinet requires quite a bit more circuitry and would not easily fit on the 1088XLD I/O ModSystem.
  4. The 1088XEL and 1088XLD are two very different animals. Both require the U1M and UAV boards to function in it's basic configuration. If you want to beef up your video output then you can opt for the Sophia or VBXE boards, but you will need to have a monitor that supports their output. Both the 1088XEL/XLD have the CF3 Dual CF adapters. The MultiSIO Internal Board is for the 1088XLD only. If you aren't soldering or assembling anything yourself, then the PIC-Stick programmer is not needed. The advantage of having either the XEL/XLD assembled for you is that it's all tested and verified working before shipment to you. Unless the postal service/USP service dumps it upside down or from 10-15 feet, you should be able to do a 'things loose and moving around inside' quick test and be up and running within minutes of arrival. I've worked with TBA in developing some of their offerings and can vouch for their professionalism.
  5. TTL is a logic level family, usually used to describe most older chip families even if they have a SMT as well as a DIP/SIP footprint. The Atari line of computers are most definitely in that logic family as are almost all chips powered by 5V. 'A TTL input signal is defined as "low" when between 0 V and 0.8 V with respect to the ground terminal, and "high" when between 2 V and VCC (5 V)' A bare ESP32 module operates on 3.3V, so is not directly TTL compatible. It has usually been depicted in most tutorials and youtube videos as needing logic level converters to interface with TTL logic, such as the UNO boards and other +5V devices. The RN used in the Fujinet provides a very simplistic level converter, but it's not really smart enough to handle power on/off, and when the Fujinet power is turned off acts as a load on the SIO bus, breaking the passthrough feature. It also doesn't isolate against feedback power. As far as the audio line needing to be filtered/logic level converted...... The original schematic does not have the signal going through the RN to drop voltage, instead it goes through C3/R5. I'm assuming that those two parts are doing the same thing as the RN to drop the voltage to something the ESP32 can handle. I'm not an engineer, so all I can say is that it's very possible it will need to handled by an additional isolate/buffer chip line as well. Which unfortunately takes us back to a two chip solution. Or maybe one chip and something discrete to handle the Audio In line. There are far better electronics savvy members than me that can weight in here to correct my assessment if I am materially wrong.
  6. Would this one chip solution work? The 3.3v power to the ESP32 is already switched on/off. With the R1 resistor holding the OE pin in a low state until the 3.3v is high enough and stable, the outputs are held in a high Z state, effectively disconnecting the ESP32 from the SIO bus.
  7. I see connection for the Audio, but not for Mtrl_Ctrl. On the original schematic Audio is not run through the RN, but the Mtrl_Ctrl signal is. Is that a mistake, a senior moment?
  8. At the risk of irritating people, I recommend taking these posts on recompiling the current firmware for a deprecated hardware version to the proper thread. This thread deals with the hardware, not even firmware, of the current version. Perhaps the sysop can move them to the right thread. 😔
  9. I'm not an engineer, but if you are referring to the strange SIO loading stutter, it sounds like a buffer delayed sound. Maybe the Fujinet isn't actually separated from the bus. Could the 07 chip actually be buffering both the Fujinet and the second SIO device? On another topic..... what board assembler did you use to have the Fujinet pcbs assembled?
  10. FYI I have a few items on my site that I am closing out. These items are on sale. Once they are gone I do not plan to stock or build any more. Super MMU Adapter Reimaged Ramrod XL ATX12V 1088XEL Power Adapter
  11. Hi Mozzwald, I still see only v1.0 board and schematics released. I went looking for the buffer chip you indicated on an earlier snap of the new 1.1 schematics and I am not finding that part #. Am I reading it right? Is that a Q or a G?
  12. I want to keep the touch screen, just swap out the board.
  13. I'm wondering what is needed to use an Arduino Pro Mini board instead of the UNO. Same Atmega 328P chip. Assuming I matched the pinout of the UNO to the pinout of the Pro Mini. I would have to use an external USB to UART board to program it.
×
×
  • Create New...