Advanced Search

Sorry that did not work for you. Seems odd that settings would force a logout/login. we have not experienced that behaviour 

Please note if you log out, its expected you will have to log in again.

roland100 wrote:

Hello PCW,

I hope to get some help from you again.
I tried to make a custom bit file consisting of these two files 7i96s_2pwmd and 7i96sd_mpgp1. 7i96s2pwmd for pwmgen (Stepgen 4-) and 7i96sd_mpgp1 for mpg on P1.
I used the enfinity software, but it doesn't work because of a version conflict.
Do you know which efinty version works with the 7i96s firmware from the homepage ? Thanks a lot

Did you ever get this working? From the description, this sounds like the firmware I need.  Would you mind posting the bin file?

i just tried to replicate your warning, but i was able t stop and make adjustments and report without running into any of those error pop up. those are actually linuxcnc statement stating that your entered parameters would cause an over travel event, are you certain the parameters you entered would be tool paths within the constrained machine motion envelope?

LOL, i feel sorry for the keyboard!
It is hard for now, but after a while everything starts to fall in place and make sense.
Changing one single thing at a time and testing is much more productive and easy to roll back in case of failure.

Lcvette wrote:

what is your machine setup like regarding tool offsets?

My machine overall is a router style setup with a 30 in x 30 in work area. My spoil board is ~24 in x24 in. The spoil board corner is not at (0,0), well inside the machine soft limits. My tool table only has Z offset and Diameter. After probing the corner of the spoil board, the G54 offsets were: X=5.0161, Y=1.1693, and Z=-7.4953. Z probe Z offset is 2.3607 and cutting tool Z offset was 1.8513. 

Very nice, thank you, and also thank you for sharing the files on GitHub.

Moved to "pathpilot" section.

5. NOT step timing: Tested DIRSETUP/DIRHOLD at 2000, 5000, and 10000ns. 5000 was slightly better but didn't solve it.

If changing the step timing changes anything that suggests that something is marginal
electrically or timing wise

Have you tried doubling the step time?

Are the drives step/dir connections single ended or differential?  (single ended is suggested for opto-coupled inputs)

Does the DRO show the error? if not it's most likely not the Trajectory Planner
 

There already is some basic merging, I'm sure it can be improved upon

Hi,

Just wanted to share the control panel I've built for my VM32 CNC conversion project. The aim was to get away from a typical PC+Monitor setup and build an all-in-one control panel for LinuxCNC which can be mounted on the mill cabinet and control the mechanics through MESA board. I published the resulting models for this build in a Github repo:  github.com/belovictor/linuxcnc-control-panel
You can also find the panel build video on my YouTube: 

Best regards,
Victor Belov
 

what is your machine setup like regarding tool offsets?

Hi tommylight, thanks for helping me with that I very much appreciate it and all the knowledge you have. I am just a newbie who is flailing around knowing squat trying to learn linux and linuxcnc; and not killing my brain in the process (my head has a few bruises from bashing it against my keyboard.
Thanks,
George

Thank you Rod for your help it makes it alot easier to see where the errors are using geany was very helpful and good learning!

yup yup,, its pulled from the tool table and activated or not in the touchoff parameters.

user params 1 and 2 are there for you to use in any custom macro capacity. you can simply click on the label names and type your new name and it will store prsistently and you can look at the parameter names in the docs as what to pass to the subroutines. so if you wanted to add something specific to your machine you can do that with those and have realtime updating parameter entries in the ui. was just a "here ya go all" thing i figured might be useful and i had some space to use up so win win!

Hi

   I am brand new to this forum. I couldn't find an answer to my question, so here goes.

   I have modified an old manual lathe to run with pathpilot. Everything works except trying to change the spindle speed range. I have set up a custom card to control a VFD and when I run with these parameters in the tormach_lathe_base.ini its all good. Both high range and low range work as expected.

[Spindle]
LO_RANGE_MIN= 200
LO_RANGE_MAX=2500
LO_SCALE=1.0
HI_RANGE_MIN= 200
LO_RANGE_MAX=2500
LO_SCALE=1.0

  What I want to do is use the gear box to drop the spindle speed by a factor of 8. The new config information is the following
[Spindle]
LO_RANGE_MIN= 35
LO_RANGE_MAX=300
LO_SCALE=0.125
HI_RANGE_MIN= 200
LO_RANGE_MAX=2500
LO_SCALE=1.0

When I make this change, the VFD frequency is wrong and it appears that the direction lines don't function either. Version of PP is 2.14.0
Any ideas out there? My guess is that there is another parameter that I haven't changed to make a change like this.

greg