Hi everyone,
I have quite an issue to submit to your knowledge.
I have a POP 2 scanner and a MINI. Lately I tried to make all that work with Windows 10… in a virtual machine (Oracle virtual box) on Linux.
Well, everything was almost OK (it is necessary to redirect USB devices to the VM but it’s ok) and Win 10 was aware of MINI. (Chishine3d ZXProduct [0419])
I started Revoscan and was able to perform one test scan with the small figurine: OK.
Then I tried to update the MINI firmware (Revoscan said there was an update). Then it all went wrong:
Revoscan switched my MINI to “update mode”. It was disconnected from the VM and from Linux kernel.
MINI turned back on with a new USB identification
Oct 3 22:43:03 erin kernel: usb 3-1: new high-speed USB device number 32 using xhci_hcd
Oct 3 22:43:03 erin kernel: usb 3-1: New USB device found, idVendor=2207, idProduct=0006, bcdDevice= 3.10
Oct 3 22:43:03 erin kernel: usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 3 22:43:03 erin kernel: usb 3-1: Product: rk3xxx
Oct 3 22:43:03 erin kernel: usb 3-1: Manufacturer: rockchip
Oct 3 22:43:03 erin kernel: usb 3-1: SerialNumber: REVO-A22710442A6F00A64
But it keeps disconnecting and reconnecting to the Linux kernel thus preventing the reconnection to the VM to finalize the update process.
The question is: how is it possible to revert to a normal state ?
What about the colour of the LED indicator at the back when it is red ?
I tried to hold the “play” button while powering up. The colour changes (red, then green and then blue) but then what ?
I’ll try to connect my MINI to a laptop running a native version of Windows but until then it would be nice to fully understand what’s going on…
This is the first time I have heard of anyone running Revo Scan on a VM (Virtual Machine) emulating Windows.
I expect your problem with the update is that the Mini’s internal firmware is a version of Android and your VM doesn’t allow adb (the Android Debugging Bridge) utility to communicate via the re-directed USB port. Could be a limitation of your VM or a configuration error for the USB redirection you mentioned in your 3rd paragraph.
I would suggest getting/borrowing an actual Windows 10/11 system and trying the update that way.
Thank you so much for so a quick reply.
I’ll try with an actual Windows 7 (not 10 on my laptop). I have a laptop sleeping somewhere in my attic
I hope the MINI will mount correctly on a native machine.
I just checked my kernel messages: MINI keeps registering with the Linux kernel, creating each time a new device (n° 37… 38… 39) with the ID RK3XXX
I hope it won’t loop this way when connecting to Windows.
As it does not stabilize the kernel can’t redirect the USB entry to the VM. At this point the VM is not concerned yet. The USB devices connect first to the Linux kernel and then are made available to any usage.
If you want to know, the USB devices appear in a menu in the VM. You can either check the device and it is redirected to the VM or you can set up an entry in the VM settings and this device is redirected automatically to the VM at startup.
This is what I do for the bluetooth dongle and some USB disks. It works all fine.
So is there a way to “hard reset” MINI ? Revert to a previous stable state ?
Good night. I’ll read any new answer tomorrow morning.
You can’t update the firmware using Windows 7 , it will not work , may tried and failed.
You can try to reset your device firmware back to original one clicking 10 times on your device play button while it is not connected to your computer , only to another power source , it should change from blue to red to blue and green .
P.S it is not called POP MINi , it is just MINI or Revo MINI /Revopoint MINI
Hi !
Thank you for your help
I’ve just done what you said: clicked 10 times the play button while connected to a power source and not to a computer.
Started from blue light, 10 press, light turned red, then blue and now it is green.
Next step: connect MINI back to my Linux and check the kernel messages.
BTW: thank you for correcting me about MINI name. I’ve just edited my previous posts to correct the name.
Best
Joseph
It looks like it worked fine ! Many thanks
I’ve just plugged MINI to my Linux and here is what the kernel said:
Oct 4 09:55:03 erin kernel: usb 3-1: new high-speed USB device number 78 using xhci_hcd Oct 4 09:55:03 erin kernel: usb 3-1: New USB device found, idVendor=2207, idProduct=110c, bcdDevice= 4.19 Oct 4 09:55:03 erin kernel: usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 4 09:55:03 erin kernel: usb 3-1: Product: ZXProduct Oct 4 09:55:03 erin kernel: usb 3-1: Manufacturer: Chishine3d Oct 4 09:55:03 erin kernel: usb 3-1: SerialNumber: A22710442A6F00A64 Oct 4 09:55:03 erin kernel: usb 3-1: Found UVC 1.00 device ZXProduct (2207:110c) Oct 4 09:55:03 erin kernel: input: ZXProduct: DepthCamA22710442A6F as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0/input/input17 Oct 4 09:55:03 erin kernel: usb 3-1: Found UVC 1.00 device ZXProduct (2207:110c) Oct 4 09:55:03 erin kernel: input: ZXProduct: RGBCamA22710442A6F00 as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.2/input/input18
MINI is seen like it was seen before.
The light is green also.
Just started my Win10 VM. Mini is automatically connected to the VM, fine !
Started Revoscan: MINI is fired up and woks fine too.
I would recommend you use Android app for now with Dual Axis Turntable and do not upgrade MINI"s firmware via your workstation again as next time it may not work to restore it back if it get corrupted .
HI there,
thank you for the tip. I was not aware of this app.
I’ve just downloaded the app. It works fine on my Android tablet. I put side by side DATT and REVOSCAN windows. It allows to manually synchronize the scan and the turntable rotation.
BTW, I’ll try to have DATT CONTROLLER work with another turntable (one I got with FOLDIO 360)? Who knows… it might work …
Thanks to the tip I was able to initialize my Mini.
And this time Mini didn’t loop initializing / connecting to the kernel. (Product: ZXProduct)
As it was stabilized, the USB device could easily be redirected to the VM.
When Mini was in the previous state (update mode) I was able to connect it to the VM under its current name ( Product: rk3xxx) but it didn’t last as, like I said, it was constantly initializing / connecting.
And to answer your question I didn’t change anything to the VM.
My VM is configured to automatically “capture” certain USB devices: the scanner and the bluetooth dongle. But it can be done manually while running the VM.
