zubax / babel-babel Goto Github PK

add the Zubax logo to the enclosure PCB - perhaps underneath "To PC" and above "To device"

Pull CAN_VDD_EN pin to 5V with 10k resistor.

"ON" should mean on.

The drain of mosfet Q2 is directly connected to power line, which causes a short if CAN_VDD_EN is high. It should be pulled up to 3.3V power line with 10K resistor instead.
Solution for current prototypes - remove Q2 from both Babel sections (Q102, Q202) at all. They can be seen in the picture below.

Footprint of USB type A connector on Babel-Babel PCB does not match with the footprint of part which we a using right now. Fix it

Currently, it is unclear how to reflash the DroneCode Probe without pulling the enclosure apart. Maybe we should add a button like in the original DCP?

The enclosure PCB is missing one hole in the upper left corner for the bolts.

• check R43 & R113, R213 - they have the same part number but different packages (402 & 603)
• resolve ERC warnings in the schematic

The ordering of the boards is incorrect; @farzan-saleem knows the correct order

https://github.com/Zubax/Babel-Babel/blob/main/manufacturing/readme.md

I know that Alexander generated this image using Autodesk Fusion.

Per the design requirements found in requirements.md, only one assembly variant is needed.

Enable label on top PCB is on switching off side.

The DCP tends to occasionally freeze up when high-voltage power is applied to the target with Babel-Babel connected. Steps to reproduce:

1. Connect Babel-Babel to the (unpowered) target via both CAN interfaces, the DCP port, and the USB.
2. Connect Babel-Babel to the USB host (in my case this is a USB hub with a dedicated wall power supply).
3. Apply high-voltage power to the target (Myxa B0 in my case).
4. Observe DCP disappear from the list of connected devices on the host.

It may take several attempts to reproduce the problem.

The issue affects none of the other three devices connected to Babel-Babel. The DCP can be brought back to life by physically re-connecting Babel-Babel to the host with the DCP port unplugged, and then plugging the DCP port back in.

I suggest equipping the DCP port with EMI mitigation measures, perhaps resistors or chokes. Also, increasing the decoupling capacitance on the MCU might help.

The order of panels is not rigth. Also the picture lacks textures.

Implement CAN bus voltage measurement as it's not implemented in babel-babel. Follow Babel for reference.

VREF pin should be tied to VDD. (Controller did not work if VREF left in floating state)

The existing documentation is missing critical details such as the description of the behaviors implemented in the firmware. Everything that is not related to the hardware should be copied from the original Zubax Babel Datasheet into the README.