Hi
I’ve assembled a Picar-X with two installations (two sd cards), one with python and one with Ezblock.
The python one works perfectly, however the Ezblock version has an odd problem: it defaults to the state of running the right wheel backwards constantly!
It runs fairly slow, with a whining sound.
Trying the Ezblock calibration on both my Mac and my iPhone only allows for calibration of the servos as far as I can tell, not the motors. Running the Move sample works, but it reverts to the state if running the wheel backwards when I stop the sample code. Same with reboot.
Tested running a tiny project with only Stop and Sleep for 3 seconds. It does exactly that, but when done again starts spinning the wheel.
I would love to admit that I’ve mangled the pin setup, but if that is the case I cannot understand why the samples seems to work.
Any ideas how to turn off the right wheel when using the Ezblock config?
Many thanks for all help!!
I’m experiencing the exact same issue.
I’m running a Raspberry Pi 4 with the 1.2.3 EZBlock image. I updated the software to 1.2.4 after the 1st connection. It is showing the same behavior before and after the update. It seems to be fine while a program is running, but as soon as it’s idle again, the right wheel slowly spins backwards.
Yes, I should have mentioned the hardware/software setup, But I have the same as Torres above, with a v2 car shipped just before Xmas.
I just completed a build of the Picar-x and have the same issue. The right wheel moves slowly and makes a loud whining noise immediately after startup. It stops after boot, but then starts again after connecting to the car over Bluetooth. When a project is started, the wheel stops squealing. It starts again whenever the program is stopped.
If I swap the motors, it is the other one does the same when connected to Motor2 on the board. I have also not been able to get the spreaker to work using the various example projects. I am using an RPi 3 B with EzBlock version 1.2.4 (upgraded from the 1.2.3 image, same as the OP). I’m using EzBlock studio app 3.2.158 on Android.
Hi guys, about the issues you mentioned, could you please record the problem video for us to help us analyze and solve the problem? Thanks a lot.
If the video memory is large, please upload the recorded video to onedrive, please share the video link in a way that anyone can access it (anyone who has the link can access it), not in a way that only specific users can access it.
Here is a video of the problem. This shows the right wheel moving and making noise when a program is not running. It also shows that sounds is not working using one of the example projects. In the video I had the car propped up allowing the wheel to move. When setting it down, the wheel is not moving enough to move the car, but the motor noise increases under the additional strain.
https://1drv.ms/u/c/c0c9db5aac18085f/EaLYFWVNBJ5NkfI0lLf4IqYB3-WlSaqmirmnyGjRYw8o2Q
Thanks, didn’t get around to finding an online video storage. Looks like it does for me, also I notice that it now spins forward. Uninitiated variable?
Anyway, I should add that apart from the wheel problem the kit is great!
I modified the init method in picarx.py to call the stop method after initializing the calibration values. This seemed to fix the issue for now.
The file was on the pi filsystem in /opt/ezblock/. The files in this folder seemed to have diverged from ezb-pi/workspace at master · ezblockcode/ezb-pi · GitHub which has the original source for those files.
We have fixed the problem, we have updated the ezblock OS image version, the latest version is 1.2.5
After your APP is successfully connected to the picar-x product, you will be prompted to update the firmware, you update the ezblock OS version to version 1.2.5, and then go to run the example to see how it works.
Appreciate the quick response! It solved the problem for me!
Having fun with the car now!
Thank you. This update fixed the wheel issue for me as well as the speaker issue I’ve been having.
I have the same problem and went to your link but the version still appears to be the old one
1.2.3
Is there another link?
The mirror link for the tutorial is for the 1.2.3 version of the system, after you download and install it to the SD card, start picar-x and APP connection, there will be a pop-up window for you to update the version, currently the latest version is version 1.2.5.
I updated to version 1.2.5 and the wheel turning issue was fixed but … now my remote devices will not connect to the Picar-X. When I select connect the Bluetooth connection sees the Picar-X but when selected it errors out and says try again - but no luck. This happens on both my Apple Ipad and my Android phone.
EZBlock does connect using the IP address from a PC
Please advise a solution
Thanks
The update worked and the wheel stopped turning on its own.
The remote units (Ipad and Android phone) stopped connecting after the upgrade however (bluetooth errors)
My PC does connect through the IP address
Somehow the upgrade impacted the Bluetooth
Please advise the fix
Bob
After you reinstalled the 1.2.3 version of ezblock OS and went to connect with the app, you could not search for a connection to Bluetooth; or is it that after the 1.2.3 version of ezblock OS connected successfully with the app, and then after updating the version to 1.2.5, and then went to connect with the app, you could not search for a connection to Bluetooth?
We have tested both the new version and the external bluetooth version of robot-hat , both work fine:
We have not reproduced the problem, please take a picture and tell us what robot_hat appearance you are using, alternatively you can log in to the Raspberry Pi using ssh and run ezlock-service using the command to see the run log:
sudo systmctrl stop ezblock
sudo ezblock-service
Please send us the runtime logs
Also consider that it may be a problem on the mobile side, please open the Bluetooth settings of your mobile system, unpair the ezlock Bluetooth device, and then go to the APP to reconnect and see how it works.
Thank you for trying to assist me.
I think I have found the problem
My Apple Ipad remembered the Bluetooth settings for the previous EZBlock version (even though it was not connected)
I told Apple to forget the settings and then connected through the app and it worked.
Again - I appreciate your efforts to help me - it means a lot to a customer like me
Thanks
Bob