Fix Broken Images (#2)

* Update mode_layering.md Fix image link * Update steppers.md * Update slingshots.md * Update mma8451.md * Update showcreator.md * Update lights.md * Update flashers.md * Update optos.md * Update quad.md * Update points.md * Update easing.md * Update types.md * Update rectangle.md * Update servos.md * Update positioning.md * Update leds.md * Update bitmap_fonts.md * Update connection.md * Update i2c.md * Update connecting.md * Update opacity.md * Update split_screen.md * Update vari_targets.md * Update drivers.md * Update layers.md * Update smartmatrix.md * Update win_x64.md * Update win_x86.md * Update up_down_ramps.md * Update line.md * Update ellipse.md * Update lights_versus_leds.md * Update connecting.md * Update rollover_switches.md * Update stationary_targets.md * Update easing_config.md * Update power_entry.md * Update mechanical_switches.md * Update dmd.md * Update gamma_correction.md * Update smbus.md * Update center_post.md * Update config.md * Update service_and_door_switches.md * Update drop_target_bank.md * Update switches.md * Update dmd.md * Update adding_dot_look_to_lcd.md * Update drivers.md * Update skill_shot.md * Update classic_single_ball.md * Update switches_p3_roc.md * Update auto_manual.md * Update configuring_bonus.md * Update pololu_maestro.md * Update architecture.md * Update mechanical_no_switch.md * Update coil_fired.md * Update two_coil_one_switch.md * Update mechanical_with_switch.md * Update classic_single_ball_no_shooter_lane.md * Update media_controller.md * Update index.md * Update index.md * Update index.md * Update index.md * Update index.md * Update index.md * Update steppers.md * Update index.md * Update index.md * Update index.md * Update index.md * Update dmd_fonts.md
atummons · Oct 4, 2024 · 8f37f3f · 8f37f3f
1 parent d92d0dd
commit 8f37f3f
Show file tree

Hide file tree

Showing 74 changed files with 203 additions and 199 deletions.
diff --git a/docs/config/instructions/gamma_correction.md b/docs/config/instructions/gamma_correction.md
@@ -21,12 +21,12 @@ looks fully bright, and that 50% looks like 50%, etc. Here is a
 screenshot of a slide which has 16 bars which fade from off to fully
 white, in a more-or-less even fashion:
 
-![image](/config/images/good_gamma.png)
+![image](../images/good_gamma.png)
 
 However if you show this slide on your physical DMD with no gamma
 correction, it looks something like this:
 
-![image](/config/images/bad_gamma.png)
+![image](../images/bad_gamma.png)
 
 Even though the individual pixels are showing their "correct"
 brightness, the human eye can't really tell a different between 50% and

diff --git a/docs/game_design/mode_layering.md b/docs/game_design/mode_layering.md
@@ -81,7 +81,7 @@ default, the global mode starts when the base mode starts and the field
 mode starts when the global mode starts. As a result, the typical player
 turn starts with field mode (a.k.a. on an open playfield).
 
-![image](/game_design/images/mode_layering.png)
+![image](images/mode_layering.png)
 
 *Field and Mission modes are mutually exclusive:* the field mode stops
 when a mission mode starts, and starts again when the mission mode

diff --git a/docs/game_logic/ball_saves/center_post.md b/docs/game_logic/ball_saves/center_post.md
@@ -8,7 +8,7 @@ title: Center Post Ball Save
 Some machines have a mechanical ball save called center post. It pops up
 between the flippers and prevents the ball from draining.
 
-![image](/game_logic/images/center_post.jpg)
+![image](../images/center_post.jpg)
 
 Video about center posts:
 

diff --git a/docs/game_logic/bonus/configuring_bonus.md b/docs/game_logic/bonus/configuring_bonus.md
@@ -17,7 +17,7 @@ Even though the bonus mode is built-in, you'll still need to add a
 
 It should look something like this:
 
-![image](/game_logic/images/bonus_folder.png)
+![image](../images/bonus_folder.png)
 
 ## 2. Add the bonus mode to your machine-wide modes list
 

diff --git a/docs/game_logic/skill_shot.md b/docs/game_logic/skill_shot.md
@@ -176,7 +176,7 @@ the group posts `skill_shot_lit_hit` and `skill_shot_unlit_hit` when a
 unlit shot is hit. To prevent races between the two events we use a
 state_machine called `skill_shot_success` which has three states:
 
-![image](/game_logic/images/skill_shot_state_machine.png)
+![image](/docs/game_logic/images/skill_shot_state_machine.png)
 
 When the mode started it starts at `start`. Then when either
 `skill_shot_lit_hit` or `skill_shot_unlit_hit` are posted in transitions

diff --git a/docs/hardware/fast/switches.md b/docs/hardware/fast/switches.md
@@ -21,7 +21,7 @@ get with FAST hardware that is discussed here.
 When you're using FAST IO boards, switches plug into individual IO
 boards. Then the IO boards are connected together in a loop.
 
-![image](/hardware/images/fast-io-3208.png)
+![image](../images/fast-io-3208.png)
 
 The `number:` setting for each switch is its board's position number in
 the chain, then the dash, then the switch input number. Note that the

diff --git a/docs/hardware/lisy/connection.md b/docs/hardware/lisy/connection.md
@@ -17,7 +17,7 @@ Gottlieb CPU board with the "LISY1" board.
     details. Basically you replace the MPU with the LISY board. You can
     still play the original ROM using PinMAME on LISY.
 
-![image](/hardware/images/lisy80_board.jpg)
+![image](/docs/hardware/images/lisy80_board.jpg)
 
 More details can be found in the [LISY user
 manual](http://www.lisy80.com/english/documentation-lisy/).
@@ -44,7 +44,7 @@ b.  Run MPF on the LISY hardware directly ("master" mode).
 
 See the following image for an architecture overview:
 
-![image](/hardware/images/lisy_mpf_overview.jpg)
+![image](/docs/hardware/images/lisy_mpf_overview.jpg)
 
 If you want to run MPF on the LISY controller itself, set DIP 4
 (option1) and DIP 8 (autostart) to 'ON' and all other DIPs on that
@@ -63,7 +63,7 @@ with the host PC running MPF, set DIP 2 to 'ON' for network mode or
     order to be able to reboot, as it will power the Raspberry Pi over the
     USB connection.
 
-![image](/hardware/images/LISY_modes.png)
+![image](/docs/hardware/images/LISY_modes.png)
 
 ## 3. Configure your Game
 
@@ -130,7 +130,7 @@ needed, a "normal" USB charging cable (Micro-USB cable) will do the
 job. Once connected to the host computer, it will (hopefully) identify a
 new serial device. This is usually `COMX` on windows:
 
-![image](/hardware/images/lisy_windows_com_port.png)
+![image](/docs/hardware/images/lisy_windows_com_port.png)
 
 Or `/dev/ttyACMX` on Linux:
 

diff --git a/docs/hardware/lisy/index.md b/docs/hardware/lisy/index.md
@@ -44,7 +44,7 @@ b.  Run MPF on the LISY hardware directly ("master" mode).
 
 See the following image for an architecture overview:
 
-![image](/hardware/images/lisy_mpf_overview.jpg)
+![image](../images/lisy_mpf_overview.jpg)
 
 LISY can controll all features of your Gottlieb System1/80 machine. This
 includes:

diff --git a/docs/hardware/mma8451.md b/docs/hardware/mma8451.md
@@ -32,7 +32,7 @@ This will configure an MMA8451 on I2C bus 1 with address 0x1D (29
 decimal which is the default for this device). The exact numbering
 depends on your i2c platform.
 
-![image](/hardware/images/mma8451-i2c-usb-accelerometer.jpg)
+![image](images/mma8451-i2c-usb-accelerometer.jpg)
 
 The device in the picture is using
 [smbus on linux](smbus.md)

diff --git a/docs/hardware/multimorphic/connecting.md b/docs/hardware/multimorphic/connecting.md
@@ -14,7 +14,7 @@ Wiki](http://pinballmakers.com/wiki/index.php/P-ROC_Main_Page).
 
 If you got a P-Roc just connect it to your computer using USB.
 
-![image](/hardware/images/multimorphic_p_roc.png)
+![image](../images/multimorphic_p_roc.png)
 
 Then connect switches and driver according to the manual (see
 [leds](../../machines/index.md) for
@@ -28,20 +28,20 @@ it is connected correctly.
 
 If you got a P3-Roc just connect it to your computer using USB.
 
-![image](/hardware/images/multimorphic_p3_roc.png)
+![image](../images/multimorphic_p3_roc.png)
 
 Connect all your SW-16 boards to the switch bus and all your PD-16 and
 PD-8x8 boards to your driver bus. Use twisted wires but connect + to +
 and - to - on all nodes.
 
-![image](/hardware/images/multimorphic_p3_roc_wireing.jpg)
+![image](../images/multimorphic_p3_roc_wireing.jpg)
 
 [mpf hardware scan](../../running/commands/hardware.md) will show the firmware version and revision of your P3-Roc
 if it is connected correctly.
 
 ### SW-16
 
-![image](/hardware/images/multimorphic_SW-16.png)
+![image](../images/multimorphic_SW-16.png)
 
 Set a unique address on every SW-16 board on your bus. Those addresses
 can overlap with the driver addresses. It does not matter on which of
@@ -64,7 +64,7 @@ SW-16 boards found:
 
 ### PD-16/PD-8x8
 
-![image](/hardware/images/multimorphic_PD-16.png)
+![image](../images/multimorphic_PD-16.png)
 
 Set a unique address on every PD-16/PD-8x8 board on your bus. Those
 addresses can overlap with the switch addresses. However, they overlap
@@ -79,7 +79,7 @@ communication is one-way only.
 
 ### PD-LED
 
-![image](/hardware/images/multimorphic_PD-LED.png)
+![image](../images/multimorphic_PD-LED.png)
 
 Set a unique address on every PD-LED board on your bus. Those addresses
 can overlap with the switch addresses. However, they overlap with the

diff --git a/docs/hardware/multimorphic/dmd.md b/docs/hardware/multimorphic/dmd.md
@@ -14,7 +14,7 @@ The P-ROC can drive a traditional single-color pinball DMD via the
 14-pin DMD connector cable that's been in most pinball machines for the
 past 25 years, like this:
 
-![image](/hardware/images/display_mono_dmd.jpg)
+![image](../images/display_mono_dmd.jpg)
 
 !!! note
 
@@ -25,7 +25,7 @@ past 25 years, like this:
 
 ## 1. Connect your hardware
 
-![image](/hardware/images/physical_dmd_in_backbox.jpg)
+![image](../images/physical_dmd_in_backbox.jpg)
 
 ## 2. Add a physical DMD device entry
 

diff --git a/docs/hardware/multimorphic/i2c.md b/docs/hardware/multimorphic/i2c.md
@@ -12,7 +12,7 @@ Related Config File Sections:
 The P3-ROC contains an I2C port (J17) which is accessible to MPF. You
 can use this port to control any I2C-based device.
 
-![image](/hardware/images/multimorphic_p3_roc.png)
+![image](/docs/hardware/images/multimorphic_p3_roc.png)
 
 You need to connect SDA, SCL and ground. You may not need the 3.3V from
 the P3-ROC as your controller might be a different voltage (which you

diff --git a/docs/hardware/multimorphic/power_entry.md b/docs/hardware/multimorphic/power_entry.md
@@ -9,7 +9,7 @@ This board can be used to fan out your power rails. See
 [Voltages and Power in Pinball Machines](../voltages_and_power/index.md) for
 details.
 
-![image](/hardware/images/multimorphic_Power_Entry.png)
+![image](../images/multimorphic_Power_Entry.png)
 
 The Multimorphic Power Filter board serves four purposes. 1. It serves
 as a central connection point for 230V/110V AC and all your PSUs using

diff --git a/docs/hardware/multimorphic/switches_p3_roc.md b/docs/hardware/multimorphic/switches_p3_roc.md
@@ -22,7 +22,7 @@ itself. Instead, you add SW-16 boards which each have 16 direct switch
 inputs. (e.g. there is no switch matrix.) You can connect up to 16
 SW-16s to support as many as 256 switches.
 
-![image](/hardware/images/multimorphic_SW-16.png)
+![image](../images/multimorphic_SW-16.png)
 
 Each SW-16 has a unique `board number` which is set using DIP switches
 (find that out now). On each board there are two `banks` (A and B) of 8
@@ -89,7 +89,7 @@ MPF.
 * Local Inputs - Alternatively you can use them as direct local inputs
     (and the burst drivers as outputs; see [How to configure coils/drivers/magnets (P-ROC/P3-ROC)](drivers.md) section for details).
 
-![image](/hardware/images/multimorphic_p3_roc.png)
+![image](../images/multimorphic_p3_roc.png)
 
 ### Burst Switches as Burst Optos
 

diff --git a/docs/hardware/multimorphic/win_x64.md b/docs/hardware/multimorphic/win_x64.md
@@ -25,7 +25,7 @@ shot below. That should be ok.
 Download and run the setup executable from the "1" link in the screen
 shot.
 
-![image](/hardware/images/ftdi_x64.jpg)
+![image](/docs/hardware/images/ftdi_x64.jpg)
 
 ## 2. Now download and unzip the other package
 

diff --git a/docs/hardware/multimorphic/win_x86.md b/docs/hardware/multimorphic/win_x86.md
@@ -22,7 +22,7 @@ Here's a screen shot of the download section of that page. Note that
 the actual version number of the driver might be newer that the screen
 shot below. That should be ok.
 
-![image](/hardware/images/ftdi_x86.jpg)
+![image](/docs/hardware/images/ftdi_x86.jpg)
 
 Download and run the setup executable from the "1" link in the screen
 shot. (We like to use that because it's easier than the manual process

diff --git a/docs/hardware/opp/cobrapin/index.md b/docs/hardware/opp/cobrapin/index.md
@@ -7,7 +7,7 @@ title: CobraPin Pinball Controller powered by OPP
 --8<-- "hardware_platform.md"
 
 
-![image](/hardware/images/CobraPinV0_2_isoSmall.jpg)
+![image](/docs/hardware/images/CobraPinV0_2_isoSmall.jpg)
 
 Features:
 
@@ -41,7 +41,7 @@ Video about cobrapin extension board:
 
 ## Power Input and Filter
 
-![image](/hardware/images/CobraPinV0_2_VIN.jpg)
+![image](/docs/hardware/images/CobraPinV0_2_VIN.jpg)
 
 **J9:** 
 
@@ -58,7 +58,7 @@ connectors.
 
 ## Switch Inputs
 
-![image](/hardware/images/CobraPinV0_2_switches.jpg)
+![image](/docs/hardware/images/CobraPinV0_2_switches.jpg)
 
 **J1, J2, J3:**
 
@@ -79,14 +79,14 @@ connectors. For example Molex KK254 series available for AWG 30-22. Each connect
 for the direct input return. If you measure the voltage between GND and
 a switch (in below picture 0-0-16) you should measure 3.3V.
 
-![image](/hardware/images/Cobra_Voltage_Switch.jpg)
+![image](/docs/hardware/images/Cobra_Voltage_Switch.jpg)
 
 For that to measure only the micro controllers need to be powered up, no
 need to apply any other voltage on the Cobra board. To perform a simple
 test connect any kind of switch to one of the inputs and setup a little
 mpf test configuration.
 
-![image](/hardware/images/Cobra_Switch_connected.jpg)
+![image](/docs/hardware/images/Cobra_Switch_connected.jpg)
 
 Do not apply any voltage to the switches, most likely that will destroy
 your CPU. For further details and fully working Cobra board
@@ -97,7 +97,7 @@ section below.
 
 ## Solenoid Outputs
 
-![image](/hardware/images/CobraPinV0_2_solenoids.jpg)
+![image](/docs/hardware/images/CobraPinV0_2_solenoids.jpg)
 
 **J6, J7, J8:**
 
@@ -123,7 +123,7 @@ must be controlled by switch with number `0-a-b`.
 Each bank has an LED next to it to indicate if that bank has power.
 Check these if you are concerned you have blown a fuse.
 
-![image](/hardware/images/Cobra_Coils_LED_Power.jpg)
+![image](/docs/hardware/images/Cobra_Coils_LED_Power.jpg)
 
 In above picture you see that the LED for bank A is alight but not for
 bank B. In order to have the LED alight you only need to have connected
@@ -138,7 +138,7 @@ voltage power or without the coils plugged in. Using these LEDs, you can
 verify that each output is being driven correctly, in the picture below
 coil 1-0-1 is being driven at this very moment.
 
-![image](/hardware/images/Cobra_Coils_LED_Switch.jpg)
+![image](/docs/hardware/images/Cobra_Coils_LED_Switch.jpg)
 
 To run the above test, there is no need for a high voltage power supply
 neither for any coil. Only the mirco controllers need to be powered up.
@@ -184,7 +184,7 @@ To have a fully working example for setting up autofire coils see the
 
 ## Solenoid Power Output and Fuses
 
-![image](/hardware/images/CobraPinV0_2_HVout.jpg)
+![image](/docs/hardware/images/CobraPinV0_2_HVout.jpg)
 
 **J13:**
 
@@ -205,7 +205,7 @@ The fuses are 5x20mm. Each fuse provides power to a bank of 8 solenoids.
 
 ## Neopixel Support
 
-![image](/hardware/images/CobraPinV0_2_NEO.jpg)
+![image](/docs/hardware/images/CobraPinV0_2_NEO.jpg)
 
 **J10:**
 
@@ -227,7 +227,7 @@ The connectors J10, J11, J12 and J14 are JST connectors VH style. There
 are lots of Neopixels which come with a JST connector SM style. You
 might want to craft a little converter cable in such a case.
 
-![image](/hardware/images/Cobra_Neopixel_JST_adapter_VH_SM.jpg)
+![image](/docs/hardware/images/Cobra_Neopixel_JST_adapter_VH_SM.jpg)
 
 There are two neopixel chains that support 256 RGB pixels each for a
 total of 512. RGBW pixels are also possible, but the number may be
@@ -240,15 +240,15 @@ fuse and are providing power for neopixels. For the LED to light up
 there is no need to run any MPF configuration, you don't even have to
 power up the micro controllers.
 
-![image](/hardware/images/Cobra_Power_LED_Neopixel.jpg)
+![image](/docs/hardware/images/Cobra_Power_LED_Neopixel.jpg)
 
 When you order the micro controllers you have various options, one
 option to choose from is Regular vs NoGlow. If you order the Regular
 version then after power is provided for the Neopixel and the micro
 controllers are powered up (still no need to run any MPF on them), the
 LEDs of your strip will glow blue, which is a good first test.
 
-![image](/hardware/images/Cobra_Neopixel_blue_glow.jpg)
+![image](/docs/hardware/images/Cobra_Neopixel_blue_glow.jpg)
 
 In order to addess the LEDs in MPF you need to know their address
 
@@ -268,7 +268,7 @@ generic LED section [LEDs](../../../mechs/lights/index.md) where as well the mor
 
 ## Microcontrollers
 
-![image](/hardware/images/CobraPinV0_2_STM32.jpg)
+![image](/docs/hardware/images/CobraPinV0_2_STM32.jpg)
 
 The brains of the CobraPin are two STM32 microcontroller boards
 programmed with OPP firmware. They are connected to the host computer

diff --git a/docs/hardware/opp/oppcombo/index.md b/docs/hardware/opp/oppcombo/index.md
@@ -7,9 +7,9 @@ title: OPP EM Combo boards
 --8<-- "hardware_platform.md"
 
 
-![image](/hardware/images/O16I16_comps.jpg)
+![image](/docs/hardware/images/O16I16_comps.jpg)
 
-![image](/hardware/images/O32_comps.jpg)
+![image](/docs/hardware/images/O32_comps.jpg)
 
 The aim of this project is to provide cheap hardware to control EM pinball machines:
 
@@ -30,9 +30,9 @@ The size of the board is about 150 x 125 mm.
 Several boards are required to drive an EM machine. 
 According to the complexity and your personal taste, 3-4 to drive the play field, 2-3 to drive the light box.
 
-![image](/hardware/images/fast_draw_lb.jpg)
+![image](/docs/hardware/images/fast_draw_lb.jpg)
 
-![image](/hardware/images/fast_draw_pf.jpg)
+![image](/docs/hardware/images/fast_draw_pf.jpg)
 
 ## Configuration
 
@@ -85,6 +85,6 @@ In the above example one would do:
 With those boards, I digitized a 1975 Gottlieb Fast Draw, which was presented to the [Pontacq Pinball Show](https://www.facebook.com/groups/154388563388625)
 on June 1rst-2nd, 2024, South of France, where it ran 375 plays without any software problem.
 
-![image](/hardware/images/pontacq.jpg)
+![image](/docs/hardware/images/pontacq.jpg)