Hello,
We are using WinXP Professional. The Edgeport ports are configured to 2 and 3. After running a while, the ports disappear and our application dies. I watched and the Device Manager shows the ports gone from the list of available ports. If we unplug the usb connection to the Edgeport and reconnect they will show back up in the device manager and we can run for a while longer.
We are using Version 5.0.0 of the driver.
Any ideas?
Try this driver instead:
http://www.digi.com/support/forum/servlet/JiveServlet/download/58-8182-74174-532/40002537_C.zip
You should first uninstall the existing driver by clicking the Uninstall button under the Advanced tab, in the Edgeport Configuration Utility, then reboot the PC when prompted.
Let me know if this helps or not.
I have installed this new version - I think. The version I installed previously was from the CD and it was 5.0.0.0. I did not fully understand that edgeser.sys has its own version, so I did not check it.
The Device Manager now shows under the Driver tab
Driver Version 5.0.0.0.
Clicking on the Driver Details:
edgeser.sys - 4.20.07
Is this correct?
If so I will continue to run with these version, but the problem takes a few days sometimes to show up.
Thanks,
Scott
You’re running the correct version now (4.20).
OK let me know how it goes.
The ports were dropped again last night on an overnight run. I should note that we have not experienced this problem before. And we have used many of the Edgeport/22c devices.
This is a the first new model of a computer we are using - a Dell OptiPlex 760 WinXP Service Pack 3.
Any other ideas?
Hmm, another customer reported a similar issue and dropping down to 4.20 seemed to resolve it. So I was hoping that was the case here, but apparently it isn’t.
In that case, try the newer 5.10 Edgeport driver:
ftp://austin:!15st3n!@ftp1.digi.com/support/Edgeport/5.10.26.0/40002537.exe
Then, of course, let me know how it goes.
Thanks for the reply. I will load the newer driver tomorrow morning and let you know how it goes.
We ran over the weekend, and the ports disappeared again, with the new driver installed. We are replacing the Edgeport/22c with another one from our stock. However, if this does not fix the problem, I am not sure what to do. Luckily this new computer and system is on a machine we are using in-house for a few months. Unless resolved within the month I will need to go with a different product, as it interrupts our production. Let me know of any ideas I can try if the problem continues with the new unit.
One more thing that came to mind. The symptom of this problem is the same as if the cable was suddenly unplugged. Though this is not physically happening, it seems to me that perhaps the new computer model I mentioned earlier may not be able to drive this Edgeport plus the additional 6 feet of USB cable. I will check the BIOS settings and power save features of the computer, and if all that checks out, try a USB power booster. In the meantime, if you think of anything, please let me know.
What do you mean by additional 6 feet of USB cable? What is the total length of the USB cable(s) between the Edgeport and the PC? Are they standard USB cable, or are there any “active extender” cables involved?
Is the Edgeport connected directly to the PC, or is it going through a USB hub?
If you haven’t already, go to the Properties of each of the USB Root Hub components in Device Manager, and look under the Power Management tab. If the option is checked to “turn off to safe power” (it says something similar), then uncheck that option for that USB Root Hub component, as well as all of the others.
What is the 50xxxxxx part number (and revision) of the Edgeport?
What is the Product ID (PID) of the Edgeport? To determine this, click the Information button at the top-right of the Edgeport Configuration Utility.
Tell me more about your application (what it does, exactly) and what the exact symptom is when you say it “dies”. For example, do you mean that it crashes, or do you mean that it just doesn’t communicate with the related serial device(s) any more?
What is the color and activity of the Edgeport’s System Status LED, immediately after the issue happens (before you unplug/replug it)?
Re: Edgeport/22c 301-1003-30 - Ports 2 & 3 dissapear after running a while
Posted: Jul 7, 2009 11:07 AM
There is a 6 ft USB extension cable plugged into the PC, which then plugs into the Edgeport. So since the Edgeport has about a 6ft usb cable, that would be around 11-12 ft of total cable between the Edgeport and the PC. No active extender cables involved.
No USB hub. See 1 above.
I will be able to check this sometime late this afternoon or tomorrow morning, the machine is down for maintenance.
4. What is the 50xxxxxx part number (and revision) of the Edgeport?
PN: (1P)50000813-01 C
SN: (S) W84975997
I will be able to check this sometime late this afternoon or tomorrow morning, the machine is down for maintenance.
6. Tell me more about your application (what it does, exactly) and what the exact symptom is when you say it “dies”. For example, do you mean that it crashes, or do you mean that it just doesn’t communicate with the related serial device(s) any more?
Well, our application dies or crashes because the communications port that it is using disappears while it is open and our application is communicating through it. It is a VB application that is tolerant of missed communications and garbled communications packets, but it was not designed to handle communications ports that are present and then disappear while in use.
According to the tech, the LED was not on at all immediately after the problem.
Ok. From the Power Management tab of the USB Root Hub I disabled all the power save features of each hub (there were like 6 or 8 of them). Then we started up running. I was leaving the floor and the problem happened again. No LED lite on the unit, and the Device Manager did not show the ports.
The PID was W84975997 - or at least that is the number I think you wanted.
Any other ideas?
Actually, that’s the serial number that you gave me, but it’s OK. I can still get the information I need based off of it. Your Edgeport is a newer model that uses the TI chipset. We’ve seen this “periodic lost ports” issue with some of these newer/TI units before and my best guess is that it has something to do with the hub chip that’s inside of them, since I don’t recall seeing this behavior, or having reports of it, with older Edgeports with the 930 chipset.
Considering that, one workaround would be using an older Edgeport that’s based on the 930 chipset. It would have to be a different model at minimum, considering that the Edgeport/22s is only available with the TI chipset. Are you only using the serial ports, or are you also using the two USB ports (the USB hub portion)? Do you have other Edgeport/22c units that you’re using (or planning on using) for this kind of application? Or is this just one particular Edgeport for one particular application?
Besides using a different Edgeport as a possible/probable workaround, we could collect a log file trace from you. That would give us a better idea of the problem. But, to be honest, I’m not certain that we’d necessarily have a fix in a month. We can try though.
> Considering that, one workaround would be using an
> older Edgeport that’s based on the 930 chipset. It
> would have to be a different model at minimum,
> considering that the Edgeport/22s is only available
> with the TI chipset. Are you only using the serial
> ports, or are you also using the two USB ports (the
> USB hub portion)? Do you have other Edgeport/22c
> units that you’re using (or planning on using) for
> this kind of application? Or is this just one
> particular Edgeport for one particular application?
I have a Rev B of the Edgeport/22c on my desk. I just had the tech pull the Rev C off the machine, and he will replace it with the Rev B. We have no record of the Rev numbers we have shipped out in the past, so this may be the first Rev C. We’ll see how the Rev B fares.
> Besides using a different Edgeport as a
> possible/probable workaround, we could collect a log
> file trace from you. That would give us a better
> idea of the problem. But, to be honest, I’m not
> certain that we’d necessarily have a fix in a month.
> We can try though.
I can get you the log file trace, just tell me how to get it. Getting an updated driver or something would be better in the long run rather than trying to figure out how to stock only Rev B’s. So a long term fix is good, as long as this Rev B fixes the immediate problem.
OK, let me know how the different rev behaves. I don’t think it will make a difference but it’s worth trying out.
There are two kinds of traces we can do. I think the more standard kind of trace using DebugView would be better to start off with.
Disconnect the Edgeport from the PC.
Be sure that Windows is configured to show file extensions, then navigate to the c:\windows\system32\drivers\ folder (c:\winnt\system32\drivers for Windows 2000) and rename the following three files with .backup extensions:
edgeser.sys -> (rename to) edgeser.sys.backup
32-bit:
ftp://austin:!15st3n!@ftp1.digi.com/support/Edgeport/5.10.26.0/Checked/edgeser.sys
64-bit:
ftp://austin:!15st3n!@ftp1.digi.com/support/Edgeport/5.10.26.0/Checked/edgeser64.sys
Save that .sys files to the \system32\drivers\ folder.
Re-connect the Edgeport to the PC.
Download the following .zip file and extract it to “c:\debugview”:
http://download.sysinternals.com/Files/DebugView.zip
Navigate to the c:\debugview folder and double-click “Dbgview.exe”. Click on “Options” at the top and UNCHECK “Force Carriage Returns” (if it’s checked). Also, click on “Capture” at the top and CHECK “Capture Kernel” (if it’s unchecked).
Re-create the issue-at-hand. In your case, this would be simply waiting for the failure to happen.
Immediately after the failure happens (or as soon as you observe that it happened), save the .log file in DebugView to a file name of your choice.
Zip up the .log file. I recommend using the free “7-Zip” software application to do this, if you don’t already have software to make .zip files.
Send me the .zip file.