Skip to content

TeleDecoder - #314

Open
chethankarandikar wants to merge 44 commits into
mainfrom
Dongler
Open

chethankarandikar wants to merge 44 commits into
mainfrom
Dongler

Conversation

@chethankarandikar

Copy link
Copy Markdown
Contributor

No description provided.

@chethankarandikar

Copy link
Copy Markdown
Contributor Author

@EDED2314
added the link to the schematic

@EDED2314
EDED2314 self-requested a review July 17, 2026 04:44

@EDED2314 EDED2314 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm (thanks!)

@KacperParaniuk KacperParaniuk left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Symbol Conventions ✅

  • There are some symbols in the general libs folder that should be put in their own symbol library but those are not used for this project thus we can fix it once we merge.

Footprint Conventions ✅

3D Models ✅

Schematic Style 🟨

  • The radio chip symbol could be better. The power pins (5,12,13,15,25,28,22,27) could all be combined into one with the others set as invisible and also moved to the top of the symbol as this is power. and gnd can be put to the bottom if we want to keep following this convention.
  • l noticed net labels were used rather than hierarchical labels. Is there a reason for this? Also if we want to be consistent with other designs we should replace these to be the hierarchical labels.
  • Additionally, within the box the following convention is not followed: "The box title describes the general functionality while the subtitle describes the main component partnumber or other design defining information."

Routing 🟨
I looked at a bit of the routing because I was curious about it and how the RF matching stuff was done. And how we implemented it with relationship to the teledongle.

Image

I noticed that it was different from what we have done and was wondering if potentially this could result in an issue in the black magic world of RF.

Image

someone with more RF knowledge can answer.

@tjmcmanamen38

Copy link
Copy Markdown
Contributor

I noticed that it was different from what we have done and was wondering if potentially this could result in an issue in the black magic world of RF.

someone with more RF knowledge can answer.

Yes agreed 100% on this, I didn't really look over this board much until it was already done and didn't catch this in time but this is definitely something to change for future revisions.

@tjmcmanamen38 tjmcmanamen38 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Crystal_NDK.kicad_sym library is not unique enough to have its own library and should be removed and replaced with the generic Crystal_GND2 symbol. Though credit where credit is due - the naming is good!

@tjmcmanamen38

Copy link
Copy Markdown
Contributor

The radio chip symbol could be better.

Reasoning for this is that it's a KiCad default library (which you would think these would follow the KLC...). Your discretion if you want to change it.

However I would caution against combining all of the power pins, at minimum DVDD and AVDD should be kept separate. And I'm not sure enough as to the differences between all of the individual pins to know if they should be kept distinct or not, would have to look more at the datasheet.

@tjmcmanamen38

Copy link
Copy Markdown
Contributor

Additionally, within the box the following convention is not followed: "The box title describes the general functionality while the subtitle describes the main component partnumber or other design defining information."

Yes this would be a good thing to change, I'd also change the SMA Connector box to be called 'RF Front End' or 'RF Matching Network' or something of that sort.

And generally I have liked to standardize the text size for the major boxes (eg microcontroller, usb, rf, radio, regulator) to 2mm rather than 1.27mm in addition to adding the main part number.

@tjmcmanamen38

Copy link
Copy Markdown
Contributor

net labels were used rather than hierarchical labels

Yeah biggest thing here I think is just to make sure we're being consistent - USB data lines use hierarchical while nothing else does.
image

@tjmcmanamen38

Copy link
Copy Markdown
Contributor

Some other formatting nitpicks:

image
  • avoid the use of C_small and other small variants
  • fix the wire over the LED here
  • avoid 4 way intersections
image image
  • add a green segment between pins and their connections
image
  • fill in rev

  • Add dimensions to board in layout (place -> draw dimensions)

Generally make sure to reference Schematic-Conventions.md, some things here we don't do regularly these days but for the most part it is still a very good baseline.

@EDED2314

Copy link
Copy Markdown
Contributor

I noticed that it was different from what we have done and was wondering if potentially this could result in an issue in the black magic world of RF.

don't think that would make RF a black magic word. But I think there are def some matching issues. Co-planar trace widths to and from antenna matched to 50 ohms should be 0.3487mm. I don't know how they 0.2mm as well, but I think that the arrangement of inductors and caps can be flexed around a little, but the target goal is to get the time a signal is along a trace to be very small.

avoid 4 way intersections

I don't see how else one would implement it without making the schematic messy if we keep all the voltages to one side

The radio chip symbol could be better. The power pins (5,12,13,15,25,28,22,27) could all be combined into one with the others set as invisible and also moved to the top of the symbol as this is power. and gnd can be put to the bottom if we want to keep following this convention.

I think convention is good, but since we are working with the individual chip and not a module, I think we should keep the official library's symbol as is, since there are definitely nuances to power supplies that should not be ignored. Some chips have a lot of power options and it is important to distinguish them/provide flexibility.

Agree with all the other comments :)

@tjmcmanamen38

Copy link
Copy Markdown
Contributor

With the RF trace imo one of the biggest nonos is the use of vias

@tjmcmanamen38

Copy link
Copy Markdown
Contributor

wdym about the 4 way intersections it should always be doable.
eg
image
vs
image

@tjmcmanamen38

Copy link
Copy Markdown
Contributor

With the symbol yeah agreed that it's fine to keep as is but technically you can move power pins to the top without having to merge them

@EDED2314

EDED2314 commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

I implemented the requested changes, lmk if I am missing anything

@EDED2314
EDED2314 requested a review from tjmcmanamen38 August 11, 2026 21:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants