help with Saidis program for Simovert 6SV1 controller for Siemens 5134WS20 motor

[ProEV]

Hi,

SAIDIS is a DOS program used to adjust parameters on Simovert controllers. It communicates over the serial port. It was written back in the day and gets confused on more modern serial ports-probably because of the FIFO buffer that later serial ports use. I used to run it on old two old Win 98 computers but they both are gone.

I am trying to get it to work on a Windows 11 computer using vDOS, DOSBox 0.74-3, and DOSBox-X. I am using a USB to Serial adapter.

In each DOS, I can get SAIDIS running and saying in the SAIDIS window 'Connection OK' but then it tells me the data is incorrect. My conclusion is that the serial connection is working but I am having the FIFO problem.

Has anyone solved this problem? Does anyone know what communication protocol SAIDIS is using? My SAIDIS is 2.0. Does anyone have the 3.0 version?

Thanks

Cliff

 

[amberwolf]

It may not be possible to disable the FIFO with a USB-serial adapter, but with "actual" serial ports connected to the PCI (E) bus, it might be, if that's an option with your computer.

https://www.sevenforums.com/hardware-devices/103451-rs232-problem.html

There are other pages describing similar problems and solutions found in a google search; perhaps one of them has a solution you can use for the USB-serial problem?

https://www.google.com/search?q=disable+fifo+in+serial+%22usb%22+windows10


Did you ever get anywhere with this?
https://www.diyelectriccar.com/threads/evdl-using-a-serial-port-sniffer-to-replace-siadis-program.2837/


FWIW, I have a connection problem to an old sound board that is probably caused by a similar issue, but in this case it seems to be that win10 actually disables some drivers from being able to be used by programs to actually transfer data, even though they show up and respond to testing. :/ That could also be your problem, but only if the USB-serial port doesn't work for other devices' programs either. The only solution I know of for this is to use a different hardware port that uses a driver win10 doesn't disable. (not possible with my board; it's built in to the hardware, and the software expects that hardware).