windows detect a virus in it
Posts made by danzaywer
-
RE: Software bundle 3.5.0rc.4 now available
-
RE: 3.5.0-rc.1 LED Issuse
@droftarts I have the same behavior, I have RGBW LEDs, set with M950 E1 C"duex.pwm5" T2
-
RE: 3.5.0-rc.1 LED Issuse
@gloomyandy It worked on 3.4.6, could not try downgrade at the moment, too many changes to do
-
RE: 3.5.0-rc.1 LED Issuse
@droftarts Yes, it worked fine. BTW no a great issue, if set blue I have cyan....
-
RE: 3.5.0-rc.1 LED Issuse
@droftarts On duex.pwm5 I should have 5v from external source, I have atx 5v rail connected on "EXT 5v" and "5v AUX" jumper is on "5v ext", while the strip on CONN_LCD have signal on a 74HCT08.
-
RE: 3.5.0-rc.1 LED Issuse
@gloomyandy Nope
I try from 3200000 to 2000000, also 1600000 and 8000, 800 500 just to try, green is always on everytime i send an M150. Maybe an hardware foult of my duet? onM950 E1 C"duex.pwm5" T2
is same same .
-
RE: 3.5.0-rc.1 LED Issuse
@danzaywer default frequency should be 3000000Hz ?
-
RE: 3.5.0-rc.1 LED Issuse
M950 E0 NeoPixel_RGBW strip on port "(connlcd.np,connlcd.db7,connlcd.5)" uses bit-banging, frequency 2500000Hz, max strip length 3
-
RE: 3.5.0-rc.1 LED Issuse
I have a strange behavior on the leds with the 3.5rc1 too, on duet2 wifi . Basically, the first set is successful if done at the same time as the print starts (I have the M80 command in the start.g and M150 R255 S3) after which with any other M150 the green on the first LED remains lit as a residue. For example, with
M150 E0 R0 U0 B0 S3
the first remains green, with
M150 E0 R255 U0 B0 S3
the first is orange (red + green) the other two red, with
M150 E0 R0 U0 B0 W250 S3
the first green, the other 2 white. I have 3 neopixel rgbw leds for the stealthburner, port CONN_LCD and a 74HCT08, older firmware all worked. I also wired 3 other LEDs to another connector with 5V logic of the Duex5, without 74HCT08, and configured E1 strip but the behavior is the same. If power on outside print and send an M150 the issue is present at first shot.
-
RE: WIFI SPI timeout error
@martinv I'm on 2.1beta4, after turned FTP off the problem not occurred yet but I restart printer for other reasons. I have the impression that the problem arises after a long period of activity .
-
RE: WIFI SPI timeout error
@martinv So you say to use
M552 S-1
instead of
M552 S0
in my trigger? Luckily since I disabled FTP I have done 4 long prints and still there is no problem
-
RE: WIFI SPI timeout error
@OwenD I just disabled FTP. Telnet already off... Let's see if anything changes
-
RE: WIFI SPI timeout error
@Phaedrux I had issue first time flashing beta so I used M997 S1 P"I-not-remenber-what-bin-working"
-
RE: WIFI SPI timeout error
@Phaedrux I haven't tried, what file should I upload for the beta4? DuetWiFiModule_32S3.bin
783 KB?
The problem is sporadic, it happened to me 3 times and after at least 2 hours of printing on a 5 hour print. Now it is completing a 5 hour print and the problem did not occur, but it is the first print after the restart, it has always happened on prints made with the printer that had already worked other prints. -
WIFI SPI timeout error
Hi, I have this error message flashing on screen and duet disconnect. this happen during print and the print finish but I have to switch off printer to reconnect, I can do nothing becouse error flash continually. now I set an external trigger withM552 S0 G4 S1 M552 S1
to see if i can restore functionality but what can be the cause? wifi module broken?
Duet 2 WiFi 2WiFi 3.5.0-rc.1
Duet WiFi Server n/a 2.1beta4
Duet Web Control DWC 3.5.0-rc.1 -
3.5.0-beta.4 neopixel on duet 2 wifi
Hi,
I updated to 3.5.0b4 but now I do not know how to configure the LEDs neopixel for stealthburner. the LEDs are connected on pin 5 CONNLCD using a 74HCT08 for level shift and up to 3.5.0b3 worked with M150 X4 Q3000000 in config.g, now I do not know what pin should be put in the C parameter of M950. Can anyone help me? -
RE: CoreXZ - X and Z accelerations are linked
@dc42
Ok, I can try, even if I've never put my hand to the Reprap firmware I think I can do it. But I try to make another request: is it possible to insert the retraction in the special movements managed by M201.1? also would it be possible to include in the special movements also the return to position between the two probes if, for example, 2 passes are used with the Bltouch?