Advanced Search

For sale new atc changers Deta International.
Location Poland
Model R3DE4  Cat 40
Price 3500E
www.deta.com.tw/For-VMC/30-disc-typeFeatures of Tool Magazine

1. High-Precision, Low-Noise Drive System
   Features a dual-roller Geneva mechanism combined with a worm gear reducer for precise indexing and positioning. Ensures stable operation, reduces motor load, and achieves high energy efficiency.
2. Highly Durable Tool Tilting Mechanism
   Employs a slim pneumatic cylinder on the rail to withstand side forces during tool tilting and provide a cushioning function.
   Equipped with a locking pin mechanism to prevent the tool pot from shifting in the event of air source interruption.
3. High-Strength, Lightweight Structure
   Key components are made of high-strength aluminum alloy, optimizing both rigidity and light weight.
4. Modular Tool Arm Design
   Modular design separates the main body and the gripper for quick and simple specification changes.
   Utilizes German spring steel wire with galvanization for superior anti-rust performance.
   Integrated drainage function prevents coolant accumulation, ensuring reliable operation
5. Components for conversion to smaller tool holders—such as BT30 or SK30—can be purchased from the manufacturer.
6. 
   

NWE wrote:

@tuxcnc, (...) I don't understand why the message is useless.

.

tuxcnc post=349633 userid=3011
but it doesn't tell you where that empty string came from.

@tuxcnc, I agree python 2.7 is ancient. I don't understand why the message is useless.

It says file ./plasmac/plasmac_gcode.py line 39
Popen() apparently returned an empty string to int() which needs some character. 

My small contribution compared to all the help I’ve received.

does the log show anything?

Yes, but since the hang doesn't happen at exactly the same point each time it's a bit murky.

After the first few tries the startup attempts have been with the postgui.hal commented out of INI completely.  I tried starting with every non-mandatory feature/setting commented out - no dice.

And the Axis good start-up is the same config.  Just switch [DISPLAY]DISPLAY = probe_basic to [DISPLAY]DISPLAY = axis.  No hal-related issues for the same exact LCNC connections.

As for the other probe basic INI stuff, I copy-pasted from the machine_setup_files INI.  You're welcome to have a look at my INI to see if I fat-fingered something.

if the sims don't hang, it is almost 100% in your configuration somewhere. may be missing an ini setting somewhere.. i would recommend going through your ini line my line and checking against the docs for configuration to see if something may be missing. then i would go over your post gui hal file and make sure nothing is wonky there, then check your main hal file and make sure everything is correctly spelled, i have had a typo plague me before and it took me weeks before i finally found the issue.

having a working axis config and a working probe basic config with all the extras is pretty different.  probe basics functionality is vastly larger and requires more things be in place at startup.  using axis as a base test is a good start but it is not a definitive proof the issue lies elsewhere than the config.

the sims use pretty much a complete running simulation of everything needed including atc and probing, so if the sims work consistently you know the software and your install are good.  that is proven so the changes between the axis config and the probe basic config is where to focus your attention.

does the log show anything?

You might plot the switch  hal signals with halscope when homing to get a better
idea of whats going on.

(it might be contact bounce or EMI)

 

Worse than what you describe, apparently I've gotten a pre-release version? The grub.config line says its booting vmlinuz6-12.95+deb13-rt-amd64
the words debian 13 show on my screen after boot for awhile then go away, I got the iso file by searching the linuxcnc site because the link to download wouldn't work for me .
on the other hand, linuxcnc says its axis.ngc - Axes 2.9.10 on LinuxCNC-HAL-SIM-AXIS
and it will simulate some parts, I'm still checking. It seems to be working very good so far, internet works, playing mp3's work, terminal works, selecting applications seems to work, usb drives seem to work.
probably too early to submit bug report here but thanks for the reply.

Yes, the style sheet was appropriate for non-flashing.

But I ran in the the same problem(s) I reported on github after this round of edits... intermittent hang during PB startup.

As before, everything works fine in sim but about 75% of attempts on real machine hang up during start.  This time I followed your instructions, started from a clean update, and didn't touch anything other than the user ui files.  All editing was done with probe_basic.ui open via editvcp.

Testing on the real machine:

• Demo configs start fine
• Turning on/off the various user features (button panel, main/side tabs, atc btns, dro) didn't appear to make any difference.

The hang condition doesn't seem to follow any pattern.  I can try to start it, hangs, then I force-close the terminal window.  Next time it starts.  Or it hangs 4 times in a row before starting.  Or I have to re-start Debian and then it works... until it hangs again.

No other GUI demos hang, and I have a minimal but working Axis config that starts no problem 100%.

As I mentioned on github I don't have different (non-ethercat) hardware to test on.  And no clue if this is ethercat related, but the hangs always happen towards what should be the end of the qtpyvcp/probe basic startup sequence.
 

thanks for pointing that out, i have updated the configuration documents to reflect the missing config items, sorry about that, got missed somehow.. should be up shortly!

did you change the style sheet for non flashing?

Here is my HAL and INI files.
 
 

Fixed. The ini file was missing this.
[ATC]
# Number of pockets in the carousel (set to 0 or 1
I did not see that referenced in any of the installation manual documents. I may have just missed it.

It's hard to help you when we don't know what you're doing, how you're doing it and why you're doing it.
It happens that the installer has a problem using a partition formatted in a different operating system or with specific programs. Then the actual solution is to tell him to format the partition in his own way.
The rest of your post has no sense and difficult to respond to.