Gmoccapy - A new screen for linuxcnc

More
9 years 8 months ago #87946 by Patrik T
Every startup I get the message "It is not possible to change to Auto Mode at the moment".
Is this normal?
I can't see that I have asked for auto.

Thanks

Please Log in or Create an account to join the conversation.

More
9 years 8 months ago - 9 years 8 months ago #88007 by newbynobi
Hallo Patrik,

thanks for using gmoccapy.
No, it is not normal to get the mentioned message. Last time I was informed about the same behavior, the user used a HB04 Pendant. The configuration used a button to toggle cooling and another one to toggle spindle on and off and that ones at connecting the pin in hal, causing the error. So I am pretty sure, you have also a connection in your hal causing that.

I used a easy fix to solve the message problem like this:
Code:
######################################################## # olli.hal file from Norbert # # pushing one momentary button allows switching # # the coolant on and off # ######################################################## # first way to load realtime components with names # the second line connects the component to a thread, # other wise it will no be updated automatically loadrt toggle names=cool,spindle addf cool servo-thread addf spindle servo-thread # and here the solution loading them with the amount of numbers to load loadrt not count=2 addf not.0 servo-thread addf not.1 servo-thread # we do need two and componends, to that ones we connect # pin motion.motion-enabled , this pin is only hight, # if the machine is switched on loadrt and2 names=and_cool,and_spindle addf and_cool servo-thread addf and_spindle servo-thread # connect the pin to IN0 of the and componends net enabled and_cool.in0 <= motion.motion-enabled net enabled and_spindle.in0 # The net command # net = the command to connect thinks together # toggle_coolant = the signal name, just think it is a cable and the name is the color # pendant.button = The hal pin name of the button to use # => = the direction the signal should flow # halui.flood.on = the pin you want to change # you can connect several hal pin to one signal (see coolant-on) # we need to make some changes to previous connections net coolant_in v_buttonlist.v_button_0 => cool.in net coolant-on cool.out => halui.flood.on net coolant-on not.0.in net coolant-in not.0.out => and_cool.in1 net coolant-out and_cool.out => halui.flood.off # same to toggle the spindle net spindle_in v_buttonlist.v_button_1 => spindle.in net spindle-on spindle.out => halui.spindle.start net spindle-on not.1.in net spindle-off not.1.out => and_spindle.in1 net spindle-out and_spindle.out => halui.spindle.stop

Is it clear? Otherwise post your config.

Norbert
Last edit: 9 years 8 months ago by newbynobi.

Please Log in or Create an account to join the conversation.

More
9 years 8 months ago #88016 by Patrik T
Hi Norbert
Thanks for making Gmoccapy, and thanks for helping me.
I thought this would be easy to fix when i knew what to look for, but I have removed all the custom hal files like this:
Code:
[HAL] HALUI = halui HALFILE = emco-lathe-gmoccapy.hal ;HALFILE = joypad.hal ;HALFILE = custom.hal ;POSTGUI_HALFILE = custom_postgui.hal # I also commented out the ui handler python script. [DISPLAY] #....... ;EMBED_TAB_NAME = xbox_1 ;EMBED_TAB_LOCATION = box_left ;EMBED_TAB_COMMAND = gladevcp -u myuihandler.py -x {XID} xboxgui.ui

I don't think I have made any changes in emco-lathe-gmoccapy.hal. Anyway, I have commented out everything but this:
Code:
# Generated by stepconf 1.1 at Sun Jan 22 06:31:44 2017 # If you make changes to this file, they will be # overwritten when you run stepconf again loadrt trivkins loadrt [EMCMOT]EMCMOT base_period_nsec=[EMCMOT]BASE_PERIOD servo_period_nsec=[EMCMOT]SERVO_PERIOD num_joints=[TRAJ]AXES loadrt hal_parport cfg="0x378 out" setp parport.0.reset-time 1000 loadrt stepgen step_type=0,0 loadrt encoder num_chan=1 loadrt abs count=1 loadrt scale count=1 loadrt lowpass count=1 #My stuff. #loadusr -W hal_input -KRAL Gamepad #loadusr io, was already loaded. addf parport.0.read base-thread addf stepgen.make-pulses base-thread addf encoder.update-counters base-thread addf parport.0.write base-thread addf parport.0.reset base-thread addf stepgen.capture-position servo-thread addf encoder.capture-position servo-thread addf motion-command-handler servo-thread addf motion-controller servo-thread addf stepgen.update-freq servo-thread addf abs.0 servo-thread addf scale.0 servo-thread addf lowpass.0 servo-thread #net spindle-cmd-rpm <= motion.spindle-speed-out #net spindle-cmd-rpm-abs <= motion.spindle-speed-out-abs # The rest is also commented out.

Still getting the startup warning. I don't know what else I can disable to locate the error.

Patrik

Please Log in or Create an account to join the conversation.

More
9 years 7 months ago - 9 years 7 months ago #88965 by Patrik T
Hi
New information:
I have managed to get rid of the startup warning by commenting out one line in the ini file,
[EMC] MACHINE = my-emco-lathe, see below.

Code:
# Generated by stepconf 1.1 at Sun Jan 22 06:21:10 2017 # If you make changes to this file, they will be # overwritten when you run stepconf again [EMC] ;MACHINE = my-emco-lathe DEBUG = 0

What does this mean? Where is this information used? Any ideas of where to go next?

Best regards
Patrik
Last edit: 9 years 7 months ago by Patrik T. Reason: Edited, I do not have full functionality on the machine as I erroneously stated initially.

Please Log in or Create an account to join the conversation.

More
9 years 7 months ago #88969 by Patrik T
Excuse my mildly confusing last post. I mistakenly thought EMC was an abbreviation for EMergenCy (stop).

Please Log in or Create an account to join the conversation.

More
9 years 7 months ago #88971 by Patrik T
Axis does not give any startup warnings if I switch to axis by doing this in the ini file, see below, and commenting some Gmoccapy stuff in the postgui.hal file.

Code:
[DISPLAY] DISPLAY = axis # CYCLE_TIME = 150

If I switch back to Gmoccapy with (or without) the same stuff commented out in the postgui.hal file, then the startup warning is still there.

Please Log in or Create an account to join the conversation.

Moderators: newbynobi, HansU
Time to create page: 0.355 seconds
Powered by Kunena Forum