Logicport owners help - driver issue

Logicport has stopped working in the lab, and now when we start the
software it reports - 

"The LogicPort hardware may already be in
use by another instance of the software".

It appears to be a software glitch that causes these problems. Our prof is
considering sending it back to Intronix for repairs but we are losing time
on finishing our project. (It appears that the usb interface using
FTDI/eeprom chip on logicport is poorly designed and may need reflashing!
FTDI drivers apparently had some major flaws then) Can someone please let
us know if you have seen this before? Intronix, the maker of Logicport,
appears to be a small company (it appears one product only) and does not
have a forum to share user problems with their product 

 

	   
					
---------------------------------------		
Posted through http://www.EmbeddedRelated.com

eedesi wrote:
> Logicport has stopped working in the lab, and now when we start the
> software it reports - 
> 
> "The LogicPort hardware may already be in
> use by another instance of the software".
> 
> It appears to be a software glitch that causes these problems. Our prof is

Are you sure it isn't something as simple as (effectively) a lock file
that wasn't properly deleted the *last* time you used the software?

Have you tried installing it (clean) on another system to rule
out that aspect?

> considering sending it back to Intronix for repairs but we are losing time
> on finishing our project. (It appears that the usb interface using
> FTDI/eeprom chip on logicport is poorly designed and may need reflashing!
> FTDI drivers apparently had some major flaws then) Can someone please let
> us know if you have seen this before? Intronix, the maker of Logicport,
> appears to be a small company (it appears one product only) and does not
> have a forum to share user problems with their product 

On Sun, 24 Oct 2010 19:35:48 -0500, "eedesi"
<vindesi2@n_o_s_p_a_m.gmail.com> wrote:

>Logicport has stopped working in the lab, and now when we start the
>software it reports - 
>
>"The LogicPort hardware may already be in
>use by another instance of the software".
>
>It appears to be a software glitch that causes these problems. Our prof is
>considering sending it back to Intronix for repairs but we are losing time
>on finishing our project. (It appears that the usb interface using
>FTDI/eeprom chip on logicport is poorly designed and may need reflashing!
>FTDI drivers apparently had some major flaws then) Can someone please let
>us know if you have seen this before? Intronix, the maker of Logicport,
>appears to be a small company (it appears one product only) and does not
>have a forum to share user problems with their product 

I get that error only when I start a second copy of the
software.

Are you sure you're not running multiple copies of the
software ? The executable is listed as 'LogicPort.exe'
under 'Processes' in the Windows Task Manager.


John Kortink

-- 

Email    : kortink@inter.nl.net
Homepage : http://www.inter.nl.net/users/J.Kortink

Those who can, do. Those who can't, manage.

>
>On Sun, 24 Oct 2010 19:35:48 -0500, "eedesi"
><vindesi2@n_o_s_p_a_m.gmail.com> wrote:
>
>>Logicport has stopped working in the lab, and now when we start the
>>software it reports - 
>>
>>"The LogicPort hardware may already be in
>>use by another instance of the software".
>>
>>It appears to be a software glitch that causes these problems. Our prof
is
>>considering sending it back to Intronix for repairs but we are losing
time
>>on finishing our project. (It appears that the usb interface using
>>FTDI/eeprom chip on logicport is poorly designed and may need
reflashing!
>>FTDI drivers apparently had some major flaws then) Can someone please
let
>>us know if you have seen this before? Intronix, the maker of Logicport,
>>appears to be a small company (it appears one product only) and does not
>>have a forum to share user problems with their product 
>
>I get that error only when I start a second copy of the
>software.
>
>Are you sure you're not running multiple copies of the
>software ? The executable is listed as 'LogicPort.exe'
>under 'Processes' in the Windows Task Manager.
>
>
>John Kortink
>
>-- 
>
>Email    : kortink@inter.nl.net
>Homepage : http://www.inter.nl.net/users/J.Kortink
>
>Those who can, do. Those who can't, manage.
>
>	   
					
---------------------------------------		
Posted through http://www.EmbeddedRelated.com

On Sun, 24 Oct 2010 19:35:48 -0500, "eedesi"
<vindesi2@n_o_s_p_a_m.gmail.com> wrote:

>Logicport has stopped working in the lab, and now when we start the
>software it reports - 
>
>"The LogicPort hardware may already be in
>use by another instance of the software".
>
>It appears to be a software glitch that causes these problems. Our prof is
>considering sending it back to Intronix for repairs but we are losing time
>on finishing our project. (It appears that the usb interface using
>FTDI/eeprom chip on logicport is poorly designed and may need reflashing!
>FTDI drivers apparently had some major flaws then) Can someone please let
>us know if you have seen this before? Intronix, the maker of Logicport,
>appears to be a small company (it appears one product only) and does not
>have a forum to share user problems with their product 

Well, I've never had a problem with the FTDI chips. I did end up having
to replace a Fluke Scopemeter serial-USB cable that used a chip from
another manufacturer <cough>prolific<cough> which wasn't usable after
one of Microsoft's XP service packs. The discussion should still be in
the Fluke support forum archives. Fluke's solution was to issue a new
rev of the cable using an FTDI interface chip.

Could some other app be capturing the LogicPort interface? It uses the
D2XX direct drivers, not via a virtual com port. Try the latest drivers?

FWIW, here's the "template" file for the FTDI chip in the LogicPort, as
captured by FTDI's FT_PROG.

<?xml version="1.0" encoding="UTF-8"?>
<FT_EEPROM>
  <Chip_Details>
    <Type>FT232/245BM</Type>
  </Chip_Details>
  <USB_Device_Descriptor>
    <VID_PID>1</VID_PID>
    <idVendor>0403</idVendor>
    <idProduct>DC48</idProduct>
    <bcdUSB>USB 1.1</bcdUSB>
  </USB_Device_Descriptor>
  <USB_Config_Descriptor>
    <bmAttributes>
      <RemoteWakeupEnabled>false</RemoteWakeupEnabled>
      <SelfPowered>false</SelfPowered>
      <BusPowered>true</BusPowered>
    </bmAttributes>
    <IOpullDown>true</IOpullDown>
    <MaxPower>200</MaxPower>
  </USB_Config_Descriptor>
  <USB_String_Descriptors>
    <Manufacturer>Intronix</Manufacturer>
    <Product_Description>LogicPort Logic Analyzer</Product_Description>
    <SerialNumber_Enabled>true</SerialNumber_Enabled>
    <SerialNumber>
    </SerialNumber>
    <SerialNumberPrefix>13</SerialNumberPrefix>
  </USB_String_Descriptors>
</FT_EEPROM>

-- 
Rich Webb     Norfolk, VA

>
>On Sun, 24 Oct 2010 19:35:48 -0500, "eedesi"
><vindesi2@n_o_s_p_a_m.gmail.com> wrote:
>
>>Logicport has stopped working in the lab, and now when we start the
>>software it reports - 
>>
>>"The LogicPort hardware may already be in
>>use by another instance of the software".
>>
>>It appears to be a software glitch that causes these problems. Our prof
is
>>considering sending it back to Intronix for repairs but we are losing
time
>>on finishing our project. (It appears that the usb interface using
>>FTDI/eeprom chip on logicport is poorly designed and may need
reflashing!
>>FTDI drivers apparently had some major flaws then) Can someone please
let
>>us know if you have seen this before? Intronix, the maker of Logicport,
>>appears to be a small company (it appears one product only) and does not
>>have a forum to share user problems with their product 
>
>I get that error only when I start a second copy of the
>software.
>
>Are you sure you're not running multiple copies of the
>software ? The executable is listed as 'LogicPort.exe'
>under 'Processes' in the Windows Task Manager.
>
>
>John Kortink
>
>-- 
>
>Email    : kortink@inter.nl.net
>Homepage : http://www.inter.nl.net/users/J.Kortink
>
>Those who can, do. Those who can't, manage.
>
>

Thanks for your responses.  We are sure that there is no other instance of
software running.  The problem began once the LogicPort was moved to a
Windows 7 machine where it was installed correctly (procedure at least) but
did not work.  Isn't it compatible with Win 7?  Since then it has not
worked on any other computer including the previous XP one where it was ok
earlier.  What is puzzling is that it enumerates when connected to USB,
gets bus power because the yellow light comes on and stays on, but the main
app software does not recognize the hardware.  May be 'part' of the
EEPROM(93C46) has got corrupted  because FTDI chip (245B) is doing its part
to enumerate... the usb device descriptor, etc. Other than the FPGA, there
is not much hardware inside. 

 	   
					
---------------------------------------		
Posted through http://www.EmbeddedRelated.com

On Mon, 25 Oct 2010 07:45:14 -0500, "eedesi"
<vindesi2@n_o_s_p_a_m.gmail.com> wrote:


>Thanks for your responses.  We are sure that there is no other instance of
>software running.  The problem began once the LogicPort was moved to a
>Windows 7 machine where it was installed correctly (procedure at least) but
>did not work.  Isn't it compatible with Win 7?

It may not be, in the sense that its default directory for the ini file
and project files is under c:/program files/logicport. Windows 7 is very
unhappy with apps that write to the "program files" directory tree.
Under the Win 7 model, as you probably know, writable ini files, project
files, and the like are expected to be in the user's home directory tree
vice a system tree.

>  Since then it has not
>worked on any other computer including the previous XP one where it was ok
>earlier.  What is puzzling is that it enumerates when connected to USB,
>gets bus power because the yellow light comes on and stays on, but the main
>app software does not recognize the hardware.  May be 'part' of the
>EEPROM(93C46) has got corrupted  because FTDI chip (245B) is doing its part
>to enumerate... the usb device descriptor, etc. Other than the FPGA, there
>is not much hardware inside. 

I'd try the latest drivers from FTDI. Perhaps also delete (after backing
up) the existing .ini file; it should be recreated with default values.

-- 
Rich Webb     Norfolk, VA

On 10/25/2010 08:45 AM, eedesi wrote:
> The problem began once the LogicPort was moved to a
> Windows 7 machine where it was installed correctly (procedure at least) but
> did not work.  Isn't it compatible with Win 7?

I use my logicport on Win7 all the time, works fine.

The FPGA in the logicport is an Altera Cyclone, if its flash is corrupt 
(unlikely?) you'll have to send it back for reprogramming.

/me wonders if something reprogrammed the EEPROM in the ftdi chip the 
logicport uses.  For reference, here's the data from my logicport:

Bus 001 Device 015: ID 0403:dc48 Future Technology Devices 
International, Ltd
Device Descriptor:
   bLength                18
   bDescriptorType         1
   bcdUSB               1.10
   bDeviceClass            0 (Defined at Interface level)
   bDeviceSubClass         0
   bDeviceProtocol         0
   bMaxPacketSize0         8
   idVendor           0x0403 Future Technology Devices International, Ltd
   idProduct          0xdc48
   bcdDevice            4.00
   iManufacturer           1 Intronix
   iProduct                2 LogicPort Logic Analyzer
   iSerial                 3 <hidden>
   bNumConfigurations      1
   Configuration Descriptor:
     bLength                 9
     bDescriptorType         2
     wTotalLength           32
     bNumInterfaces          1
     bConfigurationValue     1
     iConfiguration          0
     bmAttributes         0x80
       (Bus Powered)
     MaxPower              200mA
Device Status:     0x0000
   (Bus Powered)

In article <qp1bc6t8iti6c4uhnu2dabohbukb60epin@4ax.com>, 
bbew.ar@mapson.nozirev.ten says...
> On Mon, 25 Oct 2010 07:45:14 -0500, "eedesi"
> <vindesi2@n_o_s_p_a_m.gmail.com> wrote:
> 
> 
> >Thanks for your responses.  We are sure that there is no other instance of
> >software running.  The problem began once the LogicPort was moved to a
> >Windows 7 machine where it was installed correctly (procedure at least) but
> >did not work.  Isn't it compatible with Win 7?
> 
> It may not be, in the sense that its default directory for the ini file
> and project files is under c:/program files/logicport. Windows 7 is very
> unhappy with apps that write to the "program files" directory tree.
> Under the Win 7 model, as you probably know, writable ini files, project
> files, and the like are expected to be in the user's home directory tree
> vice a system tree.

I've had exactly that problem with a terminal emulator that wanted to
save input data to the program file directory.  We couldn't find the
data afterwards.  I think we solved the problem  by specifying an
output path in the documents folder.
> 
> >  Since then it has not
> >worked on any other computer including the previous XP one where it was ok
> >earlier.  What is puzzling is that it enumerates when connected to USB,
> >gets bus power because the yellow light comes on and stays on, but the main
> >app software does not recognize the hardware.  May be 'part' of the
> >EEPROM(93C46) has got corrupted  because FTDI chip (245B) is doing its part
> >to enumerate... the usb device descriptor, etc. Other than the FPGA, there
> >is not much hardware inside. 
> 
> I'd try the latest drivers from FTDI. Perhaps also delete (after backing
> up) the existing .ini file; it should be recreated with default values.
> 
> 
Mark Borgerson

In article <IpednVmrDLq6C1jRnZ2dnUVZ_gmdnZ2d@giganews.com>, 
dj@delorie.com says...
> On 10/25/2010 08:45 AM, eedesi wrote:
> > The problem began once the LogicPort was moved to a
> > Windows 7 machine where it was installed correctly (procedure at least) but
> > did not work.  Isn't it compatible with Win 7?
> 
> I use my logicport on Win7 all the time, works fine.
> 
> The FPGA in the logicport is an Altera Cyclone, if its flash is corrupt 
> (unlikely?) you'll have to send it back for reprogramming.
> 
> /me wonders if something reprogrammed the EEPROM in the ftdi chip the 
> logicport uses.  For reference, here's the data from my logicport:
> 
> Bus 001 Device 015: ID 0403:dc48 Future Technology Devices 
> International, Ltd
> Device Descriptor:
>    bLength                18
>    bDescriptorType         1
>    bcdUSB               1.10
>    bDeviceClass            0 (Defined at Interface level)
>    bDeviceSubClass         0
>    bDeviceProtocol         0
>    bMaxPacketSize0         8
>    idVendor           0x0403 Future Technology Devices International, Ltd
>    idProduct          0xdc48
>    bcdDevice            4.00
>    iManufacturer           1 Intronix
>    iProduct                2 LogicPort Logic Analyzer
>    iSerial                 3 <hidden>
>    bNumConfigurations      1
>    Configuration Descriptor:
>      bLength                 9
>      bDescriptorType         2
>      wTotalLength           32
>      bNumInterfaces          1
>      bConfigurationValue     1
>      iConfiguration          0
>      bmAttributes         0x80
>        (Bus Powered)
>      MaxPower              200mA
> Device Status:     0x0000
>    (Bus Powered)
> 

You might be able to rejuvenate the LogicPort by using the FTDI MPROG 
utility to read the charactersistics of a known good LogicPort, then
checking to see if the bad unit is different.  If so, you could program
the bad unit EEPROM to match the good unit.  


Mark Borgerson