#linuxcnc-devel | Logs for 2016-01-10

[07:36:37] <KGB-linuxcnc> 03John Thornton 052.7 bd249c6 06linuxcnc 10docs/src/getting-started/getting-linuxcnc.txt Docs: change the method of installing uspace. * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=bd249c6
[09:22:02] <jepler> JT-Shop: can you tell me more about why it's better to start with the linuxcnc image than a regular debian image, if the goal is to get a uspace linuxcnc?
[09:26:05] <jthornton> because sudo is not set up in the vanilla debian so the second step fails
[09:32:10] <jthornton> I could not figure out a way to execute sudo apt-get update from the vanilla debian
[09:53:18] <JT-Shop> just thinking more on this and perhaps it could be done via the synaptic package manager, I'll test that way tomorrow
[09:56:31] <JT-Shop> what does apt-get dist-upgrade do? the same as update?
[10:21:38] <jepler> I see.
[10:21:59] <jepler> no, the differences have to do with whether apt is willing to install new packages and/or remove installed packages to complete the request.
[11:05:20] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15pkmcnc opened issue #26: pncconf generates "setp pid.N.maxerror .0005" for all axes in hal for servo configs 02https://github.com/LinuxCNC/linuxcnc/issues/26
[11:12:04] <seb_kuzminsky> jthornton: i'm pretty sure i've installed a vanilla debian wheezy & jessie and had sudo work fine
[11:12:38] <seb_kuzminsky> oh man, having issues show up on irc makes me like github even more
[11:22:12] <JT-Shop> seb_kuzminsky: I followed the original instructions and link and downloaded wheezy and sudo was not set up
[11:22:34] <JT-Shop> I wonder if different desktops have sudo set up
[11:26:08] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15jepler commented on issue #25: @SebKuzminsky didn't you fix this in master branch? 02https://github.com/LinuxCNC/linuxcnc/issues/25#issuecomment-170371188
[11:27:42] <cncbasher> whats up with sudo JT
[11:30:37] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15jepler opened issue #27: sserial: everything goes south after a single error 02https://github.com/LinuxCNC/linuxcnc/issues/27
[11:31:29] <JT-Shop> I installed a vanilla wheezy and sudo was not configured so I could not get uspace
[11:32:33] <JT-Shop> any way to shorten up -linuxcnc-github/#linuxcnc-devel- ? it messes up my chat window...
[11:34:23] <Roguish> JT-Shop: I think you are right. sudo does not inherently come in debian, but is included in some desktops. you can always install sudo and add a sudo user and password., then install uspace
[11:35:13] <JT-Shop> I didn't find any easy ways to add sudo
[11:35:31] <JT-Shop> I forget the exact error I got
[11:35:55] <Roguish> how about plain old su?
[11:37:49] <JT-Shop> I "think" I tried that too
[11:38:13] <JT-Shop> I can't reinstall it right now to test pay bandwidth time now
[11:40:13] <Roguish> which exact iso are you installing?'
[11:42:06] <seb_kuzminsky> JT-Shop: i'm pretty sure i gave an empty root password, maybe that triggers it to install sudo?
[11:42:48] <Roguish> I can do a vm install to test ...
[11:43:49] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15SebKuzminsky closed issue #25: halcompile with "option userspace yes" claims to support count= and names= arguments, but does not 02https://github.com/LinuxCNC/linuxcnc/issues/25
[11:43:55] <seb_kuzminsky> jepler: thanks for the reminder
[11:44:08] <seb_kuzminsky> whoops: docs/src/gui/images/gmoccapy_3_axis.png.png | Bin 0 -> 152044 bytes
[11:47:22] <micges> jepler: for 2.7 I think disabling transmition error reporting like it was in 2.6 is best solution
[11:47:36] <micges> jepler: re sserial
[11:54:51] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15floppydisk525 commented on issue #27: I don't know if this helps you or not but here are two 'results' from my 5i25/7i77 setup. One from 2.6.8 (I think) and one from 2.7.x. ... 02https://github.com/LinuxCNC/linuxcnc/issues/27#issuecomment-170373019
[11:55:33] <pcw_home> Heres what I think is the proper handling of serial faults:
[11:55:34] <pcw_home> http://freeby.mesanet.com/sserial-faults.txt
[11:55:36] <pcw_home> If something fancier was needed it might be two categories oinc/dec parameters for severe (data loss) or minor (warning ) errors
[11:56:28] <KGB-linuxcnc> 03Sebastian Kuzminsky 052.6 57f68ab 06linuxcnc 10VERSION 10debian/changelog LinuxCNC v2.6.12 * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=57f68ab
[11:56:28] <KGB-linuxcnc> 03Sebastian Kuzminsky 05signed tags affb38e 06linuxcnc 03v2.6.12 LinuxCNC v2.6.12 (tagged commit: 57f68ab) * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=affb38e
[11:57:58] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15micges commented on issue #27: Masking non-fatal errors should help, this patch ignore extra character errors... 02https://github.com/LinuxCNC/linuxcnc/issues/27#issuecomment-170373201
[11:59:57] <pcw_home> The main problem is the 2.7 reporting doesnt account for the fact that some errors
[11:59:59] <pcw_home> are sticky and need to be qualified by the (non sticky) error category bits (8 and 13)
[12:00:59] <pcw_home> the other part is that remote errors are sticky and usually major so should be only reported once
[12:01:11] <KGB-wlo> test-linuxcnc-org branch deleted
[12:03:38] <seb_kuzminsky> 2.7.0 is 4 months old now and the 2.7 branch seems pretty good, i'm thinking of stopping maintenance of the 2.6 branch
[12:10:07] <archivist> chasing version upgrades for some of us is near impossible
[12:11:08] <seb_kuzminsky> archivist: do you mean, upgrading from one major version (like 2.6) to the next (like 2.7) is hard or inconvenient for some people?
[12:12:35] <archivist> I have one on 2.4 one/two on 2.5.4 the cost of PCs to be able to use more memory
[12:13:20] <archivist> I just hate LTS support being dropped and being cast adrift
[12:14:19] <seb_kuzminsky> we try to support linuxcnc on the underlying LTS distros as long as the underlying distros are supported by upstream
[12:29:17] <linuxcnc-build> build #3074 of 1301.rip-precise-rtai-i386 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1301.rip-precise-rtai-i386/builds/3074 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[12:39:59] <linuxcnc-build> build #3877 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/3877 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[12:52:24] <kwallace> Way off topic but kinda cool: https://www.youtube.com/watch?v=xWCmXvWM0ZY
[12:53:36] <seb_kuzminsky> hm, that's an interesting new runtest failure above...
[12:53:37] <seb_kuzminsky> libnml/os_intf/_shm.c 206: shmget(1004(0x3EC),1024,0) failed: (errno = 2): No such file or directory
[12:53:51] <seb_kuzminsky> linuxcnc-build: force build --branch=2.6 0000.checkin
[12:53:52] <linuxcnc-build> build forced [ETA 1h15m16s]
[12:53:52] <linuxcnc-build> I'll give a shout when the build finishes
[13:08:21] <seb_kuzminsky> micges, jepler, pcw_home: after you guys figure out the sserial thing i'll release 2.7.4 with your fix
[13:08:50] <pcw_home> That would be great!
[13:09:13] <jthornton> seb_kuzminsky: if you figure out how you set up the vanilla wheezy for uspace please let me know what you did
[13:15:41] <jepler> step 1. be a 20-year vetran of linux step 2. install it
[13:15:56] <jepler> unfortunately I'm not good at writing more detailed instructions, and anyway the first step takes too long
[13:18:10] <jthornton> yea, I've only got 10 years under my belt...
[13:24:40] <pcw_home> Ubuntu and Mint seem to have the expected sudo behavior, are you saying stock debian Wheezy is different?
[13:31:27] <skunkworks> I know you have to setup sudo on jessie
[13:32:31] <skunkworks> it is pretty easy IIRC - you just have to add the user to sudo then re-login
[13:37:28] <brianmorel99> I think that is what I had to do in Wheezy. Use su and add my user to the sudo group. Are you getting a file not found error or an error that says you aren’t allowed to use it?
[13:39:22] <JT-Shop> it gave some error about not set up
[13:41:59] <brianmorel99> I’m pretty sure this is what I had to do. https://wiki.debian.org/sudo
[13:47:00] <linuxcnc-build> Hey! build 0000.checkin #3878 is complete: Success [3build successful]
[13:47:00] <linuxcnc-build> Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/3878
[13:49:15] <skunkworks> yes - I think just adduser foo sudo
[13:49:31] <skunkworks> but you have to log out - back in for it to be in affect
[13:50:42] <seb_kuzminsky> i dont remember doing any of that
[13:50:59] <seb_kuzminsky> trying a fresh install now to see what i did
[13:51:23] <Roguish> seb: what iso are you using?
[13:53:49] <skunkworks> I used the network install image
[13:54:56] <Roguish> https://www.debian.org/releases/wheezy/debian-installer/
[13:59:52] <pcw_home> must be something the install script does
[14:12:21] <seb_kuzminsky> the one i've been using for the past 1.5 years is called debian-7.5.0-amd64-CD-1.iso
[14:12:55] <seb_kuzminsky> ok, it just asked me for the hostname and domain name, and now it's asking for the root password
[14:12:58] <seb_kuzminsky> it says:
[14:13:30] <seb_kuzminsky> "The root user should not have an empty password. If you leave this empty, the root account will be disabled and the system's initial user account will be given the power to become root using the "sudo" command."
[14:13:42] <seb_kuzminsky> so i just hit enter, even though it sort of says not to...
[14:14:00] <seb_kuzminsky> it asks me to verify the empty root password, so i hit enter again
[14:14:28] <seb_kuzminsky> then it asks me for the full name for the new user
[14:14:32] <JT-Shop> I need to revert the manual change and add that bit of info. I just entered a password and kept on trucking
[14:14:49] * JT-Shop goes back to lumberjacking while the sun shines
[14:15:03] <seb_kuzminsky> oooh, he's a lumberjack and he's ok
[14:15:24] <Roguish> the current wheezy available is 7.9.0
[14:15:35] <Roguish> http://cdimage.debian.org/cdimage/archive/7.9.0/amd64/iso-cd/
[14:16:03] <Roguish> a real Paul Bunyan
[14:36:02] <micges> seb_kuzminsky: if you put any password there you'll have to make this adduser bla sudo thing
[14:48:31] <seb_kuzminsky> micges: right
[14:49:02] <seb_kuzminsky> i've run without a root login for years and years now, just using sudo as needed, i'm happy with that way of doing things
[14:49:49] <micges> pcw_home: after remote fault, bit 8 will be cleared after next doit?
[14:52:57] <pcw_home> Yes but most remote faults are sticky so it doesn't help
[14:53:55] <pcw_home> Thats why they should be reported only once
[14:56:21] <micges> ok and stop/start will clear remote faults?
[14:58:36] <pcw_home> yes (currently thats only done by reloading linuxcnc)
[15:06:54] <micges> ok
[15:22:02] ChanServ changed topic of #linuxcnc-devel to: http://linuxcnc.org | Latest releases: 2.7.3 and 2.6.12 | (this channel is logged by the zlog robot)
[15:25:27] <KGB-wlo> push to master branch: http://linuxcnc.org/
[15:45:34] <pcw_home> remote faults like under or overvoltage or overcurrent need to be fixed in the hardware
[15:45:35] <pcw_home> so it not really an issue that you need to stop linuxcnc to reset them
[15:45:37] <pcw_home> (and they should just be reported once so you dont generate a stream of redundent error messages)
[15:50:01] <pcw_home> transient FPGA side errors like CRC error, extra character etc (the ones qualified by bit 13 being set after a doit)
[15:50:02] <pcw_home> should go through the inc/dec filter so nuisance messages can be eliminated
[15:50:04] <pcw_home> (maybe with inc=200 dec=1 and threshold=1000 as defaults so you need 5 errors in a row to complain and 200 good transfers erase one bad one)
[16:16:49] <KGB-linuxcnc> 03Chris Morley 052.7 a14da9b 06linuxcnc 10src/emc/usr_intf/pncconf/build_HAL.py pncconf: fix setting or PID maxerror on servo configs * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=a14da9b
[16:18:03] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15c-morley commented on issue #26: confirmed and a fix pushed to 2.7 branch (will come out in next release).... 02https://github.com/LinuxCNC/linuxcnc/issues/26#issuecomment-170397552
[16:50:05] <seb_kuzminsky> cmorley: do you have enough authorization on github.org/linuxcnc to close that issue? or should we add you somehow?
[16:50:46] <cmorley> I don't know if I do... let me see if I can figure it out..
[16:51:35] <seb_kuzminsky> when i look at the issue page, down at the bottom, below the "type a comment here" text box, there's a button labeled "Close issue", right next to the button labeled "Comment"
[16:53:20] <seb_kuzminsky> bbl
[16:53:24] <cmorley> so then it seems I cant close it. if you can add me great otherwise feel free to close it :0
[17:05:21] <jepler> cmorley: do you have github account? I believe I can add you to the list of people who can close issues.
[17:06:45] <jepler> also for your reference I think you could have done it by saying "closes #NN" in your commit message, though I haven't tested this. https://help.github.com/articles/closing-issues-via-commit-messages/
[17:07:19] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15jepler closed issue #26: pncconf generates "setp pid.N.maxerror .0005" for all axes in hal for servo configs 02https://github.com/LinuxCNC/linuxcnc/issues/26
[17:08:36] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15jepler commented on issue #26: Fixed in commit a14da9b135ee82b8aa1 02https://github.com/LinuxCNC/linuxcnc/issues/26#issuecomment-170401487
[17:22:49] <micges> pcw_home: after doit command reg have 1 on bits where was communication error, but it will be 0 on channel with only remote error?
[17:45:22] <pcw_home> a 1 in the _data_ register after a doit indicates a transfer failure
[17:45:24] <pcw_home> remote errors dont effect this, in fact you need a successful transfer to fetch the remote error data
[17:46:54] <micges> right
[18:00:24] <cmorley> jepler: yes I have an account: c-morley
[18:16:10] <jepler> cmorley: did we go through this once already? it seems familiar. if we did, I wonder if the permission was lost when the repo was moved from my name to linuxcnc...
[18:16:58] <jepler> cmorley: I think you can now close issues, let me know if you still can't.
[18:17:10] <cmorley> we had a sourceforge pasword problem you helped me with a while back
[18:18:03] <cmorley> we i can close issues now thank you.
[18:18:08] <cmorley> yes
[18:18:15] <cmorley> yes i can even
[18:21:02] <jepler> good.