[Emc-developers] Buildot Is Down

[Phillip Carter]

I think the Buildbot is having a nap.

Cheers, Phill.


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Intel graphics and RTAI

[Phillip Carter]

Could this be an issue?

# CONFIG_FB_INTEL is not set


> On 21 Dec 2019, at 12:06 pm, bari  wrote:
> 
> Here is his paste:
> 
> https://pastebin.com/ZC2LhMe5
> 
> 
> 
> On 12/20/19 7:00 PM, Alec Ari via Emc-developers wrote:
>> Phill I'm not seeing your files.. Post to dpaste or something? And sure, I'm 
>> not going to be busy for awhile so might as well make my time mean something.
>> 
>> Alec
>> 
>> ___
>> Emc-developers mailing list
>> Emc-developers@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/emc-developers
> 
> 
> 
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Intel graphics and RTAI

[Phillip Carter]

No it doesn't.

>From memory that also showed up as an error in the X11 log file when I had 
>FBDEV as a device in the X11 conf file.

> On 21 Dec 2019, at 12:10 pm, Alec Ari via Emc-developers 
>  wrote:
> 
> My mistake,
> So the config option for FBCON is CONFIG_FRAMEBUFFER_CONSOLE which is already 
> enabled.
> Does /dev/fb0 exist?
> Alec
> 
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Intel graphics and RTAI

[Phillip Carter]

Alec,

Thanks for persevering with this.

The result is:
phill@stretch:~$ grep "FBCON" /boot/config-*rtai*
phill@stretch:~$ grep "fbcon" /boot/config-*rtai*
phill@stretch:~$

I then did:
phill@stretch:~$ grep "" /boot/config-*rtai* > grep.txt
and the result is too large to attach so I will split it in two...

Cheers, Phill.


> On 20 Dec 2019, at 2:41 pm, Alec Ari via Emc-developers 
>  wrote:
> 
> Phill,
> Can you post the output of:
> grep "FBCON" /boot/config-*rtai*
> Thank you!
> Alec
> 
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net 
> 
> https://lists.sourceforge.net/lists/listinfo/emc-developers 
> 

___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Intel graphics and RTAI

[Phillip Carter]

Part 2:



> On 20 Dec 2019, at 3:49 pm, Phillip Carter  wrote:
> 
> Alec,
> 
> Thanks for persevering with this.
> 
> The result is:
> phill@stretch:~$ grep "FBCON" /boot/config-*rtai*
> phill@stretch:~$ grep "fbcon" /boot/config-*rtai*
> phill@stretch:~$
> 
> I then did:
> phill@stretch:~$ grep "" /boot/config-*rtai* > grep.txt
> and the result is too large to attach so I will split it in two...
> 
> Cheers, Phill.
> 
> 
> 
>> On 20 Dec 2019, at 2:41 pm, Alec Ari via Emc-developers 
>> > <mailto:emc-developers@lists.sourceforge.net>> wrote:
>> 
>> Phill,
>> Can you post the output of:
>> grep "FBCON" /boot/config-*rtai*
>> Thank you!
>> Alec
>> 
>> ___
>> Emc-developers mailing list
>> Emc-developers@lists.sourceforge.net 
>> <mailto:Emc-developers@lists.sourceforge.net>
>> https://lists.sourceforge.net/lists/listinfo/emc-developers 
>> <https://lists.sourceforge.net/lists/listinfo/emc-developers>


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Intel graphics and RTAI

[Phillip Carter]

I think I would be happy to use FBDEV, but I haven't been able to get it to 
work. I tried several times with differnet Xorg configs to no avail, it would 
consistently revert to the VESA driver and limit the resolution to 1024 x 768.
I cannot recall the different things I tried as it was quite a while ago and I 
went on to other things.
Both my machines have i915 video.

> On 15 Dec 2019, at 7:38 am, Alec Ari via Emc-developers 
>  wrote:
> 
> Hi everyone,
> Are people more willing to risk possibly higher latency with RTAI to use 
> Intel integrated graphics to save them the trouble of using FBDEV or VESA 
> drivers? If so, I can re-enable these Kconfig options. If you haven't had 
> latency trouble before with Intel graphics, I can't imagine a newer kernel 
> making this worse.
> Are there a lot of people on nVIDIA hardware too or just Intel?
> 
> Alec
> 
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

[Emc-developers] Buildbot

[Phillip Carter]

It looks like the Buildbot is down, I cannot access the waterfall.

Cheers, Phill





___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Archived emails

[Phillip Carter]

https://sourceforge.net/p/emc/mailman/emc-developers/Cheers, Phill
 Original message From: Marius  Date: 
17/11/19  7:53 pm  (GMT+10:00) To: Emc-developers@lists.sourceforge.net 
Subject: [Emc-developers] Archived emails Is there a place where I can see the 
archived emails for this group. I need to lookup some older 
stuff.RegardsMarius___Emc-developers
 mailing 
listEmc-developers@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/emc-developers
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

[Emc-developers] Buildbot Asleep

[Phillip Carter]

The buildbot appears to be asleep.

Cheers, Phill.


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

[Emc-developers] Buildbot Stalled

[Phillip Carter]

It seems the Buildbot has stalled.

Cheers, Phill.


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] stretch boot problem.

[Phillip Carter]

> On 10 Oct 2019, at 3:02 am, Gene Heskett  wrote:
> 
> On Wednesday 09 October 2019 06:31:09 Nicklas Karlsson wrote:
> 
>> Have sometimes also experienced boot problems and today reinstalled a
>> computer with Ubunte with boot problem stuck half way thru with
>> Debian. Software in both distributions is very similar so it must be
>> some small problem. Waiting for start process I have seen but not this
>> time.
>> 
>> Den tis 8 okt. 2019 kl 23:54 skrev Gene Heskett :
>>> I wrote a u-sd card with a pretty late April 2019 stretch. reset the
>>> video to full KMS or whatever its called, rebooted and got nice
>>> clean glxgears at about 45 fps full screen. Thats not half bad I
>>> said to myself, but needs a realtime kernel.  So I mounted my ssd's
>>> and cd'd to media/pi/workpi120/buildbot/linux and rebuilt and
>>> installed 4.19.76-rt over the top of a 4.14 something.
>>> 
>>> Rebooted, but its now stuck about halfway thru the boot trace and
>>> deader than a door nail to any method of input. I was going to take
>>> a screen shot with my camera, but despite having had a hot usb cable
>>> plugged in for about 6 weeks, its telling me to charge the battery.
>>> So I plugged it in again and will give it half an hour. Hopefully
>>> someone can diagnose whats hanging it.  That was a hot reboot, not a
>>> power cycle.  And 4.19 is a newer kernel than the 4.14 it was
>>> running.
> 
> Now I am beginning to get pissed, no matter how I ask a 
> git clone --depth=1 --branch=4.14.y-rt /https://github.com/raspberrypi/linux 
> linux-rpi-4.14.y-rt
> I get the non-rt branch. Its around 150 megabytes.
> 

Should it be —branch=rpi-4.14.y-rt

> The 4.19.y-rt build won't boot, and I cannot get the 
> realtime 4.14.y-rt code base, so when I do a make bcm2709_defconfig,
> I get a castrated .config that only has this:
> 
> # Timers subsystem
> #
> CONFIG_TICK_ONESHOT=y
> CONFIG_NO_HZ_COMMON=y
> # CONFIG_HZ_PERIODIC is not set
> CONFIG_NO_HZ_IDLE=y
> # CONFIG_NO_HZ_FULL is not set
> CONFIG_NO_HZ=y
> CONFIG_HIGH_RES_TIMERS=y
> 
> #
> # CPU/Task time and stats accounting
> ==
> 
> Whats wrong with the above git clone command?
> 
> Thanks.
> 
> Cheers, Gene Heskett
> -- 
> "There are four boxes to be used in defense of liberty:
> soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author)
> If we desire respect for the law, we must first make the law respectable.
> - Louis D. Brandeis
> Genes Web page 
> 
> 
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

[Emc-developers] Gmoccapy

[Phillip Carter]

I noticed on the Buildbot there were compile errors caused by a link in 
gmoccapy-hu.txt to a missing image.

I took the liberty of removing the link so the compiles would complete.

https://github.com/LinuxCNC/linuxcnc/commit/a4828e46a23425c22043595b4df09d782bf92c6a
 


Cheers, Phill.
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

[Emc-developers] Buildbot Asleep

[Phillip Carter]

The Buildbot seems to have been asleep for a few days.


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Travis CI Errors

[Phillip Carter]

I restarted the build and it was successful so I guess it was a Travis CI 
thing...

> On 23 Jul 2019, at 5:44 pm, Phillip Carter  wrote:
> 
> In the meantime I signed up to Travis CI and it did a build on my repository 
> <https://github.com/phillc54/linuxcnc/commits/master> and it succeeded.
> 
> Buildbot seemed to be successful as well.
> 
> Cheers, Phill 
> 
>> On 23 Jul 2019, at 3:56 pm, Phillip Carter > <mailto:phillcarte...@gmail.com>> wrote:
>> 
>> I have just pushed some commits and I noticed an error on the commits 
>> <https://github.com/LinuxCNC/linuxcnc/commits/master> page of GitHub.
>> 
>> The error is:
>> 
>> The command "./scripts/travis-install-build-deps.sh" failed and exited with 
>> 100 during .
>> 
>> Your build has been stopped.
>> 
>> Which I don’t understand.
>> 
>> I am able to build locally for both 2.8 and master with full documentation.
>> 
>> I also notice the same error on two commits on July 16.
>> 
>> Any help appreciated.
>> 
>> Cheers, Phill.
>> 
>> 
> 


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Travis CI Errors

[Phillip Carter]

In the meantime I signed up to Travis CI and it did a build on my repository 
<https://github.com/phillc54/linuxcnc/commits/master> and it succeeded.

Buildbot seemed to be successful as well.

Cheers, Phill 

> On 23 Jul 2019, at 3:56 pm, Phillip Carter  wrote:
> 
> I have just pushed some commits and I noticed an error on the commits 
> <https://github.com/LinuxCNC/linuxcnc/commits/master> page of GitHub.
> 
> The error is:
> 
> The command "./scripts/travis-install-build-deps.sh" failed and exited with 
> 100 during .
> 
> Your build has been stopped.
> 
> Which I don’t understand.
> 
> I am able to build locally for both 2.8 and master with full documentation.
> 
> I also notice the same error on two commits on July 16.
> 
> Any help appreciated.
> 
> Cheers, Phill.
> 
> 


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

[Emc-developers] Travis CI Errors

[Phillip Carter]

I have just pushed some commits and I noticed an error on the commits 
 page of GitHub.

The error is:

The command "./scripts/travis-install-build-deps.sh" failed and exited with 100 
during .

Your build has been stopped.

Which I don’t understand.

I am able to build locally for both 2.8 and master with full documentation.

I also notice the same error on two commits on July 16.

Any help appreciated.

Cheers, Phill.



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Git lost

[Phillip Carter]

Yes, that was it, thanks.

> On 20 Jul 2019, at 10:23 am, Chris Morley  wrote:
> 
> If it's just Roberts's stuff in 2.8 you are worried about - it seems to merge 
> cleanly to master  - go for it.
> 
> Chris
> 
> ________
> From: Phillip Carter 
> Sent: July 20, 2019 12:02 AM
> To: linuxcnc-developers 
> Subject: Re: [Emc-developers] Git lost
> 
> Sorry, I don’t want to actually do this.
> 
> I was just asking the question because I saw all those commits and I wasn’t 
> sure what to do.
> 
> I really don’t want to break anything...
> 
>> On 20 Jul 2019, at 9:55 am, Chris Morley  wrote:
>> 
>> I too haven't done this exact thing - i have had completely different 
>> changes go into release vrs master, so there was a conflict and I could pick 
>> the right code - big pain.
>> But look at this, I think it covers your use case:
>> https://stackoverflow.com/questions/727994/git-skipping-specific-commits-when-merging
>> 
>> Chris
>> 
>> 
>> From: Phillip Carter 
>> Sent: July 19, 2019 11:33 PM
>> To: linuxcnc-developers 
>> Subject: Re: [Emc-developers] Git lost
>> 
>> 
>> 
>>> On 20 Jul 2019, at 12:13 am, andy pugh  wrote:
>>> 
>>> On Fri, 19 Jul 2019 at 10:54, Phillip Carter 
>>> wrote:
>>> 
>>>> Oops, yes, after Tested should be Switched to master
>>> 
>>> 
>>> OK, so you are about to merge some changes that are in 2.8, not in master,
>>> and were not made by you.
>>> 
>> 
>> Correct
>> 
>>> I think that is probably OK. The norm in LinuxCNC is to put changes in the
>>> earliest branch they apply to, and then merge them up. The other things you
>>> see probably do belong in master, and were just sat there waiting for a
>>> merge.
>>> 
>> 
>> OK, thanks
>> 
>>> Is there anything in the list of commits that looks particularly wrong?
>>> 
>> 
>> Not really but I wasn’t really sure of procedure and I don’t want to do the 
>> wrong thing…
>> 
>> What happens in the case that something was meant for 2.8 but not for 
>> master, how is that prevented from being merged up in the future?
>> 
>>> --
>>> atp
>>> "A motorcycle is a bicycle with a pandemonium attachment and is designed
>>> for the especial use of mechanical geniuses, daredevils and lunatics."
>>> — George Fitch, Atlanta Constitution Newspaper, 1916
>>> 
>>> ___
>>> Emc-developers mailing list
>>> Emc-developers@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/emc-developers
>> 
>> 
>> 
>> ___
>> Emc-developers mailing list
>> Emc-developers@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/emc-developers
>> 
>> ___
>> Emc-developers mailing list
>> Emc-developers@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/emc-developers
> 
> 
> 
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers
> 
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Git lost

[Phillip Carter]

Yep, it scared the heck out of me...

> On 20 Jul 2019, at 10:17 am, Chris Morley  wrote:
> 
> So you were wanting to merge just your work and leave the other stuff to be 
> merged later?
> That would be a nice feature - cherry-pick kinda does this but IIRC it can 
> complicate merges later..
> 
> Now you can see why it's nice when a committer merges things right away so 
> they can deal with their own code.
> 
> Chris
> 
> ________
> From: Phillip Carter 
> Sent: July 20, 2019 12:02 AM
> To: linuxcnc-developers 
> Subject: Re: [Emc-developers] Git lost
> 
> Sorry, I don’t want to actually do this.
> 
> I was just asking the question because I saw all those commits and I wasn’t 
> sure what to do.
> 
> I really don’t want to break anything...
> 
>> On 20 Jul 2019, at 9:55 am, Chris Morley  wrote:
>> 
>> I too haven't done this exact thing - i have had completely different 
>> changes go into release vrs master, so there was a conflict and I could pick 
>> the right code - big pain.
>> But look at this, I think it covers your use case:
>> https://stackoverflow.com/questions/727994/git-skipping-specific-commits-when-merging
>> 
>> Chris
>> 
>> 
>> From: Phillip Carter 
>> Sent: July 19, 2019 11:33 PM
>> To: linuxcnc-developers 
>> Subject: Re: [Emc-developers] Git lost
>> 
>> 
>> 
>>> On 20 Jul 2019, at 12:13 am, andy pugh  wrote:
>>> 
>>> On Fri, 19 Jul 2019 at 10:54, Phillip Carter 
>>> wrote:
>>> 
>>>> Oops, yes, after Tested should be Switched to master
>>> 
>>> 
>>> OK, so you are about to merge some changes that are in 2.8, not in master,
>>> and were not made by you.
>>> 
>> 
>> Correct
>> 
>>> I think that is probably OK. The norm in LinuxCNC is to put changes in the
>>> earliest branch they apply to, and then merge them up. The other things you
>>> see probably do belong in master, and were just sat there waiting for a
>>> merge.
>>> 
>> 
>> OK, thanks
>> 
>>> Is there anything in the list of commits that looks particularly wrong?
>>> 
>> 
>> Not really but I wasn’t really sure of procedure and I don’t want to do the 
>> wrong thing…
>> 
>> What happens in the case that something was meant for 2.8 but not for 
>> master, how is that prevented from being merged up in the future?
>> 
>>> --
>>> atp
>>> "A motorcycle is a bicycle with a pandemonium attachment and is designed
>>> for the especial use of mechanical geniuses, daredevils and lunatics."
>>> — George Fitch, Atlanta Constitution Newspaper, 1916
>>> 
>>> ___
>>> Emc-developers mailing list
>>> Emc-developers@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/emc-developers
>> 
>> 
>> 
>> ___
>> Emc-developers mailing list
>> Emc-developers@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/emc-developers
>> 
>> ___
>> Emc-developers mailing list
>> Emc-developers@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/emc-developers
> 
> 
> 
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers
> 
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Git lost

[Phillip Carter]

Sorry, I don’t want to actually do this.

I was just asking the question because I saw all those commits and I wasn’t 
sure what to do.

I really don’t want to break anything...

> On 20 Jul 2019, at 9:55 am, Chris Morley  wrote:
> 
> I too haven't done this exact thing - i have had completely different changes 
> go into release vrs master, so there was a conflict and I could pick the 
> right code - big pain.
> But look at this, I think it covers your use case:
> https://stackoverflow.com/questions/727994/git-skipping-specific-commits-when-merging
> 
> Chris
> 
> ________
> From: Phillip Carter 
> Sent: July 19, 2019 11:33 PM
> To: linuxcnc-developers 
> Subject: Re: [Emc-developers] Git lost
> 
> 
> 
>> On 20 Jul 2019, at 12:13 am, andy pugh  wrote:
>> 
>> On Fri, 19 Jul 2019 at 10:54, Phillip Carter 
>> wrote:
>> 
>>> Oops, yes, after Tested should be Switched to master
>> 
>> 
>> OK, so you are about to merge some changes that are in 2.8, not in master,
>> and were not made by you.
>> 
> 
> Correct
> 
>> I think that is probably OK. The norm in LinuxCNC is to put changes in the
>> earliest branch they apply to, and then merge them up. The other things you
>> see probably do belong in master, and were just sat there waiting for a
>> merge.
>> 
> 
> OK, thanks
> 
>> Is there anything in the list of commits that looks particularly wrong?
>> 
> 
> Not really but I wasn’t really sure of procedure and I don’t want to do the 
> wrong thing…
> 
> What happens in the case that something was meant for 2.8 but not for master, 
> how is that prevented from being merged up in the future?
> 
>> --
>> atp
>> "A motorcycle is a bicycle with a pandemonium attachment and is designed
>> for the especial use of mechanical geniuses, daredevils and lunatics."
>> — George Fitch, Atlanta Constitution Newspaper, 1916
>> 
>> ___
>> Emc-developers mailing list
>> Emc-developers@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/emc-developers
> 
> 
> 
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers
> 
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Git lost

[Phillip Carter]

> On 20 Jul 2019, at 12:13 am, andy pugh  wrote:
> 
> On Fri, 19 Jul 2019 at 10:54, Phillip Carter 
> wrote:
> 
>> Oops, yes, after Tested should be Switched to master
> 
> 
> OK, so you are about to merge some changes that are in 2.8, not in master,
> and were not made by you.
> 

Correct

> I think that is probably OK. The norm in LinuxCNC is to put changes in the
> earliest branch they apply to, and then merge them up. The other things you
> see probably do belong in master, and were just sat there waiting for a
> merge.
> 

OK, thanks

> Is there anything in the list of commits that looks particularly wrong?
> 

Not really but I wasn’t really sure of procedure and I don’t want to do the 
wrong thing…

What happens in the case that something was meant for 2.8 but not for master, 
how is that prevented from being merged up in the future?

> -- 
> atp
> "A motorcycle is a bicycle with a pandemonium attachment and is designed
> for the especial use of mechanical geniuses, daredevils and lunatics."
> — George Fitch, Atlanta Constitution Newspaper, 1916
> 
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Git lost

[Phillip Carter]

Oops, yes, after Tested should be Switched to master.Cheers, Phill
 Original message From: andy pugh  Date: 
19/7/19  7:27 pm  (GMT+10:00) To: EMC developers 
 Subject: Re: [Emc-developers] Git lost 
On Fri, 19 Jul 2019 at 08:01, Phillip Carter wrote:> I 
am working on 2.8 locally, I have:> Pulled from origin> Modified some files> 
Committed> Tested> Switched to 2.8> Pulled from origin> Merged 2.8> Now there 
are commits that I am not sure belong in master>Should one of those 2.8s be a 
"master" ?(You seem to have switched to 2.8 from 2.8 in that sequence)-- atp"A 
motorcycle is a bicycle with a pandemonium attachment and is designedfor the 
especial use of mechanical geniuses, daredevils and lunatics."— George Fitch, 
Atlanta Constitution Newspaper, 
1916___Emc-developers mailing 
listEmc-developers@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/emc-developers
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

[Emc-developers] Git lost

[Phillip Carter]

I am working on 2.8 locally, I have:
Pulled from origin
Modified some files
Committed
Tested
Switched to 2.8
Pulled from origin
Merged 2.8
Now there are commits that I am not sure belong in master

I am not sure where to go from here.



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

[Emc-developers] GladeVCP panel names

[Phillip Carter]

I submitted a PR to master branch which allows GladeVCP panels to be named and 
it was committed three weeks ago.

https://github.com/LinuxCNC/linuxcnc/commit/9da1f618679b2f3c31054bb116ff5d48adaf676f
 


Would it be possible to get this put into 2.8?

Cheers, Phill.  
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

[Emc-developers] Did I break buildbot

[Phillip Carter]

I have done some updates to docs and when I look at the waterfall the last few 
builds in the update section say:HEAD is now at dcfbbb6 plasmac: 
rebrandingWhich I did on June 8Cheers, Phill
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] 2.8 plasmac

[Phillip Carter]

Sorry, I forgot a couple of things.

Where you have git pull, I have been doing git pull —rebase, is that ok?

Is it possible to build just the documents without building LinuxCNC?


> On 6 Jul 2019, at 10:20 am, Chris Morley  wrote:
> 
> Here is a way to do it (from memory) - again there is always more then one 
> way and surely shortcuts.
> It's a good time to try this in 2.8 because since it's not released yet we 
> can fix it without trouble :)
> 
> Assuming the  plasmac component is exactly the  same in master - I would git 
> cherry-pick it's SHA number
> Since the VCP panel is different I would commit the new version into your  
> 2.8.
> Then you must merge your  2.8 into your master.
> 
> git checkout 2.8
> git pull (so you know you are current)
> commit and/or cherry-pick changes
> gitk (check you are happy you might want to build if it's compiled code or 
> build docs if it's doc code)
> 
> git checkout master
> git pull (so you know you are current)
> git merge 2.8
> 
> There will be a conflict because the VCP names are then same.
> You must fix the conflicts, git add the fixed files and then git commit.
> (I'll let you look up how to fix conflicts or maybe you already know)
> gitk ( check you are happy)
> 
> ok so now your 2.8 and your master are updated.
> So skipping over details like the building checks etc...
> 
> Then I would switch to 2.8
> 
> git checkout 2.8
> (final happy check)
> git push --dry-run
> git push
> 
> git checkout master
> (final happy check)
> git push --dry-run
> git push
> 
> Ok now linxcnc has all your changes.
> 
> Now say later you have changes to the plasmac component that belongs in 2.8 
> and master.
> you would commit the changes in 2.8 and merge them up to master.
> This is where if you commit changes to a branch that you know will cause 
> merge conflicts,
> it's nice to do the merge right away - because you will know how the code 
> should be.
> Some times it's not possible because of someone else's complicated conflicts 
> that is in code you don't understand.
> 
> if you have changes that belong just in master you commit them just to master 
> - keeping in mind that that can still
> create merge conflicts when 2.8 is merged in next time.
> 
> Hope that helps
> 
> Chris M
> 
> From: Phillip Carter 
> Sent: July 5, 2019 11:30 PM
> To: linuxcnc-developers
> Subject: Re: [Emc-developers] 2.8 plasmac
> 
> There are no changes to existing LinuxCNC code, it is just an additional 
> component, VCP additions and configurations.
> 
> I am not sure how to proceed, currently I have locally a master branch only.
> 
> Do I copy all plasma related stuff then create a 2.8 branch from upstream 
> then put the plasmac stuff in there and push to upstream 2.8.
> 
> How do I then keep the local and upstream master and 2.8 plasmac stuff in 
> sync as well, it will be exactly the same code for both branches.
> 
> This multiple branch stuff is totally new to me and I would like to get it 
> right.
> 
> 
>> On 6 Jul 2019, at 7:12 am, Moses McKnight  wrote:
>> 
>> What Chris says is right - if GUI changes are just in the form of VCP and 
>> configs and all, it is fine with me - and thanks for your work!
>> 
>> Moses
>> 
>> On 7/5/19 2:57 PM, Chris Morley wrote:
>>> The release manager has last say on what can't be added.
>>> Assuming your 'GUI' changes are VCP changes (not say AXIS changes) , then 
>>> it sounds fine to add.
>>> plasmac is a stand alone component so is fine to add.
>>> If you don't get a negative response from Moses soon, I think you can 
>>> safely assume it's ok.
>>> (And since 2.8 isn't released yet we actually could back out code )
>>> Chris M
>>> 
>>> From: Phillip Carter 
>>> Sent: July 5, 2019 4:25 AM
>>> To: linuxcnc-developers
>>> Subject: [Emc-developers] 2.8 plasmac
>>> I have tested the plasmac configurations on 2.8 and they appear to work ok 
>>> with the only proviso that the reverse run feature is not supported.
>>> I have modified the GUIs so that none of the reverse run widgets show if 
>>> the LinuxCNC version is less than 2.9.
>>> Is it feasible to put plasmac in 2.8?
>>> If so I will then need a bit of guidance on how to do it.
>>> ___
>>> Emc-developers mailing list
>>> Emc-developers@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/emc-developers
>>> ___
>>> 

Re: [Emc-developers] 2.8 plasmac

[Phillip Carter]

Great explanation Chris, thank you, I’m sure I can work with that.

> On 6 Jul 2019, at 10:20 am, Chris Morley  wrote:
> 
> Here is a way to do it (from memory) - again there is always more then one 
> way and surely shortcuts.
> It's a good time to try this in 2.8 because since it's not released yet we 
> can fix it without trouble :)
> 
> Assuming the  plasmac component is exactly the  same in master - I would git 
> cherry-pick it's SHA number
> Since the VCP panel is different I would commit the new version into your  
> 2.8.
> Then you must merge your  2.8 into your master.
> 
> git checkout 2.8
> git pull (so you know you are current)
> commit and/or cherry-pick changes
> gitk (check you are happy you might want to build if it's compiled code or 
> build docs if it's doc code)
> 
> git checkout master
> git pull (so you know you are current)
> git merge 2.8
> 
> There will be a conflict because the VCP names are then same.
> You must fix the conflicts, git add the fixed files and then git commit.
> (I'll let you look up how to fix conflicts or maybe you already know)
> gitk ( check you are happy)
> 
> ok so now your 2.8 and your master are updated.
> So skipping over details like the building checks etc...
> 
> Then I would switch to 2.8
> 
> git checkout 2.8
> (final happy check)
> git push --dry-run
> git push
> 
> git checkout master
> (final happy check)
> git push --dry-run
> git push
> 
> Ok now linxcnc has all your changes.
> 
> Now say later you have changes to the plasmac component that belongs in 2.8 
> and master.
> you would commit the changes in 2.8 and merge them up to master.
> This is where if you commit changes to a branch that you know will cause 
> merge conflicts,
> it's nice to do the merge right away - because you will know how the code 
> should be.
> Some times it's not possible because of someone else's complicated conflicts 
> that is in code you don't understand.
> 
> if you have changes that belong just in master you commit them just to master 
> - keeping in mind that that can still
> create merge conflicts when 2.8 is merged in next time.
> 
> Hope that helps
> 
> Chris M
> 
> From: Phillip Carter 
> Sent: July 5, 2019 11:30 PM
> To: linuxcnc-developers
> Subject: Re: [Emc-developers] 2.8 plasmac
> 
> There are no changes to existing LinuxCNC code, it is just an additional 
> component, VCP additions and configurations.
> 
> I am not sure how to proceed, currently I have locally a master branch only.
> 
> Do I copy all plasma related stuff then create a 2.8 branch from upstream 
> then put the plasmac stuff in there and push to upstream 2.8.
> 
> How do I then keep the local and upstream master and 2.8 plasmac stuff in 
> sync as well, it will be exactly the same code for both branches.
> 
> This multiple branch stuff is totally new to me and I would like to get it 
> right.
> 
> 
>> On 6 Jul 2019, at 7:12 am, Moses McKnight  wrote:
>> 
>> What Chris says is right - if GUI changes are just in the form of VCP and 
>> configs and all, it is fine with me - and thanks for your work!
>> 
>> Moses
>> 
>> On 7/5/19 2:57 PM, Chris Morley wrote:
>>> The release manager has last say on what can't be added.
>>> Assuming your 'GUI' changes are VCP changes (not say AXIS changes) , then 
>>> it sounds fine to add.
>>> plasmac is a stand alone component so is fine to add.
>>> If you don't get a negative response from Moses soon, I think you can 
>>> safely assume it's ok.
>>> (And since 2.8 isn't released yet we actually could back out code )
>>> Chris M
>>> 
>>> From: Phillip Carter 
>>> Sent: July 5, 2019 4:25 AM
>>> To: linuxcnc-developers
>>> Subject: [Emc-developers] 2.8 plasmac
>>> I have tested the plasmac configurations on 2.8 and they appear to work ok 
>>> with the only proviso that the reverse run feature is not supported.
>>> I have modified the GUIs so that none of the reverse run widgets show if 
>>> the LinuxCNC version is less than 2.9.
>>> Is it feasible to put plasmac in 2.8?
>>> If so I will then need a bit of guidance on how to do it.
>>> ___
>>> Emc-developers mailing list
>>> Emc-developers@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/emc-developers
>>> ___
>>> Emc-developers mailing list
>>> Emc-developers@lists.s

Re: [Emc-developers] 2.8 plasmac

[Phillip Carter]

There are no changes to existing LinuxCNC code, it is just an additional 
component, VCP additions and configurations.

I am not sure how to proceed, currently I have locally a master branch only.

Do I copy all plasma related stuff then create a 2.8 branch from upstream then 
put the plasmac stuff in there and push to upstream 2.8.

How do I then keep the local and upstream master and 2.8 plasmac stuff in sync 
as well, it will be exactly the same code for both branches.

This multiple branch stuff is totally new to me and I would like to get it 
right.
 

> On 6 Jul 2019, at 7:12 am, Moses McKnight  wrote:
> 
> What Chris says is right - if GUI changes are just in the form of VCP and 
> configs and all, it is fine with me - and thanks for your work!
> 
> Moses
> 
> On 7/5/19 2:57 PM, Chris Morley wrote:
>> The release manager has last say on what can't be added.
>> Assuming your 'GUI' changes are VCP changes (not say AXIS changes) , then it 
>> sounds fine to add.
>> plasmac is a stand alone component so is fine to add.
>> If you don't get a negative response from Moses soon, I think you can safely 
>> assume it's ok.
>> (And since 2.8 isn't released yet we actually could back out code )
>> Chris M
>> 
>> From: Phillip Carter 
>> Sent: July 5, 2019 4:25 AM
>> To: linuxcnc-developers
>> Subject: [Emc-developers] 2.8 plasmac
>> I have tested the plasmac configurations on 2.8 and they appear to work ok 
>> with the only proviso that the reverse run feature is not supported.
>> I have modified the GUIs so that none of the reverse run widgets show if the 
>> LinuxCNC version is less than 2.9.
>> Is it feasible to put plasmac in 2.8?
>> If so I will then need a bit of guidance on how to do it.
>> ___
>> Emc-developers mailing list
>> Emc-developers@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/emc-developers
>> ___
>> Emc-developers mailing list
>> Emc-developers@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/emc-developers
> 
> -- 
> And as it is appointed unto men once to die, but after this the judgment:
> So Christ was once offered to bear the sins of many; and unto them that look 
> for him shall he appear the second time without sin unto salvation.
> (Hebrews 9:27-28)
> 
> 
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

[Emc-developers] 2.8 plasmac

[Phillip Carter]

I have tested the plasmac configurations on 2.8 and they appear to work ok with 
the only proviso that the reverse run feature is not supported.

I have modified the GUIs so that none of the reverse run widgets show if the 
LinuxCNC version is less than 2.9.

Is it feasible to put plasmac in 2.8?

If so I will then need a bit of guidance on how to do it.

___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Plasma User Information

[Phillip Carter]

You pointed me in the right direction previously with the plasmac docs.

Yes, it was intended for master.

Cheers, Phill. 

> On 3 Jul 2019, at 9:29 am, John Thornton  wrote:
> 
> I agree, are you familiar with underlying document structure and how they get 
> built? Is this going in Master?
> 
> JT
> 
> On 7/2/2019 6:16 PM, Phillip Carter wrote:
>> I had originally thought of creating a separate plasma document like the 
>> integrators as well and putting both this document and the plasmac 
>> documentation in it but as there is no specific lathe or mill document (or 
>> any others) then it would seem a bit odd.
>> 
>> I think Chris’s suggestion is the way to go at this stage.
>> 
>>> On 3 Jul 2019, at 7:07 am, Chris Morley  wrote:
>>> 
>>> While I agree the docs are large and could be organized differently, I 
>>> think 'general user information' seems about the right place for it based 
>>> on all the other chapters names.
>>> As for making the docs larger - I don't think this is a problem as if you 
>>> don't have a plasma, you do not need to/nor would, look through this.
>>> 
>>> Rather then debate about where it should go for quite some time - why not 
>>> add it and see how that works out.
>>> This is a development branch so could be changed latter.
>>> I think it's better to have the (excellently done) docs in the wrong place 
>>> then not have them at all.
>>> 
>>> In the long run we could write a formal guide line to how the docs are 
>>> meant to be laid out.
>>> Though I must confess I hate it when we change them as I have to search for 
>>> everything again (probably an indication that they are a little bit 
>>> organized inefficiently)
>>> 
>>> but after all that - linuxcnc's documents as a whole are excellent and I 
>>> thank all who work on them because doing docs sucks : )
>>> 
>>> Chris
>>> 
>>> From: John Thornton 
>>> Sent: July 2, 2019 6:09 PM
>>> To: emc-developers@lists.sourceforge.net
>>> Subject: Re: [Emc-developers] Plasma User Information
>>> 
>>> It's my humble opinion that documents that are not about LinuxCNC like
>>> the Integrators Information document should not be in the main LinuxCNC
>>> document as it is far too big now.
>>> 
>>> 
>>> 
>>> ___
>>> Emc-developers mailing list
>>> Emc-developers@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/emc-developers
>> 
>> 
>> ___
>> Emc-developers mailing list
>> Emc-developers@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/emc-developers
> 
> 
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Plasma User Information

[Phillip Carter]

I had originally thought of creating a separate plasma document like the 
integrators as well and putting both this document and the plasmac 
documentation in it but as there is no specific lathe or mill document (or any 
others) then it would seem a bit odd.

I think Chris’s suggestion is the way to go at this stage.

> On 3 Jul 2019, at 7:07 am, Chris Morley  wrote:
> 
> While I agree the docs are large and could be organized differently, I think 
> 'general user information' seems about the right place for it based on all 
> the other chapters names.
> As for making the docs larger - I don't think this is a problem as if you 
> don't have a plasma, you do not need to/nor would, look through this.
> 
> Rather then debate about where it should go for quite some time - why not add 
> it and see how that works out.
> This is a development branch so could be changed latter.
> I think it's better to have the (excellently done) docs in the wrong place 
> then not have them at all.
> 
> In the long run we could write a formal guide line to how the docs are meant 
> to be laid out.
> Though I must confess I hate it when we change them as I have to search for 
> everything again (probably an indication that they are a little bit organized 
> inefficiently)
> 
> but after all that - linuxcnc's documents as a whole are excellent and I 
> thank all who work on them because doing docs sucks : )
> 
> Chris
> 
> From: John Thornton 
> Sent: July 2, 2019 6:09 PM
> To: emc-developers@lists.sourceforge.net
> Subject: Re: [Emc-developers] Plasma User Information
> 
> It's my humble opinion that documents that are not about LinuxCNC like
> the Integrators Information document should not be in the main LinuxCNC
> document as it is far too big now.
> 
> 
> 
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

[Emc-developers] Plasma User Information

[Phillip Carter]

Rod Webster (forum member rodw) has put together a document that provides 
general information about CNC plasma cutting. I feel that it would be 
worthwhile putting it into the documentation in the General User Information 
section.

I have posted a PDF copy online.

http://home.iprimus.com.au/phillcarter/plasma-cnc-primer.pdf 


If there are no objections I would be happy to go ahead and push the document.

Cheers, Phill.
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Workflow

[Phillip Carter]

Thanks guys, I think I have it sorted now.

> On 1 Jul 2019, at 6:19 am, andy pugh  wrote:
> 
> If my new stuff is a single commit I take a short-cut.
> 
> On Sun, 30 Jun 2019 at 20:52, Chris Morley  wrote:
> 
>> If I am working on a private branch based on master and want to push my work 
>> :
>> and If my private branch is behind linuxcnc's master
>> 
>> switch to my local master and pull to bring it up to date.
> 
> git cherry-pick /the SHA of the new commit/
> git push --dry-run
> 
> and so on.
> 
> -- 
> atp
> "A motorcycle is a bicycle with a pandemonium attachment and is
> designed for the especial use of mechanical geniuses, daredevils and
> lunatics."
> — George Fitch, Atlanta Constitution Newspaper, 1916
> 
> 
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

[Emc-developers] Workflow

[Phillip Carter]

I noticed today when I pushed a commit that it also pushed a message about a 
merge between my branches which doesn't seem correct.Currently I do all my work 
on my plasmac branch. I checkout master, fetch from upstream then rebase 
upstream/master. I then checkout plasmac and merge master.Then I pushed to 
upstream master.Should I be doing all my work on my master branch or is there 
some other way I should be doing it. Cheers, Phill
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Updates

[Phillip Carter]

Sorry to be a pain but…

I have tried:

linuxcnc-build: force build --branch-2.9 2000.docs

And got the following:

Something bad happened (see logs)

I have tried master and Master instead of 2.9 and get the same result.

Also when I look at this page http://buildbot.linuxcnc.org/dists/stretch/ 
<http://buildbot.linuxcnc.org/dists/stretch/> it shows master and 2.7 haven’t 
been updated since 09-Jun 

Cheers, Phill.


> On 29 Jun 2019, at 10:21 pm, John Thornton  wrote:
> 
> If the buildbot is not down it usually shows up in a few hours. If the 
> buildbot does not rebuild you can force it to build the docs with the 
> following in the #linuxcnc-devel IRC channel.
> 
> linuxcnc-build: force build --branch-2.8 2000.docs
> 
> You can go to the buildbot waterfall page and see the status of any queued 
> builds
> 
> http://buildbot.linuxcnc.org/buildbot/waterfall
> 
> JT
> 
> On 6/29/2019 5:42 AM, Phillip Carter wrote:
>> Is there a specific time from when a commit is pushed until it appears in 
>> the online docs and the buildbot?Cheers, Phill
>> ___
>> Emc-developers mailing list
>> Emc-developers@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/emc-developers
> 
> 
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Updates

[Phillip Carter]

Thank you.Cheers, Phill
 Original message From: John Thornton  Date: 
29/6/19  10:21 pm  (GMT+10:00) To: emc-developers@lists.sourceforge.net 
Subject: Re: [Emc-developers] Updates If the buildbot is not down it usually 
shows up in a few hours. If the buildbot does not rebuild you can force it to 
build the docs with the following in the #linuxcnc-devel IRC 
channel.linuxcnc-build: force build --branch-2.8 2000.docsYou can go to the 
buildbot waterfall page and see the status of any queued 
buildshttp://buildbot.linuxcnc.org/buildbot/waterfallJTOn 6/29/2019 5:42 AM, 
Phillip Carter wrote:> Is there a specific time from when a commit is pushed 
until it appears in the online docs and the buildbot?Cheers, Phill> 
___> Emc-developers mailing list> 
Emc-developers@lists.sourceforge.net> 
https://lists.sourceforge.net/lists/listinfo/emc-developers___Emc-developers
 mailing 
listEmc-developers@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/emc-developers
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

[Emc-developers] Updates

[Phillip Carter]

Is there a specific time from when a commit is pushed until it appears in the 
online docs and the buildbot?Cheers, Phill
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] plasmac

[Phillip Carter]

Thanks Chris,

I shall begin squashing…

Cheers, Phill.

> On 28 Jun 2019, at 12:06 pm, Chris Morley  wrote:
> 
> In general if there commits that are not so note worthy such as 'WIP' you 
> probably should squash them.
> In my case I squashed almost everything with qtvcp unless I thought it was 
> really important, before I initially added it to master.
> 
> So I would suggest be ruthless with squashing before putting it in master.
> 
> Oh welcome to linuxcnc developers ..club :)
> 
> Chris M
> ________
> From: Phillip Carter 
> Sent: June 28, 2019 1:31 AM
> To: linuxcnc-developers
> Subject: [Emc-developers] plasmac
> 
> I am ready to push plasmac but before I do should I try to squash it to one 
> commit.
> 
> There are 440+ local commits and sometime I was a bit lazy with commit 
> comments.
> 
> Cheers, Phill.
> 
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers
> 
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

[Emc-developers] plasmac

[Phillip Carter]

I am ready to push plasmac but before I do should I try to squash it to one 
commit.

There are 440+ local commits and sometime I was a bit lazy with commit comments.

Cheers, Phill.

___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Gmoccapy Documentation Links

[Phillip Carter]

Thanks Andy, it seemed to have worked…

Cheers, Phill.

> On 28 Jun 2019, at 9:28 am, andy pugh  wrote:
> 
> On Thu, 27 Jun 2019 at 23:40, Phillip Carter  wrote:
> 
>> The linuxcnc repo is my upstream repo, so do I just do git push this_branch 
>> upstream:master
> 
> What I do:
> 
> git push --dry-run
> 
> (some output that generally includes abcd1234...3456dcf12)
> 
> git log -p abcd1234...3456dcf12
> 
> (do I see what I expected?)
> 
> if yes:
> 
> git push
> 
> if no:
> 
> GOOOGLE!
> 
> 
> -- 
> atp
> "A motorcycle is a bicycle with a pandemonium attachment and is
> designed for the especial use of mechanical geniuses, daredevils and
> lunatics."
> — George Fitch, Atlanta Constitution Newspaper, 1916
> 
> 
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Gmoccapy Documentation Links

[Phillip Carter]

Thank you,
Both gmoccapy.txt and gmoccapy-hu.txt have the same chapter anchor name and a 
grep of docs/src seems to show no documents requiring a link to gmoccpy-hu.
I think it would be safe to rename the anchor in gmoccopy-hu from 
[[cha:gmoccapy]] to [[cha:gmoccapy-hu]].
I tried it here and all existing links now display correctly.
If this sounds reasonable then I would like to go ahead with this as a test for 
my newly granted push access but I’m not sure of the correct procedure.
I guess I need to:
. create a branch locally
. make the changes.
. push them linuxcnc

The linuxcnc repo is my upstream repo, so do I just do git push this_branch 
upstream:master

Cheers, Phill.


> On 28 Jun 2019, at 12:20 am, John Thornton  wrote:
> 
> Check that the document anchor is what you expect in the document.
> 
> https://github.com/LinuxCNC/linuxcnc/blob/master/docs/asciidoc-markup.txt
> 
> https://github.com/LinuxCNC/linuxcnc/blob/master/docs/src/gui/gmoccapy-hu.txt
> 
> https://github.com/LinuxCNC/linuxcnc/blob/master/docs/src/gui/gmoccapy.txt
> 
> You can't work around it, the document anchor must be fixed to be unique.
> 
> JT
> 
> On 6/26/2019 8:50 PM, Phillip Carter wrote:
>> I am trying to link to the Gmoccapy document by adding 
>> <> in my document.
>> After I run make the link points to gmoccapy-hu.txt rather than gmoccapy.txt
>> I see the same problem in the LinuxCNC html documentation, the link to 
>> Gmoccapy on http://linuxcnc.org/docs/devel/html/config/lathe-config.html 
>> <http://linuxcnc.org/docs/devel/html/config/lathe-config.html> also points 
>> to the Hungarian version.
>> How can I work around this?
>> 
>> Cheers. Phill.
>> ___
>> Emc-developers mailing list
>> Emc-developers@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/emc-developers
> 
> 
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

[Emc-developers] Gmoccapy Documentation Links

[Phillip Carter]

I am trying to link to the Gmoccapy document by adding 
<> in my document.
After I run make the link points to gmoccapy-hu.txt rather than gmoccapy.txt
I see the same problem in the LinuxCNC html documentation, the link to Gmoccapy 
on http://linuxcnc.org/docs/devel/html/config/lathe-config.html 
 also points to 
the Hungarian version.
How can I work around this?

Cheers. Phill.
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] plasmac

[Phillip Carter]

I have sorted out the asciidoc format and have figured out how to get the user 
guide to build and it appears correctly in both HTML and PDF formats.
I didn’t know where it should go so at the moment I have put it in General User 
Information. Maybe plasma could have a separate section. There is another user 
currently compiling a generic plasma document that could be incorporated as 
well.


> On 26 Jun 2019, at 11:42 am, Phillip Carter  wrote:
> 
> Chris,
> 
> Thanks for that and yes, I would be interested.
> 
> Cheers, Phill.
> 
>> On 26 Jun 2019, at 11:38 am, Chris Morley > <mailto:chrisinnana...@hotmail.com>> wrote:
>> 
>> Phill
>> 
>> I just merged your axis/gladevcp work, sorry I forgot about it.
>> I think it would be great to get plasmac in 2.9.
>> I also think we should give you push access - are you interested?
>> 
>> Chris M
>> 
>> 
>> From: Phillip Carter > <mailto:phillcarte...@gmail.com>>
>> Sent: June 26, 2019 1:18 AM
>> To: emc-developers
>> Subject: [Emc-developers] plasmac
>> 
>> I have been working on a plasma config which is a complete configuration for 
>> a plasma cutter consisting of a component named plasmac.comp and 
>> configuration files for both Axis and Gmoccapy.
>> It has been tested by several users and is at the stage where I think it 
>> could be incorporated into 2.9. It cannot be used in earlier versions as it 
>> uses the reverse run feature.
>> At the moment I have the configurations in configs/by_machine/plasmac and I 
>> am not sure whether this is the correct place for them.
>> I recently put in a PR which would also be nice to have committed otherwise 
>> I would need to make some changes to the plasmac Axis config.
>> I have done a user guide in asciidoc but have just noticed that it is quite 
>> different in format to the LinuxCNC docs so I will need to rewrite that to 
>> suit. I am also unsure as to where this doc should go and how to incorporate 
>> it into the LinuxCNC docs.
>> 
>> Cheers, Phill.
>> 
>> PR: https://github.com/LinuxCNC/linuxcnc/pull/606 
>> <https://github.com/LinuxCNC/linuxcnc/pull/606> 
>> <https://github.com/LinuxCNC/linuxcnc/pull/606 
>> <https://github.com/LinuxCNC/linuxcnc/pull/606>>
>> 
>> User Guide: 
>> https://github.com/phillc54/linuxcnc/blob/plasmac/configs/by_machine/plasmac/documents/plasmac/plasmac_user_guide.adoc
>>  
>> <https://github.com/phillc54/linuxcnc/blob/plasmac/configs/by_machine/plasmac/documents/plasmac/plasmac_user_guide.adoc><https://github.com/phillc54/linuxcnc/blob/plasmac/configs/by_machine/plasmac/documents/plasmac/plasmac_user_guide.adoc
>>  
>> <https://github.com/phillc54/linuxcnc/blob/plasmac/configs/by_machine/plasmac/documents/plasmac/plasmac_user_guide.adoc>>
>> ___
>> Emc-developers mailing list
>> Emc-developers@lists.sourceforge.net 
>> <mailto:Emc-developers@lists.sourceforge.net>
>> https://lists.sourceforge.net/lists/listinfo/emc-developers 
>> <https://lists.sourceforge.net/lists/listinfo/emc-developers>
>> 
>> ___
>> Emc-developers mailing list
>> Emc-developers@lists.sourceforge.net 
>> <mailto:Emc-developers@lists.sourceforge.net>
>> https://lists.sourceforge.net/lists/listinfo/emc-developers 
>> <https://lists.sourceforge.net/lists/listinfo/emc-developers>


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] plasmac

[Phillip Carter]

Chris,

Thanks for that and yes, I would be interested.

Cheers, Phill.

> On 26 Jun 2019, at 11:38 am, Chris Morley  wrote:
> 
> Phill
> 
> I just merged your axis/gladevcp work, sorry I forgot about it.
> I think it would be great to get plasmac in 2.9.
> I also think we should give you push access - are you interested?
> 
> Chris M
> 
> ________
> From: Phillip Carter  <mailto:phillcarte...@gmail.com>>
> Sent: June 26, 2019 1:18 AM
> To: emc-developers
> Subject: [Emc-developers] plasmac
> 
> I have been working on a plasma config which is a complete configuration for 
> a plasma cutter consisting of a component named plasmac.comp and 
> configuration files for both Axis and Gmoccapy.
> It has been tested by several users and is at the stage where I think it 
> could be incorporated into 2.9. It cannot be used in earlier versions as it 
> uses the reverse run feature.
> At the moment I have the configurations in configs/by_machine/plasmac and I 
> am not sure whether this is the correct place for them.
> I recently put in a PR which would also be nice to have committed otherwise I 
> would need to make some changes to the plasmac Axis config.
> I have done a user guide in asciidoc but have just noticed that it is quite 
> different in format to the LinuxCNC docs so I will need to rewrite that to 
> suit. I am also unsure as to where this doc should go and how to incorporate 
> it into the LinuxCNC docs.
> 
> Cheers, Phill.
> 
> PR: https://github.com/LinuxCNC/linuxcnc/pull/606 
> <https://github.com/LinuxCNC/linuxcnc/pull/606> 
> <https://github.com/LinuxCNC/linuxcnc/pull/606 
> <https://github.com/LinuxCNC/linuxcnc/pull/606>>
> 
> User Guide: 
> https://github.com/phillc54/linuxcnc/blob/plasmac/configs/by_machine/plasmac/documents/plasmac/plasmac_user_guide.adoc
>  
> <https://github.com/phillc54/linuxcnc/blob/plasmac/configs/by_machine/plasmac/documents/plasmac/plasmac_user_guide.adoc><https://github.com/phillc54/linuxcnc/blob/plasmac/configs/by_machine/plasmac/documents/plasmac/plasmac_user_guide.adoc
>  
> <https://github.com/phillc54/linuxcnc/blob/plasmac/configs/by_machine/plasmac/documents/plasmac/plasmac_user_guide.adoc>>
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net 
> <mailto:Emc-developers@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/emc-developers 
> <https://lists.sourceforge.net/lists/listinfo/emc-developers>
> 
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net 
> <mailto:Emc-developers@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/emc-developers 
> <https://lists.sourceforge.net/lists/listinfo/emc-developers>

___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

[Emc-developers] plasmac

[Phillip Carter]

I have been working on a plasma config which is a complete configuration for a 
plasma cutter consisting of a component named plasmac.comp and configuration 
files for both Axis and Gmoccapy.
It has been tested by several users and is at the stage where I think it could 
be incorporated into 2.9. It cannot be used in earlier versions as it uses the 
reverse run feature.
At the moment I have the configurations in configs/by_machine/plasmac and I am 
not sure whether this is the correct place for them.
I recently put in a PR which would also be nice to have committed otherwise I 
would need to make some changes to the plasmac Axis config.
I have done a user guide in asciidoc but have just noticed that it is quite 
different in format to the LinuxCNC docs so I will need to rewrite that to 
suit. I am also unsure as to where this doc should go and how to incorporate it 
into the LinuxCNC docs.

Cheers, Phill.

PR: https://github.com/LinuxCNC/linuxcnc/pull/606 


User Guide: 
https://github.com/phillc54/linuxcnc/blob/plasmac/configs/by_machine/plasmac/documents/plasmac/plasmac_user_guide.adoc
 

___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Viewing documentation changes

[Phillip Carter]

I found a method that worked well for me:

.copy the file to be edited into a DropBox or similar location
.open http://gist.asciidoctor.org/ <http://gist.asciidoctor.org/> in a browser
.drop the link to the file in the link box at the top right of the browser page
.edit/save the file then update the browser page
.when all is good save the file back to the original location
.commit and make PR

Cheers, Phill.

> On 8 Jun 2019, at 10:34 pm, andy pugh  wrote:
> 
> On Sat, 8 Jun 2019 at 08:10, Phillip Carter  wrote:
> 
> How do I now view the documentation to ensure that it looks like it should.
>> 
> 
> You can view asciidoc directly on the Github page. However it only seems to
> get rendered as asciidoc if it has the .asciidoc or .adoc extension.
> 
> See for example:
> https://github.com/andypugh/linuxcnc/blob/master/docs/src/gui/gladevcp.adoc
> 
> You can edit the file directly on the github web site using the pencil icon
> at the top right of the document frame. You can also change the file name
> in that view.
> 
> So here is one possible workstream for docs changes:
> 
> . browse to the file, press the pencil icon
> . change the name to .adoc and make the changes
> . commit the changes and re-open the file
> . if happy, edit again to change the name back.
> . commit again, make pull request.
> 
> I don't see a way to squash the file renames in the web interface, though,
> so you would need to rebase -i the commits at the command line before
> submitting the pull request.
> (This is something that the pull request acceptor can do if that is enabled
> for the repo, but that feature is disabled for LinuxCNC)
> 
> -- 
> atp
> "A motorcycle is a bicycle with a pandemonium attachment and is designed
> for the especial use of mechanical geniuses, daredevils and lunatics."
> — George Fitch, Atlanta Constitution Newspaper, 1916
> 
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Viewing documentation changes

[Phillip Carter]

Thank you, that will give me something to play around with tomorrow.Cheers, 
Phill
 Original message From: andy pugh  Date: 
8/6/19  10:34 pm  (GMT+10:00) To: EMC developers 
 Subject: Re: [Emc-developers] Viewing 
documentation changes On Sat, 8 Jun 2019 at 08:10, Phillip Carter 
 wrote:How do I now view the documentation to ensure 
that it looks like it should.>You can view asciidoc directly on the Github 
page. However it only seems toget rendered as asciidoc if it has the .asciidoc 
or .adoc extension.See for 
example:https://github.com/andypugh/linuxcnc/blob/master/docs/src/gui/gladevcp.adocYou
 can edit the file directly on the github web site using the pencil iconat the 
top right of the document frame. You can also change the file namein that 
view.So here is one possible workstream for docs changes:. browse to the file, 
press the pencil icon. change the name to .adoc and make the changes. commit 
the changes and re-open the file. if happy, edit again to change the name 
back.. commit again, make pull request.I don't see a way to squash the file 
renames in the web interface, though,so you would need to rebase -i the commits 
at the command line beforesubmitting the pull request.(This is something that 
the pull request acceptor can do if that is enabledfor the repo, but that 
feature is disabled for LinuxCNC)-- atp"A motorcycle is a bicycle with a 
pandemonium attachment and is designedfor the especial use of mechanical 
geniuses, daredevils and lunatics."— George Fitch, Atlanta Constitution 
Newspaper, 1916___Emc-developers 
mailing 
listEmc-developers@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/emc-developers
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Viewing documentation changes

[Phillip Carter]

Thank you, that will give me something to play around with tomorrow.Cheers, 
Phill
 Original message From: andy pugh  Date: 
8/6/19  10:34 pm  (GMT+10:00) To: EMC developers 
 Subject: Re: [Emc-developers] Viewing 
documentation changes On Sat, 8 Jun 2019 at 08:10, Phillip Carter 
 wrote:How do I now view the documentation to ensure 
that it looks like it should.>You can view asciidoc directly on the Github 
page. However it only seems toget rendered as asciidoc if it has the .asciidoc 
or .adoc extension.See for 
example:https://github.com/andypugh/linuxcnc/blob/master/docs/src/gui/gladevcp.adocYou
 can edit the file directly on the github web site using the pencil iconat the 
top right of the document frame. You can also change the file namein that 
view.So here is one possible workstream for docs changes:. browse to the file, 
press the pencil icon. change the name to .adoc and make the changes. commit 
the changes and re-open the file. if happy, edit again to change the name 
back.. commit again, make pull request.I don't see a way to squash the file 
renames in the web interface, though,so you would need to rebase -i the commits 
at the command line beforesubmitting the pull request.(This is something that 
the pull request acceptor can do if that is enabledfor the repo, but that 
feature is disabled for LinuxCNC)-- atp"A motorcycle is a bicycle with a 
pandemonium attachment and is designedfor the especial use of mechanical 
geniuses, daredevils and lunatics."— George Fitch, Atlanta Constitution 
Newspaper, 1916___Emc-developers 
mailing 
listEmc-developers@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/emc-developers
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Viewing documentation changes

[Phillip Carter]

Sorry, another question.Is the --enable-build-documentation in addition to 
--with-realtime or do they need to be run separately.Cheers, Phill.Cheers, Phill
 Original message From: Chris Morley 
 Date: 8/6/19  7:17 pm  (GMT+10:00) To: EMC 
developers  Subject: Re: [Emc-developers] 
Viewing documentation changes PhillYou would need to configure with 
--enable-build-documentaion=html (for html only docs) and then compile 
linuxcnc.Developers can push a scratch branch to git and the buildbot will do 
the same.Chris MFrom: Phillip Carter 
Sent: June 8, 2019 7:08 AMTo: emc-developersSubject: 
[Emc-developers] Viewing documentation changesI have made a small change to 
Axis regarding integrating a GladeVCP panel and I intend to submit a PR when 
complete.I have edited the documentation which I found at 
/docs/src/gui/gladevcp.txt.How do I now view the documentation to ensure that 
it looks like it should.Cheers, 
Phill.___Emc-developers mailing 
listEmc-developers@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/emc-developers___Emc-developers
 mailing 
listEmc-developers@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/emc-developers
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Viewing documentation changes

[Phillip Carter]

Chris,Thank you.Cheers, Phill.Cheers, Phill
 Original message From: Chris Morley 
 Date: 8/6/19  7:17 pm  (GMT+10:00) To: EMC 
developers  Subject: Re: [Emc-developers] 
Viewing documentation changes PhillYou would need to configure with 
--enable-build-documentaion=html (for html only docs) and then compile 
linuxcnc.Developers can push a scratch branch to git and the buildbot will do 
the same.Chris MFrom: Phillip Carter 
Sent: June 8, 2019 7:08 AMTo: emc-developersSubject: 
[Emc-developers] Viewing documentation changesI have made a small change to 
Axis regarding integrating a GladeVCP panel and I intend to submit a PR when 
complete.I have edited the documentation which I found at 
/docs/src/gui/gladevcp.txt.How do I now view the documentation to ensure that 
it looks like it should.Cheers, 
Phill.___Emc-developers mailing 
listEmc-developers@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/emc-developers___Emc-developers
 mailing 
listEmc-developers@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/emc-developers
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

[Emc-developers] Viewing documentation changes

[Phillip Carter]

I have made a small change to Axis regarding integrating a GladeVCP panel and I 
intend to submit a PR when complete.
I have edited the documentation which I found at /docs/src/gui/gladevcp.txt.
How do I now view the documentation to ensure that it looks like it should.

Cheers, Phill.

___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Introduction and a couple of questions

[Phillip Carter]

Rob,

The branch I have working is here 
https://github.com/phillc54/linuxcnc/tree/reverse-run 
 it was up to date with 
master yesterday.

Basically what I did was add your original reverse run commits to an up to date 
master (12 Dec 2018) one at a time and then made changes until they took and 
appeared to work. There were a couple of commits that I couldn’t get to take 
but from memory they where some sort of tidy up and not necessary. There was 
also an additional commit I did at the end for a ramping acceleration issue. I 
thought I kept a list of notes of what I did but I seemed to have misplaced it, 
I will keep searching. It would be great if you could go through it to see if 
it is ok.

Cheers, Phill.

> On 22 May 2019, at 9:19 am, Chris Morley  wrote:
> 
> 
> 
> 
> From: Rod Webster 
> Sent: May 21, 2019 10:43 PM
> To: EMC developers
> Subject: Re: [Emc-developers] Introduction and a couple of questions
> 
> Chris/Rob/Andy
> 
>>> I don't want to sound negative or a whinger.
> You don't - it's frustration
> 
 Reverse run is not even in master yet - so how could we release it?
> 
>>> So the question really is why did Phill have to start again? All he did was
>>> update that branch. It should have been in master by now.
>>> Why don't you at least get his work into the official repository?
> 
> There is no process for merging work. It usually comes down to the guy who 
> made the
> code merging it himself. The guy who made this was not a dev and none of the 
> devs
> needed it.
> compounded that master is used so regularly that devs are reluctant to commit 
> work that is not theirs, in case
> it breaks things. - Who will fix it in a timely matter.
> 
> As you can see alot of catch 22s here.
> 
>> The last commit to the state tags branch was in February 2015 and I
>> understand its been in use commercially since around then.
>> What causes this paralysis?
> 
> Pilotpath is it's own project they pay people to work on the code for what 
> they want.
> Again with no formal merge process nor enough devs to spend on it the patches 
> sit too long, then are hard to merge.
> 
>> Why did I see Andy's multi spindle sneak into master and I knew nothing
>> about it? Yeh, I know I don't use a spindle but I do follow progress pretty
>> closely
>> You might recall that was not entirely bug free on its debut.
> 
> Andy can push his own work and commit to fixing what broke quickly.
> There was no serious talk of release in the near future.
> 
>> I think what Phill has done with his plasma component and GU's is amazing.
>> But he
>> should not need to maintain the core code for a 4 year old feature on a
>> private repository to achieve it.
> 
> I agree - and it's great they we are talking about it - I feel this time 
> something will happen.
> 
> We have tried a few time to address these short comings and have never got it 
> satisfactory.
> But the project continues.
> 
> Chris M
> 
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Introduction and a couple of questions

[Phillip Carter]

I do have a separate reverse-run branch if that is up to date with Master (well 
it was of a couple of hours ago)

https://github.com/phillc54/linuxcnc/tree/reverse-run 


Most probably if there are other TP updates then this will be broken…

Cheers, Phill.


> On 21 May 2019, at 3:32 pm, Chris Morley  wrote:
> 
> I feel we have be cautious with 'getter done'
> Each time we add some capability time is needed to properly find bugs and 
> update screens configuration wizards etc.
> We are notorious for waiting waaay too long to make a stabilization branch 
> and so feel compelled to release it too early.
> Particularly the configuration wizards always have bugs that show themselves 
> right after release.
> Since we historically only build a ISO once - we are stuck with buggy 
> software for newbees to endure till they update.
> 
> I would suggest we have already started to go too far with the inclusion of 
> python 3 code work.
> Our 2.8 stabilization branch should probably be made under that and soon.
> Then we should stabilize for a long time like 4 -6 months.
> 
> Then we should release in another year because there is lots to add in that 
> year.
> And that is when reverse run should go in.
> 
> My 2 cents
> Chris M
> 
> 
> From: Rod Webster 
> Sent: May 21, 2019 4:22 AM
> To: EMC developers
> Subject: Re: [Emc-developers] Introduction and a couple of questions
> 
> Well forum member PhillC has a working version of  Reverse run in his git
> repository  and enough people
> have been using it to confirm it works without breaking anything.
> 
> Aside from some simulations and one component (plasmac.comp), incorporating
> reverse run is the only change Phill has done to the core code and he keeps
> it up to date with master branch weekly. I think he's kept the sims and
> component separate from his modified master branch code.
> 
> So there is not really any excuse to leave Reverse run out.   Get it done
> Andy!
> 
> 
> 
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] future of rpi?

[Phillip Carter]

This DIY tutorial may be of interest.

>

Cheers, Phill.

> On 6 Mar 2019, at 12:50 pm, Gene Heskett  wrote:
> 
> Greetings all;
> 
> About 90 days back there were some new kernels and libraries made 
> available that I've heard sped up the video on the pi's quite a bit.
> 
> But I have the stuff wrapped around the realtime kernel its running 
> pinned so as not to lose the ability to run my lathe.  That file is 
> here:
> pi@picnc:/etc/apt/preferences.d $ cat kernel.pref
> Package:linux-kernel
> pin: version 4.4.4-rt9-v7+
> Pin-Priority: 1001
> 
> Package: linux-headers
> Pin: version 4.4.4-rt9-v7+
> Pin-Priority: 1001
> 
> Package: raspberrypi-bootloader
> Pin: version 1.20170427-1
> Pin-Priority: 1001
> 
> Package: raspberrypi-kernel
> Pin: version 1.20170427-1
> Pin-Priority: 1001
> 
> But while they been pinned, apparently the video has been updated and the 
> older signal paths between the keyboard/mouse, and feedback to the video 
> have been destroyed to the extent that my sheldon is now no longer 
> usable. There is now at least a 1 second delay for any keyboard or mouse 
> event to get to linuxcnc from my fingers, and at least a 1 second delay 
> between lcnc's movements of the machine, and any update making it back 
> to the backplot. An because the machine isn't under the usual tight 
> control I've now destroyed 2 of the very expensive, smallest 3 cornered 
> threading chips for making external threads.
> 
> So I need a freshly built and installable realtime kernel that is 
> compatible with the latest libraspberripi.bin and friends, or I'm going 
> to have to find a D-525-MW mobo and reconvert it to a 7i90 with a 
> parport interface since theres no such thing as an spi driver for the 
> x86 boards. Given the rpi communities attitude vis-a-vis machine 
> controls, (we are being ignored on their many lists and forums, the rare 
> exception being the linux-arm list) it looks like going back to an intel 
> driven system is the only choice I really have if I want a useable lathe 
> again. My biggest problem is where the heck am I going to put a D-525-MW 
> mobo in the hacked up mess hanging on the riser pole on the back of the 
> machine now.
> 
> I have several later rt kernels built, right there on the pi, but so far, 
> despite repeated pleas for instructions on how to install them, nothing 
> has been offered, and I'm now convinced after 2 years, that the pi folks 
> would just as soon I took the blue pill and went away. I wish there were 
> a thousand of me beating on the drums for support, but one voice is 
> swept away in the multimedia wind.
> 
> So is there a chance of a new kernel, realtime enough to work with 
> linuxcnc AND take advantage of the new video modes made available in the 
> last 5 or 6 months which might materialize by the 1st of May, or do I 
> put a intel mobo on it and install from the wheezy install iso?  Does 
> that involve the wholesale replacement of $200+ worth of 7i90HD+ 3x 
> 7i42TA's with something else?  That, once the noise was whupped, has 
> Just Worked. I think the question then is, is the intel parport fast 
> enough to service the 7i90HD over that interface?
> 
> I know that manpower to support one user of this architecture is not 
> efficient use of your time so if I have to rebuild, I won't be hugely 
> upset as this is the real world, but while it worked, it worked quite 
> well.
> 
> So what say you folks?
> 
> Like Douglas Adams, Thanks for the fish.
> 
> Cheers, Gene Heskett
> -- 
> "There are four boxes to be used in defense of liberty:
> soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author)
> Genes Web page 
> 
> 
> 
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Reverse Run

[Phillip Carter]

Rod,
There are quite a few changes to the original commits so I think if anyone is 
interested they should probably run some tests as well.
Cheers, Phill

 Original message From: Rod Webster  
Date: 14/12/18  12:50 pm  (GMT+10:00) To: EMC developers 
 Subject: Re: [Emc-developers] Reverse 
Run 
Phill,

I think the testing has been done and the devs tried to push it to master
but had to revert because it has been so long. So you've just caught it up.
The best one to get involved is Rene.

Maybe add some comments in the relevant commits and he might see them.

commit:
https://github.com/LinuxCNC/linuxcnc/commit/628626062188441f1dd29a8f948f190f40f47116

revert:
https://github.com/LinuxCNC/linuxcnc/commit/5a63d03110ec0f9ed92799b3f6507042894ba833

Rod Webster
+61 435 765 611
Vehicle Modifications Network
www.vehiclemods.net.au



On Fri, 14 Dec 2018 at 08:56, Phillip Carter 
wrote:

> I think that it would need a fair bit of testing from a variety of users
> which is the reason I asked what to do next.
> It appears to work fine on my sim config.
>
> Cheers, Phill.
>
> > On 12 Dec 2018, at 9:44 am, Rod Webster  wrote:
> >
> > Phil,
> >
> > I'm excited by this. Really want to get this into master! Maybe just post
> > your repo URL here and hopefully the dev team will pick it up...
> >
> > Rod Webster
> > +61 435 765 611
> > Vehicle Modifications Network
> > www.vehiclemods.net.au
> >
> >
> >
> > On Wed, 12 Dec 2018 at 16:39, Phillip Carter 
> > wrote:
> >
> >> I have managed to incorporate the commits from the
> >> feature/reverse-run-master2 branch into the current version master as
> well
> >> as fixing issue #524.
> >>
> >> It was done by cherry picking one commit at a time and running make
> after
> >> any required edits. I did find that three of the original commits were
> not
> >> needed due to later changes to tp.c
> >>
> >> I have the resultant branch on my GitHub repo and am unsure as to what I
> >> should do to make it available to others.
> >>
> >> Cheers, Phill.
> >>
> >>
> >>
> >>
> >> ___
> >> Emc-developers mailing list
> >> Emc-developers@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/emc-developers
> >>
> >
> > ___
> > Emc-developers mailing list
> > Emc-developers@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/emc-developers
>
>
>
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers
>

___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Reverse Run

[Phillip Carter]

I think that it would need a fair bit of testing from a variety of users which 
is the reason I asked what to do next.
It appears to work fine on my sim config.

Cheers, Phill.

> On 12 Dec 2018, at 9:44 am, Rod Webster  wrote:
> 
> Phil,
> 
> I'm excited by this. Really want to get this into master! Maybe just post
> your repo URL here and hopefully the dev team will pick it up...
> 
> Rod Webster
> +61 435 765 611
> Vehicle Modifications Network
> www.vehiclemods.net.au
> 
> 
> 
> On Wed, 12 Dec 2018 at 16:39, Phillip Carter 
> wrote:
> 
>> I have managed to incorporate the commits from the
>> feature/reverse-run-master2 branch into the current version master as well
>> as fixing issue #524.
>> 
>> It was done by cherry picking one commit at a time and running make after
>> any required edits. I did find that three of the original commits were not
>> needed due to later changes to tp.c
>> 
>> I have the resultant branch on my GitHub repo and am unsure as to what I
>> should do to make it available to others.
>> 
>> Cheers, Phill.
>> 
>> 
>> 
>> 
>> ___
>> Emc-developers mailing list
>> Emc-developers@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/emc-developers
>> 
> 
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

[Emc-developers] Reverse Run

[Phillip Carter]

I have managed to incorporate the commits from the feature/reverse-run-master2 
branch into the current version master as well as fixing issue #524.

It was done by cherry picking one commit at a time and running make after any 
required edits. I did find that three of the original commits were not needed 
due to later changes to tp.c

I have the resultant branch on my GitHub repo and am unsure as to what I should 
do to make it available to others.

Cheers, Phill.




___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

[Emc-developers] LinxCNC Python Module

[Phillip Carter]

Is the documentation correct for the LinuxCNC Python Module in regards 
to kinematics_type?


In the documentation for the LinuxCNC Python Interface there is 
reference to:

kinematics_type
(returns integer) - identity=1, serial=2, parallel=3, custom=4 .


in the kins manpage there is reference to:
kinstype=1 for KINEMATICS_IDENTITY (default if kinstype= omitted)
kinstype=[b|B] for KINEMATICS_BOTH
kinstype=[f|F] for KINEMATICS_FORWARD_ONLY
kinstype=[i|I] for KINEMATICS_INVERSE_ONLY


in emcmodule.cc there is reference to:
ENUM(KINEMATICS_IDENTITY);
ENUM(KINEMATICS_FORWARD_ONLY);
ENUM(KINEMATICS_INVERSE_ONLY);
ENUM(KINEMATICS_BOTH);

Cheers, Phill.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] joint mode jogging in master

[Phillip Carter]

On 16/4/17 9:17 am, Gene Heskett wrote:
> On Saturday 15 April 2017 06:29:22 Phillip Carter wrote:
>
>> I have just noticed in sim/axis/gantry that joint 3 does not jog with
>> the leftbracket/rightbracket keyboard keys but does with the
>> minus/equals keyboard keys. Is this the correct behaviour?
> I also, for lack of anything better to do, rigged up my chop saw and
> sawed off a couple hunks on 1.5" thick alu to make a new set of bearing
> pushers to fit the larger OD of the correct bearing. Fired up
> linuxcnc -l, (this after an early morning update of LinuxCNC-2.8-pre to
> LINUXCNC - 2.8.0-pre1-2988-ge9f9469) x and z are still swapped at the
> keyboard yet before being homed. Hit ctl+home, and it homed to the
> correct places, and in the correct directions and homeing order. Tapped
> the uparrow, then downarrow, and z moves left-right.  Tapped the left
> and right arrows, and x moves in and out.  Switch to MDI, and its now
> scrambled as well, as in G0X moves Z and G0Z moves X. So it appears
> Phillips commit made the keyboard scramble apply to MDI too, which means
> it cannot run code I ran on it just 2 days ago.
>
> Help! I do not have another functioning lathe now.
>
> Can you back out Phillips commit and retrigger the buildbot? It at least
> ran correctly after being homed, and I could use it, once it had been
> homed.
>
> Thanks guys.
>
> Cheers, Gene Heskett

I have just checked again with both sim/axis/lathe and 
sim/axis/historical_lathe.

Keyboard jogging before and after homing works as it should:

left/right arrows move Z and up/down arrows move X

mdi moves are also moving correctly

-- 
Cheers, Phill
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

[Emc-developers] joint mode jogging in master

[Phillip Carter]

I have just noticed in sim/axis/gantry that joint 3 does not jog with 
the leftbracket/rightbracket keyboard keys but does with the 
minus/equals keyboard keys. Is this the correct behaviour?


-- 
Cheers, Phill

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Help, after joints merge, my TLM is all miss-configured.

[Phillip Carter]

On 14/4/17 12:40 pm, Gene Heskett wrote:
> On Thursday 13 April 2017 22:33:23 Phillip Carter wrote:
>
>> On 14/4/17 12:08 pm, Gene Heskett wrote:
>>> On Thursday 23 March 2017 16:47:39 Gene Heskett wrote:
>>>
>>> There has been 3 or 4 lcnc updates since I originally posted this,
>>> but I still have the problem. The keyboards jog xz keys are still
>>> scrambled UNTIL its been homed, after which everything moves the
>>> direction it is supposed to.
>>>
>>> I've changed the order of the XZ to ZX in the ini file but it makes
>>> no difference, even if I reboot after changing it, so I've put that
>>> back to XZ in all 3 of the places in the ini file.  And I'm still
>>> puzzled.
>>>
>>> Are there any other places I should be checking?
>>>
>>> Thanks all;
>>>
>>>> Greetings guys;
>>>>
>>>> Chucking up that pulley to start making the taper boring, I found
>>>> TLM wouldn't run, throwing errors about a non-existant Y axis
>>>>
>>>> I had not run it since before the joints merge.
>>>>
>>>> 3 hours worth of checking and editing later, I can make it run but
>>>> the axis's are all weird. Pressing a left-right key runs X, and the
>>>> in-out keys run Z.
>>>>
>>>> Watching the leds on the bob, it is actually driving the wrong
>>>> axis.
>>>>
>>>> But, the DRO is showing the axis thats moving as the correct axis
>>>> for the one thats actually moving. Me confused. Bumfuzzled even.
>>>> Configs attached. Hopefully enough to run it.
>>>>
>>>> What did I miss?
>>>>
>>>> Thanks all;
>>>>
>>>> Cheers, Gene Heskett
>>> Cheers, Gene Heskett
>> I have noticed the same and am trying out some fixes at the moment.
> So I am not alone. Please post any successes. It will be appreciated.
>
> Thank you Phillip.
>
> Cheers, Gene Heskett

A commit to fix this has been merged into master.

-- 
Cheers, Phill
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Help, after joints merge, my TLM is all miss-configured.

[Phillip Carter]

On 14/4/17 12:08 pm, Gene Heskett wrote:
> On Thursday 23 March 2017 16:47:39 Gene Heskett wrote:
>
> There has been 3 or 4 lcnc updates since I originally posted this, but I
> still have the problem. The keyboards jog xz keys are still scrambled
> UNTIL its been homed, after which everything moves the direction it is
> supposed to.
>
> I've changed the order of the XZ to ZX in the ini file but it makes no
> difference, even if I reboot after changing it, so I've put that back to
> XZ in all 3 of the places in the ini file.  And I'm still puzzled.
>
> Are there any other places I should be checking?
>
> Thanks all;
>
>> Greetings guys;
>>
>> Chucking up that pulley to start making the taper boring, I found TLM
>> wouldn't run, throwing errors about a non-existant Y axis
>>
>> I had not run it since before the joints merge.
>>
>> 3 hours worth of checking and editing later, I can make it run but the
>> axis's are all weird. Pressing a left-right key runs X, and the in-out
>> keys run Z.
>>
>> Watching the leds on the bob, it is actually driving the wrong axis.
>>
>> But, the DRO is showing the axis thats moving as the correct axis for
>> the one thats actually moving. Me confused. Bumfuzzled even. Configs
>> attached. Hopefully enough to run it.
>>
>> What did I miss?
>>
>> Thanks all;
>>
>> Cheers, Gene Heskett
>
> Cheers, Gene Heskett

I have noticed the same and am trying out some fixes at the moment.

-- 
Cheers, Phill
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers