BATC Video Source - Revision history

G8GKQ at 09:58, 19 June 2023

2023-06-19T09:58:38Z

M0YDH: Assembly link and 2 photos

2021-02-01T18:05:05Z

Assembly link and 2 photos

G8GKQ: /* General */

2020-12-16T14:25:28Z

General

G8GKQ: /* Inserting New Images */

2020-12-16T14:24:27Z

Inserting New Images

G8GKQ: /* General */

2020-12-16T14:22:03Z

General

G8GKQ: /* Inserting New Images */

2020-12-16T13:37:24Z

Inserting New Images

G8GKQ: /* Inserting New Images */

2020-12-16T13:36:54Z

Inserting New Images

G8GKQ at 13:36, 16 December 2020

2020-12-16T13:36:22Z

G8GKQ at 13:35, 16 December 2020

2020-12-16T13:35:40Z

G8GKQ: Created page with "The BATC Video Source, based on a Raspberry Pi Zero or later models (but not the Raspberry Pi 4), was published in CQ-TV 270. It was based on an earlier (now unsupported) ver..."

2020-12-15T21:51:25Z

Created page with "The BATC Video Source, based on a Raspberry Pi Zero or later models (but not the Raspberry Pi 4), was published in CQ-TV 270. It was based on an earlier (now unsupported) ver..."

New page

The BATC Video Source, based on a Raspberry Pi Zero or later models (but not the Raspberry Pi 4), was published in CQ-TV 270.

It was based on an earlier (now unsupported) version by G4EWJ described here [[RPi Test Card]].

@@ Line 3: / Line 3: @@
 It was based on an earlier (now unsupported) version by G4EWJ described here: [[RPi Test Card]].
-The information below is provided to help advanced users to customise their VideoSource.  Please refer to the original CQ-TV article for construction details.
+===Capabilities===
-===General===
+Using a Raspberry Pi 1, 2 or 3, or a Pi Zero or a Pi Zero W, this video source will output a PAL static test card, or a test card with a moving banner and bouncing balls, from the composite video output.  Test card F can be overlayed with a programmable callsign.  Additionally, a Contest Card is available.
 All the files used to customise the display are in the folder /boot/testcard.  This folder can be accessed directly on the card if you log in by SSH on a network-connected Raspberry Pi (not a Pi Zero on its own), or as the boot volume if you read the card on a Windows PC.  The files are owned by root, so the use of sudo is required to edit them by ssh.

@@ Line 3: / Line 3: @@
 It was based on an earlier (now unsupported) version by G4EWJ described here: [[RPi Test Card]].
-The information below is provided to help advanced users to customise their VideoSource.  Please refer to the orriginal CQ-TV article for construction details.
+The information below is provided to help advanced users to customise their VideoSource.  Please refer to the original CQ-TV article for construction details.
 ===General===
@@ Line 38: / Line 38: @@
 Current consumption of a Raspberry Pi Zero running the test card is about 150 mA, which increaes to 190 mA if the camera is selected.

@@ Line 9: / Line 9: @@
 All the files used to customise the display are in the folder /boot/testcard.  This folder can be accessed directly on the card if you log in by SSH on a network-connected Raspberry Pi (not a Pi Zero on its own), or as the boot volume if you read the card on a Windows PC.  The files are owned by root, so the use of sudo is required to edit them by ssh.
-On start-up, if the previous banner text on the second and third slides included the text "BATC" or "IO90LU", the callsign.txt and locator.txt files are read and the banners are changed to "''callsign at locator''".  This enables all the callsigns on the card to be initialised simply by setting the callsign.txt file correctly.
+On start-up, if the previous banner text on the second and third slides include the text "BATC" or "IO90LU", the callsign.txt and locator.txt files are read and the banners are changed to "''callsign at locator''".  This enables all the callsigns on the card to be initialised simply by setting the callsign.txt file correctly.
 Also on start-up, the text in "callsign.txt" is convereted to an image and superimposed on the Test Card F used in the first slide.  The same text is also stored for use as a camera caption.

@@ Line 26: / Line 26: @@
 The number in the filename determines the sequence that the card is displayed in; for example the card specified in tcdata10.txt will be displayed in the 10th button push after the first card.
-The first line must be tcprog.
+ The first line must be tcprog.
-The second line is the filename of the .jpg image to be displayed, without the .jpg extension.
+Be careful to edit the file in a true text editor.  Microsoft Word and Wordpad introduce special characters that will cause the file to not work.  Use Notepad, or Notepad++.
-The third line is the x displacement of the bottom left of the card.  This should be 40 for cards with a banner and 0 for cards filling the screen.
+===Current Consumption===
-The fourth line is the y displacement of the bottom left of the card.  This should be 52 for cards with a banner and 0 for cards filling the screen.
+Current consumption of a Raspberry Pi Zero running the test card is about 150 mA, which increaes to 190 mA if the camera is selected.

@@ Line 9: / Line 9: @@
 All the files used to customise the display are in the folder /boot/testcard.  This folder can be accessed directly on the card if you log in by SSH on a network-connected Raspberry Pi (not a Pi Zero on its own), or as the boot volume if you read the card on a Windows PC.  The files are owned by root, so the use of sudo is required to edit them by ssh.
-After boot, if the previous banner text on the second and third slides included the text "BATC" or "IO90LU", the callsign.txt and locator.txt files are read and the banners are changed to "''callsign at locator''".  This enables all the callsigns on the card to be initialised simply by setting the callsign.txt file correctly.
+On start-up, if the previous banner text on the second and third slides included the text "BATC" or "IO90LU", the callsign.txt and locator.txt files are read and the banners are changed to "''callsign at locator''".  This enables all the callsigns on the card to be initialised simply by setting the callsign.txt file correctly.
 ===Inserting New Images===

@@ Line 32: / Line 32: @@
 The fourth line is the y displacement of the bottom left of the card.  This should be 52 for cards with a banner and 0 for cards filling the screen.
-The sixth line is the text for the "bubbles".  A maximum of 5 characters.  Some special characters such as "-/P-" can be displayed (try it).
+The fifth line is the text for the "bubbles".  A maximum of 5 characters.  Some special characters such as "-/P-" can be displayed (try it).
-The seventh line is the text for the scrolling banner.
+The sixth line is the text for the scrolling banner.
 Be careful to edit the file in a true text editor.  Microsoft Word and Wordpad introduce special characters that will cause the file to not work.  Use Notepad, or Notepad++.

@@ Line 8: / Line 8: @@
 All the files used to customise the display are in the folder /boot/testcard.  This folder can be accessed directly on the card if you log in by SSH on a network-connected Raspberry Pi (not a Pi Zero on its own), or as the boot volume if you read the card on a Windows PC.  The files are owned by root, so the use of sudo is required to edit them by ssh.
 After boot, if the previous banner text on the second and third slides included the text "BATC" or "IO90LU", the callsign.txt and locator.txt files are read and the banners are changed to "''callsign at locator''".  This enables all the callsigns on the card to be initialised simply by setting the callsign.txt file correctly.
@@ Line 15: / Line 13: @@
 ===Inserting New Images===
-Each image needs to be accompanied by a text file named in sequence like tcdata10.txt and containing:
+Additional image files without a banner should be 720x576 .jpg files, and those for use with a banner should be 640x480.  Each image needs to be accompanied by a text file named in sequence like tcdata10.txt and containing:
   tcprog

← Older revision		Revision as of 13:35, 16 December 2020
Line 1:		Line 1:
	The BATC Video Source, based on a Raspberry Pi Zero or later models (but not the Raspberry Pi 4), was published in CQ-TV 270.		The BATC Video Source, based on a Raspberry Pi Zero or later models (but not the Raspberry Pi 4), was published in CQ-TV 270.

−	It was based on an earlier (now unsupported) version by G4EWJ described here [[RPi Test Card]].	+	It was based on an earlier (now unsupported) version by G4EWJ described here: [[RPi Test Card]].
		+
		+	The information below is provided to help advanced users to customise their VideoSource. Please refer to the orriginal CQ-TV article for construction details.
		+
		+	===General===
		+
		+	All the files used to customise the display are in the folder /boot/testcard. This folder can be accessed directly on the card if you log in by SSH on a network-connected Raspberry Pi (not a Pi Zero on its own), or as the boot volume if you read the card on a Windows PC. The files are owned by root, so the use of sudo is required to edit them by ssh.
		+
		+	Additional image files without a banner should be 720x576 .jpg files, and those for use with a banner should be 640x480.
		+
		+	After boot, if the previous banner text on the second and third slides included the text "BATC" or "IO90LU", the callsign.txt and locator.txt files are read and the banners are changed to "''callsign at locator''". This enables all the callsigns on the card to be initialised simply by setting the callsign.txt file correctly.
		+
		+	===Inserting New Images===
		+
		+	Each image needs to be accompanied by a text file named in sequence like tcdata10.txt and containing:
		+
		+	tcprog
		+	testcard640
		+	40
		+	52
		+	CQ
		+	G8GKQ in IO91CC
		+
		+	The number in the filename determines the sequence that the card is displayed in; for example the card specified in tcdata10.txt will be displayed in the 10th button push after the first card.
		+
		+	The first line must be tcprog.
		+
		+	The second line is the filename of the .pjg image to be displayed, without the .jpg extension.
		+
		+	The third line is the x displacement of the bottom left of the card. This should be 40 for cards with a banner and 0 for cards filling the screen.
		+
		+	The fourth line is the y displacement of the bottom left of the card. This should be 52 for cards with a banner and 0 for cards filling the screen.
		+
		+	The sixth line is the text for the "bubbles". A maximum of 5 characters. Some special characters such as "-/P-" can be displayed (try it).
		+
		+	The seventh line is the text for the scrolling banner.
		+
		+	Be careful to edit the file in a true text editor. Microsoft Word and Wordpad introduce special characters that will cause the file to not work. Use Notepad, or Notepad++.