Thread: Upgrade to V2_0_12014_1630 and FTDI issues

This was a brand new Laptop, so it's a fresh build.

The sequence was built eitirely from one version back from the latest revision (so it's not an import from any other program)

The Output bulb is not highlighted

The controllers in the sequence are 16 Lynx Pixel controllers, varying from 25 pixels (75 RGB Pixels in total) to 120 pixels (360 RGB pixels in Total)

I've never plugged in any dongles (don't have one yet to plug in)

There's two D-Light AC 16's in the sequence.

Start LSP when it open the dialogue box asking whether you want to open/create new sequence close that out and close out the tips screen if that comes up. Then go up and select the options tab and select configure outputs and see if anything is in there, also make sure the the "Initialize outputs after sequence load" box is unchecked (which I think you did) If you have any output plug-ins listed see if there configured our not. If there are plug-ins listed you can delete those plug-ins and that should get rid of your error.

Originally Posted by Caretaker

Start LSP when it open the dialogue box asking whether you want to open/create new sequence close that out and close out the tips screen if that comes up. Then go up and select the options tab and select configure outputs and see if anything is in there, also make sure the the "Initialize outputs after sequence load" box is unchecked (which I think you did) If you have any output plug-ins listed see if there configured our not. If there are plug-ins listed you can delete those plug-ins and that should get rid of your error.

I started LSP, then opened the options tab and selected configure outputs, all the Pixel Net Controllers are shown and are tagged as configured. The "Initialize Outputs after sequence load" is not checked.

For the Pixel Net Plugins that are shown as configured, do I need to delete those? and then reconfigure them?

Do you have the pixelnet set up for E1.31? If so then no I would not delete them, but if they are set up for a dongle then yes (they will need to be set up for E1.31 anyway).

Well I dug into this alittle more.

I dug out my D-LIght USB dongle and plugged it in. The FTDI driver then got installed automatically. I then checked in device manager
to make sure it installed correctly (it had).

I then ran LSP, with the USB dongle still plugged in. LSP started up just fine, with no FTDI errors.

So I closed LSP, removed the USB dongle, checked in device manager that it had been removed (it had).

Then I started LSP again (but without the dongle plugged in)

It started just fine, and no FTDI errors.

So for some reason, LSP is checking (at least on my sequence and machine) for the FTDI drivers and the associated USB dongle.

If it doesn't see it, it throws the error which doesn't go away until the driver gets fully installed by plugging in the USB dongle.

Kinda strange that it requires the USB dongle/FTDI drivers, when I wouldn't plan on using them if I go for the Etherdongle route.

Thanks for everyone's help, but I would like David to chime in on why LSP needs an FTDI USB dongle though on this S/W build.

Pete,

When you did the initial install what type did you do. The drivers get loaded automatically and in your case have caused an error. If you choose custom then you are given a choice as to what you would like to install. If memory serves, the last choice is the driver in question. I choose not to install it as I only use E1.31 for output.

You may want to uninstall everything, including the FTDI stuff and then reinstall. Choose the custom option and uncheck the driver install box. That should clear up that error for you

Good to see you again. Are you getting into christmas or are you still a haloween guy

Cheers

Originally Posted by Unibits

Pete,

When you did the initial install what type did you do. The drivers get loaded automatically and in your case have caused an error. If you choose custom then you are given a choice as to what you would like to install. If memory serves, the last choice is the driver in question. I choose not to install it as I only use E1.31 for output.

You may want to uninstall everything, including the FTDI stuff and then reinstall. Choose the custom option and uncheck the driver install box. That should clear up that error for you

Good to see you again. Are you getting into christmas or are you still a haloween guy

Cheers

Hi Unibits,

I've give that a go, might have been an install error, but from what I could see, I just did a clean de-install and then rebooted and then re-installed and let the S/W install itself. Glad the dongle cleaned everything up.

I 'm still mainly a halloween guy, but took the last two years off, then I saw the RGB led lights and the Pixel net designs, they got me re-inspired for Halloween.
I think I will do both this year, but because of the steep leavning curve I'm starting early.
I'm off to the garage to finish my Singing Pumpkin. :-)