Back
[00:16:26] <linuxcnc-build> build #3899 of 0000.checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/3899 blamelist: Norbert Schechner <nieson@web.de>, Jeff Epler <jepler@unpythonic.net>
[07:08:10] <KGB-linuxcnc> 03Dewey Garrett 05joints_axes11 a326dd8 06linuxcnc New branch with 246 commits pushed, 10527 files changed, 0326258(+), 0421054(-) since master/170bb5a
[09:31:32] <cradek> JT-Shop: I think you might want configure -r, not -a?
[09:32:26] <cradek> the -a kernel search is wonky and I bet only works with rtai
[09:32:36] <JT-Shop> ok thanks
[09:49:34] <pcw_home> I usually run the latency-histogram to see if things look OK
[09:49:36] <pcw_home> The 4.4-rt2 kernel is the best I've found for my Core Duo desktop and my (older) laptop
[09:49:38] <pcw_home> the previous one (4.1.rt15?) is better latency wise on a G3258 and Atom MBs
[09:50:37] <JT-Shop> ok, I'll do that when I get LinuxCNC installed
[10:11:25] <lair82> Hello Guys, I have a question regarding manually stopping the spindle during a running program, I have this function working on my turning centers, which are all using 2.6.4-5-6, ( some version of 2.6 ), and my mill is using 2.7.3. I programmed my mill the same way as my turning centers to use a start and stop PB on my control, but regardless of what I do, when the spindle restarts, it goes to max allowable spindle speed,
[10:11:26] <lair82> not back to what ever it was running before the stop.
[10:12:08] <lair82> Did something change in 2.7 or is there a way to do this, and I am missing the boat?
[10:15:15] <mozmck1> what is a "start and stop PB"?
[10:22:30] <lair82> Two physical pushbuttons on the front of my control
[10:25:08] <lair82> The way I have it setup is, a small relay breaks the analog signal going to the drive, and it stops, and starts back up at the programmed speed, but now on the mill, as soon as I stop the spindle ( open the relay contacts), I see the analog command voltage at the 7i49 imediatly go to 10 volts
[10:26:03] <lair82> It works fine in MDI, but in the middle of a running program, it takes off
[10:29:05] <JT-Shop> john@wheezy:~/lcnc/debian$ ./configure -r
[10:29:05] <JT-Shop> your kernel '4.4.0-rt2' is not known. There might be needed dependencies which won't get set automatically.
[10:29:05] <JT-Shop> successfully configured for 'Debian-7.9'-'4.4.0-rt2'..
[10:29:31] <JT-Shop> I'll have to get all the dependencies in the morning
[10:30:25] <mozmck1> lair82: I don't know - sounds like there is some feedback to linuxcnc - is the speed controlled with a PID component?
[10:46:30] <lair82> No, I do not use pid on the spindle, there are a few things, all that I know of, and can find, I have lied to in some fashion or another. I have the spindle at speed true all the time, as longs the control "thinks" it should be on, the I have the encoder feedback velocity tied into my logic, so when I manually stop the spindle it copies the commanded revs per second to the spindle-speed-in input, and still no dice.
[10:48:04] <cradek> encoder feedback velocity tied into my logic"
[10:48:16] <cradek> this part seems like the likely cause
[10:48:18] <cradek> but it's hard to guess
[10:48:35] <cradek> why don't you just set spindle override to 0% and then back to 100%?
[10:50:17] <pcw_home> is motion.spindle-speed-out wrong or is this further down the chain?
[10:50:39] <cradek> it has to be further down
[10:50:57] <cradek> I suggest using halmeter and searching for where it goes wrong
[10:52:50] <mozmck1> pcw_home: is there a way I can put a unique identifier in a bitfile for the 7i92 that I can read out later to verify which bitfile is loaded?
[10:53:01] <lair82> I haven't messed with the spindle-speed-out pin
[10:54:37] <lair82> The encoder velocity part was the last thing I tried, I was just going through all the motion related pins, and saw the motion.spindle-speed-in signal, and figured I would try working that over as well to see if it made a difference, not so
[10:55:20] <pcw_home> crc the IDROM
[10:56:31] <mozmck1> what is the IDROM?
[10:57:07] <pcw_home> IDROM V4 will have the config name and alternate pin names
[10:58:24] <pcw_home> the IDROM is a 256x32 ROM that has the pinout and module information of every Hostmot2 configuration
[10:58:25] <pcw_home> (the driver read this to determine the available modules and pinout)
[10:58:55] <pcw_home> might be nice if mesaflash could echo/check a CRC of this
[10:59:22] <mozmck1> Ah, ok. I can also just compare that info with the pinout I want - which is what I was planning if there was not an easier way.
[10:59:43] <mozmck1> crc would be pretty easy.
[12:14:33] <maxcnc> hi question im getting an error no modul named pango did i checkout the wrong branch
[12:15:40] <maxcnc> git checkout 2.6
[12:15:54] <maxcnc> 10.04 python 2.7
[12:28:31] <jepler> pango is required for linuxcnc. on debian systems, it is in package python-gtk2 which is a requirement of python-gtkglext1 which is listed as a dependency in debian/control.in
[12:30:39] <maxcnc> python-gtkglext1 is already the newest version.
[12:32:02] <jepler> python -c 'import pango'
[12:32:13] <jepler> ^^ if that encounters an error, then resolve it before continuing
[12:32:31] <maxcnc> No module named pango
[12:32:44] <maxcnc> cairo is also not on the system
[12:33:30] <maxcnc> python2.6 -c 'import pango' that got the files
[12:33:54] <maxcnc> but python 2.6 is not compiling i need 2.7
[12:34:11] <maxcnc> python 3.1 also no pango
[12:34:13] <jepler> are you trying to use linuxcnc master branch on ubuntu 10.04? that is not supported anymore.
[12:34:45] <maxcnc> what shoudt i checkout
[12:34:55] <maxcnc> 2.5
[12:35:28] <jepler> http://wiki.linuxcnc.org/cgi-bin/wiki.pl?MinimumSoftwareVersions is up to date as far as I know
[12:35:38] <maxcnc> thanks
[12:37:51] <jepler> it sounds like you have changed your ubuntu 10.04 system so that "python" is a version of python 2.7 you installed from some other source besides the regular ubuntu 10.04 package, and which doesn't have the same modules available as the system python2.6. you will have to fix this change you made on your system before linuxcnc will build.
[12:38:05] <jepler> it is hard for me to guess exactly what you've done and give you good advice
[12:38:08] <jepler> afk, time for lunch here.
[12:38:29] <maxcnc> i will go back to 2.6
[12:38:39] <maxcnc> python and linuxcnc
[12:40:21] <maxcnc> lrwxrwxrwx 1 root root 18 Jan 21 19:15 python -> /usr/bin/python2.6
[12:40:23] <maxcnc> lrwxrwxrwx 1 root root 25 Jan 21 19:15 python-config -> /usr/bin/python2.6-config
[12:40:33] <maxcnc> need to restart the systrem
[12:42:34] <maxcnc> Back
[12:44:02] <maxcnc> successfully configured for 'sim-Ubuntu-10.04'-'sim'..
[12:45:07] <maxcnc> this seas the problem git reset --hard origin/master
[12:45:35] <maxcnc> git reset --hard v2.6.11 mayber
[12:46:14] <maxcnc> i simply dont know the git code lineup
[12:46:32] <jepler> 13:25:53 <jepler> maxcnc: there is a version of the git book in german. I believe it is of good quality, it might be of help to you.
https://git-scm.com/book/de/v1
[12:47:01] <maxcnc> thanks
[12:50:00] <maxcnc> thats my problem all about version controling but not a simple lineup on howto from git clone
[12:50:49] <maxcnc> and not at all to find if i need to clone a branch or simply git clone git://git.linuxcnc.org/git/linuxcnc.git does the job and then a checkout to a brunch
[12:53:10] <maxcnc> HEAD is now at 25bd222... LinuxCNC 2.6.11
[12:55:50] <maxcnc> ;-)
[13:02:19] <maxcnc> thanks jepler you are the master of my desaster
[13:02:27] <maxcnc> works great
[13:27:12] <maxcnc> and now im stock in C++
[13:27:27] <maxcnc> as im not a C man
[13:28:10] <maxcnc> *x = s->current_x; the function is int Interp::find_current_in_system(setup_pointer s, int system, double *x, ...
[13:28:43] <maxcnc> for my understanding the function is called with the *x value
[13:29:13] <maxcnc> but *x= gets somthing from s->current_x;
[13:29:35] <maxcnc> brrr not sutobel fo a conventionel braiin
[13:30:49] <maxcnc> now does *x give its value to s->current_x parameter or the oposit
[13:43:18] <cradek> that is just an assignment. the thing pointed to by x gets assigned the value from s->current_x
[13:44:07] <cradek> since the function prototype has "double *x" it means x is a pointer to a double
[13:44:12] <maxcnc> you said i shoudt grap the value of _unoffset_x from here
[13:46:01] <maxcnc> can i do a s->unoffset_x = *x; and im done
[13:46:57] <maxcnc> in interp_find.cc
[13:47:20] <maxcnc> int Interp::find_current_in_system and int Interp::find_current_in_system_without_tlo
[13:47:46] <maxcnc> let me check this
[13:49:46] <lair82> cradek, it looks like that will work for now, setting override to 0%, but I have gotten a few random errors about trying to turn off spindle while in auto mode. So I will have to figure out how to get it to work with the buttons I believe.
[13:51:10] <maxcnc> NO emc/rs274ngc/interp_find.cc:476: error: invalid operands of types 'double' and 'double*' to binary 'operator*'
[13:52:00] <mozmck1> lair82: I'm not using the spindle speed stuff, but I use an "and" hal component and a checkbox on the screen so I can turn off "spindle" (really a plasma torch) while cutting.
[13:53:37] <mozmck1> lair82: So basically motion.spindle-on goes to one input of the and comp, and another signal controlled by a screen button (but could be a hardware button) to the other "and" input. Both must be active for the and.x.out pin to be active.
[14:02:13] <maxcnc> cradek: so wherer do i get the real value of the unoffset_x from
[14:09:00] <maxcnc> to be continued
[14:12:56] <lair82> mozmck1 It has to be some feedback to the control that it see's that makes it max out, as soon as it sees me shut off the analog command to the spindle drive. But that is my question, what is linuxcnc lookin at ( has to be something in motion) that is telling the the 7i49 pwmgen to go to full 10 VDC, to, I guess, get the spindle back up to speed??
[14:13:45] <lair82> It almost acts like it is pid controlled, but there is no pid any where dealing with the spindle
[14:13:49] <mozmck1> yeah, that's why I wondered if you had a PID component in there
[14:14:42] <mozmck1> I have not used a real spindle speed control yet, so I don't have any experience there.
[14:14:55] <lair82> I like going with the straight analog voltage, and then letting the drive do it's thing to control the motor.
[14:16:07] <mozmck1> Yeah, so it does this even if there is no feedback from the spindle at all?
[14:18:20] <lair82> Yes,
[14:18:40] <PCW> I would first check "motion.spindle-speed-out" to see if you see a problem there then
[14:18:42] <PCW> check that the PWM for the spindle analog out is set in the correct mode for a 7I49
[14:19:51] <PCW> ( The 7i49 needs up/down PWM mode, if its set for PWM/DIR havoc will ensue )
[14:20:02] <lair82> Ok PCW, of course they are throwing another part up on it as we speak, but I am taking some notes
[14:22:17] <PCW> AFAIK spindle speed is gcode --> interpreter --> motion.spindle-speed-out --> hal --> output device
[14:24:52] <lair82> It is set for up down mode
[14:28:48] <PCW> so what is the PWM scale and what is motion.spindle-speed-out when you get 10V (and dont expect it)
[14:48:35] <lair82> I know the pwm scale is 949, but I will have to wait on the motion.spindle-speed-out, he is indicating a part in on the machine right now.
[16:21:33] <PCW> PWM scale of 949 means 949 RPM is top speed, is that correct?