Recent PlasmaC Update and No Motion

More
29 Aug 2020 20:49 #179966 by rodw
So how are you doing probing? Still with Ohmic3 or the float switch?
If Ohmic, Is it a water table? is the plate wet on the second probe?
Is the torch lifting to pierce height after probing?

If something goes wrong on a probe event and the Ohmic probe output does not turn on, it won't ever proceed to a cut. This is more likely with ohmic3 as you may need to change the settings based on different water quality etc.

I guess what I am trying to understand if the issue is my ohmic3 component, an ArcOK failure or something in Plasmac.

Regarding the Z axis settings, I found a lot of problems went away if I jogged to the top of travel and touched off at that height. eg. if I had 4" of z axis travel, touch off and enter 4.0" when touching off.

Please Log in or Create an account to join the conversation.

More
29 Aug 2020 21:02 #179969 by Tesremos
process used to update orignally that started this rollercoaster.


sudo apt update
sudo apt get-update
sudo apt-get dist-upgrade

downloaded ohmic3.comp

sudo apt-get install linuxcnc-uspace-dev

compiled ohmic3.

noted that plasmac version still read 0.142?( i could look this number up if vital)

ran configurator in upgrade mode.

at this stage, it was doing the fail to move after pierce.


made a 100/ new config fron scratch, which got homing working correctly.

applied confurator to it.
did not add any ohmic to it.

still.issue. came to the board, applied your plasmac.comp each time you loaded it.


yesterday we tried a full linuxcnc purge.

sudo rm modules (to ensure no extra reminants were left hanging)

re installed 2.9 tried again.

purged 2.9

rolled back to 2.8 tried again.


here we are now at today :)

Please Log in or Create an account to join the conversation.

More
29 Aug 2020 21:04 #179970 by Tesremos
ohmic is disabled enitrely until we get standard float switch cutting operational.

ohmic3.comp / .so has been purged

Please Log in or Create an account to join the conversation.

More
29 Aug 2020 21:11 #179971 by rodw
Ok, so not my software :)
So does the torch probe with float switch and rise to pierce height? If yes all probing is OK.

Next step, does the torch fire at all?
If no, sounds like a plasmac issue or faulty wiring.
Use halshow to check that the output pin is being triggered. Confirm with a multimeter.

If the output is not being enabled it is a plasmac issue..

Please Log in or Create an account to join the conversation.

More
29 Aug 2020 21:58 #179972 by Tesremos
moves to probe location
probes down,
uses float switch
finds material,
moves to pierce height
pierces.(torch works fine)
moves to cut height (torch still on)
ceases movement.
arc_okay is lost,
retracts to "pause position"
and controls are dead.

no resume. no jog. no start. no reloading.

stop button works. but jog machine will not move until restarted

(hopefully my thcad from stuart arrives this week and i can play with hypersensing ((excited)) )

Please Log in or Create an account to join the conversation.

More
29 Aug 2020 22:11 #179974 by tommylight

moves to probe location
probes down,
uses float switch
finds material,
moves to pierce height
pierces.(torch works fine)
moves to cut height (torch still on)
ceases movement.
arc_okay is lost,
retracts to "pause position"
and controls are dead.

no resume. no jog. no start. no reloading.

stop button works. but jog machine will not move until restarted

No need to restart, just disable and enable with F2 will bring motion back and can continue to cut.
Having the same issue with 165 and 169, so started from terminal and got a message saying keyboard interruption so i changed the laptop, the issue remained but the keyboard error did not appear ever again, no errors appear, period.
I chalked it to an interference issue from the plasma having a 12 meter long cable going parallel to the rest of the machine cables, although they are shielded, they are not of good quality to write home about.
But the original poster mentions this happens with the torch off, so i am baffled as it never happened here in over a moth of every day dry runs lasting 10 to 12 hours a day, with every version of PlasmaC up to 148.

Please Log in or Create an account to join the conversation.

More
29 Aug 2020 22:27 #179978 by Tesremos
reckon we can roll back to pre 0.148 and try?

Please Log in or Create an account to join the conversation.

More
29 Aug 2020 22:30 #179980 by tommylight

reckon we can roll back to pre 0.148 and try?

You can try, but i can not as the machine is 120KM from me.
Then again i have to go do a photo shooting session there in a few days, so if i have the time i can give it a run.

Please Log in or Create an account to join the conversation.

More
29 Aug 2020 22:57 #179982 by rodw

Then again i have to go do a photo shooting session there in a few days, so if i have the time i can give it a run.


What movie star now Tommy? An hour ago you were starting battles! (on another thread)

So anyway back on topic.

Normally, the only buttons enabled when the cut pauses is the resume or cancel button. You cannot jog while paused!
So possibly, the machine lost ArcOK (or did not establish an arc) and perhaps Plasmac does not recover cleanly. Lets focus on the loss of AcOK now.

Did it really happen? (Lose ArcOK) or did Plasmac imagine it?.
1. Does your machine have an ArcOK output?
2. Are you using it?
3. What material and thickness?
4. What is your pierce delay? (if too long, the material will burn away and maybe loos a valid arc.)
The following user(s) said Thank You: tommylight

Please Log in or Create an account to join the conversation.

More
30 Aug 2020 00:50 - 30 Aug 2020 01:33 #179988 by phillc54
@PurduePete

Did you try my earlier suggestion of changing the limit values. I have just completed some more testing an it seems to work ok by either changing the Probe Height to 4.0 or the Safe Height to 1.0 without changing anything in the ini file.

It sure is strange though...

Edit: I am slowly working my way though versions to find where I broke it...
Last edit: 30 Aug 2020 01:33 by phillc54.

Please Log in or Create an account to join the conversation.

Moderators: snowgoer540
Time to create page: 0.191 seconds
Powered by Kunena Forum