Jump to content

Big Dave

  • Content Count

  • Joined

  • Last visited

  • Days Won


Big Dave last won the day on December 12 2016

Big Dave had the most liked content!

About Big Dave

  • Rank
    Maximum Member

Profile Information

  • Gender
  • Location

Recent Profile Visitors

736 profile views
  1. I don't think that this isn't recommended... Or did I get this wrong ? We just use a damp, lint free cloth, and scrub any paper residue off the rollers. What about those "rubber rejuvenator" chems that press people use ? We received a small bottle of it and have been itching to try it on the Noritsu rollers, but we don't want to mess up the paper magazine rollers ! What do you guys think ?
  2. Ok, thank you for this advice. We will wait and see if this happens more often and replace at that time. Have a great week.
  3. Hi Kodak_Service, Thank you for this information. With the problem we had the other day, are there other warning signs of impending failure, or was this just a one-time glitch, or do you recommend we replace that board NOW ? Yustas, Thank you for the information. It is very helpful. Thank you Minilab service. Did you receive my PM from the other day ?
  4. Which PSU ? Do you have description or Part # ? Yesterday, after Breaker Off/On, it was just fine for ~ 200 prints. Today, Daily Setup went normal, and prints are OK. I forgot to check the condition of the Color Wheel after power off last night, but will try to check tonight after closing. Thank you all for your assistance so far, but I am really interested in finding the "source" of this problem, and trying to replace the "right" PCB so it doesn't happen again. Any Additional Help / Suggestions Appreciated !!
  5. Hi Yustas, We did replace the MLVA PSU last year(?) with a spare. I am truly afraid to test with a multi-meter when the machine is powered on. I am a little bit clumsy at times, and have killed other electronics trying to do this.
  6. Ok guys, Last resort - I shutdown and turned OFF the power at the breaker for 5 minutes. Turned it back on, went straight to daily setup, and BAM !!! It PRINTED the daily setup ! - no uniformity issues, but a little bit more Magenta than normal. no biggie. - we are going to assume it's "OK" for now, - BUT we would Really Like to Know what may have caused this, so we can be ready if it happens again, OR replace what may have caused it - before it happens again. THANK YOU !
  7. Sorry, but there is "nothing" on any print. The paper is Pure white. So Chems are OK !, So it seems (to me) that No light getting to the MLVA head -- OR -- MLVA head not putting any light on the paper. MLVA Lamp is good, color wheel is spinning (I think), so there is some other problem. Hopefully not a bad MLVA head, but I'm not an expert ! For the 6029 error, the Service Manual suggests: MLVA unit, Drive Voltage PCB, Data Output PCB, Image Processing PCB, Printer Control PCB. But I don't know what to focus on. I have NO spare Image processing PCB, the other PCBs I May have, but not 100% sure. Thanks you for your suggestion though ! If you think this will help, I will try it, but I think there is some other problem. If I am wrong, and you are correct, I OWE YOU A BEER !
  8. Hi All, This just happened to us today, for the Daily Setup, got error message: 6088-0024 - Uniformity Correction Error. The Daily Setup print came out, and it was ALL white, so cancelled daily setup. MLVA lamp is LIT, and appears to be fine (was replaced less than 2 weeks ago with new lamp). Color wheel (seems) to be spinning. Tried printing something else, it too was all white. Performed Uniformity Calibration, completed successfully, but gave error message: 6029-0004 MLVA Auto Gain execution error. (though auto gain is carried out during MLVA setup, the dark level reading sensitivity value of outside MLVA*1 is higher than that of around the MLVA center.) Performed MLVA head cleaning, Performed Uniformity Calibration, completed successfully, but gave error message: 6029-0001 MLVA Auto Gain execution error. (though auto gain is carried out during MLVA setup, the measured result is extremely low.) I'm stuck. Any suggestions on how to fix this ??
  9. Hey all, Someone asked me if there is a difference in the parts manuals from the regular V50 and the "V50A" -- (never heard of the V50A before) Thanks all !
  10. Awesome ! Let us know how it works out for you.
  11. Hi Dave S, Replenishment pump output amount checks - looks mostly good. Maybe under replenishing a tiny little bit. previously: CD = 60.0 / BF = 58.1 / STB = 111.0 NOW: CD = 58.3 / BF = 57.0 / STB = 113.3 - each run 4 times, measured and divided by 4 As far as the SSD TRIM function, there are quite a few others that have mentioned that they are running on older OS' with SSDs and not having issues after use for over 2 years -- and these were posts from 2015. This article, from 2015, seems to say that even without TRIM, it might wear out your SSD a little faster, but nothing to really worry about. https://arstechnica.com/gadgets/2015/04/ask-ars-my-ssd-does-garbage-collection-so-i-dont-need-trim-right/ The SanDisk I installed was bought in 2017, so should be good for at least another 10 years - unless it has a catastrophic failure at some point -- it was on sale when I bought it ! -- advertised as an 80 GB drive, 75 GB total with 64 GB free. -- lots of spare cells to use. I can swap SSD to HDD if you think that's a plausible suspect in this data corruption. Thanks !
  12. Chemistry seems to be OK, no major ups or downs on the daily setups (sorry, we don't run control strips). Chem usage is good, but I will double check the pump output amounts later today. Colorimeter unit and position is good -- Only issue is the calibration plate is a bit on the old side. -- Last replaced back in Oct of 2009. TRIM isn't/can't be enabled on Win2K (from what I could find out) but no un-healthy side effects from it so far. Other people say that the system might be a little slower, but it's more than fast enough for us. The usable space has not deviated at all in the past 8 months - that I can tell, but I've not really thought about it. -- I do have a good working HDD inside the machine, if the SSD ever fails, I just have to move the SATA/power cable from the SSD to the HDD, do a system restore and we're back up. BTW, it's an 80GB SanDisk SSD, not 128gb.
  13. Ok, less 8 days later, the problem has returned. Performed another data restore - and this DID FIX IT. The question now, is why ? Why did it happen again, so quickly ? How can we prevent this issue going forward, or is this a precursor to "something else" ?? I cloned and installed a new 128GB SSD at the end of November 2017 -- so the hard drive is "good".
  • Create New...