where are the f*ng rtapi_print_msg(RTAPI_MSG_INFO, -messages?

Start
Prev
1
Next
End

wicki
Topic Author
Offline
Elite Member

27 Jan 2019 09:32 - 27 Jan 2019 09:32 #124952 by wicki

where are the f*ng rtapi_print_msg(RTAPI_MSG_INFO, -messages? was created by wicki

I remember, that I have always been bothered by these missing messages :-(

even if I set

DEBUG = 0xFFFFFFFF

there is NOTHING.
not on the screen, not in the terminal, not in the logs (pring, debug, dmesg)

what's the problem with it?

if the messages don't appear, why just send them to /dev/null an deletethis stupid
RTAPI_MSG_INFO from the docs?

the solution from 2012 (this forum) may help - but it is not really a solution

Consequently I use rtapi_print_msg(RTAPI_MSG_ERR, " .........."); for debugging, even for none errors.
It displays to Axis and in the terminal.

Last edit: 27 Jan 2019 09:32 by wicki.

Please Log in or Create an account to join the conversation.

andypugh
Offline
Moderator

29 Jan 2019 17:27 - 29 Jan 2019 17:27 #125181 by andypugh

Replied by andypugh on topic where are the f*ng rtapi_print_msg(RTAPI_MSG_INFO, -messages?

The rtapi messaging level is not controlled by the DEBUG= INI entry. It is a separate mask.

It used to be the case that you could set it (by the rather Byzantine method of)

echo 6 > /proc/trapi/debug

But I think that no longer works.
sourceforge.net/p/emc/mailman/emc-develo...priv.at/#msg30532123

Here is a suggestion, a little custom component. (untested)

component set_message_level;
param rw level
;;
static int last_level = 0
if (last_level != level){
    rtapi_set_msg_level(level)
}

You can loadrt this, then setp it in your HAL file, or from the halcmd prompt while the system is running.

Last edit: 29 Jan 2019 17:27 by andypugh.

Please Log in or Create an account to join the conversation.

wicki
Topic Author
Offline
Elite Member

30 Jan 2019 17:28 #125312 by wicki

Replied by wicki on topic where are the f*ng rtapi_print_msg(RTAPI_MSG_INFO, -messages?

andypugh wrote:
The rtapi messaging level is not controlled by the DEBUG= INI entry. It is a separate mask.

It used to be the case that you could set [....]
You can loadrt this, then setp it in your HAL file, or from the halcmd prompt while the system is running.

that's the hint! thx

in the original-driver is a
rtapi_set_msg_level(RTAPI_MSG_WARN);

thatś the reason why no info-messages are shown.....

Please Log in or Create an account to join the conversation.

Start
Prev
1
Next
End

Time to create page: 0.104 seconds