7rooper

This year has taken so many celebrities lives... so sad...

Can't wait for it!

It worked now. It just needs a little bit of adjustment to my hardware needs like you said. The problem was in the BOLD line of code. How could I be so blind??? I feel stupid.. Thank you all for your help.

Great job! This will bring many more modellers who can't afford 3dsMax to DCS

John, thank you very much for your detailed explanation. I'm sorry for mispelling your nickname. I have followed your work and it has inspired me to build my instruments in a very organized and space efficient way but our electronics approach seems different for now...mine being simpler For this engine cluster I want to connect three Pro Minis communicatong through I2C, each one driving 4 steppers. I just wanted to try with one before programming the other two using the wire.h library. How many Arduinos are you using to handles all these Easy Drivers? Are these drivers daisy chained or each one must be connected to the microcontroller?

Remember that not everybody has a Warthog HOTAS with enough buttons...

Warthog, I quoted the part where Ian said that he and you created a VID29 class and posted the same code I'm using. That's why I'm trying to get some help from this DCS-Bios thread. I know how steppers work and know the accelstepper library quite well. It's just that I don't understand your code. I don't see where to declare the Arduino pins like I do it in the accelstepper library using this line of code AccelStepper APU_EGT_stepper(4, 13,12,11,10); Could you please elaborate it for me or telling what's wrong with my implementation. I'm driving my VID29 steppers directly from the Arduino.

As far as telling if the stick is in the center is not a problem because you have the visual feedback of your stick position in your virtual world. For rotating knobs or using the HOTAS hats you can bind the Touch buttons to this increase/decrease functions and you even have a thumb joystick in the Touch controllers to slew your sensors and trim your aircraft. It won't be like operating the real aircraft but you will have a greater level of inmersion than anything seen yet. The Touch can "track" your fingers by telling which one is pressing or depressing a button. So it could work... However, an improved Leap Motion could be the real solution to this

The more natural use for the Touch controller would be flying without a physical HOTAS. You just press a Touch button to enter "grabbing mode", then move your hands near the stick or throttle and a snap function renders your hands as if you have grabbed the grip. Press the button again and your hands are free to reach out a switch or button and by pressing the Touch trigger button you could flip or press them How about that?

Hi, Ian My VID29 used to work great with DCS-Bios previous versions but I can't get it to work using your new VID29 class. What could be wrong with my code. Maybe it's the part where I should describe the pins where the stepper is connected in the Arduino #define DCSBIOS_IRQ_SERIAL #include <Servo.h> //This library needs to go before DcsBios.h for the servos to work #include <DcsBios.h> #include <AccelStepper.h> struct StepperConfig { unsigned int maxSteps; unsigned int acceleration; unsigned int maxSpeed; }; class Vid29Stepper : public DcsBios::Int16Buffer { private: AccelStepper& stepper; StepperConfig& stepperConfig; unsigned int (*map_function)(unsigned int); unsigned char initState; public: Vid29Stepper(unsigned int address, AccelStepper& stepper, StepperConfig& stepperConfig, unsigned int (*map_function)(unsigned int)) : Int16Buffer(address), stepper(stepper), stepperConfig(stepperConfig), map_function(map_function), initState(0) { } virtual void loop() { if (initState == 0) { // not initialized yet stepper.setMaxSpeed(stepperConfig.maxSpeed); stepper.setAcceleration(stepperConfig.acceleration); stepper.moveTo(-((long)stepperConfig.maxSteps)); initState = 1; } if (initState == 1) { // zeroing stepper.run(); if (stepper.currentPosition() <= -((long)stepperConfig.maxSteps)) { stepper.setCurrentPosition(0); initState = 2; stepper.moveTo(stepperConfig.maxSteps/2); } } if (initState == 2) { // running normally if (hasUpdatedData()) { unsigned int newPosition = map_function(getData()); newPosition = constrain(newPosition, 0, stepperConfig.maxSteps); stepper.moveTo(newPosition); } stepper.run(); } } }; struct StepperConfig stepperConfig = { 620, // maxSteps 1000, // maxSpeed 1000 // acceleration }; // define AccelStepper instance AccelStepper stepper(AccelStepper::DRIVER, A2, A4); // define Vid29Stepper class that uses the AccelStepper instance defined in the line above // +-- arbitrary name // | +-- Address of stepper data (from control reference) // | | +-- name of AccelStepper instance // v v v v-- StepperConfig struct instance Vid29Stepper RFAN(0x10a4, stepper, stepperConfig, [](unsigned int newValue) -> unsigned int { /* this function needs to map newValue to the correct number of steps */ return map(newValue, 0, 65535, 0, stepperConfig.maxSteps); }); void setup() { DcsBios::setup(); } void loop() { DcsBios::loop(); }

Thank you all for all your responses. As a matter of fact I'm an electronical enginner but I have never used this bus before. The good thing I see it's that the front pin header in the Pro Mini can be used to make the RS485 connection. This makes the retrofitting easier and therefore make the Pro Mini more convenient because in many panels I don't have any more I/O pins available

How do you suggest to connect 30+ RS485 devices with an Arduino Mega? I'm converting all my panels from homerun wiring to modular each one with its microcontroller/arduino mini nano and your wonderful DCS Bios and I need to have this connectivy issue resolved asap Thank you very much for your help, Ian

Well... I supposed this is the end for my goal of having ALL the panels connected through USB... I really thought the limit was going to be the max current and I had modified two 10-port USB huds to allow external power only with a beefy PC PSU... Ian, what do you mean with DCS-Bios 2.0 will allow to talk to multiple comm ports? With DCS-Bios 0.2x I had 5 panels running connected via USB using different comm ports. Also, when you say that Windows renumbers the panels at will because they don't have proper serial numbers, do you mean that they don't have vendor id as a plug and play usb device?

It seems that this instrument won't fit in the multigauge backplate. Check the reference document that Lynx provided for actual distance allowed between the standoffs so it slides in the backplate cutout

I got it to work using IRQ instead of DEFAULT like the comments in your example sketch stated!!

Whomadewho, your pit is shaping up excellent. btw, your CMSC looks badass but I noticed the dimmensions and letter spacing were rearranged to fit the OLED screens (0,96" I suppose..). Did you have to steer away too much from the real size?

Hi, Gadroc! I'm interested too. Please share your notes and knowledge ;)

This fixed DCS BIOS too.. Thank you!

It makes my day to see a new cockpit build thread! Great job!

Painfully slow download... but low fps with Oculus have been reported and I'm not sure to let it update now...

:doh:

This have been discussed before and I don't recall anyone from ED talking of future plans for an entire world. As a matter of fact, it seems that in DCS, even though out of bounds terrain is procedurally generated you just can't travel from Nevada to Black Sea :D

ED is brutally perfectionist and that's why they take so long developing. I never thought they were going to revamp the Black Sea map and upgrade NTTR as well. It's like they give a step forward and come back two to improve something and and on top of that their staff seems to be too small for a project like this. IMHO, they are wasting time upgrading the simplistic Flaming Cliffs aircrafts instead of focusing on more DCS level modules. If it is for the FC customer base there are many other ways to compensate them

Does anyone know if the throttle base is detachable? I'm sorry if it was already mentioned but I didn't want to go through tenths of pages of thread