Search
310 results for “timixretroplays”
-
And finally, the whole shebang - an #Arduino Pro Micro clone, my own custom dual #NES controller breakout with a #3DPrinting socket, and the #nanoDLA logic analyser ready to help me learn how to talk to a NES Four Score - and later, to help document how to do the same with a NES Satellite!
This is the confluence of a decade plus of hobby learning and making.
A note mainly for myself: CLK and LAT are pins 5 and 6, and channels 0 and 1; P1D0 is pin 7 and channel 2, P2D0 is pin 8 and channel 3.
-
Not a lot of free project time the last week or so, but the simple-as-anything breakout I made for my nanoDLA logic analysers arrived. It's just a board that lets you plug a nanoDLA directly into a standard breadboard and access all ten of its channels at once, without having jumper wires untidily trailing to it off the board.
Oh, and that 3D printed NES socket works flawlessly. Next week I'll make a dual socket version to talk to the Four Score properly.
-
Huh, I think #Rhino3D's "Display modes" will do what I want: https://www.rhino3d.com/features/display/display-modes/
Looks like they're even (almost) all in my super old version of Rhino, so all I'll have to do is model the plugs and sockets to a reasonable degree of accuracy, SetDisplayMode to something pretty, then save as an image and label the pins separately.
I'm also liking Ghosted mode for showing the internal structure of a complex shape rather than getting it from multiple angles, too.
-
Here's how multiple #GravisGrIP controllers work, daisy-chained to a single gameport. Each digital device uses two button lines to flash their signals to the computer, and the Y-adapters on these simply rewire the second controller's B1/B2 lines to B3/B4 on the gameport - the GrIP driver looked at both pairs of button signals and supported different controllers simultaneously.
PulseView here shows the Blackhawk Digital's clock and data on D0/D1, and the slower GamePad Pro on D2/D3. #retrogaming
-
I have been fortunate enough to collect two amazing bits of rare, unusual and near-mint #Sega #MegaDrive / #MegaCD hardware this week. The first is the "Team Player", which let you use up to four controllers on a single system.
Of the six positions on that slide switch, A B C and D picked which of the four controllers would be passed through to the console, so you could flip seamlessly between a 3- or 6-button controller, or a mouse.
Mouse? Yeah, hang on - I'll get to that. 🧵
-
First proper look at some more Advanced Gravis controllers with my #nanoDLA logic analyser.
Here's the original Gravis XTerminator gamepad. It's got an analog stick, a D-pad, a ton of action buttons, analog and digital shoulder buttons, a POV hat and a throttle slider - all of which is made to work on the 15-pin gameport with the Gravis GrIP digital protocol.
Check out that gameport plug - I had trouble with this pad initially because I'd wired up +5V and GND to missing pins in the connector.
-
First proper look at some more Advanced Gravis controllers with my #nanoDLA logic analyser.
Here's the original Gravis XTerminator gamepad. It's got an analog stick, a D-pad, a ton of action buttons, analog and digital shoulder buttons, a POV hat and a throttle slider - all of which is made to work on the 15-pin gameport with the Gravis GrIP digital protocol.
Check out that gameport plug - I had trouble with this pad initially because I'd wired up +5V and GND to missing pins in the connector.
-
First proper look at some more Advanced Gravis controllers with my #nanoDLA logic analyser.
Here's the original Gravis XTerminator gamepad. It's got an analog stick, a D-pad, a ton of action buttons, analog and digital shoulder buttons, a POV hat and a throttle slider - all of which is made to work on the 15-pin gameport with the Gravis GrIP digital protocol.
Check out that gameport plug - I had trouble with this pad initially because I'd wired up +5V and GND to missing pins in the connector.
-
First proper look at some more Advanced Gravis controllers with my #nanoDLA logic analyser.
Here's the original Gravis XTerminator gamepad. It's got an analog stick, a D-pad, a ton of action buttons, analog and digital shoulder buttons, a POV hat and a throttle slider - all of which is made to work on the 15-pin gameport with the Gravis GrIP digital protocol.
Check out that gameport plug - I had trouble with this pad initially because I'd wired up +5V and GND to missing pins in the connector.
-
First proper look at some more Advanced Gravis controllers with my #nanoDLA logic analyser.
Here's the original Gravis XTerminator gamepad. It's got an analog stick, a D-pad, a ton of action buttons, analog and digital shoulder buttons, a POV hat and a throttle slider - all of which is made to work on the 15-pin gameport with the Gravis GrIP digital protocol.
Check out that gameport plug - I had trouble with this pad initially because I'd wired up +5V and GND to missing pins in the connector.
-
Pausing the project here for a bit. With seven pins dedicated to reading a #SEGA controller, I can use the 8th pin as a signal from the #Arduino not just to indicate when a certain thing is happening, but also as a trigger in #PulseView to start capturing data.
Are you an Arduino/generally a microcontroller or electronics hobbyist? You should go buy a #nanoDLA logic analyser - for a few bucks you can easily visualise exactly what's going on with your I/O signals. Solid recommendation from me.
-
Pausing the project here for a bit. With seven pins dedicated to reading a #SEGA controller, I can use the 8th pin as a signal from the #Arduino not just to indicate when a certain thing is happening, but also as a trigger in #PulseView to start capturing data.
Are you an Arduino/generally a microcontroller or electronics hobbyist? You should go buy a #nanoDLA logic analyser - for a few bucks you can easily visualise exactly what's going on with your I/O signals. Solid recommendation from me.
-
Pausing the project here for a bit. With seven pins dedicated to reading a #SEGA controller, I can use the 8th pin as a signal from the #Arduino not just to indicate when a certain thing is happening, but also as a trigger in #PulseView to start capturing data.
Are you an Arduino/generally a microcontroller or electronics hobbyist? You should go buy a #nanoDLA logic analyser - for a few bucks you can easily visualise exactly what's going on with your I/O signals. Solid recommendation from me.
-
Pausing the project here for a bit. With seven pins dedicated to reading a #SEGA controller, I can use the 8th pin as a signal from the #Arduino not just to indicate when a certain thing is happening, but also as a trigger in #PulseView to start capturing data.
Are you an Arduino/generally a microcontroller or electronics hobbyist? You should go buy a #nanoDLA logic analyser - for a few bucks you can easily visualise exactly what's going on with your I/O signals. Solid recommendation from me.
-
Pausing the project here for a bit. With seven pins dedicated to reading a #SEGA controller, I can use the 8th pin as a signal from the #Arduino not just to indicate when a certain thing is happening, but also as a trigger in #PulseView to start capturing data.
Are you an Arduino/generally a microcontroller or electronics hobbyist? You should go buy a #nanoDLA logic analyser - for a few bucks you can easily visualise exactly what's going on with your I/O signals. Solid recommendation from me.
-
Tonight's setup - the SEGA controller is now hooked up to an #Arduino Pro Micro alongside the #nanoDLA. To start with I'm just flicking the signal line up and down every 200ms.
I know digitalWrite can make changes on the order of single-digit microseconds - I wonder how fast a Megadrive controller can react?
-
Tonight's setup - the SEGA controller is now hooked up to an #Arduino Pro Micro alongside the #nanoDLA. To start with I'm just flicking the signal line up and down every 200ms.
I know digitalWrite can make changes on the order of single-digit microseconds - I wonder how fast a Megadrive controller can react?
-
Tonight's setup - the SEGA controller is now hooked up to an #Arduino Pro Micro alongside the #nanoDLA. To start with I'm just flicking the signal line up and down every 200ms.
I know digitalWrite can make changes on the order of single-digit microseconds - I wonder how fast a Megadrive controller can react?
-
Tonight's setup - the SEGA controller is now hooked up to an #Arduino Pro Micro alongside the #nanoDLA. To start with I'm just flicking the signal line up and down every 200ms.
I know digitalWrite can make changes on the order of single-digit microseconds - I wonder how fast a Megadrive controller can react?
-
Tonight's setup - the SEGA controller is now hooked up to an #Arduino Pro Micro alongside the #nanoDLA. To start with I'm just flicking the signal line up and down every 200ms.
I know digitalWrite can make changes on the order of single-digit microseconds - I wonder how fast a Megadrive controller can react?
-
Six days later, a #nanoDLA 1.3 has arrived. It cost me AU$10.54 including postage. It's an open source logic analyser, documentation in English here: https://github.com/wuxx/nanoDLA/blob/master/README_en.md
This thread will document my first explorative experiences with it and sigrok's #PulseView, an open source logic analyser software package and the recommended counterpart to the nanoDLA: https://sigrok.org/wiki/PulseView
-
Six days later, a #nanoDLA 1.3 has arrived. It cost me AU$10.54 including postage. It's an open source logic analyser, documentation in English here: https://github.com/wuxx/nanoDLA/blob/master/README_en.md
This thread will document my first explorative experiences with it and sigrok's #PulseView, an open source logic analyser software package and the recommended counterpart to the nanoDLA: https://sigrok.org/wiki/PulseView
-
Six days later, a #nanoDLA 1.3 has arrived. It cost me AU$10.54 including postage. It's an open source logic analyser, documentation in English here: https://github.com/wuxx/nanoDLA/blob/master/README_en.md
This thread will document my first explorative experiences with it and sigrok's #PulseView, an open source logic analyser software package and the recommended counterpart to the nanoDLA: https://sigrok.org/wiki/PulseView
-
Six days later, a #nanoDLA 1.3 has arrived. It cost me AU$10.54 including postage. It's an open source logic analyser, documentation in English here: https://github.com/wuxx/nanoDLA/blob/master/README_en.md
This thread will document my first explorative experiences with it and sigrok's #PulseView, an open source logic analyser software package and the recommended counterpart to the nanoDLA: https://sigrok.org/wiki/PulseView
-
Six days later, a #nanoDLA 1.3 has arrived. It cost me AU$10.54 including postage. It's an open source logic analyser, documentation in English here: https://github.com/wuxx/nanoDLA/blob/master/README_en.md
This thread will document my first explorative experiences with it and sigrok's #PulseView, an open source logic analyser software package and the recommended counterpart to the nanoDLA: https://sigrok.org/wiki/PulseView
-
Do you own a #Toshiba #Libretto #50CT with a password-locked BIOS? The guy who 3D prints replacement cases for vintage laptops took to a 50CT recently, and designed a special circuit board that slots into its dock connector to reset the password.
You can buy one, or download the files and get one made: https://github.com/hrushka/LibrettyKey
His video on the process of designing everything is here: https://www.youtube.com/watch?v=AdeswJreJ98
Boosts are love for keeping old hardware alive.
-
#Fritzing has never felt *completely* comfortable to me - it somehow feels both overcomplicated and underpowered for making simple boards like this - but it remains the only PCB design tool I've ever been able to open and just make a thing in without poring over documentation about vias and footprints. You drag and drop stuff, you fettle with the exact positions of things by slightly changing numbers, and you can export everything to a file PCB makers understand - and that works for me.
-
I see #Fritzing still runs slow as a wet week once you get a few components in PCB view - it goes from being super snappy to only highlighting what part is under your cursor a few times a second, making it feel super laggy when adding wires or new bits and bobs. These aren't four-layer motherboards or anything that complex either - just breakout boards and little adapter's for stuff.
Lowering the grid resolution and turning the visual grid off helps, but CPU still shoots up just mousing around.
-
A few-months-in update to my #Sony #WH1000XM5 headphones, and: for my use cases, I dearly wish I'd bought something else.
Pros: Incredible sound quality (both out and in, I've had people pause in meetings to compliment how good my voice sounds), great battery life, unbelievable comfort (I could wear these for 8 hours a day), can connect to and seamlessly switch between two devices (crucial, my work day is a mix of music on my phone and work meetings).
But the cons. Oh, the cons. 🧵
-
I wish all
Summernats experiencees
A very
hearing protectionThis post might seem early, but the guys up the road are already dyno'ing something that sounds like it could bring about the end of the world if they pressed the wrong button on it, and it's never too early to start looking after your body.