Advanced Search

forgot to add, we don't use this for 3d printing but as a router, it has the dm556s connected to NEMA 23 motors.

We have used this settings before, and the machine worked fantastic, the only change we've made is the change from raspberry pi 3 to 5 and the Remora version change. Well attempt config changes. Thankyou Scotta!

Yes! Got it working now. My spindle.0.at-speed that was taken from hy_vfd.spindle-at-speed was the problem.

hy_vfd.spindle-at-speed is not set to TRUE when MDI M05 and spindle actually comes to a stop. This behavior is not according to the docs. linuxcnc.org/docs/html/man/man1/hy_vfd.1.html

So, instead, now I'm taking the spindle-speed-fb from hy_vfd and compare that to speed-command in a near component, and that sets spindle.0.at-speed correctly.

Now probing and movement works as expected.

github.com/hmunktell/printNC/commit/46ca...22d4761f4831403e5867

Hi Gusugs,

Thanks for sharing your setup. In your ini file your accelerations are extremely high, way higher than I use in 3D printing.

Also, your FERROR of 0.025 and MIN_FERROR of 0.25 are the most likely causes. These are way way to small. You need enough allowable following error for the control loop to do it's thing.

Have a look at some of the example configs to get a feel for what is needed.

github.com/scottalford75/Remora/tree/mai...nuxCNC/ConfigSamples

You need to create a "persistence" file on the thumbdrive, search the Debian forum on how to do that.
Sorry but i have not done that in over 10 years.

GDTH wrote:

ah okay, i will take a poteniometer with me next time. the machine is not close by. are there other things you might suggest? i was thinking of maybe doing the auto tune with the vfd, if i can figure it out.

Do you also think that i force it too quickly to high freq or just too slow?

Also a picture of the spindle, in case it helps some insight
 

Yes, it might solve the problem if you add a limit3 (I think that is the name of the hal component) to slow down the change of the spindle speed value.
Jon

ah okay, i will take a poteniometer with me next time. the machine is not close by. are there other things you might suggest? i was thinking of maybe doing the auto tune with the vfd, if i can figure it out.

Do you also think that i force it too quickly to high freq or just too slow?

Also a picture of the spindle, in case it helps some insight

i have tried several different times to save the configs, rename them,   re locate them.   
After a power cycle;  LinuxCnc No longer appears in my  Home, file syste, or user.

after i run a fresh stepconfig wizard the system runs pretty well,    I get the desktop shortcut ,   but it won't save.

   I did manage to get my mill table going  I had a latency error, and  I had to turn the max acceleration down a bit, but it mostly seems to run well.    Or at least enough that i can assume that my servos are strong  enough, and i can carry on with the hardware adapt to get the new servos connected and mounted to the machine.  
      I will have to buy some semi special timing pulleys to get the L size pitch with a .250" shaft bore.   



 

Moved to GmoccaPy section.

I'm installing a 20w laser on my CNC and I control the power of laser using the spindle pwm. The software LightBurn use M67 to control the laser power. I modify the HAL file to connect  analog-out-00 to the spindle PWM and set the scale. The laser is ok and the power change. Can i use the slide of spindle override to increse and reduce  the new laser signal ????  I'm not expert to configure linuxcnc. 

I’m about to start virtually the same conversion on my Shizuoka ST-N, has the same Bandit and motors. Do you still have that documentation available? The above link doesn’t seem to work.

I really appreciate the insight. I initially thought it might be a brake resistor but the 'dynamic braking package' on page 88 is only listed as an option for the larger 7.5-20HP inverters whereas this is a 5HP model. I've put in a request with TB Woods and Vacon but this is a 12 yr old, discontinued and obsolete product...

HI GUYS

i played with the carousel comp.. and .. possible i am too stupid for it... but.. after the homing/indexing is done.. my carousel stays at tool 1. Tool 1 is the original position where the index sensor is engaged.

so if i start the machine... home xyz.. and i call m6t1.. the toolchanger makes his initial homing.. and then stays. 

if i start m6t4 as example... toolchanger search for index signal... find it.. and then goes to tool 4. Tool4 is then shown.

if i then call m6t1.. it goes to tool 1.

i play virtual with it.. mesa 7i92 with buttons and switches.. and looking to the halpins.

i search for the solution that when the m6t1 is called .. that the indexing/homing.. said.. ok now its homed and we are at tool 1.

another question.... if i had the index signal on another toolslot.. how to tell this to the carousel comp that pocket/position X is the reference point?

i use index as mode.. every tool has a detection screw which is detected by a proximity sensor-2 and index is another proximity sensor-1 that look for the screw on tool 1 which cant detect by the sensor-2.

but on tool1 sensor1 and sensor2 are active.
sensor1 looks for index
sensor2 looks for position reached.


thanks
 

I tried setting the spindle speed to s1000 And then my Linux screen goes off the side showing this s number. Can someone shed some light on this? I thought it had something to do with the scaling in the hal, but if I mess with that the spindle speed is way off.

 

Thanks in advance