DistantStar001 Posted July 19, 2018 Share Posted July 19, 2018 (edited) I'm trying to get ADTPro to connect to my //e via super serial card from my mac, but I haven't had any luck. I've tried using multiple computers, but my principle is a MacBook Pro, running Mac OS X v. 10.13. When I start ADTPro, and click the serial button, I get the error in the first image. When I go to configure the serial connection I get the options displayed in the second image (which is to say none). I've tried installing this on an older MacBook running 10.6, and I do get 4 options, but all of them have the word "bluetooth" in the identification, and none of them seem to do anything. I've looked this up multiple times, and even followed the Install, and Read Me instructions in the rxtx file (dragging RXTXcomm.jar, and librxtxSerial.jnilib to /Library/Java/Extensions), and got nothing. In fact, when I did this on 10.6, I got the same errors as on 10.13. What am I doing wrong? Edited July 19, 2018 by DistantStar001 Quote Link to comment Share on other sites More sharing options...
Osgeld Posted July 19, 2018 Share Posted July 19, 2018 (edited) Last time I messed with it I had to use an older version of java Now keep in mind that was like 3 years ago Side note rxtx has caused me so much pain in my arse over the years I hate it Edited July 19, 2018 by Osgeld Quote Link to comment Share on other sites More sharing options...
DistantStar001 Posted July 19, 2018 Author Share Posted July 19, 2018 What version of Java? Quote Link to comment Share on other sites More sharing options...
Osgeld Posted July 19, 2018 Share Posted July 19, 2018 like 6 but again it was a while ago Quote Link to comment Share on other sites More sharing options...
DistantStar001 Posted July 20, 2018 Author Share Posted July 20, 2018 I think that's what I have. How did you solve the rxtx issue? Quote Link to comment Share on other sites More sharing options...
Osgeld Posted July 20, 2018 Share Posted July 20, 2018 heck if I remember, I would have to sit down and fiddle with it again and even then I only have winders and linux Quote Link to comment Share on other sites More sharing options...
david__schmidt Posted July 23, 2018 Share Posted July 23, 2018 (edited) Don't use the app launcher - use the adtpro.command file instead. (And don't move the RXTX files around, either - you will want to undo whatever you did there.) I'm making an assumption that 1) you have a USB-serial adapter plugged in to your Mac, and 2) it's got the correct driver installed so it's visible to the system. Edited July 23, 2018 by david__schmidt Quote Link to comment Share on other sites More sharing options...
DistantStar001 Posted July 23, 2018 Author Share Posted July 23, 2018 Your assumptions are correct, and I've removed the files, so everything's back where it was. However, while I can see the USB-serial adaptor in my system profiler, it's still not visible to ADTPro. My options appear to be /dev/cu.Bluetooth-Incomming-Port, and /dev/tty.Bluetooth-Incomming-Port. Launching from ADTPro.command did help, I think, as I no longer get the first error message when I click the serial button. Quote Link to comment Share on other sites More sharing options...
david__schmidt Posted July 23, 2018 Share Posted July 23, 2018 What's the USB device's name that shows in the profiler? Quote Link to comment Share on other sites More sharing options...
DistantStar001 Posted July 23, 2018 Author Share Posted July 23, 2018 Edgeport/1: Product ID: 0x0240 Vendor ID: 0x1608 (Inside Out Networks) Version: 0.01 Serial Number: I43801745-0 Speed: Up to 12 Mb/sec Manufacturer: Inside Out Networks Location ID: 0x14100000 / 25 Current Available (mA): 500 Extra Operating Current (mA): 0 Quote Link to comment Share on other sites More sharing options...
DistantStar001 Posted July 23, 2018 Author Share Posted July 23, 2018 (edited) I have another, but it doesn't seem to make a difference. USB-Serial Controller: Product ID: 0x2008 Vendor ID: 0x0557 (ATEN International Co. Ltd.) Version: 3.00 Speed: Up to 12 Mb/sec Manufacturer: Prolific Technology Inc. Location ID: 0x14200000 / 26 Current Available (mA): 500 Current Required (mA): 100 Extra Operating Current (mA): 0 Edited July 23, 2018 by DistantStar001 Quote Link to comment Share on other sites More sharing options...
david__schmidt Posted July 23, 2018 Share Posted July 23, 2018 (edited) I don't see the Mac listed as a supported platform (i.e. for drivers) on Digi's documentation for the Edgeport set of products. Are you sure you've got drivers installed for either device you have plugged in? It's a separate step you have to explicitly do in the Mac world. Edited July 23, 2018 by david__schmidt Quote Link to comment Share on other sites More sharing options...
DistantStar001 Posted July 23, 2018 Author Share Posted July 23, 2018 No, but I think I managed to find the driver for the generic one. I now get two more options: /dev/tty.UC-232AC, and /dev/cu.UC-232AC. Quote Link to comment Share on other sites More sharing options...
david__schmidt Posted July 23, 2018 Share Posted July 23, 2018 Either of those could work; there's no reason to pick one over the other. Prolific has historically been poorly cloned and drivers are notoriously bad on a Mac, but that might work for you. Quote Link to comment Share on other sites More sharing options...
DistantStar001 Posted July 23, 2018 Author Share Posted July 23, 2018 Neither did, and I think that the driver is causing a conflict in High Sierra. ADTPro locks up when I try to switch between them, and won't quit when I tell it to. Even a force quit doesn't help. I've had to restart my mac three times, and I had to force a shutdown to do it. Quote Link to comment Share on other sites More sharing options...
david__schmidt Posted July 23, 2018 Share Posted July 23, 2018 Yep, that's consistent with lots of other Mac users. FTDI-based USB adapters are the way to go. 1 Quote Link to comment Share on other sites More sharing options...
DistantStar001 Posted July 23, 2018 Author Share Posted July 23, 2018 (edited) Alright, I'll have to get one. Thanks. Also, how do I get rid of this driver? Edited July 23, 2018 by DistantStar001 Quote Link to comment Share on other sites More sharing options...
david__schmidt Posted July 24, 2018 Share Posted July 24, 2018 Find and remove the .kext file it laid down... I'm not an expert on where that is exactly, but that's the extent of it. It's likely got some relationship with the name in the profiler. Quote Link to comment Share on other sites More sharing options...
DistantStar001 Posted July 24, 2018 Author Share Posted July 24, 2018 Thanks. Quote Link to comment Share on other sites More sharing options...
Like us on Facebook
Follow us on Twitter
AtariAge on Instagram
Watch us on YouTube
Chat on Discord
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.