Theia API question

IamGenZod

Learning to Drive
General User
Joined
Mar 26, 2020
Messages
36
Reaction score
50
Location
Pittsburgh, PA
Just had a quick question that may possibly generate more. With the delays in the public release of the highly anticipated theia, has the upcoming API made any progress? I inquired in the past but that was prior to the long delayed launch.

I had hoped to get started working on some early code with the API. If not I am good with it as long as progress keeps moving forward.

Thank you
 

Jon at Radenso

Manufacturer
Lifetime Premium
Corgi Lovers
Advanced User
Manufacturer
Joined
Oct 9, 2012
Messages
3,226
Reaction score
26,255
Age
32
One thing that I will mention since it is very unique is that there are actually two APIs for Theia - one for BT to app, but also another one we are exposing between the FPGA and SoM - the DSP API.

One of the challenges with using a FPGA is that writing useful HDL is so difficult there is maybe only one or two people on rdforum that could do it, but there are several great app developers on here who could benefit from getting "answers" from the FPGA to questions they have. For example, right now detectors will tell you via an API "we are alerting, front horn, K band." And that's great - but you don't have access to the low-level information the radar detector knows (for example, which channel energy is present in, what type of energy, etc). You don't get to know why the detector is alerting.

The way we built Theia's DSP API, developers will have access to tons of low level information. For example, if an app wants to know the pulse rate of radar energy in channel 21, all it has to do is ask. If it wants to know what Dragoneye pulses look like when decimated or low pass filtered, it just has to ask. If it wants to know the output of a match filter, it can. This will provide very sophisticated conditional logic possibilities in apps that are not currently present; in essence, app developers will not just be able to be told "there is an alert," but they will be able to design their own alerts and filtering if they wish using the DSP blocks built into Theia's API. And our system is intentionally extensible; a developer can reach out to us and request a certain DSP operation and if it's not already in our IP library we can build it and add it in.
 
Last edited:

G37X Jockey

Premium Plus
Lifetime Premium
Advanced User
Joined
Jul 22, 2012
Messages
2,336
Reaction score
3,823
Location
Behind my Steering Wheel
One thing that I will mention since it is very unique is that there are actually two APIs for Theia - one for BT to app, but also another one we are exposing between the FPGA and SoM - the DSP API.

One of the challenges with using a FPGA is that writing useful HDL is so difficult there is maybe only one or two people on rdforum that could do it, but there are several great app developers on here who could benefit from getting "answers" from the FPGA to questions they have. For example, right now detectors will tell you via an API "we are alerting, front horn, K band." And that's great - but you don't have access to the low-level information the radar detector knows (for example, which channel energy is present in, what type of energy, etc). You don't get to know why the detector is alerting.

The way we built Theia's DSP API, developers will have access to tons of low level information. For example, if an app wants to know the pulse rate of radar energy in channel 21, all it has to do is ask. If it wants to know what Dragoneye pulses look like when decimated or low pass filtered, it just has to ask. If it wants to know the output of a match filter, it can. This will provide very sophisticated conditional logic possibilities in apps that are not currently present; in essence, app developers will not just be able to be told "there is an alert," but they will be able to design their own alerts and filtering if they wish using the DSP blocks built into Theia's API. And our system is intentionally extensible; a developer can reach out to us and request a certain DSP operation and if it's not already in our IP library we can build it and add it in.
Jon the R&D your team has engineered into Theia truly sounds amazing. We're all pulling for you guys; making Theia into a device we can actually get our hands on some day.
 

VideosFromNH

Learning to Fly
Beginner User
Joined
Apr 30, 2020
Messages
361
Reaction score
1,376
Location
New Hampshire
One thing that I will mention since it is very unique is that there are actually two APIs for Theia - one for BT to app, but also another one we are exposing between the FPGA and SoM - the DSP API.

One of the challenges with using a FPGA is that writing useful HDL is so difficult there is maybe only one or two people on rdforum that could do it, but there are several great app developers on here who could benefit from getting "answers" from the FPGA to questions they have. For example, right now detectors will tell you via an API "we are alerting, front horn, K band." And that's great - but you don't have access to the low-level information the radar detector knows (for example, which channel energy is present in, what type of energy, etc). You don't get to know why the detector is alerting.

The way we built Theia's DSP API, developers will have access to tons of low level information. For example, if an app wants to know the pulse rate of radar energy in channel 21, all it has to do is ask. If it wants to know what Dragoneye pulses look like when decimated or low pass filtered, it just has to ask. If it wants to know the output of a match filter, it can. This will provide very sophisticated conditional logic possibilities in apps that are not currently present; in essence, app developers will not just be able to be told "there is an alert," but they will be able to design their own alerts and filtering if they wish using the DSP blocks built into Theia's API. And our system is intentionally extensible; a developer can reach out to us and request a certain DSP operation and if it's not already in our IP library we can build it and add it in.
Nice to hear some new news for a change.
Sucks having to wait for parts, but this update is a nice treat.
 

Vortex

Making Videos
Observer
VIP
Lifetime Premium
Corgi Lovers
Advanced User
Joined
Jul 19, 2012
Messages
22,176
Reaction score
61,488
Location
Washington State
One thing that I will mention since it is very unique is that there are actually two APIs for Theia - one for BT to app, but also another one we are exposing between the FPGA and SoM - the DSP API.

One of the challenges with using a FPGA is that writing useful HDL is so difficult there is maybe only one or two people on rdforum that could do it, but there are several great app developers on here who could benefit from getting "answers" from the FPGA to questions they have. For example, right now detectors will tell you via an API "we are alerting, front horn, K band." And that's great - but you don't have access to the low-level information the radar detector knows (for example, which channel energy is present in, what type of energy, etc). You don't get to know why the detector is alerting.

The way we built Theia's DSP API, developers will have access to tons of low level information. For example, if an app wants to know the pulse rate of radar energy in channel 21, all it has to do is ask. If it wants to know what Dragoneye pulses look like when decimated or low pass filtered, it just has to ask. If it wants to know the output of a match filter, it can. This will provide very sophisticated conditional logic possibilities in apps that are not currently present; in essence, app developers will not just be able to be told "there is an alert," but they will be able to design their own alerts and filtering if they wish using the DSP blocks built into Theia's API. And our system is intentionally extensible; a developer can reach out to us and request a certain DSP operation and if it's not already in our IP library we can build it and add it in.
WOW! That's taking the concept of an Open API to a whole 'nother level...
 

InDecay

¯\_(ツ)_/¯
Intermediate User
Joined
Dec 20, 2019
Messages
513
Reaction score
1,008
Location
Phoenix, AZ
One thing that I will mention since it is very unique is that there are actually two APIs for Theia - one for BT to app, but also another one we are exposing between the FPGA and SoM - the DSP API.

One of the challenges with using a FPGA is that writing useful HDL is so difficult there is maybe only one or two people on rdforum that could do it, but there are several great app developers on here who could benefit from getting "answers" from the FPGA to questions they have. For example, right now detectors will tell you via an API "we are alerting, front horn, K band." And that's great - but you don't have access to the low-level information the radar detector knows (for example, which channel energy is present in, what type of energy, etc). You don't get to know why the detector is alerting.

The way we built Theia's DSP API, developers will have access to tons of low level information. For example, if an app wants to know the pulse rate of radar energy in channel 21, all it has to do is ask. If it wants to know what Dragoneye pulses look like when decimated or low pass filtered, it just has to ask. If it wants to know the output of a match filter, it can. This will provide very sophisticated conditional logic possibilities in apps that are not currently present; in essence, app developers will not just be able to be told "there is an alert," but they will be able to design their own alerts and filtering if they wish using the DSP blocks built into Theia's API. And our system is intentionally extensible; a developer can reach out to us and request a certain DSP operation and if it's not already in our IP library we can build it and add it in.
How much of the raw data from the SDR will be made available to developers? Or will it only be post-DSP / AI filtered data (if that makes sense)?
Also, random question. Any chance Theia is just Codename Theia and we may see an updated product name on launch?
 

Jon at Radenso

Manufacturer
Lifetime Premium
Corgi Lovers
Advanced User
Manufacturer
Joined
Oct 9, 2012
Messages
3,226
Reaction score
26,255
Age
32
How much of the raw data from the SDR will be made available to developers? Or will it only be post-DSP / AI filtered data (if that makes sense)?
Also, random question. Any chance Theia is just Codename Theia and we may see an updated product name on launch?
Well, there is really no such thing as "pre-DSP data." The simple act of digitizing it and channelizing it so it's usable is DSP in and of itself. But the intent is to allow very low-level data products to be available. We wrote the API for our own use (it's what the linux SoM uses to communicate with the FPGA), so it's very powerful. Developers will be able to use the data products just as we do.
 

JagMan

Learning to Fly
Lifetime Premium
Beginner User
Joined
May 31, 2016
Messages
67
Reaction score
32
Location
Sedona, AZ
Well, there is really no such thing as "pre-DSP data." The simple act of digitizing it and channelizing it so it's usable is DSP in and of itself. But the intent is to allow very low-level data products to be available. We wrote the API for our own use (it's what the linux SoM uses to communicate with the FPGA), so it's very powerful. Developers will be able to use the data products just as we do.
Great to hear from you Jon. I always enjoy your what you share. Thanks!
 

Patton250

Lifetime Premium
Advanced User
Joined
Feb 20, 2017
Messages
3,387
Reaction score
4,609
Location
Florida
I hope you guys are taking this time to develop remote Theia. I had heard you guys would have that available roughly a year after the windshield mount version came out. Did that project get bumped into the future as well?
 

Randy at Radenso

beyond radar.
Lifetime Premium
Corgi Lovers
Advanced User
Manufacturer
Joined
Sep 9, 2011
Messages
1,460
Reaction score
7,820
Location
Cincinnati, OH
I hope you guys are taking this time to develop remote Theia. I had heard you guys would have that available roughly a year after the windshield mount version came out. Did that project get bumped into the future as well?

All focus is on Theia. Unfortunately we can't speak about way future plans regarding products, hope you understand!
 

Discord Server

Latest threads

Forum statistics

Threads
97,612
Messages
1,482,260
Members
24,726
Latest member
Livsy
Top