AMX Mouse - Revision history

Phi2x: /* Links */

2025-02-19T07:40:19Z

‎Links

KSL at 10:38, 8 June 2024

2024-06-08T10:38:03Z

Phi2x: /* Pictures */

2024-06-05T23:57:26Z

‎Pictures

Phi2x: /* Pictures */

2024-06-05T23:56:07Z

‎Pictures

Arnoldemu: /* AMX Mouse Hardware Clones */

2015-08-23T13:07:04Z

‎AMX Mouse Hardware Clones

Deprecated: The each() function is deprecated. This message will be suppressed on further calls in /mnt/cpcwiki-httpdocs/includes/diff/DairikiDiff.php on line 434

Arnoldemu: /* Technical */

2015-08-23T13:01:30Z

‎Technical

Arnoldemu at 12:19, 23 August 2015

2015-08-23T12:19:22Z

Arnoldemu at 12:17, 23 August 2015

2015-08-23T12:17:35Z

Arnoldemu: /* Technical */

2015-08-23T12:16:13Z

‎Technical

Arnoldemu: /* Technical */

2015-08-23T12:14:18Z

‎Technical

← Older revision		Revision as of 07:40, 19 February 2025
Line 193:		Line 193:
	* [http://www.cpc-power.com/index.php?page=detail&num=4286 CPC game base from CPC Power]		* [http://www.cpc-power.com/index.php?page=detail&num=4286 CPC game base from CPC Power]

−	[[Category:Input Device]] [[Category:Peripherals]] [[Category:Manual~~]][[Category:Amstrad Products~~]]	+	[[Category:Input Device]] [[Category:Peripherals]] [[Category:Manual]]

@@ Line 173: / Line 173: @@
 * [[The Advanced OCP Art Studio]]
 * [[Cosmos|Cosmos]]
 == Download ==

@@ Line 158: / Line 158: @@
 <gallery>
-Amx mouse img1.jpg
+Amx mouse img1.jpg|Package
-Amx mouse img3.jpg
+Amx mouse img3.jpg|Top view
-Amx mouse img2.jpg
+Amx mouse img2.jpg|Mouse
 </gallery>

@@ Line 155: / Line 155: @@
 Image:AMX Mouse Connection Guide (photo by jrp king).jpg|Connection Guide
 Image:ACU8510-105.jpg|Advert (ACU Oct 1985)
 </gallery>

@@ Line 99: / Line 99: @@
 * [[PS2Mouse]] (DIY by Bryce)
-Moreover, the [[Dk'tronics Mouse Interface]] seems to be AMX compatible, too. (Not confirmed if it is really compatible, but the circuit looks very similar.) (though dk'tronics seems to support only one button, not three buttons.) (Tested 24.9.14 by user Spookspring does not appear to work at all)
+== Compatible mice/Interfaces ==
 == Other ways to connect a mouse to the CPC ==

← Older revision		Revision as of 13:01, 23 August 2015
Line 84:		Line 84:
	jp update_loop		jp update_loop

		+	Selecting the joystick for longer doesn't appear to change the value. The value is updated when the joystick is deselected.

	Contains the following ICs:		Contains the following ICs:

@@ Line 33: / Line 33: @@
 Note II: Looking at the photos, it seems that /joystick1 (keyb row 9 select) is wired to the multivibrator, so the mickey timings may be software controlled; accordingly, software would be required to deselect keyboard row 9 between each read.
-Confirmed: Software MUST deselect keyboard row 9 to read the mouse correctly.
+Confirmed: Software will select keyboard row 9 to read the mouse, but then MUST deselect it to read the mouse correctly.
 For example, the loop here doesn't work:

@@ Line 47: / Line 47: @@
   ld bc,&f792    ;; PPI port A input
   out (c),c
@@ Line 70: / Line 73: @@
   update_loop:
-  ld bc,&f649
+  ld bc,&f649    ;; select keyboard row 9 (joystick 0)
   out (c),c
   ld b,&f4
   in a,(c)
-  ld bc,&f640
+  ld bc,&f640    ;; deselect keyboard row 9 (by selecting keyboard row 0)
   out (c),c
   jp update_loop

@@ Line 13: / Line 13: @@
 == Technical ==
-The AMX Art software uses the CPC's 300Hz interrupt to read the joystick port (at least it tries to do that, while moving the mouse pointer, the software accidently disables IRQs, and so, misses some interrupts). This is giving it a relative low resolution of max 300 mickeys per second (or actually less, due to the missed IRQs).
+The AMX Art software uses the CPC's 300Hz interrupt to read joystick port 0 (at least it tries to do that, while moving the mouse pointer, the software accidently disables IRQs, and so, misses some interrupts). This is giving it a relative low resolution of max 300 mickeys per second (or actually less, due to the missed IRQs).
-The AMX Interface hardware basically converts the incoming mouse signals to joystick signals, issuing LOW pulses (per mickey) on the corresponding direction lines. The protocol is thus very simple (unlike modern RS232 and PS/2 mice, the hardware doesn't contain any motion counters).
+The AMX Interface hardware basically converts the incoming mouse signals to joystick 0 signals, issuing LOW pulses on the corresponding direction lines. The interface doesn't report anything for joystick 1 when connected to the CPC's joystick port (which provides both joystick 0 and joystick 1 input).
-   Row9.Bit0 Joy1up    LOW for 1/300s per mickey, when mouse moved up
+In addition the AMX mouse doesn't appear to clash with the keyboard.
-   Row9.Bit1 Joy1down  LOW for 1/300s per mickey, when mouse moved down
-   Row9.Bit2 Joy1left  LOW for 1/300s per mickey, when mouse moved left
+The protocol is thus very simple (unlike modern RS232 and PS/2 mice, the hardware doesn't contain any motion counters).
-   Row9.Bit3 Joy1right LOW for 1/300s per mickey, when mouse moved right
    Row9.Bit5 Joy1fire1 LOW when Right mouse button pressed
    Row9.Bit4 Joy1fire2 LOW when Left mouse button pressed
@@ Line 27: / Line 31: @@
 Note: The exact hardware timings are '''unknown''', the values "1/300s" in the above description assume that the AMX '''hardware''' timings were designed to match up with the 300Hz AMX '''software''' timings.
-Note II: Looking at the photos, it seems that /joystick1 (keyb row 9 select) is wired to the multivibrator, so the mickey timings may be software controlled; accordingly, software would be required to deselect keyb row 9 between each read.
+Note II: Looking at the photos, it seems that /joystick1 (keyb row 9 select) is wired to the multivibrator, so the mickey timings may be software controlled; accordingly, software would be required to deselect keyboard row 9 between each read.
 Contains the following ICs: