These are chat archives for machinekit/machinekit

16th
Jun 2016
Michael Haberler
@mhaberler
Jun 16 2016 09:58
Differential between what? No
zhivko
@zhivko
Jun 16 2016 10:09
OK... I need to create remote component with single pin...
zhivko
@zhivko
Jun 16 2016 10:22
Doing some more intensive testing with BBB and machinekit last days - there were few times when BBB kind of freeze, any sugestion what log to check to find out the reason?
Michael Haberler
@mhaberler
Jun 16 2016 14:32
the SUB vs XSUB might be an oversight by Alex
use an XSUB and send the subscribe message like in hal_glib
zhivko
@zhivko
Jun 16 2016 14:33
Using: XSUB for remotecomponent I am getting:
subscription flag
    at zmq.XSub.xsend(XSub.java:136)
    at zmq.SocketBase.send(SocketBase.java:641)
    at org.zeromq.ZMQ$Socket.send(ZMQ.java:1302)
    at com.kz.pipeCutter.BBB.BBBHalRComp.run(BBBHalRComp.java:97)
    at java.lang.Thread.run(Thread.java:745)
Michael Haberler
@mhaberler
Jun 16 2016 14:34
well maybe the java bindings do not support that, no wonder
zhivko
@zhivko
Jun 16 2016 14:34
hmm.. need to go now - I will research: https://github.com/machinekit/machinekit/blob/master/lib/python/hal_glib.py#L87-L587 further later...
Michael Haberler
@mhaberler
Jun 16 2016 14:34
but I cannot tell
zhivko
@zhivko
Jun 16 2016 14:34
maybe advice on frozen BBB ?
What can I look - I mean what log ?
Michael Haberler
@mhaberler
Jun 16 2016 14:34
put in oven
zhivko
@zhivko
Jun 16 2016 14:35
or better - if it happens again ? :) hehe
Michael Haberler
@mhaberler
Jun 16 2016 14:35
do you have a console serial connected
zhivko
@zhivko
Jun 16 2016 14:35
usb on BBB is very lame
sometimes work sometimes not
Michael Haberler
@mhaberler
Jun 16 2016 14:35
that is not the question
I said "serial" not "USB"
do you have a serial console connected
zhivko
@zhivko
Jun 16 2016 14:36
what happens - I power it from usb when that happened - ssh console was opened at that time but over IP not over serial...
Michael Haberler
@mhaberler
Jun 16 2016 14:36
jeepers NO I am not talking about a login line, I am talking about the CONSOLE LINE
zhivko
@zhivko
Jun 16 2016 14:37
you mean serial console like putty on /dev/ttyASM0 ?
Michael Haberler
@mhaberler
Jun 16 2016 14:37
YES
zhivko
@zhivko
Jun 16 2016 14:37
Thanks for sharing link
Michael Haberler
@mhaberler
Jun 16 2016 14:37
you definitely want one, without one tracking issues with the kernel is next to impossible
zhivko
@zhivko
Jun 16 2016 14:37
YES i have this extra cable
Michael Haberler
@mhaberler
Jun 16 2016 14:38
excellent. Go use it.
zhivko
@zhivko
Jun 16 2016 14:38
And yes I could use this at the time when this happens but that serial cable was not at the hand at that time....
briliant! thank you
really ened to go now... later!
Michael Haberler
@mhaberler
Jun 16 2016 15:04
in case you get around to it - a backtrace from the FAST crash would be great
zhivko
@zhivko
Jun 16 2016 16:42
yes here is backtrace:
Program received signal SIGSEGV, Segmentation fault.
0xb6a17556 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
(gdb) backtrace
#0  0xb6a17556 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
#1  0xb6a1a1ca in free () from /lib/arm-linux-gnueabihf/libc.so.6
#2  0x00000000 in ?? ()
Is it OK or you need some additional info ?
doesn't say much for my taste
hmm i am not sure... this is strange
zhivko
@zhivko
Jun 16 2016 16:49
ignore my previous backtrace
here is right one
(gdb) continue
Continuing.

Program received signal SIGSEGV, Segmentation fault.
halpr_describe_funct (funct=0xb6790e08, pbfunct=0xea0e8) at hal/lib/halpb.cc:97
97        pbfunct->set_runtime(*(funct->runtime));
(gdb) backtrace
#0  halpr_describe_funct (funct=0xb6790e08, pbfunct=0xea0e8) at hal/lib/halpb.cc:97
#1  0x0000fe26 in describe_funct_cb (funct=0xb6790e08, arg=0xbeff25d8)
    at machinetalk/haltalk/haltalk_introspect.cc:129
#2  0xb6dc546c in halpr_foreach_funct (name=0x0, 
    callback=0xfde1 <describe_funct_cb(hal_funct_t*, void*)>, cb_data=0xbeff25d8)
    at hal/lib/hal_iter.c:155
#3  0x0000ff42 in process_describe (self=0xbeff25d8, from=0x2fbf0, socket=0x32f80)
    at machinetalk/haltalk/haltalk_introspect.cc:44
#4  0x0000eff4 in dispatch_request (socket=0x32f80, from=0x2fbf0, self=0xbeff25d8)
    at machinetalk/haltalk/haltalk_command.cc:481
#5  handle_command_input (loop=<optimized out>, poller=<optimized out>, arg=0xbeff25d8)
    at machinetalk/haltalk/haltalk_command.cc:60
#6  0xb6c2ce50 in zloop_start () from /usr/lib/arm-linux-gnueabihf/libczmq.so.1
#7  0x0000b980 in mainloop (self=0xbeff25d8) at machinetalk/haltalk/haltalk_main.cc:113
#8  main (argc=3, argv=<optimized out>) at machinetalk/haltalk/haltalk_main.cc:467
do you need me to open issue for this ?
zhivko
@zhivko
Jun 16 2016 17:42
I am reading: https://github.com/mhaberler/asciidoc-sandbox/wiki/Remote-HAL-Components
A lot of details explained at the end of document about communication flow...
Michael Haberler
@mhaberler
Jun 16 2016 23:08
I do not think this backtrace is from by branch