TWOPASS anomaly
31 Jul 2017 11:01 #96744
by hwylie
TWOPASS anomaly was created by hwylie
With reference to the attached files, 'POSTGUI_HALFILE = spindle_to_pyvcp.hal' fails to execute when TWOPASS is invoked in the [HAL] stanza of the INI file.
Correct postgui net creation is confirmed when TWOPASS is not invoked (but cannot be demonstrated without restructure of these files to avoid TWOPASS invocation).
Manual HAL inspection, and creation of the required two postgui nets confirms failure of postgui execution - while TWOPASS functionality for the implemented 'pre-gui' HAL files is as expected.
Another (initial) anomaly was observed when attempting to execute two postgui files as follows:
POSTGUI_HALFILE = spindle_to_pyvcp.hal
POSTGUI_HALFILE = xhc-hb04_mode_nets.hal
In this case, the first executed, but not the second (contents of 'xhc-hb04_mode_comps.hal' were incorporated in primary HAL file for purposes of the test).
Are multiple postgui files supported? Is there an error in my approach? No errors are reported, and LCNC launch appears normal until missing nets are reflected in pyvcp instrumentation dysfunction.
Further tests to identify precise conditions for postgui failure were not carried out, since the structure and modularity of actual implementation (as attached) is preferred. If required for analysis however, the scenario (including addressing any specific test conditions) can be created, and further feedback (including 'dmesg' log) provided.
Correct postgui net creation is confirmed when TWOPASS is not invoked (but cannot be demonstrated without restructure of these files to avoid TWOPASS invocation).
Manual HAL inspection, and creation of the required two postgui nets confirms failure of postgui execution - while TWOPASS functionality for the implemented 'pre-gui' HAL files is as expected.
Another (initial) anomaly was observed when attempting to execute two postgui files as follows:
POSTGUI_HALFILE = spindle_to_pyvcp.hal
POSTGUI_HALFILE = xhc-hb04_mode_nets.hal
In this case, the first executed, but not the second (contents of 'xhc-hb04_mode_comps.hal' were incorporated in primary HAL file for purposes of the test).
Are multiple postgui files supported? Is there an error in my approach? No errors are reported, and LCNC launch appears normal until missing nets are reflected in pyvcp instrumentation dysfunction.
Further tests to identify precise conditions for postgui failure were not carried out, since the structure and modularity of actual implementation (as attached) is preferred. If required for analysis however, the scenario (including addressing any specific test conditions) can be created, and further feedback (including 'dmesg' log) provided.
Please Log in or Create an account to join the conversation.
31 Jul 2017 13:21 - 31 Jul 2017 18:06 #96770
by dgarrett
Replied by dgarrett on topic TWOPASS anomaly
The handling of [HAL]POSTGUI_HALFILEs is dependent
upon the gui.
A simple test with the axis gui shows that if multiple
[HAL]POSTGUI_HALFILEs are specified, only the first one
is executed.
TWOPASS processing is gui-independent and does not
process POSTGUI_HALFILEs. To take advantage of twopass
handling for multiple loadrt commands for a given
component type, you can issue the loadrt commands prior
to gui startup. Example for the axis gui:
Documentation ref:
linuxcnc.org/docs/2.7/html/hal/twopass.html
upon the gui.
A simple test with the axis gui shows that if multiple
[HAL]POSTGUI_HALFILEs are specified, only the first one
is executed.
TWOPASS processing is gui-independent and does not
process POSTGUI_HALFILEs. To take advantage of twopass
handling for multiple loadrt commands for a given
component type, you can issue the loadrt commands prior
to gui startup. Example for the axis gui:
[HAL]
TWOPASS = verbose
HALFILE = one.hal
HALFILE = two.hal
HALFILE = loadrts_for_postgui.hal
POSTGUI_HALFILE = postgui.halDocumentation ref:
linuxcnc.org/docs/2.7/html/hal/twopass.html
Last edit: 31 Jul 2017 18:06 by dgarrett. Reason: Include Documenation reference
The following user(s) said Thank You: hwylie
Please Log in or Create an account to join the conversation.
Time to create page: 0.059 seconds