On 11 September 2017 at 09:52, Marius Liebenberg <[email protected]> wrote:
> Yes I am aware of that. I will be using a very short packet message system. > The thing I cannot get my head around is how my compoenent will interface > with the mesa RS-422 port. Is it just a pin called MESA-XXX-RX and > MESA-XXX-TX and my component connect to that in hal or is it a low level > interface of sorts. For this I have ot seen any examples. There is some (very limited) documentation here: http://linuxcnc.org/docs/2.7/html/man/man9/hostmot2.9.html#UART You need a Mesa bitfile which puts UARTS on some of the 7i44 ouputs rather than the default smart-serial. Until you haave UARTS in the firmware you won't get anywhere. I do hope, eventually, to make the UART and BSPI configurable in the same way as the absolute encoders. At the time I did the UART driver the smart-serial auto-discovery wasn't there, so load-time pin definition wasn't there. The absolute encoders use the smart-serial dynamic pinout code. Whatever you use, you need to find a way to work out where you are in the byte stream. A synch-byte might already exist in the protocol you are trying to use. -- atp "A motorcycle is a bicycle with a pandemonium attachment and is designed for the especial use of mechanical geniuses, daredevils and lunatics." — George Fitch, Atlanta Constitution Newspaper, 1916 ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
