VOGONS

Timing problem related with directserial

Topic actions

First post, by yagoo

Posted on 
User metadata
Rank Newbie
Rank
Newbie

Hello,

I use dosbox with a program to connect via com port to the computer(ECU) of a car.
The problem is that ECU needs an inicialization procedure with very strict timings - something like that:
set break on for 300ms(+/- 1ms), set break off for 25ms(+/- 1ms), set break on for 25ms(+/- 1ms) and start writting requests.

It seems that program cannot achieve those accurate timings when working under DosBox.

Is there a way to fix that?

Thanks,
yagoo

Reply 1 of 3, by h-a-l-9000

Posted on 
User metadata
Rank DOSBox Author
Rank
DOSBox Author

You could try a build with the timesync patch or increase dosbox priority in task manager.

Did you have a look at the timing the program generates with Dosbox?

1+1=10

Reply 2 of 3, by yagoo

Posted on 
User metadata
Rank Newbie
Rank
Newbie

Actually it seems to be more complicated problem.
I don't see in the serial log where the program makes inicialization by set/clear break, while I am sure that it should do it.
Do you know if dosbox supports com break?

Also I cannot find that timesync patch - can you give me alink?

By the way I use your timer patch build from 08.04.2006 - great work!
Task manager now shows 1% system usage while using the base build it is 10%.

Last edited by yagoo on 2006-05-09, 07:31. Edited 1 time in total.

Reply 3 of 3, by h-a-l-9000

Posted on 
User metadata
Rank DOSBox Author
Rank
DOSBox Author

Dosbox 0.65 does, 0.63 doesn't have com break.

Timesync: Actually I don't know myself, just read that such a thing exists and thought it might help.

Unfortunately that timer patch build has a bug in it...

1+1=10

Go to top of page Go to top of page
Back to DOSBox General
Close window
Close window