[3.5.0-beta.3] Duet 3 Mainboard 6HC + wifi module

Aitor

Good morning @dc42,

I am testing the new version 3.5.0-beta.3 and the wifi module. In the object models, I can see module 0 (Ethernet) and module 1 (external wifi module), but the MAC address does not appear for the latter. I have also noticed that the same issue occurs with the M540 command. Additionally, it seems that M540 I0 indicates the MAC address of module 0 and M540 I1 indicates the MAC address of module 1, although in this case it appears as 00.00.00... which doesn't seem correct. Shouldn't they have different MAC addresses? I have also noticed that the M540 In function is not included in the documentation, but it seems to work.

On the other hand, I have tested M587.1 and M587.2 and they seem to work perfectly. I wonder if there is an object model where these data read by M587.1 can be recorded (ideally in array format) to be used with the new functions of M291 and create a macro for scanning and selecting SSIDs.

If anything is unclear, please do not hesitate to ask.

Regards,
Aitor

dc42

@Aitor thanks for your report. I will test reporting of the MAC address of the WiFi module when I return from RMRRF. Meanwhile you can get the WiFi MAC address from M122.

The M587.2 command has a F1 option to return the data in JSON format. This will be used by future PanelDue and DWC versions to implement a wizard for selecting and configuring access points to connect to.

Aitor

Good morning @DC42,

Currently, I am using stepper motors with brakes that have been configured as follows:

M569.7 P0.2 S100 C"out3"

However, I have noticed that the brake does not activate when executing the M84 command. This is different from what happened in version 3.4.0 of the firmware. Additionally, I have also observed that the brake does not activate immediately when using the emergency stop on the DWC control panel. It is possible that both situations are related.

If you need more information or if my explanation is unclear, please do not hesitate to ask.

Regards,
Aitor

droftarts

@Aitor please start a new thread for new issues; your last post does not relate to the thread title.

Ian

Aitor

Good morning @droftarts,

I apologize for any mistakes I made in mentioning the electronics I was using during the tests. I thought it was important to include that information in the thread title, as I didn't intend to describe the problem. However, I have created a new thread with a more general title as I have more information to add and I find it difficult to express myself in English. Additionally, I sometimes struggle to select the correct categories.

Thank you for your understanding.

Best regards,
Aitor