Bed Level Visualizer Plug-In does not probe

I installed the Bed Level Visualizer Plugin and I copied the Bilinear bed code G-Code and pasted the code into the GCODE MESH UPDATE PROCESS. I hear the double beep while the mesh update is processing but the BLTouch will not probe the bed. The mesh update process ends and I see a visual display BUT the display is my ORIGINAL mesh info. In addition, I do see the bed temperature rising. If I recall, the bed temp gets close but does not reach 60c. My firmware on by Ender 3v2 clone (Voxelab Aquila) is MRiscoC ProUI-EX 2.1.3g-4

What did you already try to solve it?
I changed the Baud speed from Auto to the fastes speed and at 25000 I was UNABLE to connect. I set the baud rate to 115200 and was able to connect.

Have you tried running in safe mode?
YES

Did running in safe mode solve the problem?
No, Bed Visualizer plugin is not avaialble for use in Safe Mode

Systeminfo Bundle
browser.user_agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/18.6 Safari/605.1.15
connectivity.connection_check: 1.1.1.1:53
connectivity.connection_ok: True
connectivity.enabled: True
connectivity.online: True
connectivity.resolution_check: octoprint.org
connectivity.resolution_ok: True
env.hardware.cores: 4
env.hardware.freq: 1800.0
env.hardware.ram: 1906548736
env.os.bits: 32
env.os.id: linux
env.os.platform: Linux-6.6.51+rpt-rpi-v7l-armv7l-with-glibc2.36
env.plugins.pi_support.model: Raspberry Pi 4 Model B Rev 1.5
env.plugins.pi_support.octopi_camera_stack: webcamd
env.plugins.pi_support.octopi_version: 1.1.0
env.plugins.pi_support.octopiuptodate_build: 1.1.0-1.11.3-20250909113029
env.plugins.pi_support.octopiuptodate_build_short: 2025.09.09.113029
env.plugins.pi_support.throttle_check_enabled: True
env.plugins.pi_support.throttle_check_functional: True
env.plugins.pi_support.throttle_state: 0x0
env.python.pip: 25.0.1
env.python.version: 3.11.2
env.python.virtualenv: True
octoprint.last_safe_mode.date: 2025-09-20T22:28:49Z
octoprint.last_safe_mode.reason: settings
octoprint.safe_mode: False
octoprint.version: 1.11.3
systeminfo.generated: 2025-09-20T22:35:56Z
systeminfo.generator: zipapi

Additional information about your setup

Version 1.11.3
Browser is Safari
Mac OS v15.6.1
Voxelab Aquila (Ender 3V2 clone)
MRiscoC ProUI-EX 2.1.3g-4 is firmware on printer

This firmware uses UBL if I'm not mistaken. You should update the plugin's settings to use the gcode from that example instead of bilinear.

I will. I also read on the firmware forum @ Octoprint · classicrocker883/MRiscoCProUI Wiki · GitHub
I need to set the baud rate at 250000. For some reason I cannot connect my printer at this baud rate. I can only connect at 115200. I also tried to connect at 250000 with Pronterface and unable to connect at this baud rate. I ordered a new micro USB cable to connect my Pi 4 and printer. I also disabled with tape the +5 volt on my current micro USB cable. I will change the G code as suggesteda and try again.

Here is some info from the serial log file:

025-09-21 03:42:23,798 - Connection closed, closing down monitor
2025-09-21 03:42:23,804 - Changing monitoring state from "Operational" to "Offline"
2025-09-21 03:42:33,835 - Changing monitoring state from "Offline" to "Opening serial connection"
2025-09-21 03:42:33,837 - Connecting to port /dev/ttyUSB0, baudrate 250000
2025-09-21 03:42:33,869 - Changing monitoring state from "Opening serial connection" to "Connecting"
2025-09-21 03:42:33,870 - Connected to: Serial<id=0xaa1e7d90, open=True>(port='/dev/ttyUSB0', baudrate=250000, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
2025-09-21 03:42:33,873 - Send: N0 M110 N0125
2025-09-21 03:43:07,213 - No answer from the printer within the connection timeout, trying another hello
2025-09-21 03:43:07,216 - Send: N0 M110 N0
125
2025-09-21 03:43:17,218 - There was a timeout while trying to connect to the printer
2025-09-21 03:43:17,225 - Changing monitoring state from "Connecting" to "Offline"
2025-09-21 03:43:17,230 - Connection closed, closing down monitor

Changing the G code as you suggested works. Mahalo. Can u provide any insight on why I can't increase the baud rate to 250000? My mainboard on my Voxelab Aquila is using a Creality V4.2.7 Silent Board. Do you know if the USB port on the 4..2.7 board supports 250000 baud rate?

Can't really say why the firmware doesn't actually match what they've documented. It's definitely a communication variable in Marlin and that board would definitely support the higher rate. Maybe it's considered more stable at the lower rate.

FWIW, both the V4.2.2 and V4.2.7 Creality boards reliably support 250K baud rate with OctoPrint/OctoPi. BUT, I had a heck of a time getting it enabled. After rebuilding Marlin for 250K on a printer and Octopi that had run reliably for years at 115K, I could not get OctoPi to connect at the higher speed. No printer found during the serial scan. After much frustration, power-cycling both printer and Pi after making the rate change and manually initiating a serial scan in OctoPrint yielded a 250K connection that has continued to run without problems since. That board will work reliably at that speed.