Advanced Search

Code from terminal

linuxcnc
LINUXCNC - 2.9.0~pre1+git20230208.f1270d6ed7
Machine configuration directory is '/home/cnc/linuxcnc/configs/T17'
Machine configuration file is 'T17.ini'
Starting LinuxCNC...
linuxcnc TPMOD=tpmod HOMEMOD=homemod EMCMOT=motmod
Note: Using POSIX realtime
Found file(REL): ./T17.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: 10.10.10.10: INFO: Hardware address (MAC): 00:60:1b:16:03:5b
hm2_eth: discovered 7I96
hm2/hm2_7i96.0: Low Level init 0.15
hm2/hm2_7i96.0: Smart Serial Firmware Version 43
hm2/hm2_7i96.0: 51 I/O Pins used:
hm2/hm2_7i96.0: IO Pin 000 (TB3-01): IOPort
hm2/hm2_7i96.0: IO Pin 001 (TB3-02): IOPort
hm2/hm2_7i96.0: IO Pin 002 (TB3-03): IOPort
hm2/hm2_7i96.0: IO Pin 003 (TB3-04): IOPort
hm2/hm2_7i96.0: IO Pin 004 (TB3-05): IOPort
hm2/hm2_7i96.0: IO Pin 005 (TB3-06): IOPort
hm2/hm2_7i96.0: IO Pin 006 (TB3-07): IOPort
hm2/hm2_7i96.0: IO Pin 007 (TB3-08): IOPort
hm2/hm2_7i96.0: IO Pin 008 (TB3-09): IOPort
hm2/hm2_7i96.0: IO Pin 009 (TB3-10): IOPort
hm2/hm2_7i96.0: IO Pin 010 (TB3-11): IOPort
hm2/hm2_7i96.0: IO Pin 011 (TB3-13/TB3-14): SSR #0, pin Out-00 (Output)
hm2/hm2_7i96.0: IO Pin 012 (TB3-15/TB3-16): SSR #0, pin Out-01 (Output)
hm2/hm2_7i96.0: IO Pin 013 (TB3-17/TB3-18): SSR #0, pin Out-02 (Output)
hm2/hm2_7i96.0: IO Pin 014 (TB3-19/TB3-20): SSR #0, pin Out-03 (Output)
hm2/hm2_7i96.0: IO Pin 015 (TB3-21/TB3-22): SSR #0, pin Out-04 (Output)
hm2/hm2_7i96.0: IO Pin 016 (TB3-23/TB3-24): SSR #0, pin Out-05 (Output)
hm2/hm2_7i96.0: IO Pin 017 (TB1-02/TB1-03): StepGen #0, pin Step (Output)
hm2/hm2_7i96.0: IO Pin 018 (TB1-04/TB1-05): StepGen #0, pin Direction (Output)
hm2/hm2_7i96.0: IO Pin 019 (TB1-08/TB1-09): StepGen #1, pin Step (Output)
hm2/hm2_7i96.0: IO Pin 020 (TB1-10/TB1-11): StepGen #1, pin Direction (Output)
hm2/hm2_7i96.0: IO Pin 021 (TB1-14/TB1-15): StepGen #2, pin Step (Output)
hm2/hm2_7i96.0: IO Pin 022 (TB1-16/TB1-17): StepGen #2, pin Direction (Output)
hm2/hm2_7i96.0: IO Pin 023 (TB1-20/TB1-21): StepGen #3, pin Step (Output)
hm2/hm2_7i96.0: IO Pin 024 (TB1-22-TB1-23): StepGen #3, pin Direction (Output)
hm2/hm2_7i96.0: IO Pin 025 (TB2-02/TB2-03): StepGen #4, pin Step (Output)
hm2/hm2_7i96.0: IO Pin 026 (TB2-04/TB2-05): StepGen #4, pin Direction (Output)
hm2/hm2_7i96.0: IO Pin 027 (TB2-07/TB2-08): Encoder #0, pin A (Input)
hm2/hm2_7i96.0: IO Pin 028 (TB2-10/TB2-11): Encoder #0, pin B (Input)
hm2/hm2_7i96.0: IO Pin 029 (TB2-13/TB2-14): Encoder #0, pin Index (Input)
hm2/hm2_7i96.0: IO Pin 030 (TB2-16/TB2-17): IOPort
hm2/hm2_7i96.0: IO Pin 031 (TB2-18/TB2-19): IOPort
hm2/hm2_7i96.0: IO Pin 032 (internal): IOPort
hm2/hm2_7i96.0: IO Pin 033 (internal): SSR #0, pin AC Ref (internal) (Output)
hm2/hm2_7i96.0: IO Pin 034 (P1-01/DB25-01): IOPort
hm2/hm2_7i96.0: IO Pin 035 (P1-02/DB25-14): IOPort
hm2/hm2_7i96.0: IO Pin 036 (P1-03/DB25-02): IOPort
hm2/hm2_7i96.0: IO Pin 037 (P1-04/DB25-15): IOPort
hm2/hm2_7i96.0: IO Pin 038 (P1-05/DB25-03): IOPort
hm2/hm2_7i96.0: IO Pin 039 (P1-06/DB25-16): IOPort
hm2/hm2_7i96.0: IO Pin 040 (P1-07/DB25-04): IOPort
hm2/hm2_7i96.0: IO Pin 041 (P1-08/DB25-17): IOPort
hm2/hm2_7i96.0: IO Pin 042 (P1-09/DB25-05): IOPort
hm2/hm2_7i96.0: IO Pin 043 (P1-11/DB25-06): IOPort
hm2/hm2_7i96.0: IO Pin 044 (P1-13/DB25-07): IOPort
hm2/hm2_7i96.0: IO Pin 045 (P1-15/DB25-08): IOPort
hm2/hm2_7i96.0: IO Pin 046 (P1-17/DB25-09): IOPort
hm2/hm2_7i96.0: IO Pin 047 (P1-19/DB25-10): IOPort
hm2/hm2_7i96.0: IO Pin 048 (P1-21/DB25-11): IOPort
hm2/hm2_7i96.0: IO Pin 049 (P1-23/DB25-12): IOPort
hm2/hm2_7i96.0: IO Pin 050 (P1-25/DB25-13): IOPort
hm2/hm2_7i96.0: registered
Found file(lib): /usr/share/linuxcnc/hallib/qtplasmac_comp.hal
Found file(REL): ./custom.hal
QSocketNotifier: Can only be used with threads started with QThread
Can't jog any joints while homing.
emc/task/taskintf.cc 976: Error on joint 0, command number 106
task: main loop took 0.145498 seconds
task: main loop took 0.159640 seconds
task: main loop took 0.166205 seconds
joint 3 on limit switch error
emc/task/taskintf.cc 976: Error on joint 3, command number 364
task: main loop took 0.218127 seconds
/usr/bin/linuxcnc: line 974: 8429 Segmentation fault $EMCDISPLAY -ini "$INIFILE" $EMCDISPLAYARGS $EXTRA_ARGS
Shutting down and cleaning up LinuxCNC...
Running HAL shutdown script
task: 41912 cycles, min=0.000008, max=0.218127, avg=0.010067, 4 latency excursions (> 10x expected cycle time of 0.010000s)
hm2_eth: in hm2_eth_reset
hm2_eth: HostMot2 ethernet driver unloaded
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

Nice setup old chap, puts my merger efforts at PCB design to shame.

I remember there was a thread about the BSPI thing, tried searching but couldn't find it.

Disclaimer:
The below are all my own opinions and 99.99% of the time aren't worth the time spent reading. Also the fact I use a modified version of English, Australian, and was more interested in watching clouds at school or seeing how long it took to get chucked out of the class, record was walking in the door, not saying a word and being asked to leave,may also make the below difficult to make sense of.

Whether you believe something to be this way or that way doesn't make it so. The only way to find out for sure is to ask, sometimes those that hold that info may not want to share.

User structure, who edits what.
Hmm not too sure about that or what you mean.

Who can put new versions of LinuxCNC online?
I'd be guessing the core dev team, I generally just build from source and make my own deb packages. Actually when I was sharing my Mint iso I was also putting up new packages, the Debian pacakges weren't an easy install on Mint at the time, on a server I paid for myself (along with the domain name). I got the hump with people expecting weekly updates, the depression started hitting me hard so I said, fuck em.

Who edits the wiki?
wiki.linuxcnc.org/cgi-bin/wiki.pl?BasicSteps
I haven't felt the need to, plus I'm not good at explaining stuff. I doubt many are aware that it exists. I doubt many realise Linuxcnc has a home page or any other pages apart from the forum. There's a lot of historical info there on the wiki. In reality it comes down to users adding to the wiki, if no one wants to add anything it may stay, shall we say stale. In saying that it does make for an interesting read. Tho we seem to be in a culture where everything needs to be up the minute relevant.


Forum admins ?
I guess the guys that are the most knowledgable, have the best input (and don't lose their rag or spit the dummy..you know stable sort of chaps) and are chosen, via whatever method, by the other admins. Not something that I feel a regular user should be concerned about.

If you really are concerned about the direction of things it may be of use to join the mailing list and start asking questions there.

To tell the truth I've never had any security issues come from using the forum. I can't remember it being down to some "script kiddie" or other nefarious player. Sure from time to time the spammers turn up. Tommy & co usually jump on it quick. There also the chance to be active if this respect and report it.

I'm working on a low-cost retrofit for my Deckel FP4A and I really want to reuse the existing motors, but I'd like to replace the stock Industrial Drives drives with ones that operate on single phase 220VAC, so in order to do that in an affordable way I think I need to use a resolver to SSI converter to get absolute position data from the motors for commutation by the drives. I'm wondering if anyone has gone down this road before and had any insight to add.

Currently I think I want to use the Delta ASDA-A2 drive and a Vega 2796524 Resolver to SSI Converter, has anyone tried this before?

I'm still going through all the datasheets I can find, but based on what I've found so far, I think this should be a workable solution.

Ideally I would be using a drive that can natively handle resolver feedback, but I haven't had any luck finding such a drive for a reasonable price. Any info is greatly appreciated!

Luckly the company that built the machine vfd sent me the manual.

Just checked the price for an EL4102 costs more than a new recent VFD, are there other ways to control the spindle with ethercat?

The VFD allow to control rpm in many ways:

0/10v
-10/10v
0/20mA
4/20mA
By serial

Are you going with ColorCNC by romanetz or LiteX-CNC.

Either way the basic thing is, your create a config for the firmware using a json file, follow the instructions to build the firmware, upoad the bit file to the Colorlight board, then create a Linuxcnc config & ini files.

Litex-CNC (it's been awhile since I decided not to use this as I felt it was easier to go another route.)
So, no one does not upload a config to the board, a new bit file has to be built.

The way I tackle a new project.
Read the whole thread, take notes, follow the link on the github page to the docs, read the docs, have a browse around the github page. Take a bit of time to get the feel.
Setup a build environment, and attempt to build a config. Then I'd modify one of the supplied configs to get a hang of it.
Eventually I'll upload a bit file to the board, probably from one of the supplied json files. Reread the read or refer to any note regarding creating a hal file.
May take a couple of nights or weeks depending on a lot of things. You may find you'll have to read & reread & reread some more. I'm sure there's some examples scattered about in the thread.
Research is the key point. All the info is there.
If you don't fully understand how it works, you may have to find someone to do the hard work for you. Or have a look of one of the more active projects, maybe Linuxcnc-RIO, which uses a larger range of FPGA boards (even the mesa clone I designed works with Linuxcnc-RIO) and doesn't rely on the ever changing availability or certain Colorlight boards being available and actually being shipped to you.

I think there won't be any problems with this. The main thing is to understand what needs to be done with the control board, in particular with colorlight. As I understand it, the author of the topic dropped the firmware files from this board and not only the author. i.e. all the files for changing and assigning ports are there. In fact, you just need to upload the files changed to your parameters to the board. Is that correct?

Cant do this anymore bye all wrote:

I like the fact there’s no adds.

I agree with you!

Cant do this anymore bye all wrote:

It would nice to see a link of method to donate a few coins. If I’ve missed it if someone has a link it would be appreciated.

Du hast Recht, das habe ich auch noch nicht gesehen, aber das ändert nichts an der Grundproblematik.

Cant do this anymore bye all wrote:

Whilst the editor is a pain, switching to “source view” can make life easier for edits.

It's not just the editor.
The site and I believe the forum are no longer included in the updates (security update).
Many functions have been deactivated or are not working properly.

Hence the desire to update something here.
(I am ignorant though)
- User structure, who edits what.
- Who can put new versions of LinuxCNC online?
- Who edits the wiki?
- Forum administrators, ....
- ... etc.

There are so many different places in the background that I don't know, as I'm just a normal user, so I can't estimate all the consequences, hence my suggestion.

Guys need help new to linux cnc
just starting to build my 1st cnc
using linux cnc
any recommendations for my setting 
 

my solution is convert analog out of vfd ( config analog out is load ) to fequency + use mesa card counter function

Usually, an analog input is required. However, another option is to connect an RS232/RS485 interface to the spindle inverter. I chose the second option, and it works well. You can skip to the 1-minute mark in the video to see it in action. There's a small bug with the numbers, though

Is that just a y thing?

Is it possible to run all these things together: 

Mesa 7i76 E  ---- 7I84 (Isolated remote field I/O card). Will use it to output quadrature signals to the Ultra3000s, it will generate this quadrature output from the Fanuc encoders [is this possible?], remaining I/O used elsewhere. 
                               
                         ---- 7I85 (4 Channel encoder 5 channel Serial RS-422 interface). Will hook up the 4 Fanuc redcaps to 4 of these RS-422 ports. And the encoder inputs are good to have around incase I want to add linear scales (2 axis) and maybe two MPG wheels. 

Sure would be great if this system worked because it happens to be two fairly inexpensive boards. Canadian dollar isn't so great right now 
I would be pleased to have those encoder inlets, too. 

Progress pic from a little while ago: 
 

Licenses were reviewed in depth by Debian as part of getting into their distros. (There are many different licenses) I think you can say the differences in licenses is not a conflict or we would not be in Debian

If the axis do not move, I would check:

1. That you don't have a watchdog bite
(If you are running "Axis" it will report this if not,
you may need to check with halshow)


2. The physical wiring (remember I asked what were the
connections between TB2 pins and drive signals?)


3. The timing specifications of the drives (the current timings should work
with most drives but there are so oddball drives with really slow inputs)