Donkie / Spoolman

Keep track of your inventory of 3D-printer filament spools.
MIT License
1k stars 93 forks source link

Select Spool Not Work In Mainsail #246

Open Multicore87 opened 10 months ago

Multicore87 commented 10 months ago

The select spool Not work in mainsail, i try with many browser. IMG_3978

pdsccode commented 10 months ago

Did you do any updates of your mainsail instance? What does the moonraker.log show? All in all I'd suspect that this is not a Spoolman issue but log files are helpful for clarification.

Multicore87 commented 10 months ago

I don't know if it depends on spoolman or anything. It doesn't go with any browser while from a smartphone or clipper screen it seems so. What do you have to do? What files do you need or what do you want to know?

Multicore87 commented 10 months ago

I also have a error on moonracker that concerns spoolman

pdsccode commented 10 months ago

The file of interest would be "moonraker.log" which can be found in the logs folder of your Mainsail installation image

Multicore87 commented 10 months ago

moonraker.log

Multicore87 commented 10 months ago

Just put if you can understand something

pdsccode commented 10 months ago

I also have a error on moonracker that concerns spoolman

Can you show me the error you have somehow? The logs seem pretty normal and there is no error seen.

Multicore87 commented 10 months ago

moonraker.log.2023-12-24.txt moonraker.log.2024-01-01.txt

Multicore87 commented 10 months ago

Try to see these two older files too

Donkie commented 10 months ago

Everything seems to be working fine according to the logs, which makes me believe it's your browser. Can you check your browser's javascript console and see if theres any errors that pop up there when you open the spool selection window?

Multicore87 commented 10 months ago

IMG_4002

Multicore87 commented 10 months ago

I've tried with many browsers like chrome, Safari, Edge etc. both Mac and Windows but it doesn't go. I don't think it depends on the browser but something about spoolman or moonracker or mainsail I don't know.

rufinus commented 10 months ago

0.8.0-209 may be a bit to old to have the spoolman integration.

Multicore87 commented 10 months ago

So what should I do?

Multicore87 commented 10 months ago

logs-20240104-133327.zip

Ladin69 commented 10 months ago
[spoolman]
server: http://192.168.0.20:7912  ( link to yours Spool Manger )
#   URL to the Spoolman instance. This parameter must be provided.
# sync_rate: 5
#   The interval, in seconds, between sync requests with the
#   Spoolman server.  The default is 5.
rufinus commented 10 months ago

@ladin69 can you stop commenting with your config under every ticket? this neither helps the topic nor you in any way.

Multicore87 commented 10 months ago

What can I do?

pdsccode commented 10 months ago

I in this case would start over by removing every reference to spoolman from the moonraker.conf

After that, reboot the mainsail host, see if any updates are pending under the machine tab and then reconfigure the Spoolman integration as seen in the documentation.

If this does not work, try with a freshly installed mainsail instance to see if your config is the issue.

From the logs I can't find any reason why it shouldn't work.

Also, did you try to look at the JavaScript console as suggested by @Donkie?

Multicore87 commented 10 months ago

I had already tried to remove the spoolman references on mooracker and everything else but nothing to do. I can try this javascript thing if you tell me what to do but does this have to do with it since it doesn't work with any browser or operating system?

Donkie commented 10 months ago

It's probably nothing wrong with your browser, but obviously something is wrong with your UI, and if something is wrong with the UI then it's likely you also have some error in your browser console.

pdsccode commented 10 months ago

I had already tried to remove the spoolman references on mooracker and everything else but nothing to do. I can try this javascript thing if you tell me what to do but does this have to do with it since it doesn't work with any browser or operating system?

As Donkie said, it is likely to see the issue in the javascript console even if it has nothing to do with the browser itself. https://www.digitalocean.com/community/tutorials/how-to-use-the-javascript-developer-console shows how to access the console from different browsers.

P.S. did you switch Mainsail hosts in the meantime? The first two logs show a user "pi" likely from a Raspberry Pi, the last one shows a "biqu" user from either a Biqu Hurakan or a BTT Manta board.

PP.S. also, the image from your last post seem to not have been uploaded correctly

Multicore87 commented 10 months ago

Because he does the same thing to both me and a friend, I have Raspberry and he cb1 btt. I'm trying to understand for both of us, and for that I think it's not just my problem but maybe it depends on mainsail or moonracker. The main problems are that if you open filament picker from blank page and every now and then it also gives error notification as in the picture

Multicore87 commented 10 months ago

IMG_4006 IMG_4004

pdsccode commented 10 months ago

Alright, I see. Then please do us and yourself a favour and at least leave some info when you provide a log that is not from your instance. This can lead to confusion and makes it even harder to help.

To move forward with your issue, please check the JavaScript console as requested. Open the console, then open the "pick spool" dialog, and post the output from the console here.

Edit: Ok, I went through your config again and compared it with your screenshot. It seems that you have Mainsail and Spoolman running on the same host, right? This opens the following questions for me:

Multicore87 commented 10 months ago

hi, yes spoolman runs on a raspberry along with everything without docker. the interface with ip opens easily and everything works. I can only select or remove filaments via macro. but if I open the page to select it is completely white as in the photo. I tried to edit in the moonracker file with ip http://127.0.0.1:7912 but the problem doesn't change.

Multicore87 commented 10 months ago

this is the window select spool on all browser and operative sistems

Multicore87 commented 10 months ago

Javascript

pdsccode commented 10 months ago

Almost there. Would you please close the select spool dialog (the one that doesn't work) again? Then click on "console" in the dev tools on the right and open the spool selection again.

image

Post another screenshot after you did this please.

Multicore87 commented 10 months ago

https://github.com/Donkie/Spoolman/assets/91397090/f81ebd1e-b909-47d5-87e0-4f52c0117de1

Multicore87 commented 10 months ago

moonraker.log

Multicore87 commented 10 months ago

tempImage5t0n09

Multicore87 commented 10 months ago

This error also often appears

pdsccode commented 10 months ago

Ok, now we have an actual error in the log file. Just to check the current state, the Spoolman web interface is still correctly working via http://192.168.1.15:7912?

Ladin69 commented 10 months ago

@Multicore87 You skipped something during the installation, I'm repeating the entire installation

Multicore87 commented 10 months ago

I've already tried several times and to redo installation but the problem doesn't change

pdsccode commented 10 months ago

I agree with Ladin69 here to a degree. I went ahead and tried to mimic your environment as close as possible by installing a fresh MainsailOS to a Raspberry Pi and installing Spoolman standalone on the same Pi as described in the Readme.

image

Please check again if there are pending updates on the "Machine" tab in Mainsail. If not, I would suspect a broken Mainsail install at this point and suggest a complete reinstall of the Pi with a current image. Make sure to backup the printer.cfg before doing so.