which version of DWC are you running? I am on 1.22.5 or 1.22.6 . there was one release that was not on the git site listed, but on dc42's page or linked somewhere else. RRF3 is probably the way to go for a lot of reasons, but right now I am staying with it until i get my HW issues worked out.by sinned - Firmware - experimental, borrowed, and future
I think you might have a voltage issue then. How are you powering the controller? If you are using 5V from USB it might not have enough capacity. I found that with the ReArm board with the ethernet controller module. With UBS only, it was constantly misbehaving. Once I put dedicated 12V adapter on the controller and used PS_ON to control the main PSU power, it got reliable.by sinned - Firmware - experimental, borrowed, and future
QuoteMKSA @jay_s Looks like this huge delay is due to how slow the scripts are transferred to the PC ??? Am I the only one facing this ? Did you try to define all your network parameters in your config file? I had better luck hard coding the static IP and gateway with M552, M553 and M554 in the config file than with DHCP. I also forced compatibility with M550 I think I did it this way- Mby sinned - Firmware - experimental, borrowed, and future
sure, that works! but the thing is you need some sort of device to parse it and direct it to a display. Since I longer use the raspi with RRF, what is missing is the computer to process the M408 data and a means to display it. I am curious how you are parsing the M408 data and how far back a data stream you archiveby sinned - Firmware - experimental, borrowed, and future
dc42: are you saying that the LPC subsystem is already spitting out the datastream ? what I was refering to was an LCD connected to the raspi. the data stream parsed by Octoprint and processed through the raspi/GPIO pins to a 4 line 20x4 HD44780 display. there was another one that did it with I2C - see in my pic that the 12864 is connected to the RAMPs? the 20x4 is connected to the pby sinned - Firmware - experimental, borrowed, and future
I think that a 1264 GLCD is nice too have for BASIC machine control. Other than that, one of the plugins i used to use with octoprint was a 4 line display that parsed the state change strings and would output on the LCD. It would work in conjunction with Octoprint, ATX-Pi breakout hat, and PSU_Control. i miss that having switched to LPC port. It would give the state, the temps, percent completeby sinned - Firmware - experimental, borrowed, and future
sdavi - thanks for explaining it so well. I have forgotten so much of this since college. 1. so by moving the tcp/ip stack off the LPC,does it gain us any more memory to the system as well? is this desirable to do anyhow? 2. what pins does the esp/wifi unit need to work? will it free up more pins on the LPC boards then? 3. can you compare performance overall between Eth0 and Wifi? is it mby sinned - Firmware - experimental, borrowed, and future
question about the ESP-Wifi integration: Is the ESP unit working as a bridge to communicate to the network or is it working as an integrated piece of hardware with the LPC processor? What if any code runs on the ESP unit? Perhaps I misunderstand, do we need both Ethernet AND Wifi modules compiled in to the FW?by sinned - Firmware - experimental, borrowed, and future
that's great news! I look forward to your updatesby sinned - Firmware - experimental, borrowed, and future
this works great on SKR 1.3 with an LCD. are you sure you are looking at the right place? the binary is already compiled. start here - look to the 'right' for releases, there are 6 so far. binary is here - sample board configs are here- i wrote up my notes and put them here- i need to do a bit of updating, but you might find some of the content relevent. you might find this page usby sinned - Firmware - experimental, borrowed, and future
sdavi- thanks for he heads up! for now i might try to go with 2 Z motors- X, Y, Z, Z1, E0 to stay at 5. recompiling will be a project for me right now.by sinned - Firmware - experimental, borrowed, and future
Now that I have the IR probe worked out, I want to try 3 independent Z-screw leveling. My printer suffers from a bit of layer mis-registration due to the dual screw Z axis is eccentric to the Z guide rods. I am hoping that this will resolve itself if I add another screw and 2 independent Z motors. I'd like to keep the option for using E1 later open. So I am looking for spare pins to assign to thby sinned - Firmware - experimental, borrowed, and future
Quotesinned So to use the analog Mode 1, the Smart IR needs to be fed +5V 3.3V from somewhere, and the Signal and GND wires get connected to say the HE2 thermistor input. The +5V voltage can come from the same place that the LCD or servo would have gotten power from. I'd really appreciate it if someone could comment on my understanding and scheme, I would appreciate it. I separated the Siby sinned - Firmware - experimental, borrowed, and future
wow, i really misundertstood this. I will try again EDIT: I think I have this figured out. I did not understand how the analog signal worked compared to the digital. For some reason, I had it in my head that analog was either OFF or ON => 0 or 1000. The conventional endstop pins are digital GPIO pins. 1.24, 1.25, 1.26 ... 3.3V The reprap configurator will spit this out as the ideal confiby sinned - Firmware - experimental, borrowed, and future
Sometimes I really like the dozuki documentation, then sometimes I hate it because I think its missing the basic info. 1. Going the route of the selecting the 'Unmodulated or Smartr IR Probe' spits this out- Analog with HIGH signal. M558 P1 H5 F120 T6000 ; set Z probe type to unmodulated and the dive height + speeds 2. P5 is Digital connected to Zprobe input, HIGH forby sinned - Firmware - experimental, borrowed, and future
Anyone tried using an IR Probe with the LPC port? How did you configure it? I can only get it to work in analog mode. I suspect its might be because I have not defined the modulation in board.txt but I am not sure. I tried M558 P1 H5 F120 T6000 ; DID NOT WORK set Z probe type to modulated and the dive height + speeds but I could not see any change in DWC when I triggeredby sinned - Firmware - experimental, borrowed, and future
BigTreeTech released the SKR 1.4/Pro/Turbo whatever with the 1769 chip and apparently all the pins available on the board. Good news for connecting other drives and Ethernet. They have a Fb site- though its dominated by Ender/BL Touch/Marlin queries. I considered ordering one to play with for giggles- they are ~$20. I was thinking to do it with RRF3. Thoughts anyone?by sinned - Firmware - experimental, borrowed, and future
Yay-Thank You!by sinned - Firmware - experimental, borrowed, and future
Quoteleadinglights Warning, this may be Too Long Did Not Read, it was damn near Too Long Did Not Write. Thank you for writing this up!by sinned - General
I am hoping to confirm this- if you are using a board with modular stepper drivers, like A4988 or DRV8825's, there is no need for using the M906 command to define motor or idle currents. M906 X800 Y800 Z800 E800 I30 ; set motor currents (mA) and motor idle factor in per cent thanks in advanceby sinned - Firmware - experimental, borrowed, and future
Quotesdavi @sinned your also still running RC1 of 2.04. The latest v2.04 was uploaded earlier this month. @dc42- I have done M303 a couple of times. I was reading the wikipedia page on it too before this happened. I was actually contemplating going to RRF3 .... I will stay with 2.04 for now I think.by sinned - Firmware - experimental, borrowed, and future
original post/thread is here- i stuck an ammeter inline to try and see what is going on. i am getting random 'Heater Fault" reporting. It does not show up on the GCode console. the print does not pause either- the heaters are still on and the print is still going. the false positive is just as bad as a real one in my mind. Is this a RRF issue or LPC port issue? here is M122 output -by sinned - Firmware - experimental, borrowed, and future
Thanks all. 1. My silicone bed heater is mains powered and controlled from the heater output to an SSR. The aluminum bed has an additional ground, going back to mains ground. The thermistor is 'built in' to the bed. My hotend is controlled similarly- I have a 24V buck converter feeding an external MOSFET unit. I am considering the DSO138 mini-scope from JYTech /Banggood? It seems to be welby sinned - Firmware - experimental, borrowed, and future
I am pretty sure its getting noise from somewhere or there is the tiniest of connection issues. i dont have an oscilloscope to check Agnd, Aref, Vref. every once and a while after i get 2-3 layers into a print, the controller will spit out a heater fault but I dont have any more info to figure it out with. the fault message usually only appears on the paneldue consol, not DWC. that is one tby sinned - Firmware - experimental, borrowed, and future
QuotePB 3. On temperature plot I notice short but high spikes at all thermistors. Probably only one reading wrong. Not causing problems. @PB- did you get this figured out? I have similar and its driving me nuts tryging to track it down. Anyone elser get this behavior ?by sinned - Firmware - experimental, borrowed, and future
for all that work, why not solder a wire to the pin on the chip to get a LAN8270 module to work? if you map out the pims on the SKR all but one are available on the board.by sinned - Firmware - experimental, borrowed, and future
sdavi- that sounds GREAT! I can only imagine the work that went into making it work. speaking for myself, I am still trying to figure out what the compelling reasons, features and benefits might be to upgrading to RRF3? i see all the 'whats new' type discussions and how-to and the like, and the mostly deal with what you have to DO to upgrade but I have not seen much on WHY one might want toby sinned - Firmware - experimental, borrowed, and future
After I posted, I realized that I did make another change- I am using LPC port of RRF and I updated the FW to 2.04RC1. I am searching duet forums now too in case of an issue. I did not change the V2 pot after nozzle change, or even consider it. I suppose its worth checking and tweaking. EDIT: its been working fine for months. I suppose if its got a mind of its own, then maybe I am feeling itby sinned - General
Everything was fine and dandy until I had to change a nozzle- now my Z probing is like rugby hit! I don't like it. I can see the deflection in the bed and rods when it makes contact and changes direction. The probing is now a solid 'hit', compared to a gentle 'tap' before. I am not sure what if anything I changed. Here is the section from my config- i usually put the params in comments so I donby sinned - General
sdavi- Are you versioning the updates? I swear up updated the fw to the latest one. It reports as - Firmware Version: 2.04RC1 (2019-07-14b1) Thanks sinneDby sinned - Firmware - experimental, borrowed, and future