Jump to content

displaced

New Members
  • Content Count

    53
  • Joined

  • Last visited

Community Reputation

45 Excellent

About displaced

  • Rank
    Star Raider

Recent Profile Visitors

1,287 profile views
  1. I did the same with my XEGS in the UK last year. Took a good couple of weeks but there was a noticeable improvement!
  2. In case it helps, the buzzing/hissing from around the processors is normal - my fully-working Jag does the same - and always has since I bought it on release. In fact, it’s probably a good sign - shows activity!
  3. D’oh! I’d spotted this late last year - thought I’d treat myself for my 40th birthday (end of this month - Jan). Just seen the discontinuation announcement! Oh well - snoozing and losing and all that!
  4. I’ve got the code finished, with pin state changes being properly reflected on each Arduino via Bluetooth LE. Pins 1-4 on the Jag side set pins 1-4 on the controller, with all other pins operating in the other direction. Just soldering up the DB15HD plug and socket, plus the Arduino to some veroboard. Words can’t quite express how much I hate soldering a full DB15! On the subject of powering the Jag-side Arduino. Although they work fine with 5V on the VIN pin, the board’s regulator is indeed lowering the voltage on the digital pins to ~3.5V, which is too low for TTL. The Nano doc’s show that already-regulated power can be fed to the 5V pin, which bypasses the nano’s regulator. If the 5V on the controller port is stable enough for the Jaguar, it should be fine for the Nano, so I’ll switch to using that pin. Gives a stable 5V on the digital pins when running with the bench PSU.
  5. Hi Stephen, Like most of these ideas, it comes from my own desire. My Jaguar’s connected via an OSSC to a big TV that’s about 4 metres from where I sit, and I like to avoid extension cables if possible. On my breadboard right now two idle BLE-Nano boards are taking 20mA according to my bench PSU, so the jag’s port should power the ‘receiver’ Nano fine. The Nano has a VIN pin for power input which is regulated and accepts 6V to 20V. 5V may be a little low for that, but they’re behaving fine on the bench. On the controller side, I’d be happy with the jagpad’s lead shortened and plugged into a box containing the Nano, battery and charge controller. I could even forego the battery and power via Micro USB (my chair on the other side of the room has a USB multi-way charger beside it). Sure, it wouldn’t be wireless, but stowing away a 0.5m micro usb lead is neater than finding somewhere for 4 metres of 15-way cable that would otherwise be draped across the room. As for team-taps, I’m very unlikely to ever want one - pretty much just building this for my own convenience. And it gives me an excuse to play with some Arduinos and, if it all works out, design and 3D print some enclosures.
  6. Thanks, Zerosquare! All that makes sense. Slightly concerned about the team-tap bit, since if the jag and Arduino have differing ideas about pin directions, nastiness could happen. I don’t mind losing team-tap compatibility, so maybe I’ll use some diodes to prevent the jag outputting on pins that are nominally inputs. Im using Bluetooth 4.0 LE which apparently has massively better latency. I’m not expecting my simple approach to work, but I’ll start with it just to see how badly it doesn’t work (if that makes sense!). Then I’ll fiddle with state caching to see what happens. I want to try something similar with the simple CX40 joystick on my XEGS too. Perhaps I should start there to keep things simple!
  7. ure Hi! I have a couple of Arduino Nano boards with bluetooth which I'm eyeing for a project. Thought I'd mention it here in case it's a stupid idea... I was thinking I could connect one Nano to the Jaguar's controller port, and connect another Nano to a controller. Then, via Bluetooth, replicate the controller's signals to the Jag, essentially turning any Jaguar controller wireless. Now, technically there's nothing magic here. The Arduino code's quite straightforward. But I'm assuming that this won't work for reasons I don't yet know I've been researching how the Jag's controller works, since there's clearly more buttons than signal lines on the port. So it would appear that the connection is bidirectional - the Jag sets pins 1-4 to choose what group of buttons it wants to read, then reads their state on other pins. I'm not actually replicating a controller, rather, just trying to reflect the pin states between the two Arduinos over bluetooth -- so I don't really care about the nitty-gritty. So it would seem that the Jag-side Arduino should have pins 1-4 as inputs and the others as outputs, whilst the controller-side Arduino would have 1-4 as outputs and the others as inputs (to read from the controller). All I need to do is watch for changes on the signals and ping BT messages back and forth to reflect those changes on the other end. Has this been tried before? Is there a glaring reason why it won't work? If it does work, would anyone else be interested? (I'm imagining there being a little Arduino dongle that'll connect to and be powered by the Jag. Then, a little box with a DB15 socket for the controller to plug into, and a micro-USB for charging a battery for the controller-side nano. If it does work well, I could see if I could fit the 'duino and a battery pack inside the shell of the controller) [edit: The glaring issue I can foresee is lag. If the Jag sets pin1 and assumes it can scan other pins straight away to get button states, it may well not be happy about the delay introduced by bluetooth. The best way to find out is to try, I suppose!]
  8. Ah, superb -- thanks very much indeed! Didn't realise the ATR support depended on a driver supplied by U1MB - that bit of info makes what I'd been reading make more sense now. Knew I was missing something... At the moment I can't quite justify a U1MB purchase, even though it's objectively a very nifty bit of kit - especially after having just bought the XEGS and VBXE! Perhaps after some future payday. Cheers!
  9. Hi, I've read a load of threads here on this subject - just wanted to coalesce it here to make sure I've got the right end of the stick... The Aim Upgrade my SIDE2 firmware to the latest version on my 64K XEGS with VBXE The Problem SIDE2 firmware is supplied as an .ATR file. SIDELoader or SIDE2's SDX mode cannot work with ATR files/APT partitions because 64K isn't enough. A Solution? The VBXE can be flashed so that it provides 320K additional 'RAMBO' memory. So, my questions are: Is the above even vaguely correct, or utter nonsense? Could I switch the VBXE to provide RAM by upgrading it with an ATR via an SIO2PC cable? After doing that, would the SIDE2/SDX be able to use that RAM and allow ATR support? If so, could I then simply upgrade SIDE2 to the latest firmware using its own ATR support, or would that need loading via SIO2PC as well? Thanks for your help - I'm totally new to A8's beyond having a read through the SpartaDOS X manual and a little fiddling in BASIC (and my brain works on BBC Basic at that, not Atari Basic!)
  10. Partial to a bit of Neil Young too! When smartphones were new, I did stuff like film gigs... but ended up preferring to take a few photos, a minute or two of video, then just enjoy. It’s nice to imperfectly recall seeing everything than just remembering looking through the phone’s lens. There’s not quite room for a couch, instead there’s some IKEA seat with a footstool which is fantastic for falling asleep in whilst playing Elite I think the Lynx stand came from an Etsy shop - nice little clear acrylic display stand thing. It’s meant for the Lynx II but my Mk. I sits there fine! I’ll make sure I get those onto the CF card! the speakers are part of a 7.1 setup - far more than enough for the small room, but it was an absolute eBay bargain, including the amp. Mrs. Displaced and I had a fun road-trip from Kent to Devon to go pick that lot up! I’ve wired the audio out of the XEGS so that the mono signal goes to both L and R channels on the amp. The fact that both channels are identical doesn’t give the amp much to work with for its spatial effects. But setting it to all-speaker stereo sounds pretty good. I love hooking these old machines up to A/V gear that was the stuff of a madman’s dreams back when they were released. Having said that, I know there’s an authenticity to playing these old machines on contemporary CRTs. Especially when game graphics took advantage of interlacing and phosphor decay to produce particular effects. Personally though, I like to make using my old stuff every bit as convenient as playing Elite Dangerous or Battlefront II on my PC. ...and that’s my next project - turn some Arduino Nano boards into Bluetooth-to-Atari Joystick/Keyboard bridges. That’s going to be harder than I thought with the XEGS - might end up running a ribbon out from the motherboard so I can hook the Start/Option/Select/Reset lines up to the Arduino.
  11. Quite - can’t bear stretchy-vision on TV shows, films or games!
  12. Made up the mini-DIN to VGA cable and plugged it all in. I know this comes as no surprise to most of you, but as this is my first A8 and my first VBXE installation, I am well pleased with the video output quality! I've not put any games on my SIDE2 yet, but here's a quick pic of the XEGS's self-test menu on my TV. The XEGS goes to an Aten VS1601 16-port VGA switch. The output from that feeds an OSSC scan-converter. Then, HDMI to the TV. Now to obtain some software!
  13. Ah-ha! My genius (read: pokey-fingered) wife comes to the rescue again (after helping fix the Option switch). The smaller spring needs sits with its wide end around the bit of X-shaped plastic on the underside of the button. Then she noticed that the narrow-end of the spring was a bit out of shape. It's meant to sit on top of the metal post of the power switch without falling down it. Bent the narrow bit back, reassembled, and perfect! I'll take a few snaps for my other thread showing the finished article (and the amazing video output of the VBXE!)
  14. Hmmm -- well the XEGS's power button pushes a big metal mechanical switch, rather than the small black rubber-dome switches under the other XEGS buttons. So it feels quite different anyway. I've been scouring Google and Youtube for teardown pics/vids. No-one seems to remove the buttons, which is frustrating! I don't want to keep experimenting too much - the latches on the buttons which hold them in place are likely to be a bit brittle with age and I'd hate for one to snap. I think I'll keep my fingers crossed that another XEGS owner wouldn't mind confirming how their machine's power button is installed. That, or keep looking at it and wait for inspiration! Thanks for your help though guys... It's a bit funny that I got through the ANTIC desoldering, VBXE install and RGB output install without any problems or breakage, but am falling down on a stupid button!
×
×
  • Create New...