Re: [Emc-developers] Graphical HAL Viewer-Editor

On Monday 05 December 2016 19:55:26 andy pugh wrote: > On 5 December 2016 at 19:58, Gene Heskett wrote: > > When I am carving up a new control function in hal, its somewhat of > > a nuisance to stop and consult the man page for an and, or, xor, > > mul2, mux2 or similar

Re: [Emc-developers] Graphical HAL Viewer-Editor

On 5 December 2016 at 19:58, Gene Heskett wrote: > When I am carving up a new control function in hal, its somewhat of a > nuisance to stop and consult the man page for an and, or, xor, mul2, > mux2 or similar small module to find out if the first input is .in0 > or .in1.

Re: [Emc-developers] Graphical HAL Viewer-Editor

On Monday 05 December 2016 15:06:34 Nicklas Karlsson wrote: > It is quite common for schematic capture software to have the concept > of pin swap, could this be a path forward? > > Otherwise I probably did not get what you are talking about. > > > Would it be a huge job to scan thru the module

Re: [Emc-developers] Graphical HAL Viewer-Editor

On Monday 05 December 2016 12:57:14 andy pugh wrote: > On 5 December 2016 at 17:29, Jim Craig wrote: > > There is too much variation in wording in the man > > pages also. > > There shouldn't be _that_ much as the ones for anything written as a > .comp are all

Re: [Emc-developers] Graphical HAL Viewer-Editor

On 12/5/2016 8:55 AM, andy pugh wrote: > > You can often (but not always) determine the sub-component count by > looking at the number of commas or spaces in the config string. (this > is moderately safe as the RTAPI_MP_ARRAY macros always break on commas > or spaces. > OK, So based on the above,

Re: [Emc-developers] Graphical HAL Viewer-Editor

Thanks Dewey, I will figure out how to implement this in my program. Jim On 12/5/2016 9:55 AM, Dewey Garrett wrote: >> I think this system library is located at /usr/share/linuxcnc/hallib > This is accurate for current deb installs but is different for > Run-In-Place (RIP) users. > > The

Re: [Emc-developers] Graphical HAL Viewer-Editor

> I think this system library is located at /usr/share/linuxcnc/hallib This is accurate for current deb installs but is different for Run-In-Place (RIP) users. The scripts/linuxcnc.in file (creates the linuxcnc script at make time) expands: HALLIB_DIR=@HALLIB_DIR@; export HALLIB_DIR The value

Re: [Emc-developers] Graphical HAL Viewer-Editor

On 5 December 2016 at 14:29, Jim Craig wrote: > However looking over some of > the components. number= and names= are not always present and other > loadrt variables determine the quantity and names of subcomponents. What > do you all think is the best method? I

Re: [Emc-developers] Graphical HAL Viewer-Editor

I am working on the code that reads HAL files directly. I am using this to get the loadrt statements so that I can split the components into the subcomponents. What do you all think is the best method for determining sub components? My first thought was to read the loadrt statements and get

Re: [Emc-developers] Graphical HAL Viewer-Editor

On 11/25/2016 9:49 AM, andy pugh wrote: > On 25 November 2016 at 15:30, John Kasunich wrote: >> As you and others pointed out, font sizes quickly become a problem. > CAD programs tend to display dimensions at the same font size > regardless of zoom level, though I doubt

Re: [Emc-developers] Graphical HAL Viewer-Editor

On 11/25/2016 9:30 AM, John Kasunich wrote: > This looks like a great start. I've wanted something like this since > pretty much day 1 of HAL. But I never tackled it because I'm definitely > not a GUI programmer. (Halscope about killed me, thankfully others > made it into the nice tool it is

Re: [Emc-developers] Graphical HAL Viewer-Editor

On Fri, Nov 25, 2016, at 11:04 AM, Gene Heskett wrote: > On Friday 25 November 2016 10:30:35 John Kasunich wrote: > > > Part 2 - many if not most pin names start with the instance name. > > For example, component "or2_0" has pins named "or2_0.in0", > > "or2_0.in1", and "or2_0.out". Part 1

Re: [Emc-developers] Graphical HAL Viewer-Editor

On Friday 25 November 2016 10:30:35 John Kasunich wrote: > This looks like a great start. I've wanted something like this since > pretty much day 1 of HAL. But I never tackled it because I'm > definitely not a GUI programmer. (Halscope about killed me, > thankfully others made it into the nice

Re: [Emc-developers] Graphical HAL Viewer-Editor

On 25 November 2016 at 15:30, John Kasunich wrote: > As you and others pointed out, font sizes quickly become a problem. CAD programs tend to display dimensions at the same font size regardless of zoom level, though I doubt that would work here. Perhaps the answer here

Re: [Emc-developers] Graphical HAL Viewer-Editor

This looks like a great start. I've wanted something like this since pretty much day 1 of HAL. But I never tackled it because I'm definitely not a GUI programmer. (Halscope about killed me, thankfully others made it into the nice tool it is today.) Some comments: As you and others pointed

Re: [Emc-developers] Graphical HAL Viewer-Editor

On 11/24/2016 9:04 PM, TJoseph Powderly wrote: > wow, great Jim > if you want > i will test by trying to draw the hal files supplied with standard > linuxcnc distro That would be great. I will need some willing testers. > > also > how will you connect to a thread? > handle parameters & functions >

Re: [Emc-developers] Graphical HAL Viewer-Editor

On 11/24/2016 11:37 AM, TJoseph Powderly wrote > i find myself zooming and panning between different areas a lot > and opting to use an intermediate value of zoom where the text is barely > legible, just so i get a larger scope This is an issue with this type of schematic. It is a balancing act of

Re: [Emc-developers] Graphical HAL Viewer-Editor

Jim very interesting the first thing i did with the pdf is to try to understand what it represented i find myself zooming and panning between different areas a lot and opting to use an intermediate value of zoom where the text is barely legible, just so i get a larger scope i ran into the same

Re: [Emc-developers] Graphical HAL Viewer-Editor

On 11/24/2016 09:08 AM, Jim Craig wrote: > Progress report. I have the graphics area drawing, panning > and zooming how I like it. Currently I am just drawing the > entire active configuration on a single design sheet. I > plan on keeping this overall design sheet for the final > application.

Re: [Emc-developers] Graphical HAL Viewer-Editor

On Thursday 24 November 2016 10:08:42 Jim Craig wrote: > Progress report. I have the graphics area drawing, panning and zooming > how I like it. Currently I am just drawing the entire active > configuration on a single design sheet. I plan on keeping this overall > design sheet for the final

Re: [Emc-developers] Graphical HAL Viewer-Editor

Progress report. I have the graphics area drawing, panning and zooming how I like it. Currently I am just drawing the entire active configuration on a single design sheet. I plan on keeping this overall design sheet for the final application. It gives a good overview of the entire

Re: [Emc-developers] Graphical HAL Viewer-Editor

On 11/16/2016 6:54 AM, Jeff Epler wrote: > On Wed, Nov 16, 2016 at 06:13:35AM -0600, Jim Craig wrote: >> If I develop this application around the python-pygoocanvas package can >> we modify the standard linuxcnc distribution to include this package by >> default? If so I will continue and modify

Re: [Emc-developers] Graphical HAL Viewer-Editor

On Wed, Nov 16, 2016 at 06:13:35AM -0600, Jim Craig wrote: > If I develop this application around the python-pygoocanvas package can > we modify the standard linuxcnc distribution to include this package by > default? If so I will continue and modify the code to use this new > canvas for the

Re: [Emc-developers] Graphical HAL Viewer-Editor

Hello all, I have been working on this project slowly. I am still working based on the crapahalic program however it is becoming less and less of what I am using at the time being. My latest setback is when scaling the gnomecanvas so that the display has a zoom capability everything scales

Re: [Emc-developers] Graphical HAL Viewer-Editor

i did not know of Xcos, thanks Andy tomp -- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and

Re: [Emc-developers] Graphical HAL Viewer-Editor

> > On 30 October 2016 at 14:47, Jim Craig wrote: > >> Since the current functionality reads a running configuration, I would > >> like to be able to read the .ini file that is currently loaded to get > >> access to the .hal files that make up the current running

Re: [Emc-developers] Graphical HAL Viewer-Editor

On 10/31/2016 8:26 AM, andy pugh wrote: > On 31 October 2016 at 13:11, Jim Craig wrote: >> Is there any way to determine what the current .ini file is for the >> running configuration? > It may be exported as an environment variable >

Re: [Emc-developers] Graphical HAL Viewer-Editor

On 31 October 2016 at 13:11, Jim Craig wrote: > Is there any way to determine what the current .ini file is for the > running configuration? It may be exported as an environment variable https://github.com/LinuxCNC/linuxcnc/blob/master/scripts/linuxcnc.in#L726 Once

Re: [Emc-developers] Graphical HAL Viewer-Editor

On 10/31/2016 7:47 AM, andy pugh wrote: > On 30 October 2016 at 14:47, Jim Craig wrote: >> Since the current functionality reads a running configuration, I would >> like to be able to read the .ini file that is currently loaded to get >> access to the .hal files that

Re: [Emc-developers] Graphical HAL Viewer-Editor

On 30 October 2016 at 14:47, Jim Craig wrote: > Since the current functionality reads a running configuration, I would > like to be able to read the .ini file that is currently loaded to get > access to the .hal files that make up the current running configuration. I

Re: [Emc-developers] Graphical HAL Viewer-Editor

> I would like to use the halcmd save command to save the current .hal > file, but I don't think this is going to work if there is a postgui.hal > file. Using this command with a running configuration makes sure the > syntax is correct without having to write a bunch of additional code to > write

Re: [Emc-developers] Graphical HAL Viewer-Editor

On Fri, Oct 28, 2016, at 01:31 PM, andy pugh wrote: > Perhaps the trick is for you to not load the HAL file, but for you > code to parse the HAL file. Yes! > You can fairly readily "loadrt" each component using the parameters > from the HAL file, make a note of the pins, then "unloadrt" it.

Re: [Emc-developers] Graphical HAL Viewer-Editor

On 28 October 2016 at 15:29, Jim Craig wrote: > What is your opinion of this general method of working with a running > HAL configuration? The only drawback that I see at the moment is that it > would make editing a broken configuration with the tool impossible as it

Re: [Emc-developers] Graphical HAL Viewer-Editor

On Fri, Oct 28, 2016, at 11:26 AM, Jim Craig wrote: > On 10/28/2016 10:02 AM, John Kasunich wrote: > > > > On Fri, Oct 28, 2016, at 10:29 AM, Jim Craig wrote: > No, it is not using the -s option. However it does not appear that it > will fix the issue either. Below is a snippet of the component

Re: [Emc-developers] Graphical HAL Viewer-Editor

On 10/28/2016 10:02 AM, John Kasunich wrote: > > On Fri, Oct 28, 2016, at 10:29 AM, Jim Craig wrote: >> I did some more debugging of Crapahalic last night. So some brief >> overview of how it works so far. It uses halcmd show to generate output >> that is then parsed through to determine the

Re: [Emc-developers] Graphical HAL Viewer-Editor

On Fri, Oct 28, 2016, at 10:29 AM, Jim Craig wrote: > I did some more debugging of Crapahalic last night. So some brief > overview of how it works so far. It uses halcmd show to generate output > that is then parsed through to determine the loaded hal components, the > pins for each component

Re: [Emc-developers] Graphical HAL Viewer-Editor

On Fri, Oct 28, 2016 at 09:29:29AM -0500, Jim Craig wrote: > What is your opinion of this general method of working with a running > HAL configuration? I think using experimental loading of a hal component after the user provides the arguments (to see what pins and parameters it presents) is a

Re: [Emc-developers] Graphical HAL Viewer-Editor

I did some more debugging of Crapahalic last night. So some brief overview of how it works so far. It uses halcmd show to generate output that is then parsed through to determine the loaded hal components, the pins for each component and the signals that are all loaded in the current

Re: [Emc-developers] Graphical HAL Viewer-Editor

On 10/27/2016 05:23 PM, Jim Craig wrote: > I am trying to get Crapaholic to run. I have found the first issue and > was able to get it to run and "show" the running hal confguration. There > are some pretty major bugs as things have changed somewhat over the last > 11 years. Is there a good python

Re: [Emc-developers] Graphical HAL Viewer-Editor

I am trying to get Crapaholic to run. I have found the first issue and was able to get it to run and "show" the running hal confguration. There are some pretty major bugs as things have changed somewhat over the last 11 years. Is there a good python debugger that you all recommend. I would

Re: [Emc-developers] Graphical HAL Viewer-Editor

On 10/27/2016 8:43 AM, Sebastian Kuzminsky wrote: > On 10/27/2016 02:47 AM, andy pugh wrote: >> On 27 October 2016 at 01:59, Jeff Epler wrote: >>> I'm totally open to 'comp' gaining a new output format that describes the >>> component. that beats parsing manpage markup by