HSI Pulse Range Counter Display - How to manipulate in SIOC?

[Boeing 747 Flyer]

Hi Nico,

Well what can I say. It is absolutely brilliant. Thanks so much!

Changing it to 45 pulses/sec has solved EVERYTHING. I mean everything!

Not a single error, it never stops being called, and it accruately reports the station be it 1.6 or 51.3nm away. It also perfectly resets to 0 even if I'm in the middle of flying towards the VOR and loose the signal.

There really is nothing left to fix IMO. A few problems may crop up, but there are none at the moment, it just works brilliantly.

Thanks so very, very much!

Regards,

Jack

[kiek]

Hi Jack,
CONGRATULATIONS!
Enjoy your HSI.

I will add the SIOC code of the Pulses subroutine to my howto page.

Let's close this thread now. It is very long already.

regards,
Nico

[Boeing 747 Flyer]

Hi Nico,

Thanks so much, but you deserve most of the thanks for your oustanding efforts and fault-finding.

Should we submit a bug report to OC regarding the SIOC issue?

That's just the glideslope and localiser motors left to do on the HSI!

Regards,

Jack

[kiek]

Hi Jack,
I have added a HowTo example about making a led blink a fixed number of times to my website.

Do you submit the bug report to OC?

regards,
Nico

[fordgt40]

Nico, Jack

Some interesting coding - thanks
Another application of the principles of sending pulses could be dc motor control through one of the proprietary motor control chips that act upon ttl level logic on/off signals and variable durations - could be cheaper than buying an OC card.

David

[Boeing 747 Flyer]

Hi David,

I had thought about using the PWM technology in the motors card, but it simply wasn't precise enough.

I myself had developed a little test circuit with a potentiometer, capacitor and PIC chip. If I put the potentiometer in "position X" for 10 seconds the HSI would count to 200, but if I did it again, it would count to 213, etc.

Nico's script makes sure we control the EXACT number of pulses sent, so that it never goes off track (even by 1).

Nico, just a small note:

I noticed one condition in which the script struggles. It is not our fault, but that of FSUIPC/FSX.

Whenever a frequency is changed, the Offset in question changes to 0 for a split second, then back up to whatever distance it is away.

This change to 0 affects our script, because the HSI tries to go to 0, and then back up to X miles. Obviously, as I said, sending two different instructions "confuses" the HSI.

I am wondering, if there is any way around this? Maybe to tell the HSI to "ignore" the temporary value of 0. Or, another idea, we make the pulse rate so fast, so that it does change to 0 and then back up to whatever extremely quickly (maybe 1000 pulses/sec, I don't know).

Anyway, just a minor problem. It is nothing to do with the script; just the offset by which it is governed.

Regards,

Jack

[fordgt40]

Hi Jack

I understand why you did not use PWM. I was thinking more about general (undemanding!!) motor control where the pulse system you have developed with Nico could easily control motors with inexpensive chips.

Regards

David

[Boeing 747 Flyer]

Ahhh I see, indeed!

Is there a "limit", or at least a guideline, to the maximum speed of the pulsing? I want to increase it but do not wish to damage or destroy an ouput.

Jack

[fordgt40]

Jack

Sorry, but I have not developed this thought any further. I would need to check the datasheets of the motor contoller chips to see what are the parameters. It is certainly feasible as I did a small experiment some while back using SIOC to send control pulses to the motors - though it was very hit and miss due to my crap coding at the time

David