SIOC Script - "powerful FS-gauge-Start"

Hi everyone,

a quick and easy question, so i hope. Maybe someone has this problem or ever had observed

Using OC- ServoCard and SIOC-Script.

The sioc-scripts are already done; e.g. using ASI,VSI,Flap,EGT... and working perfect !. But

If i start the Simulator (FS2004) and then the SIOC at second, the ASI´s (using two of them) moving fast up to the end and stay there at needles-stop-pin. The servo-motor continues, slight hum is heard.


if i open the SIOC-Card-test.exe i can bring them down.

But with next entry, maybe flap pos. 1; the needles running up again.

So therefore i have to make a takeoff-run until the ASI´s begin to start around 60kts; they come back and drive normal (take on ride from 60kts then). Now everything works.

I have to do this everytime -only- at new Start of FS2004 and SIOC- Connection.
The same if the Aircraft is on the Gate and if i gonna taxi out. Always that impulse.

Seems to me that the ASI gauges get a weird fs-impulse a the beginning.

Has anyone an idea or solution what that can be

Thanks - Cheers

Have you checked what values are being sent to the gauges at startup? Using the IOCPConsole will show you if an out of range value is being sent to the gauge. If not done already, you may need to set an initial value for the gauges at startup using the Var 0 construct.

David

Hi David,

thanks for fast responding. so i watched before at IOCPConsole through LogON - but there´s a big number of ranges. further on i´m not sure how to solve that. in the sioc- script i think isn´t a usefuel var 0 construct. under IOCPConsole just says e.g. V0005 (valor dec) 0. so i have to search again.

thanks a lot, appreciated,

max

Max

I just compiled and ran that code you sent me for the IAS and it seemed ok with no out of range values for the IAS gauge
Try cutting back your code to just the elements for the IAS gauge and take it from there.

David

Perhaps there is a problem in the interplay with the other gauges. But I can remember that this also occurred previously in single-handedly. So i gonna try few more variants. At this point i really don´t know why that occurs.

Thank You David, stay tuned !.

Cheers

i´m back and I've tried everything now.

i have changed the positions of gauges with each other in the script. therefore replaced numbers and assignments. also i tried the asi´s alone and then they work, but not with the others (other gauges) in one script. still the bug occurs by open fsSim2004 and opening SIOC.exe afterwards. don´t know which internal interface of that impulse is responsible. think there is no change in future about.

same can be said that there are not necessarily only the ASI´s - think that´s a general impulse problem, because the others coming up a little bit - but not so bad.

using: latest SIOC-Version 4,01 and reg.copy of FSUIPC 3.989x

what a crap.

Cheers

Max

Keep at it :)

As you know that the ASI code and gauge work properly on their own, then the problem lies in the rest of the code somewhere. Try adding one extra gauge at a time until the problem shows up again. The we can examine that code and search for the problem.

Regards

David

Thanks David.

So i´ll try. But i can also remember that the EGT´s have to come at first in the script- otherwise want not work (e.g. at the end or somewhere inside). Next place/step is the third and fourth row and then the problem exist/comes up as described.

So for better understanding ´ll send you the script at PM. Thanks for your help, David.

Best wishes, Max. :wink:

Max

Did you write the script yourself or get it from somewhere else? If it is your script then it should be a simple matter to code each gauge separately and check that they work before joining them together. I am convinced that that there is an error in the code causing your problems. Sorry, but just about to go out, so cannot respond again today

Regards

David

David

Thanks for help. It have time and it doesn´t matter if you´re not answering today. Some Information i compiled and these have been sent already. So may gonna find that bug, crap or whatever....:wink:

thanks, cheers

Max

Max

There was an error in your second script - you had duplicated var 0005 and var 0006, indeed it would not compile!! I corrected the errors by renumbering the variables in sequence. The script worked ok with no gauge "shoot up" on the ASI and the EGT gauge worked correctly when the engine was started

David

David

Thanks for letting me know. Indeed that´s true and i gonna have a look out. `ll inform you later on.

Thank You, great. Stay tuned

Cheers, Max.

David

I once looked at it. Indeed, that Var was/is duplicated due to make an example to show that´s equal which script i do use as follow. So what i want to say is, that i can use that last one or that above to bring them at Var0005 and Var0006. In my using script (i sent already) all be fine about Var and assignments/ numbering. So where ever the hook is - i don´t know.

So by time just have a look at it. Thanks for that.

Cheers

Max

Ok a misunderstanding over what you had sent me:)

I have run your latest script, the one you are using and which gives the problem. I find that it compiles ok and also shows the correct values for IAS in the IOCPConsole when the aircraft is stationary and at boot up.

Are you sure that your servos are rotating in the right direction? perhaps a zero IAS speed is showing up as a maximum on your gauge if it is rotating in the wrong direction? Forgive me raising this but I see no evident problem with your script, hence questioning the hardware

Try putting different values into var 0005 via the IOCPConsole and see how the gauge moves.

Regards

David

David

yeep, thanks for that information. so i cannot find any bug in the script either. maybe i turn the servo (without touching needle) back 180°. At first gonna put different values into var 0005 via Console and ´ll have a look how it moves.

´ll keep you informed.

Regards

Max

so but the question is, why they work perfect as stand alone ones..:shock:

Max

On my machine, with all the scripts that you sent me, the VSI value is always 0 at the start, that is why I question your servo rotation

David

Quote:

---

Originally Posted by fordgt40

Max

On my machine, with all the scripts that you sent me, the VSI value is always 0 at the start, that is why I question your servo rotation

David

---

so it do not depend on servo rotation - i tried it now - 180° back without needle - no way - same bug.

so use just the last script of sioc and think about that´s equal which gauge i gonna use at 0005 or 0006 after the ASI´s, always the same speed up problem. further i´ll give you a shot of iocpconsole while gauges are running 180° and back to 60kts. after speeding up the aircraft.

what a crap. thanks a lot and don´t worry about.

cheers, max

Max

So there is no doubt, can you be a bit clearer on what you did and the result?
If your full scale movement is say 400knots, did you enter 100, 200, 300 and 400 into var 0005 via the IOCPConsole. If so, how did the needle move for each value?

David

Var 0005 IOCPConsole

100 = 090
200 = 120
300 = 150
400 = 180

so i tested now. if i use the iocpconsole btw flight-sim can use the gauges - therefore do not have to start the test.exe to bring them back. further tests going on...

regards

Max

Thanks, so the rotation is ok. One last question, when you first run sioc what value do you get for var 0005 in the IOCPConsole?

David

Quote:

---

Originally Posted by fordgt40

Max

Thanks, so the rotation is ok. One last question, when you first run sioc what value do you get for var 0005 in the IOCPConsole?

David

---

#5 - DEC VALUE is 0 !

so if i use value 20 for var0005 the needle turning back to 60kts on dial.

Max

I am beginning to think that your code is ok, but there is something odd with the servo
A long shot - try removing the argument "Type 2" from your USBservos variable definition as it is not implemented yet, according to OC

David

Max

Just come across a sioc script for servos which uses the argument Type 1 !!!! Try that as well :p

david

talking about that ?

1: .......Output 1, PosL 0, PosC 562, PosR 988, Type 2

2: .......Output 3, PosL 0, PosC 512, PosR 557, Type 2

Max

Yes try Type 1 and then try removing the Type argument

Also, I recall elsewhere on this forum advice that you should not define two variables to the same FSUIPC offset! You have both IAS and ASI variables linked to the same FSUIPC offset Try temporarily removing the ASI code from your script and see if this makes any difference.
Beginning to run out of ideas now :)

David

david

so it doesn´t matter what ever i change.

if i change to nothing instead Type 2

or

if i change to Type 1

always the same speed up

Cheers

Quote:

---

Originally Posted by fordgt40

Max

Yes try Type 1 and then try removing the Type argument

Also, I recall elsewhere on this forum advice that you should not define two variables to the same FSUIPC offset! You have both IAS and ASI variables linked to the same FSUIPC offset Try temporarily removing the ASI code from your script and see if this makes any difference.
Beginning to run out of ideas now :)

David

---

ok. ´ll do and keep you informed.

mmh, that should mean, that´s not possible to use an ASI maybe with one backup-ASI in the Cockpit ?? let´s see what happend

Max

No, you can use both gauges, just need to change the coding slightly. Lets see what happens

David

david

uups that´s very weird, indeed.

so first i removed that ASI -script (placed on Servocard 3) --> no difference; also speeding up

so then i removed that IAS -script (placed onServocard 1) --> also no difference; speeding up although it is not driven according to script; häh ? how can that be ??

the names ASI and IAS i had to do - because otherwise also no work (if it´s the same: IAS and IAS)

that´s very weird

regards

Max

I should check again your connections from the gauges to the servo card and the numbers you have given them in sioc.

David

david

uuuups, even if i remove both speedindicators - that´happens ?????

that´s crazy

cheers

Have you rechecked your connections as suggested?

David

yes - rechecked - but i´ll do again...wondering that the servos running up while opening the sim or start sioc - even the speedindicators are removed. maybe i have to rename all again - just cut out from script. maybe that´s why.

so ´ll keep you informed.

thanks a lot for your work, david

cheers

So all is rechecked and and numbered exactly. the positions in the script and on the card are identical.

thanks again, regards