Posts made by Glen_Remix

@Glen_Remix the 1HLC looks like it might have an under-voltage error which might be causing this?

Is there anything else that jumps out in the log as maybe a clue?

So I got the error just now. Attached are the M122 outputs of both the 6XD mainboard and one of the 1HCL toolboards.

Thanks for your help,
Glen

M122 B6XD.txt
M122 1HCL.txt

@dc42 said in Duet 3 getting stuck during macros:

@Glen_Remix try sending M122 when it gets stuck and post the result here.

When using more than one trigger as youvare doing, you should allow for the fact that only one trigger can execute at a time, except for trigger 0 (emergency stop) which can interrupt the macro for another trigger.

We're running a load of tests today, I will upload the M122 result when it comes up.

The PLC side of the code is meant to wait until the "done" bit is received until it sends any more triggers, but I can double-check with our control engineer if that's definitely true.

Is there any M400 equivalent for macros? I've added M99 to the end of each macro so that it's definitely ended before it starts a new one, but that doesn't seem to have helped.

@chrishamm
RepRapFirmware for Duet 3 MB6XD version 3.4.2rc1 (2022-07-06 16:23:35) running on Duet 3 MB6XD v1.0 or later (standalone mode)

Some further info:

This time the delta seems to have frozen at its top, hard against its endstops, as if its homing but hasn't triggered the switches.

It also makes this jittering noise that you can hear in the video below.

https://photos.app.goo.gl/cEgmyTqrEsWX6Vpn6

The motors are attached to 1HCL boards, but are in open-loop mode.

The board status is idle.

To rectify this, I have to send M999 then home all.

trigger7.g trigger6.g trigger5.g trigger4.g trigger3.g config.g Hi all,

I'm using a Duet 3 6XD to motion control a delta robot as part of a larger system. The duet receives input triggers from a PLC to run macros. The macros are a couple of lines of movements, along with a "busy bit" which is high for the duration of the macro, and a "done bit" which is on for half a second at the end of the macro to signal to the PLC that the move is complete.

I'm having an issue in that the duets seem to randomly get stuck during this routine. They stop responding to inputs, and when I connect via DWC, I am unable to interact with the duet without sending M999 to reset the board. I then need to home the robot, and send M582 to check the trigger status.

I have attached my config and macro files.

Any ideas as to what I can look into to resolve this problem would be greatly appreciated.

Thanks,
Glen
config.g
trigger7.g trigger6.g trigger5.g trigger4.g trigger3.g

@jay_s_uk said in Checking Trigger Status:

@Glen_Remix post an output of M98 P"config.g"
and I see the .iso thing is specific to the 6XD. thats my new thing learnt today

M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled

@jay_s_uk I believe this is to specify the use of the opto-isolated IO pins, rather than the general IO pins.

I very well could be wrong though.

@OwenD thanks for your reply.

I don't seem to have 'object model' as an option in the sidebar.

How would I enable this option?

Good morning,

Apologies if this has been explained elsewhere but I haven't been able to find a solution.

I'm using IO inputs to trigger macros.

I'm running into some issues and it would be really helpful to be able to check the status of the IO inputs to understand why the machine is doing (or not doing!) what I expect.

I have the IO setup as follows on my 6XD:

M950 J2 C"!io5.in.iso" ;Delta Move 1
M581 P2 T5 S1 R0
M950 J3 C"!io6.in.iso" ;Delta Move 2
M581 P3 T3 S1 R0
M950 J4 C"!io7.in.iso" ;Delta Move 3
M581 P4 T6 S1 R0
M950 J5 C"!io8.in.iso" ;Delta Move 4
M581 P5 T4 S1 R0
M950 J6 C"!io0.in" ;Delta Move 5
M581 P6 T8 S1 R0

I have tried M582 Tx to check the trigger status, but this command just seems to trigger the Macro, rather than checking the input for the trigger.

M409 also comes back Null.

Any help with this would be greatly appreciated.

Thanks!

@jay_s_uk Thanks for your speedy reply!

Looks like I'll have to do some rearranging to reach that port.

Thanks!

Good morning,

I have a MB6XD and three 1HCL boards connected via CAN network.

I am running Firmware version 3.4.5 on the MB.

Due to space constraints, I was intending on using the 2-pin CAN_0_OUT connection rather than the RJ11 CAN_1_OUT on the 6XD board, however, this doesn't seem to work when connecting this way.

I have found an older post that this port's functionality was to be included in RRF 3.4, but I can't find any further information if this port functions the same way as the CAN_1_OUT.

Any help in pointing me in the right direction would be greatly appreciated.

Thanks!

Glen

@dc42 Thanks for your quick response.

I understand, thanks for clarifying. I think I will use interface relays.

Cheers.

Hi all,

I'm working on a project using a Duet3 6XD for motion control for a larger system controlled by a PLC.

The PLC has 5 24V PNP outputs which trigger macros on the Duet, and 2 inputs from the Duet to indicate 'Busy' and 'Finished' states.

I have used up all four opto-isolated IO, and need to use three other pins.

The datasheet states that the Input pins are +30V tolerant. Does this mean that I can connect the IO GND pin to the PLC 0V and the ioX.in pin to the PLC Output? Does this require anything else to avoid damaging the Duet?

The PLC output is up to 0.5A per channel.

Any advice would be greatly appreciated.

Thanks,
Glen

@phaedrux Purchased on 17/08/2022 directly from Duet3D as an OEM.

Getting 0.5V on SPI pin 8, same as the regulator output.

Thanks,
Glen

@markz Thanks for your reply.

So interestingly there is 3.3V to the IO (measured at IO_0).

However, there doesn't seem to be an internal 3.3V. At the 5v-3.3V regulator U4, which I mentioned was heating up, I measured 4.6V at the input, but only 0.5V at the output. This regulator is listed as "Output for internal use only" in the schematic.

I don't know if there is a way of testing this, or if a warranty return is the best option?

Thanks,
Glen

Good morning,

Tl;dr: New 6XD board 5v-3.3v regulator doesn't seem to be working.

I am working on a project where I am integrating a Duet-powered machine with industrial automation hardware.

I was using a Mini 5+ for initial testing but opted to change to the 6XD due to the optoisolated I/O making PNP hardware easier to work with.

After removing the Mini 5+ and changing all of the wiring to suit the new board, I unwrapped the 6XD and plugged in the USB to set up networking.

Unfortunately, I wasn't able to connect to the board via USB and the board wasn't coming up in Device Manager.

I noticed that although the USB and 5V LEDs were lit, the 3.3V wasn't. I also noticed that the 5V-3.3V regulator U4 gets very hot as soon as the board is plugged in.

I have nothing else plugged into the board, and have tried powering on both with and without the SD card.

Is there anything else I could try, or is this a hardware failure?

Grateful for any help.
Thanks,
Glen