Simatic Pc Adapter Usb Drivers Windows 10 64bit.zip

0 views

Skip to first unread message

Tabita Knezevic

unread,

Aug 3, 2024, 3:04:20 PM8/3/24

to restbalichun

I cannot get my 6ES7972-0CB20-0XA0 to work. I have downloaded drivers and tried installed. Still not working.
All I see is this:
Online: The local MPI address for the programming device/PC is higher than the maximum device address or the wrong transmission rate or wrong interrupt is set.
I ma running windows 10.
HELP

There are several situations where this problem occurs:
The MPI address setting conflicts with the MPI address of other devices
The MPI communication rate is set incorrectly
PG/PC settings are incorrect

I have bought your 6GK1 571-0BA00-0AA0 PC ADAPTER USB A2, and installed drivers from the internet, and it shows in device manager as usb pc adapter but when I try to connect to PLC s7-200 with simatic step7 v4.0 i cant conect because it requires to set com port in pg pc , but I only have usb .
Help please!

Better to buy an original Siemens MPI adapter. My amsamotion mpi adapter will stop during copying of blocks(if copying over a thousand blocks), the mpi led will go off, I need to unplug and re-plug it to work again.

I've had this problem for a long time now and had contact with the display manufacturer, MSI support and i also tried numerous forums to get a solution, which obviously did not help since i'm writing this here. It was okay for watching videos so i just gave up in 2017, but the situation has changed and i would like my secondary display to work correctly again, because pdfs and programming scripts are horrible in 640x480. I've been looking around again and tried different approaches and i am at a point where i don't know any further.

There is only the 640x480 (60 Hz) resolution available for my 2nd display. Main display works fine. Setting something else with adrenalin (custom resolution) or tools like CRU does only result in "no signal" error on the display. Windows device manager shows 1st display as PnP monitor and 2nd display as non-Pnp monitor.

After fiddling with settings for a few days again, deleting and installing drivers and changing resolutions via CRU, i have now reached a stage in which the display hast the correct solution after startup juuuuust >>until radeon software loads

If it does, then that indicates that your fujitsu monitor is not 100% compatible with Windows 10 or you need to install the original 2006 Monitor H19-7 driver and see if it shows up as Fujitsu Monitor or possibly use a different Video port from your GPU card as a test.

DVI is a digital signal in the same format as the video portion of HDMI. The difference is that DVI doesn't carry the audio signal like HDMI does. This means that if you are only using the video signal you can use a simple DVI to HDMI plug adapter that changes the physical connections. If you want to go from a DVI source with audio, you'll need an active converter to combine the video signal from the DVI source and the audio into the HDMI signal.

Went to Fujitsu and inputted a slightly different Model E19-7 and downloaded their Windows 10 WHQL driver from 2015. See if it will work on your Monitor. The E19-7 seems to have the same Resolutions as your older model: Fujitsu Technical Support pages from Fujitsu Fujitsu Continental Europe, Middle East, Africa & India

I downloaded and attached it to this post if you want to download it to your computer and see if your Non-PNP Monitor now shows Fujitsu Monitor. Then see if you are able to get the correct Resolution on your Fujitsu Monitor.

This tech site has some troubleshooting tips on how to resolve NON-PnP Monitor in Device Manager. By the way that is the reason why you have low Resolution on your Monitor: Windows Suddenly Does Not Recognize Monitor, Stuck On Generic non-PnP Driver at Low Resolution

Which seems to be why the download-link on their page does not give a result for the H19-1. I've tried the original .inf i had stored but it only includes the name-change and no further information about resolution or timings.

It also works on my system (rx 480) in 1280x1024 for a few seconds during the time of the login (to windows) and the start of the radeon software. The moment the radeon software loads up, the 2nd display goes to either 640x480 or "no signal" mode. So it works with win 10 until radeon software does something... or windows does something to the radeon software...

Once it finishes uninstalling the current AMD Driver in Safe mode and boots back to Windows Desktop, still with the Internet disconnected, delete the AMD Installation folder C:\AMD if it was created before.

Now install the full AMD Drive package you downloaded manually from AMD Download page. Not the express package. Run the package and if it installs correctly again delete C:\AMD folder and reconnect the internet.

Which reminds me, because of it's WHQL certification, that i also went to the bios settings to disable the "Win10 WHQL-support "option to see if it makes a difference during or after the installation process. It doesn't. well ...regarding this problem.

You cannot use DVI and HDMI video outputs at the same time. Use only HDMI port or use only DVI port. Your GPU manufacturer's DVI support does not indicate that the product you have has multiple support simultaneously. And this problem is not related to drivers. Almost all new generation GPUs do not even contain a DVI port. A converter adapter can be used for the DVI-supported monitor, but no one can guarantee it.

The combination of of 2x PA238 works fine in either combination (except HDMI, possibly because the cable seems to be defect; single monitor on HDMI did not work). 1xDP and 1xDVI-D works, but on the DVI-D-connected monitor the color- and pixelformat-information is missing in radeon software and MonInfo. Sadly i forgot to take a look at the device manager to see if the DVI-D is listed as Pnp or non PnP-monitor). Will do again when i get the chance.

So ... maybe there's something going on with the EDID, which in turn leads to some sort of default monitor, which then leads to some conflict between some windows magic and/or radeon default monitor stuff? As written before it works for a brief moment until the radeon software loads up, if i override the resolution with CRU before the restart.

The driver won't install due to a missmatch with the hash, unless forced to. After a restart it did not automatically change to PA238, but after specifically updating the driver for each entry in the device manager it worked, no surprise there.

If you can connect PA238 and H19-1 models to your graphics card one by one without any problem, it is not necessary to search for the problem with the display driver or with the graphics card. So there is probably incompatible. And an converter adapter can solve your problem. But I cannot guarantee it. Adapters look like that...

If graphics cards with DVI(-D) support were produced for multi-display support, these graphics cards would be released with more than one DVI port. But in almost all of the newly released graphics cards, I could not see any DVI port. Existing types only have "one" port.

Actually I changed too many graphics cards. There were single VGA outputs, VGA + DVI outputs, VGA + DVI + DVI-D outputs, DVI + DVI-D outputs. But I did not have a graphics card with two DVI-D outputs. Multi monitor support has already come up with HDMI for me.

Well the thing is, that the GPU is able to produce a resolution of 1280x1024 on the H19-1 at DVI-D, but only if you force it to do so via CRU and only UNTIL radeon software loads up. As soon as the software comes along it goes either to "no signal", or to 640x480 depending if 1280x1024 was forced via CRU beforehand. I'n no expert in these kind of things, some basic knowledge about microcontrollers from school at best, but to me it looks like it is able, but not allowed to. Wether it is because the software says it's not supported, to old, can't read EDID or some feature that requires something the monitor can't deliver, i don't know.

After deinstalling monitors and reinstalling drivers radeon software still did the 640x480 and recognized it as H19-1, but now both overrides work (CRU software or custom resolution in radeon software package) and won't revert to 640x480 after radeon software launch.