Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gcode viewer out of the window #719

Closed
RFranta opened this issue Jan 14, 2015 · 23 comments

Comments

Projects
None yet
5 participants
@RFranta
Copy link

commented Jan 14, 2015

When I go to gcode viewer tab I dont see the gcode platform. I found that is somewhere out of the window and if I press the left mouse button and drag down I can finally see ithe platform, but next time when I restart my device I dont see gcode viewer again. Can I set the position of gcode platform to be lower on start?

I am using Olinuxino A20 (similar to RPi) and browsers Midori and Google Chrome.
I tried version OctoPrint 1.1.1-4-gc35b7a6-dirty (master branch)
2014-06-13 and also today I updated to newest version by "git pull && python setup.py install"
Firmware is Marlin about 6 months old version with megatronics board, but because I don't see gcode viewer even without connecting, problably doesn't matter.

Here are my log files

Octoprint log:
http://pastebin.com/8nTzGxEG

I love cookies

Octoprint terminal:
http://pastebin.com/2Yce22PX

@foosel

This comment has been minimized.

Copy link
Owner

commented Jan 14, 2015

Your working copy is dirty according to the version string. Please make sure that this issue is not caused by any changes you made to the code.

Also check your browser's error console.

@RFranta

This comment has been minimized.

Copy link
Author

commented Jan 14, 2015

Here is the log from the updated Octoprint (it's not dirty now):
http://pastebin.com/6vhWjxDs

But problem still remain.

Here is console log:
http://pastebin.com/rDG5HhmM

There is error "Failed to load resource: the server responded with a status of 404 (NOT FOUND) http://192.168.1.103:5000/static/js/lib/jquery/jquery.min.map"
Could that be the problem?

@foosel

This comment has been minimized.

Copy link
Owner

commented Jan 15, 2015

And github also didn't notify me of this reply. Grmpf :/

Ok. That jquery error is not the reason here. You are seeing the same behaviour in both midori and chrome?

How are your Renderer Options set beneath the viewer? This should be the default:

image

@RFranta

This comment has been minimized.

Copy link
Author

commented Jan 15, 2015

Yes, I have default Renderer options same as on you rscreenshot and yes,
it look the same both on Chrome, Firefox and Midori.

@foosel

This comment has been minimized.

Copy link
Owner

commented Jan 15, 2015

Is this with or without a loaded file? If with a loaded file, can you supply the file? If without, can you try with one?

@RFranta

This comment has been minimized.

Copy link
Author

commented Jan 15, 2015

Its both with and without, but any file is loaded properly in gcode viewer so that shouldnt be the case.

@foosel

This comment has been minimized.

Copy link
Owner

commented Jan 15, 2015

As said in the other ticket of you, I'm at a complete loss regarding this too. Nothing in the javascript console, can't be caused by a loaded file either, no weird options. I'm out of ideas and I fear I'll have to capitulate for now, sorry

@RFranta

This comment has been minimized.

Copy link
Author

commented Jan 15, 2015

Only different think is that I am using Olinuxino, not RPi.

Is there any variable in Octoprint code that would move the platform on start in Y axis? I know its not a nice solution but it would help me. Thanks

@nophead

This comment has been minimized.

Copy link
Contributor

commented Jan 15, 2015

Actually I have seen the grid appear not in the centre of the window sometimes. I just drag it to where is should be.

@irrenhaus

This comment has been minimized.

Copy link

commented Jan 17, 2015

I can confirm this too, only experienced it after using a fresh installation of OctoPi (like around 15 days ago). I think it was running version 1.1.1 (not exactly sure, I'm currently not using it). Checking the "Center viewport on model" checkbox fixed it each time.

If there's anything I can check let me know, I will then try to reproduce it.

@lovesegfault

This comment has been minimized.

Copy link

commented Jan 18, 2015

I can also confirm this. It used to happen every single time I uploaded and loaded a Gcode, but ever since I moved to devel (1.2.0-dev-395-g4e4ad0b) this has been much less recurring. At times if the Gcode file was very large, above 20Mb or so, the grid would be out of the window and it would 'stick' to the mouse making it impossible to center. Neither 'center viewport on model' nor 'zoom in on model' options would help in that, or in any case.

@foosel

This comment has been minimized.

Copy link
Owner

commented Jan 19, 2015

I just managed to successfully reproduce this (or at least something that looks suspiciously like it) on master. That's at least a start I guess.

foosel added a commit that referenced this issue Jan 19, 2015

Fixed a bug causing the GCODE viewer to be zoomed in outside of the p…
…rint bed due to missing initial move

Possible fix for #719
@foosel

This comment has been minimized.

Copy link
Owner

commented Jan 19, 2015

I just pushed a change to master, can everyone affected by this please check if that solves the issue for you? If not, please provide a screenshot.

foosel added a commit that referenced this issue Jan 19, 2015

foosel added a commit that referenced this issue Jan 19, 2015

@RFranta

This comment has been minimized.

Copy link
Author

commented Jan 19, 2015

Now it's bed centered great! Works nice both on Olinuxino LCD display in Midori and in my PC in Chrome. Awesome. Thank you very much!

@foosel

This comment has been minimized.

Copy link
Owner

commented Jan 22, 2015

@Arengorn @nophead @irrenhaus Can you give it another test too?

@nophead

This comment has been minimized.

Copy link
Contributor

commented Jan 22, 2015

That is worse for me because the model is no longer in the centre of the grid, presumably because my origin is 0,0, not 100,100. Previously the model was centred on the grid but the grid was not always centred. That was easy to fix by dragging it.

@irrenhaus

This comment has been minimized.

Copy link

commented Jan 22, 2015

I will have a look this evening or tomorrow, whenever I find time for it.

@foosel

This comment has been minimized.

Copy link
Owner

commented Jan 22, 2015

@nophead Ah, so now you are running into what @imitation described in #677 and which is tracked in #682. I guess this bug somehow covered this up for you. I'll try to look into it, on the master branch you still should be able to work around it by setting an offset for the extruder 1 though like described in #677

@irrenhaus thanks!

@nophead

This comment has been minimized.

Copy link
Contributor

commented Jan 22, 2015

Yes adding an extruder offset puts it back in the centre of the grid. Does
that have any other side effect?

On 22 January 2015 at 11:00, Gina Häußge notifications@github.com wrote:

@nophead https://github.com/nophead Ah, so now you are running into
what @imitation https://github.com/imitation described in #677
#677 and which is tracked in
#682 #682. I guess this bug
somehow covered this up for you. I'll try to look into it, on the master
branch you still should be able to work around it by setting an offset for
the extruder 1 though like described in #677
#677

@irrenhaus https://github.com/irrenhaus thanks!

Reply to this email directly or view it on GitHub
#719 (comment).

@foosel

This comment has been minimized.

Copy link
Owner

commented Jan 23, 2015

Only if you run multi extruder setups. It might have some small effect on how the gcode interpreter analyses your files, but that shouldn't really affect your. So I guess not.

@irrenhaus

This comment has been minimized.

Copy link

commented Jan 23, 2015

@foosel Fixed for me :) Thank you very much!

@foosel

This comment has been minimized.

Copy link
Owner

commented Jan 23, 2015

Ok, closing this then.

@nophead I hope you can live with the offset workaround for a while until I implement #682

@foosel foosel closed this Jan 23, 2015

@nophead

This comment has been minimized.

Copy link
Contributor

commented Jan 24, 2015

Yes it is working fine for me and since updating the gcode viewer always
seems to work. Previously it only worked occasionally.

Regarding the first extruder offset. I think it always needs a configurable
setting because some deltas have three nozzle arranged radially, so they
are all offset relative to the centre of the end effector.

On 23 January 2015 at 17:18, Gina Häußge notifications@github.com wrote:

Closed #719 #719.

Reply to this email directly or view it on GitHub
#719 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.