Skip - Revision history

Kartoffel: Lijstje

2020-02-09T16:48:23Z

Lijstje

← Older revision		Revision as of 16:48, 9 February 2020
Line 5:		Line 5:
	\|Picture=SkipGuts.jpg		\|Picture=SkipGuts.jpg
	}}		}}

			{{Skipknoppenlijstje}}

	= Skip =		= Skip =

Bertrik Sikken at 21:28, 28 July 2017

2017-07-28T21:28:54Z

← Older revision		Revision as of 21:28, 28 July 2017
Line 11:		Line 11:
	== Status ==		== Status ==
	Status (most recent first):		Status (most recent first):
	* 2017-07-28([[bertrik]]): replaced the physical button by an elevator button, the button does not really that well in the case but does seem to work. Wireless transmission seems to work fine too, pressing the button gives several 534B4950 messages over the serial output. We can't figure out which script is supposed to listen to this message and perform the actual skip action towards the media player.		* 2017-07-28([[bertrik]]): replaced the physical button by an elevator button, the button does not fit really that well in the case but does seem to work. Wireless transmission seems to work fine too, pressing the button gives several 534B4950 messages over the serial output. We can't figure out which script is supposed to listen to this message and perform the actual skip action towards the media player.
	* 2017-06-18 ([[bertrik]]): Skip is currently not operational. It appears the button itself is a bit flaky, the contact is not super reliable. I cloned the git repo and made some changes such that at least it compiles without tricks (put the .ino in a directory of the same name to satisfy Arduino IDE, applied consistent indenting). I cannot reproduce the problem on the receiver side where at some point it stops receiving SKIPs, but it does often receive multiple SKIPs (but that appears intentional). I used the [https://github.com/gcopeland/RF24 gcopeland fork of the RF24 library].		* 2017-06-18 ([[bertrik]]): Skip is currently not operational. It appears the button itself is a bit flaky, the contact is not super reliable. I cloned the git repo and made some changes such that at least it compiles without tricks (put the .ino in a directory of the same name to satisfy Arduino IDE, applied consistent indenting). I cannot reproduce the problem on the receiver side where at some point it stops receiving SKIPs, but it does often receive multiple SKIPs (but that appears intentional). I used the [https://github.com/gcopeland/RF24 gcopeland fork of the RF24 library].

Bertrik Sikken: update 2017-07-28

2017-07-28T19:52:48Z

update 2017-07-28

← Older revision		Revision as of 19:52, 28 July 2017
Line 11:		Line 11:
	== Status ==		== Status ==
	Status (most recent first):		Status (most recent first):
			* 2017-07-28([[bertrik]]): replaced the physical button by an elevator button, the button does not really that well in the case but does seem to work. Wireless transmission seems to work fine too, pressing the button gives several 534B4950 messages over the serial output. We can't figure out which script is supposed to listen to this message and perform the actual skip action towards the media player.
	* 2017-06-18 ([[bertrik]]): Skip is currently not operational. It appears the button itself is a bit flaky, the contact is not super reliable. I cloned the git repo and made some changes such that at least it compiles without tricks (put the .ino in a directory of the same name to satisfy Arduino IDE, applied consistent indenting). I cannot reproduce the problem on the receiver side where at some point it stops receiving SKIPs, but it does often receive multiple SKIPs (but that appears intentional). I used the [https://github.com/gcopeland/RF24 gcopeland fork of the RF24 library].		* 2017-06-18 ([[bertrik]]): Skip is currently not operational. It appears the button itself is a bit flaky, the contact is not super reliable. I cloned the git repo and made some changes such that at least it compiles without tricks (put the .ino in a directory of the same name to satisfy Arduino IDE, applied consistent indenting). I cannot reproduce the problem on the receiver side where at some point it stops receiving SKIPs, but it does often receive multiple SKIPs (but that appears intentional). I used the [https://github.com/gcopeland/RF24 gcopeland fork of the RF24 library].

	Next steps:		Next steps:
	* Investigate whether the actual button inside Skip indeed has a problem, then fix or perhaps replace it
	* Connect the receiver up to the Linux box thing again		* Connect the receiver up to the Linux box thing again

Bertrik Sikken at 06:43, 26 June 2017

2017-06-26T06:43:40Z

← Older revision		Revision as of 06:43, 26 June 2017
Line 14:		Line 14:

	Next steps:		Next steps:
	* Investigate the ~~skip~~ button ~~itself~~, fix or perhaps replace ~~the big red button~~		* Investigate whether the actual button inside Skip indeed has a problem, then fix or perhaps replace it
	* Connect the receiver up to the Linux box thing again		* Connect the receiver up to the Linux box thing again

Bertrik Sikken at 18:16, 25 June 2017

2017-06-25T18:16:45Z

← Older revision		Revision as of 18:16, 25 June 2017
Line 11:		Line 11:
	== Status ==		== Status ==
	Status (most recent first):		Status (most recent first):
	* 2017-06-18 ([[bertrik]]): Skip is currently not operational. It appears the button itself is a bit flaky, the contact is not super reliable. I cloned the git repo and made some changes such that at least it compiles without tricks (put the .ino in a directory of the same name to satisfy Arduino IDE, applied consistent indenting). I cannot reproduce the problem on the receiver side where at some point it stops receiving SKIPs, but it does often receive multiple SKIPs (but that appears intentional). I used the [https://github.com/gcopeland/RF24 gcopeland fork of the ~~nrf24~~ library].		* 2017-06-18 ([[bertrik]]): Skip is currently not operational. It appears the button itself is a bit flaky, the contact is not super reliable. I cloned the git repo and made some changes such that at least it compiles without tricks (put the .ino in a directory of the same name to satisfy Arduino IDE, applied consistent indenting). I cannot reproduce the problem on the receiver side where at some point it stops receiving SKIPs, but it does often receive multiple SKIPs (but that appears intentional). I used the [https://github.com/gcopeland/RF24 gcopeland fork of the RF24 library].

	Next steps:		Next steps:

Bertrik Sikken at 16:35, 25 June 2017

2017-06-25T16:35:56Z

← Older revision		Revision as of 16:35, 25 June 2017
Line 11:		Line 11:
	== Status ==		== Status ==
	Status (most recent first):		Status (most recent first):
	* 2017-06-18: Skip is currently not operational. It appears the button itself is a bit flaky, the contact is not super reliable. I cloned the git repo and made some changes such that at least it compiles without tricks (put the .ino in a directory of the same name to satisfy Arduino IDE, applied consistent indenting). I cannot reproduce the problem on the receiver side where at some point it stops receiving SKIPs, but it does often receive multiple SKIPs ~~often~~ (but that appears intentional).		* 2017-06-18 ([[bertrik]]): Skip is currently not operational. It appears the button itself is a bit flaky, the contact is not super reliable. I cloned the git repo and made some changes such that at least it compiles without tricks (put the .ino in a directory of the same name to satisfy Arduino IDE, applied consistent indenting). I cannot reproduce the problem on the receiver side where at some point it stops receiving SKIPs, but it does often receive multiple SKIPs (but that appears intentional). I used the [https://github.com/gcopeland/RF24 gcopeland fork of the nrf24 library].

	Next steps:		Next steps:

Bertrik Sikken: Update Skip status

2017-06-25T16:27:06Z

Update Skip status

← Older revision		Revision as of 16:27, 25 June 2017
Line 8:		Line 8:
	= Skip =		= Skip =
	Skip annoying music with the skip button.		Skip annoying music with the skip button.

			== Status ==
			Status (most recent first):
			* 2017-06-18: Skip is currently not operational. It appears the button itself is a bit flaky, the contact is not super reliable. I cloned the git repo and made some changes such that at least it compiles without tricks (put the .ino in a directory of the same name to satisfy Arduino IDE, applied consistent indenting). I cannot reproduce the problem on the receiver side where at some point it stops receiving SKIPs, but it does often receive multiple SKIPs often (but that appears intentional).

			Next steps:
			* Investigate the skip button itself, fix or perhaps replace the big red button
			* Connect the receiver up to the Linux box thing again

	== Operation ==		== Operation ==

Bertrik Sikken at 16:25, 15 June 2017

2017-06-15T16:25:31Z

← Older revision		Revision as of 16:25, 15 June 2017
Line 30:		Line 30:
	* automatic ACK is disabled		* automatic ACK is disabled
	* dynamic playload size is enabled		* dynamic playload size is enabled
	* ~~frequency/~~channel?		* channel 76 (RF24 library default)
			* datarate 1 mbps (RF24 library default)
			* 16-bit CRC on (RF24 library default)

	Each message is sent several times in rapid succession, so the receiver should be prepared to handle duplicates.		Each message is sent several times in rapid succession, so the receiver should be prepared to handle duplicates.

Bertrik Sikken at 16:01, 15 June 2017

2017-06-15T16:01:02Z

← Older revision		Revision as of 16:01, 15 June 2017
Line 35:		Line 35:

	The message sent is structured as follows:		The message sent is structured as follows:
	* first byte contains the length of the rest of the message		* first byte contains the length of the rest of the message (not including this byte), 4 in the case of the "SKIP" message
	* next four bytes contain the type of message in uppercase ASCII (not 0-terminated), for example "SKIP"		* next four bytes contain the type of message in uppercase ASCII (not 0-terminated), for example "SKIP"
	* rest of the bytes are message-specific, no data in case of the "SKIP" message		* rest of the bytes are message-specific, no data in case of the "SKIP" message

Bertrik Sikken: Add headers, protocol description

2017-06-15T15:58:44Z

Add headers, protocol description

← Older revision		Revision as of 15:58, 15 June 2017
Line 6:		Line 6:
	}}		}}

			= Skip =
	Skip annoying music with the skip button.		Skip annoying music with the skip button.

	Operation:		== Operation ==
	;press: skip		;press: skip
	;press and hold (2 seconds): stop		;press and hold (2 seconds): stop
Line 20:		Line 21:
	* Uglier case, uglier button.		* Uglier case, uglier button.

	Software:		== Software ==
	* Daemon and button: https://github.com/Juerd/rf24skip		* Daemon and button: https://github.com/Juerd/rf24skip
	* Receiver: https://github.com/Juerd/rf24server		* Receiver: https://github.com/Juerd/rf24server

			=== Protocol ===
			We use the following settings for the nRF24L01+ module:
			* every device uses the same address, which is 0x0066996699ULL
			* automatic ACK is disabled
			* dynamic playload size is enabled
			* frequency/channel?

			Each message is sent several times in rapid succession, so the receiver should be prepared to handle duplicates.

			The message sent is structured as follows:
			* first byte contains the length of the rest of the message
			* next four bytes contain the type of message in uppercase ASCII (not 0-terminated), for example "SKIP"
			* rest of the bytes are message-specific, no data in case of the "SKIP" message

			== Updates ==
	See also the README files in the Git repositories.		See also the README files in the Git repositories.