Funny jumping of the Printer at the Dashboard

CBX_Micha

... this time again in English; There are probably more English reading users here than German ones...

Since yesterday I have a second printer running on the server. It is still under construction and is therefore not currently switched on.
What is interesting, however, is the jumping back and forth/changing position of the two printers on the RS web dashboard.

Is that how it's supposed to be or is it a BUG? Could this be disabled somehow so that the connected printers retain their position? It's pretty annoying...

Video about this: https://steamradio.de/3dp/240127-RS-WebGUI-jump.mp4<br/>

Repetier

The problem is that the anet is not succeeding in connecting. So when it starts connecting it is counted as online and startign with A it is before the other printer. Order is Online and then alphabetically. When it fails it is offline moving to end. So actually this is correct.

What you need to check is why it fails so it can connect correctly. If it is just the port being visible where is a checkbox in connection settings that the port is visible also firmware is not running. Check it to prevent this in that case. Happens with Rambo boards for example.

CBX_Micha

Sorry, but you didn't understand my post or I didn't understand you.
Condition:
- ANET = OFF
- GEEE = ON (printing)

If I imagine that I have 4, 5, 6 or more printers on it and all the printers that are not currently switched on are creating this drama on the GUI, then it is pure luck to hit the right printer with the mouse. It is then impossible to calculate when which printer will take up which space on the GUI.

I think it's good that the status is shown here with colors and messages because you can see it at first glance. But do you have to constantly change the order of the printers on the GUI?
Can't you just say the printers are sorted by name, regardless of status? Or maybe add this as an option in the settings?

Repetier

There is a switch in dashboard to select alphabetically ordering already, just use it.

But you did not understand that the anet is visible causing the issue! You must tell server that it is visible also when disabled to prevent this toggling.

CBX_Micha

Ahhh... I'm starting to understand that. So you meant that the interface converter of the ANET board is supplied with power from the RPi via USB and is therefore visible to the RS, but the ANET CPU is still off. So RS see the Interface, but can't babble with the CPU... Have I understood you correctly?

Repetier

Yes that is what I meant. And with that switch you can disable server from assuming it is active until it sees a response that is expected so not switching on/off.

CBX_Micha

Ok I understand... My brain-fault
Another shortcoming is popping up, but it has nothing to do with RS:
With multiple printers that draw energy from the PI's USB ports even when switched off, this places an unnecessary burden on the PI (power supply).
I'm going to build USB adapters that separate the supply line from the PI to the printer with a Schottky... This would also eliminate the virtual problem with the jumper without having to change anything.

Repetier

Or you tape the 5v pin on usb adapter as shown in our faq. Would also solve the anet issue:-)

CBX_Micha

.... naaaaa... That's botch... B)

CBX_Micha

Sorry to say it, but a new problem has arisen in this context.

Same starting point:
-Geee ON
- ANET off
Both connected to the PI, but options set as you recommended (visible although off / sort alphabetically)

Now the following often happens in an incomprehensible order, after each restart of the RS:
- The Geee is forced into a reset by the RS in an endless loop, approximately every 10 seconds.
- The Geee is incorrectly seen as the ANET from RS
- Neither printer is seen
- RS briefly shows a popup "Update available" at the top left
- RS starts with wild GUI (hard reset required)
- ... and so forth...

After deactivating the ANET in RS and disconnecting the USB there, everything seems normal again at the moment. But as soon as both printers are on, the system goes completely crazy.

Unfortunately I don't know where to start looking here. I can only offer the most recent errors that are shown in the log...

[29.01.2024 20:32:34] : error: Reading conection failed: End of file. Closing connection.

[29.01.2024 20:32:34] : ANET ET5 PRO: Your OS syslog contains these messages close to this disconnect that might help to understand:

[29.01.2024 20:32:34] : GEEEE_i3: Your OS syslog contains these messages close to this disconnect that might help to understand:

[29.01.2024 20:32:34] : ANET ET5 PRO: syslog: Startup finished in 6.929s (kernel) + 24.659s (userspace) = 31.589s.

[29.01.2024 20:32:34] : GEEEE_i3: syslog: Startup finished in 6.929s (kernel) + 24.659s (userspace) = 31.589s.

[29.01.2024 20:32:34] : ANET ET5 PRO: syslog: [ 77.977092] usb 1-1.2: new full-speed USB device number 4 using xhci_hcd

[29.01.2024 20:32:34] : GEEEE_i3: syslog: [ 77.977092] usb 1-1.2: new full-speed USB device number 4 using xhci_hcd

[29.01.2024 20:32:34] : ANET ET5 PRO: syslog: [ 78.083225] usb 1-1.2: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.64

[29.01.2024 20:32:34] : GEEEE_i3: syslog: [ 78.083225] usb 1-1.2: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.64

[29.01.2024 20:32:34] : ANET ET5 PRO: syslog: [ 78.083247] usb 1-1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0

[29.01.2024 20:32:34] : GEEEE_i3: syslog: [ 78.083247] usb 1-1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0

[29.01.2024 20:32:34] : ANET ET5 PRO: syslog: [ 78.083254] usb 1-1.2: Product: USB Serial

[29.01.2024 20:32:34] : GEEEE_i3: syslog: [ 78.083254] usb 1-1.2: Product: USB Serial

[29.01.2024 20:32:34] : ANET ET5 PRO: syslog: checking bus 1, device 4: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2"

[29.01.2024 20:32:34] : GEEEE_i3: syslog: checking bus 1, device 4: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2"

[29.01.2024 20:32:34] : ANET ET5 PRO: syslog: [ 78.139903] usbcore: registered new interface driver usbserial_generic

[29.01.2024 20:32:34] : GEEEE_i3: syslog: [ 78.139903] usbcore: registered new interface driver usbserial_generic

[29.01.2024 20:32:34] : ANET ET5 PRO: syslog: [ 78.139941] usbserial: USB Serial support registered for generic

[29.01.2024 20:32:34] : GEEEE_i3: syslog: [ 78.139941] usbserial: USB Serial support registered for generic

[29.01.2024 20:32:34] : ANET ET5 PRO: syslog: [ 78.147390] usbcore: registered new interface driver ch341

[29.01.2024 20:32:34] : GEEEE_i3: syslog: [ 78.147390] usbcore: registered new interface driver ch341

[29.01.2024 20:32:34] : ANET ET5 PRO: syslog: [ 78.147439] usbserial: USB Serial support registered for ch341-uart

[29.01.2024 20:32:34] : GEEEE_i3: syslog: [ 78.147439] usbserial: USB Serial support registered for ch341-uart

[29.01.2024 20:32:34] : GEEEE_i3: syslog: [ 78.147507] ch341 1-1.2:1.0: ch341-uart converter detected

[29.01.2024 20:32:34] : GEEEE_i3: syslog: [ 78.157301] usb 1-1.2: ch341-uart converter now attached to ttyUSB0

[29.01.2024 20:32:34] : GEEEE_i3: syslog: checking bus 1, device 4: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2"

[29.01.2024 20:32:34] : GEEEE_i3: syslog: [ 175.785658] usb 1-1.1: new full-speed USB device number 5 using xhci_hcd

[29.01.2024 20:32:34] : GEEEE_i3: syslog: [ 175.891747] usb 1-1.1: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.64

[29.01.2024 20:32:34] : GEEEE_i3: syslog: [ 175.891766] usb 1-1.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0

[29.01.2024 20:32:34] : GEEEE_i3: syslog: [ 175.891773] usb 1-1.1: Product: USB Serial

[29.01.2024 20:32:34] : GEEEE_i3: syslog: [ 175.898491] ch341 1-1.1:1.0: ch341-uart converter detected

[29.01.2024 20:32:34] : GEEEE_i3: syslog: [ 175.907949] usb 1-1.1: ch341-uart converter now attached to ttyUSB1

[29.01.2024 20:32:34] : GEEEE_i3: syslog: checking bus 1, device 5: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1"

[29.01.2024 20:32:34] : ANET ET5 PRO: syslog: [ 78.147507] ch341 1-1.2:1.0: ch341-uart converter detected

[29.01.2024 20:32:34] : ANET ET5 PRO: syslog: [ 78.157301] usb 1-1.2: ch341-uart converter now attached to ttyUSB0

[29.01.2024 20:32:34] : ANET ET5 PRO: syslog: checking bus 1, device 4: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2"

[29.01.2024 20:32:34] : ANET ET5 PRO: syslog: [ 175.785658] usb 1-1.1: new full-speed USB device number 5 using xhci_hcd

[29.01.2024 20:32:34] : ANET ET5 PRO: syslog: [ 175.891747] usb 1-1.1: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.64

[29.01.2024 20:32:34] : ANET ET5 PRO: syslog: [ 175.891766] usb 1-1.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0

[29.01.2024 20:32:34] : ANET ET5 PRO: syslog: [ 175.891773] usb 1-1.1: Product: USB Serial

[29.01.2024 20:32:34] : ANET ET5 PRO: syslog: [ 175.898491] ch341 1-1.1:1.0: ch341-uart converter detected

[29.01.2024 20:32:34] : ANET ET5 PRO: syslog: [ 175.907949] usb 1-1.1: ch341-uart converter now attached to ttyUSB1

[29.01.2024 20:32:34] : ANET ET5 PRO: syslog: checking bus 1, device 5: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1"

[29.01.2024 20:32:52] : error: Reading conection failed: End of file. Closing connection.

[29.01.2024 20:32:52] : ANET ET5 PRO: Your OS syslog contains these messages close to this disconnect that might help to understand:

[29.01.2024 20:32:52] : GEEEE_i3: Your OS syslog contains these messages close to this disconnect that might help to understand:

[29.01.2024 20:32:52] : ANET ET5 PRO: syslog: Startup finished in 6.929s (kernel) + 24.659s (userspace) = 31.589s.

[29.01.2024 20:32:52] : GEEEE_i3: syslog: Startup finished in 6.929s (kernel) + 24.659s (userspace) = 31.589s.

[29.01.2024 20:32:52] : ANET ET5 PRO: syslog: [ 77.977092] usb 1-1.2: new full-speed USB device number 4 using xhci_hcd

[29.01.2024 20:32:52] : GEEEE_i3: syslog: [ 77.977092] usb 1-1.2: new full-speed USB device number 4 using xhci_hcd

[29.01.2024 20:32:52] : ANET ET5 PRO: syslog: [ 78.083225] usb 1-1.2: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.64

[29.01.2024 20:32:52] : GEEEE_i3: syslog: [ 78.083225] usb 1-1.2: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.64

[29.01.2024 20:32:52] : ANET ET5 PRO: syslog: [ 78.083247] usb 1-1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0

[29.01.2024 20:32:52] : GEEEE_i3: syslog: [ 78.083247] usb 1-1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0

[29.01.2024 20:32:52] : ANET ET5 PRO: syslog: [ 78.083254] usb 1-1.2: Product: USB Serial

[29.01.2024 20:32:52] : GEEEE_i3: syslog: [ 78.083254] usb 1-1.2: Product: USB Serial

[29.01.2024 20:32:52] : ANET ET5 PRO: syslog: checking bus 1, device 4: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2"

[29.01.2024 20:32:52] : GEEEE_i3: syslog: checking bus 1, device 4: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2"

[29.01.2024 20:32:52] : ANET ET5 PRO: syslog: [ 78.139903] usbcore: registered new interface driver usbserial_generic

[29.01.2024 20:32:52] : GEEEE_i3: syslog: [ 78.139903] usbcore: registered new interface driver usbserial_generic

[29.01.2024 20:32:52] : ANET ET5 PRO: syslog: [ 78.139941] usbserial: USB Serial support registered for generic

[29.01.2024 20:32:52] : GEEEE_i3: syslog: [ 78.139941] usbserial: USB Serial support registered for generic

[29.01.2024 20:32:52] : ANET ET5 PRO: syslog: [ 78.147390] usbcore: registered new interface driver ch341

[29.01.2024 20:32:52] : GEEEE_i3: syslog: [ 78.147390] usbcore: registered new interface driver ch341

[29.01.2024 20:32:52] : ANET ET5 PRO: syslog: [ 78.147439] usbserial: USB Serial support registered for ch341-uart

[29.01.2024 20:32:52] : GEEEE_i3: syslog: [ 78.147439] usbserial: USB Serial support registered for ch341-uart

[29.01.2024 20:32:52] : ANET ET5 PRO: syslog: [ 78.147507] ch341 1-1.2:1.0: ch341-uart converter detected

[29.01.2024 20:32:52] : GEEEE_i3: syslog: [ 78.147507] ch341 1-1.2:1.0: ch341-uart converter detected

[29.01.2024 20:32:52] : GEEEE_i3: syslog: [ 78.157301] usb 1-1.2: ch341-uart converter now attached to ttyUSB0

[29.01.2024 20:32:52] : GEEEE_i3: syslog: checking bus 1, device 4: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2"

[29.01.2024 20:32:52] : ANET ET5 PRO: syslog: [ 78.157301] usb 1-1.2: ch341-uart converter now attached to ttyUSB0

[29.01.2024 20:32:52] : GEEEE_i3: syslog: [ 229.749013] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0

[29.01.2024 20:32:52] : ANET ET5 PRO: syslog: checking bus 1, device 4: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2"

[29.01.2024 20:32:52] : GEEEE_i3: syslog: [ 229.829873] usb 1-1.2: reset full-speed USB device number 4 using xhci_hcd

[29.01.2024 20:32:52] : ANET ET5 PRO: syslog: [ 229.749013] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0

[29.01.2024 20:32:52] : GEEEE_i3: syslog: [ 229.933108] ch341 1-1.2:1.0: ch341-uart converter detected

[29.01.2024 20:32:52] : ANET ET5 PRO: syslog: [ 229.829873] usb 1-1.2: reset full-speed USB device number 4 using xhci_hcd

[29.01.2024 20:32:52] : GEEEE_i3: syslog: [ 229.940921] usb 1-1.2: ch341-uart converter now attached to ttyUSB0

[29.01.2024 20:32:52] : ANET ET5 PRO: syslog: [ 229.933108] ch341 1-1.2:1.0: ch341-uart converter detected

[29.01.2024 20:32:52] : ANET ET5 PRO: syslog: [ 229.940921] usb 1-1.2: ch341-uart converter now attached to ttyUSB0

[29.01.2024 20:33:03] : error: Reading closed serial conection failed: Operation canceled

[29.01.2024 20:33:15] : error: Reading closed serial conection failed: Operation canceled

[29.01.2024 20:33:45] : error: Reading closed serial conection failed: Operation canceled

Repetier

What port did you select? Sounds a bit like enable order matters and that means you use names /dev/... and not /dev/serial/by-path or by-id when they differ. That way it might also mi firmwares and not being satisfied or if you still have the anet to show port but associated to geee port it will fail there then.

Linux also reconnects usb ports. There is an option to disconnect usb on communication errors which might get triggered by this wrong association, so check anet if there is the usb reconnect on timeout active.

CBX_Micha

Good morning...

the connection is defined by "/dev/serial/by-path/platform-fd500000.pcie-pci-0001:01:00.0-usb-0:1.2:1.0-port0" for the Geee. I haven't touch that.

If I unplug the Geee and plug in the ANET they catch "/dev/ttyUSB0"

That looks like different names for the same physical port for me as linux-rookie...

But if I open the dropdown to chose the port there are only the same ones as I can see if the Geee is connected...

No matter which printer I have currently connected, only a single "/dev/serial/by-path/..." appears, which is completely identical in both cases. But that would be exactly what should be entered, right?
There are a lot of them like "/dev/ttyUSB0", "/dev/ttyAMA0", "/dev/ttyprintk", "/dev/ttyS0" or the whole "/dev/tty[NULL || 0-61] ", but that's something completely different and not one of the printers...

I'll read up a bit more about how Linux handles USB devices... There's obviously something I don't understand yet...

Repetier

/dev/ttyUSB0 is first seen device /dev/ttyUSB1 is second seen one. You should not use them. Linux creates a symlink in /dev/serial/by-path when it connect so it always selecting the correct one if you use that on both.

CBX_Micha

... ty a lot. Meanwhile, I have read much about it and understand it much better now, how linux handle stuff like this.

However, I don't understand why a SymLink that starts with USB0 is created when a USB device is inserted. If you were to attach this to the physical port, as a counterpart to the DeviceID system, I could still understand it... From my point of view, it would only make sense if you were only allowed to plug in a single device, which would then always be addressed as USB0 no matter which port it is in. But as? Well... It's just Linux ^^

Repetier

The devices are adding their sockets all in /dev and if you have hardware using USB it enumerates them as they get created. I think the udev system is then adding extra symlinks to make them accessible in a more predictable way.

CBX_Micha

... I get it now... Crazy Linux B)

Just found something new. Since I don't know if this is an RS problem, I'll leave it in this thread:
Component with 13 layers; Simple cover for a flush-mounted cable box.
In CURA exactly 13 layers are specified. As soon as I transfer it to RS, it becomes 27 layers for RS and that is also passed on to MARLIN.
With RS/MARLIN, the first layer that is printed is already layer 3, the second layer is already layer 6...

... do I have to understand that ?

EDIT say:
it looks like support is counted extra in RS. I could just see that while printing and hold an eye on the counter.
. End of layer 13
- Layer 14 = printing the support
- Layer 15 = printing the component
From a technical point of view, 14 and 15 are on the same print level and the identical "layer level"...

Am I not understanding something here again?

Repetier

Everything is fine. We work with different slicers and do not rely/promote their layer count concept. In Repetier-Server every time you extrude on a different z height we count this as layer. So if your start code e.g. has a prime line at other height then first layer you get already higher layer number. Also if raft is layer -2, -1 and 0 in slicer it becomes 1,2,3 in server.

CBX_Micha

Ahhh ok... Then I haven't to wonder about. Just confuses me due have noticed it the 1st time so better ask then sorry...