Jump to content

Recommended Posts

Posted (edited)

A couple of Months ago I built a Device for MSFS with an Arduino Nano V3 using the AAO's Arduino Bridge. Everything worked fine on that Device. After some Weeks of not using it, I plugged it in again and found it not working anymore with AAO.

Long Story Short: I ended up with a brand new Arduino Nano plugged into a Prototyping Board with a single momentary Push Button connected to GND and D2. I wrote a short Test Sketch in the Arduino IDE, just to make sure everything worked, and it did. I then created a brand new Configuration in AAO and added the new Board to the Arduino Bridge. The COM Port of the Arduino was correctly identified bei AAO. I just added a single Input (Add Digital) to the Board on PIN 2 and saved the Configuration. RX and TX LEDs on the Board showed me that the Configuration was saved and now the "Green LED" in the Ardiono Bridge Window is lit beneath my Arduino Board. But in the Assignment Window of AAO I can't assign the one Button, connected to my Arduino, to anything. While the Device shows up in the Devices Pull-Down Field (WebAPI: 873# [-873]), Button presses are not recognized by AAO, as with my original Device mentioned above. Somehow the Arduino Bridge just stopped working for me. 

While testing with the new Board no additional Joysticks or Arduinos where attached to my Computer. 

My wiring is OK, as the Test-Sketch in the Arduino IDE shows. Anyway: "Button Presses" are registered in AAO sometimes, when I disconnect or connect Wires on my Prototyping Board to PIN 2. I tried the Input Configuration on the Ardiono Bridge with and without "inverted" setting for the Input on PIN 2. 

I'm now out of Ideas what's wrong here and how I may get my Device working again, as I can't image a simpler setup as the new Arduino Nano with just one momentary button attached to it. 

 

 

Edited by theflyguy
  • Commercial Member
Posted
8 hours ago, theflyguy said:

found it not working anymore 

What changed? These things don't just happen for no reason, something must be different?

Are you using the latest version(s) and is the Bridge used in stand alone or plugin mode?

Are you sure that it is the input that stopped working? Maybe it is what you are trying to trigger with that button that is at fault?

Finally, check the polarity of the Digital Input. Maybe the input creates the wrong order of events (up before down)I

LORBY-SI

Posted
Quote

What changed? These things don't just happen for no reason, something must be different?

All my Flightsim Input Hardware has changed (from Thrustmaster- to WinWing/Virpil-Devices), but nothing else than my Test-Arduino was connected to my Computer during the Tests. Especially there were no other Arduinos attached, so that I didn't mix up the COM Ports. Apart from that: Sorry, I don't know. I mean, there has been Windows- and other Updates since I used my Arduino Hardware the last time, but I have no clue what's causing the problems now with the AAO Bridge.

Yes, it could be, that somehow my Hardware is broken, but I don't think so, because not a single Button on any formerly working Arduino Project I've tried with AAO works anymore, that's why I'm now testing with a brand new Board and the simplest Wiring for an Input Device I can think of.

I've built more Flightsim-Hardware Devices using Arduinos, but also using other "Middleware", like Mobiflight. They still work on my PC. 

 

Quote

Are you using the latest version(s) and is the Bridge used in stand alone or plugin mode?

Yes, latest Versions of AAO (4.10 build 51) and Arduino Bridge (1.00 b02) in Plugin Mode.

Quote

Are you sure that it is the input that stopped working? Maybe it is what you are trying to trigger with that button that is at fault?

Yes, because first of all, I can't create new Button Assignments with Arduino Based Hardware in AAO anymore. Neither with my formerly working Hardware nor with my simple test setup with just one momentary Button. With existing AAP Profiles I can't see the green "LEDs" blinking in the AAO "Assigned Buttons" List when I press any Hardware Button or turn any Encoder. It looks like AAO is constantly "talking" to the Arduino (RX/TX lights flashing), but AAO doesn't catch any Events from the Inputs on the Arduino.

Normal Joystick Assignments still work, but no Arduinos

Quote

Finally, check the polarity of the Digital Input. Maybe the input creates the wrong order of events (up before down)

Shouldn't the "inverted" setting in the Arduino Input Configuration take care of that? I tried it with this feature checked and also unchecked.

 

Above I wrote that AAO doesn't catch any Events from the Inputs of the Arduino. There is one Exception to this Rule: When I define a Digital Input in the Arduino Bridge Configuration Dialogue but don't connect anything to it, this will cause "Flickering Inputs" in existing AAO Profiles that use this Input (i.e Button 2). I can see the green light flashing next to the Button Assignment in the Assigned Buttons List. Obviously the Input has no defined initial state like INPUT_PULLUP or INPUT_PULLDOWN, but is in an indifferent State. That's OK, and it shows me that the Communication between the Arduino and AAO is generally working. But it stops working as soon as I attach a momentary Button to this Pin (connected to GND on the other Side). Then Button presses aren't recognized by AAO.

  • Commercial Member
Posted
23 minutes ago, theflyguy said:

With existing AAP Profiles I can't see the green "LEDs" blinking in the AAO "Assigned Buttons" List when I press any Hardware Button or turn any Encoder.

That is not what I meant. I am assuming that you did check the actual operation of the assignments (in the sim) too? Did you try stand-alone mode too?

As it says on the AAO website, these Bridges etc. are just hobby projects. I cannot invest a massive amount of time into developing or supporting them. With the amount of trouble you have, I'd suggest using Mobiflight instead.

LORBY-SI

  • Commercial Member
Posted (edited)
40 minutes ago, theflyguy said:

Arduino Bridge (1.00 b02)

Latest version is  1.03 b04

I have a newer one too 1.04 b02, but that hasn't really been tested yet. I will upload it too.

 

Edited by Lorby_SI

LORBY-SI

  • Commercial Member
Posted (edited)
49 minutes ago, theflyguy said:

Obviously the Input has no defined initial state like INPUT_PULLUP or INPUT_PULLDOWN, but is in an indifferent State.

? you can set the pin mode on the "Add/Edit Digital Input" dialog to "input" or "input pullup". Same thing.

Edited by Lorby_SI

LORBY-SI

  • Commercial Member
Posted

I ran a quick test with an Arduino Mega

Connected one lead to GND and another to PIN 7. Configured a digital input in Arduino Bridge 1.04 b02, running in Plugin mode, Pin Number 7, Pin Mode; InputPullup, Reverse checked, Send as button1.

When I connect the two leads I get the button event in AAO. Bound a virtual key to it (s) and I can type "s"es in Notepad by connecting the two wires.

LORBY-SI

Posted (edited)
Quote

you can set the pin mode on the "Add/Edit Digital Input" dialog to "input" or "input pullup". Same thing.

...and that's exactly what I've missed out. 

Quote

As it says on the AAO website, these Bridges etc. are just hobby projects. I cannot invest a massive amount of time into developing or supporting them. With the amount of trouble you have, I'd suggest using Mobiflight instead.

Yes, I completely understand this, and I really appreciate your quick responses and your willingness to help your users/customers anyway. It's incredibly how far you brought your initial idea of AAO in all the years I'm using it now, and since the last time I've payed for it. I wrote my initial post on this topic, hoping that you may know a similar Problem from one of your customers. The problem is (possibly) about your software, but mainly about MY Computer; MY Programing and MY Wiring that you can't see and I would bet that you would have solved the Problem in Seconds if you would be here, sitting next to me. 

You are a real Champion in customer support and Software Development. I write his, because you already supported me at least four Times since I've started building my own Hardware Devices for MSFS and because I see the progress in a Software Product that I bought Years ago, and for that I got more and more Functionality over the Years. I never payed you for this excellent progress in AAO.

I just want want to say "thank your" Sir for this great Software and your ongoing Support. I finally got my Hardware working again and of course it was my fault and not your software that prevented it from working. Thanks again for your ongoing support and evolution of AAO. 

Keep up the good work, and thanks again!

Edited by theflyguy

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...