Back
[11:48:06] <mozmck> Using python, can I read a HAL parameter from another component? All the samples I find only show reading pins etc from the HAL component associated with that python module.
[11:51:49] <cradek> no, surely you have to make them pins and connect them together
[11:55:24] <mozmck> ok, I thought surely I could do that.
[11:56:00] <mozmck> My thought was to reduce the number of pins that get checked and updated
[11:56:34] <cradek> I guess the hal utils like halmeter read parameters from others, but I think they do that by manipulating the hal shm goop directly
[11:56:53] <mozmck> hmm, ok
[11:57:36] <mozmck> If a setup has many hal pins and signals, will that potentially slow things down on a slower computer?
[11:57:44] <cradek> if two components need to communicate values, pins are the normal way? not sure what you're facing here that led you to want a different way.
[11:58:59] <cradek> once pins are connected, they are just pointers. I think how many other pins exist doesn't affect how fast reading/writing through a pointer is.
[11:59:48] <cradek> there are limits to the number of pins, though, because the max hal shared memory size is fixed
[12:00:01] <cradek> but it's not a speed issue, it's a space issue
[12:00:41] <mozmck> Ok, I guess I don't know how some of that works still.
[12:02:58] <mozmck> Do signals get updated at the base thread rate?
[12:04:41] <mozmck> Or do they change all connected pins as soon as the signal is changed?
[12:05:24] <cradek> with signals there is no copying, everything is a pointer to one memory location
[12:05:37] <cradek> so all read and write operations on it are atomic
[12:07:12] <cradek> so in a servo thread component if you read a pin twice in a single run of your function, you might get two different values (if a base thread component preempts you and changes it in between your reads)
[12:08:41] <mozmck> hmm, ok. So linking a pin to a signal sets the pins pointer to the signal location? Where does it point to when not linked? Maybe I should just read some more code and quit asking all these questions :)
[12:08:55] <cradek> yes
[12:09:09] <cradek> when not linked it points to a private dummy spot
[12:09:49] <mozmck> I see. thanks for the information. I'll use pins then and connect them.
[12:09:59] <cradek> 8702094f3779 is an example of being defensive against preemption changing a value in the middle of some calculations
[12:12:33] <mozmck> If that's a git commit, I can't find it.
[12:12:39] <cradek> err, maybe it's not, I don't understand that change
[12:14:53] <cradek> aha I wasn't the only one: df3f3609bd9 finishes it
[12:17:47] <mozmck> ok, I found those commits, and understand I believe.
[12:21:06] <mozmck> I think it's like the read-modify-write problem in some microcontrollers.
[12:41:06] <ju_emb> linuxcnc channel is busy with house building so sorry if I ask here about some doubt's I have
[12:41:43] <ju_emb> what is the relation in the ini file between velocities and scale?
[12:42:26] <ju_emb> I put down the scale to match my machine and she becomes slow in movement
[12:46:21] <mozmck> Maybe you need to change the max velocity?
[12:47:53] <ju_emb> My problem is, beside of making that machine work, I like to understand that.
[12:48:30] <ju_emb> and Doc's say's Velocities are in machine units per time
[12:48:49] <ju_emb> so scale shouldn't have a influence on it
[12:48:50] <mozmck> SCALE sets the steps-per-unit, so if it takes 5000 steps to move an inch, your scale should be 5000
[12:49:13] <ju_emb> that I understand
[12:49:32] <ju_emb> in my case I have 2.9 steps per unit
[12:49:45] <archivist> scale changes how many steps per time at max velocity
[12:51:23] <mozmck> Yes, scale will influence it. If it takes 2.9 steps per unit (I guess that's mm?), but you set scale to 6 steps per unit, then the machine will move 6 steps and think it has gone 1 unit, but it really went 2.x units
[12:53:21] <mozmck> So the machine actually moved twice as fast as it thought it was moving.
[12:54:21] <ju_emb> that's OK and I understand it. What I don't understand is max velocity is 25 mm/s scale is 80 machine runs but doesn't have the scale
[12:55:09] <mozmck> I don't understand that sentence - "doesn't have the scale"?
[12:55:10] <ju_emb> so that means she generates makes 25 * 80 steps per sec
[12:55:55] <mozmck> Yes
[12:56:14] <ju_emb> sorry, she does not run the distance she shout because physical setup is 2.9 steps per unit
[12:56:42] <mozmck> I see, that means you missed something in calculating the scale.
[12:57:09] <mozmck> If you are using steppers, how many microsteps is it set to?
[12:57:18] <ju_emb> now I put scale in 2.9 without changing velocities
[12:57:51] <ju_emb> she generates means 25 * 2.9 steps per second
[12:58:32] <ju_emb> but she should still run at 25mm per sec
[12:59:40] <ju_emb> mazmck: is fullstep
[13:00:45] <mozmck> Look on page 19 of the Getting Started manual for more information about SCALE
[13:01:05] <mozmck> bbl
[13:48:23] <mozmck> Can you pass a haltcl file to gladevcp with -H?
[20:11:28] <KGB-linuxcnc> 03Jeff Epler 05jepler/linuxcnc-deps 84e0671 06linuxcnc 10debian/configure 03debian/control-alldeps.in 10debian/control.in 03debian/rules-alldeps.in debian/configure: improvements * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=84e0671
[20:12:15] <linuxcnc-build> build #1250 of 1400.rip-wheezy-i386 is complete: Failure [4failed install-missing-build-dependencies configuring] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1400.rip-wheezy-i386/builds/1250 blamelist: Jeff Epler <jepler@unpythonic.net>
[20:23:20] <linuxcnc-build> build #245 of 1903.clang-wheezy-amd64 is complete: Failure [4failed install-missing-build-dependencies compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1903.clang-wheezy-amd64/builds/245 blamelist: Jeff Epler <jepler@unpythonic.net>
[20:23:36] <jepler> yay I totally busted it
[20:23:57] <jepler> geez did I even test it (no)
[20:28:16] <KGB-linuxcnc> 03Jeff Epler 05jepler/linuxcnc-deps 8f7717b 06linuxcnc 10debian/configure 03debian/control-alldeps.in 10debian/control.in 03debian/rules-alldeps.in debian/configure: improvements * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=8f7717b
[20:31:05] <linuxcnc-build> build #1250 of 1403.rip-wheezy-amd64 is complete: Failure [4failed install-missing-build-dependencies compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1403.rip-wheezy-amd64/builds/1250 blamelist: Jeff Epler <jepler@unpythonic.net>
[20:31:50] <linuxcnc-build> build #1441 of 1404.rip-wheezy-rtpreempt-amd64 is complete: Failure [4failed install-missing-build-dependencies compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1404.rip-wheezy-rtpreempt-amd64/builds/1441 blamelist: Jeff Epler <jepler@unpythonic.net>
[20:34:15] <linuxcnc-build> build #761 of 1402.rip-wheezy-rtpreempt-i386 is complete: Failure [4failed install-missing-build-dependencies compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1402.rip-wheezy-rtpreempt-i386/builds/761 blamelist: Jeff Epler <jepler@unpythonic.net>
[20:34:29] <linuxcnc-build> build #245 of 1902.clang-wheezy-rtai-i386 is complete: Failure [4failed install-missing-build-dependencies compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1902.clang-wheezy-rtai-i386/builds/245 blamelist: Jeff Epler <jepler@unpythonic.net>
[20:34:41] <linuxcnc-build> build #911 of 1401.rip-wheezy-rtai-i386 is complete: Failure [4failed install-missing-build-dependencies compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1401.rip-wheezy-rtai-i386/builds/911 blamelist: Jeff Epler <jepler@unpythonic.net>
[20:40:24] <linuxcnc-build> build #1280 of 1405.rip-wheezy-armhf is complete: Failure [4failed install-missing-build-dependencies compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1405.rip-wheezy-armhf/builds/1280 blamelist: Jeff Epler <jepler@unpythonic.net>
[20:43:22] <linuxcnc-build> build #3092 of 1300.rip-precise-i386 is complete: Failure [4failed install-missing-build-dependencies compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1300.rip-precise-i386/builds/3092 blamelist: Jeff Epler <jepler@unpythonic.net>
[20:43:40] <linuxcnc-build> build #3094 of 1306.rip-precise-amd64 is complete: Failure [4failed install-missing-build-dependencies compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1306.rip-precise-amd64/builds/3094 blamelist: Jeff Epler <jepler@unpythonic.net>
[20:44:08] <linuxcnc-build> build #3093 of 1200.rip-lucid-i386 is complete: Failure [4failed install-missing-build-dependencies compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1200.rip-lucid-i386/builds/3093 blamelist: Jeff Epler <jepler@unpythonic.net>
[20:45:04] <linuxcnc-build> build #2296 of 1301.rip-precise-rtai-i386 is complete: Failure [4failed install-missing-build-dependencies compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1301.rip-precise-rtai-i386/builds/2296 blamelist: Jeff Epler <jepler@unpythonic.net>
[20:45:44] <linuxcnc-build> build #3093 of 1202.rip-lucid-amd64 is complete: Failure [4failed install-missing-build-dependencies compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1202.rip-lucid-amd64/builds/3093 blamelist: Jeff Epler <jepler@unpythonic.net>
[20:48:45] <linuxcnc-build> build #3093 of 1201.rip-lucid-rtai-i386 is complete: Failure [4failed install-missing-build-dependencies compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1201.rip-lucid-rtai-i386/builds/3093 blamelist: Jeff Epler <jepler@unpythonic.net>
[20:48:46] <linuxcnc-build> build #3103 of 0000.checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/3103 blamelist: Jeff Epler <jepler@unpythonic.net>
[20:52:26] <linuxcnc-build> build #3094 of 1201.rip-lucid-rtai-i386 is complete: Failure [4failed install-missing-build-dependencies configuring] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1201.rip-lucid-rtai-i386/builds/3094 blamelist: dummy, Jeff Epler <jepler@unpythonic.net>
[20:55:26] <jepler> go home jeff, we know you mean well
[21:12:01] <linuxcnc-build> build #912 of 1401.rip-wheezy-rtai-i386 is complete: Failure [4failed install-missing-build-dependencies compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1401.rip-wheezy-rtai-i386/builds/912 blamelist: dummy, Jeff Epler <jepler@unpythonic.net>
[21:12:14] <linuxcnc-build> build #246 of 1902.clang-wheezy-rtai-i386 is complete: Failure [4failed install-missing-build-dependencies compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1902.clang-wheezy-rtai-i386/builds/246 blamelist: dummy, Jeff Epler <jepler@unpythonic.net>
[21:14:14] <KGB-linuxcnc> 03Jeff Epler 05jepler/linuxcnc-deps 31e1919 06linuxcnc 10debian/configure 03debian/control-alldeps.in 10debian/control.in 03debian/rules-alldeps.in debian/configure: improvements * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=31e1919
[21:14:24] <jepler> this would go better if I had any systems left with rtai on them
[21:21:19] <linuxcnc-build> build #3104 of 0000.checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/3104 blamelist: dummy, Jeff Epler <jepler@unpythonic.net>
[21:31:16] <memfrob> jepler: i have a system with rtai
[21:31:23] <memfrob> i can test :)
[21:31:52] <memfrob> oh build dependencies.. :/ not a debian based distro though
[21:33:26] <jepler> I'll stick with buildbot .. worst thing is it spams this channel
[22:14:15] <mozmck> jepler: have you looked at the new configure stuff seb did? I made a minor change to it as well. In the mozmck/new-deb-conf branch
[22:14:46] <mozmck> seb's original is in the seb/master/new-deb-configure branch