Back
[03:36:34] <archivist> when is the (log... supposed to be interpreted?
[03:44:44] <archivist> because during the syntax check stage is silly
[07:08:01] <KGB-linuxcnc> 03John Thornton 052.7 de0062d 06linuxcnc 10docs/src/gcode/overview.txt Docs: add info about examples of logging * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=de0062d
[07:14:02] <KGB-linuxcnc> 03John Thornton 052.7 28f10ab 06linuxcnc 10docs/src/gui/axis.txt Docs: add info on how to stop the do you really want to quit dialog * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=28f10ab
[08:54:07] <KGB-linuxcnc> 03John Thornton 052.7 04f8509 06linuxcnc 10docs/src/gcode/coordinates.txt 10docs/src/gcode/g-code.txt Docs: fix a couple of places that still had six axes or planes * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=04f8509
[08:54:38] <jepler> weird, I couldn't reproduce this
https://forum.linuxcnc.org/forum/38-general-linuxcnc-questions/30110-g53-after-g10-l2-p1-r45/67342
[08:55:04] <jepler> after rotating, g0g53x0y0 goes to machine 0,0 as I expect
[08:55:21] <jepler> tested in 2.7 branch, uspace, amd64, sim/axis
[10:34:15] <KGB-linuxcnc> 03Sebastian Kuzminsky 052.6 9ee785a 06linuxcnc 10src/rtapi/sim_common.h better error reporting in rtapi/sim * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=9ee785a
[11:07:59] <cncbasher> jepler: where in the hostmo2 firmware is the fallback , i'm consistanly getting the fallback red led , pcw suggested to see if i had the fallback bit set
[11:08:54] <cncbasher> every 5i25 i do seems to fail, iam wondering if something is wrong
[11:27:09] <pcw_home> fallback is a generic set in the top level file:
[11:27:10] <pcw_home> FallBack: boolean := false -- is this a fallback config?
[11:28:36] <cncbasher> thanks
[11:29:20] <cncbasher> i'm just wondering if i have a fundamental error in my build set , or a genuine error
[11:29:30] <pcw_home> its not harmful (all it does is blink the light)
[11:29:59] <cncbasher> i know i need to read the code more ! haha
[11:30:33] <pcw_home> _but_ you can also get a fallback (the the 5I25s fallback config) if your bitfile is corrupted so it fails to load properly
[11:31:37] <pcw_home> thats why is suggested mesaflash --readhmid so you can check if your bitfile pinout is the expected one
[11:32:05] <cncbasher> arh fallback boollean = true
[11:32:59] <cncbasher> so i should make that false , then i might get a better idea if i do have a error or not
[11:33:05] <pcw_home> the one in the latest dist seems to be false (I copy pasted from it)
[11:33:46] <cncbasher> from hostmot2-firmware ? jeplers build
[11:35:46] <cncbasher> thanks the learning curve for vhdl just clearing the clouds LOL
[11:35:57] <pcw_home> If I had been smarter I would have included the flag in the pinout file (But unfortunately it was added quite late)
[13:05:49] <linuxcnc-build> build #3792 of 1202.rip-lucid-amd64 is complete: Failure [4failed compile runtests] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1202.rip-lucid-amd64/builds/3792 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[13:12:08] <seb_kuzminsky> i think that failure is the 2.6-sim version of the problem we fixed in 2.7-uspace recently
[13:13:15] <seb_kuzminsky> in 96026f6fcf8856f6ebdc87c21a2a77e903b1da1b
[13:18:18] <KGB-linuxcnc> 03Sebastian Kuzminsky 052.6 77918d2 06linuxcnc 10scripts/realtime.in realtime script: wait for the last rtapi_app to die when stopping realtime * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=77918d2
[13:18:30] <seb_kuzminsky> cherry pick for the win
[13:35:02] <linuxcnc-build> build #3805 of 0000.checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/3805 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[13:44:13] <jepler> cncbasher: I doubt I'll have time this weekend to run the fpga building test you e-mailed me about. sorry. ping me after tuesday if you haven't been able to make any headway yet.
[14:07:49] <cncbasher> thats ok it's no problem
[14:07:57] <JT-Shop> seb_kuzminsky: should I change the documents to match the behavior for logging?
[17:16:26] <micges> cncbasher: I also have fallback red led from bitfile from latest hostmot2-firmware, but the firware works
[17:30:49] <PCW> that just means wherever you got TopPCIHostMot2.vhd from had the generic boolean "fallback" set true
[17:30:50] <PCW> It does nothing but blink the red Init LED
[17:32:22] <PCW> So its not harmful
[17:32:22] <PCW> its not true in (at least the current) hostmot2.zip files
[17:35:51] * PCW continues pressing connectors into PC-104 cards
[17:43:13] * JT-Shop continues rewiring the BP
[17:45:18] <seb_kuzminsky> JT-Shop: i haven't gotten to the bottom of it yet, so i'm not sure what it should say
[17:47:42] <JT-Shop> ok I'll stand by and keep on working on my BP
[20:11:51] <jepler> jepler@babs:~/src/hostmot2-firmware$ git grep -i fallback.*true *.vhd
[20:11:52] <jepler> TopPCIHostMot2.vhd: FallBack: boolean := true -- is this a fallback config?
[20:12:00] <jepler> yes I see this file is committed in hostmot2-firmware with fallback set true
[20:13:46] <KGB-linuxcnc> 03Jeff Epler 05master 0e40f19 06hostmot2-firmware 10TopPCIHostMot2.vhd pci: don't mark configs as fallback * 14http://git.linuxcnc.org/?p=hostmot2-firmware.git;a=commitdiff;h=0e40f19
[21:00:46] <KGB-linuxcnc> 03chris morley 05panelui f7ccee1 06linuxcnc 10src/hal/components/panelui.c panelui -use a simpler function call to python * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=f7ccee1
[21:00:46] <KGB-linuxcnc> 03chris morley 05panelui 692a743 06linuxcnc 10src/emc/usr_intf/pyui/widgets.py panelui: add not pins to status pins * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=692a743
[21:00:46] <KGB-linuxcnc> 03chris morley 05panelui 743b463 06linuxcnc 10src/emc/usr_intf/pyui/commands.py panelui: dont adjust spindle rpm if its already running. * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=743b463
[21:13:10] <linuxcnc-build> build #3003 of 1301.rip-precise-rtai-i386 is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1301.rip-precise-rtai-i386/builds/3003 blamelist: chris morley <chrisinnanaimo@hotmail.com>
[21:15:22] <linuxcnc-build> build #3793 of 1300.rip-precise-i386 is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1300.rip-precise-i386/builds/3793 blamelist: chris morley <chrisinnanaimo@hotmail.com>
[21:15:37] <linuxcnc-build> build #3795 of 1306.rip-precise-amd64 is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1306.rip-precise-amd64/builds/3795 blamelist: chris morley <chrisinnanaimo@hotmail.com>
[21:40:16] <linuxcnc-build> build #3807 of 0000.checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/3807 blamelist: chris morley <chrisinnanaimo@hotmail.com>