Posts by Jens

Caution: Non registered users only see threads and messages in the currently selected language, which is determined by their browser Please create an account and log in to see all content by default. This is a limitation of the forum software.
Don't Panic. Please wash hands.

    This is all really confusing. After removing the Vampire and booting the ADF I get the GURU requester again and its the same old game. No EDID, no Settings recognized...

    So what exact Guru message is that?

    And did the person who did the re-cap of your PSU also give you the technical data of the caps that were used? I mean, if you don't have the measuring equipment to verify that everything was done correctly, you might have ended up with higher ripple than before, because the person saved a few cents on higher-ESR caps. The mere choice of 105 degrees types does not say a single bit about ESR, and that's the critical, dominant bit of data that you want to know if you have such maintenance done.

    the config tool works just fine and recognizes the monitor when there's no Vampire plugged in.

    Oh boy - so the Vampire guys didn't learn a tiny bit about compatibility? Timm, can you please confirm in public that you're using the exact chip register mirrors that were "the solution" for Indivision ECS V2? I don't want to jump to conclusions (just yet). The error might as well be on our side, but that's for Timm to verify/falsify.

    It is a Fujitsu E19-9 monitor and the cable is a standard DVI to HDMI one. Input is DVI.

    Please remember to tick the "DVI mode" box in the "advanced" settings, and of course to run a firmware update (from drop-down menu), as the factory-flashed version of your unit does not have that setting. If that's not ticked, audio will be encoded in the blanking periods of the monitor signal, which confuses some (if not all) DVI monitors. It's about the same problem that you have if you're trying to use an RPi on a DVI monitor - it does not work out of the box.

    All units that are shipped today have an updated config that has the DVI-mode checked, so every single monitor will display a stable picture.

    1 currently I have mk2cr do I have to uninstall old drivers and settings or it can stay in case of re-to mk2

    There are no actual "drivers" - the config/flash tool of the MK2cr will just not work with the new version and vice versa. Both can be on the harddrive at the same time, that's no problem.

    2. Are your power supplies adapted to work with the mk3 and future ACA 040 060

    There is no need for specific "adaption" - our power supplies comply with the specifications that Commodore has provided. Any other power supply that complies with the specs will work as well, provided it's not overloaded with the overall system. The ACA1240/1260 takes most of it's power from the 12V rail, so interference with any 5V device is *very* unlikely.

    3. I will use the MK3 on the 16: 9 monitor (I have no other 4: 3 RIP)

    Is it possible to set the picture with the proportions and with black stripes on the sides?

    Yes, that's no problem - you can either set to "black borders left and right", or you can stretch the picture to be full-screen. There are of course settings in the monitor that we can't influence - one of the settings is the "picture mode" which can be "full screen", "aspect" or "1:1" (sometimes called "PC mode"). The latter is what you should choose in order to have pixel-exact control over the panel from the Amiga side. Your monitor's manual is your friend :-)

    The config tool is totally unusable. It'll throw GURU requesters at random which makes it hard to even get to the point to save the settings.

    The tool works fine without accel, with 020 and with 030 accelerators. Granted, it's currently not yet been tested with 040/060 CPUs, but that should not cause any trouble. To fix any bugs (if any), there is a debug version that outputs a lot of additional information through the serial port - Timm can send that (or upload it to the Wiki).

    First of all, please describe your exact setup - the artefacts you've shown in your YT video clearly point to a power supply issue, which may be caused by the PSU itself, or by another component in the computer.

    Another problem I have encountered is, that OSDPos option results in black screen or shifted image. The OSD itself will always stay at the top left.

    ..meaning that settings don't even reach the flicker fixer in your computer. We'll have to find out what's the cause for this - I have already suspected a contact problem in your computer, and your continuous other error messages support that. Do you have an old toothbrush and alcohol that you can use the clean the contacts around Lisa?

    Also, please don't forget to answer the other questions I've asked in my previous posting. We're here to help. However, you need to work with us, not against us. At this point, I'm making suggestions, you're ignoring them and post more errors that appear to have the same cause. There's no point in doing the same thing over and over again, but expecting different results.

    There must be an error in calculation of the frequencies, as the same settings with different pixel clock will result in different horizontal&vertical frequencies. I wonder where that's located.

    Further, didn't Alastair already find that you rmonitor does not support the low resolution you're trying to use?

    Just noticed that my oldest PSU is rated with 2.5 amps on the 5v line.

    Is it enough to drive the ACA500 Plus?

    That may be a little on the low-side, yes. Further, the 2.5A model has the worst efficiency, so it gets hotter than the switchmode-PSUs. This will result in worse ageing of the output caps and ultimately result in failures like the one you're describing here.

    These PSUs are quite old - you might want to re-cap them (or replace with something new, just make sure they have proper regulation and don't do weird "overvoltage protection" advertising, hiding that they use unsuitable MeanWell-Chassis).

    what writing status do you have

    to write a configuration file.

    The flashtool reports the return status using the Amiga's power LED, as follows:

    That's only for the rescue disk and the non-GUI flash tool. The GUI tool writes to flash if you click on "save/apply". However, before Cego thinks that a setting is "forgotten", you can always exit and re-enter the flash tool, which will read back and compare the flash contents with the saved config on HD. If there's a difference, the tool will let you know in a requester - how dows that behave?

    Is this option by default enabled? Or do we have to enable it with the config tool? Really looking forward to try this out.

    Unfortunately, yes, the audio option is switched on by default, which causes most DVI-only monitors to either not display a picture, or to have it go away (actually more than you see it). The solution is to switch to DVI mode in the config tool, this will let you use all DVI monitors.

    I just got the MK3, but on the wiki there's no Config Tool available. Jens, can you please give me a download link?

    It was late, uploaded yesterday afternoon - a day before the promosed release date, but a day after the first customers got it:

    i won't get a picture at all from the HDMI output.

    Sounds like you have a DVI monitor - please switch to DVI mode in the config tool. Sorry about that pre-config - we need to change that on the standard factory config!

    And the config tool won't read the EDID information.

    This is most likely a contact problem - we didn't have a single monitor that would not share it's info, (almost) no matter how old. The one that failed was an old Eizo 15-inch CRT that really does not support EDID - all flat screens do. Please double-check your cable.

    On VGA the picture appears and disappears (except HighGFX mode)

    That's a known problem with bad power supplies. You say you have a re-capped 4.5A model - what's the output cap brand you've used, and what were the ripple and voltage values at the computer after you did the re-cap?

    Could it be the hot weather at the moment ?

    Likely, as a hot power supply will also have hot output caps, leading to higher ripple. Also, I'd double-check the available voltage inside the computer.

    Same problem here... To be more in detail: works perfect in HighGFX-Mode, but I get a blanking screen when using - for example - PAL:HighRes Interlace.

    Before you upload a video, a simple description of the setup will help: Type of monitor, cable used, input used, and of course anything you've changed in the config tool. The factory-preset has HDMI mode enabled by detault, which leads to problems with DVI monitors - that was an oversight on our side, but it can be easily fixed with the config tool.

    my Indivision isn't recognized at all now. No VGA or HDMI output. Will send it back tomorrow...

    That sounds like it just isn't installed - did you push it on Lisa all the way down and did you hear&feel that clicking sound?

    The fast-config by keyboard works so far.

    My config:

    - A1200 Rev 1b

    - Orig C= A600 PSU

    - Vampire 1200 V2 (tested without -> caused yellow and red guru-meditations during trying to boot)

    you probably have a combination of problems - we did not test with Vampire, as that's not a 68000 accelerator, but a whole different platform. However, we did implement the same "workaround" as we did for Indivision ECS V2 - if the Vampire team has learned a tiny bit about compatibility issues from that, they would have changed "nothing" and left the register space outside the mirrors "untouched". So from our side, we've done what's required to make it work - please try with a real-CPU accelerator (or completely without accelerator) to see if the flicker fixer is found. If it is found, please turn to the Vampire vendor(s) and ask what register space they block this time..

    Hopefully the shipping cost to the USA eases up soon.

    While DHL is pulling the "because of COVID-19"-card, I fear that us small businesses are paying the losses that DHL is making with the big boys (Amazon & co).

    There's no sign of anyone missing out on the new flicker fixers - we've produced a lot.

    What does this option do?

    It installs Thor's MMU libraries.

    Does it cause problems if I install the MMULib myself?

    If you have a newer version (is there anything newer than what's in the latest ACA500plus flash?), then you should disable this option, otherwise you may either mix files (which is generally "asking for trouble"), or the older version from flash takes precedence, because it was installed earlier in the boot process.

    I thought it meant I could generate a config file on my pc and apply it using the command line tool.

    Sorry, the config tool is an Amiga-only application. The idea would be that you run it on a different computer, which of course needs to be an Amiga, and it should be equipped with an Indivision ECS V2.

    If I apply the config to the board the settings will stay saved for 1.3 correct?

    Yes, the flicker fixer has it's own flash ROM where the settings are stored and retrieved whenever the screen mode changes.

    First how do I change the configuration on an a500 with KS1.3?

    The GUI tool requires Kick 2.0 or higher. The commandline tool can "only" write firmware and pre-compiled configuration files. This has been clearly communicated in the product description - it's under "fine print", and it's actually not written that small.

    The other question I have is has anyone found a fix for the ghosting issue so many people have?

    I have finally investigated this a few weeks ago, and found that the input stage of Samsung monitors is substantially different to what other monitors use. I did find a solution, but that involves replacing a number of SMD components that you probably won't get that easily in shops. When the Indivision AGA MK3 and CA-PSU craze is over, I'll look into making a small patch-pcb that contains all the required parts, and run a modded Indivision ECS V2 through CE testing again (that's because I'm expecting changes in the spectrum, mainly because I decided to use much faster driver transistors). It might be september/october until this is available.

    yes, finally, 3 days before the official date

    yes, and pre-orders are flooding in, now that the official delivery date gets closer. We'll do our best to ship all current pre-orders until the 10th, but I have now set the "promised date" for both the MK3 flicker fixer and the CA-PSU to Friday August 14th. We already had lots of pre-orders, but what's currently coming in is massive, and I don't want to disappoint people because their order may be shipped a few days late.

    Is it possible to change the delivery address?

    Only if your order has been paid with a bank transfer. If it was paid with PayPal, the only way is a refund.

    Please send me an eMail (just answer the confirmation eMail from the shop system) to sort things out, and please hurry. The first units will be shipped today.

    A hotter PSU will decrease its efficiency?

    A hotter PSU will change the available capacitance on the big electrolytic caps. Depending on their inner construction, it can go up or down, and this heavily depends on the frequency that the switchmode PSU is using, so I would not dare any prediction other than "behaviour is different at different temperatures".

    2) the white aux card led does light up and the Amiga power led starts to blink and nothing happens to;

    That's a signal from the automatic mounter that tells you "something is wrong", and it's attempting to power-cycle the card to try again. This also explains the prolonged time that the computer takes to boot if the AUX card is inserted.

    While your test with swapping the two cards is perfect, it does not tell us of the Sandisk cards are real or not. Sandisk is a top brand that unfortunately pulls in lots of counterfeit products. I'd suggest to try a no-name card as well, something that comes from your local shop, not from ebay, which is full of fake cards.

    Maybe to implement audio filters digitally for HDMI audio output?

    Exactly :-)

    The implication of this is quite large, as Lisa does not do Audio in the AGA chipset. That's still Paula's task. However, all data that is pushed to Paula via DMA is also flying by Lisa, so we can sniff that and push it into a Paula audio emulation. This gives us a fully digital implementation of the chipset audio. Needless to say that Paula audio emulation is taking up a significant part of the FPGA logic - one explanation for an FPGA that has about twice as many logic cells as the MK2 model had.

    Please mind that audio over HDMI is not an advertised feature and it's therefore not covered by official product support. We still have it on the "experimental" features list, as filtering the audio is something that we didn't get right yet. Digital audio is generated with a frequency of 3.58MHz (CCK of the chipset), and re-sampling to 48kHz is something we haven't done before, and you can hear it in the current state of the filters. You do hear a difference of "low pass filter on or off", but there's still a metallic kind-of-noise especially with low-quality samples that is not there on the analogue audio of the computer. We may or may not improve this in the future with a core update.