🚀 go-pugleaf

Thanks for the answers.

I could see with an osciloscope that the Low-Hight state which i want, i can 
make ik sending a 0x0 using as baudrate of 360. That is something ;-) . 
When i send the 0x0 i get a Low signal for exact 25 ml.  The problem is to 
calculate the time after that happens.

The duration of send a 0x0 is (if i understud well)      (1/360)*1000 = 
2,7777 ml . so, in order to send something in the next 25 ml shall the 
program wait theoretic

This hardware is a standard device to communicate to a Car.  The name is 
K-Line and in order to start a comunication must be sent a 25 ml low, 25 ml 
hight and some start bytes after that.  But it must be just 25ml, if it is 
not exact (+/- 1 ml) don't work.  I find a sample program mad in Delphi 
(only the Exe file) and i see in the osciloscope that it make just that what 
i want, so must to be a simple way.

"Bob Gonder" <notbg@notmindspring.invalid> schrieb im Newsbeitrag 
news:jf9ek095ohfqfgl304ncsf62mhc340nu88@4ax.com...
> Eelke Klein wrote:
>
>>Notice that these signals will never be completely low or completely
>>high they will allways be a series of pulses zero bits are short pulses
>>and 1 bits are long pulses. The start and stop bits have fixed lengths.
>
> No pulses.
> You're probably thinking modem signals where the frequency shifts
> according to bit state.
> The RS232 voltage goes high or low for the duration of the bit time.
> The reader is supposed to wait for the middle of the bit time to read
> the value. This gives the signal the maximum anount of time to
> overcome line capacitance, and achieve a non-ambigous signal state.
>
>>> Can i maybe at 10472 in someway make the same low-hight behavior?
>
> No, then it really would look like pulses.
> The start and stop bits are both high. So a 0 looks like goal posts.
>
> Doesn't the OEM have windows drivers for this?
>
> I get the feeling this is ancient hardware and MS isn't going to allow
> very nice support for it.
>
> You could also try sending a "break" signal.
> It's been too many decades, and I never used them, but perhaps this is
> the signal the OEM contemplated being sent.
> I no longer have my hardware manual for the UART, but a communications
> library says that a Break is  spacing (0) for more than a character's
> time.  It doesn't say how much more, or if it spaces for wall-clock
> time, or just a bit more than a char time. In any case, I don't think
> it would have any start/stop (high) bits.
>
>