#linuxcnc-devel | Logs for 2014-01-08

[00:49:22] <memleak> works here..
[00:50:07] <eric_unterhausen> fixed
[00:50:20] <memleak> sweet!
[07:43:51] -kornbluth.freenode.net:#linuxcnc-devel- [freenode-info] why register and identify? your IRC nick is how people know you. http://freenode.net/faq.shtml#nicksetup
[08:29:54] <skunkworks> pcw, if you do have some extra time - I would love it if you would test a working card with my motherboard/hd...
[08:30:17] <skunkworks> (I am sure you have tons of extra time..)
[08:33:33] <pcw_home> already set back (well minus the hard drive which we forgot and will send back today)
[08:33:47] <cradek> what did you find?
[08:33:54] <pcw_home> I'm really certain its a driver bug
[08:35:28] <skunkworks> That's ok. I am glad it probably wasn't me :)
[08:36:03] <pcw_home> which is not really surprising since the code churn needed to packetize
[08:36:05] <pcw_home> all the read commands throughout the code is not likely to be right the first time
[08:37:08] <pcw_home> the WD is funny also since it has its own function so its a likely trouble spot
[08:39:01] <pcw_home> actually all the packetizing is good for HM2 in general (PCI/EPP/Ethernet/SPI/Serial all benefit by doing all I/O in a burst)
[08:39:28] <skunkworks> why is the wd different?
[08:39:38] <skunkworks> * what makes the wd different
[08:39:52] <pcw_home> it has its own function
[08:40:01] <skunkworks> oh - I was thinking HD vs wd (watchdog..) hever mind
[08:41:51] <skunkworks> (no coffee yet this morning)
[08:43:01] <skunkworks> can you run the 7i80 without the watch dog?
[08:43:10] <pcw_home> sure
[08:43:31] <pcw_home> not a good idea in general...
[08:43:31] <skunkworks> (for testing purposes... of course..)
[08:45:53] <pcw_home> hmm the manual says its always enabled so maybe you can't disable it
[08:46:09] <pcw_home> I can always make a config with no WD
[08:47:56] <skunkworks> eh - no hurry.. lets see what micges comes up with
[08:48:23] <skunkworks> (I was just reading the same manual)
[13:46:52] <KGB-linuxcnc> 03John Thornton 05v2.5_branch 77638db 06linuxcnc 10docs/src/gcode/gcode.txt Docs: add link to replace vague description * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=77638db
[13:58:52] <KGB-linuxcnc> 03Norbert Schechner 05master f2f694d 06linuxcnc 10share/gscreen/skins/gmoccapy/gmoccapy_handler.py 10share/gscreen/skins/gmoccapy/release_notes.txt gmoccapy_0_9_9_7_6 - solved bug in units after startup * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=f2f694d
[13:58:52] <KGB-linuxcnc> 03Norbert Schechner 05master c28f88d 06linuxcnc Merge branch 'master' of ssh://norbert@git.linuxcnc.org/git/linuxcnc.git * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=c28f88d
[14:13:39] <KGB-linuxcnc> 03Norbert Schechner 05master be8da3e 06linuxcnc 10share/gscreen/skins/gmoccapy/gmoccapy_handler.py 10share/gscreen/skins/gmoccapy/release_notes.txt gmoccapy_0_9_9_7_6 - getting away from unneeded data * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=be8da3e
[14:27:06] <KGB-linuxcnc> 03Norbert Schechner 05master 79a426e 06linuxcnc 10share/gscreen/skins/gmoccapy/gmoccapy_handler.py 10share/gscreen/skins/gmoccapy/release_notes.txt gmoccapy_0_9_9_7_6 - get away from gscreen preference * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=79a426e
[15:23:38] <PCW> anonimasu: we decided not to produce the analog interface to the 8I20 (the 8C20)
[15:24:06] <alex_joni> PCW: wrong channel ;)
[15:24:45] <PCW> oops
[18:44:22] <memleak> what's the top of the line mesa card nowadays?
[18:46:19] <andypugh> I would guess the 5i22 by the price :-)
[19:03:46] <Tom_itx> cradek, that code causing 2.6 to burp came from here: http://linuxcnc.org/hardy/dapper/index.php/russian/forum/47-hal-examples/9518-pauseresume-button-using-one-input
[19:08:51] <seb_kuzminsky> memleak: depends on what you want
[19:09:09] <seb_kuzminsky> if i was building a machine i'd go for a 5i23
[19:09:39] <Tom_itx> 5i25 too small?
[19:22:41] <andypugh> There are more daughter cards available.
[19:23:59] <andypugh> My machine is based around a 5i23. I have Resolvers (7i49) smart-serial devices (7i44 to 3 x 8i20 + 7i64) and a 7i39 connected.
[19:46:19] <memleak> how elaborate can you get with a series of mesa cards with linuxcnc? andypugh that seems like quite a chain reaction!
[19:46:49] <Tom_itx> how elaborate do you want to get?
[19:47:44] <andypugh> On that same machine I could also connect a 7i80HD to the ethernet port (for all the same cards again) and a 7i43 to the P-port (for somw of them)
[19:48:09] <Tom_itx> i'm testing boards but i've got a 7i43 with a 7i47 and 2 sserial cards tied off the 7i47
[19:48:15] <andypugh> Basically, if you can plug them in, then they will work.
[19:48:34] <Tom_itx> a 7i84 and 7i71
[19:48:44] <andypugh> At some point you will run out of CPU to service them
[19:48:51] <Tom_itx> yeah sserial is pretty nice for adding IO
[19:50:10] <cradek> Tom_itx: have you figured out what's wrong with it? what has changed in master to break it?
[19:50:20] <andypugh> But a machine with one PCI port, one parallel port and a single ethernet card could support 4608 IO lines, and more than that inside the spec (sserial can handle 96 IO linse per card, but most cards only have 48)
[19:50:29] <Tom_itx> i haven't had a chance to test it anymore
[19:51:02] <Tom_itx> i was reviewing the logic when i found jt's post
[19:51:17] <andypugh> With deep enough pockets 10,000 GPIO lines is doable
[20:06:09] <KGB-linuxcnc> 03Norbert Schechner 05master 34e7cde 06linuxcnc 10share/gscreen/skins/gmoccapy/gmoccapy_handler.py 10share/gscreen/skins/gmoccapy/release_notes.txt gmoccapy_0_9_9_7_6 - no more gscreen.emc or gscreen.ini * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=34e7cde
[20:11:38] <KGB-linuxcnc> 03Norbert Schechner 05master e258356 06linuxcnc 10share/gscreen/skins/gmoccapy/gmoccapy_handler.py gmoccapy_0_9_9_7_6 - forgot to add some wait_complete * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=e258356
[20:13:51] <Tom_itx> cradek this is what it's _supposed_ to do: http://tom-itx.dyndns.org:81/~webpage/cnc/configs/sherline/Pause-resume.jpg
[21:05:30] <memleak> heh 10,000 GPIOs
[21:40:07] <cradek> Tom_itx: funky! I'll be happy to hear where exactly it's failing... might be a bug to fix before 2.6.
[21:41:22] <Tom_itx> doesn't look quite so bad in a diagram :)
[21:42:29] <cradek> yes and drawing that is a very important debugging step, if you're anything like me
[21:42:54] <Tom_itx> well it's what i did when i coded it
[21:47:02] <Tom_itx> two things i can think of on this are does toggle2nist hold the output states _and_ are the halui.program.pause and halui.program.resume affected by being held in state?
[21:47:19] <Tom_itx> earlier today i was looking at ways to pulse the outputs instead
[23:26:32] <psha> logger[mah]_: .
[23:26:32] <logger[mah]_> psha: Log stored at http://linuxcnc.mah.priv.at/irc/%23linuxcnc-devel/2014-01-09.html