Advanced Search

blazini36 wrote:

The file browser is a little hard to navigate because it doesn't show the current directory, easy to get lost. Any chance you can add current directory at the top or something?
 

Do you have an example of what you mean? I'm having a hard time visualizing that...

JT

To change the jumper position just pull the little link off and put it back on the top pin

Murphy wrote:

The one labeled Remora 
 

I just edited my last post after having a think.  Ignore the STEP_SCALE value from the wrong INI... but apply the concept and put a minus sign in front of your existing value.

The one labeled Remora 

blazini36 wrote:

Didn't get a chance to update and try the label yet as I'm working on the hal file at the moment. Couple of things I'm noticing now that I'm running some sims......

Since I added a qss, INPUT = TOUCH seems to not have an effect anymore. Pretty sure I had the touch style file browser before the qss but now it is back to the normal one.

The file browser is a little hard to navigate because it doesn't show the current directory, easy to get lost. Any chance you can add current directory at the top or something?

The flood and mist push buttons disable when a program is running. I'm used to Gmoccapy where you can still operate the mist and flood while running a program. Sometimes I forget to add coolant to the program and need to turn it on when it's running. Not quite sure why yet but as soon as the GUI disables coolant even if I stop the program I can't control it again with the hal buttons until I first turn it on with the GUI buttons.
 

The ini entry INPUT is now THEME gnipsel.com/linuxcnc/flexgui/ini.html#themes

Which file browser, the keyboard or the touch screen?

Good point on the flood and mist and I see no reason to disable them at any time and that has been fixed.

JT

PCW wrote:

I would not use the 192.xxx.xxx.xxx range, but rather set the 7I96s
to 10.10.10.10 = W4 down W5 up +power cycle and set the host address
to 10.10.10.100:

[
auto eth0
iface eth0 inet static
address 10.10.10.100
hardware-irq-coalesce-rx-usecs 0
]

 

Hi,

Thank you for your reply. I would like to use 10.10.10.10 also: I have read the manual on this part and I have watch some set up vidoes for this card too. But I am not entirely certain about the jumpers. Please refer to the attached image:



To pull W4 down, do I just push that shiny piece pointed to by the green arrow down, please?

Thank you and best regards,

...behai.

rodw wrote:

Please watch my video

start at about 16 minutes in if you want to get to the section on networking
 

Hi,

Thank you very much for your suggestion, I did watch the entire video. I understand your explanation on the TCP/IP protocol.

Best regards,

...behai.

Which of the three INI files is yours?

EDIT - 

The search velocity for home is a positive number. It should be negative? But I change it it goes the wrong way.

Your home/limit switch is to the operator's left (towards spindle) - i.e. Z-negative.

If you edit your INI file so that the initial home search is negative, but the Z-axis moves to the right, this suggests your Z-axis motor direction is backwards.

You can change the Z motor direction in INI by changing the sign of the step scale (to positive):
[JOINT_1]
STEP_SCALE = 50799.998

Try changing the motor direction and set your homing direction as negative and latch velocity as positive:
HOME_SEARCH_VEL = (negative number)
HOME_LATCH_VEL= (positive number)

Once you get this sorted, you may also want to adjust your home offset so that the Z-positions are more like 'normal' CNC lathes.  "Normal" lathes have G53 Z0 at the extreme limit away from the chuck/spindle.  Commanding a 'G53 G0 Z0' will result in the turret/slide moving to the safest position (extreme right end).

If you leave the home position (G53 Z0) near the spindle end you'll have to be very careful about G53 and G28 homing moves since LCNC has no idea what chuck is mounted or what stock is in the chuck.

Didn't get a chance to update and try the label yet as I'm working on the hal file at the moment. Couple of things I'm noticing now that I'm running some sims......

Since I added a qss, INPUT = TOUCH seems to not have an effect anymore. Pretty sure I had the touch style file browser before the qss but now it is back to the normal one.

The file browser is a little hard to navigate because it doesn't show the current directory, easy to get lost. Any chance you can add current directory at the top or something?

The flood and mist push buttons disable when a program is running. I'm used to Gmoccapy where you can still operate the mist and flood while running a program. Sometimes I forget to add coolant to the program and need to turn it on when it's running. Not quite sure why yet but as soon as the GUI disables coolant even if I stop the program I can't control it again with the hal buttons until I first turn it on with the GUI buttons.

I tried every possible combination with the X axis limits and homing. Still isn't working. I noticed something with the Z axis. The search velocity for home is a positive number. It should be negative? But I change it it goes the wrong way. My limits for Z are 250 positive away from the spindle. And 40 negative pass homing.Iv attached two other working ini files from other people. Iv noticed in one of them that for X axis the search velocity is positive. That would bring it up but the home switch is in the negative direction. Is there other settings somewhere else in a file for machine setup ?

Ok. As long as I am aware of it I can handle with it and I will choose smaller values.

Right now I am trying to get a 4 axis Machine running. Right now the scurve tp is making a lot dump things.

Grotius, do you have a 4 axis sim machine running to play with?

Boot into Ubuntu, mount the linuxcnc partition and bingo you have access to the files.

But if you can’t do that what’s more annoying, copying the files or not being happy with your machine ?

If you want to be helped you need to provide the info.

Without the info it’s hard to impossible for those helping and you don’t get the answers you require.

Yes, the problem with using a fixed blend radius on all segment intersections would be that the path deviation depended on the angle at which the two segments intersect, which would be rather unfortunate (If that is indeed what it is doing). For angles larger than 60° the blend radius and thus the feed rate could actually be larger for a 0.1mm deviation while angles below 60° would require a smaller blend radius to stay within a maximum deviation of 0.1mm.

Hi Cakeslob! Thank you for your reply. I attached some picture of my mill for clarity. So I got 1710 RPM motor with a fixed 1.8:1 pulley ratio, the encoder is on top of the second pulley, after that I have a lever for High/Low lever that with a 8.3:1 ratio. It's possible to put the encoder after all that but a lot of work. So my ultimate goal is when I call M3 S1650 the control output what he think is the correct 0-10v voltage, read the value from the single pulse Hall sensor and adjust the voltage to hit the target perfectly. I think it's closed loop. The cherry on top would be the ability of rigid tapping but not sure if it is possible with my current configuration. Probably a lot of work and if I need another kind of encoder i'm willing to replace it, i started this project 5 years ago and i'm not in a hurry. If I understand correctly, the remora PRUencoder doesn't work with single pulse hall sensor so your code is probably not suitable for my setup. The maximum pulse frequency is 5000/minute, does the EC-500 can handle that?

spumco wrote:

Writing a help manual targeted at the lowest common denominator means including tons of info many people will find annoyingly superfluous.  The author(s) just don't know what the audience already knows... hence the forum questions.

It would be enough, how did i wrote above.
Needed pins, photo/video of the mechanism and the sensors, schematic of the electric connection, example *.hal (with comments) for all cases.