Blog

IR Camera Controller

Posted on by user

The idea behind this simple IR communication enabled set of boards is to allow remote control of Red Epic or Weapon camera via the RS232 interface.

Requirements:

  • IR communication up to 10 meters,
  • Configurable IR key codes,
  • IR to UART bridge,
  • Low power profile,

Major components:

  • MSP430FR5739
  • TSOP4840
  • TPS7B6933
  • IR12-21C

Number of PCB layers: 2

BOM price: 19 USD

Realization time: 4 weeks

Versatile debugging agent – ReCON

Posted on by user

During the process of firmware development two types of tests are initiated: functional and performance test. Each set of tests requires different tools which at the end lead to case where bunch of devices/instruments/probes are connected to device and PC. Having a all-in-one solution for these kind of tests is hard to achieve due to the spectrum of the tests and the range of the device. As such for a range of ST micro-controllers we made such an attempt with the device which incorporates:

  • USB 2.0 1-4 USB Hub
  • STLINK v2.0 programmer via STM32F103 MCU
  • Signal generation and debugging via STM32F446 FS & HS USB interface separately exposed on USB hub
  • ability to daisy chain through USB port

The key role of the STM32F446 is to provide bridge like function through USB CDC VCP class and designated peripheral on the aforementioned MCU. With the total of 15 USB endpoints (FS + HS) a rich set of functions can be simultaneously instantiated through separated USB class. In our case one USB VCP interface is used for device configuration of the remaining USB VCP interfaces which can act as serial probes/converters, digital and analog signal pattern generators, ADC signal capture, complex protocol implementation, etc… All digital IO pins are opto isolated for safe purposes.

The idea for this versatile board came from a sub-project where the multiple UART interfaces where enabled on a small dongle based on STM32F446 MCU. The good side of this approach was compact size, multiple IO’s and protocols exposed. However, no overcurrent/overvoltage protection.

BLE Keychain

Posted on by user

As name it self states this is a small BLE enabled keychain with inductive custom built inductive charging mechanism. The device once paired with mobile phone tracks the distance from mobile phone. If the mobile phone distance from keychain is above the predefined threshold the sound alarm is initiated.

Requirements:

  • BLE interface for device configuration
  • BLE signal monitoring
  • Inductive battery charging
  • Audio signal for out of range indication
  • Small and compact size

Major components:

  • nRF52832 BLE SoC
  • MSP430G2230
  • TPS78233
  • MCP73831
  • BQ29700

Number of PCB layers : 4

Realization time: 7 weeks

BOM price: 46 USD

Motion Detection & Tracking

Posted on by user

Low power low voltage 1V8 BLE board to enable IMU sensor data streaming and logging on NOR serial flash memory.

Requirements:

  • BLE interface for device configuration
  • BLE IMU data streaming via notifications
  • Serial NOR flash data logging 64MB
  • UART2USB interface
  • IMU data capture

Major components:

  • nRF52832 BLE SoC
  • S25FS512 NOR Flash
  • FT234XD
  • ICM.20948
  • TPS62740 & MCP73810

Number of PCB layers : 4

Realization time: 6 weeks

BOM price: 40 USD

Manual routing vs auto-router

Posted on by user

Auto-routers can be a great tool if it is used correctly. Like any tool, it can be used to expedite certain tasks, and has limitations which need to be understood in order to leverage it effectively.

Young engineers entering the world of PCB design might be tempted to use the Auto-router tool expecting that this tool will do entire work for them. But soon they will see that this is not the case.

While we working on the custom development board we got an idea. For us, working on the development boards are always fun because most of the time these boards are symmetrical, and there is something quite mesmerizing about symmetry. (Figure 1).

We wanted to see how will the auto-router perform on this board. With the components already placed, for us humans, this would be a relatively easy task.

But for auto-router this was not an easy task. As you can see on Figure 2, the auto-router wasn’t able to finish the board. It gave us a couple of solution but non of them was finished. (Figure 3,4,5) show some of the solutions that we got from the auto-router.

Conclusion: When creating the auto-router, the creators where not able to replace the PCB engineers with the machine but they manged to give us a tool to increase our productivity.