Homemade CNC Plasma - hypertherm, Mesa, gear drives, nema 34.

More
1 year 8 months ago #320577 by RNJFAB
Halshow has the reading fluctuating from about -3650 -> +3650 with no plasma source having power.

in linuxcnc, the arc reading sits at -29

Jumping the B input?

Confirmed - mesa i/o pin 10 is lighting up when I should get an arc-ok input from the plasma, but linuxcnc isn't showing this.

Current codes

 

Attachment not found

Attachment not found

Attachment not found

Please Log in to join the conversation.

More
1 year 8 months ago #320589 by tommylight

Halshow has the reading fluctuating from about -3650 -> +3650 with no plasma source having power.
Repeating myself here, interference, lots of it, so check the wiring and especially the grounding, ground loops will cause havoc.

Please Log in to join the conversation.

More
1 year 8 months ago #320640 by rodw
>Halshow has the reading fluctuating from about -3650 -> +3650 with no plasma source having power.
you have a 0 volt frequency of 3637 in you system so 3650 is expected. The swings are not
There is something not right in hal, like you have a double ended encoder or something.

Please Log in to join the conversation.

More
1 year 8 months ago #320645 by PCW
+- velocity values are not possible in counter mode unless you have noise on the "B" input

Try jumpering the "B" input for single ended mode
(and make sure nothing is connected to either "B" input at TB2)

 

Please Log in to join the conversation.

More
1 year 8 months ago #320719 by RNJFAB
Thanks PCW.

Yes, I had the Ohmic sensing into the B encoder input on TB2.

Once this was unpluged, Encoder velocity stayed at 0. or flucuated to -3750.

Grounded everything i could and moved plasma source 30cm further away.

And hey presto.





 

Please Log in to join the conversation.

More
1 year 8 months ago #320766 by PCW
Yes, I had the Ohmic sensing into the B encoder input on TB2.

That's OK with 7i96dpl.bit firmware (that has three separate encoder 'A' pins)

Please Log in to join the conversation.

More
1 year 8 months ago #321522 by RNJFAB
Thanks PCW.

I'll try an reconnect the ohmic to a different encoder A pin.

Also need to work on the air scribe next.

Please Log in to join the conversation.

More
1 year 8 months ago #322576 by RNJFAB
Its been a very busy few days. slowly getting tools dialed in for the new machine. Still a long way to go with ohmic sensing and the air scribe, but I'm happy with how everything is moving. the factory hypertherm cut charts are about 1000mm/min off what is actually working.

Please Log in to join the conversation.

More
1 year 6 months ago #325797 by RNJFAB
so working away and everything is going great, until. went to cut some plate today for the air scribe, turn everything on and then, she no connect. Worked fine a few days ago.

This is the error and i can't find a fix. Help

$ linuxcnc
LINUXCNC - 2.9.3-125-g62642dde63
Machine configuration directory is '/home/cnc/linuxcnc/configs/T19'
Machine configuration file is 'T19.ini'
Starting LinuxCNC...
linuxcnc TPMOD=tpmod HOMEMOD=homemod EMCMOT=motmod
Note: Using POSIX realtime
Found file(REL): ./T19.hal

identityKinematicsSetup: coordinates:XYYZ
   Joint 0 ==> Axis X
   Joint 1 ==> Axis Y
   Joint 2 ==> Axis Y
   Joint 3 ==> Axis Z
identityKinematicsSetup: Recommend: kinstype=both

hm2: loading Mesa HostMot2 driver version 0.15
hm2_eth: loading Mesa AnyIO HostMot2 ethernet driver version 0.2
hm2_eth: ERROR: Could not retrieve hardware address (MAC) of 10.10.10.10: Connection refused
hm2_eth: rtapi_app_main: Connection refused (-111)
./T19.hal:9: waitpid failed /usr/bin/rtapi_app hm2_eth
./T19.hal:9: /usr/bin/rtapi_app exited without becoming ready
./T19.hal:9: insmod for hm2_eth failed, returned -1
Shutting down and cleaning up LinuxCNC...
Running HAL shutdown script
hm2: unloading
Note: Using POSIX realtime
LinuxCNC terminated with an error.  You can find more information in the log:
    /home/cnc/linuxcnc_debug.txt
and
    /home/cnc/linuxcnc_print.txt
as well as in the output of the shell command 'dmesg' and in the terminal



 

Please Log in to join the conversation.

More
1 year 6 months ago #325798 by tommylight
I would guess you changed the IP on the PC ....
That error is almost always due to PC having the IP set at 10.10.10.10 (or 192.168.1.121), set it to anything else for the last 2 (or 3) digits:
10.10.10.11 is fine
192.168.1.100 is fine
etc.
Edit:
check with
ip a

Please Log in to join the conversation.

Time to create page: 0.128 seconds
Powered by Kunena Forum