BTW, a phenomenon I’m also used to: whenever I’m going to replace an old aging component (whatever it is), it starts misbehaving a few days after I ordered its replacement… Not very painful if there’s only a couple of days to get the new one, much more problematic when there are weeks or months delay before getting the replacement delivered.
If you spend too much time with me then you will certainly have more problems , plus my box will teach your box how to be good when needed and then play up when not. I even looked at the serial number to make sure it didn’t have three sixes in it
Well, I was wondering Duncan! If I ever get to meet you and have a listen to your system, especially your 808’s. I’ll be having a good look at your scalp first!
My Bartók has been typically behaving it self, I did think about cancelling its return, but knowing my luck it’ll play up just when the warranty expires!
Just been in my 60c loft to retrieve the Bartók’s Box, it will be collected tomorrow and shipped to dCS via The Audiobarn in Essex.
Late to this post, think you have done the right thing by sending it back for repair. Hope it gets sorted soon. I had the issues way back in Dec 22’. Same boot up screen. Mine had issues trying to obtain an IP address and proceeded to lose it and restarting the sequence again and again. Check out this link below. Good luck.
The symptoms indicated issues with acquiring an IP address and holding on to it. It is like a computer running a Unix/Linux embedded OS. Not sure why it kept losing the IP and stuck with the boot up screen. While it was in the repair centre, the Apex version became available. DCS offered me the upgrade with a slight reduction cost. Hasn’t had any issues since, fingers crossed.
This thread now raises a lot of questions with me.
@MoreBeer had the same problem in 2022,4 years ago. Bartok was repaired,so far so good. But what was wrong? Flaw in hardware design? Then why is that not fixed and still a problem in later manufactured units? Bad hardware parts? Same question,why still a problem after 4 years?
Same goes if the problem is in firmware. Why is that not fixed after 4 years? As the units were repaired the cause must be known. So why not fix it on forehand?
Happy with my Bartok but it is a mistery to me why this problem still pops up. dCS?
I had the same issue too 5y ago or so.
My unit was first repaired, then as I was still having this issue among others (distortion at startup, other freeze conditions…) purely replaced by dCS.
No more issue at all since the replacement.
Not necessarily. He had similar symptoms but I cannot see any evidence that it was the same cause.
How do you know that it was not fixed or that the hardware was faulty? He clearly says
So , whatever it was, it has been fixed.
My experience of reports of what was done from service engineers is not always reliable in may case. They can mix up the dozens of units tthat hey service ( this is not limited to dCS). IFor example I have been told that tobacco film was the problem ( a new unit and this is a non-smoking household and has been for decades). Then there was a radio which the service agent accused me of submerging in water! Maybe he has seen one but it wasn’t mine ( the fault was actually a dodgy internal connection). Maybe it was a case of saying anything to get rid of the enquirer .
The only way to deal with this is for each repair to come back with a full service report. However I have no doubt this would involve an additional cost ( if outside warranty).
Whatever, even if you have the information , what are you going to do with it?
Although OP’s unit exhibits similar symptoms. It may or may not have the same exact issues. If one can perform some more diagnostics. My unit’s symptoms was related to flaky network. I had access to a Cisco switch which gives me blow by blow what the network were doing in the logs.
Btw, you can open a browser an point the IP address to your Apex, go to “Device Settings”. At the bottom of the page you can download the system logs. Hitting the download button will pull a compressed file which you can extract out some useful logs. I basically corresponded time of issues with the Cisco logs and time stamp on the Apex’s “messages” (under var folder). The flaky network could be issues related to firmware, OS, PSU or hardware, I am not entirely sure. All one can do is to provide as much useful details to the repair centre and to ensure the issues was not coming from my network or the grid.
Not entirely sure the local repair centre changed. I am unsure what the upgrade entails, swapping out board(s) and maybe the PSU? I have observed the Bartok crashed and stuck on boot screen due to fluctuation in the grid, it was very minor that my computer stayed up, the microwave beeped, but the Bartok has gone into a boot screen. If you have a uninterrupted power supply (UPS) or a home battery with same function, try plugging the unit into it for stable power supply.