Yahoo Groups archive

Emax

Index last updated: 2026-04-28 23:23 UTC

Message

RS422 progress

2009-06-26 by mr julian

OK.

So - some people here might remember how near the end of last year I 
said I'd have a go at designing a usb-RS422 adapter for the emax that 
would world just like a normal asynchronous serial device until it was 
requested to go to 500k baudrate, when it would then jump into 
synchronous slave mode.

Well.. lots of stuff happened to me since then (lots good, mostly) and 
the whole thing got left on the side for a while....

Anyway. I actually got around to building up my RS422 adapter board this 
week.

And today I have been mucking about with the test download program given 
to me by esynthesist, seeing if I can make firmware for my adapter that 
esynthesist's test program can use.

and... it seems to work.... well - work as good as I can see. right now 
I have a cmd window saying (after a bunch of scrolling)

---------------------------------------------------
.
.
.
.
Sent 6 bytes
[F0 7E 0 7F F F7 ]
(16) 10:20:19.758 received 127 bytes, status is 1 [0 0 0 0 0 0 ]
Sent 6 bytes
[F0 7E 0 7F 10 F7 ]
(17) 10:20:19.768 received 127 bytes, status is 1 [0 0 0 0 0 0 ]
Sent 6 bytes
[F0 7E 0 7F 11 F7 ]
Start of MMA unload: 10:19:30.347
End   of MMA unload: 10:20:19.788
                           S U C C E S S F U L  !


Press a key...

---------------------------------------------------

I think the next thing to do from here is send my prototype adapter off 
to esynthesist, so he can develop a proper app, and then when the proper 
operation of the hardware/software pair is confirmed, get the adapter 
schematic and firmware info all up in the emax group archives for 
everyone, and start work on a PCB to make building up these adapters a 
bit easier. (promise I won't take 8 months to do a PCB... in fact I 
already have the schematic captured)





julian

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.