kadda

and another one :)

:thumbup:

Hello, did you followed tye steps copiyng the files in the saved games/.../script folder? Did you enabled the interactive control that is in tht folder? What about your export file?

i know this guy, https://forums.eagle.ru/member.php?u=62324 may be he can help you ...

i m following

i can may be help with that, in my case the line of sketch for controling the motor with the joystick were making it react exactly like you said it was with yours, so in my case i added a function for the button that s in the joystick so it can make the motor move only when the button is pushed in the same time i move the stick, may be you need to modify a little the lines controling the zeroing detector ...

Thank you :) i will do my best, thanks to IAN and warhog too :)

good luck, and if you need something let me know :)

i already use ikarus for the leds and helios for the instruments in wainting for the moment i finnish all the gauges, so if you need any help let me know, and they are working well, so if you need some thing just let me know and if i don t answer just PM me :)

can you explain me what do ou mean by "plane ID" exactly ? sorry i didn t saw this part of the question ... i thought that you need only the dimentions of the instruments ...

My Altimeter is working very well, with manual zeroing using a small joystick :)

here s the link to the video ... for the altimeter the gauge is 70mm

oups the first one !!!

oups the first one !!! https://vk.com/video26022551_456239019

Good morning guys and thank you very much IAN for answering, i ll correct my l-39 file and send you a link by pm of dcs-bios for verification this afternoon.

Hello every one, i ve finnished yesterday adding the instruments for l-39, but i ve one question to ask, When i ve compared for ex the ka50 lua file in bios lib i ve found that for ex IAS gauge it like that «defineFloat("IAS", arg num, {0,1},...."» For the l-39 in the output value {0,...,...,...,...,1} So my noob question of the day is, have i to put all the intermediat output values or just the 0 and the 1? Thank you for the futur answer(s), my altimeter is working fine thanks to IAN and Warhog, ian i ve modifyied the mainpanel init.lua so now value from dcs on land is «0» :) Cheers

Hello every one, i ve finnished yesterday adding the instruments for l-39, but i ve one question to ask, When i ve compared for ex the ka50 lua file in bios lib i ve found that for ex IAS gauge it like that «defineFloat("IAS", arg num, {0,1},...."» For the l-39 in the output value {0,...,...,...,...,1} So my noob question of the day is, have i to put all the intermediat output values or just the 0 and the 1? Thank you for the futur answer(s), my altimeter is working fine thanks to IAN and Warhog, ian i ve modifyied the mainpanel init.lua so now value from dcs on land is «0» :) Cheers

Thankd warhog for answering, and my stepper choise is due to your expertise :) the motor that i ll use for real is the M35SP-11NK from mitsumi and it is fast

yes i m using the cockpit argument 52, in the instrument that i get from the simulator, the meters and km gauges are related mechanically to make and the shaft is related with the meters gauge ... so if i use the 53 arg witch is for meters and map that with 2048 it would be like a max step value that the motor can t go so i took the 52th argument and amplified his mouvement to simulate the 53th the terrain " Batumi " that i use for my tests is 11m MSL

code: #define DCSBIOS_IRQ_SERIAL #include <AccelStepper.h> #include "DcsBios.h" #define FULLSTEP 4 #define motorPin1 3 #define motorPin2 4 #define motorPin3 5 #define motorPin4 6 // Initialize with pin sequence IN1-IN3-IN2-IN4 for using the AccelStepper with //28BYJ-48 AccelStepper Motor1(FULLSTEP, motorPin1, motorPin3, motorPin2, motorPin4); void onVd20Change(unsigned int newValue) { unsigned int newPosition = map (newValue ,0 , 65498, 0, 40960); Motor1.moveTo(newPosition); } DcsBios::IntegerBuffer vd20Buffer(0x3200, 0xffff, 0, onVd20Change); void setup() { DcsBios::setup(); Motor1.setMaxSpeed (800); Motor1.setAcceleration(800); } void loop() { DcsBios::loop(); Motor1.run(); } ------------------------end of sketch------------------------------- i m talking about the altimeter for the L-39, so i followed the developer guide and your advices to add a new module to DCS-bios with the starting adress "0x3200" for the moment i'm trying to master the programing part it s why i didn't add other instruments the stepper that i use for experiments is the "28BYJ-48" it makes 2048 steps per revolution, and i added the argument for the km indication, the instrument it self is maked to show 20km so it s why i have 40960 as a max step value. at the start of the simulation the stepper makes a little less than 20 revolutions because of the " Value From DCS : 65498, then 20 revolutions back when that value passes by 0 then it work as it should be ... i m more than ready to share all the changes that i ve made, it's just that i added just one instrument " altimeter " for testing and mastering the beast at the present moment, and i'll add all the other instruments in the futur few day ( i m speaking only about the instruments not about the other controles for the moment ) then i ll have some thing relatively significant to share with great pleasure on GitHub

Hi every body, can some one tell me why my starting value is not 0 but 65498? and if possible how can i make it back to 0 ? thanks

Thanks for all the help my altimeter is working exelent Cheers

Sorry about asking many time the same question i didn t see the complete answer :)

Thank you for the answer :)

The 0x3200 is the adress for the L-39 that i m adding to dcs bios and the 40960 is my mistake i thought «wrong» that i need to specify number of steps for 20 revolutions of the stepper but i need only 2048 steps per rev So i need to run the motor from the loop? Does dcs bios support arduino mega 2560 rev3? thank u very much for your answer