halviewer, go or no go?

Hi Chris,

How about if a sheet only knows all your halfile pins and show the route with these blocks and colors horizontally.
This pins is what you see. It are the colored boxes.

I have to think about implementation some more.

Each item you see, can be clicked. When clicked i can code that is show's related data.

Attached picture is when halview is rotated to horizontal by the rotate box.
The blue lines are all the signals of the axis gui project.
This axis gui project has 31 signals. Each signal may contain readers and writers.

It isn't showing internal component connections lines from pin to pin, they are now invisible.

You see one component is huge. It's like a tower to the moon.

Hi Grotius
Yes i forgot, some components have lots of pins.
But the idea is very nice. Makes diagnosis easier for mechanics too. They always need pictures.

Hi,

For now i have finished the program. You can download it to give it a try.

It has the watchlist :

1. The watchlist is auto saved.
2. The watchlist is loaded after program restart.
3. You can clear the watchlist.

It has a halcommand input and a halcommand verbose output.

During install it will create a desktop launcher into the system menu, and it will create a ldconfig to link the liblinuxcnchal.so.

So far as i can see it works.

Download .deb installer :
sourceforge.net/projects/halview/

Maybe drop the pins that are not connected from the viewer?

Hi Andy,

It shows the current loaded hal config. It's tested with a quite huge halconfig, the standard axis gui template.

A future plan could be using it to create hal files.

Grotius wrote: Hi Andy,

It shows the current loaded hal config. It's tested with a quite huge halconfig, the standard axis gui template.

I thought that it looked to be showing all pins of the loaded modules. I was suggesting only showing _used_ pins of loaded modules.
(Though you also want to be able to see unused pins, so you can see which ones need to be connected)