ADMIN LOGLEVEL 0 1

How can I get  to use ADMIN LOGLEVEL 0 1  in PP 2.0

I have been asked to run this in the MDI

On v2.8.1 typing ADMIN LOGLEVEL in the MDI box show the current loglevels on the status page.

Typing ADMIN LOGLEVEL 0 1 reports linuxcnc loglevel changed to 0, hal loglevel changed to 1.

Also tried a few other values.

Same info is written to ~/gcode/pathpilotlog.txt, here's the relevant part with the time stamps removed:

Ken.

rafferty wrote:

On v2.8.1 typing ADMIN LOGLEVEL in the MDI box show the current loglevels on the status page.

Typing ADMIN LOGLEVEL 0 1 reports linuxcnc loglevel changed to 0, hal loglevel changed to 1.

Also tried a few other values.

Same info is written to ~/gcode/pathpilotlog.txt, here's the relevant part with the time stamps removed:

ADMIN LOGLEVEL [/home/operator/v2.8.1/python/ui_common.py:3737]
Current ADMIN LOGLEVEL for linuxcnc = 0x0 [/home/operator/v2.8.1/python/admincmd.py:994]
Switched to notebook page: alarms_fixed [/home/operator/v2.8.1/python/ui_common.py:6816]
Current ADMIN LOGLEVEL for hal = 0x0 [/home/operator/v2.8.1/python/admincmd.py:995]
Switched to notebook page: notebook_main_fixed [/home/operator/v2.8.1/python/ui_common.py:6816]
Switched to notebook page: alarms_fixed [/home/operator/v2.8.1/python/ui_common.py:6816]
Switched to notebook page: notebook_main_fixed [/home/operator/v2.8.1/python/ui_common.py:6816]
ADMIN LOGLEVEL 0 1 [/home/operator/v2.8.1/python/ui_common.py:3737]
ADMIN LOGLEVEL changed linuxcnc level from 0x0 to 0x0 [/home/operator/v2.8.1/python/admincmd.py:1016]
Switched to notebook page: alarms_fixed [/home/operator/v2.8.1/python/ui_common.py:6816]
ADMIN LOGLEVEL changed hal level from 0x0 to 0x1 [/home/operator/v2.8.1/python/admincmd.py:1017]
Switched to notebook page: notebook_main_fixed [/home/operator/v2.8.1/python/ui_common.py:6816]
Must take machine out of estop before jogging. [tormach_mill_ui.py:4348]
Switched to notebook page: alarms_fixed [/home/operator/v2.8.1/python/ui_common.py:6816]
Switched to notebook page: notebook_main_fixed [/home/operator/v2.8.1/python/ui_common.py:6816]
ADMIN LOGLEVEL 0 6 [/home/operator/v2.8.1/python/ui_common.py:3737]
ADMIN LOGLEVEL changed linuxcnc level from 0x0 to 0x0 [/home/operator/v2.8.1/python/admincmd.py:1016]
Switched to notebook page: alarms_fixed [/home/operator/v2.8.1/python/ui_common.py:6816]
ADMIN LOGLEVEL changed hal level from 0x1 to 0x6 [/home/operator/v2.8.1/python/admincmd.py:1017]
Switched to notebook page: notebook_main_fixed [/home/operator/v2.8.1/python/ui_common.py:6816]
ADMIN LOGLEVEL 0X3 [/home/operator/v2.8.1/python/ui_common.py:3737]
Unrecognized ADMIN LOGLEVEL command. Try
    ADMIN LOGLEVEL [value] [value]
where [value] is a hexadecimal value. [/home/operator/v2.8.1/python/admincmd.py:1021]
Switched to notebook page: alarms_fixed [/home/operator/v2.8.1/python/ui_common.py:6816]
Switched to notebook page: notebook_main_fixed [/home/operator/v2.8.1/python/ui_common.py:6816]
ADMIN LOGLEVEL 1 8 [/home/operator/v2.8.1/python/ui_common.py:3737]
ADMIN LOGLEVEL changed linuxcnc level from 0x0 to 0x1 [/home/operator/v2.8.1/python/admincmd.py:1016]
Switched to notebook page: alarms_fixed [/home/operator/v2.8.1/python/ui_common.py:6816]
ADMIN LOGLEVEL changed hal level from 0x6 to 0x8 [/home/operator/v2.8.1/python/admincmd.py:1017]


Ken.

Thanks for the reply.
My problem is that Pathpilot V 2 (on my system) does not accept the command ADMIN LOGLEVEL 0 1 in the MDI

OK, didn't realise V2 was literal.

Looking at admincmd.py, the ADMIN LOGLEVEL command arguments set debug levels, first is for linuxcnc, second if for HAL. Can't see how the linuxcnc argument is used (my python skills are woeful) but the second one I can follow.  

In my 2.8.1 setup there is a HAL pin "tormach.debug-level", a u32. The second argument, a 1 in your case (can be any hex value) is written to this pin. I've verified this with halshow.

If this pin exists in your path pilotversion, you should be able to get the equivalent of ADMIN LOGLEVEL 0 1 (at least the 1 part) by manipulating the pin with halcmd, 

In my setup the pin connects to zbotatc.debug-level and zbotschnozz.debug-level.