My Name is Sebastian and I am new to this Forum.
The Reason I'll write is that I am currently breaking my head about a fact that I am unable to solve on my own....
But lets start with the original setup:
Intended by Design there was a i386 PC in my Industrial Machine which communicates via 4 RS232 Ports with different parts of this machine.
Serial Port one communicates with the Machine itsels via something like a Signal repeater
Serial Port two communicates with a controller for Signal processing
Serial Port three communicates with a Internet Modem
Serial Port four communicates with a USB (Backup Battery controller)
Software:
Everything runs on a proprietary Software completely developed by this Company, Base System is a shrinked down (compared by the files in the DOS folder) MS-DOS 6.22.
During roughly 2014 this PC Broke and the Company who built this machine sold something like a retrofit for this System. This New-System Contains of the following specs I know:
Base computing Module called PICMG 1.3 (Weird (and expensive) stuff, google it):
Intel Core I 3 (Third Generation)
1GB Ram
Intel HD Graphics
Intel Q77 Chipset
1 Serial Port Hard on the PCB (Used as Com1)
1 Serial Port Through a connector (Used As Com2
and 2x EXS-EX-40053 RS232 Isa Cards running a 16c550 Chip.
This System performs well until today, the only reason to virtualize is the fact that the system got a variety of Changes (for example some kind of remote desktop connection) in the past making it necessary to run on a newer System (Windows 10 in my case), and of course another reason is the fact that propably something will break in the future, which might gets hard to get some spare parts for it. For a virtualized system these risks are much lower since it can run on any modern platform.
For my retrofit I am Using a Dell Optiplex 8060 with 16gb Ram, a Chipset driven RS232 Port as Com1 and a USB to RS232 for the other RS232 ports (which I ignore for the moment, Mainly I am interested in getting Com1 working)
Now the problem:
I use DOS-Box 0.74-3 on this system but the Software refuses to receive any live data from the running machine. No RPM, Voltage or temperatures,.
Just to make sure: When I run the "Old retrofit PC" everything works out of the box and as it is intended. The only thing i exchange is the PC itself, everything else is running like before. Same RS232 cables etc.
Also what i get are some weird messages from DOSBox during the program start:
1DOSBox version 0.74-3 2Copyright 2002-2019 DOSBox Team, published under GNU GPL. 3--- 4CONFIG:Loading primary settings from config file C:\Users\SeMa Wind\AppData\Local\DOSBox\dosbox-0.74-3.conf 5MIDI:Opened device:win32 6Serial1: Opening COM1 7Serial2: Opening COM2 8Serial3: Opening COM3 9Serial4: Opening COM4 10DOS keyboard layout loaded with main language code GR for layout gr 11Serial4: Desired serial mode not supported (5,7,m,1) 12Serial4: Desired serial mode not supported (5,6,n,2) 13Warning: tried to activate hardware handshake. 14Serial4: Desired serial mode not supported (5,5,n,1) 15Serial4: Desired serial mode not supported (5,5,n,1) 16Warning: tried to activate hardware handshake. 17Serial2: Desired serial mode not supported (5,7,m,1) 18Serial2: Desired serial mode not supported (5,6,n,2) 19Warning: tried to activate hardware handshake. 20Serial2: Desired serial mode not supported (5,5,n,1) 21Serial2: Desired serial mode not supported (5,5,n,1) 22Serial3: Desired serial mode not supported (5,7,m,1) 23Serial3: Desired serial mode not supported (5,6,n,2) 24Warning: tried to activate hardware handshake. 25Serial3: Desired serial mode not supported (5,5,n,1) 26Serial3: Desired serial mode not supported (5,5,n,1) 27Serial1: Errors: Framing 4, Parity 23, Overrun RX:10 (IF0:0), TX:0, Break 2 28Serial1: Errors: Framing 3, Parity 18, Overrun RX:2 (IF0:0), TX:0, Break 3 29Serial1: Errors: Framing 1, Parity 16, Overrun RX:3 (IF0:0), TX:0, Break 0
Especially these framing error make me a bit curios here....
Anyways, this is what my config looks like, I used the Autostart informations directly from the original system 1 by 1.
[code]# This is the configuration file for DOSBox 0.74-3. (Please use the latest version of DOSBox)
# Lines starting with a # are comment lines and are ignored by DOSBox.
# They are used to (briefly) document the effect of each option.
[sdl]
# fullscreen: Start dosbox directly in fullscreen. (Press ALT-Enter to go back)
# fulldouble: Use double buffering in fullscreen. It can reduce screen flickering, but it can also result in a slow DOSBox.
# fullresolution: What resolution to use for fullscreen: original, desktop or fixed size (e.g. 1024x768).
# Using your monitor's native resolution (desktop) with aspect=true might give the best results.
# If you end up with small window on a large screen, try an output different from surface.
# On Windows 10 with display scaling (Scale and layout) set to a value above 100%, it is recommended
# to use a lower full/windowresolution, in order to avoid window size problems.
# windowresolution: Scale the window to this size IF the output device supports hardware scaling.
# (output=surface does not!)
# output: What video system to use for output.
# Possible values: surface, overlay, opengl, openglnb, ddraw.
# autolock: Mouse will automatically lock, if you click on the screen. (Press CTRL-F10 to unlock)
# sensitivity: Mouse sensitivity.
# waitonerror: Wait before closing the console if dosbox has an error.
# priority: Priority levels for dosbox. Second entry behind the comma is for when dosbox is not focused/minimized.
# pause is only valid for the second entry.
# Possible values: lowest, lower, normal, higher, highest, pause.
# mapperfile: File used to load/save the key/event mappings from. Resetmapper only works with the defaul value.
# usescancodes: Avoid usage of symkeys, might not work on all operating systems.
[dosbox]
# language: Select another language file.
# machine: The type of machine DOSBox tries to emulate.
# Possible values: hercules, cga, tandy, pcjr, ega, vgaonly, svga_s3, svga_et3000, svga_et4000, svga_paradise, vesa_nolfb, vesa_oldvbe.
# captures: Directory where things like wave, midi, screenshot get captured.
# memsize: Amount of memory DOSBox has in megabytes.
# This value is best left at its default to avoid problems with some games,
# though few games might require a higher value.
# There is generally no speed advantage when raising this value.
[render]
# frameskip: How many frames DOSBox skips before drawing one.
# aspect: Do aspect correction, if your output method doesn't support scaling this can slow things down!
# scaler: Scaler used to enlarge/enhance low resolution modes. If 'forced' is appended,
# then the scaler will be used even if the result might not be desired.
# To fit a scaler in the resolution used at full screen may require a border or side bars,
# to fill the screen entirely, depending on your hardware, a different scaler/fullresolution might work.
# Possible values: none, normal2x, normal3x, advmame2x, advmame3x, advinterp2x, advinterp3x, hq2x, hq3x, 2xsai, super2xsai, supereagle, tv2x, tv3x, rgb2x, rgb3x, scan2x, scan3x.
frameskip=0
aspect=false
scaler=normal2x
[cpu]
# core: CPU Core used in emulation. auto will switch to dynamic if available and
# appropriate.
# Possible values: auto, dynamic, normal, simple.
# cputype: CPU Type used in emulation. auto is the fastest choice.
# Possible values: auto, 386, 386_slow, 486_slow, pentium_slow, 386_prefetch.
# cycles: Amount of instructions DOSBox tries to emulate each millisecond.
# Setting this value too high results in sound dropouts and lags.
# Cycles can be set in 3 ways:
# 'auto' tries to guess what a game needs.
# It usually works, but can fail for certain games.
# 'fixed #number' will set a fixed amount of cycles. This is what you usually
# need if 'auto' fails. (Example: fixed 4000).
# 'max' will allocate as much cycles as your computer is able to
# handle.
# Possible values: auto, fixed, max.
# cycleup: Amount of cycles to decrease/increase with keycombos.(CTRL-F11/CTRL-F12)
# cycledown: Setting it lower than 100 will be a percentage.
[mixer]
# nosound: Enable silent mode, sound is still emulated though.
# rate: Mixer sample rate, setting any device's rate higher than this will probably lower their sound quality.
# Possible values: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716.
# blocksize: Mixer block size, larger blocks might help sound stuttering but sound will also be more lagged.
# Possible values: 1024, 2048, 4096, 8192, 512, 256.
# prebuffer: How many milliseconds of data to keep on top of the blocksize.
[midi]
# mpu401: Type of MPU-401 to emulate.
# Possible values: intelligent, uart, none.
# mididevice: Device that will receive the MIDI data from MPU-401.
# Possible values: default, win32, alsa, oss, coreaudio, coremidi, none.
# midiconfig: Special configuration options for the device driver. This is usually the id of the device you want to use
# (find the id with mixer/listmidi).
# Or in the case of coreaudio, you can specify a soundfont here.
# See the README/Manual for more details.
mpu401=intelligent
mididevice=default
midiconfig=
[sblaster]
# sbtype: Type of Soundblaster to emulate. gb is Gameblaster.
# Possible values: sb1, sb2, sbpro1, sbpro2, sb16, gb, none.
# sbbase: The IO address of the soundblaster.
# Possible values: 220, 240, 260, 280, 2a0, 2c0, 2e0, 300.
# irq: The IRQ number of the soundblaster.
# Possible values: 7, 5, 3, 9, 10, 11, 12.
# dma: The DMA number of the soundblaster.
# Possible values: 1, 5, 0, 3, 6, 7.
# hdma: The High DMA number of the soundblaster.
# Possible values: 1, 5, 0, 3, 6, 7.
# sbmixer: Allow the soundblaster mixer to modify the DOSBox mixer.
# oplmode: Type of OPL emulation. On 'auto' the mode is determined by sblaster type. All OPL modes are Adlib-compatible, except for 'cms'.
# Possible values: auto, cms, opl2, dualopl2, opl3, none.
# oplemu: Provider for the OPL emulation. compat might provide better quality (see oplrate as well).
# Possible values: default, compat, fast.
# oplrate: Sample rate of OPL music emulation. Use 49716 for highest quality (set the mixer rate accordingly).
# Possible values: 44100, 49716, 48000, 32000, 22050, 16000, 11025, 8000.
[gus]
# gus: Enable the Gravis Ultrasound emulation.
# gusrate: Sample rate of Ultrasound emulation.
# Possible values: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716.
# gusbase: The IO base address of the Gravis Ultrasound.
# Possible values: 240, 220, 260, 280, 2a0, 2c0, 2e0, 300.
# gusirq: The IRQ number of the Gravis Ultrasound.
# Possible values: 5, 3, 7, 9, 10, 11, 12.
# gusdma: The DMA channel of the Gravis Ultrasound.
# Possible values: 3, 0, 1, 5, 6, 7.
# ultradir: Path to Ultrasound directory. In this directory
# there should be a MIDI directory that contains
# the patch files for GUS playback. Patch sets used
# with Timidity should work fine.
[speaker]
# pcspeaker: Enable PC-Speaker emulation.
# pcrate: Sample rate of the PC-Speaker sound generation.
# Possible values: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716.
# tandy: Enable Tandy Sound System emulation. For 'auto', emulation is present only if machine is set to 'tandy'.
# Possible values: auto, on, off.
# tandyrate: Sample rate of the Tandy 3-Voice generation.
# Possible values: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716.
# disney: Enable Disney Sound Source emulation. (Covox Voice Master and Speech Thing compatible).
[joystick]
# joysticktype: Type of joystick to emulate: auto (default), none,
# 2axis (supports two joysticks),
# 4axis (supports one joystick, first joystick used),
# 4axis_2 (supports one joystick, second joystick used),
# fcs (Thrustmaster), ch (CH Flightstick).
# none disables joystick emulation.
# auto chooses emulation depending on real joystick(s).
# (Remember to reset dosbox's mapperfile if you saved it earlier)
# Possible values: auto, 2axis, 4axis, 4axis_2, fcs, ch, none.
# timed: enable timed intervals for axis. Experiment with this option, if your joystick drifts (away).
# autofire: continuously fires as long as you keep the button pressed.
# swap34: swap the 3rd and the 4th axis. Can be useful for certain joysticks.
# buttonwrap: enable button wrapping at the number of emulated buttons.
[serial]
# serial1: set type of device connected to com port.
# Can be disabled, dummy, modem, nullmodem, directserial.
# Additional parameters must be in the same line in the form of
# parameter:value. Parameter for all types is irq (optional).
# for directserial: realport (required), rxdelay (optional).
# (realport:COM1 realport:ttyS0).
# for modem: listenport (optional).
# for nullmodem: server, rxdelay, txdelay, telnet, usedtr,
# transparent, port, inhsocket (all optional).
# Example: serial1=modem listenport:5000
# Possible values: dummy, disabled, modem, nullmodem, directserial.
# serial2: see serial1
# Possible values: dummy, disabled, modem, nullmodem, directserial.
# serial3: see serial1
# Possible values: dummy, disabled, modem, nullmodem, directserial.
# serial4: see serial1
# Possible values: dummy, disabled, modem, nullmodem, directserial.
[dos]
# xms: Enable XMS support.
# ems: Enable EMS support.
# umb: Enable UMB support.
# keyboardlayout: Language code of the keyboard layout (or none).
xms=true
ems=true
umb=true
keyboardlayout=auto
[ipx]
# ipx: Enable ipx over UDP/IP emulation.
ipx=false
[log]
logile=D:\SCADA\DOSBOX\Logfile.txt
[autoexec]
# Lines in this section will be run at startup.
# You can put your MOUNT lines here.
KEYB GR
VERIFY ON
PROMPT $P$G
PATH = A:\;C:\;C:\DOS\
ECHO MSDOS V6.22 loaded
mount C D:\SCADA\DOSBOX\C
mount D D:\SCADA\DOSBOX\D
#PATH = A:\;C:\;C:\DOS\
C:\
#From here from SCADA Autoexec.bat
LH /L:0:1,45968 /S C:\DOS\SMARTDRV.EXE
PROMPT $p$g
PATH C:\DOS;c:\scada
SET TEMP=C:\DOS
LH /L:1,17184 KEYB GR,,C:\DOS\KEYBOARD.SYS
verify on
set scadaprogpath=c:\scada
set scadadatpath=d:\dat
call scandisk /all /autofix /nosave /nosummary
if NOT EXIST d:\dat.exe goto start
d:\dat.exe -d -o d:\ > d:\dat.log
del d:\dat.exe
:start
c:\scada\scada.exe
# Until here[/code]
I really hope you guys have ideas here since i am currently running out of ideas....
try plugging it in a different USB controller. Some don't work very well with USB to serial adapters. (at least that is what I think you are using)
I already did, I am currently use the one provided by the Intel Chipset provided with the Dell Optiplex PC.
Same behavior with "another" USB-RS232 Dongle.
These values are read out AFTER the Software was shutdown by using the MODE COM command on the Windows 10 Systems. They might aren't right. Especially with handshakes i am curios because in the Scada Software settings it says something about TSR YES/NO where i do not know what it could mean in a understanding for RS232 connections. Originally it is set to "Yes".
You could try setting the wanted serial mode in windows yourself, as for some reason, dosbox is not allowed/capable of doing so.
Of course, no clue if your program actually uses that specific serial mode (5,5,n,1) (but those errors are from serial 2,3,4) and not serial one that gives the framing error.
Unfortunately I receive the same results... I changed the windows settings to their corresponding onmes and also activated the hardware handshake (which doesbox mentions) but still have no improvement.
Attached you'll see the failure counter of the software.
Here I'll attach a code snippet where com1 is the main error:
You could try to change the speed of dosbox (cycles) to see if that changes the errors or not and another thing you could the dosbox setup on the old machine.
