cefs

I did notice the other day that pressing the autopilot mode switch either up/down or both and then back to off I was able to lift off with a lot less forward motion, have not had time to confirm this behaviour, but give it a try.

Had that same error code when I had a problem when MSVCP120.dll went missing, check to see if you have the VS 2013 x64 redistributable installed, if not then download the vc_redistx64.exe (or something like that) for Visual Studio 2013.

Problem resolved, MSVCP120.dll is the redist for vs 2013, was thinking it was vs 2012, managed to download it and reinstall, no idea how it became uninstalled though, most curious.

MSVCP120.dll is missing Was flying ok earlier today, but for some reason the open beta v1.5 will no longer start. I have reinstalled but still get the same message at startup that MSVCP120.dll is missing. Have run vcredist_x64.exe and asked me to repair or uninstall, so repaired but still displays the same message. Any ideas.

No offence taken, each to their own. If anyone is going to download, you just fill out a short form, only need to supply a genuine email address, there are no checks for genuine student credentials or anything else.

Autodesk Inventor 3 year free student licence. Inventor Professional Free Download | Free Student Version

UART's are very unreliable in a bus topology without transceivers, there are a lot of reflections and the uart most probably wont have sufficient drive current to drive a number of receivers. Wifi is doable, but the overhead of decoding and encoding ethernet packets is the only downside. A low overhead protocal like Mifi might be better suited.

You should be able to use DirectInput yourself to grab what you need, only problem may be how sim sets the cooperative level, and you will need to decode the data sent. Have a look at this link also as another possible way, also has links to DirectInput API. http://www.codeproject.com/Articles/185522/Using-the-Raw-Input-API-to-Process-Joystick-Input

If you are having errors with rs485, could be down to bus and terminating resistor value or not using them altogether, for a short bus with only two devices then only one resistor should be ok, but any more evices then each end of the bus should be terminated, generally 120 ohm. Are you bit banging yourself or using an onboard uart, could be down to baud rate settings.

Will you then be running say a few at the top level in multi master mode and they will then feed each segment. Would be handy if the pro mini had two i2c ports.

The I2C spec. says a max of 400pf bus capacitance. Wire, solder joints, pcb traces and each device all add to the bus capacitance and you will have to select the correct pullup resistor values. The minimum pullup value I think is around 1.5k and the max for a 400pf bus is around 2k. At some point due to high capacitance the bus will just not be able to switch between high and low fast enough or even not at all. So playing aroung with the pullup values may be needed. One way around this may be to segment the network by using devices as hubs or repeaters, or better really would be to use rs485 or can.

I understand where you are coming from and there is no harm in asking, but I just cant see ED doing that, it would not be something that I would expect of them from experience of other sims. If the demand was there some one would be selling it already.

My point is that ED produce a flight sim, same as xplane and fsx, they are not really concerned with the pit building side of things, as you pointed out, that side of things such as project magenta are 3rd party efforts, its easy enough already to extract state data through lua scripting, why would ED make more work for themselves, its not necessary, they have already provided a convenient way to do it.

Not seen too many encoders with a 3mm shaft, grayhill do some reasonably priced rotary switches with adjustable stops with that size shaft, would have thought the originals would have been rotary switches, and if they were and its a matter of i/o pins then a port expander chip could solve that problem.

This is not a flight sim built for pit builders and I cant remember ever seeing anything like helios in any other sim. I would be very surprised to see anything more than we already have, and apart from texture exporting not working I think its good enough, there is a consistent interface to state data through lua, and its got to be the easiest sim to interface to, have a look at xplane and fsx/p3d.

I could see start_index getting a wonky value and the '* 16' made me think you were indexing into unsigned shorts. I was getting freaked out by those while(1)'s in the setup routine, glad they are now gone.

bored at work so had a look at the sketch, could problem be at line 127: unsigned char row = (address - 0x10d4) * 2; maybe not multiply by 2.

Below are initialisation values I have used in successfully before in sequence. I generally set all registers to known values rather than just use defaults. Have you set the scan limit and decode mode. NOOP, 0x00 // Decode mode - all off DECMODE, 0x00 // Scan limit 0x00 - 0x07 SCANLIMIT, 0x07 // Intensity 0x00(LOW) - 0x0F(HIGH) INTENSITY, 0x08 // Test display TEST, 0x01 DelayMs(500); TEST, 0x00 // Shutdown 0x00=OFF 0x01=ON SHUTDOWN, 0x01

Looks very good. I suppose the weight of the x axis eliminates the play in the y axis bearings. If you do change the bearings and they are the press in type, if you see a row of small holes running down the outside of the carriage along the line of the bearings then there are grub screws holding the bearing in place and will need to be unscrewed before you can knock them out.

Just looked at the datasheet and that sounds about right.

Using a single resistor may work for a certain period of time, bit as Ian has said, due to manufacturing tolerances all leds are not equal, and you will find that the most conductive led will conduct more than the rest and burn out sooner, then the next and so on. Boltz, I suddenly had a eureka moment and understood what you were saying, funny how everything is clearer once the meds have kicked in.

As Mike says, the 2n7000 is very handy, I generally have a few on hand in the parts box, but for the amount of leds for the caution panel the uln2xxx makes things a little easier I think. My point is that if you are using 2 volt leds with a 12 volt power supply, 2 volts are consumed by the led and 10 volts by the resistor. If the current through the led is 20ma then the power that the resistor dissipates is 10v multiplied by 20ma, which is 200mw. Multiply that by however many leds you need and that is a lot of wasted power that the resistors convert to heat. Also the resistor used would need to be able to handle that amount of power dissipation, at a minimum a 250mw or 1/4 watt resistor would be needed, but recommended would be a 500mw or 1/2 Watt resistor. A better alternative would be to reduce the input voltage, either using a fixed power supply such as 5 volts or an adjustable one, there are plenty of adjustable switch mode power supplies available. Boltz said in his post to connect the resistor after the darlington array, the darlington array switches each circuit to ground so you do not connect anything after the darlington array, you cant anway, just thought that might have caused some confusion, no offense to Boltz, he seems a lot more knowledgeable than me, also I was wrong about the Arduinos current handling capability so take anything that I say with a pinch of salt and do your own research.

What leds are you using, what voltage and current are needed. I just noticed you are supplying 12v, that will be a lot of wasted power, as heat, if the led only needs 2 to 3 volts.

A darlington or 'darlington pair' is a pair of transistors acting as one, so you can use a minimal current into the first to switch a higher load through the second, basically the same function as a logic level mosfet. They are packaged together in groups of 7 or 8 in one chip, hence darlington array, in the uln2003 and uln2803. You will need a resistor for each led or number of leds on each circuit, same as you would use for driving directly from each arduino pin. There are loads of circuit diagrams, just search for 'ulnxxxx circuit on google'. I was wrong about the arduino's current handling capability, the page you linked to trise has been updated and atmel have confirmed that the arduino can handle 200ma per gnd pin. Anyway, it is always advisable to buffer any input and output so using the darlington arrays as you have is the best way, it provides a level protection for the arduino pins.

Some mighty impressive work Warhog, and good to know the MAX chip is up to the job. I did come across this yesterday https://www.coolcomponents.co.uk/white-led-backlight-module-small-12mm-x-40mm.html so it is clearly evident that a single led would suffice.