Posts made by 3mm

Hello All,

What is the last release version of SW that supports the DUET EtherNet v1.02 hardware controller?

thanks in advance...3mm

@bberger said in Best way to increase rod spacing without 3D printed parts?:

@3mm because I want to get rid of the flying extruder.

I have hard mounted the Orbiter v2 on my Smart Effector with an approx 7cm adapter and prints come out insanely beautifully compared to my (genuine) BMG flying extruder (with only 15cm bowden).

I have way less ringing, can run 5k accel / 600 jerk / 100-150mm/s, 0.015 PA, 0.6mm retractions and no input shaping with barely any artifacts.. (I had to run 70mms, 3k accel, 50Hz DDA, 300 jerk, 1.5mm retractions to get any resemblance of a good looking print on my flying BMG before, I contribute that to the bowden tube yanking on the SE, I doubt that's the 150g saving on mass of the flying extruder..) - and also that 7cm "lever" with the mass of the motor up that high has me a bit concerned..

I'm currently prototyping some 80mm adapters in PLA-CF, trying to keep them flat so it can possibly be laser cut / milled out of Alu/CF in the future.

I'm not after speed benchys, but more after rapid prototyping..

@bberger

HI. Sounds like you have a better handle on things than I do. I'm still dealing with a few significant artifacts, however, my prints became signficantly better when I implemented my own (OScad) BMG flying-extruder for my SmartEffector and linear-rail magball PCB adapters. I designed my linear-rail MagBall adapters to use the SE effector MagBall PCB. My Bowow tube is about 18cm long. But I'm not seeing a any major ringing, but anything above a specific height gets mangled.

I'd be interested to see your flying-extruder configuration if you happen to have any photos of it before you chucked-it out?

In any case, good luck with your strategy, sounds interesing.

3mm

@bberger

If I understand things correctly, why not implement a flying-extruder mount for the Orbiter? That way you everything remains as it was designed and intended to work.

3mm

@bberger

Pardon me for butting in, however, I solved that problem with my BMG BondTech direct drive extruder on my AnyPubic delta, by designing and printing a nifty problem solving flying-extruder platform supported by soft surgical tubing. I looked each of the direct-drive extruders you cited, I speculate that they are all roughly the same size and weight of of my BMG BondTech. There is no tilt or weight added to my Smart-Effector. I am very happy with the arrangement I fabricated. Not what you'd like to see, but it is certainly a doable work-around.

Eventually I'll get off my lazy butt to upload the details along with oScad design files so others can hack it up as they choose.

3mm

@heinrich-platau

Hey, probably shouldn't need to remind anyone, but when implementing high-Voltage wiring, to use extra safe wiring methods. heat-shrink where possible, Insulate all exposed current carrying metals, enclose it if possible, definently fuse it, etc. And be sure to mount the SSR on a heatsink, preferrably finned. In addition to one not desiring to burn-down one's house, it is also unpleasant to electrocute one's pets, children, wife and-or self!! ;-}

Rotsa Ruck!

3mm

@mdejong

Since when is Pulse Width Modulation, not On/OFF?

3mm

@phaedrux and All,

Interesting 'intro' post by our late friend Danal.

See: https://forums.autodesk.com/t5/community-meet-greet/hi-from-texas-danal-estes/td-p/7459955

3mm

Hello,

Since I added my homebrew flying effector and modified the DUET Smart-Effector linear rail adapters, (shortened bowden tube to about 6inches/152,4mm, from 80inches/203,2cm), my mostly homebrew delta printer is more or less behaving itself! Yeah!!

However I have a question. When I'm auto-cal'ing, I notice that the Z-Probe status indicator infrequently, as the nozzel touches the bed, it'll turn red with a 1000 depiction, while many of the other touch-downs remain 0 without the background changing to red. What does this represent? Is it an indication of something that needs to be remedied?

Thanks in advance...3mm

@droftarts

Ok, will do. The screen re-reverted user interface returned after a power-cycle. I getting used to it, at first things seem scattered randomly about, but there is actually a logic strategy in it's implementation. On a 38,1cm/15" LapTop screen the fonts are a bit small, but with the 'dark' its useable. I'll get used to it. I printed a few things tonight using the Linux box and the new version. The user interface is obviously designed for production!! Heh heh. Gotta love it!

Thanks for everything...3mm

@droftarts,

Note that this WILL update DWC to version 2.x, which is
a bit different from 1.x. You can go back to 1.x if you prefer it.

I clicked the 'Revert' to older user interface button, but where is the revert back button? I'd be interested to try to use that new interface for a time, to see how it works. Need I reinstall the whole FW packaged to regain that user interface?

Thanks in advance...3mm

@SupraGuy

Well I finally have it working. I discarded the xubuntu 20.04, just too buggy and virtually no information that matched the mods from the ubuntu fork. Now, I need to do is make hack together an EtherNet 'switch', a couple of toggle switches that routes the laptop either to my InterNet router or to the printer, OR the printer to the InterNet router! I've got all the configurations working. Essentially very similar to your strategy.

Thanks for the indepth answer.

3mm

@droftarts said in Connect Ubuntu PC Directly to DUET EtherNet Without a Router?:

@3mm Thanks for the information. You didn't update to 2.05.1? The M122 command reports "Used output buffers: 6 of 24 (8 max)", which is high. There were quite a lot of fixes in later RRF 2.x versions for this issue.

To update, you should be able to upload this file to DWC: https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip
Download it as a zip (don't unzip it), and upload it to the Duet via DWC > Settings > General > Upload Files button.

Note that this WILL update DWC to version 2.x, which is a bit different from 1.x. You can go back to 1.x if you prefer it.

Ian

@droftarts (& DC42),

Ok, I uploaded v2.05 to the printer, and while, the new user interface is taking a bit of time with which myself to become accustomed, the http time-out (EtherNet dropout) problem has vanished, or so it seems. I have not tested every function but the newer version seems to have remedied the problem.

Thanks for the link and the instruction for installation.

3mm

@SupraGuy said in Connect Ubuntu PC Directly to DUET EtherNet Without a Router?:

Crossover cable issue has been addressed.

If I were dealing with a Linux PC, I'd probably use a separate network card and configure DHCP on that interface.

Google gave me a basic link to configure it here

This also allows you to use it with a switch for other network functions for things that you might not want connected to the Internet. You can also edit the configuration file to always assign the same IP address by MAC address, allowing you to always be able to find any given host by IP address, when desired.

My ISP router doesn't support assigning addresses to devices, so I shut off it's DHCP server entirely, and have set up DHCP services on a Linux machine so that I can always find things like my MotionEye cameras, the Duet, and a few other things on the network.

Edit: The advantage to doing it this way is that you can still take the Duet based printer somewhere else and still easily connect it to most networks.

@SupraGuy

Unfortunately, my PC is a laptop, and actually I did try (using ubuntu 14.04 LTS) the DHCP method, but I was suffering the EtherNet dropout problem and DC42 asked that I capture the failure modality using WireShark, which I was unable to cause to work properly with that version of Linux. So I dug out an HP-8640p LapTop onto which I loaded a different version Linux OS & WireShark. However I could not cause that configuration to easily swap between static IP and DHCP, as I would like to be able to connect the LapTop to the InterNet occasionally, and other times only to the printer. Then I broke that OS somehow and I've given up trying to resolve that problem, I'm just going to rebuild the OS with a standard Ubuntu 20.04.10 LTS Linux. The Net Mapping (NetPlan) software is very powerful, but seems a bit sketchy, in my opinion.

Thanks for your suggestions - 3mm

@droftarts said in Connect Ubuntu PC Directly to DUET EtherNet Without a Router?:

@3mm Thanks for the information. You didn't update to 2.05.1? The M122 command reports "Used output buffers: 6 of 24 (8 max)", which is high. There were quite a lot of fixes in later RRF 2.x versions for this issue.

To update, you should be able to upload this file to DWC: https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip
Download it as a zip (don't unzip it), and upload it to the Duet via DWC > Settings > General > Upload Files button.

Note that this WILL update DWC to version 2.x, which is a bit different from 1.x. You can go back to 1.x if you prefer it.

Ian

Thank you for your time in this matter and for the update link. I'll give it a whirl... In the mean time, I have successfully broken the Linux software connection point. I can not cause the EtherNet port to talk to the InterNet or to the printer. There is a bug in the mapping (NetPlan) software and it broke something for which I can not find any documentation. I chose xubuntu as it sports a smaller memory usage footprint than the standard ubuntu version. Only there is a problem, that port of Linux is poorly documented, does not have a large user community AND they changed a lot of the ways Linux operates AND it is really buggy! In my opinion. So, I'm going to overwrite it with a ubuntu 20.04.10 LTS OS, to try to get back to a standard Linux normalicy, so if there is a problem, I'll be able to find literature for it.

Thanks a lot...3mm

@3mm said in Connect Ubuntu PC Directly to DUET EtherNet Without a Router?:

@dc42 said in Connect Ubuntu PC Directly to DUET EtherNet Without a Router?:

@3mm said in Connect Ubuntu PC Directly to DUET EtherNet Without a Router?:

Maybe its a really old DUET-E firmware version problem thats been fixed?

1. Please run M122 and post the resulting report here.

2. It may help us diagnose this if you install WireShark on the notebook, capture the data to/from the Duet and stop the capture immediately after a disconnection. Then attach the capture file to a post.

Hi DC42,

I down-loaded & installed WireShark on the Linux box, now I gotta fiddle around a bit to use it, and tomorrow I'll upload the M122 output, gotta hit the sack, its 4:00am here in LA, and I have a meeting with pirate atty (aren't they all?) tomorrow. Thanks for your attention to this matter.

3mm

Hi DC42,

<sigh> Well, the version of Ubuntu and the age of the Dell NoteBook running ubuntu 14.04 LTS that I was trying to use with the DUET-E controller, and then later install WireShark into...not a good fit, it just did not work correctly. So, now that I've changed to a HP 8640P LapTop, and have installed the latest xubuntu (ubuntu 20.04.10 LTS) Linux operating system and installed the latest WireShark, --those peices are working properly together. The for WebControl, FireFox version: 86.0 (64bit) Ubuntu canonical - 1.0, which is a fairly recent version.

I now am able to finally cause the new laptop+ubuntu OS to connect to the DUET-E controller, (using NetPlan) I finally have been able to acquire the WireShark diagnostic traffic file that you requested.

So now, just as before, everytime I connect (via static IP & a direct EtherNet CAT5 cable) from the LapTop to the DUET-E controller, the connection remains functioning (40 + minutes, while moving the hot-end, setting the temps, heating things up, etc) as long as I do not access the G-Code Files directory which loads and displays all the files. The EtherNet remains connected for around 5 seconds and then drops the connection and emits an 'HTTP timeout error'. The only way I can reconnect is to power-cycle the DUET-E controller.

The LapTop IP Address: 192.168.2.1/24 (the /24 is required by ubuntu)
DUET-E Controller Addr: 192.168.2.2/24 (ditto)
NetMask: 255.255.255.0

network configuration file: /etc/netplan/99_config.yaml

  network:
    version: 2
    renderer: networkd
      ethernets:
        enp0s25:
          addresses: 
                 - 192.168.2.1/24
                 - 192.168.2.2/24

sudo netplan apply<cr>

M122 Status List:
M122 Status List.txt

WireShark Diagnostic (dropout occurs around 1331) file - Rename file from .txt to .pcapng:
EtherNet_DropOuts_Around_1331_pcapng.txt

Thanks in advance for your help.

3mm

@dc42 said in Connect Ubuntu PC Directly to DUET EtherNet Without a Router?:

@3mm said in Connect Ubuntu PC Directly to DUET EtherNet Without a Router?:

Maybe its a really old DUET-E firmware version problem thats been fixed?

1. Please run M122 and post the resulting report here.

2. It may help us diagnose this if you install WireShark on the notebook, capture the data to/from the Duet and stop the capture immediately after a disconnection. Then attach the capture file to a post.

Hi DC42,

I down-loaded & installed WireShark on the Linux box, now I gotta fiddle around a bit to use it, and tomorrow I'll upload the M122 output, gotta hit the sack, its 4:00am here in LA, and I have a meeting with pirate atty (aren't they all?) tomorrow. Thanks for your attention to this matter.

3mm

@gaweyo

sounds like you might have dhcp client still
running, does the IP for the PC change
when it stops working or does it say static?

No. But thanks for the reply.

@droftarts

Is the netbook connected by WiFi to your network as well?
No. WiFi is disabled.

I have further information. When the NoteBook connects to the DUET-E controller & the Web-Console, EtherNet/Controller stays connected so long as there is not a lot of I/O hand-shaking. For instance, I can issue motion commands via the web-interface without any disconnects, but when I click the 'G-Code Files' tab, sometimes it'll load the page and then disconnect, other times it'll instantly disconnect. The only way I can reconnect and have a stable connection is power-cycling the DUET-E (EtherNet) v1.02 controller.

When the connection crashes, the WebConsole emits an error message:

! Request Timeout
The last HTTP request has timed out. Please make sure the connection between your
device and the board is not interrupted.

DUET-E Controller Info:

(old)
Duet 2 WiFi/EtherNet Board (v1.02)
Firmware: 2.03 (2019-06-13b2)
Web Interface: 1.21

The settings in the DUET-E controller are:

M552 S0 ; Disable network
; ----------------- static IP direct connect via CAT5e cable DUET-E controller config ------------
M552 P192.168.2.2     ; Static IP Addr - DUET's IP Addr
M553 P255.255.255.0 ; NetMask 
M552 S1                      ; Enable network

The settings in Ubuntu 14.04 Linux - /etc/network/interfaces file are:

auto lo
iface lo inet loopback

auto eth0 
iface eth0 inet static
     address 192.168.2.1
     netmask 255.255.255.0

While in the Ubuntu DeskTop 'NetworkManager' taskbar dialog
the IPv4 Settings are:

  Address: 192.168.2.1
  Netmask: 255.255.255.0
  Gateway:   0.0.0.0

I think this should be working.

Maybe its a really old DUET-E firmware version problem thats been fixed? The NoteBook Linux seems to be doing something that may be
scrambling the controller logic?? It isn't a perfect world. Although these DUET products are very good IMO. I was lucky finding you guys. Thanks.

3mm

@droftarts

Hi, after screwing around quite a bit and reading the URLs you cited and a few others derived from those you cited, I was able to connect the NoteBook running Ububut 14.04 Linux, directly (using a straight through CAT5e cable) to the DUET-EtherNet (v2) controller, via static IPv4 configuration. However, it wont stay connected. It acts like a timing problem? I'm wondering what the minimum version of (FireFox) web-browser is required? And maybe, is there a time-out retry setting somewhere in the controller firmware? It occurs to me that the NoteBook, a Dell "Inspiron Mini 1012" just might be too old...too slow. I have a marketing brochure dated 1999 for that model.

Any ideas to what might be a solution? I've changed cables; fiddled around with settings in the Linux. I may try changing to a more recent PC with a more recent version of Linux.

Thanks in advance for your time in this matter.

3mm

@droftarts

Excellent. Thank you so much!

Best Regards

3mm