USB 3 will not working on MAC in this case … so I guess we can close this case ?
until there is another better solution provided by the tech team .
USB 3 will not working on MAC in this case … so I guess we can close this case ?
until there is another better solution provided by the tech team .
Andy did already stated that on Dec.23 Until anything else is provided there is nothing else to do in this case .
Where comes this sudden knownledge about USB 2.0 cables from? I can’t remember seeing that before in this thread?
I still think it’s a rights issue since something changes when I use sudo to open revoscan. Also some people seem to have success connecting their Miraco to their Mac using the supplied cable. Wouldn’t cal this case solved just yet.
click on the arrow on Andy’s quote … Dec.23
it is not solved for real , just temporary until there is better solution for that , we already run out of all solutions . For almost 3 months I did not believed it was a cable either as I tried all cables I had and even purchased some but in my case my PC don’t liked the cables until I got thunderbolt 40GB 8K USB C , for the transfer mode the original cable from Miraco worked fine , but not in PC mode …
for now in your case is only USB 2.0 if the original cable don’t works … All our beta testers used it with Mac and it worked .
Just some more info (I just sent this to customer support as well). When I start revoscan via command line without sudo I see this when I connect the Miraco:
[13:21:15.396 info TID:5368679 RevoVersionManager]: is newest revo scan version
Device 0 (VID=2207 and PID=0006) is a YiFang BQ Tesla.
LIBMTP PANIC: Unable to find interface & endpoints of device
Device 0 (VID=2207 and PID=0017) is a iBasso DX170 DAP.
libusb_detach_kernel_driver() failed, continuing anyway...: Invalid argument
error returned by libusb_claim_interface() = -3LIBMTP PANIC: Unable to initialize device
Device 0 (VID=2207 and PID=0017) is a iBasso DX170 DAP.
libusb_detach_kernel_driver() failed, continuing anyway...: Invalid argument
error returned by libusb_claim_interface() = -3LIBMTP PANIC: Unable to initialize device
Device 0 (VID=2207 and PID=0017) is a iBasso DX170 DAP.
libusb_detach_kernel_driver() failed, continuing anyway...: Invalid argument
error returned by libusb_claim_interface() = -3LIBMTP PANIC: Unable to initialize device
The last bit keeps repeating every second or so.
When I start revoscan with sudo, the first error is the same, but after that its different:
13:17:31.310 info TID:5365912 RevoVersionManager]: is newest revo scan version
Device 0 (VID=2207 and PID=0006) is a YiFang BQ Tesla.
LIBMTP PANIC: Unable to find interface & endpoints of device
Device 0 (VID=2207 and PID=0017) is a iBasso DX170 DAP.
Android device detected, assigning default bug flags
[13:17:47.765 info TID:5365912 ]: MTPDeviceManager.cpp:425 open Device succeed
[13:17:47.769 info TID:5366234 ]: MTPDeviceManager.cpp:467 getBackupLoation start
Hope this is helpful for anyone.
For anyone wondering: The iBasso DX170 is some sort of high end portable music player… It seems the Miraco is presenting itself as such a player or something?
I found this thread interesting as I have a similar problem with my new Range 2. It will not connect to either a Mac Mini M1 or a HP laptop running windows 10 HP. In short I dont think this is just an issue with the Miraco.
No it is not the same issue here .
Please write to customer@revopoint3d.com if you have issues with your hardware .
I know this is an old thread but the Terminal command above worked for me, ie:
sudo /Applications/RevoScan5.app/Contents/MacOS/RevoScan5
M2 Mac Studio.
My Miraco was already connected to USB and in data transfer mode. The cable connected via a hub (I’ll try direct next time). When I ran the Terminal command I was asked to give Revo Scan bluetooth connection permission so I suspect a ‘local devices’ connection permission is also given by running sudo (as suspected by @jackjansen above) but then saw the import window and that worked.
Thanks for tips!
That worked for me too - thank you everyone, and thank you for writing the script out galexa! I just copied/pasted it into Terminal and bam, the pop up window in RevoScan popped up and I can download the files from my Miraco.
I’ve been pulling my hair out over this. My Miraco has occasionally (maybe 10% of the time) connected properly to my MacBook Pro (ie bringing up the the pop-up window that allows the download the scan files from the Miraco). The rest of the time I’ve just had to try again and again, restarting the MacBook and the Miraco and just waiting for it to finally connect - which until this week it eventually has.
To be clear I haven’t being changing any settings (on Mac or Miraco) and have been using the same Miraco data cable, and the same usb c port on the Mac everytime, it’s just that RevoScan’s pop-up window has sometimes popped up, but mainly it hasn’t. Things have seemed to be worse after upgrading to RevoScan 5.4.6
Anyway, thanks again everyone. I hope that using this script will solve the issue - at least until the problem can be solved within RevoScan, or until it becomes clear that there’s an access issue that we Mac users need to be aware of that will easily allow RevoScan to access the Miraco perfectly each time.
MacBook Pro M3 Max 32gb
Hi @Peter108 it came to my attention that using USB 3 data cable and Mac can cause some connectivity issues .
Try with USB 2 data cable connecting MIRACO to your Mac for transfer mode, one cable is not quite the same as other cable .
For example I could not use PC mode on my PC , but after purchasing USB Thunderbolt Cable 8K it actually worked perfect on my PC in all modes using MIRACO .
I had so many good data cables of any kind , but nothing compared to the 8K thunderbolt .
So just from curiosity try to use USB 2 data cable in place of the provided USB 3 data cable .
How could they get a Mac to work? The MacOS version of RevoScan5 doesn’t have any menus, so how did they select file transfer? Also, there is no MacOS program to launch a WiFi file exchange. I’m baffled at how they could get it to work.
Are you sure you not running iOS mobile version in place of the actual Mac version ?
From what you explained looks like you installed the mobile version .
You can download the latest MAC version here
This worked for me. I was pretty frustrated because the MacOS software, when you ask for help, points you to the PC manual.
Booting up Terminal and running:
sudo /Applications/RevoScan5.app/Contents/MacOS/RevoScan5
It is a godsend! Thank you for thinking of that, it never would have occured to me.
And Revopoint folks, do that and look at the log. A LOT of errors are flowing. Also, why didn’t the edits I’d done on the Miraco get transferred? It was the raw data that came across.
The MacOS software UI is VERY different from the PC UI in the manual. Given that the MacOS software help points to the PC manual, I went nuts until I found this forum.
Also, you can’t install iOS software on a Mac - at least not yet.
The good news is that the hack of opening Terminal and running
sudo /Applications/RevoScan5.app/Contents/MacOS/RevoScan5
Worked!
How do you get a USB 2 cable that is USB C at both ends?
Hi @bgrh
Please check this document to see if it helps you.
You can install the iPad version on a Mac, at least you could before. I tried it before to help someone in your situation, but I just checked the App Store and it’s gone. But to prove the point Revo Assistant shows up as an iPhone app that “Works on this Mac Studio.”
So if you installed Revoscan from the App Store on your Mac, it’s the iPad version. The MacOS UI is identical to the PC version. Trust me, I have them side by side.
I’m using a mac. Here’s the note I’ve written to remind myself how to get the Miraco to exchange files with my Mac.
RevoPoint Miraco to MacOS File Transfer Process - A Kludge!
These steps are necessary to ensure the smooth operation of the file transfer process.
Run this in Terminal, and file transfer should work.
NOTE:
Re:
Did you check the preference for where files get saved? I made a folder on Desktop rather than the default that’s buried in the Library. I don’t think that has anything to do with running sudo.
Thank you all so much for taking the time to document this. I spent about 3 hours getting the run-around regarding “fixes”, then found this post and had my Mac-USB issue resolved in minutes thanks to your efforts, and all of those that fed into this solution.