I'm working dual toolhead setup. T0 regular FDM extruder and T1 a syringe-based paste extruder. With any change, let's say a new needle, the needle will be off every time.

Is there a way to measure and set the needle-offset by passing it through a series of different opto-endstops, let say X' Y' and Z'?

This is with the intention of using a macro after homing T0 to set the T1 offset automatically.

Hello DSF experts,

I want to modify the value of a global variable using CommandConnection as follows:

pConn = CommandConnection()
pConn.connect()
pConn.lock_object_model()
pConn.set_object_model("global.a_MachPos", "123")
pConn.unlock_object_model()

However, the code doesn't change the value of the global variable a_MachPos. The code was based on the comments in base_command_connectioon.py file

In the future, I want to be able to change the values of variables used inside jobs.

Thanks for you help.

@dc42 I'll keep an eye on it and try my best not to definitely fry my board this time

Really happy with how you design this board. It has been a blast playing with them.

Kudos to you and the Duet team!

Hi Devs,

I used to program in C and a bit more in C++ some 20 years ago. Some of the basics are there but my experience ended in object-oriented coding. I'm asking for your recommendations on literature/courses/tutorials on how to restart my coding skills in order to make some firmware modifications for the Duet 3 family. Any advice will be appreciated.

I'll take a look.

Thanks for the fast answers.

I've been working with Marlin and Smoothieware, but the Duet it's a superior solution to anything I have seen. Congrats and keep up with the excellent work.

Hi Devs,

I used to program in C and a bit more in C++ some 20 years ago. Some of the basics are there but my experience ended in object-oriented coding. I'm asking for your recommendations on literature/courses/tutorials on how to restart my coding skills in order to make some firmware modifications for the Duet 3 family. Any advice will be appreciated.

@dc42 After looking at my code, I was querying the wrong probe. The sensors.probe[1].value works, the problem was between the keyboard and the chair.

However, using the Object model plugin, no probe value gets updated at sensors.probes[#].value[0]. Even when meta-commands and the status board shows the right value.

Add: The JSON file gets updated but requires refreshing the website for the values to be updated into the Object model plugin.

Thanks for your answer @chrishamm. I tried the Object model plugin and sensors.probes[1].value[0] is always 0. Even when the status section displays 1000 for probe 1, this happens for any probe. I have firmware 3.4.5 installed. Everything else works but this. How can I query the Z-probe value via gcode?

Dear Duet Team:

I'm trying to read a Z-probe for tool probing. When the probe is triggered, this gets reflected in the Z-probe section of the Status. When using G38.2 and G38.4 I have no problem working with such a probe. However, when I try to query the probe value via Object Model "sensors.probes[1].value[0]" is always zero even when the Status says otherwise. I get the actual probe value by using M409 K"sensors.probes[1].value[0].value". Unexpectedly, using "sensors.probes[1].value[0].value" with metacommands I received an error.

@chrishamm @Phaedrux
Duet Web Control 3.4.1
DSF Version: 3.4.1
RepRapFirmware for Duet 3 MB6HC 3.4.5
On config.g - M586 C"*"

Making further tests, our emergency button sends M112 M999. If I send only the M112 command, the websocket keeps working. Sending M999 creates the error. If I press the emergency button on DWC or the physical button connected to the reset pins, the websocket cannot connect back until the duet web server is reset or power cycle the machine.

@dc42 the config.g has it, and I created a dsf-config.g and added to it. Also, was manually executed via DWC after reset. Same results

Hi,

I'm working on a web controller for Duet. The web control software is hosted on the internet, and accessed via a PC. The PC is connected to the printer with Duet 3 6HC with the SBC set as an access point.

When the printer and software start, it works like a charm. Connects, GET, and POST requests can be made. However, if reset is hit (on the DWC, M112 code or physically pushing the reset button), I receive the following error when trying to reconnect:

Access to XMLHttpRequest at 'http://192.168.1.10/machine/connect?password=reprap' from origin 'http://localhost:3000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

It seems that no matter what we do on the server side, nothing works only after either, the printer has been turn off and on again, or the webserver has been restarted (sudo systemctl restart duetwebserver via SSH).

This our httpRequest function, using AxiosRequest

export async function httpRequest(config: IRequestConfig) {
    const fullUrl = `http://${PRINT_WEBSERVER}${config.url}`;
    console.log(`Request to ${fullUrl}`);
    const request: AxiosRequestConfig = {
        ...config,
        url: fullUrl,
    };
    try {
        const response = await axios(request);
         }
        console.log(`Success! - Request to ${fullUrl} returned`, response.data);
        return response;
    } catch (e: any) {
        console.log(`Failed! - Request to ${fullUrl} returned ${e.status} - ${e.message}`);
        throw e;
    }
}

How to connect to the printer again, after a reset or how can we reset the webserver via JS?

Re: How to check the real current of the stepper motor

Hi Duet experts,

I'm looking for a method to record the current of the extruder stepper during printing.

Trinamic drivers monitor that current, is there a way to get that measurement via gcode, object model, or dsf-python?

Thank you

@Falcounet said in Modify a global variable value:

@DDD Actually, you can use pConn.perform_simple_code("set global.var_name=value")

Is there a way to modify the variable value without using a gcode command?

I'm assuming that this command gets into the buffer to be executed. I'm looking for the fastest way to make this change.

@Falcounet thanks for the help, will test it on Monday