FW Stack & HW Dwgs?



  • Hi there all,

    HW:
    AnyCubic Delta Linear Plus, (trashed the TriGorilla Board),
    AnyCubic Delta round 24Vdc Heat Bed,
    Mini-IR Differential Optical Z-Height Probe by DC42,
    DUET3D WiFi v1.02 with only EtherNet Port (is that a version 1 or a version 2 board?),
    PanelDUE v3.0 with 7 Inch/177,8 mm Touch-Panel & LCD,
    350W 24VDC Switching Power-Supply,

    Its been awhile. I'm working to cause my AnyCubic delta to work. I replaced the skimpy TriGorilla Arduino controller/LCD clone with DUET wizardry. Nothing is working, because I have not turned it on yet. I work on it as time permits.

    About a year ago I bought the DC42 Mini-IR Dif Height Probe. Well, at first glance, I couldn't figure how to mount it on the AnyCubic effector platform. After a bit of fiddling around, and then using my X2 Seig mini-mill + ShumaTech DRO-350/iGaging digital scales, I accuarately milled the AnyCubic effector plate and also milled an aluminum right-angle extrusion adapter/heat-shield plate to form an adjustable-height probe mount. I have photos of that project if any one is interested. It mounts well. At some juncture, I will likely replace the AnyCubic effector assy with the DC42 PCB & mag-ball assy. But not right now.

    I bought a DUET controller, (marked on the board "DUET3D WiFi", which is populated via a 'socket' with an EtherNet module). I bought it about eight months ago, and then a couple of months later, I bought the associated PanelDUE (177,8mm / 7inch version) LCD-touch-panel along with the PanelDUE v3.0 controller. I acquired both the PanelDUE+Controller and the DUET-WiFi controller from the (excellent) US Distributor, "FilaStruder" (they manufacture an inexpensive filament producing apparatus, put plastic chips in, out comes filament…it produces quality filament).

    I've not powered either of these two controllers. However I finally wired the delta to the DUET-W controller using the pretty block drawing pictures provided after, finally, tracking down the hardware/electrical schematic drawings to verify that the colored block drawing connectors are properly drawn, so that I wouldn't have to return fried parts due to a possible drawing mistake. I prefer engineering drawings produced by the CAD capture process, eg, jacks & plugs with pin numbers type drawings.

    Ok, so I've wired up the DUET-W controller to the AnyCubic delta mechanics and now I figured-out how to fabricate a reasonable PanelDUE enclosure (I don't have a working 3D printer so I couldn't print an enclosure and the local guys here too greedy to print something for me that's affordable...I was quoted $300 by several different 3D printing folks). So I tracked down a manufactured sloped plastic TenTec enclosure panel for $20 U$ Dollars via Amazon; milled the aluminum LCD bezel and have mounted a DB-15 inter-subsystem connector for external cabling to the delta+DUET-W controller. I desire to check the HW/electrical schematic drawing of the LCD v3.0 controller, but for the life of me, I can't find those drawings or schematics anywhere on the 'Net.

    Can someone please point me to where the KiCAD (or what ever?) electrical drawings for the PanelDUE LCD v3.0 controller are located so that I can verify the electrical connections before I wire the connectors and cables. 🙂

    And then, what are the names of the firmware modules required for each of the controllers that I have? Is it a stack that is loaded one after the other into specific flash locations or just one or two .hex/.bin files that need be uploaded into the hardware? Since I plan to use just the PanelDUE for local control, but be able to transfer motion path files via my local IntraNet, what files are required to support both functionality? I am confused what is required and which versions should be loaded at this time juncture.

    Re; the DUET-W to PanelDUE 3.0 controller, how long may the so-called "4-way" 4-wire cable be? I read something about 800mm/31inches, can it be longer and still reliably work?

    And then finally, I happened to locate the most recent schematic for the V2 DUET WiFi board, and noticed that there is a wiring difference between the version I have (I think its a v1.02, DUET-WiFi w/EtherNet). In the later version each of the stepper drivers pin-out the SG signal, which are then logically OR'd (via an HC32) into an ARM port, whereas the board I have those SG pins are not connected to anything. Can I add an HC32 and wire those pins and then use the FW for the V2 board on my older board? Can that work, or must I modify the software and recompile?

    thanks in advance for all the good hard work.

    3mm


  • administrators

    PanelDue PCB files are at https://github.com/dc42/PanelDue/tree/master/PCB. However, the pinout of the 4-pin connector is also marked on the PCB.

    The standard firmware binary for the Duet Ethernet supports the web interface and PanelDue. Current stable firmware for the Duet is at https://github.com/dc42/RepRapFirmware/releases. Firmware for PanelDue it at https://github.com/dc42/PanelDueFirmware/releases.

    The 4-way cable between PanelDue and the Duet can be longer than 800mm. the one on my delta is 1.5M. However, you should keep the resistance per conductor below 0.1 ohm. If you go much above 2m then you might possibly need to reduce the baud rate from the default of 57600.

    The firmware does not currently use the output of that HC32, and it's likely that it never will. I originally thought we would need that signal in order to respond quickly to motor stalls when we implemented stall detection, but it turned out not to be needed.



  • @dc42:

    PanelDue PCB files are at https://github.com/dc42/PanelDue/tree/master/PCB. However, the pinout of the 4-pin connector is also marked on the PCB.

    The standard firmware binary for the Duet Ethernet supports the web interface and PanelDue. Current stable firmware for the Duet is at https://github.com/dc42/RepRapFirmware/releases. Firmware for PanelDue it at https://github.com/dc42/PanelDueFirmware/releases.

    The 4-way cable between PanelDue and the Duet can be longer than 800mm. the one on my delta is 1.5M. However, you should keep the resistance per conductor below 0.1 ohm. If you go much above 2m then you might possibly need to reduce the baud rate from the default of 57600.

    The firmware does not currently use the output of that HC32, and it's likely that it never will. I originally thought we would need that signal in order to respond quickly to motor stalls when we implemented stall detection, but it turned out not to be needed.

    @David,

    I see on the V3.0 LCD controller sch, that the Power-Pins are arranged to prevent TFT panel burn-out due to 'flipped-around' improper 180º connector mating. In lieu of mating-plug-blocks…very good.

    thanks

    3mm -


  • administrators

    @3mm:

    I see on the V3.0 LCD controller sch, that the Power-Pins are arranged to prevent TFT panel burn-out due to 'flipped-around' improper 180º connector mating. In lieu of mating-plug-blocks…very good.

    thanks

    3mm -

    Thanks! I designed the very first version of PanelDue with that in mind.



  • @David,

    Hi…

    https://github.com/dc42/RepRapFirmware/releases

    Perhaps I'm missing something here? I'm confused, which items listed below, from the above cited URL need be loaded into my DUET3D WiFi w/EtherNet module?

    Thanks in advance…3mm
    = = = = = = = = = = = = = = = = =

    Here is the list:
    Release 1.21
    dc42 dc42 released this 5 days ago
    Duet2CombinedFirmware.bin
    DuetEthernetFirmware.bin
    DuetMaestroFirmware.bin
    DuetWebControl.zip
    DuetWiFiFirmware.bin
    DuetWiFiServer.bin
    DuetWindowsDriverFiles.zip
    iap.bin
    iap4e.bin
    iapalligator.bin
    iapradds.bin
    RepRapFirmware-Alligator.bin
    RepRapFirmware-RADDS.bin
    RepRapFirmware.bin
    Symbols-CoreNG-SAM3X8E.zip
    Symbols-CoreNG-SAM4E8E.zip
    Symbols-CoreNG-SAM4S.zip
    Symbols-RepRapFirmware-Duet085.zip
    Symbols-RepRapFirmware-Duet2.zip
    Symbols-RepRapFirmware-DuetM.zip


  • administrators

    See the text on that Releases page below the list of files.



  • @dc42:

    See the text on that Releases page below the list of files.

    David,

    For me, here is the confusion, my DUET3D board is marked, "DUET3D WiFi" not "DUET3D EtherNet" yet I suppose that I should infer that its (obviously) an EtherNet rather than a WiFi as it sports an EtherNet module instead of a WiFi unit. It is not clear to me the numerical version of the board is either. I get the impression that the board is a version 2 board, although it is marked "V1.02". I've asked about this before and so far, I do not believe that I have seen an authoritative clarification.

    Not intending to beleagure the matter, which of these two load sequences are the one? (so-to-speak)

    @dc42:

    For Duet WiFi: DuetWiFiFirmware.bin or Duet2CombinedFirmware.bin (which are the same file), DuetWiFiServer.bin and iap4e.bin
    For Duet Ethernet: DuetEthernetFirmware or Duet2CombinedFirmware (which are the same file) and iap4e.bin

    So?
    Is the load instructions for the DUET3D WiFi board thus:

    • load in this order
    • Duet2CombinedFirmware.bin (same as DuetWiFiFirmware)
    • DuetWiFiServer.bin
    • iap4e.bin

    or is the load instructions for 'EtherNet' version of the DUET3D WiFi board thus:

    • load in this order
    • Duet2CombinedFirmware.bin (same as DuetEthernetFirmware)
    • iap4e.bin

    And do the FW modules need be loaded in proper sequence or is that handled by the loader?

    Thanks in advance (for your patience with my questions)

    3mm


  • administrators

    The second one is correct. I suggest you upload iap4e.bin first in case the version already on your SD card is very old.



  • @dc42:

    The second one is correct. I suggest you upload iap4e.bin first in case the version already on your SD card is very old.

    David,

    Thanks for the heads up. However, when I visit the cited URL:
    https://github.com/dc42/RepRapFirmware/releases
    and I try to download the appropriate .bin files, I receive xml text stating "This XML file does not appear to have any style information associated with it. The document tree is shown below." and then fills the page with:

     <error>`SignatureDoesNotMatch`
    <message>The request signature we calculated does not match the signature you provided. Check your key and signing method.</message><awsaccesskeyid>AKIAIWNJYAX4CSVEH53A</awsaccesskeyid><stringtosign>AWS4-HMAC-SHA256
    20180327T095237Z
    20180327/us-east-1/s3/aws4_request
    e569b165028c78a819bc12c0250301f000c43637d09c519dd92bd1944dfdb42e</stringtosign><signatureprovided>72b46869a9bec89d191167ecc41002ab1adeb1432390570a281955e02f01628b</signatureprovided><stringtosignbytes>41 57 53 34 2d 48 4d 41 43 2d 53 48 41 32 35 36 0a 32 30 31 38 30 33 32 37 54 30 39 35 32 33 37 5a 0a 32 30 31 38 30 33 32 37 2f 75 73 2d 65 61 73 74 2d 31 2f 73 33 2f 61 77 73 34 5f 72 65 71 75 65 73 74 0a 65 35 36 39 62 31 36 35 30 32 38 63 37 38 61 38 31 39 62 63 31 32 63 30 32 35 30 33 30 31 66 30 30 30 63 34 33 36 33 37 64 30 39 63 35 31 39 64 64 39 32 62 64 31 39 34 34 64 66 64 62 34 32 65</stringtosignbytes><canonicalrequest>GET
    /15792831/ce8d7750-2cf2-11e8-886b-b6f0aeb05954
    X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20180327%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20180327T095237Z&X-Amz-Expires=300&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B%20filename%20Duet2CombinedFirmware.bin&response-content-type=application%2Foctet-stream
    host:github-production-release-asset-2e65be.s3.amazonaws.com
    
    host
    UNSIGNED-PAYLOAD</canonicalrequest><canonicalrequestbytes>47 45 54 0a 2f 31 35 37 39 32 38 33 31 2f 63 65 38 64 37 37 35 30 2d 32 63 66 32 2d 31 31 65 38 2d 38 38 36 62 2d 62 36 66 30 61 65 62 30 35 39 35 34 0a 58 2d 41 6d 7a 2d 41 6c 67 6f 72 69 74 68 6d 3d 41 57 53 34 2d 48 4d 41 43 2d 53 48 41 32 35 36 26 58 2d 41 6d 7a 2d 43 72 65 64 65 6e 74 69 61 6c 3d 41 4b 49 41 49 57 4e 4a 59 41 58 34 43 53 56 45 48 35 33 41 25 32 46 32 30 31 38 30 33 32 37 25 32 46 75 73 2d 65 61 73 74 2d 31 25 32 46 73 33 25 32 46 61 77 73 34 5f 72 65 71 75 65 73 74 26 58 2d 41 6d 7a 2d 44 61 74 65 3d 32 30 31 38 30 33 32 37 54 30 39 35 32 33 37 5a 26 58 2d 41 6d 7a 2d 45 78 70 69 72 65 73 3d 33 30 30 26 58 2d 41 6d 7a 2d 53 69 67 6e 65 64 48 65 61 64 65 72 73 3d 68 6f 73 74 26 61 63 74 6f 72 5f 69 64 3d 30 26 72 65 73 70 6f 6e 73 65 2d 63 6f 6e 74 65 6e 74 2d 64 69 73 70 6f 73 69 74 69 6f 6e 3d 61 74 74 61 63 68 6d 65 6e 74 25 33 42 25 32 30 66 69 6c 65 6e 61 6d 65 25 32 30 44 75 65 74 32 43 6f 6d 62 69 6e 65 64 46 69 72 6d 77 61 72 65 2e 62 69 6e 26 72 65 73 70 6f 6e 73 65 2d 63 6f 6e 74 65 6e 74 2d 74 79 70 65 3d 61 70 70 6c 69 63 61 74 69 6f 6e 25 32 46 6f 63 74 65 74 2d 73 74 72 65 61 6d 0a 68 6f 73 74 3a 67 69 74 68 75 62 2d 70 72 6f 64 75 63 74 69 6f 6e 2d 72 65 6c 65 61 73 65 2d 61 73 73 65 74 2d 32 65 36 35 62 65 2e 73 33 2e 61 6d 61 7a 6f 6e 61 77 73 2e 63 6f 6d 0a 0a 68 6f 73 74 0a 55 4e 53 49 47 4e 45 44 2d 50 41 59 4c 4f 41 44</canonicalrequestbytes><requestid>A20EFC85785A4B48</requestid><hostid>hJDaE4Dh70jUrSq6XEqKNqH95/aHA1wscec08ivjvBwxcr9lDTRxUh4+77hYPgikZs+HueeMJFY=</hostid></error>
    
    

    Only the SOURCE.ZIP & SOURCE.tgz (RepRapFirmware-1.21.zip) files are downloadable.

    Got any clues about what's happening?

    Thanks in advance

    3mm


  • administrators

    It works for me. I suspect either network glitch or a virus on your PC.



  • @dc42:

    It works for me. I suspect either network glitch or a virus on your PC.

    David,

    Going back a few DUET version iterations, other .bins download properly. As for a virus, I have up to-date McAfee AV signature templates installed and, frankly, as I no longer surf the web with java-script enabled, and I have all the download-ports locked off, I haven't had a virus in over 20 years. I also use the NoScript plug-in for Mozilla. I don't believe that I have a virus that only affects your recent .bin files. For instance, I can download any of the PanelDUE .bin files from:
    https://github.com/dc42/PanelDueFirmware/releases

    And I can download "RepRapFirmware-Duet06-085.bin" file from Version 1.21RC5 anchor. But not all of those files are downloadable?! So something screwing is happening with the server, in my estimation.

    If I'm having this problem so are others who are likely not so disposed to yak about it…

    Thanks in advance

    3mm
    ps..going through the SOURCE.zip file, I found via the 'edgeRelease' folder in the RC3 directory all of the files you cited, so I'm probably ok in terms of acquiring the requisite upload files, FYI. But something screwy is still happening in any case. Thx and good nite's respite to you.



  • @3mm:

    If I'm having this problem so are others who are likely not so disposed to yak about it…

    Thanks in advance

    3mm

    just tested it, downloads work for me…


  • administrators

    Try clearing your browser cache?



  • @whosrdaddy:

    If I'm having this problem so are others who are likely not so disposed to yak about it…

    Thanks in advance

    3mm

    just tested it, downloads work for me…



  • @dc42:

    Try clearing your browser cache?

    David,

    I auto-clear browser cache each time I power-down.

    One last wiggle…on a hunch, I fired up McNazi$oft's InterNut-Exploder v11 (shipped with Win7 OS), and sure enough, it downloads all the .bin files properly. Which web-browser and version do you use? Just curious. Maybe its something in the way my NoScript module is intercepting suspiscious client-server messages to & fro the webserver? But in any case, IE works....I don't use IE due to it the program's inherent security risks. My employer, ITT Defense, also doesn't use IE for that same reason, all our 57,000 corporate workstations.

    Thanks in advance

    3mm


  • administrators

    I normally use Chrome with github.



  • @dc42:

    I normally use Chrome with github.

    David,

    It lives. 🙂 I don't know for certain what its doing, but things are alive. The mini-IR probe seems to be working but the effector stops about six inches…15cm above the heat bed, it goes through its ritual, but the IR sense indicator doesn't illuminate, unless I stick a finger up close to it. I get the delta to home, it does that ok, but the XYZ movement presets are not all the same. For instance the XY preset buttons are 100, 50, 10, etc, while the Z axis movement presets are 10, 5 & 1, etc. The SW seems to be configured for something other than a delta... I suspect that its all config, macros, etc at this juncture. I've got a learning curve to wade through. The PanelDUE is v1.17 and I don't know what the DUET3D is running? As I recall there is command for querying the version. I'll look it up.

    Ok, I'll wade through the docs and see what gives. Thanks for your help and your good efforts. I'll try to pestering the community for a change :)).

    Cheers

    3mm
    ps..by any chance you a Ham? If so, there's a group of us that meetup Wednesdays via EchoLink @8pm EST and on Fridays we do a net on 40m, it might be a little early for ya? But the spherics should be good.


  • administrators

    M115 will tell you what firmware version you are running; or just look at the Settings General page of DWC.

    The Z movement presets are deliberately different from XY because you need greater resolution on Z.

    Under what conditions does the effector stop 6" above the bed? Have you set P500 in your G31 command?

    Many years ago I thought about getting a ham radio license, but so far I haven't.


Locked
 

Looks like your connection to Duet3D was lost, please wait while we try to reconnect.