Software package 3.3beta3 released
-
@droftarts Well sadly I'm not a walking encyclopedia of gcode... But I'll file that one away if it happens again...
-
After upgrading (SBC) it looks like neither variables nor RGBW Neopixels work which sucks because I've been dying for both!
@nurgelrot said in Software package 3.3beta3 released:
So everything but the board is upgraded what did I miss?
the right package is installed on the PI:
ii reprapfirmware 3.3-b3-1 all RepRapFirmware Software Bundle
Rebooting nothing working.I'm in the same boat where the firmware doesn't upgrade. I'm considering just reflashing the SD card but that would be a pain.
-
@nmsmith89 see my post 2 above to update board.
Ian
-
@stephen6309 said in Software package 3.3beta3 released:
@paulhew If you are using PrusaSlicer you need to add to the Before layer change G-Code: ;LAYER:[layer_num]
It's under Custom G-Code in Printer Settings.Hi, I have the same problem using S3D 4.1.2
-
@nurgelrot said in Software package 3.3beta3 released:
@droftarts Well sadly I'm not a walking encyclopedia of gcode... But I'll file that one away if it happens again...
I've updated the link I sent earlier to include the basic update procedures (uploading via DWC or sending the M997)
-
@pkos I have an 3 meter USB3 extension cable killed
, and now it's working as expected (with 3 Meters)
And I found a small bug in DWC if i have more than one CSV file and click on an entry another entry (not clicked) will be highlighted. -
@siam Interesting, can you post some more detail? I'm about to mess up an ethernet extension cable, but USB might be better for me since the connector is smaller...
-
@diamondback i use this cable https://www.amazon.de/gp/product/B08BJSK567/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1 I cut of the plugs and I crimped it to dupont connectors thats all
-
@siam Any specific pins for specific functions? Or just randomly took what was there?
-
@diamondback
(picture was stolen at wikipedia 
Red = 3.3V
Black = GND
Blue = SDA => MOSI
Yellow = SDO => MISO
Green = CS =>CS3
Orange = INT => CS4
Violet = SCL => SCK
White = NC -
I see that Duet 2 can now do neopixel LEDs, which is super cool, but how do I wire them up and configure? Which pins should I use?
-
@thebaseddoge said in Software package 3.3beta3 released:
I see that Duet 2 can now do neopixel LEDs, which is super cool, but how do I wire them up and configure? Which pins should I use?
-
@phaedrux I saw that but it seems to only be for Duet 3 right? Duet 2 has no NP_LED pins
-
@thebaseddoge Correct. Duet2 lacks the hardware.
Duet 3 MB6HC supports both DotStar and NeoPixel LED strips. Duet 3 Mini supports NeoPixel only. Duet 2 and Duet Maestro do not support these LED strips directly, but you can use an Arduino to interface them to a Duet.
-
@phaedrux Right, but this line in the 3.3beta3 changelog implies that Duet 2 can now do it. That is where my confusion comes from.
Bit-banged NeoPixel LED strips are supported on Duet WiFi/Ethernet. On these boards RRF will wait stop movement while updating the LED strip, so M150 commands should not be issued while the machine is printing, other than at places where a short pause is acceptable such as at layer change and in the start and end scripts. -
@thebaseddoge I think a pin has been enabled for controlling the Neopixels on 12864 displays. But I don’t know if it works outside this use case. Will need some @dc42 guidance.
Ian
-
@droftarts I didn't think the Duet 2 Wifi supported the 12864 either, only the Maestro? Hopefully dc42 can clarify everything.
thanks. -
@dc42 I upgraded and noticed user variables in SBC mode are not showing up. I know integration was pulled in b2 and a fix was in the works for 3.3b3... Is this is a bug or have plans changed for user variable integration in SBC mode?
-
Global variables appear in the Object Model Explorer in 3.3beta3 but changes to their values are not picked up. That is fixed in the forthcoming 3.3RC1.
-
@thebaseddoge said in Software package 3.3beta3 released:
@phaedrux Right, but this line in the 3.3beta3 changelog implies that Duet 2 can now do it. That is where my confusion comes from.
Bit-banged NeoPixel LED strips are supported on Duet WiFi/Ethernet. On these boards RRF will wait stop movement while updating the LED strip, so M150 commands should not be issued while the machine is printing, other than at places where a short pause is acceptable such as at layer change and in the start and end scripts. @droftarts said in Software package 3.3beta3 released:
@thebaseddoge I think a pin has been enabled for controlling the Neopixels on 12864 displays. But I don’t know if it works outside this use case. Will need some @dc42 guidance.
Ian
@dc42 do you have any more info on this? thank you!