MeshCore - Revision history

Jschrempp: /* V17.0 Notes */

2026-08-09T14:43:36Z

V17.0 Notes

← Older revision		Revision as of 10:43, 9 August 2026
Line 44:		Line 44:
	:FEM LNA was turned off in 1.16		:FEM LNA was turned off in 1.16
	:set radio.fem.rxgain off		:set radio.fem.rxgain off
	:However, "The 'set radio.fem.rxgain off' setting is not persisted. After a reboot the rxgain is back to on. This should be persisted." See [https://github.com/meshcore-dev/MeshCore/issues/3150 Github issue.]		:However, "The 'set radio.fem.rxgain off' setting is not persisted. After a reboot the rxgain is back to on. This should be persisted." See [https://github.com/meshcore-dev/MeshCore/issues/3150 Github issue 3150.] [https://github.com/meshcore-dev/MeshCore/pull/3137 issue 3157]

	=== Random Things ===		=== Random Things ===

Jschrempp: /* V17.0 Notes */

2026-08-09T14:35:56Z

V17.0 Notes

← Older revision		Revision as of 10:35, 9 August 2026
Line 44:		Line 44:
	:FEM LNA was turned off in 1.16		:FEM LNA was turned off in 1.16
	:set radio.fem.rxgain off		:set radio.fem.rxgain off
	:However, "The 'set radio.fem.rxgain off' setting is not persisted. After a reboot the rxgain is back to on. This should be persisted." See [https://github.com/meshcore-dev/MeshCore/issues/~~3145#issuecomment-5231394102~~ Github issue.]		:However, "The 'set radio.fem.rxgain off' setting is not persisted. After a reboot the rxgain is back to on. This should be persisted." See [https://github.com/meshcore-dev/MeshCore/issues/3150 Github issue.]

	=== Random Things ===		=== Random Things ===

Jschrempp: /* V17.0 Notes */

2026-08-09T14:34:07Z

V17.0 Notes

← Older revision		Revision as of 10:34, 9 August 2026
Line 44:		Line 44:
	:FEM LNA was turned off in 1.16		:FEM LNA was turned off in 1.16
	:set radio.fem.rxgain off		:set radio.fem.rxgain off
			:However, "The 'set radio.fem.rxgain off' setting is not persisted. After a reboot the rxgain is back to on. This should be persisted." See [https://github.com/meshcore-dev/MeshCore/issues/3145#issuecomment-5231394102 Github issue.]

	=== Random Things ===		=== Random Things ===

Jschrempp: /* Misc Info */

2026-08-09T14:32:25Z

Misc Info

← Older revision		Revision as of 10:32, 9 August 2026
Line 38:		Line 38:

	== Misc Info ==		== Misc Info ==

			=== V17.0 Notes ===

			The Heltec V4 reported a much higher noise floor after update from v16 to v17.0. The suggestion was:
			:FEM LNA was turned off in 1.16
			:set radio.fem.rxgain off

	=== Random Things ===		=== Random Things ===

Jschrempp: /* Repeaters */

2026-07-29T02:37:32Z

Repeaters

← Older revision		Revision as of 22:37, 28 July 2026
Line 71:		Line 71:
	=== Repeaters ===		=== Repeaters ===
	: Adverts are sent by repeaters just to help the analysis of the mesh. We could have the entire mesh set up without repeater adverts and it would work fine.		: Adverts are sent by repeaters just to help the analysis of the mesh. We could have the entire mesh set up without repeater adverts and it would work fine.
	: You ~~used to worry about using the same key prefix of someone near you. You would admin via your companion to set an unused prefix.~~ [https://~~analyzer~~.~~letsmesh.net~~/~~nodes~~/~~prefix-utilization Prefix Utilization grid~~]~~. But router prefix collisions do not affect message delivery, just the effectiveness of off-line mesh analysis. So it was polite to pick an unused prefix.~~		: Setup Advice
	~~: As of 1.14 multi-byte path support makes this unnecessary. Instead, use any two digit prefix you want to generate your repeater's keys. Connect to your repeater and '''set path.hash.mode 1'''~~		: You can't do better than [https://bayareameshcore.org/repeater-setup/ this]
	~~: (Leave your companion at the default 1-byte support until all the routers in your area are up on 1.14 or later.)~~
	~~: set advert.interval 240 (for 0 hop adverts, in minutes)~~
	~~: set prv.key <key>~~
	: set owner.info <info>		: set owner.info <info>
	: for a G2 - set agc.reset.interval 4		: for a G2 - set agc.reset.interval 4
	: Paths both ways get cached and if a route is bad you might get a message to the destination but the ack may not get back. If you have a repeater you own in the path force a flood by hard pressing the logon button. The path back might still be wrong so go to the console and send “reboot” 3 times … you don’t need a confirmation just spam it 3 times		: Paths both ways get cached and if a route is bad you might get a message to the destination but the ack may not get back. If you have a repeater you own in the path force a flood by hard pressing the logon button. The path back might still be wrong so go to the console and send “reboot” 3 times … you don’t need a confirmation just spam it 3 times
	: Outdoor node. [https://store.rokland.com/products/wismesh-repeater-mini-reliable-coverage-expansion-for-smart-networks This is a nice one.]		: Outdoor node. [https://store.rokland.com/products/wismesh-repeater-mini-reliable-coverage-expansion-for-smart-networks This is a nice one.]
	: Duty Cycle. Can be set in 1.16+. After each transmission, the repeater enforces a silent period proportional to the on-air time. You are responsible for choosing a value appropriate for your jurisdiction (e.g. EU 868 MHz requires 10% duty cycle).
	~~: set dutycycle 80~~
	: Loop Prevention. If a path has a loop in it (1a, e6, 9f, e6, 9f, 2c) messages loop around. In single byte paths this kind of thing might be legitimate because different routers could have the same byte id. Going to two or three byte path modes makes these collisions unlikely. Repeaters can be set to stop loops with loop.detect. The values show how many times a given id is allowed in a path. For example, minimal allows 4 duplicates in a 1-byte path, 2 duplicates in a 2-byte path, and no duplicates in a 3-byte path: minimal is 4,2,1; moderate is 2,1,1; strict is 1,1,1.		: Loop Prevention. If a path has a loop in it (1a, e6, 9f, e6, 9f, 2c) messages loop around. In single byte paths this kind of thing might be legitimate because different routers could have the same byte id. Going to two or three byte path modes makes these collisions unlikely. Repeaters can be set to stop loops with loop.detect. The values show how many times a given id is allowed in a path. For example, minimal allows 4 duplicates in a 1-byte path, 2 duplicates in a 2-byte path, and no duplicates in a 3-byte path: minimal is 4,2,1; moderate is 2,1,1; strict is 1,1,1.
	: set loop.detect moderate		: set loop.detect moderate

Jschrempp: /* Repeaters */

2026-07-18T15:09:51Z

Repeaters

← Older revision		Revision as of 11:09, 18 July 2026
Line 81:		Line 81:
	: Outdoor node. [https://store.rokland.com/products/wismesh-repeater-mini-reliable-coverage-expansion-for-smart-networks This is a nice one.]		: Outdoor node. [https://store.rokland.com/products/wismesh-repeater-mini-reliable-coverage-expansion-for-smart-networks This is a nice one.]
	: Duty Cycle. Can be set in 1.16+. After each transmission, the repeater enforces a silent period proportional to the on-air time. You are responsible for choosing a value appropriate for your jurisdiction (e.g. EU 868 MHz requires 10% duty cycle).		: Duty Cycle. Can be set in 1.16+. After each transmission, the repeater enforces a silent period proportional to the on-air time. You are responsible for choosing a value appropriate for your jurisdiction (e.g. EU 868 MHz requires 10% duty cycle).
	: set dutycycle 50		: set dutycycle 80
			: Loop Prevention. If a path has a loop in it (1a, e6, 9f, e6, 9f, 2c) messages loop around. In single byte paths this kind of thing might be legitimate because different routers could have the same byte id. Going to two or three byte path modes makes these collisions unlikely. Repeaters can be set to stop loops with loop.detect. The values show how many times a given id is allowed in a path. For example, minimal allows 4 duplicates in a 1-byte path, 2 duplicates in a 2-byte path, and no duplicates in a 3-byte path: minimal is 4,2,1; moderate is 2,1,1; strict is 1,1,1.
			: set loop.detect moderate

	==== About Two Byte Routing ====		==== About Two Byte Routing ====

Jschrempp: /* MeshCore */

2026-07-05T20:19:48Z

MeshCore

← Older revision		Revision as of 16:19, 5 July 2026
Line 6:		Line 6:

	MeshCore is an open source mesh network that runs on top of [[Mesh_Networks\|LoRa radio technology]]. It is low bandwidth and only suitable for text messaging. It is also very low power and long range (10's of miles) line-of-sight. It is different from [[Meshtastic]] in that it relies on dedicated repeater hardware. This hardware is still owned by individuals and deployed as they see fit. Because Meshcore repeaters are dedicated devices they tend to stay in one place and can be used to route messages instead of always flooding a message.		MeshCore is an open source mesh network that runs on top of [[Mesh_Networks\|LoRa radio technology]]. It is low bandwidth and only suitable for text messaging. It is also very low power and long range (10's of miles) line-of-sight. It is different from [[Meshtastic]] in that it relies on dedicated repeater hardware. This hardware is still owned by individuals and deployed as they see fit. Because Meshcore repeaters are dedicated devices they tend to stay in one place and can be used to route messages instead of always flooding a message.

			There is a Python version that runs on RPi class hardware. Called [https://docs.openhop.dev/projects/openhop-core/ OpenHop]

	== Documentation ==		== Documentation ==

Jschrempp: /* MeshCore */

2026-06-30T17:54:30Z

MeshCore

← Older revision		Revision as of 13:54, 30 June 2026
Line 3:		Line 3:
	As we gather more tips, we'll reformat this page to be more cogent.		As we gather more tips, we'll reformat this page to be more cogent.

	~~(We have information on~~ [[Mesh_Networks\|~~other mesh networks~~]] ~~too~~.)		If you want to know about LoRa radio things, go [[Mesh_Networks\|here]].

	MeshCore is an open source mesh network that runs on top of [[Mesh_Networks\|LoRa radio technology]]. It is low bandwidth and only suitable for text messaging. It is also very low power and long range (10's of miles) line-of-sight. It is different from [[Meshtastic]] in that it relies on dedicated repeater hardware. This hardware is still owned by individuals and deployed as they see fit. Because Meshcore repeaters are dedicated devices they tend to stay in one place and can be used to route messages instead of always flooding a message.		MeshCore is an open source mesh network that runs on top of [[Mesh_Networks\|LoRa radio technology]]. It is low bandwidth and only suitable for text messaging. It is also very low power and long range (10's of miles) line-of-sight. It is different from [[Meshtastic]] in that it relies on dedicated repeater hardware. This hardware is still owned by individuals and deployed as they see fit. Because Meshcore repeaters are dedicated devices they tend to stay in one place and can be used to route messages instead of always flooding a message.

Jschrempp: /* Unexplained Things */

2026-06-26T00:25:52Z

Unexplained Things

← Older revision		Revision as of 20:25, 25 June 2026
Line 144:		Line 144:
	== Unexplained Things ==		== Unexplained Things ==

	* All contacts not in contacts list.		None at this time. Add an item if you can't find the answer.
	~~: With a Heltec V4 on 1.14.0 and iOS app. I see 146 contacts in my Contacts list. When I go to Discover Contacts I see 270 contacts; the ones not in my contact list have~~ an ~~"add" button. In Settings > Contacts I have set to Add All and Overwrite Oldest. Why aren~~'t ~~all~~ the ~~contacts in my Contacts list?~~

	== Open Questions ==		== Open Questions ==

Jschrempp: /* Hardware */

2026-06-26T00:21:48Z

Hardware

← Older revision		Revision as of 20:21, 25 June 2026
Line 45:		Line 45:

	=== Hardware ===		=== Hardware ===
	~~For a~~ G2~~, transmit~~ power of 10 = 1 watt		==== Station G2 ====
	~~For~~ a Heltec V4~~, transmit~~ power of 22 = 650 mw		Transmit power of 10 = 1 watt

			If the G2 experiences a brief power outage it will come back in a low power state (all the LEDs are not lit up). Power it down for 60 seconds or so, then power it up.

			The G2 pulls a lot of power. Make sure you have a USB power supply that can supply the current - the inexpensive ones will not and the three LEDs will not light up, showing that the power amplifier is not working.

			Update a G2 over WiFi:
			1) download the non merged firmware binary on your phone or computer. Do this with [https://flasher.meshcore.io flasher.meshcore.io]
			2) connect to a companion and then log in to the repeater via the mesh
			3) open the command line and type "start ota" - note the web address provided. The G2 will become a WiFi access point.
			4) on phone or computer, connect to the Meshcore-OTA wifi
			5) use a browser to go to the provided web address from step 3
			6) choose the binary file downloaded in step 1 - it will reboot automatically

			==== Heltec V4 ====
			Transmit power of 22 = 650 mW

	The V4 doesn’t reboot after losing power without a physical reset button press.		The V4 doesn’t reboot after losing power without a physical reset button press.

			Make sure you have a USB power supply that can supply the current - the inexpensive ones will not. You won't know it, but you won't be transmitting at 650 mW. You can see this yourself with a USB current monitor. Hook it up and then send a message. You should see the current jump up considerably. If not, your power supply is not strong enough.

	=== Repeaters ===		=== Repeaters ===