Emax

Hello, i did not mean to hurt te feelings of the authors in any way, who must have had extreme amount of work with this thing, and they deserve nothing, but respect. I agree with that. I also plan to support their efforst, it is no question. (Donation-wise ofcourse)

The point of what i said was, that anyone who goes into building this, should not think of it as something easy. It may become serious effort and many work hours might be required. I was already preparing a good amount of extra information to share, but i don't think i can finish this unless i get help.

Maybe i was naive, but i thought by ordering the parts, getting it together will be 2-3 hours. 

Maybe i was naive with thinking that the user group will help me with their experience, but it did not happen and it's true for other issues.  

At this point, i am not sure i can get this to work by myself. 
But let's hope, someone may find these information useful, i am going to share what i know.
 
> - "I would be glad to share the knowledge and experience with the hardware we made"
> Fine, but from the electronics point of view the EmuSer based on Teensy++ 2.0 is exactly the same as the circuits using the Teensy 2.0, except for the pin numbering of the Teensy.
> From the firmware point of view, a different build of the firmware must be used, because it's another processor board. 
 
> - It's true that there's no well documented source code and HOWTO provided for changing the source code of the firmware... because it was simply not the intention that anyone would do that !! 

sorry, i did not know that. if i knew this i did not even try it, because to get that compiler run on os-x with all the libraries and other stuff to work took me a day. And it still does not compile the code, i guess some more days of work has to go into it.

on the other hand, from what i could measure the thing works like it supposed to, and what i could experience that the problem relates to the clocking.  Seems like EMXP kicks off the Teensy++ from asynchronous mode and switches the clock pin to output instead of input. The board i made works perfect in other aspects. Connecting the tx-rx pins on teensy will pass the RS422 test on the EMAX I diag, and  Hyperterminal on PC will happily send back the characters too. However, it looks like it does not sync to the EMAX I's clock. 

all my question was -and thats why i wrote al this- if anyone actually tried it with Teensy++ but i had the usual silence. i am glad to hear, that you report, that the hex files provided work on this board 100%. Means i did something wrong with the circuit, although i still can't imagine why, because of the above. (Do you have an idea how could it pass the above tests and still not working with EMXP?)

"So yes, if you want to start changing and re-compiling this code, I can imagine it will not be easy. But maybe...(??) I will add a readme file explaining what should be done if someone really wants to start programming for AVR with AVR Studio... although I don't think many E-Mu users will be interested..."

I only wanted to recompile your code because i assumed, something went wrong with the included firmware. 
Actually the files are well documented, but many files missing from the sources you included on your page. Normally i wouldn't want to touch it, it required a hell of a work. I wanted to use it to figure out why it does not go to asyncrhonous mode.
I don't go to my work these days i wanted to figure this out so hard.

> I will check if the latest Teensy++ 2.0 boards sold by PJRC are still exactly the same ones as I have used here in 2010, and I will also double check if the HEX file provided for the Teensy++ on my website is really the correct version and that I didn't make a mistake with that one. 

That would be super-great! Please let me know what you found!

I'd also welcome if you had some hints now regarding this clock-issue or what could went wrong with it.

If you didn't mind sharing the folder you used for compiling the firmware, i could also help tracing. May not be necessary though.

> I can only do this in the weekend though because I don't have access to my material now. I had other things planned in the weekend, but hey who cares...

;) thumbs up! 

Adam