#linuxcnc-devel | Logs for 2016-09-09

[01:02:13] <linuxcnc-build> build #594 of 4017.5.deb-wheezy-armhf is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4017.5.deb-wheezy-armhf/builds/594 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[01:15:51] <linuxcnc-build> build #21 of 4025.deb-jessie-armhf is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4025.deb-jessie-armhf/builds/21 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[03:22:46] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15nicokid opened pull request #161: Bugfix for stepconf (06master...06master) 02https://github.com/LinuxCNC/linuxcnc/pull/161
[06:46:15] <skunkworks> zlog
[08:07:43] <jepler> it's entirely clear to my programmer brain what I'm trying to explain about "it is an error if...." but apparently not to humans
[08:09:14] <archivist> I was thinking you may have overstated the removal of a text precludes later change, I sort of went wtf
[08:11:59] <jepler> In my second post I did not try to be very nuanced
[08:13:05] <jepler> but yeah, if G18.1 G76 ... is defined by the documentation (by the absence of "this is an error if" text) and the implementation to do a threading cycle in ZX, then it takes a very high bar to say, OK, let's change it to be a WU threading cycle instead
[08:13:15] <jepler> because real part programs out in the world that obeyed the documentation will break
[08:16:08] <archivist> I think some future possibilities should be in the text, so you know now it would be an error but expect change or like he asks has actual error messages rather than default to something not mentioned
[08:24:35] <archivist> so something like: it is currently an error if not along Z (will default to yada)
[09:44:02] <cradek> I am sympathetic both to jepler's position and also the position that if the docs say a thing is an error, the interpreter should give an error when you do it
[17:51:25] <JT-Shop> which 5i25 firmware would be the same as two parallel ports?
[18:01:35] <Tom_L> JT-Shop did you do much dos programming in the day?
[18:14:47] <JT-Shop> just a bit of batch files, my first programming was in FoxPro
[18:23:56] <pcw_mesa> 5I25 firmware needs to be built for the specific hardware (to get things like step/dir pins in the right places)
[18:27:39] <JT-Shop> ok, I should have known that but it's been a long day lol
[18:27:40] <JT-Shop> thanks
[18:28:12] <pcw_mesa> (there are several prebuilt bit files that match many standard breakouts)
[18:28:14] <pcw_mesa> 5i25_r990x2.bit 5i25_mx3660x2.bit 5i25_dmmbob1x2.bit
[18:28:15] <pcw_mesa> 5i25_hdbb2.bit 5i25_benezanx2D.bit 5i25_prob_rfx2.bit
[18:28:17] <pcw_mesa> 5i25_g540x2.bit 5i25_bstechx2.bit
[18:28:18] <pcw_mesa> are all parallel port compatible
[18:29:19] <JT-Shop> I don't see the 5i25_hdbb2.bit 5i25_benezanx2D.bit files what are they for?
[18:29:32] <pcw_mesa> and its about a 10 minute exercise for me to make a new one if the desired pinout is known
[18:30:08] <pcw_mesa> the benezan is for the Benezan tripple beast
[18:30:36] <JT-Shop> sounds like me running the 308, I know the key presses by heart and don't even look at the keyboard
[18:30:52] <pcw_mesa> Ive forgotten what hdbb stands for
[18:31:18] <pcw_mesa> hd breakout board probably
[18:31:30] <pcw_mesa> whoever HD are...
[18:31:54] <JT-Shop> while we are chatting is the 7i92M replacing the 7i92?
[18:32:20] <pcw_mesa> if the pin file is not available you can (rather awkwardly) use mesaflash to create a .pin file
[18:33:06] <pcw_mesa> Yes the M and H models are all we will have for a while (and M is a couple weeks out)
[18:33:12] <JT-Shop> with --readhmid or whatever it is
[18:33:25] <JT-Shop> ok thanks
[18:33:42] <pcw_mesa> really just a cable difference (and M can do without a cable in some cases)
[18:34:12] <JT-Shop> yea that makes more sense to my pea brain to just plug it into the daughter card
[18:35:28] <pcw_mesa> sudo mesaflash --device 5i25 --write somebitfile.bit
[18:35:30] <pcw_mesa> sudo mesaflash --device 5i25 --reload
[18:35:31] <pcw_mesa> sudo mesaflash --device 5i25 --readhmid > somebitfile.pin
[18:36:01] <JT-Shop> ah use redirect to send it to a file
[18:39:23] <pcw_mesa> if you are considering making a configuration tool ( for 2.8+ ) you might consider using use the new GPIO aliases
[18:40:31] <pcw_mesa> makes the HAL files more readable and portable
[18:40:45] <JT-Shop> I am working on one, thanks for the tip on the GPIO aliases
[18:41:36] <JT-Shop> I decided to simplify it and target card family like 5i25/6i25 and reuse some routines between configuration tools
[18:41:44] <JT-Shop> at least that is the current plan
[18:42:15] <JT-Shop> saves a lot of choices up front and makes the UI a bit simpler
[18:44:00] <pcw_mesa> yeah theres a lot of factoring that can be done
[18:44:47] <JT-Shop> for a HF start plasma you use the THCAD-300?
[18:46:11] <pcw_mesa> GPIO aliases mean for things like inverting a stepgen output you say
[18:46:12] <pcw_mesa> setp hm2_7i92.0.stepgen.00.direction.invert_output true
[18:46:14] <pcw_mesa> rather than
[18:46:16] <pcw_mesa> setp hm2_7i92.0.gpio.014.direction.invert_output true
[18:46:43] <JT-Shop> that is much easier to follow
[18:46:49] <pcw_mesa> yes you can use a THCAD300
[18:47:31] <pcw_mesa> not only more readable but it does not change with hardware pinout
[18:49:37] <JT-Shop> the 7i92 would be the only part that changes? like to 5i25
[18:55:58] * JT-Shop listens to Telstar then retires for the night
[18:57:02] <Roguish> gentlemen. My press brake has 2 motors with tachs, not encoders. Is there a Mesa solution for them? I need a drive.
[18:58:35] <JT-Shop> do the tachs feed back to the drives or are the drives doa
[18:58:43] <Roguish> I also have 4 motors with encoders. a 7i40L is good for 2 of them. but i need more power for other 2.
[18:59:02] <Roguish> the tachs feed to the ancient drives, which I want to replace.
[18:59:43] <JT-Shop> can you fit an encoder and drive with a vfd?
[19:00:21] <Roguish> I can probably replace the tach with an encoder, but I am trying to modify as little present hardware as possible.
[19:00:35] <Roguish> brush dc motors
[19:00:56] <JT-Shop> I understand
[19:01:08] <cradek> do the drives work?
[19:01:12] <Roguish> about size 34 motors.
[19:01:32] <JT-Shop> well maybe I'll listen to sam the sham then go inside
[19:01:44] <Roguish> I have no idea if the drives work. it's a late 80's Cincinatti press brake.
[19:02:09] <Roguish> rumors in the shop are that 'it just doesn't work.'
[19:02:20] <cradek> heh
[19:02:38] <JT-Shop> I love to hear it's the Allen Bradley that is broke
[19:02:43] <Roguish> hey, cradek. you wrote touchy, huh?
[19:02:46] <cradek> the sysadmin equivalent is "my computer is down"
[19:02:56] <JT-Shop> lol yep
[19:03:02] <cradek> I don't readily admit to something like that
[19:03:08] <JT-Shop> lol
[19:03:26] <Roguish> i would like to mod it to fit the press brake. it's to be a pretty simple 6 independent axes machine.
[19:03:46] <cradek> cool
[19:04:19] <Roguish> i may ask a few questions. I am NOT a programmer, but i'm pretty good at modifying.
[19:04:30] <cradek> same here
[19:04:38] <Roguish> you are tooooo modest.
[19:05:04] <JT-Shop> same here
[19:06:38] <JT-Shop> time to retire to the cocina
[19:06:42] <Roguish> you're modest too JT?
[19:07:58] <JT-Shop> I'll buy you a beverage of your choice one day
[19:08:35] <cradek> JT-Shop: we still haven't met have we?
[19:09:07] <JT-Shop> nope, one day I need to make it up that way
[19:09:24] <JT-Shop> say goodnight Gracie
[19:09:39] <Roguish> goodnight Gracie....
[19:09:42] <cradek> bye
[19:09:48] <Roguish> ciao
[23:14:20] <KimK> Roguish: Still around?
[23:15:10] <KimK> You're talking about a programmable back gauge, right?
[23:16:12] <KimK> How did it work to begin with? I mean how did it measure position? Was there a linear scale somewhere on the back gauge?
[23:18:58] <KimK> Back gauges generally have light-duty motors for their size, and are geared down quite a bit, so sometimes a simple toothed disc with index hole is enough to get by. Maybe it does have an "encoder" somewhere?
[23:19:36] <KimK> I'll be nearby for awhile.