SDS100/SDS200: Uniden Scanner font glyphs

[Dexrn]

Are there any downloads or premade files that provide the glyphs found on the SDSXXX series in an accessible format? (e.g. bitmap/font file)

Would publishing them under an open-source project go against any guidelines that I am likely to get struck for not following?
I am willing to create the bitmap myself as long as I will not run into any legal issues, but for now I would like to try to take the easy way out. (not having to create it myself)

 

[Ubbe]

Usually how it works are that a scanners main CPU are writing to a memory area that represents the display and write a character to it at a location that representing a position on the display. It will have a config byte telling what colors it should use and if blinking or not.

That memory area are sent to the front panel CPU maybe 4 times a second, the update frequency. In that front panel CPU will be the bitmaps for the characters and it will be a CPU with a ROM memory content that Uniden have specified to the chip supplier. So no way of changing anything of its functionality.

/Ubbe

 

[ProScan]

Are there any downloads or premade files that provide the glyphs found on the SDSXXX series in an accessible format? (e.g. bitmap/font file)

Would publishing them under an open-source project go against any guidelines that I am likely to get struck for not following?
I am willing to create the bitmap myself as long as I will not run into any legal issues, but for now I would like to try to take the easy way out. (not having to create it myself)

This what you're looking for.
It's one big bitmap. I think if you find software that can extract the bitmap from the pdf file and take it from there.

SDS200_FontData_V1_00.pdf

 

[Dexrn]

This what you're looking for.
It's one big bitmap. I think if you find software that can extract the bitmap from the pdf file and take it from there.

SDS200_FontData_V1_00.pdf

Sounds good. Have there been any incidents with Uniden striking down companion software that makes use of their protocol or other assets? I have a pretty cool (IMO) POC that I would like to show off and make open source, but I'm not sure whether it will get me into hot waters or not for referencing the SDS100 docs (for understanding structs and possible values, everything else was reversed by manually checking the response of the scanner.)

 

[ProScan]

Sounds good. Have there been any incidents with Uniden striking down companion software that makes use of their protocol or other assets?

Not regarding the scanner protocol. It's published and they encourage 3rd party apps such as mine. Donno what you mean by "other assets"

I have a pretty cool (IMO) POC that I would like to show off and make open source, but I'm not sure whether it will get me into hot waters or not for referencing the SDS100 docs (for understanding structs and possible values, everything else was reversed by manually checking the response of the scanner.)

The docs are publicly available, so I don't see why you can't. I'm not sure what you're getting up to regarding structures and values. That's not part of the protocol and the protocol doesn't contain the font data matrix either.

 

[Dexrn]

Not regarding the scanner protocol. It's published and they encourage 3rd party apps such as mine. Donno what you mean by "other assets"


The docs are publicly available, so I don't see why you can't. I'm not sure what you're getting up to regarding structures and values. That's not part of the protocol and the protocol doesn't contain the font data matrix either.

By structures I mean the XML structure for MSI & GSI but also generally just how responses like STS should be parsed, since all sounds good I'll probably post the POC here once I finish abstracting stuff out so I can easily add support for other scanners

I went ahead and published some TypeScript typings that make understanding and parsing these responses easier. (unsure if I should share a link here)

 

[ProScan]

By structures I mean the XML structure for MSI & GSI but also generally just how responses like STS should be parsed, since all sounds good I'll probably post the POC here once I finish abstracting stuff out so I can easily add support for other scanners

I went ahead and published some TypeScript typings that make understanding and parsing these responses easier. (unsure if I should share a link here)

I see what you're doing now. One thing to be aware of is when parsing the STS data. The fav, sys, dept, and channel names can contain commas but that can be worked out.

 

[Dexrn]

I see what you're doing now. One thing to be aware of is when parsing the STS data. The fav, sys, dept, and channel names can contain commas but that can be worked out.

Thanks, will make sure to deal with that.