Home Forums Vinyl Cutter Discussions Roland Cutters Has anyone else had problems with a VersaCamm disconnecting?

  • Has anyone else had problems with a VersaCamm disconnecting?

    Posted by John Dorling on 22 December 2009 at 12:16

    Hi All

    Got a major problem at the moment; my VP540 stops printing halfway through a job and comes up as ‘Not Connected’ in VersaWorks. I have to turn the power off to the machine and re-start the job.

    Has anyone else had this problem and if so how did you resolve it?

    (I should point out that it is usually connected through a network switch, which I thought was causing the problem, but it does it even when connected directly to a computer)

    Thanks

    John

    John Dorling replied 15 years, 9 months ago 4 Members · 6 Replies
  • 6 Replies
  • Matt Hammond

    Member
    22 December 2009 at 13:02

    Do you have a screensaver on your rip?

  • Peter Dee

    Member
    22 December 2009 at 13:13

    This could be down to power saving settings on the PC where it powers down after a set period.

  • John Dorling

    Member
    22 December 2009 at 13:29

    Thanks for replies. I have ruled those things out but looks like it may be a dirty encoder strip. Can anyone tell me how to remove these for cleaning?

  • George Elsmore

    Member
    22 December 2009 at 13:36

    no need to remove just carefully clean with a lint free cloth front and back its easy, a tiny speck can make the machine throw extraordinary whammers

  • John Dorling

    Member
    22 December 2009 at 14:08

    Tried all of the above now and still no luck! Looks like it’s time to open my wallet!

    Humbug.

  • John Dorling

    Member
    12 January 2010 at 14:43

    Update on this in case anyone else has the same issue – it seems the machine was too cold!

    After re-installing the firmware, trying different network cables and computers etc, I spoke to Canopy Digital (on the advice of Jeremy) and they were very helpful. I have just moved a heater near the motherboard end of the machine (which is under the window) and it all seems fine now! Not sure why this should happen but it does seem to have sorted the problem.

    John

Log in to reply.