Every previous plot is erased when a new one arrives.
I can't see the resulting profile with all the plots. Only the last one.

I think you are using 'Measure' not a profile process????


I have no idea what Calman uses.

Steve

Nope, the i1D3 probe works by default with LightSpace.
Nothing else is needed.

Steve

Every previous plot is erased when a new one arrives.
I can't see the resulting profile with all the plots. Only the last one

.
I wanted to use the mini as a pattern generator.
I will review the instructions.

Connecting mini3D;
1- communication fails because lightspace try to connect at 57600 Baud whereas the default is 9600 on the mini. Will try tomorrow
2- by the way lightspace does not identify virtual ports

Can't access neither "Calibration" nor "Display" : the application crashes
will install on another laptop with W7

Definitely the i1D3 is not identify. Not listed when trying to "change probe"
will try with my i1 pro V1

Do you have the latest Lumagen software?
The Coms has changed totally with the latest versions.
Also, if the first connection fails try again...
The Coms will cycle baud rates.

What Virtual Ports? Probably realated to my points above. Update your Lumagen firmware?
I Have a Mini here, and it works perfectly.

If you have any crashes there is definitely something wrong with your installation.
There are no known crashes with the software at the present time.
That really suggest something is wrong.
Have you tried ti install a newer version of LightSpace over an older one, without first un-installing the old version?
That can cause problems.

Steve

Lumagen connection solved.
The user should power on from its own and not upload when in standby mode.
If not the first commands are not interpreted by the lumagen ( setting baud rate and alive)
The % lumagen command takes at least 4 seconds to proceed.
If the mini3D is powered off and LS is still running, LS keeps going at 57600 whereas Min3D restart at default.

Everything is working with W7 but the probes.
i1D3 ,i1 pro and i1 display LT ARE NOT identified at all.

The installation under XP was the first one. I will investigate later.

When I first activated the LS all the tools were available but the probes were grayed which is normal.
Then when I registered DPS the probes turned on but some tools are desactivated
Unfortunately I can't come back to the test version

My first concern is the probes not working with DPS

Glad the Lumagen connection issue is sorted.
Is there something we can do to prevent this problem?

As for no probes working there must be something wrong with your installation...
All works perfectly here, and with 'most' other users - the only other problem reported to us has been 'Kerlucun' on this thread.
This may be a driver or software conflict of some kind...

Do go back to an 'unlicensed' version of LightSpace navigate to: 'C:\ProgramData\IProt' and delete any 'LightSpaceXXXX' folders found there.
This will remove the licenseing when LightSpace is re-started.

Steve

New install on a third PC: XP SP3
No crash. )

I installed the i1 drivers supplied with LS (it was the first install of the drivers)
D2 properly idendified in Windows Device Manager
D2 not recognyzed by LS
D2 working with another software installed AFTER LS

Thanks for the info regarding unlicensing. Will be helpfull later

Will come back later for the radiance subject

Would you have a previous version of LS just for testing the probes.
Does LS produce log files in that regard?

You should not have to install ANY drivers.
Just install LightSpace and then plug in the probes with LightSpace not open.
The probe will be recognised and the correct drivers accessed.

That may be you problem?

The re is no previous Free version of LightSpace.
What you have will work when you isolate what has been configured incorrectly with your set-up.

No log file can be generated as the probe are not being seen - therefore there is no data to log.

Steve

I uninstalled the drivers without any better result.
The case of the i13 is very strange since that probe does not require any driver.
It just need the i1D3DSK.dll which is actually installed in the LS folder.
After LS has started I can see that the Hid.dll image is already loaded in RAM.
I guess i1D3sdk.dll is dynamically loaded.
That does not happen at any moment.

Have you tested your own copy with a free DPS license key?

We test all versions of LightSpace, with all license keys, and all work perfectly.
We have may 100's of DPS users, and as I say the only reports of problems have been you and Kerlucun in this thread...

As we cannot replicate this problem there is unfortunately little we can do to help.

Sorry - we are stuck at this point... there must be something different with your PC configuration that is causing a problem that we just can't replicate.

Hello Steve, I realized yesterday 2 additional trials.
The first at my neighbor house in repatriating the installer on a USB key, result was windows blue screen.
The 2nd in the evening on the laptop of a friend (Vista) and by downloading the demo and the key DSP program.
It was also a failure, see the following link...
I would think that my home is a cursed place haunted by evil spirits.
More seriously, it is really frustrating not being able to perform an operation as simple as installing a demo software.



http://imageshack.us/photo/my-images/707/ak42.jpg/

Looks to me like the OS is missing vital components.
You must have the latest upgrades for the OS installed.

However, I don't think we have ever actively used Vista... A horrible OS!!!

I have just re-run tests on LightSpace DPS on Windows XP, 7, and 8.

All worked perfectly...

Unfortunately there really is nothing more we can do to help unless you can isolate further the problem you have.
This really does look to be a problem limited to your PC configuration for reasons we just cannot replicate.