Advanced Search

Hi,
how to configure pncconf for analog speed control of the VFD with Mesa 7i96s (only pwm options are available for TB2 spindle speed control) i got a fuling DZB200 vfd wich is connected with a Mesa 7i96s. it needs 0-10V for speed control. I connected the vfd with TB2 22 and 23 for the speedcontrol.

• TB2 pin 23 (SPINDLE OUT) → VFD VI
• TB2 pin 22 (SPINDLE−) → VFD ACM

in pncconf i now only have pwm variants for the spindle speed control in the TB2 pinout config? which to choose for analog speedcontrol? For now when i enable the spindle i got a fixed speed which i cant change and consequently the output from the speedcontrol measures all the time arround 0.7V and doesnt change for whatever which speed i put in via the linuxcnc GUI which strenghtens the idea i always get the same voltage with only anoher pwm. 

i dont know if this is a bug in pncconf or with my setup, but i had the same problem as you. I connected the enable spindle on tb3 13 and 14 and configured in pncconf the pins out0- and out0+ as the enable spindle. didnt work at all. the moment i connected them with out1- and out1+ (TB3 15 and 16) but kept the configuration in pncconf to out0- and out0+ it worked. I expect there is a mismatch in pncconf between the numbering of the outputs and the pin layout of the mesa 7i96s. Not sure why but it worked toi enable the spindle (though no speedcontrol yet)

If you are NOT using G96:
linuxcnc.org/docs/html/gui/gmoccapy.html...ers_in_the_info_area

If you are using G96 then you may need to update:
github.com/LinuxCNC/linuxcnc/pull/3454

Hakan,
Could you please give me more information about sii +m option? I yesterday didn't find it on documentation. And when im try to use -m option - there was an error in answer
update: in your message about siitool -m esi.xml eeprom.bin i founded about -m. Try to do the same. And download eeprom.bin but situation the same. After re-plug the power settings needed to be downloaded..

thanks Tommylight.    ok I will work on transferring to the hard drive.    But probably not rite away.    Currently i am having trouble adding the next axis.     Some kind of Clearpath initialization  problem; as the problem is only with the new servo.    
    Also i need to work on the Estop,   and the hardware cabinet

thanks   i will just deal with the re config issue until i learn a bit more about what i am doing
    

Are you saying that the spindle-at-speed signal interrupted the probe routines?

Hi,
I was hoping somebody might be able to help me with modifying the 5axiskins kinematics to rotate the B axis 90deg and rename it to A axis.  I have everything moving and working with the 5axiskins and switchkins, but to match up with my machine setup I have to rotate and offset the B axis 90deg. 

There was a reason that apparently now does not exist, so feel free to install it on the hard drive from the USB.
And yes, you can make as many configs as you like for the same machine, like have a slower config for when stuff can not fail, or a very high speed one where you can adjust sliders and actually test how fast you can push the machine before it fail, or ... turn RGB light on.

Thanks Tommylight.    I looked into the Debian Persistance  stuff.      Is there a reason NOT to put linuxCnc on my dedicated LinuxCnc computer?    So i don't have to use the thumbdrive permanently     I brought this up a few posts ago.    This machine will eventually be living in the shop running the machine will be its only job
 
        If i change to put the live linuxCnc image on my computer will it solve the Not saving the configuration file problem?

And i can change stepconfig wizard stuff at will,  and just erase the old configs correct?

thanks


 

Hi again and thanks for all the help up until now!

I wan't to give more context and explain myself better, we have been using this cnc router since 2023, originally setup with a raspberry pi 3b and octopus pro combo, it has worked wonders and is amazing the only real issue is that the raspberry pi 3b was slow. Recently we made the change to a raspberry pi 5, we took the original .ini and .hal files which we then update to be compatible with the new remora version, we kept the same config.txt file. We installed the linuxcnc-raspberrypi5 image and installed the remora components as instructed in the documentation.

The issues we've seen: when we first loaded linuxcnc and ran the .ini file by double clicking on it and choosing linuxcnc as the app to run the ini file we then saw the raspberry pi 5 using rp1 driver alert, we initially thought this was error but figured this was just an alert and so continued. We then started testing leaving e stop we could but just for a moment, no more than 3s, we could even get to enable but non of the drivers actually enable. We then tested if this was the E-stop's fault but we assumed it wasn't since if we disconnected the estop we could exit estop at all, wehn it was properly setup we could but can't enable the steppers fisically. This isn't a stepper issue or driver issue since they get enabled with the raspberry pi 3.

Thanks in advance and thank you for all of the help until now! Oh and sorry for any grammar or spelling mistakes, english isn't our first tounge.

What type of laser and what speeds will it be working at?

Found my failure... the index proximity sensor was missing the counter nut... when carousel turns some vibration brings some movement in which make issues..

Thanks

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