Nanopb Alternatives

nanopb reviews and mentions

• ESP-Now: multiple devices, but how to do multiple types of data?
  1 project | reddit.com/r/esp32 | 9 Jul 2022

  The OTHER way to do it is with protobufs, since they don't encode parts of the message that aren't included (that is: any missing part of the message has 0 transmission overhead). nanopb works well on the ESP32.

• looking for c++ libraries whose equivalent c libraries are also present..
  1 project | reddit.com/r/embedded | 19 May 2022

  You could look at my library Embedded Proto and Nanopb. If you have any questions let me know.

• How many of you do you actually use C++ for device drivers?
  2 projects | reddit.com/r/embedded | 18 May 2022
• Nanopb - Protocol Buffers for Embedded Systems
  1 project | reddit.com/r/github_trends | 21 Apr 2022
• nanopb VS protobuf-c - a user suggested alternative
  2 projects | 4 Feb 2022
• Network serialization libraries for C?
  1 project | reddit.com/r/C_Programming | 2 Dec 2021

  Nanopb - https://github.com/nanopb/nanopb

• Coding messages
  1 project | reddit.com/r/embedded | 28 Oct 2021

  If you control both endpoints, use nanopb. (https://jpa.kapsi.fi/nanopb/) It's a scaled down implementation of google's protocol buffers. You create your message and it will generate the encode/decode functions and structures. Don't re-invent the wheel.

• nanopb VS EmbeddedProto - a user suggested alternative
  2 projects | 14 Oct 2021
• Efficient multi-language message packing / serialization for embedded applications. (stuff_sack)
  2 projects | reddit.com/r/programming | 17 Jul 2021

  You are on the right track regarding protobufs, FlatBuffers, and Cap'n Proto. They are targeted at server communication and/or RPC and have features (optional fields, variable length arrays, etc) that stuff_sack does not have. There is an implementation for protobufs called nanopb which is targeted at embedded devices and is a good option for application requiring those features. Without these features stuff_sack is generally faster in packing and unpacking. Whether or not the binaries are smaller actually depends on the number of messages defined, but for common use cases (<15 messages) they should be.

• SharedMemory concept for mesh of micro controllers : Does it work ? Can it be done for "free" (using pointers only) ? (Do you wanna help me ?)
  1 project | reddit.com/r/embedded | 21 May 2021

  Also, Protocol Buffers is a good library for defining messages and getting generated code to serialize / deserialze them. The nanopb project is an implementation suitable for embedded. This has nothing to do with moving data between devices, but it is an easy way to make your messages portable and compatible with different versions (which is very helpful when you are updating your distributed system).

• Groc for GSM
  1 project | reddit.com/r/stm32f4 | 13 Apr 2021

  I was going through an example https://github.com/nanopb/nanopb/blob/master/examples/simple/simple.c

• Grpc with GSM
  1 project | reddit.com/r/embedded | 12 Apr 2021

  https://github.com/nanopb/nanopb/blob/master/examples/simple/simple.c Since i don't have a setup, would you be able to please set this up and try to send the encoded binary payload using AT commands? It could be a great brag on your CV, you can see how scarce the info about GRPC on embedded is :)