Ratpack - Recent changes [en]

Itinerary

Nelson — Sun, 02 Aug 2026 02:10:59 GMT

← Older revision		Revision as of 20:10, 1 August 2026
Line 1:		Line 1:
	[[Category:Meetings]]		[[Category:Meetings]]

			Nelson: Bob's method of interpreting frequencies

ADC

Nelson — Sun, 02 Aug 2026 02:10:14 GMT

← Older revision		Revision as of 20:10, 1 August 2026
Line 4:		Line 4:

	I am wondering how well this will work for selecting a square wave. I'll try to do a demo in python.		I am wondering how well this will work for selecting a square wave. I'll try to do a demo in python.


			== Gay bob's idea ==

			Just use a first difference, maybe taking it a few samples back, and see when that becomes big enough, then record that as a transition, and calculate the average difference in time between them over the period.

Formatting

Bean — Fri, 31 Jul 2026 22:07:37 GMT

← Older revision		Revision as of 16:07, 31 July 2026
(One intermediate revision by the same user not shown)
Line 7:		Line 7:
	- Struct names: Upper Snake Case, append "_t"		- Struct names: Upper Snake Case, append "_t"
	- Variables: Lower Snake Case		- Variables: Lower Snake Case
			- Constants: Upper Snake Case
	- Files:		- Files:
	- .c, .h, .txt Lowercase with underscores		- .c, .h, .txt Lowercase with underscores
Line 23:		Line 24:
	- docs		- docs
	- build: stuff relating to build frameworks and tools		- build: stuff relating to build frameworks and tools
			- merge:

File:2026 07 31-Meeting.png

Nelson — Fri, 31 Jul 2026 19:56:49 GMT

Nelson uploaded File:2026 07 31-Meeting.png

New page

2026 07 31-Meeting

Nelson — Fri, 31 Jul 2026 19:56:45 GMT

← Older revision		Revision as of 13:56, 31 July 2026
Line 16:		Line 16:
	- Make past code conform to style guide		- Make past code conform to style guide
	- Get completed commits from BeanBranch into main		- Get completed commits from BeanBranch into main

			[[File:2026_07_31-Meeting.png]]

DAC

Nelson — Fri, 31 Jul 2026 19:56:06 GMT

Timer6 Interrupts

← Older revision		Revision as of 13:56, 31 July 2026
Line 45:		Line 45:
	The fast one that sends 0s and 1s to the dac		The fast one that sends 0s and 1s to the dac

			This could alternately be implemented by xoring 1 with the old value and only having an interrupt at the end of a faster timer, but reading the old value is likely less worth it.

			Two interrupts method (I think better?)
	Halfway interrupt: Write 1 into dac		Halfway interrupt: Write 1 into dac
	Fullway interrupt: Write 0 into dac		Fullway interrupt: Write 0 into dac

	~~This could alternately be implemented by xoring 1 with the old value and only having an interrupt at the end of a faster timer, but reading the old value is likely less worth it.~~

ADC

Nelson — Fri, 31 Jul 2026 19:55:36 GMT

← Older revision		Revision as of 13:55, 31 July 2026
Line 2:		Line 2:

	https://en.wikipedia.org/wiki/Goertzel_algorithm		https://en.wikipedia.org/wiki/Goertzel_algorithm

			I am wondering how well this will work for selecting a square wave. I'll try to do a demo in python.

DAC

Nelson — Fri, 31 Jul 2026 19:54:10 GMT

Timer6 Interrupts

← Older revision		Revision as of 13:54, 31 July 2026
Line 45:		Line 45:
	The fast one that sends 0s and 1s to the dac		The fast one that sends 0s and 1s to the dac

	Halfway interrupt		Halfway interrupt: Write 1 into dac
	- Write 1 into dac		Fullway interrupt: Write 0 into dac

	~~Fullway~~ interrupt		This could alternately be implemented by xoring 1 with the old value and only having an interrupt at the end of a faster timer, but reading the old value is likely less worth it.
	~~- Write 0 into dac~~

2026 07 31-Meeting

Nelson — Fri, 31 Jul 2026 19:46:46 GMT

← Older revision		Revision as of 13:46, 31 July 2026
Line 1:		Line 1:
	[[Category:Meetings]]		[[Category:Meetings]]

			Most of the meeting time was spent discussing and defining the [[DAC]] Contract, to be implemented by next week

			The [[Formatting]] page now defines a rough style guide for code going forward.

	DMA:		DMA:
Line 6:		Line 10:
	- DMA Shares AHB system bus with other masters		- DMA Shares AHB system bus with other masters

	~~I'm writing [[DAC]] to define the contracts we plan to implement by next week.~~

	Next week Goals: 16:00 Friday Meeting, Me and Ben in this room		Next week Goals: 16:00 Friday Meeting, Me and Ben in this room
	- Hardware testing, Will scope the connections next meeting		- Hardware testing, Will scope the connections next meeting
	- Have dac output pipeline all the way from a faux packet_framer() to the Dac outputting		- Have dac output pipeline all the way from a faux packet_framer() to the Dac outputting
			- Make past code conform to style guide
			- Get completed commits from BeanBranch into main

Category:Contracts

Nelson — Fri, 31 Jul 2026 19:44:18 GMT

Created page with "Category:Index Code contracts and definitions. This file is the source of truth, follow it, or discuss and change it."

New page

[[Category:Index]]
Code contracts and definitions. This file is the source of truth, follow it, or discuss and change it.

DAC

Nelson — Fri, 31 Jul 2026 19:42:57 GMT

Created page with "Category:Contracts == DataBlock Struct == ``` typedef struct { int length; // Length in bits int current_index; // current position *TO BE READ NEXT* in bits uint8_t flags; // an area to communicate between different things accessing this memory const int max_length; // maximum length which can be stored in `data` in bits const uint8_t* data; // pointer to uint8 array to store data in } DataBlock_s; ``` == FLAGS Data == - 0 for DAC_STOP..."

New page

[[Category:Contracts]]

== DataBlock Struct ==
```
typedef struct {
int length; // Length in bits
int current_index; // current position *TO BE READ NEXT* in bits
uint8_t flags; // an area to communicate between different things accessing this memory
const int max_length; // maximum length which can be stored in `data` in bits
const uint8_t* data; // pointer to uint8 array to store data in
} DataBlock_s;
```

== FLAGS Data ==
- 0 for DAC_STOPPED
- 1 for DAC_WORKING

== Dac Outputting Overview ==
- Setup handled by DAC_init()
- Tim3 will hold a given frequency, it has an approximately 0.5second period. This is how long the high freq is held for the one bit.
- Once Tim3 finishes, it will call a handler that checks if done, or sets Tim6 ARR depending on the next bit
- Tim6 will at halfway through set the dac's output to 1, and at the end set the dac's output to 0. This has a frequency on the order of 1.2kHz, or 2.4kHz. This will transmit the frequency for the duration of Tim3's output

- From packet_framer() we write the DataBlock_s->length and ->data fields, then call DAC_init()

== DAC_init() ==
- Set current_index to zero
- set flags to 1 to mean the dac is working, external stuff should respect that and not try to write into this block
- Enable Tim6
- Enable radio PTT (once implemented)
- Enable Tim3
- Manually set Tim3 to max value to 'naturally' trigger a reset? Is this possible? We could also just call the handler, but then we get a race condition I think if the timer's going and other interrupts could delay it? We could also just wait 0.5s for it to happen actually naturally

== Timer3 Interrupt ==
The long one that changes the frequency of TIm6
- if current position is less than message length
- Get the bit stated by current_index and set TIM6's ARR accordingly to hf if it's a 1, or lf it's a 0. Remember that current_index is the bit index
- else (current pos is strictly greater than message length)
- Disable radio PTT (once implemented)
- Stop Tim6
- Stop Tim3
- Set ->flags to 0 to indicate done transmitting

== Timer6 Interrupts ==
The fast one that sends 0s and 1s to the dac

Halfway interrupt
- Write 1 into dac

Fullway interrupt
- Write 0 into dac

Formatting

Nelson — Fri, 31 Jul 2026 19:14:09 GMT

@@ Line 1: / Line 1: @@
 == 2026 07 31 ==
 What format do we use to name things?
@@ Line 9: / Line 11: @@
       - .txt and .json Upper Camel Case
   - Folders: By vibes

2026 07 31-Meeting

Nelson — Fri, 31 Jul 2026 18:59:19 GMT

← Older revision		Revision as of 12:59, 31 July 2026
Line 5:		Line 5:
	- Circular: Reruns over the same circular buffer repeatedly		- Circular: Reruns over the same circular buffer repeatedly
	- DMA Shares AHB system bus with other masters		- DMA Shares AHB system bus with other masters

			I'm writing [[DAC]] to define the contracts we plan to implement by next week.

			Next week Goals: 16:00 Friday Meeting, Me and Ben in this room
			- Hardware testing, Will scope the connections next meeting
			- Have dac output pipeline all the way from a faux packet_framer() to the Dac outputting

Formatting

Nelson — Fri, 31 Jul 2026 18:41:36 GMT

Created page with "== 2026 07 31 == What format do we use to name things? - Using "*" then " * " then ": " to write comments - Method names: Upper Snake Case - Struct names: Upper Snake Case, append "_t" - Variables: Lower Snake Case - Files: - .c, .h, .txt Lowercase with underscores - .txt and .json Upper Camel Case - Folders: By vibes"

New page

== 2026 07 31 ==
What format do we use to name things?
- Using "/**" then " * " then " */" to write comments
- Method names: Upper Snake Case
- Struct names: Upper Snake Case, append "_t"
- Variables: Lower Snake Case
- Files:
- .c, .h, .txt Lowercase with underscores
- .txt and .json Upper Camel Case
- Folders: By vibes

Itinerary

Nelson — Fri, 31 Jul 2026 18:41:14 GMT

Replaced content with "Category:Meetings"

← Older revision		Revision as of 12:41, 31 July 2026
Line 1:		Line 1:
	[[Category:Meetings]]		[[Category:Meetings]]

	~~What format do we use to name things?~~

	~~Talk about how the packet side will get an interrupt handled (possibly with a timer just checking every so often if DAC is not busy once armed)~~

	~~Talk about the DAC flow (arming and just letting it go until it's not busy)~~

	~~Having the struct be passed along~~

2026 07 31-Meeting

Nelson — Fri, 31 Jul 2026 17:47:41 GMT

← Older revision		Revision as of 11:47, 31 July 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	[[Category:Meetings]]		[[Category:Meetings]]

	~~Beans!~~		DMA:
			- Oneshot: writes a long bit of data to a section out/in from adc/dac
			- Circular: Reruns over the same circular buffer repeatedly
			- DMA Shares AHB system bus with other masters

2026 07 31-Meeting

Nelson — Fri, 31 Jul 2026 17:39:48 GMT

Created page with "Category:Meetings Beans!"

New page

[[Category:Meetings]]

Beans!

Itinerary

Ggbax — Fri, 31 Jul 2026 06:09:46 GMT

← Older revision		Revision as of 00:09, 31 July 2026
Line 1:		Line 1:
	[[Category:Meetings]]		[[Category:Meetings]]

	What format do we use to name things		What format do we use to name things?

			Talk about how the packet side will get an interrupt handled (possibly with a timer just checking every so often if DAC is not busy once armed)

			Talk about the DAC flow (arming and just letting it go until it's not busy)

			Having the struct be passed along

Itinerary

Nelson — Fri, 31 Jul 2026 05:58:30 GMT

Created page with "Category:Meetings What format do we use to name things"

New page

[[Category:Meetings]]

What format do we use to name things

ADC

Nelson — Fri, 31 Jul 2026 05:04:10 GMT

Created page with "Category:Index https://en.wikipedia.org/wiki/Goertzel_algorithm"

New page

[[Category:Index]]

https://en.wikipedia.org/wiki/Goertzel_algorithm

2026 07 23-Meeting

Nelson — Fri, 31 Jul 2026 04:36:08 GMT

← Older revision		Revision as of 22:36, 30 July 2026
Line 10:		Line 10:
	Discussed wanting to do smaller things weekly		Discussed wanting to do smaller things weekly
	- Planning to try and finish the skeleton of the dac pathway below, by our meeting next friday at 11:30		- Planning to try and finish the skeleton of the dac pathway below, by our meeting next friday at 11:30

			[[File:2026_07_23-Meeting.png]]

2026 06 24-Meeting

Nelson — Fri, 31 Jul 2026 04:35:31 GMT

← Older revision		Revision as of 22:35, 30 July 2026
Line 2:		Line 2:

	Most of what was decided on was turned into The [[Protocol]] spec.		Most of what was decided on was turned into The [[Protocol]] spec.

			[[File:2026_06_24-Meeting.png]]

File:2026 07 23-Meeting.png

Nelson — Fri, 31 Jul 2026 04:32:43 GMT

Nelson uploaded File:2026 07 23-Meeting.png

New page

File:2026 06 24-Meeting.png

Nelson — Fri, 31 Jul 2026 04:27:29 GMT

Nelson uploaded File:2026 06 24-Meeting.png

New page

2026 06 24-Meeting

Nelson — Fri, 31 Jul 2026 04:18:19 GMT

Created page with "Category:Meetings Most of what was decided on was turned into *The* Protocol spec."

New page

[[Category:Meetings]]

Most of what was decided on was turned into *The* [[Protocol]] spec.

2026 07 23-Meeting

Nelson — Thu, 23 Jul 2026 22:43:30 GMT

← Older revision		Revision as of 16:43, 23 July 2026
Line 1:		Line 1:
	[[Category:Meetings]]		[[Category:Meetings]]

	~~Beans!~~		Discussed how the radio side should be structured
			- Protocol block will call `int frame_packet(unframed_packet* data_source, framed_packet* data_dest) {` after writing message data into data_source
			- Frame packet will split by MTU, frame each, and schedule the dac interupt
			- ADC's raw data buffer needs to be decoded often, we're really memory limited here

			- We're going to allocate everything once at the start of main, then propigate the pointers down. This way we only need to allocate big things once, and the rest can just chill

			Discussed wanting to do smaller things weekly
			- Planning to try and finish the skeleton of the dac pathway below, by our meeting next friday at 11:30

Category:Meetings

Nelson — Thu, 23 Jul 2026 22:11:20 GMT

← Older revision		Revision as of 16:11, 23 July 2026
Line 1:		Line 1:
			[[Category:Index]]
	Meeting Logs		Meeting Logs

Category:Meetings

Nelson — Thu, 23 Jul 2026 22:10:24 GMT

Created page with "Meeting Logs"

New page

Meeting Logs

Meetings

Nelson — Thu, 23 Jul 2026 22:09:13 GMT

Created page with "See https://ratpack.ece.utah.edu/index.php/Category:Meetings"

New page

See https://ratpack.ece.utah.edu/index.php/Category:Meetings

2026 07 23-Meeting

Nelson — Thu, 23 Jul 2026 22:08:53 GMT

Created page with "Category:Meetings Beans!"

New page

[[Category:Meetings]]

Beans!

Protocol

Bean — Sun, 12 Jul 2026 21:58:57 GMT

Scheme-Plan yes-yes :3

← Older revision		Revision as of 15:58, 12 July 2026
Line 21:		Line 21:
	- One frame contains a preamble, header, packet/packet part, footer		- One frame contains a preamble, header, packet/packet part, footer

	=== ~~Preamble~~ ===		=== Preramble ===
	- More than a standard bit string, could just stop transmitting within the block. This will allow the reciever to calibrate their bit width offset		- More than a standard bit string, could just stop transmitting within the block. This will allow the reciever to calibrate their bit width offset
	- All messages start this way in some fashion		- All messages start this way in some fashion