Maxstream Pkg U Drivers For Mac
Need help with Xbee config on a Mac Forum 2005-2010 (read only) Interfacing Need help with Xbee config on a Mac (2/3) dorseykrofft1: same here! (kinda) Powerbook G4, OSX 10.5.8 running VPC 7, Windows 2000 BASE - XBee 1mW Chip Antenna on an XBee Explorer USB (connected to mac) REMOTE - XBee 1mW Chip Antenna on an XBee Explorer Regulated (connected to battery-powered Arduino Duemilanove sitting on the table) XBee 1mW Chip XBee Explorer USB XBee Explorer Regulated 1. Picked up the PKG-U USB Drivers for Windows here: as instructed from the XCTU page here: and got XCTU running just fine. Did a basic configuration on both XBees using the Explorer USB. BUT mac wouldn't recognize (in Terminal - typed 'ls /dev/tty.' and nothing, NO XBee in the list) 3.
I thought to myself, 'oh! Didn't i see drivers for the mac on that same page?'
So i got the mac drivers from same url in step 1 above. Installed, but STILL no mac recognition. just in case, i checked XCTU in Windows again.
Still working! SO (missing the 'Troubleshooting' note at the BOTTOM of the ReadMe.txt file that warned of using ONLY the drivers from the link in step 1 above), i went ahead to the FTDI site to download a more recent driver here: and installed. i'm guessing this is where things went wonky for XCTU. So DON'T DO IT if you still want to be able to configure your XBees using XCTU in Windows!
Step 4 didn't work right away, but i found a little trick here: and, VOILA! Mac can see the XBee in Terminal! BUT now i can't communicate with the XBee in Windows XCTU!!! So i'm thinking it's kind of a case of dueling drivers. Something got mucked up on the mac side after installing the drivers from the FTDI site. THANKS ahead of time for ANY response! It may help some of you with newer macs: dorseykrofft1: UPDATE soooooooo.
I gave up trying to make this seamless, so here's the dirty: ON THE MAC 1. Re-installed the mac drivers from the digi site: NOTE: installing this version will force a restart. Use this opportunity to unplug ANY and ALL usb devices connected to your machine. (this is ONLY A THEORY) because when you try to install new usb devices in Windows 2000, it will automatically defer to Microsoft drivers if it can IN WINDOWS 2000 via VIRTUAL PC 7 1.
(with NO usb devices connected to my mac) i uninstalled ALL usb drivers using DEVICE MANAGER 2. I removed any/all usb drivers i had installed myself (from previous failures) using ADD/REMOVE PROGRAMS 3. I uninstalled all the usb devices using ADD/REMOVE HARDWARE (even if they aren't connected, they MAY show up here) NOTE: when you get the list of devices, be sure to click SHOW HIDDEN DEVICES.
This is where the USB SERIAL CONVERTER (shows up as a usb device) and the USB SERIAL PORT (COM 3) (shows up as a com port) that i've been so desperately seeking will be hiding out. Be sure to scroll ALL the way down and uninstall ALL usb devices (and that one com port). (unfortunately, ADD/REMOVE HARDWARE will only let you get rid of these one at a time, so you'll be opening this over and over until you've gotten rid of all the usb devices.
Plug in your XBee/XBee Explorer USB 5. Go to DEVICE MANAGER and under ACTION choose SCAN FOR HARDWARE CHANGES. It should detect your XBee/XBee Explorer USB and automatically open FOUND NEW HARDWARE WIZARD 6. When you are asked what you want the wizard to do, select SEARCH FOR A SUITABLE DRIVER FOR MY DEVICE (this is the default selection 7. On the next screen check only SPECIFY A LOCATION 8. Navigate to wherever you stored the windows drivers from the digi site (the link above) 9. Finish up installation as directed 10.
Once that's done, you will find another FOUND NEW HARDWARE WIZARD underneath. Repeat steps 5-9 as directed. I suspect it's because there are two new devices-in-one: USB SERIAL CONVERTER (the XBee Explorer USB )and USB SERIAL PORT (COM 3) (the XBee itself) NOTE: you may get a warning about overwriting an existing and newer version of the driver.
I went ahead and overwrote it, and it seemed to work fine. Check your work: give DEVICE MANAGER a few seconds to refresh itself. Expand PORTS - you should see SERIAL PORT (COM 3) added there expand UNIVERSAL SERIAL BUS CONTROLLERS - you should see USB HIGH SPEED SERIAL CONVERTER added there 12. Open XCTU, et voila! You should have access to SERIAL PORT (COM 3) and your Xbee for configuration NOTE: now it's safe to plug in your other usb devices if this doesn't work, i have no idea what to say.
Rinse and repeat? VERY IMPORTANT NOTE: before going back to work on the mac (which i guess you want to do).
BE SURE TO PROPERLY UNPLUG YOUR XBee/XBee Explorer USB DEVICE - strange: i've had to go though this a couple of times, and it randomly chose to either a) let me just pull the device out without procedure (meaning it's hot-swappable) OR b) force me to use that little 'remove device' icon in the lower right-hand corner of Windows (meaning it's NOT hot-swappable) - either way, be sure your XBee/XBee Explorer USB is unplugged. THEN (and ONLY after you've unplugged your device) be sure to SHUT DOWN your virtual PC before going back to mac, and SAVE PC's STATE. You can decide if you want to quit Virtual PC 7 or not. It doesn't matter.
NOT DONE YET.! Here comes the REAL pain in the a$$. BACK TO THE MAC 1. When you go back to your mac you have to (re)install the latest FTDI drivers so your mac can see your XBees! After installing the drivers and plugging in your XBee/XBee Explorer USB, you should be able to see your device using Terminal (ls /dev/tty.) 3. Here's the REAL kicker here: in order to go back to Windows in VPC and use XCTU. YOU HAVE RE-INSTALL THE OLD MAC DRIVERS from the original digi site!
YOU WILL BE FORCED TO RESTART YOUR MAC! This means YES! EVERY SINGLE TIME you have to reconfigure your XBee YOU WILL BE FORCED TO RESTART YOUR MAC! AGAIN, between shutdown and restart be sure to unplug your XBee/XBee Explorer USB. Your other USB devices can stay plugged in at this point.
It's all about what Windows in VPC thinks is happening at that point. When you shut down your virtual PC in step 14, you had your XBee/XBee Explorer USB UNPLUGGED and all other usb devices plugged in. You just have to make sure when you restart your Windows in VPC, things are as they were when you shut it down. Somewhere between steps 12 and 13 above i configured both my XBees using the USING THE MAXSTREAM SOFTWARE part of this tutorial: 2. I wired one XBee to my Arduino using my XBee Explorer using the CONCEPT of STEP 4: WIRE UP THE REMOTE UNIT of this tutorial: (a link from this tutorial: NOTE: i used a breadboard instead of soldering.
I have commitment issues 3. I plugged the XBee/XBee Explorer USB into my computer 4. To get them talking to each other i used the very bottom of this tutorial: a friend once called me a pragmatist.
I wasn't sure how i felt about that. Until i read this: A pragmatist would never plant such a messy tree, but I like its flowers. I try to make things as simple and clean as possible. Barring that, i will get to where i want to be regardless of the route. It's messy, but it works! I call it The Frankenstein Approach. Hope this helps, folks!
Bhima: dkrofft1, thanks for this epic instructional post. So far, I don't have success. So I have a few questions. In step one, you say to remove all USB Devices. Macs use USB keyboards and mice. How did you do all the other steps with no keyboard or mouse? I have a fresh install of XP in Parallels, do you think this is my problem?
I don't have Win2k or Virtual PC. Also when I install the mac drivers from digi, I never see the devices appear in /dev when I plug my USB XBee devices in. So I am not surprised that when I have my WinXP vm running & plug them in I am never asked if I want to connect the new USB device to the WinXP vm (despite having Parallels set to ask me). Dorseykrofft1: oops! I'm working on a PB G4, so i completely forgot about the whole mouse/keyboard thing for desktops. You can leave those in. (uh, NEED to leave those in!) my guess is that since the keyboard and mouse are input devices, they won't be mistaken as external hard drives or card readers, etc.
Out of curiosity (and to see if i could help) i installed Windows XP Pro (which i had chosen NOT to do so before because OSX and VP7 don't seem to like XP - it runs SOOOOO SLLLOOOOWWW!!!) i have been trying over and over (and over) to get XP Pro to allow me to install third party USB drivers and it simply REFUSES! Windows XP Pro tells me the microsoft drivers already installed are already the best drivers and it decides for you. You are forced to use the microsoft USB drivers. After uninstalling all USB drivers (and even after trying to control where Windows searches for drivers) Windows XP Pro still automatically decides for you and installs the microsoft drivers. Again, you are forced to use the microsoft USB drivers. Awfully cavalier of microsoft, the devil's spawn. Sorry i can't offer any more help.
I'm still trying tho! If i come up with anything, i'll be sure to post it here! FataleXception: hi guys, I don't know if this will help in your specific situations, but here is my solution for using X-CTU on a mac. I recently went from using a windows laptop to a Intel Macbook, and needed to be able to configure and program XBees properly, ie with X-CTU. This was relatively straightforward: Prerequisites:. Intel-based mac (AFAIK you can't run a windows VM on G5?).
Mac USB drivers for FTDI/USB modules, so that you can at least read/write from the terminal. FTDI drivers for the Windows version you're going to install; the easiest is the ones included in the Arduino distribution under /drivers in the zip. Download virtualbox (free VM software). Windows ISO or CD (I used 32bit, SP3). Install virtualbox.
Install windows XP in a VM. Go to Devices - USB Devices - select the devices to use in the VM, eg 'FTDI FT232R USB UART (0600)' which both of mine are; can't tell them apart:/ Devices then pop up in windows and demand drivers. Tell it to install the drivers you got earlier, ie point it at the extracted zip. Drivers should be installed; check device manager to make sure all have drivers. You may need to re-connect them to the VM, like unplugging and replugging a real device, so they get the drivers. Run X-CTU and you should be able to select the COM port:) One nice thing is that windows tends to assign the same COM port for a specific FTDI device, so you can identify which device it's communicating with by that. Caveats: Occasionally X-CTU is unable to read or write the device, and sometimes resetting it helps.
I don't know if this actually has anything to do with it being a VM or what. Hope this helps! - FataleXception Navigation 0 #.
Hi all, I am the proud owner of a new iMac Pro. I'm trying to get my eGPU working with it, but it seems that High Sierra has a new build number (17C2120) that doesn't seem to have a corresponding vNvidia web driver.
It's strange because I restored my system from a backup (taken from an 'amateur' iMac?!) which had a working build. Was a migration rather than Time Machine style restore, in case that makes a difference.
Does anyone know how I can resolve this issue? Does the webdriver really have to match the build, and if not any idea how to fool it otherwise? Thanks in advance for help. For those curious about iMac Pro's graphics performance, I did some quick benchmarks using Unigene Heaven. 955 was the score at 4k resolution, everything maxed out, and 1933 on 1600.900.
Nowhere near as good as my 1080TI via eGPU which was hooked up via TB2-TB3 adapter on my Late 2014 iMac, which scored something like 2600 in the same test). Hi devild, thanks so much for trying to help. Unfortunately I'm still a bit stuck.
At this point, I don't have the nVidia drivers installed at all. Here's the situation:. Before I did anything else I tried your exact suggestions.
However after the kextcache part ran, nothing seemed to happen after that. The nVidia webdriver GUI still didn't let me switch from OSX to nVidia, and rebooting made no difference. I the uninstalled my existing webdriver which was probably a mistake because now I can't reinstall it at all. If I try to run the webdriver installer package it says I can't because the package isn't compatible with this build. I can use your proposed script with this command./webdriver.sh -u and it appears to install and completes successfully, but nothing happens after that. I don't have this file any moreNVDAEGPUSupport.kext/Info.plist, I think I need to install the eGPUsupport package but I can't because it fails because of no webdrivers.
Could you please help me to start from scratch? Fantastic, that worked! Thanks so much. The only remaining issue is that I have to use the workaround 'plug in the TB3 cable once logged in, then log out once recognised in System Report, then log in again'. I had exactly the same issue, as have others, with my Late 2014 iMac 5K.
I don't suppose you know how to get it to work without the above, so that I can leave plugged in and reboot at will any time? Thanks again so much for your help. I will post an implementation guide summarising the instructions above for the benefit of others using iMac Pro.
Posted by: DANgerous25 Hi devild, thanks so much for trying to help. Unfortunately I'm still a bit stuck. At this point, I don't have the nVidia drivers installed at all. Here's the situation:. Before I did anything else I tried your exact suggestions. However after the kextcache part ran, nothing seemed to happen after that. The nVidia webdriver GUI still didn't let me switch from OSX to nVidia, and rebooting made no difference.
I the uninstalled my existing webdriver which was probably a mistake because now I can't reinstall it at all. If I try to run the webdriver installer package it says I can't because the package isn't compatible with this build.
I can use your proposed script with this command./webdriver.sh -u and it appears to install and completes successfully, but nothing happens after that. I don't have this file any moreNVDAEGPUSupport.kext/Info.plist, I think I need to install the eGPUsupport package but I can't because it fails because of no webdrivers. Could you please help me to start from scratch? Did you have to turn off Startup Security on your iMac Pro or was leaving it at it's default 'Full Security' work just fine?
Posted by: devild Hey @dangerous25, Update Nvidia drivers with script (./webdriver.sh -u ) Open Terminal and edit Info.plist in NVDAEGPUSupport.kext: sudo nano /Library/Extensions/NVDAEGPUSupport.kext/Contents/Info.plist Change NVDARequiredOS to 17C2205. Save changes and close the file (CTRL+X - Y -Enter). Run next command: sudo touch /Library/Extensions/ && sudo touch /System/Library/Extensions/ && sudo kextcache -u / Reboot. Any chance you make break this down a bit more step by step. I am not a regular Terminal user, only when needed.
I'm having the same issue. IMac Pro with eGPU setup. I've been at this for several hours now. I'm stuck at the very start. I'm trying to download the web drivers.
Maxstream Pkg U Driver Download
I can't just install the drivers because they aren't compatible with 10.13.2 and I'm trying to follow your terminal script however I keep getting a 'fork: Resource temporarily unavailable' error. Any help is greatly appreciated. Also, earlier today I tried installing Beta 4 of 10.13.3 hoping it would just work, but no luck. I'm back on 10.13.2 for now.
I'm keeping at this so anything you can tell me would be a huge help. Thanks everyone for the help. It's up and running. For fun I did a side/side comparison.
Pretty interesting results. Honestly I felt the eGPU would make a bit more difference. IMac Pro: 10 core, 128gb ram, Radeon Pro 64 16gb.
Maxstream Pkg U Drivers For Mac
Macbook Pro: '16, 2.9GHz i7, 16gb ram, Radeon Pro 460 4 GB/Intel HD Graphics 530 1536 MB eGPU:, NVIDIA GTX 1080 Ti Software: MacOS X High Sierra 10.13.2, Adobe Premiere Pro 2018 - 4K ProRes422 1m 14sec Plugins: Colorista IV, Lumetri Color, Cosmo II - iMac Pro w/ eGPU - 3:52 iMac Pro w/o eGPU - 4:18 ’16 Macbook Pro w/ eGPU - 8:17 ’16 Macbook Pro w/o eGPU - 10:36. Hi, I also have an iMac Pro with 10.13.3 (17D2104).
Maxstream For Pc
I tried to follow the instructions to hook up my new egpu case and card but I’m stuck at the webdriver installation like the others here. Supposedly the appropriate driver for my macOS build is 378.10.10.10.25.159 but neither using the installer directly or the webdriver.sh script works. They both say that no matching driver has been found or that my build is not compatible. Any idea what the culprit could be? I found this thread and there seems to be some solution for earlier versions but not for this. Any help would be greatly appreciated!