Hi,

I have issues connecting CR-100/CR250 devices to Lightspace CMS. System is Windows 7 running on VMware fusion on Macbook air.
Lightspace do not detect CR-100/CR250 probes nevertheless they are marked as detectable. Probes are connected via Virtual COM port in VMware fusion.
CRIapp on Virtual machine's Windows detects and works perfectly with those devices, but as soon as I switch to Lighspace it can not detect those devices.
Steve mentioned that it can be firewall issue, but firewall is turned off in Windows and as I mentioned previously CRIapp on Windows detects devices with no issues.
I've tried to connect i1 Display Pro to Lighspace and it works with no issues.
Has anyone any clues why this is happening and how to solve it?

Linas

Such issues have been reported before, and there are various threads in this forum.
For example: https://www.lightillusion.com/forums/index.php?action=vthread&forum=17&topic=358

Steve

I've read all the threads that might be useful before posting here, including the one you are metioning, but it does not solve my issue.

Unfortunately, there is little more we can suggest.
It is not a LightSpace issue, and so will be something to do with your specific VM setup.
But as to what - that's unfortunately beyond our ability to assist.
I guess you'll need to find a VMware fusion specialist?

But, within Windows, do the COMs ports show the CR probes in 'Device Manager'?

Steve

CR probes are listed in Device manager and they work perfectly with CRIapp on the same Windows/VMware fusion machine. Lightspace do not recognize probes but all other apps and system do recognise probes and work without any problems, so I can not call VMware fusion support and tell them that I have an issue with their software, because they will send me back to you

Linas

Unfortunately, as ColourSpace on all other systems works perfectly with the CR probes (including all other VM installations - after the issues mentioned in this forum have been overcome), its obviously not a ColourSpace issue...

As to what the issue is with your specific system, I have no idea.
But If the probes do show in Device Manager I am very surprised.
Please post a screen grab of the Device Manager window.

However, there are known issues with VM and virtual COMs ports.
You may want to look into that.
Also check Security and Privacy within the Mac System Preferences. Programs can be 'blocked' there.

Steve

Any progress?

Steve

Sorry for delay, I've reinstalled Win10Pro on VM, updated VM but Lightspace still doesn't recognise CR-100/CR250. CRIapp on the same VM machine works perfectly and recognises the same CR-100/CR250. I've attached print screen of device manager.
If there would be VM and virtual COMs ports issue then in this case CRIapp would't see CR-100/CR250 either? Or I'm wrong? Image attached.
All firewalls and that stuff is turned on Windows.

There are numerous potential issue with VM operation, depending on the VM you are using.
A search of this forum will show a number of such issues, and how users have overcome them.
But, it is not a LightSpace/ColourSpace issue - that we can guarantee.
(And that CRIapp works does suggest some form of OS communication issue...)

But, we do not guarantee Windows 7 operation.
For may users it does appear to work, but as it is a depreciated OS we do not guarantee it.
(We do not test with any OS that is depreciated.)

Steve

It's Windows 10 Pro updated to latest version, not Win7.
VM ware fusion 12.1.1 which is up to date and newest possible version too.
Maybe you can provide temporary license for two or so days for ColorSpace cms to check if it works with the probes.
Because I did run out of ideas what can be wrong, device manager recognises probe, other software recognises too, As I mentioned before I've read all the forum threads but none of them has ideas how to solve the issue. I already bought newest VM ware fusion version, bought newest Windows version, clean installed everything and nothing helps. And though it's not Lightspace issue I still need to sort this out.
Or maybe you can send very old Lightspace install file to me (oldest possible for Win10), because long time ago probes were working with Lightspace CMS and it stopped working after some update.

Linas

Sorry, I was not aware you had upgraded to Windows 10.
But the same is true - there are no issues with LightSpace and CR probes.
The problem will be localised to your system, and will be some form of VM issue.

Unfortunately we cannot provide temp ColourSpace licenses - but regardless, that would not help with your underlying issue.
We have a number of LightSpace uses using the latest LightSpace version via VM, so we know it 'can' work, but we also know there can be a number of issues getting the VM to work.

All I can hope is another VM user can respond with their thoughts.
I'll see if I can find another user to provide their feedback.

Steve

One question - what do you see in LightSpace?
What message do you see when you are trying to connect to any probe?
Are the CR probes ticked in Available Probes?

Steve

@LinasD

Reading through you issue it indeed seems like a pretty wierd issue, where you would expect that if one program can see and use the device all others should also be able to see that device. But that is not always the case and depends on what features/protocols are used.
I unfortunately dont own any of these probes (i wish....) but i did experience a similar issue where Lightspace was not able to use my probe while other software was.
The difficult to spot issue was related to the virtual USB port and its set compatibility mode (eg 3.1) did not match the USB type of the physical device (in my case USB2.0). . As , looking at the specs, your probes are also physicaly connected to your Mac via USB2.0 and therefore also require a similar virtual USB device, on top of which other devices can be defined like virtual COM ports etc its worth to check the following to make sure the USB communication is at least correct.
Go (with shutdown VM) to Virtual Machines > USB & Bluetooth settings > open Advanced USB options tab > USB compatibility. If set to 3.1 , set it to 2.0 and start your VM that way and see if it helps.

Ciao
Glenn

At LinasD: The probe itself is natively connect via USB or do you use some kind of Serial-COM-to-USB-adapter?

Hi, thank you for you insight, already tried USB2 and even USB1 with no luck.
I believe that the best way to solve this is to buy separate laptop for windows and Lighspace CMS, VM ware on mac is too much of a struggle.
Thank you for the input again.

All the best,

Linas