Siemens Primergy TX150S
Windows 2003 Server (Standard Edition)
Scales:
Opus
Leon
Case:
At this peticular site we have two scales (measuring the weight from trucks) and sends this information to an application. This is done via the COMs, COM 1 and COM 3. COM 3 and COM4 ports are created with the help of this Digi card.
The old scale was on COM 1 and has been working perfectly. When we then got this Digi card and connected the second scale to COM 3, everything went bad. One of the most reacuring things is the mouse “flipping” out and we also lose the weight from the COM 1 scale. Disconnecting scale 2 (on COM 3) and it works fine again.
We have input from both scales, and its the correct input - application is setup correctly. We just can’t get them to dance together.
I’ve seen people on this forum mentioning IRQ setups and that the card might not even be supported by Win2003.
On a general note, it’s seems to me that there is a conflict (duh), it’s the trying to figure out what and where that is the problem.
Has anyone had a similiar problem? Or might have any ideas on where to start looking for the problem/solution.
I did not install this card on this peticular machine so I can’t say if it’s installed correctly. It ended up on my table in the end anyway (as things usually do)…
Thank you for providing enough details about the situation so that I can offer some advice, potentially resolving the issue.
The adapter should work fine in all versions of Windows Server 2003, provided the latest drives are installed.
I do not see which driver version you have installed, so, my first recommendation is to get the latest drivers installed. I’ll attach a file with installation instructions. It contains a link to get the latest drivers.
Please follow the instruction to get the new drivers installed. This will eliminate the possibility of the race conditions from occurring.
In this driver there is an option for the driver called Skip Enumerations.
I recommend enabling this option for each of the AccelePort Xp ports which do not have a modem or a printer attached to it. This stops Windows from querying the ports and potentially interfering with your application. Windows will sometimes misinterpret inbound data on the port and thinking the input is from a serial mouse, it assigns a mouse to the port causing many problems.
Did everything you gave me instructions todo and voila - it worked. It turned out the driver installed was very old. Sloppy installation in the beginning.
If the skip port enumeration is enabled, and if you have rebooted and the problem still exists, then Windows has probably already added the non-existent devices added to the device manager.
You can try uninstalling any of these fictitious devices from the device manager. Windows should no longer try to detect or identify the devices attached to the ports.
Remember, the option is settable “per port”, so enable it for each port.
It is too bad Windows doesn’t accurately identify the devices.
