#linuxcnc-devel Logs

Nov 07 2018

#linuxcnc-devel Calendar

03:22 AM linuxcnc-build: build #2388 of 4015.deb-wheezy-rtpreempt-amd64 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4015.deb-wheezy-rtpreempt-amd64/builds/2388 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
03:28 AM linuxcnc-build: build #4526 of 4008.deb-precise-amd64 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4008.deb-precise-amd64/builds/4526 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
03:33 AM linuxcnc-build: build #4526 of 4007.deb-precise-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4007.deb-precise-i386/builds/4526 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
03:36 AM linuxcnc-build: build #3356 of 4009.deb-precise-rtai-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4009.deb-precise-rtai-i386/builds/3356 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
03:38 AM linuxcnc-build: build #3095 of 4016.deb-wheezy-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4016.deb-wheezy-i386/builds/3095 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
04:06 AM linuxcnc-build: build #2354 of 4014.deb-wheezy-rtpreempt-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4014.deb-wheezy-rtpreempt-i386/builds/2354 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
04:24 AM linuxcnc-build: build #2786 of 4018.deb-wheezy-rtai-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4018.deb-wheezy-rtai-i386/builds/2786 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
04:33 AM linuxcnc-build: build #3098 of 4017.deb-wheezy-amd64 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4017.deb-wheezy-amd64/builds/3098 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
04:42 AM linuxcnc-build: build #1767 of 4022.deb-jessie-amd64 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4022.deb-jessie-amd64/builds/1767 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
04:43 AM linuxcnc-build: build #1769 of 4021.deb-jessie-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4021.deb-jessie-i386/builds/1769 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
04:46 AM linuxcnc-build: build #1656 of 4019.deb-jessie-rtpreempt-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4019.deb-jessie-rtpreempt-i386/builds/1656 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
04:48 AM linuxcnc-build: build #1655 of 4020.deb-jessie-rtpreempt-amd64 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4020.deb-jessie-rtpreempt-amd64/builds/1655 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
04:51 AM linuxcnc-build: build #550 of 4031.deb-stretch-rtpreempt-amd64 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4031.deb-stretch-rtpreempt-amd64/builds/550 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
04:55 AM linuxcnc-build: build #550 of 4030.deb-stretch-rtpreempt-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4030.deb-stretch-rtpreempt-i386/builds/550 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
09:24 AM jepler: I have considered making the "supported architecture" check say "no" for all architectures in a couple of these branches, but it would create an additional speed bump when merging that branch back in to master so I resist.
09:25 AM jepler: still, I wish cmorley would take some steps to avoid this noise for us
09:25 AM jepler: seb_kuzminsky: all the same, thanks for fixing it so we can hear linuxcnc-build again
09:32 AM mozmck: I think I'm going to merge external offsets...
09:56 AM mozmck: Shouldn't branches which have been merged be deleted at some point?
09:58 AM seb_kuzminsky: mozmck: yes, they should be deleted
09:59 AM seb_kuzminsky: jepler: it looks easy to fix the packaging problem in cmorley's branch
10:00 AM mozmck: hi seb. I'm really trying to work towards a freeze and then release soon. I will probably need some pointers on how to go about some of that!
10:00 AM seb_kuzminsky: awesome!!! woooooo!!!!!!
10:00 AM seb_kuzminsky: i'm always happy to help with that part
10:01 AM mozmck: Great - thanks! My question on branches comes partly from looking through 252 branches on github :-)
10:01 AM seb_kuzminsky: the part i was sucking at was deciding when new features were good enough to merge, so i'm glad you folks have been making those decisions and moving forward
10:02 AM seb_kuzminsky: i don't mind managing the release branches and tagging and packaging and buildbotting and stuff
10:03 AM mozmck: Yeah, I don't reckon I'm any good at it, but I'm relying on others input mostly.
10:03 AM seb_kuzminsky: do you have a feel for how the stability of master is at this point? i've only been paying a little bit of attention
10:03 AM mozmck: branching and tagging is easy, but the buildbot stuff is different.
10:03 AM seb_kuzminsky: nearly all my machines run 2.7, and the few 2.8~pre machines haven't been updated for months
10:05 AM mozmck: From what I can tell from not using it myself - It seems really stable. Numbers of people are running with external_offsets for plasma and have for a while.
10:06 AM mozmck: Reverse run is one other feature I'm looking at - but it looks like Rob is having to do some stuff in the TP to handle it better, so I don't know if it should go in yet or wait until after the release.
10:07 AM sync: I would put it in
10:07 AM seb_kuzminsky: there are a *lot* of new features in 2.8 already, and it's been... over 3 years since 2.7.0, so my recommendation would be to push out a release without waiting for more things
10:08 AM seb_kuzminsky: if there's stuff that's ready to go, that you approve of and think is mostly stable, and that has a developer willing to help stabilize it the rest of the way, then sure merge it, but i'd say don't hold the release for things that are not yet ready
10:08 AM seb_kuzminsky: that's what the next release is for ;-)
10:09 AM mozmck: True. I don't plan to wait long on that one.
10:10 AM seb_kuzminsky: looks like rene merged and then reverted reverse-run last night?
10:10 AM mozmck: sync: do you know more about reverse run? I see that Rob made a commit yesterday "Added groundwork for reverse run in TP execution"
10:11 AM mozmck: seb_kuzminsky: yes - there were some conflicts. I think Rob made that commit after rene reverted but not sure.
10:12 AM sync: I know that they talked about it
10:13 AM skunkworks: I think rene might be working on it..
10:13 AM skunkworks: I was supposed to find him a config but I think it is at work
10:14 AM mozmck: hi skunkworks!
10:18 AM skunkworks: Hi!
10:23 AM mozmck: oh... I think that commit I saw from Rob was an artifact of Rene merging reverse-run
10:24 AM mozmck: So maybe it is just a more minor conflict now
12:11 PM -!- #linuxcnc-devel mode set to +v by ChanServ
03:19 PM mozmck: Hmm, was reverse-run in dgarr's external-offsets branch??? I'm playing with merging reverse-run and it acts like it is already there!
03:26 PM rene_dev_: mozmck thats just git
03:27 PM rene_dev_: because I reverted it
03:27 PM rene_dev_: It looked ok, but then problems came up
03:27 PM mozmck: Hi rene_dev_ how is that? I made a test branch off of master, then tried to merge reverse-run-master2 into it and it said it was already up to date.
03:28 PM rene_dev_: that is how git works. I merged it, so its in. git doesnt know about the revert
03:29 PM rene_dev_: but I think I know how to fix it now.
03:29 PM rene_dev_: https://github.com/LinuxCNC/linuxcnc/commit/5a63d03110ec0f9ed92799b3f6507042894ba833
03:29 PM mozmck: I see - that's kind of strange though. Does git just go by the commit numbers?
03:30 PM rene_dev_: thats just how it works. lets say you merge some stuff, and ten undo it by hand. git doesnt know about the undo
03:31 PM rene_dev_: you can just checkout the repo after my merge
03:32 PM mozmck: Interesting. How do you get the changes back then if you want to merge them in later?
03:34 PM mozmck: will do
03:34 PM rene_dev_: revert the revert :D
03:34 PM rene_dev_: I didnt want to force push
03:34 PM mozmck: yeah
03:35 PM rene_dev_: that can cause bad things
03:40 PM rene_dev_: but reverse run seems to be stable, many pepole seem to be using it
03:41 PM mozmck: hi andypugh
03:41 PM rene_dev_: the pepole in the forum seemd to be very happs about that
03:42 PM andypugh: I haven’t looked today
03:42 PM andypugh: Hi mozmck
03:42 PM rene_dev_: https://forum.linuxcnc.org/plasma-laser/35449-another-plasma-component?start=50
03:43 PM andypugh: Oh, I hadn’t seen those go in.
03:44 PM rene_dev_: they are not, I messed up badly :D
03:44 PM andypugh: But, still, I normally expect an email
03:44 PM andypugh: But EO went in
03:45 PM rene_dev_: yes
03:45 PM mozmck: andypugh: I was looking through branches, and I noticed that your multispindle branch has commits not in master?
03:45 PM andypugh: Has it?
03:45 PM mozmck: I merged EO this morning - hope it goes well!
03:45 PM andypugh: I rebased and combined a few things before merge
03:46 PM mozmck: andypugh: on github it says the branch is 25 commits ahead of master...
03:46 PM mozmck: I was looking around seeing if there were already merged branches we could delete!
03:46 PM rene_dev_: joint axis can be deleted
03:47 PM andypugh: mozmck: Curious.
03:47 PM mozmck: rene_dev_: ah, that's true.
03:53 PM andypugh: I am not sure what is going on there, but those 25 commits are all of multispindle.
03:54 PM andypugh: It all went in, but possibly all the commit hashes changed when I re-factored into fewer commits.
03:54 PM mozmck: oh, maybe so.
03:55 PM rene_dev_: yes, thats possible
03:55 PM mozmck: Well, I won't delete the branch, but if you think it is ok maybe you can. I'll probably delete JA
03:56 PM andypugh: I just deleted the branch
03:56 PM andypugh: https://github.com/LinuxCNC/linuxcnc/branches
03:57 PM andypugh: We could possibly delete some of the 15 year old stale branches too :-)
03:57 PM mozmck: That's what I was thinking :-)
03:57 PM andypugh: Though those are so old perhaps they have historical value
03:58 PM mozmck: yeah
03:58 PM andypugh: I have only recently remebered the G71/G72 branches
03:59 PM andypugh: I can’t even recall where we were.
03:59 PM Tom_L: are those intended as lathe cycles?
03:59 PM andypugh: Oddly we have docs for a feature that doesn’t exist, which is a novelty
03:59 PM andypugh: Yes
04:00 PM Tom_L: as is g76?
04:01 PM rene_dev_: https://www.youtube.com/watch?v=XJ8MNLQjcjE
04:01 PM rene_dev_: https://www.youtube.com/watch?v=yFVgUKC8HJE
04:02 PM rene_dev_: like that?
04:04 PM andypugh: https://github.com/LinuxCNC/linuxcnc/blob/andypugh/g71type2remap/docs/src/gcode/g-code.txt#g71-lathe-roughing-cycle-turning
04:05 PM mozmck: who was it saying they had a g71 but wouldn't release it?
04:05 PM rene_dev_: 2 years old, wow
04:05 PM rene_dev_: well, they have to, dont they?
04:06 PM mozmck: no - especially if they don't distribute it.
04:06 PM andypugh: It doesn’t matter who said that, we already have one
04:06 PM andypugh: https://github.com/LinuxCNC/linuxcnc/tree/BenPotter/G71
04:07 PM mozmck: Seemed like his had some really nice benefits - but I can't remember the details. Maybe it wasn't much.
04:07 PM andypugh: But that one doesn’t do pockets or, as far as I recall, radius comp
04:07 PM andypugh: But, I did a remap as an algorithm check in Python.
04:08 PM rene_dev_: mozmck well, they do distribute it. anyway, I can look what they use.
04:08 PM andypugh: The plan was to merge the Python code in to the C++ version and then use the generic radius comp code.
04:09 PM mozmck: I don't think it was someone with tormach - unless maybe tormach paid him for his code?
04:09 PM andypugh: But, well, we didn’t. I think Ben Potter got bored, or didn’t see the point once there was a remap to do it.
04:10 PM rene_dev_: andypugh one of the tormach guys also has a near-a-car, but cant remember who
04:11 PM andypugh: Zultron / John Morris.
04:11 PM andypugh: Because his great-grandfather was Carl Neracher, the designer of the Ner-a-Car
04:13 PM rene_dev_: ah, yes. he was the one.
04:13 PM rene_dev_: would g71 not be a good project after multi spindle? :D
04:15 PM andypugh: Yes
04:15 PM andypugh: It’s on the list
04:15 PM andypugh: But I would like to see 2.8 out first.
04:20 PM rene_dev_: yes
04:21 PM rene_dev_: I think we should come up with a roadmap for 2.8, and decide on a date for feature freeze...
04:22 PM andypugh: I suggested a few weeks ago that we should freeze now (including reverese run) and aim to release by new-year
04:22 PM andypugh: But I don’t know how keen CMorley is to get qtvcp in
04:23 PM mozmck: andypugh: you mean including reverse-run in 2.8 or freezing it out?
04:24 PM andypugh: Talking about roadmaps, can anyone make any sense of the last post here? I really don’t even understand the question: https://www.model-engineer.co.uk/forums/postings.asp?th=136751&p=2
04:24 PM andypugh: mozmck: Including it
04:25 PM mozmck: I'm for including it if the problems rene found can be resolved soon and aren't major. I thought it was up to date with master already.
04:29 PM mozmck: I *think* he is saying that tormach had to spend money to make a usable system that their users don't have to read lots of docs to use, because linuxcnc lacks "good functional mileposts"
04:29 PM mozmck: tell him that linuxcnc is not a highway and therefore doesn't need mileposts.
04:30 PM andypugh: I really don’t understand what a “functional milepost that users can choose” is
04:30 PM mozmck: If he means a good "roadmap", I'm not sure how that would help any users.
04:31 PM mozmck: yeah, I don't know.
04:32 PM sync: I think he means milestones aka revisions that "work" and are documented
04:32 PM sync: but idk
04:33 PM mozmck: That would be strange because each revision has worked and had documentation.
04:34 PM sync: maybe they were not to his liking
04:34 PM cradek: andypugh: I don't think that question is asked in good faith
04:36 PM andypugh: No, that’s mainly why I didn’t reply.
04:37 PM andypugh: I suspect he is not a LinuxCNC user.
04:48 PM rene_dev_: he is probably better off with mach3
04:58 PM andypugh: We are better off with him using Mach3
05:05 PM CMorley: andypough: I'm ok with qtvcp not being included in 2.8 -provided my don't wait another three years for 2.9
05:05 PM CMorley: thanks for asking though
05:05 PM CMorley: I am interested in opinions of pncconf - i'm considering removing it.
05:06 PM andypugh: Hmmm
05:06 PM rmu: what is missing from qtvcp
05:06 PM andypugh: I can see why, but it does seem to be in-demand
05:07 PM CMorley: rmu: time to find bugs and a good fully functional production ready screen
05:08 PM CMorley: andypugh: yes when it works it is _very_ helpful to users but it is _very_ difficult to make sure it works.
05:10 PM andypugh: A version that queried the actual hardware and got the pin names that way might be less of a maintainance headache, but a ton of work to write.
05:11 PM CMorley: yes. but it is still a lot of work to maintain for new hardware.
05:11 PM rene_dev_: I think the approach of pncconf and stepconf is not the best
05:11 PM andypugh: for new interfaces, yes, but as far as looking to see what it finds?
05:12 PM rene_dev_: of generating hal files, that can then not be edited
05:12 PM CMorley: anyways i'm tired of if and i guess it's too difficult for others to help - as i see John was making his own to the 7i96...
05:12 PM andypugh: Yes, I rather wish that he had tried to help with pncconf rather than write a one-off tool
05:12 PM CMorley: Yes pncconf can query the boards right now..it's a slightly hidden option
05:12 PM jthornton: CMorley: I made that just as a simple way for users to get up and running with the 7i96
05:13 PM CMorley: Oh I understand john
05:13 PM rene_dev_: would be better to have generic hal files for the most common setups, that are then overwritten by user changes, or ini settings
05:13 PM andypugh: rene_dev_: We have _some_ of that
05:13 PM rene_dev_: like the stmbl hal files, or the way some of the xhc stuff works
05:13 PM jthornton: one thing I did was make the wizard read the ini file
05:13 PM rene_dev_: after all, that is the idea of the hal pulling data from the ini
05:14 PM andypugh: The XHC #include files messed up the update_ini script.
05:14 PM andypugh: Well, to be fair, I failed to test update_ini with #include files
05:15 PM rene_dev_: I did a retrofit of another weiler a few days ago, with a 7i77. and there are no example configs. took me an hour to even get the basic stuff working
05:16 PM CMorley: did you use pncconf?
05:16 PM rene_dev_: no, I could not figure out how to use it
05:16 PM CMorley: interesting
05:16 PM jthornton: that's what I use an example from pncconf for 7i77
05:17 PM rene_dev_: 7i92+7i77, analog servo
05:17 PM jthornton: I think the one I have is a 5i25 7i77
05:18 PM rene_dev_: well, I know how stuff works, and can come up with a hal file quickly, but I can imagine that its very difficult for pepole when they get started
05:18 PM rene_dev_: should not make a difference...
05:18 PM CMorley: it doesn't in pncconf- either are possible
05:21 PM rene_dev_: I guess Im just not very good with GUIs
05:21 PM CMorley: lol
05:22 PM CMorley: to be fair - pncconf could be made to be simpler but then you lose options - it's a balance.
05:23 PM CMorley: also it was orignally made when hardware was much simpler and i was a much worse programmer
05:23 PM rmu: i did try to make pncconf work with 7i90 connected via spi on the raspberry ;-)
05:23 PM rmu: had some success
05:23 PM CMorley: really - i don't think the 7i90 is actually supported
05:24 PM rmu: no, not really...
05:25 PM CMorley: One of the real problems with it is, in general the devs don;t use it, so it never gets tested much when it's released - hence always buggy
05:25 PM rene_dev_: :D
05:26 PM CMorley: rmu: did you use the discovery option/
05:26 PM rmu: i tried
05:26 PM rmu: IMO it is the only sensible way to do things, connect to whatever mesa device you have, and try to make sense of the HAL pins that appear
05:26 PM jthornton: what does the discovery option do?
05:27 PM CMorley: yes it's true
05:27 PM CMorley: it queries the actual hardware
05:27 PM jthornton: does it do that with a readhmid?
05:28 PM CMorley: It uses mesaflash to read everything
05:28 PM rmu: i hit some roadblocks, it could query the 7i90 (with hacked-in SPI stuff), but then i got stuck somehow and gave up... there were some other problems like non-working MESA firmware at that time
05:28 PM jthornton: that's what I meant, I don't have it on this pc
05:28 PM CMorley: so it require mesaflash, which we don't include IIRC
05:28 PM jthornton: I added that to the 7i96 wizard in two flavors 32bit and 64bit
05:28 PM jthornton: I use it to get some info
05:29 PM jthornton: not sure if anyone has actually used it yet lol
05:29 PM CMorley: Well John please add all the other cards, so I can get rid of pncconf... :)
05:29 PM jthornton: I was thinking about doing one for each family of cards...
05:31 PM rmu: i think a bigger roadblock for mesa users is trying to figure out which firmware to use... names like SVSS6_8 or SSSVST8_8_8 are not very intuitive and I at least didn't find a real reference besides the VHDL sources
05:31 PM CMorley: rmu: yes the discovery option helps the user for sure, but the problem then becomes it will find hardware that pncconf doesn't support
05:32 PM jthornton: actually I have some started for the 7i76E and the parallel port
05:32 PM jthornton: Chris how do you translate the mesaflash info into pins?
05:32 PM CMorley: You don't think speconf works well for the parport?
05:32 PM CMorley: very dificulty
05:33 PM rmu: why don't you just start up HAL and look at the pins of the hm2 driver?
05:33 PM jthornton: well mine read the ini file so a bit better I think
05:33 PM rmu: that should be easier than parsing whatever mesaflash returns
05:33 PM CMorley: you can look in the source. it's worse because I needed to convert it what pncconf expected from the XML file
05:34 PM CMorley: read what from the INI file?
05:34 PM jthornton: all the configuration information, I add some at the bottom for the wizard
05:35 PM jthornton: I can open an ini and it sets everything in the wizard and if something has changed in the ini it gets that right
05:35 PM CMorley: I am missing something - we were talking mesa hardware info used to make an configuration - so there would be no INI file
05:36 PM jthornton: sorry jumping around a bit
05:37 PM CMorley: anyways for pncconf - if I had three other people helping it all might have happened but i'm interested in other things now :)
05:37 PM CMorley: i guess my qiestion is pull it out now before 2.8 or after.
05:38 PM jthornton: if your going to pull it before a release would be better, you could put it in a branch for those that use it
05:38 PM CMorley: rmu - reading using mesaflash get you more info then reading just the HAL pins
05:39 PM CMorley: pulling it out after allow someone to make a replacement in the mean time
05:39 PM jthornton: ah yes
05:43 PM jthornton: I wonder if I should add my 7i96 configuration tool to master?
05:44 PM CMorley: Can't really hurt... it's option to use
05:44 PM jthornton: I'll have to try and figure out where to put it in the directory structure
05:46 PM CMorley: src/emc/usr/intf would be the place I think
05:47 PM jthornton: ok I'll make a branch in the morning and see if I can get it all sorted out
05:47 PM jthornton: good talking with you again Chris
05:47 PM rene_dev_: rmu hal pind dont tell you the hardware pins
05:47 PM CMorley: you bet John!
05:48 PM jthornton: time to start some chow
05:49 PM CMorley: mozmck: migth be nice to add mesaflash to linuxcnc
05:49 PM jthornton: yes for sure that would be nice
05:50 PM andypugh: I find the bitfile names fairly intuitive:-)
05:50 PM CMorley: ttyl guys
05:50 PM jthornton: see you later
05:50 PM andypugh: SSSVST8_8_8 means “SmartSerial / Servo / Stepper and 8 of each.
05:51 PM jthornton: you will have to elaborate a bit on how you got that lol
05:52 PM Tom_L: especially for a noob :)
05:53 PM andypugh: SS = Smart Serial. SV = Servo, ST = Stepper. then the numbers are the numbers of each
05:53 PM andypugh: TP = three-phase PWM (7i39 etc) and RV = Resolver (7i49)
05:53 PM andypugh: UA + UART
05:54 PM * jthornton takes notes
05:54 PM Tom_L: some are obvious but others not so much
05:56 PM rmu: andypugh: but "servo" doesn't say much at all, there are different pinouts
05:58 PM andypugh: Typically SV == 7i33 pinout. The more recent cards tend to have the actual card name. (7i65 for example)
05:58 PM Tom_L: not too bad for a descriptive filename though
05:58 PM rmu: and "SSSV6_36" hat 18 stepgens and nothing else IIRC
05:59 PM andypugh: https://github.com/LinuxCNC/hostmot2-firmware/blob/master/src/PIN_SSSV6_36_96.vhd
06:00 PM andypugh: That’s 18 muxed encoders (so 36 encoders total) and 6 smart-serial channels.
06:00 PM rmu: yeah, but flashing the file with SSSV6_36 with SPI for 7i90 has only 18 stepgens ;)
06:01 PM andypugh: Something wrong there, it shouldn’t have any stepgens.
06:02 PM rmu: perhaps i messed up my table, i made the effort some time ago to dump the HMID of all 7i90 firmwares
06:02 PM andypugh: (should point out that this is just what I have picked up over the years, I have no actual connection to Mesa)
06:02 PM Tom_L: and here i thought you were one of their main debuggers :)
06:03 PM andypugh: Not at all, I am one onf the main bug-writers
08:16 PM mozmck: I think we have mesaflash on the iso - but it might be nice to include with linuxcnc somehow. Or even just have it packaged in the repo and information on it.
09:05 PM jepler: yes, mesaflash should be available for any architecture that linuxcnc packages are
09:05 PM jepler: from linuxcnc.org.
09:13 PM pcw_home: rmu: there are possibly some missnamed 7I90 files around (I think my build script didn't notice if one failed to build (too big) so you ended up with last bitfile that built)
09:19 PM pcw_home: (and 36 stepgens will not fit in a 7I90)
09:59 PM hazzy1 is now known as hazzy
10:00 PM CMorley: andypugh:Looking a linuxcnc status program in master - looks like spindle info is not displaying right. Hope you are good with tcl :)