Software package 3.3beta3 released

Print3d

@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?

dc42

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

@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!

dc42

@thebaseddoge these are the pins to use when connecting a 12864 LCD to a Duet WiFi/Ethernet:

constexpr Pin EncoderPinB = PortCPin(7);		// connlcd.3	-> exp2.6
constexpr Pin EncoderPinA = PortAPin(8);		// connlcd.4	-> exp2.8
constexpr Pin LcdNeopixelOutPin = PortDPin(18);	        // connlcd.5	-> exp1.5
constexpr Pin LcdResetPin = PortCPin(28);		// connlcd.6	-> exp1.6
constexpr Pin LcdA0Pin = PortDPin(19);			// connlcd.7	-> exp1.7
constexpr Pin LcdCSPin = PortAPin(25);			// connlcd.8	-> exp1.8
constexpr Pin EncoderPinSw = PortDPin(20);		// connlcd.9	-> exp1.9
constexpr Pin LcdBeepPin = PortDPin(21);		// connlcd.10	-> exp1.10

// Additional spi wiring for FYSETC Mini 12864 display:
// connlcd.2 (gnd)	-> exp1.2
// connsd.1 (+5V)	-> exp1.1
// connsd.2 (gnd)	-> exp2.2
// connsd.3 (SD CS)	-> exp2.7
// connsd.4 (sck)	-> exp2.9
// connsd.5 (mosi)	-> exp2.5
// connsd.6 (miso)	-> exp2.10

Warning! Some displays have the EXP1 and EXP2 connectors the other way round. So don't rely on the exp1 and exp2 pin numbers in the above.

droftarts

@dc42 I think the question was what pin to use to control Neopixels independently. Is connlcd.5 always available for Neopixels, or only when a 12864 is connected and defined in config.g?

Ian

dc42

The support in RRF is intended for driving the LEDs on 7567 displays, however I think it should work without a display being configured provided that you don't try to use drivers 10 and 11. You will need to level shift the signal from 3.3v to 5V.

nmsmith89

@dc42
The RGBW Neopixels don't seem to work in 3.3b3 even though it's in the release notes. Is it not implemented yet or am I doing something wrong?

dc42

@nmsmith89, it is implemented. There are new M150 X parameter values for RGBW. I have just updated the documentation at https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M150_Set_LED_colours.

TheBasedDoge

@dc42 I do have a PanelDue 5" display, but i dont have anything on stepper 10/11. so do I just need to use pin 5? what fw config changes are required?

nmsmith89

@dc42 Thank You!!!

Diamondback

@siam Finally managed to get the accelerometer connected... I'm currently using about 3m of USB 3 extension cable and that seems to work ok, was just a lot of pain to wire up...
It looks like shielding is way more effective here than just twisted wire pairs (which I tried before and didn't work on its own)

dc42

@diamondback said in Software package 3.3beta3 released:

@siam Finally managed to get the accelerometer connected... I'm currently using about 3m of USB 3 extension cable and that seems to work ok, was just a lot of pain to wire up...
It looks like shielding is way more effective here than just twisted wire pairs (which I tried before and didn't work on its own)

The SPI frequency is currently 4MHz. I'll try reducing it, that may make it easier to use long cables.

Diamondback

@dc42 said in Software package 3.3beta3 released:

@diamondback said in Software package 3.3beta3 released:

@siam Finally managed to get the accelerometer connected... I'm currently using about 3m of USB 3 extension cable and that seems to work ok, was just a lot of pain to wire up...
It looks like shielding is way more effective here than just twisted wire pairs (which I tried before and didn't work on its own)

The SPI frequency is currently 4MHz. I'll try reducing it, that may make it easier to use long cables.

Thanks for looking into this. Is there any advantage to the higher frequency in practical use? If so, maybe offer te higher speeds as an option still?

dc42

3.3RC1 will default to 2MHz and allow the frequency to be changed using a new Q parameter on the M955 command.

snagit007

Thanks all for your great work!
I have updated my BLV Cube with Duet3 and SBC to 3.3beta3 and everything works flawlessly. It is just incredible that the software can support individual configured systems providing first class prints.

MintyTrebor

I have had a couple of instances of SBC users experiencing issues with the duetpluginservice not running by default, which is preventing 3rd party plugins being installed/run.

Running

sudo systemctl enable duetpluginservice

and rebooting the sbc seems to clear the issue.

Not sure if its the right thing to do or not.

Adding it here by way of feedback.

A Former User

@phaedrux said in Software package 3.3beta3 released:

@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?

https://duet3d.dozuki.com/Wiki/Neopixel_and_DotStar_LEDs

Does it support only original Adafruit NeoPixel stripes or other brands of RGBW stripes?

cosmowave

@thedragonlord In the dozuki is written:
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.

A Former User

@cosmowave said in Software package 3.3beta3 released:

@thedragonlord In the dozuki is written:
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.

sure but some rows below:

Connecting NeoPixel strips to Duet 2 Wifi or Ethernet
A signal for controlling Neopixel strips can be output on pin 5 of the CONN_LCD connector provided that you do not have external stepper drivers connected to CONN_LCD. The signal level is 3.3V so you need to level shift it to 5V. A non-inverting 74HCT series gate or buffer such as 74HCT08 can be used to do this.

RGB NeoPixels draw up to 60mA per LED. RGBW ones draw up to 80mA per LED. Therefore the Duet cannot provide enough power for an LED strip unless the number of LEDs in the strip is small (for example 16 RGB or 12 RGBW LEDs). For longer strips you must provide external 5V power to the strip.

dc42

@thedragonlord said in Software package 3.3beta3 released:

Does it support only original Adafruit NeoPixel stripes or other brands of RGBW stripes?

Any brand using the WS2812B or compatible chips should work.