Nicolas Schodet

From the firmware, you have access to system command and direct command. There is no command for the LCD screen. However, you have access to the “IOMAPs”, have a look...

Do you have more details? What’s your program? What parameters did you use? Does `bluetoothctl` manage to see the brick? Can you run `nxt_test --log-level=debug`?

Does your address starts with 00:16:53? Make sure there is no NXT-Python program still running in the background (reboot if not sure). Here is what I do to make it...

There is an open ticket about this: https://github.com/pybluez/pybluez/issues/473 Could you do this test, replacing the address with your NXT address: ``` strace nxt_test --host 00:16:53:AA:BB:CC ``` Thanks.

There is another option, using the devfile backend: ``` nicolas@boktor:~/work/lego/nxt-python% sudo rfcomm bind 0 00:16:53:AA:BB:CC [sudo] password for nicolas: nicolas@boktor:~/work/lego/nxt-python% ls /dev/rfcomm0 /dev/rfcomm0 nicolas@boktor:~/work/lego/nxt-python% nxt_test --backend devfile Find brick... NXT...

Locking at the strace output, the connection failed with EACCES (Permission denied)… so there is something forbidding the connection. You can try with the btsocket branch (see #199), but I...

Actually, on https://github.com/pybluez/pybluez/issues/473, the reporter said that it works using direct sockets, so testing with the btsocket branch could be interesting too. Thanks.

@Zackariyya could you look at Fedora log files to see if there is some useful information there? Did you had the opportunity to try the btsocket branch?

OK, closing.

The NXT is using Bluetooth classic, not BLE. QT might be an option, would you like to try it?