Skip to comments
Hello everyone,
I would like to share the new custom firmware available for EZB 4.
Currently i'm beta testing the firmware fixing and polishing the code.
I'm still open for ideas, please comment.
1) Initial screen:
2) Access point configuration:
3) Client/Station mode configuration:
4) HOST/EZB configuration:
5) Ports Configuration:
6) Tools
Working in progress
I will describe in another post the new features.
By ptp
— Last update
Other robots from Synthiam community
Cardboardhacker's Technopro Wall-E Project
I have finally started my wall-e project. I have desided to keep it simple due to my lack of income at age 12. I have...
Rb550f's Tars Robot Concept
I started working on a TARS concept robot.This only simulates walking action.The robot is made from foam board and...
Buratino's Basilio
Basilio: 3d printed - 45cm walking robot with 26 axis of movement, (arms, torso legs and head). Basilio has external...
Thanks, regarding the broadcast protocol does include the camera port ?
I tried different combinations and no success.
another question for you or Jeremie:
As you know when the PIC32 lockups (i2c or other conditions) the red led is on.
1) does exist a byte cmd sequence to restart the PIC32 ?
2) Is the PIC32 MCLR pin available in the PCB ?
3) there two pins x1 x2, are those clock pins ?
i would like to build a firmware option to reset the PIC32.
If no byte sequence, and the PIC32 MCLR pin is available i can connect to one of the WF121 digital ports.
It's actually when the STM32 on main board locks up that the red LED stays lit.
1) Sorry I don't know but @DJ might.
2) Yes, MCLR is broken out to the first pin of the programming header
3) X1 and X2 are "extra" pins made available from the STM32. There were broken out for future projects but haven't been utilized yet.
The red led is connected to the bottom board STM32. When the red led comes on from incorrect i2c communication, there is no software recovery. You will need to reset the power on the stm32, as it cannot be done via software.
As for the ezb broadcast, here is the protocol...
Code:
Transmit those packets every 3-6 seconds to 255.255.255.255 (0xffffffff). For udp broadcast, be sure to use socket option SO_BROADCAST
Thanks for coming back to the thread, i know you have a lot in your plates.
I wrote it incorrectly (PIC32) i wanted to write ARM
@Jeremie:
Arm board:
The NRST pin (7) is not accessible,
1)i see a capacitor C13 connected to GND and NRST
2)i presume the NRST is connected to the VCC, but i can't guess if there is a resistor between VCC and NRST ?
If there is a resistor, i can safely pull down to do a reset. The idea is to restart the ARM when is in lock mode.
Lumpy
Yes C13 is the only connection to NRST. There is a weak 40kohm internal pullup resistor that ties it high.
I've been busy improving and testing the Firmware, but to avoid delaying more.
I'm releasing the binary here:
EZB-V2.zip
I've plans to create a github repository similar to the V1 version plus some posts about the development challenges.
it will take extra time meanwhile i would love to get some feedback from the community.
Combining the last hardware manufacturer firmware (Blue Giga) plus optimizing the BGS code, i believe the new firmware is more stable and reliable.
I've introduced new features (next post) so i cannot guarantee is bug free
Some of his teenager students decided to "sabotage" other students rebooting or changing the servos positions plus adding other devices to the school network (password is open in the client page) .
They had some fun trolling around.
To avoid those issues I decided to improve the EZB http server security.
To access pages: Access Point, Client, Ezb, Ports, Security you will need to authenticate first:
the default password is password.
you can then later change via Security page:
Also the Client & AP security keys are masked "*" just in case you browsing around with someone looking:
The initial page is always accessible without authentication:
although the reboot button is only available if you are authenticated.
If you reboot the EZB, or someone else authenticates, your session is gone, and the browser will redirect you to the login page when you try to access the secured pages.
Thumb rule:
Only one user authenticated on the EZB HTTP Server.
I hope this will keep away the middle school bullies.
1) Overview page shows the Client Remote IPs connected to the EZB and the Camera.
I've plans to log these events to a server, that will help to avoid students messing other EZBs.
2) When in client mode, EZB synchronizes the time with a time server only once after the connection is established.
Although the hardware and the firmware supports a RTC (Real Time Clock) the EZR pcb does not have a required 32kHz crystal.
@Jeremie i know the PCB space is always a constrain, but if please next time think about hackers and add extra connections pins/soldering points for the remain IO pins, add-ons etc.
So without a hardware RTC, the clock is software based... expect to loose some seconds.
One possible solution is to keep updating the clock
I have more ideas and some of them requires a clock, for example performing some actions based on time/day of week.
It was a really fun challenge, but the EZR future is with another chip.
I have other projects between work and family, the free time is not enough to explore all the ideas.
Loaded the firmware onto one of my V4's today.
So far everything is looking good. Great work on this!
I'll let you know if I run into any glitches.
Kris
You pretty much hit the nail on the head for my initial ideas about what I felt could be improved in the web interface. Authentication being a big one!
Good job and keep it up!
(which is normally 3 times the price of the item) *eyeroll*
Also have this info available in ARC
My hope is to use 3 APs signal strengths to triangulate my position.
RichardZ
Great work @ptp