Ezb V4 Custom Firmware V2

ptp

USA
Skip to comments   Jump to end
robot image
robot image
robot image
robot image
robot image

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:

User-inserted image

  1. Access point configuration:

User-inserted image

  1. Client/Station mode configuration:

User-inserted image

  1. HOST/EZB configuration:

User-inserted image

  1. Ports Configuration:

    User-inserted image

  2. Tools

Working in progress

I will describe in another post the new features.

By — Last update
Jump to end

Other robots from Synthiam community

Daman's Metal Boxbot... Yes I'm That Impatient

Daman's Metal Boxbot... Yes I'm That Impatient

Hey all! So I read the title BoxBot by thetechguru and while I love the salmon box platform, it wasnt quite what I...
Jeremie's Richard R And Bhouston In Make Magazine

Jeremie's Richard R And Bhouston In Make Magazine

Congrats to @Richard R and @Bhouston for getting their inMoov robots published! Its pretty awesome seeing you guys in...
Jason's Roli Time-Lapse Video Robot

Jason's Roli Time-Lapse Video Robot

Hey everyone, I wanted to introduce to you the Worlds first Roli Time-lapse Rig Pretty straight forward, your standard...

ARC Pro

Upgrade to ARC Pro

Get access to the latest features and updates before they're released. You'll have everything that's needed to unleash your robot's potential!

PRO
Synthiam
#10  

I would have shared the broadcast protocol if you still need it:)

#11  

Alan, thank you for the break down. That makes perfect sense. :)

PRO
USA
#12  

@DJ

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.

Hungary
#13  

Ports configuration is a great feature!

PRO
Canada
#14  

Sorry @PTP I didn't see this post until today.

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.

PRO
Synthiam
#15  

The PIC32 is the wifi module that you are programming, and it does not lock up with the red led.

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...


UDP Port: 4242

"EZ-B v4.x||%s||%s||%u",
  name of ezb (i.e. "My EZB")
  ip address  (i.e. "192.168.23.1")
  port        (i.e. "23")
  
"Camera||%s||%s||%u", 
  name of ezb (i.e. "My EZB")
  ip address  (i.e. "192.168.23.1")
  port        (i.e. "24")

Transmit those packets every 3-6 seconds to 255.255.255.255 (0xffffffff). For udp broadcast, be sure to use socket option SO_BROADCAST

PRO
USA
#16  

@DJ, Jeremie: 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.

Login to post a comment