#linuxcnc-devel Logs

Feb 24 2017

12:32 AM seb_kuzminsky: the jessie-armhf machine croaked again, despite the better cooling and despite being under just about no load
12:33 AM seb_kuzminsky: maybe the SD card is bad? maybe one day i'll try another :-/
07:25 AM stustev: I cloned master into linuxcnc-dev and linuxcnc-devv. It compiles in both directories.
07:25 AM stustev: linuxcnc starts and runs
07:25 AM stustev: linuxcnc-dev starts and runs - ignore the previous line
07:26 AM stustev: linuxcnc-devv doesn't run - it presents the config choices but immediately dies when I chose a config file and click OK
07:28 AM stustev: It doesn't find the Linuxcnc package. The message is from line 83 of the check_config.tcl file.
07:28 AM stustev: Am I right in assuming the RIP is default and both directories should run?
07:28 AM stustev: thanks
08:52 AM KGB-linuxcnc: 03Dewey Garrett 05dgarr/per_seq_homing 4b2cf36 06linuxcnc 10src/emc/usr_intf/axis/scripts/axis.py axis.py: non-ident kins:home menu items: show SYNC * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=4b2cf36
08:52 AM KGB-linuxcnc: 03Norbert Schechner 05dgarr/per_seq_homing 45efe29 06linuxcnc 10src/emc/usr_intf/gmoccapy/gmoccapy.py 10src/emc/usr_intf/gmoccapy/release_notes.txt gmoccapy_2_2_3_2 - bug. double hal pin creation * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=45efe29
08:52 AM KGB-linuxcnc: 03Norbert Schechner 05dgarr/per_seq_homing 7f3b967 06linuxcnc 10configs/sim/axis/gantry_mm.ini 10configs/sim/gmoccapy/gmoccapy-JA/Gantry/gantry_mm.ini 10configs/sim/gmoccapy/gmoccapy-JA/Gantry/gmoccapy_GANTRY_sim.pref configs - corrected the home sequence values to be negative * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=7f3b967
08:53 AM KGB-linuxcnc: 03Norbert Schechner 05dgarr/per_seq_homing 70fff63 06linuxcnc 10configs/sim/gmoccapy/gmoccapy-JA/Gantry/gantry_mm.ini 10src/emc/usr_intf/gmoccapy/gmoccapy.py 10src/emc/usr_intf/gmoccapy/release_notes.txt gmoccapy_2_2_3_3 - check for double letters in coordinates and home the correct joint * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=70fff63
11:06 AM KGB-linuxcnc: 03Dewey Garrett 05master 87d2a4e 06linuxcnc 10(7 files in 4 dirs) motion: update for hal pos-cmd, vel-cmd pins * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=87d2a4e
11:41 AM seb_kuzminsky: stustev: i have several git working trees in use, i haven't seen a problem like that
11:42 AM seb_kuzminsky: each working tree (or clone) has its own scripts/rip-environment that points at that clone, so once you source one rip-environment in a shell, then that shell is stuck pointing at that clone until you exit
11:59 AM dgarr: stustev: You can get that type of error if you source the rip-environment more than once in a shell for different local repositories. This is because the rip-environment script _appends_ to existing environmental variables like TCLLIBPATH.
11:59 AM dgarr: Like many path specifications, the first item found in the colon separated TCLLIBPSATH list wins--if it is not appropriate for the rip specified by the current linuxcnc command there can be problems. (i know from experience)
12:00 PM dgarr: env|grep TCLLIBPATH should usually show only a single item
12:01 PM dgarr: It is also a good idea to run the which command to make sure you are using the linuxcnc you intend: $ which linuxcnc
12:09 PM seb_kuzminsky: hi dgarr, thanks for the motion pin updates
12:10 PM seb_kuzminsky: since renaming a pin can break existing configs, it should be noted in the Updating LinuxCNC document
12:10 PM seb_kuzminsky: and in the motion manpage
01:33 PM KGB-linuxcnc: 03Dewey Garrett 05master 351d14e 06linuxcnc 10docs/src/getting-started/updating-linuxcnc.txt updating-linuxcnc.txt pin name change * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=351d14e
01:52 PM seb_kuzminsky: thanks
03:37 PM andypugh: Hadn’t seen this before: http://www.yurtaev.com
03:39 PM cradek: interesting
03:43 PM andypugh: Somebody as asking about SCCNET protocol on the forum, and RodW found that. It probably belongs on the “supported hardware” page.
03:43 PM andypugh: I wonder if his HAL driver is open-source or not?
03:44 PM cradek: there are links to deb packages with probably-corresponding source but I didn't look in them
03:45 PM andypugh: Nor I
04:35 PM seb_kuzminsky: yurtaev.com should do what the general mechatronics folks did, and send us a PR with their driver
04:58 PM jepler: their website has a linuxcnc source tree
04:59 PM jepler: compared to 2.7.8 it has changes including a new .comp file which says 'license "GPL";'
05:00 PM jepler: the .comp includes several added .h files as well
05:00 PM jepler: aside from the mandatory license declaration in the .comp files, the files don't contain any specific license grant. in particular, the .h files just say they are copyright
05:01 PM jepler: http://www.yurtaev.com/files/linuxcnc_2.7.8ssc8/
05:02 PM jepler: just a listing of added and modified files: http://paste.debian.net/916649/
05:02 PM jepler: for some reason it seems to include a form of the reverse-run patch (?)
05:04 PM jepler: it includes signal aliases which .. what does that even mean
11:44 PM -!- #linuxcnc-devel mode set to +v by ChanServ