Messages posted by: hlfritz

wow - those are quite expensive! still probably less so that the amount of time it would take to create or port something else.

completely understand, trading simplicity and a few dollars for time. from my point, an extra $20 savings on a board (vs. comparing only chip cost differences) does make a difference, especially if I am going to use two of them. I think I am coming around more to the idea of a separate "brain box" with two controllers and maybe even a usb hub, sits on the desk, the controllers connect to it (gotta figure out wire/cable).

i am well aware of PCB/PCA fab costs - deal with it a lot.

while being able to bury the mcu within the controller enclosure is a nice idea with a board that definitely fits, it seems it would not be worth the effort - especially if you are going to expand hempstick to ethernet later. (i think i will be ordering stuff within 2-3 weeks and will see how things fit)

along those lines, would you keep support for Due and ATSAM4S-XPRO? or select one over the other?

Understood on low level stuff, but maybe I misunderstand the custom library? It seems that it abstracts some stuff, but perhaps that is the complicated, low-level glue that make all this work with the rest of the application? And it would require porting to a different IDE?

I do have a very sr. ee on tap i can ask questions of, so i feel a bit cocky.

My guess is I will feel very overwhelmed once i start, but I like challenges. I also have time on my side, absolutely no rush required.

I do like the idea of the multiple mcu's and discreet devices so everything is native widows as well.

Regarding mcu's themselves, does it really need to be that high power? There are plenty of other arduino boards that are in fact smaller, but they are significantly less powerful - i.e. 16MHz. The same may well be fore ATMEL MCU's. I would have to look at the other features such as number of digital pins, memory, etc. Maybe those are just not as well suited or just plain old underpowered/underfeatured. You might know already, but I can try to figure it out as well. I feel the need to start looking at freeRTOS now as well to see about its requirements.

Thx once again!

Thx. for taking the time, especially for a newbie. I view this a way to really get into programming and embedded stuff, especially potentially taking on a port. I am thinking just do as is first, then maybe port. Along those lines, I would like to ask if you care if someone worked on that using your code?

For 3A I was not suggesting you do it, just a question about the feasibility. Your answer to 3B kinda sums that effort up as well I believe.

Perhaps a separate box on the desk with connections to each controller might be a better way to go? I think the original Cougar stick gets away with a 5 or 6 pin cable because the buttons are matrixed on the original config? Is that a correct assumption? If so, in this case it seems a higher conductor count cable would be required, and then the same for the stick.

So after writing that and thinking about it, perhaps 2 MCU's in a separate box on the desktop (no pit here - no way I could get away with that!) with discreet connections to each controller. This avoids the 32 button limit for DirectX (one of my requirements), unless you think that TARGET has an advantage here (interested in opinions, I have never used it - only foxy way back when for stickworks digital chips and saitek sst).

Thanks again for your time, appreciated.

Hello,
I registered and when I clicked on the activation link (in the email) I received a "invalid key" message. The same thing occurred when I tried manual activation, but obviously I am in! Just an FYI.

Hello,
First a great thanks for doing all this work on Hempstick and then even sharing it. I absolutely love trying stuff like this out, especially if I can re-use an old HOTAS. I intend to try this project with a TM FLCS and TQS. I am an engineering manager, but still a layman.

I can muddle my way through code if I have to, cut and pasting and figuring out config files is not a problem, I can read schematics and do wiring of electronics, good at linux and windows, network and firewall administration, etc. to give you a little background. I do have a few questions:

1. I was thinking to use two MCU's, one for each device. This is due to your note about potential noise introduced on the analog wires going from one device to the next, plus it avoids the Windoze 32 button limit. But, when these devices are originally created do they not have these analog connections going from one device to the next (i.e. the TM FLCS/TQS combo or even newer Cougar setup)?

2.a. I cannot find anything that is an Arduino DUE/X, only Arduino DUE. Is there really something that is a DUE/X? where do I find it?

2.b. Related, do you anticipate any issues using a DUE clone? they are far cheaper, and I need cheaper right now (or I would just buy a warthog stick!).

2.c. You stated you need a separate debugger to program the Arduino DUE, but I have read that it can be programmed though its USB interface? (the answer to 2.a. might be telling though)

3.a. Looking at the size of the boards, I would like to use something smaller than I can definitely fit inside the enclosures. Could this be ported to say a Teensy 3.1/3.2? Does it have the specs to run this project? The processor can be overclocked on that if necessary.

3.b. What issues would you forsee porting this first to a new IDE (Arduino with teesyduino) and then the code? maybe just figuring out the config options and a few other annoying issues?

Thanks for your time!