Hmm, the documentation and components mention do not seem to exist in master branch. http://linuxcnc.org/docs/devel/html/drivers/hostmot2.html I also had a look in 2.7 git and could not locate the uart comps. Any links to git would be appreciated Moving forward, plasma activity is going to be in master branch due to joint axis and Dewey's external offsets branch so it would be good to restore this.

I'm assuming Marius wants to talk to a Hypertherm plasma cutter using their documented modbus protocol.
That is precisely what I have to do. A HPR260 plasma source.

When I've thought about this problem, I did not think serial comms should be in real time but in user space. In my config, a gcode M67 E0 Q440 is sent to the glade screen python handler where it is decoded as "Set plasma amps to 40 amps". Similarly for air pressure. I'm not doing anything with this command yet. There are any number of modbus libraries for python so I was hoping if I knew how to access the uart, I could write commands with a high level python routine. I'm assuming Python could access the uart functions Andy mentioned?

Pretty sure the Gmocappy plasma GUI and its supporting plasma.py I've modified was written by Marius so thanks
I will have to add quite a bit of functions and a screen or two to Gmoccapy in order to handle the requirements for the Hypertherm HPR260




Rod Webster
0435 765 611
Vehicle Modifications Network
http://www.vehiclemods.net.au/


On 13 September 2017 at 04:02, Marius Liebenberg <[email protected]> wrote:


On 12 September 2017 at 10:47, Marius Liebenberg <[email protected]> wrote:

> >You need a Mesa bitfile which puts UARTS on some of the 7i44 ouputs

> Does this apply to the 7i80 or 7i44?

7i80 bitfile.

> > Whatever you use, you need to find a way to work out where you are in
> > the byte stream.

> Does this imply that the data stream on the UART is not all mine and that there are other info being sent ?

No, it is all yours, but once your data spans multiple packets you need to work out where you are in the byte stream. This can be done simply by timing, if there is a longer pause between the start and end packets than the inter-byte gap, or some protocols have byte patterns that can not exist in the data as frame markers.
Or a state machine if the frames are predictable as mine is.
Something like this:-
> = Start of message

3 byte command ID

Data

2 byte checksum

< = End of message

Sample: >0011C2<




> Does the mesa_uart.comp serve as an example only or is it a
> loadable component.

If you have uarts in your firmware it should work. I have used a very similar component to send data from an Arduino to a Mesa card.
That is interesting and might open a whole lot of scope.


--
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

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
------------------------------------------------------------------------------
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
------------------------------------------------------------------------------
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

Reply via email to