Troubleshooting - Revision history

Acid: /* Troubleshooting */

2022-06-28T14:43:37Z

Troubleshooting

← Older revision		Revision as of 14:43, 28 June 2022
Line 3:		Line 3:
	* '''Medusa logo turns on and off and nothing happens'''		* '''Medusa logo turns on and off and nothing happens'''

	Check power. Medusa has overvoltage and undervoltage protection circuit and it cuts off the power when voltage drops below about 4.5V. To work Medusa needs substantial amount of current (more than 400mA). When you connect it for example to a computer using passive HUB then voltage can easily drop down even to 4.2V. Nevertheless just after start all A/D converters are powered off and FPGA chip has no core loaded. In this state it needs less power and therefore voltage doesn't drop that bad. In such case it may be able to send the logo to the display and then when all circuits are powered, voltage drops and causes device reset.		Check power. Medusa has overvoltage and undervoltage protection circuit and it cuts off the power when voltage drops below about 4.5V. To work, Medusa needs substantial amount of current (more than 400mA). When you connect it for example to a computer using a passive HUB then voltage can easily drop down even to 4.2V. Nevertheless just after start all A/D converters are powered off and FPGA chip has no core loaded. In this state it needs less power and therefore voltage doesn't drop that bad. In such case it may be able to send the logo to the display and then when all circuits are powered, voltage drops and causes device reset.

	* '''No Picture'''		* '''No Picture'''

Acid: /* Troubleshooting */

2022-06-28T10:41:49Z

Troubleshooting

← Older revision		Revision as of 10:41, 28 June 2022
Line 1:		Line 1:
	== Troubleshooting ==		== Troubleshooting ==

	* No Picture		* '''Medusa logo turns on and off and nothing happens'''

			Check power. Medusa has overvoltage and undervoltage protection circuit and it cuts off the power when voltage drops below about 4.5V. To work Medusa needs substantial amount of current (more than 400mA). When you connect it for example to a computer using passive HUB then voltage can easily drop down even to 4.2V. Nevertheless just after start all A/D converters are powered off and FPGA chip has no core loaded. In this state it needs less power and therefore voltage doesn't drop that bad. In such case it may be able to send the logo to the display and then when all circuits are powered, voltage drops and causes device reset.

			* '''No Picture'''

	[[File:no_signal.png\|400px\|thumb]]		[[File:no_signal.png\|400px\|thumb]]
Line 13:		Line 17:


	* SDTV picture is ugly		* '''SDTV picture is ugly'''

	# Try to avoid connecting signal using composite video - always use s-video cables if possible		# Try to avoid connecting signal using composite video - always use s-video cables if possible
Line 26:		Line 30:


	* RGB picture is ugly		* '''RGB picture is ugly'''

	# If your device hasn't been detected (you see "unknown PAL", "unknown NTSC", "unrecognised lo" or "unrecognised hi" on second line on OLED/OSD - also if you see a name that does not match your device) then you should manually adjust pixels per line parameter (rgb only -> pixels/line) - see [[Sample phase / Pixers per line]]. In such case consider contacting us with the device's fingerprint (rgb only -> fingerprint). We might be able to add your device to the list of recognised devices in future firmwares.		# If your device hasn't been detected (you see "unknown PAL", "unknown NTSC", "unrecognised lo" or "unrecognised hi" on second line on OLED/OSD - also if you see a name that does not match your device) then you should manually adjust pixels per line parameter (rgb only -> pixels/line) - see [[Sample phase / Pixers per line]]. In such case consider contacting us with the device's fingerprint (rgb only -> fingerprint). We might be able to add your device to the list of recognised devices in future firmwares.
Line 33:		Line 37:


	* Displaying device looses sync whenever input resolution changes		* '''Displaying device looses sync whenever input resolution changes'''

	:: It is normal. Medusa processes picture line by line. In such case whenever input line is missing (i.e. during input mode switch) also lines are missing on the output. Practically all displaying devices loose sync (even multisync CRT displays). Usually it means that the display becomes blank for half a second or so. See the [[Description]] chapter.		:: It is normal. Medusa processes picture line by line. In such case whenever input line is missing (i.e. during input mode switch) also lines are missing on the output. Practically all displaying devices loose sync (even multisync CRT displays). Usually it means that the display becomes blank for half a second or so. See the [[Description]] chapter.

Acid: /* Troubleshooting */

2022-06-24T11:32:18Z

Troubleshooting

← Older revision		Revision as of 11:32, 24 June 2022
Line 28:		Line 28:
	* RGB picture is ugly		* RGB picture is ugly

	# If your device hasn't been detected (you see "unknown PAL", "unknown NTSC", "unrecognised lo" or "unrecognised hi" on second line on OLED/OSD - also if you see a name that does not match your device) then you should manually adjust pixels per line parameter (rgb only -> pixels/line). In such case consider contacting us with the device's fingerprint (rgb only -> fingerprint). We might be able to add your device to the list of recognised devices in future firmwares.		# If your device hasn't been detected (you see "unknown PAL", "unknown NTSC", "unrecognised lo" or "unrecognised hi" on second line on OLED/OSD - also if you see a name that does not match your device) then you should manually adjust pixels per line parameter (rgb only -> pixels/line) - see [[Sample phase / Pixers per line]]. In such case consider contacting us with the device's fingerprint (rgb only -> fingerprint). We might be able to add your device to the list of recognised devices in future firmwares.
	# If your device has been properly detected but the picture is not crystal clear - first try to adjust sample phase (rgb only -> sample phase).		# If your device has been properly detected but the picture is not crystal clear - first try to adjust sample phase (rgb only -> sample phase) - see [[Sample phase / Pixers per line]].
	# If you see a lot of noise you may try to increase smoothing (filter -> smoothing -> 5-10), but also check power cables (yes power cables). Source of picture noise is usually on the ground signal. To reduce ground noise you may consider connecting ground of Medusa with ground of your device using separate cable. Although it is counterintuitive, exchange your modern filtered multiple outlet extension cord for a basic one (without filters, switches etc). Very often such noise is generated by power supply - try different power supply unit.		# If you see a lot of noise you may try to increase smoothing (filter -> smoothing -> 5-10), but also check power cables (yes power cables). Source of picture noise is usually on the ground signal. To reduce ground noise you may consider connecting ground of Medusa with ground of your device using separate cable. Although it is counterintuitive, exchange your modern filtered multiple outlet extension cord for a basic one (without filters, switches etc). Very often such noise is generated by power supply - try different power supply unit.

Acid at 18:33, 22 June 2022

2022-06-22T18:33:05Z

Acid: /* Troubleshooting */

2022-06-22T17:22:49Z

Troubleshooting

← Older revision		Revision as of 17:22, 22 June 2022
Line 28:		Line 28:
	* RGB picture is ugly		* RGB picture is ugly

	# If your device hasn't been detected (you see "unrecognised lo" or "unrecognised hi" on second line on OLED/OSD - also you see name that do not match your device) then you should adjust manually pixels per line parameter (rgb only -> pixels/line). In such case consider contacting us. Likely we will be able to add your device to list of recognised devices in future firmwares.		# If your device hasn't been detected (you see "unknown PAL", "unknown NTSC", "unrecognised lo" or "unrecognised hi" on second line on OLED/OSD - also you see name that do not match your device) then you should adjust manually pixels per line parameter (rgb only -> pixels/line). In such case consider contacting us. Likely we will be able to add your device to list of recognised devices in future firmwares.
	# If your device has beed properly detected but picture is not crystal clear - first try to adjust sample phase (rgb only -> sample phase).		# If your device has beed properly detected but picture is not crystal clear - first try to adjust sample phase (rgb only -> sample phase).
	# If you see a lot of noise you may try to increase smoothing (filter -> smoothing -> 5-10), but also check power cables (yes power cables). Source of picture noise is usually on the ground signal. To reduce ground noise you may consider connecting ground of Medusa with ground of your device using separate cable. Although it is counterintuitive, change modern filtered multi-outlets into simple one (without filters, switches etc). Very often such noise is generated by power supply - try different power supply unit.		# If you see a lot of noise you may try to increase smoothing (filter -> smoothing -> 5-10), but also check power cables (yes power cables). Source of picture noise is usually on the ground signal. To reduce ground noise you may consider connecting ground of Medusa with ground of your device using separate cable. Although it is counterintuitive, change modern filtered multi-outlets into simple one (without filters, switches etc). Very often such noise is generated by power supply - try different power supply unit.

Acid at 16:50, 22 June 2022

2022-06-22T16:50:18Z

← Older revision		Revision as of 16:50, 22 June 2022
Line 1:		Line 1:
	~~== Info on OLED ==~~

	~~Lines:~~
	~~# - used A/D chip (RGB or SDTV) and input (SCART/VGA for RGB and S-VIDEO/CVBS for SDTV) or firmware version when there is no input signal~~
	~~# - detected mode, for RGB name of the system ("Atari ST PAL", "Amiga PAL" itp.), for SDTV detected signal standard (PAL, NTSC, SECAM with type) or "NO INPUT SIGNAL"~~
	~~# - Horizontal frequency of input signal~~
	~~# - Vertival frequency of input (and output) signal~~
	~~# - Flags (such as LINEDBL - line doubling)~~
	~~# - Current DVI window (you may think of it as a "resolution")~~
	~~# - Screen shift horizontal:vertical~~
	~~# - Working Pixel Frequency~~

	~~== Front LED color ==~~

	* Red - RGB signal detected
	* Green - SDTV signal detected
	* Yellow - both signals detected (RGB on VGA and SDTV on SCART) - in this mode you may switch input using "middle" button
	* Blue - firmware flash / clearing settings
	* Nothing - no input signal detected

	== Troubleshooting ==		== Troubleshooting ==

Acid: /* Troubleshooting */

2022-06-22T16:43:41Z

Troubleshooting

← Older revision		Revision as of 16:43, 22 June 2022
Line 38:		Line 38:
	# To reduce stripes/noise you may consider using smoothing (filter -> smoothing -> 5-10)		# To reduce stripes/noise you may consider using smoothing (filter -> smoothing -> 5-10)
	# If you only want monochromatic picture and you have s-video cable you may consider "hacking" Medusa and force to process luminance. Enter this commands in USB/serial console:		# If you only want monochromatic picture and you have s-video cable you may consider "hacking" Medusa and force to process luminance. Enter this commands in USB/serial console:
	<~~PRE~~>		<pre>
	cmd :>scartmode rgb		cmd :>scartmode rgb
	cmd :>setyasg 1		cmd :>setyasg 1
	cmd :>rgbcurve mfg 1		cmd :>rgbcurve mfg 1
	cmd :>rgbcomponent 1		cmd :>rgbcomponent 1
	</~~PRE~~>		</pre>

Acid: /* Troubleshooting */

2022-06-22T16:42:49Z

Troubleshooting

← Older revision		Revision as of 16:42, 22 June 2022
Line 31:		Line 31:
	# If after that your device still do not display anything it of course may mean cable problems but it also may mean that your device is not compatible with signal produced by Medusa. Control screen is generated with vertical frequency of 50Hz. Since almost all old computers also generates picture with refresh rate of 50Hz then it means that your device has to be capable of displaying 50Hz. If it is not, then you may need to find another device.		# If after that your device still do not display anything it of course may mean cable problems but it also may mean that your device is not compatible with signal produced by Medusa. Control screen is generated with vertical frequency of 50Hz. Since almost all old computers also generates picture with refresh rate of 50Hz then it means that your device has to be capable of displaying 50Hz. If it is not, then you may need to find another device.
	# Check input cables or try different input signal		# Check input cables or try different input signal


	* SDTV picture is ugly		* SDTV picture is ugly
Line 43:		Line 44:
	cmd :>rgbcomponent 1		cmd :>rgbcomponent 1
	</PRE>		</PRE>


	* RGB picture is ugly		* RGB picture is ugly
Line 49:		Line 51:
	# If your device has beed properly detected but picture is not crystal clear - first try to adjust sample phase (rgb only -> sample phase).		# If your device has beed properly detected but picture is not crystal clear - first try to adjust sample phase (rgb only -> sample phase).
	# If you see a lot of noise you may try to increase smoothing (filter -> smoothing -> 5-10), but also check power cables (yes power cables). Source of picture noise is usually on the ground signal. To reduce ground noise you may consider connecting ground of Medusa with ground of your device using separate cable. Although it is counterintuitive, change modern filtered multi-outlets into simple one (without filters, switches etc). Very often such noise is generated by power supply - try different power supply unit.		# If you see a lot of noise you may try to increase smoothing (filter -> smoothing -> 5-10), but also check power cables (yes power cables). Source of picture noise is usually on the ground signal. To reduce ground noise you may consider connecting ground of Medusa with ground of your device using separate cable. Although it is counterintuitive, change modern filtered multi-outlets into simple one (without filters, switches etc). Very often such noise is generated by power supply - try different power supply unit.


	* Displaying device lost sync whenever input resolution changes		* Displaying device lost sync whenever input resolution changes

	It is normal. Medusa processes picture line by line. In such case whenever input line is missing (i.e. during input mode switch) also lines are missing on the output. Practically all displaying devices lost sync (even multisync CRT displays). Usually it means that display becomes blank for half a second or so. See the [[Description]] chapter.		:: It is normal. Medusa processes picture line by line. In such case whenever input line is missing (i.e. during input mode switch) also lines are missing on the output. Practically all displaying devices lost sync (even multisync CRT displays). Usually it means that display becomes blank for half a second or so. See the [[Description]] chapter.

Acid: Created page with "== Info on OLED == Lines: # - used A/D chip (RGB or SDTV) and input (SCART/VGA for RGB and S-VIDEO/CVBS for SDTV) or firmware version when there is no input signal # - detected mode, for RGB name of the system ("Atari ST PAL", "Amiga PAL" itp.), for SDTV detected signal standard (PAL, NTSC, SECAM with type) or "NO INPUT SIGNAL" # - Horizontal frequency of input signal # - Vertival frequency of input (and output) signal # - Flags (such as LINEDBL - line doubling) # - Cur..."

2022-06-22T16:39:33Z

Created page with "== Info on OLED == Lines: # - used A/D chip (RGB or SDTV) and input (SCART/VGA for RGB and S-VIDEO/CVBS for SDTV) or firmware version when there is no input signal # - detected mode, for RGB name of the system ("Atari ST PAL", "Amiga PAL" itp.), for SDTV detected signal standard (PAL, NTSC, SECAM with type) or "NO INPUT SIGNAL" # - Horizontal frequency of input signal # - Vertival frequency of input (and output) signal # - Flags (such as LINEDBL - line doubling) # - Cur..."

New page

== Info on OLED ==

Lines:
# - used A/D chip (RGB or SDTV) and input (SCART/VGA for RGB and S-VIDEO/CVBS for SDTV) or firmware version when there is no input signal
# - detected mode, for RGB name of the system ("Atari ST PAL", "Amiga PAL" itp.), for SDTV detected signal standard (PAL, NTSC, SECAM with type) or "NO INPUT SIGNAL"
# - Horizontal frequency of input signal
# - Vertival frequency of input (and output) signal
# - Flags (such as LINEDBL - line doubling)
# - Current DVI window (you may think of it as a "resolution")
# - Screen shift horizontal:vertical
# - Working Pixel Frequency

== Front LED color ==

* Red - RGB signal detected
* Green - SDTV signal detected
* Yellow - both signals detected (RGB on VGA and SDTV on SCART) - in this mode you may switch input using "middle" button
* Blue - firmware flash / clearing settings
* Nothing - no input signal detected

== Troubleshooting ==

* No Picture

[[File:no_signal.png|400px|thumb]]

When you connect Medusa to your displaying device even without any signal on input you should see control picture (on the left)

# Check if your DVI window is set to default (DVI: 720x576) - if not then reset current settings (reset -> rst curr prof) or manually change window to 720x576 (shift/size -> dvi presets -> 720x576). You may also experiment with 720x480 and 640x480, but 720x576 is most compatible window size for 50Hz.
# Check if Medusa is switched to "pure DVI" mode (global options -> DVI mode -> pure DVI). Some (especially DVI) devices do not accept audio packets and do not display anything when audio packets are present in DVI stream. Especially good old 17" and 19" VGA monitors are not compatible with audio.
# If after that your device still do not display anything it of course may mean cable problems but it also may mean that your device is not compatible with signal produced by Medusa. Control screen is generated with vertical frequency of 50Hz. Since almost all old computers also generates picture with refresh rate of 50Hz then it means that your device has to be capable of displaying 50Hz. If it is not, then you may need to find another device.
# Check input cables or try different input signal

* SDTV picture is ugly

# Try to avoid connecting signal using composite video - always use s-video cables if possible
# To reduce stripes/noise you may consider using smoothing (filter -> smoothing -> 5-10)
# If you only want monochromatic picture and you have s-video cable you may consider "hacking" Medusa and force to process luminance. Enter this commands in USB/serial console:
<PRE>
cmd :>scartmode rgb
cmd :>setyasg 1
cmd :>rgbcurve mfg 1
cmd :>rgbcomponent 1
</PRE>

* RGB picture is ugly

# If your device hasn't been detected (you see "unrecognised lo" or "unrecognised hi" on second line on OLED/OSD - also you see name that do not match your device) then you should adjust manually pixels per line parameter (rgb only -> pixels/line). In such case consider contacting us. Likely we will be able to add your device to list of recognised devices in future firmwares.
# If your device has beed properly detected but picture is not crystal clear - first try to adjust sample phase (rgb only -> sample phase).
# If you see a lot of noise you may try to increase smoothing (filter -> smoothing -> 5-10), but also check power cables (yes power cables). Source of picture noise is usually on the ground signal. To reduce ground noise you may consider connecting ground of Medusa with ground of your device using separate cable. Although it is counterintuitive, change modern filtered multi-outlets into simple one (without filters, switches etc). Very often such noise is generated by power supply - try different power supply unit.

* Displaying device lost sync whenever input resolution changes

It is normal. Medusa processes picture line by line. In such case whenever input line is missing (i.e. during input mode switch) also lines are missing on the output. Practically all displaying devices lost sync (even multisync CRT displays). Usually it means that display becomes blank for half a second or so. See the [[Description]] chapter.

← Older revision		Revision as of 18:33, 22 June 2022
Line 5:		Line 5:
	[[File:no_signal.png\|400px\|thumb]]		[[File:no_signal.png\|400px\|thumb]]

	When you connect Medusa to your displaying device even without any signal on input you should see control picture (on the ~~left~~)		When you connect Medusa to your displaying device even without any signal on input you should see control picture (on the right)

	# Check if your DVI window is set to default (DVI: 720x576) - if not then reset current settings (reset -> rst curr prof) or manually change window to 720x576 (shift/size -> dvi presets -> 720x576). You may also experiment with 720x480 and 640x480, but 720x576 is most compatible window size for 50Hz.		# Check if your DVI window is set to default (DVI: 720x576) - if not then reset current settings (reset -> rst curr prof) or manually change window to 720x576 (shift/size -> dvi presets -> 720x576). You may also experiment with 720x480 and 640x480, but 720x576 is the most compatible window size for 50Hz.
	# Check if Medusa is switched to "pure DVI" mode (global options -> DVI mode -> pure DVI). Some (especially DVI) devices do not accept audio packets and do not display anything when audio packets are present in DVI stream. Especially good old 17" and 19" VGA monitors are not compatible with audio.		# Check if Medusa is switched to "pure DVI" mode (global options -> DVI mode -> pure DVI). Some (especially DVI) devices do not accept audio packets and do not display anything when audio packets are present in DVI stream. Especially good old 17" and 19" VGA monitors are not compatible with audio.
	# If after that your device still do not display anything it ~~of course~~ may mean cable problems ~~but it also may mean~~ that your device is not compatible with signal produced by Medusa. Control screen is generated with vertical frequency of 50Hz. Since almost all old computers also ~~generates~~ picture with refresh rate of 50Hz then it means that your device has to be capable of displaying 50Hz. If it is not, then you may need to find another device.		# If after that your device still does not display anything it may mean either cable problems or that your device is not compatible with signal produced by Medusa. Control screen is generated with vertical frequency of 50Hz. Since almost all old computers also generate picture with refresh rate of 50Hz then it means that your device has to be capable of displaying 50Hz. If it is not, then you may need to find another device.
	# Check input cables or try different input signal		# Check input cables or try different input signal

Line 17:		Line 17:
	# Try to avoid connecting signal using composite video - always use s-video cables if possible		# Try to avoid connecting signal using composite video - always use s-video cables if possible
	# To reduce stripes/noise you may consider using smoothing (filter -> smoothing -> 5-10)		# To reduce stripes/noise you may consider using smoothing (filter -> smoothing -> 5-10)
	# If you only want monochromatic picture and you have s-video cable you may consider "hacking" Medusa and ~~force~~ to process luminance. Enter ~~this~~ commands in USB/serial console:		# If you only want monochromatic picture and you have s-video cable you may consider "hacking" Medusa and forcing it to process only luminance signal using RGB A/D. Enter these commands in USB/serial console:
	<pre>		<pre>
	cmd :>scartmode rgb		cmd :>scartmode rgb
Line 28:		Line 28:
	* RGB picture is ugly		* RGB picture is ugly

	# If your device hasn't been detected (you see "unknown PAL", "unknown NTSC", "unrecognised lo" or "unrecognised hi" on second line on OLED/OSD - also you see name that do not match your device) then you should adjust ~~manually~~ pixels per line parameter (rgb only -> pixels/line). In such case consider contacting us. ~~Likely we will~~ be able to add your device to list of recognised devices in future firmwares.		# If your device hasn't been detected (you see "unknown PAL", "unknown NTSC", "unrecognised lo" or "unrecognised hi" on second line on OLED/OSD - also if you see a name that does not match your device) then you should manually adjust pixels per line parameter (rgb only -> pixels/line). In such case consider contacting us with the device's fingerprint (rgb only -> fingerprint). We might be able to add your device to the list of recognised devices in future firmwares.
	# If your device has ~~beed~~ properly detected but picture is not crystal clear - first try to adjust sample phase (rgb only -> sample phase).		# If your device has been properly detected but the picture is not crystal clear - first try to adjust sample phase (rgb only -> sample phase).
	# If you see a lot of noise you may try to increase smoothing (filter -> smoothing -> 5-10), but also check power cables (yes power cables). Source of picture noise is usually on the ground signal. To reduce ground noise you may consider connecting ground of Medusa with ground of your device using separate cable. Although it is counterintuitive, ~~change~~ modern filtered ~~multi-outlets into simple~~ one (without filters, switches etc). Very often such noise is generated by power supply - try different power supply unit.		# If you see a lot of noise you may try to increase smoothing (filter -> smoothing -> 5-10), but also check power cables (yes power cables). Source of picture noise is usually on the ground signal. To reduce ground noise you may consider connecting ground of Medusa with ground of your device using separate cable. Although it is counterintuitive, exchange your modern filtered multiple outlet extension cord for a basic one (without filters, switches etc). Very often such noise is generated by power supply - try different power supply unit.


	* Displaying device ~~lost~~ sync whenever input resolution changes		* Displaying device looses sync whenever input resolution changes

	:: It is normal. Medusa processes picture line by line. In such case whenever input line is missing (i.e. during input mode switch) also lines are missing on the output. Practically all displaying devices ~~lost~~ sync (even multisync CRT displays). Usually it means that display becomes blank for half a second or so. See the [[Description]] chapter.		:: It is normal. Medusa processes picture line by line. In such case whenever input line is missing (i.e. during input mode switch) also lines are missing on the output. Practically all displaying devices loose sync (even multisync CRT displays). Usually it means that the display becomes blank for half a second or so. See the [[Description]] chapter.