Can no longer connect to PiCar-X via WiFi or Bluetooth

Robotic kit for Raspberry Pi
1

Hi

I was briefly able to connect to PiCar-X and now I can’t. I’ve tried rebooting the PiCar-X multiple times.

This is what the log file says

ezblock version: 2.0.2

python version: 3.11.2 (main, Sep 14 2024, 03:00:30) [GCC 12.2.0]

Kernel version:
Linux picar 6.6.51+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.51-1+rpt3 (2024-10-08) aarch64 GNU/Linux

OS version:
Description: Debian GNU/Linux 12 (bookworm)

PCB info:
Revision : a020d3
Model : Raspberry Pi 3 Model B Plus Rev 1.3

25/02/17 20:45:31,099 [Entry] start >>>
25/02/17 20:45:31,099 [websokcets] Ezb_Service.start_service
25/02/17 20:45:31,100 [websokcets] user:pi
25/02/17 20:45:31,101 [websokcets] userhome:/home/pi
25/02/17 20:45:31,112 [websokcets] reset_mcu
25/02/17 20:45:31,349 [websokcets] Products type: PiCarMini
25/02/17 20:45:31,394 [websokcets] i2c_adress_list:
25/02/17 20:45:31,522 [RESET-SERVICE] stop motors
25/02/17 20:45:31,533 [RESET-SERVICE] OSError
25/02/17 20:45:31,631 [websokcets] i2c_adress_list:
25/02/17 20:45:31,867 [websokcets] i2c_adress_list:
25/02/17 20:45:32,068 [websokcets] I2C 0x14 not found
25/02/17 20:45:32,069 [websokcets] Ezb_Service.ezb_service_start
25/02/17 20:45:32,073 [websokcets] ws.user_service_start does not auto-run
25/02/17 20:45:32,076 [websokcets] ws_status_led thread start
25/02/17 20:45:32,235 [BLE] Not BLE only, changing config
25/02/17 20:45:32,671 [RESET-SERVICE] restart ezblock service
25/02/17 20:45:35,339 [RESET-SERVICE] restart ezblock service
25/02/17 20:45:38,750 [RESET-SERVICE] restart ezblock service
25/02/17 20:45:41,435 [RESET-SERVICE] restart ezblock service
25/02/17 20:45:44,082 [RESET-SERVICE] restart ezblock service
25/02/17 20:45:46,638 [RESET-SERVICE] restart ezblock service
25/02/17 20:45:49,201 [RESET-SERVICE] restart ezblock service
25/02/17 20:46:08,539 [RESET-SERVICE] restart ezblock service
25/02/17 20:46:11,149 [RESET-SERVICE] restart ezblock service
25/02/17 20:46:13,935 [RESET-SERVICE] restart ezblock service
25/02/17 20:46:17,110 [RESET-SERVICE] restart ezblock service
25/02/17 20:46:19,735 [RESET-SERVICE] restart ezblock service
25/02/17 20:46:22,464 [RESET-SERVICE] restart ezblock service
25/02/17 20:46:25,373 [RESET-SERVICE] restart ezblock service
25/02/17 20:46:28,496 [RESET-SERVICE] restart ezblock service
25/02/17 20:46:31,091 [RESET-SERVICE] restart ezblock service
25/02/17 20:46:33,720 [RESET-SERVICE] restart ezblock service
25/02/17 20:46:36,395 [RESET-SERVICE] restart ezblock service
25/02/17 20:46:39,154 [RESET-SERVICE] restart ezblock service
25/02/17 20:46:41,777 [RESET-SERVICE] restart ezblock service
25/02/17 20:46:44,397 [RESET-SERVICE] restart ezblock service
25/02/17 20:46:47,017 [RESET-SERVICE] restart ezblock service
25/02/17 20:46:50,047 [RESET-SERVICE] restart ezblock service
25/02/17 20:46:52,962 [RESET-SERVICE] restart ezblock service
25/02/17 20:46:55,904 [RESET-SERVICE] restart ezblock service
25/02/17 20:46:58,788 [RESET-SERVICE] restart ezblock service
25/02/17 20:47:01,597 [RESET-SERVICE] restart ezblock service
25/02/17 20:47:04,187 [RESET-SERVICE] restart ezblock service
25/02/17 20:47:07,009 [RESET-SERVICE] restart ezblock service
25/02/17 20:47:09,702 [RESET-SERVICE] restart ezblock service
25/02/17 20:47:12,280 [RESET-SERVICE] restart ezblock service
25/02/17 20:47:14,866 [RESET-SERVICE] restart ezblock service
25/02/17 20:47:17,690 [RESET-SERVICE] restart ezblock service
25/02/17 20:47:20,362 [RESET-SERVICE] restart ezblock service
25/02/17 20:47:23,048 [RESET-SERVICE] restart ezblock service
25/02/17 20:47:26,096 [RESET-SERVICE] restart ezblock service
25/02/17 20:47:28,918 [RESET-SERVICE] restart ezblock service
25/02/17 20:47:31,599 [RESET-SERVICE] restart ezblock service
25/02/17 20:47:34,276 [RESET-SERVICE] restart ezblock service
25/02/17 20:47:36,913 [RESET-SERVICE] restart ezblock service
25/02/17 20:47:39,639 [RESET-SERVICE] restart ezblock service
25/02/17 20:47:42,633 [RESET-SERVICE] restart ezblock service
25/02/17 20:47:45,197 [RESET-SERVICE] restart ezblock service
25/02/17 20:47:47,830 [RESET-SERVICE] restart ezblock service
25/02/17 20:47:50,461 [RESET-SERVICE] restart ezblock service
25/02/17 20:47:53,070 [RESET-SERVICE] restart ezblock service
25/02/17 20:47:55,931 [RESET-SERVICE] restart ezblock service
25/02/17 20:47:58,487 [RESET-SERVICE] restart ezblock service
25/02/17 20:48:01,269 [RESET-SERVICE] restart ezblock service

2

I found out those errors were because I was rebooting the PiCar.

Now when I shutdown the PiCar I get

------------------------25/02/17 21:08:49------------------------
ezblock version: 2.0.2

python version: 3.11.2 (main, Sep 14 2024, 03:00:30) [GCC 12.2.0]

Kernel version:
Linux PiCarMini 6.6.51+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.51-1+rpt3 (2024-10-08) aarch64 GNU/Linux

OS version:
Description: Debian GNU/Linux 12 (bookworm)

PCB info:
Revision : a020d3
Model : Raspberry Pi 3 Model B Plus Rev 1.3

25/02/17 21:08:59,372 [Entry] start >>>
25/02/17 21:08:59,373 [websokcets] Ezb_Service.start_service
25/02/17 21:08:59,374 [websokcets] user:pi
25/02/17 21:08:59,375 [websokcets] userhome:/home/pi
25/02/17 21:08:59,396 [websokcets] reset_mcu
25/02/17 21:08:59,644 [websokcets] Products type: PiCarMini
25/02/17 21:08:59,806 [RESET-SERVICE] stop motors
25/02/17 21:09:01,705 [RESET-SERVICE] OSError

3

25/02/17 21:11:50,043 [websokcets] i2c_adress_list:
25/02/17 21:13:44,923 [websokcets] i2c_adress_list:

4

Ok, I’m able to connect with BlueTooth and WiFi…sometimes.

If there is any kind of error the device disconnects and I can’t connect again.

#!/usr/bin/python3
from ezblock import Remote
from picarx import PiCarX
px = PiCarX()
from ezblock import mapping

RM_OBJECT = Remote()

def forever():
px.forward(RM_OBJECT.get_joystick_value(“A”, “Y”))
px.set_steering_angle((mapping(RM_OBJECT.get_joystick_value(“A”, “X”), (-100), 100, (-45), 45)))

25/02/17 21:33:46,224 [websokcets] [Process] user_service_start: 34293
25/02/17 21:33:47,290 [websokcets] reset_mcu
25/02/17 21:33:47,525 [websokcets] Products type: PiCarMini
25/02/17 21:33:54,894 [websokcets] recv “ST”
25/02/17 21:33:54,930 [websokcets] [Process] kill user_service_child_process, pid: 34342
25/02/17 21:33:54,931 [websokcets] [Process] kill user_service_main_process, pid: 34293
25/02/17 21:33:54,931 [websokcets] reset_mcu
25/02/17 21:33:55,166 [websokcets] Products type: PiCarMini
25/02/17 21:35:35,481 [BLE] ble properties_changed: 1
25/02/17 21:35:50,396 [websokcets] i2c_adress_list:

5

Suggest to provide the problem video to us, so that we can help you analyze the problem.
What brand of cell phone or tablet are you currently using, and what is the system version, so that we can reproduce the problem.
If you are using an iPhone or iPad:
If you can’t search and connect to the bluetooth information, we suggest you go to the bluetooth settings of your cell phone, ignore the bluetooth devices that have been successfully connected, and then go to the APP again to connect and see how it works.

6

I’m not sure why/how to send you a video of it losing connection? It loses connection

I am using an Android phone, Pixel 7.

Did you see the log file snippets I pasted?

Update: If I wait long enough the connection resets

25/02/17 23:13:40,489 [websokcets] [Process] user_service_start: 5186
25/02/17 23:13:42,518 [websokcets] reset_mcu
25/02/17 23:13:42,757 [websokcets] Products type: PiCarMini
25/02/17 23:13:58,555 [websokcets] recv “ST”
25/02/17 23:13:58,590 [websokcets] [Process] kill user_service_child_process, pid: 5263
25/02/17 23:13:58,590 [websokcets] [Process] kill user_service_main_process, pid: 5186
25/02/17 23:13:58,591 [websokcets] reset_mcu
25/02/17 23:13:58,827 [websokcets] Products type: PiCarMini
25/02/17 23:15:53,816 [websokcets] i2c_adress_list:
25/02/17 23:17:48,696 [websokcets] i2c_adress_list:
25/02/17 23:19:43,580 [websokcets] i2c_adress_list:
25/02/17 23:19:43,781 [websokcets] I2C 0x14 not found
25/02/17 23:19:43,795 [websokcets] [Process] start ws_battery_process, pid: 16361
25/02/17 23:19:43,824 [websokcets] client connected
25/02/17 23:19:43,828 [websokcets] disconnected:no close frame received or sent
25/02/17 23:19:43,833 [websokcets] client disconnected
25/02/17 23:19:43,834 [websokcets] ---------------------------------------------
25/02/17 23:19:44,139 [websokcets] disconnected:no close frame received or sent
25/02/17 23:19:44,150 [websokcets] client disconnected
25/02/17 23:19:44,151 [websokcets] ---------------------------------------------