Advanced Search

swapping the HDD gave some issues with the drivers for graphics card.
just gave it another try by installing 2.8.4 and somehow it sort of worked.

even pcloud installed
the issue is been solved for now, but I do find it confusing that an 'upgrade' to 2.9 breaks some functionality

Righto I've added those lines in. No change on the x axis motor movement though.

In the interim I've connected up my second servo drive in order to start getting a full setup. I've essentially just copied and pasted the working x drive info but I'm gettingI've attached the files. No doubt it's some stupid simple thing.

*Is it easier if I just put the files straight into the post as code rather than attaching them? I want to make sure it's as easy as possible for everyone.[/code][/code]

It's good thing to know.
Do you know are there some configs with stmbl driving robots available around?
I saw some integrations with robots but encoders are read by mesa cards directly.
I would be more interested in this part which you mentioned if stmbls are set up in this way that they send position over smart serial.

Do you happen to know on higher level how this position report over smart serial works if we want to read 6 robot joints positions?
Correct me if I am wrong, but possibly in HAL we would have 6 sequential position requests, one request per each joint. We would wait for each one stmbl to report its position. So request + stmbl processing time + reply over smart serial and this happens 6 times. From fast look earlier not 100% sure but I think that there are 2 mcu in stmbl, so possibly one of them fast handles communication.

boksi wrote:

Interesting that you mentioned stmbl, I remember they were integrated with some robot (video of manutec carrying a coin).
Do they send its position over smart serial ?

They do report position by smart-serial if configured to do so. And can also accept position commands the same way (but it is all configurable)

STMBL firmware has its own HAL so you can configure the command module and the feedback module (and quite a lot more) 

Cooped-Up wrote:

watching the "DRO" the z axis zeros then moves, hits the index, zeros, and then hits the estop. I have the offset set to 0 so it should just stop correct?
 

There is a final move to the HOME position once the switches (and index, where specified) have been found.
linuxcnc.org/docs/stable/html/config/ini-homing.html

It is possible that your HOME_OFFSET has the wrong sign. 


 

That's what makes it so challenging with ethercat. Settings in several places and cross-dependencies.
Anyways, the second line in ethercat-conf.xml has the appTimePeriod setting.
There also


There are two more settings you can do now when things start to work.
Add this line right under the "<slave" line

and go back up to the second line in the file and add a minus-sign to the refClockSyncCycles value

You are right.

Switched the 7I85 channel to TTL mode, disconnected A−/B−/Z−, and kept +5, A+, B+, Z+, GND only.
The encoders now start in IDLE every time and looks work.

These Chinese “RS-422” linear scales most likely don’t have a true RS-422 line driver and cannot drive the 120 Ω termination on the Mesa inputs.

As a side note — it seems these low-cost Chinese sensors are often mislabeled:
one of my units was even shipped with 1 µm resolution instead of 5 µm as specified.
So if anyone else is buying similar “RS-422” magnetic scales, be cautious — the specs are not always accurate.

This is a new version of the 'vismach' simulation tool based on VTK instead of OpenGL:
github.com/Sigma1912/vtk-vismach

Still work in progress.
For more information see the README and the comments in the files.
 

I had a pretty hard time finding a pc with a parallel port. I don’t use a mesa card

The new pc is a dell optiplex 980 That is a very compact unit. The old HDD doesn’t seem to fit in the housing.

I use pcloud for gcode synchronization and I just couldn’t open the site on 2.8. So I decided to install te latest version of LinuxCNC

Yes that is right.
Interesting that you mentioned stmbl, I remember they were integrated with some robot (video of manutec carrying a coin).
Do they send its position over smart serial ?
I suppose when position is requested drives can’t replay all at same time because of other priorities, but stll they have to provide position.
I have custom drives build and they are reading encoders and do control but I am looking next part integrating with kinematics module.

Hi Guys,

A plasma machine I built that runs the original PlasmaC is having a fatal error message that is stopping the machine from operating. 

   

The guys who run the machine tell me the machine ran fine last Friday and when they came to use it on Monday morning they got this error message not matter what gcode program they tried to run.

This same issue happened back in March, and the only way I could fix the issue was to reformat the machine to a default state. Since it is re-occuring, there must be something going on to cause the issue.

Ive attached the gcode file to this post. 

I finally got around to getting everything wired up enough to test.
At first, I couldn't get it to start using a relay and a power supply on a switch. I realized the manual says "or dry contact closer", so I wired the relay directly to start- pin 15 and start+ pin 34, which worked.

Now I can't get my arc ok signal. I followed the example wiring in the manual. I connected ark ok+ pin 23 to the relay. Then 24vdc+ pin 37 to the relay. Then ark ok- pin 4 to power ground pin 36.
Wired up like this, the arc will not start and the plasma cutter gives an error. If I disconnect the ground to ark ok- pin 4, the plasma will start without errors. I am getting 24 volts between power and ground, and the 2 ark ok pins will close the circuit when the arc starts.

I am attaching the examples from the manual plus diagram of how I wired the arc ok relay.
I may have wired it up like example 4(which it says don't use) a long time ago before I decided to remove the old interface connection on it, so maybe that messed it up.

Does my ark ok wiring seem right? Should I try wiring it differently or should I consider using a reed relay instead?
 

Poke. Figured I should stick this here.

Machine is back together with some new upgraded, ethercat is working for the xyz.

Now I'm on to making the spindle work with modbus.
Is there a simple step by step instruction to set this up? I got a usb adapter, and I'm running qtdragon. In addition to just tuning on and off, id like it to display the true spindle speed and the load.

Thanks

I thought so but obviously something is wrong. I did post my ini file a post or so ago. I was trying to change the direction the axis moves after the index is seen. Nothing I change seems to do anything

Do you ini file settings match the requirements for index only homing?

linuxcnc.org/docs/html/config/ini-homing.html#_configuration