Vista CNC pendent install challenges

More
9 years 8 months ago #87725 by Jake
I am installing my new pendant, I am getting an error

Code:
vc-p4s.hal warning has dos style endings libusbx couldnt open usb device......permission denied libusbx requires write access to usb device nodes error could not insert module usr/realtime...............

I for the life of my can not remember how to copy the error message at the moment.
How do I copy it?

Do you have any ideas of where to go from here?

Thanks!

Please Log in to join the conversation.

More
9 years 8 months ago #87765 by Jake
I have gotten past the permission challenges,

now I have the error of
vc-p4s.hal:2 warning file contains dos style line endings
vc-p4s.hal: exit value: 1
vc-p4s.hal: insmod for and2 failed, returned -1
Code:
# 0---vc-p4s Control Pendant loadusr -W vc-p4s loadrt and2 names=and2.vc addf and2.vc servo-thread

Any ideas what is wrong with these lines?

Thanks!

Please Log in to join the conversation.

More
9 years 8 months ago #87778 by Jake
I got the DOS endings taken care of, gedit and saving the file correctly took care of that.

I removed the "and2" since I have "loadrt and2" in my load.hal file but I still have an error
Code:
loadrt and2 names=and2.vc


Code:
loadrt names=and2.vc

Please Log in to join the conversation.

More
9 years 8 months ago #87788 by tommylight

Jake wrote: I got the DOS endings taken care of, gedit and saving the file correctly took care of that.

I removed the "and2" since I have "loadrt and2" in my load.hal file but I still have an error

Code:
loadrt and2 names=and2.vc


Code:
loadrt names=and2.vc


That will not work, you need to have that in a single line, so you can add it to the existing line. That implies that if you already have 1 and2 loaded it automaticly gets the name "and2.0" and that is the name used in the rest of the hal file. Now to add 2 more as you need them it should be like this
Loadrt and2 names=and2.0,and2.1,vc
Also add them to the servo thread, and when connecting other things to them use the "and2.1" and "vc" names

Please Log in to join the conversation.

More
9 years 8 months ago #87795 by Jake
I changed my and2 to the2.2 and took off the .vc through the rest of the hal file. It gets past the first few lines but now I am at an error on line 99 halui.mdi-command-06 does not exist. I have been reading some other pendant threads that have had this problem, but can not seem to find exactly what they did to fix it.
Code:
# 0---vc-p4s Control Pendant HURCO BMC30 02/10/2017 loadusr -W vc-p4s #loadrt and2 names=and2.2 addf and2.2 servo-thread
Code:
net zero-x vc-p4s.zero-x => halui.mdi-command-05 net zero-y vc-p4s.zero-y => halui.mdi-command-06 net zero-z vc-p4s.zero-z => halui.mdi-command-07

99 is the second line

Please Log in to join the conversation.

More
9 years 8 months ago #87797 by Jake
I added a enough lines to MDI_COMMAND in the ini file and that made that happy. Now I have upset my ESTOP logic somewhere, LCNC will open, just cant get it out of ESTOP now.

I guess I need to figure out how to make the pendent estop and my estop happy.

PPMC ESTOP
Code:
#ESTOP net ppmcEstop ppmc.0.din.estop.in net ppmcEstop and2.0.in0 net EstopOkIn estop-latch.0.fault-in net EstopOkIn and2.0.out net EstopOkOut ppmc.0.dout.07.out net EstopOkOut ppmc.0.dout.Estop.out net EstopOkOut iocontrol.0.emc-enable-in net EstopOkOut estop-latch.0.ok-out net EstopOkOut and2.0.in1 net emc-estop-out iocontrol.0.user-enable-out net emc-estop-out estop-latch.0.ok-in net emc-estop-reset iocontrol.0.user-request-enable net emc-estop-reset estop-latch.0.reset

P4S ESTOP
Code:
# 13---E-STOP net estop vc-p4s.estop.activate => halui.estop.activate net reset vc-p4s.estop.reset => halui.estop.reset net estop-is-activated halui.estop.is-activated => vc-p4s.estop.is-activated

Any ideas on making them both happy?

Thanks@!

Please Log in to join the conversation.

More
9 years 8 months ago #87798 by Jake

Jake wrote: I added a enough lines to MDI_COMMAND in the ini file and that made that happy. Now I have upset my ESTOP logic somewhere, LCNC will open, just cant get it out of ESTOP now.

I guess I need to figure out how to make the pendent estop and my estop happy.

PPMC ESTOP

Code:
#ESTOP net ppmcEstop ppmc.0.din.estop.in net ppmcEstop and2.0.in0 net EstopOkIn estop-latch.0.fault-in net EstopOkIn and2.0.out net EstopOkOut ppmc.0.dout.07.out net EstopOkOut ppmc.0.dout.Estop.out net EstopOkOut iocontrol.0.emc-enable-in net EstopOkOut estop-latch.0.ok-out net EstopOkOut and2.0.in1 net emc-estop-out iocontrol.0.user-enable-out net emc-estop-out estop-latch.0.ok-in net emc-estop-reset iocontrol.0.user-request-enable net emc-estop-reset estop-latch.0.reset

P4S ESTOP
Code:
# 13---E-STOP net estop vc-p4s.estop.activate => halui.estop.activate net reset vc-p4s.estop.reset => halui.estop.reset net estop-is-activated halui.estop.is-activated => vc-p4s.estop.is-activated

I think something in my and2 has upset it.


out of the pendant.hal
Code:
# 0---vc-p4s Control Pendant HURCO BMC30 02/10/2017 loadusr -W vc-p4s loadrt and2 names=and2.2 addf and2.2 servo-thread


out of my load.hal
Code:
# make some signals for the scope for tuning. loadrt ddt count=5 loadrt estop_latch count=1 loadrt and2 count=5 loadrt near count=5 loadrt lowpass count=5 loadrt conv_s32_float count=5 loadrt mult2 count=5 loadrt abs count=5 loadrt lut5 count=2 addf and2.0 servo-thread addf and2.1 servo-thread #addf and2.2 servo-thread addf near.1 servo-thread

out of the io.hal
Code:
#ESTOP net ppmcEstop ppmc.0.din.estop.in net ppmcEstop and2.0.in0 net EstopOkIn estop-latch.0.fault-in net EstopOkIn and2.0.out net EstopOkOut ppmc.0.dout.07.out net EstopOkOut ppmc.0.dout.Estop.out net EstopOkOut iocontrol.0.emc-enable-in net EstopOkOut estop-latch.0.ok-out net EstopOkOut and2.0.in1 net emc-estop-out iocontrol.0.user-enable-out net emc-estop-out estop-latch.0.ok-in net emc-estop-reset iocontrol.0.user-request-enable net emc-estop-reset estop-latch.0.reset

Any ideas on making them both happy? LCNC will start, I just cant get it out of estop now. The hardwire estop chain is happy, just not the software one.

Thanks@!

Please Log in to join the conversation.

More
9 years 4 months ago #94997 by 10K
Sorry no one answered your thread at the beginning of the year!

I'm having the same problem with my VistaCNC pendant. It won't let LinuxCNC run after you hit the power button. It's this line in the INI file that's doing it:
Code:
net estop vc-p2s.estop.activate => halui.estop.activate

Did you ever figure this out?

I do know the answer to the DOS-style line endings. It's just a warning, but I had the same problem. Install tofrodos
Code:
sudo apt-get install tofrodos

and then run this command
Code:
fromdos (filename)

Please Log in to join the conversation.

More
9 years 4 months ago #95057 by Jake
Thanks 10K !

I had figured it out. Since I have Pico PPMC, I moved one of the lines in the estop chain down a line, the PPMC was not happy with it. It wants its Estop line to come before anything else, as its way to pet the watchdog.

I did use the editor in Debian and saved all the files as Linux endings and it solved it also.

Please Log in to join the conversation.

More
9 years 4 months ago #95059 by 10K
Thanks for the reply! Glad you got your system working.

Could you be more specific on the changes you made? Were they to the pendant HAL or your machine HAL file? Which estop command was the problem? I have estop net assignments in both the pendant and machine HAL files.

machine HAL
Code:
net estop-ext <= hm2_7i92.0.gpio.013.in_not net estop-out <= iocontrol.0.user-enable-out net estop-ext => iocontrol.0.emc-enable-in

pendant HAL
Code:
net estop vc-p2s.estop.activate => halui.estop.activate net reset vc-p2s.estop.reset => halui.estop.reset net estop-is-activated halui.estop.is-activated => vc-p2s.estop.is-activated

Please Log in to join the conversation.

Time to create page: 0.109 seconds
Powered by Kunena Forum