i bought a rostockmax v3.2 a couple of weeks ago
things have gone ok until 2 days ago
when i try to connect the web interface i get
A JavaScript error has occurred so the web interface has closed the connection to your board. It is recommended to reload the web interface now. If this happens again, please contact the author and share this error message:
Version: 1.21
Message: ReferenceError: lineSegmentOffset is not defined
URL: http://rmaxv32/js/dwc.js
Line: 4:1551
Error object: {}
i submitted a help request to seemecnc 2 days ago but have not heard from them yet
this printer makes a really good looking door stop but i had hoped to get more use from it
the seemecnc support has really let me down
does any one here have suggestions
can not connect to printer
Re: can not connect to printer
I would suggest that you wipe the SD card and copy the data you downloaded from the git repository again.
This is something you should have already tried.
g.
This is something you should have already tried.
g.
Delta Power!
Defeat the Cartesian Agenda!
http://www.f15sim.com - 80-0007, The only one of its kind.
http://geneb.simpits.org - Technical and Simulator Projects
Defeat the Cartesian Agenda!
http://www.f15sim.com - 80-0007, The only one of its kind.
http://geneb.simpits.org - Technical and Simulator Projects
Re: can not connect to printer
i planned to try that but if i do i would not be able to supply more info for seemecnc support if they so needed
i do not mind being down a bit if it helps them fix bugs but this is a bit much
i do not mind being down a bit if it helps them fix bugs but this is a bit much
-
- ULTIMATE 3D JEDI
- Posts: 1407
- Joined: Sun May 11, 2014 6:18 pm
Re: can not connect to printer
It appears that there is more traffic by SeeMeCNC people on their Facebook page than there is here. You might get a faster response there.
R-Max V2
Eris
Folger Tech FT-5 R2
Eris
Folger Tech FT-5 R2
Re: can not connect to printer
thanks for the tip
format the hard drive and start over seems to have made the problem go away
format the hard drive and start over seems to have made the problem go away