Topics created by amimafe

@gloomyandy

Wow, it's certainly very interesting and I think it might be just what I needed. I will study it well and give an answer.

Thank you very much

@amimafe If you save a position, check G0/G1 for the R parameter to move back to that position, you can also use offsets to for example move to a Z pos above the previous pos, and then move down into that position.

@amimafe

Thanks for the feedback.

Frederick

@oliof

Gracias por tu ayuda. Me diste una pista de cual era el fallo y finalmente lo he podido solucionar. Era un error al indicar el número de sensor que quería.
Revisé el archivo config.g y lo configuré correctamente.

Declaración de los sensores en config.g:

;DHT Sensor on Temperature Daughterboard SPI CS1 pin M308 S10 P"0.spi.cs1" Y"dht22" A"Temperatura" ; define DHT22 temperature sensor M308 S11 P"S10.1" Y"dht-humidity" A"Humedad [%]" ; Attach DHT22 humidity sensor to secondary output of temperature sensor

daemon.g:

if !exists(global.logTemps) global logTemps = false while global.logTemps ==true && job.file.fileName != null echo >>{"0:/sys/templog/templog.csv"} {sensors.analog[10].lastReading}^","^{sensors.analog[11].lastReading} G4 S30

@amimafe "Jerk" is supposed to be set to what the mechanics of your system can handle. Setting it too low and you will see deceleration and acceleration when going around a curve made up of sets of straight lines. Setting it too high and you will excessive shaking etc on corners.

What you describe as 160-180 degrees as "continue at constant speed", while more acute angles avoiding abrupt speed changes is what Jerk is used for. A single value does this because it sets the amount of change of velocity at a corner that is acceptable before acceleration needs to be applied.

If you think about the movement around a polygon approximating a circle, decomposed into X and Y elements this becomes clear, X and/or Y needs to change velocity at each corner of the polygon, even though speed remains constant. (velocity being speed & direction). So in order to keep speed constant, those (relatively) small changes in velocity need to happen "instantly" hence setting Jerk above the threshold.

Now if we keep making the polygon simpler and simpler until its a square, at this point there must be deceleration into the corners, and acceleration out of them for any reasonable print speed. Somewhere between the polygon with lots of sides (almost a circle) and a square, there will be a polygon with a corner angle where the mechanical performance of the machine at the set print speed makes "jerk" unacceptable, and acceleration and deceleration will have to occur.

@chrishamm Thanks for your help. I was finally able to compile using an older version of Node.js. Version 18.18
I want to modify some DWC parameters to suit our machine.
I hope this can help other users with the same problem.

@amimafe I'm glad you solved it.

If you don't specify the name of the access point that you want to connect to, then RRF will perform a scan looking for access points in its list. If there is more than one in its list that is available, it will connect to the one with the strongest signal. So it appears that there is another access point in the list that sometimes has a stronger signal than the one you want it to connect to. Use M587 with no parameters to display the list. You can use M588 to delete any unwanted entries.

@amimafe According to the ispyconnect website, the DS-2CD1027G0-L outputs FFMPEG using an RTSP camera video stream. So it cannot be embedded in a webpage, or DWC, without using third-party converters like VLC, or by using an intermediate media server (eg raspberry pi) to convert the stream to something a browser can understand.

From https://docs.duet3d.com/en/User_manual/Reference/DWC_webcam

Important: You must choose a camera that has the facility to return a static JPEG image in response to a HTTP request. Not all IP cameras have this facility. Sadly, none of the major browsers supports including a RTSP camera video stream in a web page.

Ian

@dc42

I thought the same thing at the beginning but I have tried different jerk values (from 0 to 300mm/s) with different accelerations and although it improves the movements with high jerks, it still stutters a little bit.
Is there any way to avoid deceleration at certain angles?
Our printer has a size of 3.5m for the Y axis and 2.5m for the X axis. In case this information is useful.

@amimafe said in Can't show the camera in Print Status screen:

Can I hide the menu that comes by default with DWC at the top?

In the plugins Global Settings

The size of the screen is set by DWC/Browser resolution. You can however add as many tabs/pages as you like .

It might be worthwhile reviewing the Wiki for the plugin.

@amimafe Pin names for LCD connector endstops are here: https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview#Section_Pin_names_for_Duet_2_WiFi_Ethernet

connlcd.encb, connlcd.3 (Endstop 10)
connlcd.enca, connlcd.4 (Endstop 11)
connsd.encsw, connsd.7 (You can also use this pin)

You can't define the enable, step and direction pins; they are not directly addressable. You also can't connect the stepper motor directly to the pins; it's an output for an external stepper driver. See https://duet3d.dozuki.com/Wiki/Using_external_stepper_motor_drivers

Once you have connected an external stepper driver (and the motor to that driver), add M569 P10 with appropriate timings for your stepper driver (see T parameter of M569 here https://duet3d.dozuki.com/Wiki/Gcode#Section_M569_Set_motor_driver_direction_enable_polarity_and_step_pulse_timing ) and add it to the M584 command, eg M584 E10.

Ian