Advanced Search

My current version is 3.4.9

What version of mesaflash are you using ?

forum.linuxcnc.org/27-driver-boards/5285...-by-mesaflash#302114

Maybe of some help

Aciera wrote:

Sounds all sensible to me but I really don't feel competent to comment on the proposed path.
I certainly like the structured approach of your initiative, that is something that has been sorely lacking in other attempts.
I think/hope that Rob will be able to give an educated opinion on it and shape it into a concrete roadmap.

Note that Mitsubishi SSCNET requires a servo cycle <= 222us
forum.linuxcnc.org/9-installing-linuxcnc...cnet?start=70#256576
 
defenetly is great to have something faster then 1ms .. ethercat can run at 50us with 16axis but this complex calculations are far slower for now 

I think 250us is very pretty goal (common industrial standard) at any hardware and then reduce it based at used hardware 


Note than many ethercat drives are also limited to 1khz in position mode. lichuan is, stepperonline/jss i think is and Im pretty sure the delta b3 is. My omrons I think are restricted to 2khz in csp mode.

For 4khz or 8khz usually you are restricted to other modes. At least in the drives I have. There definitely are (much) faster ones, but they are more specialised gear vs generic milling cnc applications.

Point being, 250us sounds great, but I don't know it needs to be any sort of priority cause only few people could use it. But then maybe those few people are important (like the people I know wanting to nanometer scale optical things and MUST have the higher "loop" speed so can't entertain linuxcnc right now)
 

You are right, I agree with you 100%, main goal is get lcnc with curves at 1khz ... Timig is very wide and difficult topic but faster code means more play to some latency or timig issues of something, stability, rigidity etc...

I think it is reachable timing .. faster tick means better final result of movement and better regulation feedback with velocity or current control.. 

Then we can say isolated cpu to sleep if it will runs at longer timing then 250us .. finally we can use more masters at other network interface to run it with different timing if it is needed and then let cpu to sleep

I think Luca's goal are very very well definied .. from my point of view there is missing just pos(t+1) or pos(t-1) for position commands to any drivers which is not using the velocity setpoint(its cosmetic to not see the ferror during movement with position setpoint)

We can runs 16khz with beckhoff but there is latency restictions... for now... I am running 0.5khz with profibus equidistant and it works well but with trapeziodal its was pain.. now with scurve its smooth like butter... lower timing than 1khz are for gentelmen which they know what they are doing.. its advanced I think

Here are some (random) results

ping 10.10.10.10
PING 10.10.10.10 (10.10.10.10) 56(84) bytes of data.
64 bytes from 10.10.10.10: icmp_seq=1 ttl=64 time=0.124 ms
64 bytes from 10.10.10.10: icmp_seq=2 ttl=64 time=0.089 ms
64 bytes from 10.10.10.10: icmp_seq=3 ttl=64 time=0.092 ms
64 bytes from 10.10.10.10: icmp_seq=4 ttl=64 time=0.096 ms
^C
--- 10.10.10.10 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3060ms
rtt min/avg/max/mdev = 0.089/0.100/0.124/0.013 ms

---

mesaflash --device ethernet --addr 10.10.10.10 --readhmid
No ETHERNET board found

---

ls /lib/firmware/hm2/
3x20-1 4i65 4i68 5i20 5i22 5i22-1 5i22-1.5 5i23 7i43 7i43-2 7i43-4 7i97t_d.bin

---

mesaflash --device ethernet --addr 10.10.10.10 --readhmid
Unsupported ethernet device 7I97T at 10.10.10.10
No ETHERNET board found

I'm a little unconvinced how changing to USB would have an affect on the "wiring nightmare or EMI issues".

On my machine, I have a 30ft active USB cable going from the control box to the spindle mount (it's for a camera, but I have other wires up there for other things and the cable chain is getting full).  I could see a use for another going to the tool rack (it's on the far side of the machine wrt the control box) for monitoring the pockets etc .  It's no different than running 24V and RS422 between Mesa cards, or ethernet/ethercat, but with hubs and latency
As for noise, I imagine cases where replacing "home runs" to sensors with a single USB cable with CRCs would prevent some EMI spikes from triggering faults.
As always, we each have different needs and having a wide range of options available is good
 

Correct me if im wrong here but as far as im informed there will be no ini nor hal file before the configuration?
Since im not there yet i have none of them - or at least from what i can see
I can ping the board and mesaflash sees it but thats about it.

I'm really curious to hear if my setup with a Linuxcnc and a mesa 7i97T is a dead end street. If so I would rather stop now and go back to my safe world of PLCs and Mach

baking...

     

Look for Asus ZenScreen , usually over 100$ but often under on sale.
For some reason, 15.6" are cheaper than 14" !
Also, get the IPS version, not the TN or VA versions.

Vielen Dank,

das teil ist gefräst, alles gut.

danke karlhe

Hallo, ich habe das noch einmal nachvollzogen.
Bearbeitungsbildschirm wieder herstellen:
taste strg und taste alt  drücken, dann pfeiltasten li bzw. rechts
tschüß
karlhe


 

Yeah I got it casting with the quadro card installed and plugged into that card it does work up to the GRUB menu then turns off during boot.

A longer cable was definitely my first thought but it's still one more thing to trip over and need to remember any time I move the machine or anything.

Thanks for the heads up about the Nvidia driver. Glad I didn't try it.

The wireless setup does display the GRUB menu when plugged into the quadro card, just not when plugged into the Optiplex 9020 (or whatever it is) internal graphics port.
I'll try the "nomodeset" test.

If that doesn't work I'm still torn on whether it would be worth getting a cheap GPU with HDMI to try.

I am also considering trying to attach a smaller monitor to my machine. At the time a bigger monitor separate made sense but maybe I could find a way to attach an arm and a 12-15 ish inch monitor in a way that wasn't too obnoxious.

Of course then that gets me wondering.
Is there any sub $100ish touchscreen in that size range that would have 1920x1080 for Probe Basic that would be relatively plug and play?

All that seems easy enough and Mesa combo should be more than enough fast for everything you mentioned.
1. Yes
2. No, unless you need something extremely fast, 1000Hz is normal servo rate, and even that can be pushed further
3. should all be doable easily, and 10Hz is very slow
-
In general, plasma is the biggest offender regarding EMI noise, so you should be perfectly fine, granted the wiring and grounding and shielding is done correctly.
Regarding XYZ, it will be much easier to do a normal CNC machine setup, everything else can be set in gcode or some automated VCP panel to make use much easier and requires one time setups.
-
I have been tasked with such painting automation about 15 years ago but the financing failed, still had some time to do some thinking about implementation, hence i might be a bit fuzzy on details.
Go for it, that would be my personal advice.

i had the same problem, to overcome this i used home offset=0 and added an offset in pos comand

1. press and hold down ALT and press TAB then release TAB while still holding down ALT
2. press and hold CTRL+ALT and press left or right arrow key while still holding down CTRL+ALT