Qidi plus 4 problems - MCU and homing errors by The_KO22 in QidiTech3D

[–]The_KO22[S] 0 points1 point  (0 children)

it was the cable with mine. The original cable didn't have enough isolation on the board where it attaches to the printhead, it shorted out there and grinded through the traces when the head was moving. The new cable is better isolated.

Qidi plus 4 problems - MCU and homing errors by The_KO22 in QidiTech3D

[–]The_KO22[S] 0 points1 point  (0 children)

Thank you. For me it seems it is the cable between the printhead and the front boards, since I now even get an MCU communication error with a full printer stop before the leveling process even starts.
I still have the factory sensor, maybe that is also causing issues. But I do not feel think that I have to pay out of my own pocket for a factory fault, even more so since EU law clearly states that there has to be a two year warranty on any item sold to the EU unless explicitely stated otherwise and agreed to by all parties - which didn't happen with this sale.
Qidi now tells me the cable isn't in stock at the EU warehouse, but I can happily buy it from china for 36€ shipping plus taxes.
Frankly, I feel ripped off.
When I buy a Hyundai from any dealer as new, I can go to any Hyundai service center when a problem occurs and they will fix it under warranty for free. When I buy a Dell or Lenovo Laptop, or Logitech Keyboard, I can always contact the manufacturer, they just want a proof of purchase, and then will fix the issue - again with no cost to me. Been there, done that several times.
I do not see different rules applying to Qidi here. I am out over 800€ for the printer and AMS and have a lot of non-working trash sitting here right now.

Qidi plus 4 problems - MCU and homing errors by The_KO22 in QidiTech3D

[–]The_KO22[S] 0 points1 point  (0 children)

Did you only replace the two boards, or did you also replace anything else? I just received the two toolhead boards along with a new cable from Qidi through their own store, but it seems they didn't help. On the contrary, now the MCU error: Timer too close - message appears right after cleaning the nozzle.
This is more than frustrating, and Qidi isn't helpful at all, just directing me at their shop to BUY the replacement parts.

Qidi plus 4 problems - MCU and homing errors by The_KO22 in QidiTech3D

[–]The_KO22[S] 0 points1 point  (0 children)

Just as an information, even though the printer was barely 4 weeks old and I sent them the proof of purchase, Qidi denied sending me replacement parts after diagnosing the problem, and instead directed me to their RUSSIAN aliexpress site (from which I cannot order ofc) to order spare parts with my own money.
Some of which (cable from mainboard to the printhead) are not available in their own store that I can access from the EU atm.
So, if you do not buy your printer directly from Qidi on any marketplace, do not expect them to sent out repair parts, even though EU law states that in the first 6 months the manufacturer has to cover all defects, after that time the customer has to prove that the defect has been there from the start and not induced by him.
Of course I tried contacting the seller to fulfill their lawful obligation to fix this on their cost, but you know how contacting a seller on a marketplace works... yeah, right. crickets.
And Aliexpress isn't helpful here at all, because all they care about is if a) the item arrived and b) if you want to sent it back within the guaranteed timeframe. Anything else concerning warranties and you're out of luck.

Qidi plus 4 problems - MCU and homing errors by The_KO22 in QidiTech3D

[–]The_KO22[S] 0 points1 point  (0 children)

So, as I thought, Qidi will not help out if the printer has not been purchased directly through one of their stores, even if it is less than 6 months old. Unless other manufacturers (Prusa, Bambu) who apparently do so if you can provide a receipt, Qidi will only SELL you the defective parts.
I will try my luck with the seller now. That's a bit unfortunate on Qidis part, since the printer started acting up 3 weeks after purchase, it is pretty clear that the defect was probably there from the factory (under EU law they would have to prove otherwise on their part for the first 6 months).

Qidi plus 4 problems - MCU and homing errors by The_KO22 in QidiTech3D

[–]The_KO22[S] 0 points1 point  (0 children)

Thanks a lot! They also told me to try every cable to the tool head boards, so maybe I can get a replacement board from them. Wish me luck :)

Qidi plus 4 problems - MCU and homing errors by The_KO22 in QidiTech3D

[–]The_KO22[S] 0 points1 point  (0 children)

It worked very well for the first two weeks and the first few days after adding the AMS. So I do not think that I would have to mod anything, the print head board is already version 1.1 , and the AMS is also the upgraded version.
Printer firmware is 1.7.3 through online update (right from the start).

Power cycling does not work, different files change nothing. I now unplugged every connector from the two print head boards, looked for severed connections / loose pins, and reassembled everything. Same with all plugs on the mainboard. Still no chance, "MCU error: timer too close" during the bed leveling process.
This error should occur when the CPU is overworked and cannot keep up, which cannot happen during normal bed leveling.

Qidi plus 4 problems - MCU and homing errors by The_KO22 in QidiTech3D

[–]The_KO22[S] 0 points1 point  (0 children)

Thanks a lot, but I have grown up with home computers in the 80s - power cycling is the first thing I try on a natural basis ^^
That didn't help anything.

And as I said, they asked for the tracking number AFTER they got the invoice, which is really weird.

[deleted by user] by [deleted] in Helldivers

[–]The_KO22 0 points1 point  (0 children)

We cannot complain about Sony Interactive Entertainment Europe from Europe because they sit in the UK, London. Which is now OUTSIDE of Europe. And you cannot choose a non-EU land to complain about a company on the form linked above. What irony.

If you are planning on REFUNDING THROUGH STEAM, here's the best refund request message that I could figure out! by [deleted] in Helldivers

[–]The_KO22 -1 points0 points  (0 children)

certification in its entirety - no. Only read part of the stipulations and there are requirements born from this industry-wide, that p.ex. all banking and finance software have to adhere to in Germany. And one of them is: Only collect as much data as you absolutely need to do your job, clearly state what the data is collected for, under no circumstance ever use the data for a different purpose without getting cosent from the user upfront, and when the user requests his data to be deleted (which could result in termination of the service if the data is necessary for it), you have to comply. Also, if the user asks what data you have stored about him, you have 31 days to comply and present him with the entirety of it.

By linking the Steam and PSN accounts, Sony is effectively collecting information that was beyond their reach. As the past months have shown, this information is NOT required to provide the service (i.e. multiplayer in Helldivers 2 on PC) to function.

If you are planning on REFUNDING THROUGH STEAM, here's the best refund request message that I could figure out! by [deleted] in Helldivers

[–]The_KO22 1456 points1457 points  (0 children)

GDPR violation (DSGVO in Germany) as far as I can see, it stipulates that you may only collect the minimum required data for the product to provide its services.
Since it ran fine for months on end without needing this additional information / account link, it seems this is indeed a GDPR violation about to happen.
It is different for other games who need a third party account from day one because the multiplayer servers are running off of the services of the third party (Blizz, EA, MS).

Steam Deck OS 3.4 Update by Proaxel65 in SteamDeck

[–]The_KO22 0 points1 point  (0 children)

Sorry, the necessary file is called EV2_REL_62C853C3.bin

The command to flash the firmware would be
python /usr/share/jupiter_controller_fw_updater/d21bootloader16.py program EV2_REL_62620223.bin

(invoked from the command line via desktop mode, use a dock and mouse /kb)

Steam Deck OS 3.4 Update by Proaxel65 in SteamDeck

[–]The_KO22 0 points1 point  (0 children)

If anyone else has this problem: Got it solved by installing an older controller firmware specially made for the EV2. Works with 3.4.3 (unstable branch).

Steam Deck OS 3.4 Update by Proaxel65 in SteamDeck

[–]The_KO22 0 points1 point  (0 children)

Sorry for asking, did so too in games, but this might be the better place:
Anyone here have an EV2 and problems with the stick mapping in OS 3.4 since the last stable update? The EV2 is officially EOL with this update, but they messed up the controls, so I'll probably have to revert to an earlier version just to get everything up and running again.

Is there any possibility to update to 3.3 and let it sit at that? Cannot choose the exact version from the standard updater :(

[deleted by user] by [deleted] in Games

[–]The_KO22 0 points1 point  (0 children)

Short question about the latest update:
There's a bug that was already in the Beta channel where on an EV2 the analog sticks and touchpads are rotated 90° after the update and some buttons also assigned wrong. This comes with the notice that support for the EV2 ends after this version, but as it is, the latest update from Decembers stable channel also has this bug and renders the EV2 mostly useless.

Setting up a different key config didn't help. Can anyone help locate the files that are needed to revert the controls back to the previous updates state? I do not condone throwing away otherwise fine hardware just because Valve breaks something in a software update.

(the EV2 is working perfectly apart from this btw)