@dc42

I'm going ahead with it.

Jumpers removed.
CS is set to CS_1.
Tank Capacitor value changed, and resistors added as per your suggestion.

Just waiting on an assembly price from Chinese supplier.

I'd like to send you a few boards to test with the firmware. ( Take this offline and get address etc via pm ?? )

Thanks
Keith

@dc42 Thanks David.

The ground is definitely commoned.

I'll add the resistors as per your suggestion.

Would the firmware changes be added just for this project ? Or, does it need to be added to the features 'wishlist' for Duet 2 firmware ?

How would this be operated in terms of G code ? with M150 command ?

Also, assume that if a thermocouple board is used, only 2 of the CS would be available anyway ?

Thanks,

Keith

@dc42

See replies below ...miss-tagged them ... there is a pdf with potential circuit diagram of addon board

@dc42

Will this work ?

Did you see my previous questions ?

Duet-LED-Driver.pdf

That's what I was alluding to. I can design a cheap pcb with the 74HCT02 and some connectors ( with a set of jumper to select an appropriate CS ).

Would the firmware changes be added just for this project ? Or, does it need to be added to the features 'wishlist' for Duet 2 firmware ?

I'll post a circuit diagram in the coming days for the potential design.

@bearer Missed that bit ..... DOH!!

Another thought .... your WiFI network ... Does it allocate DHCP addresses ? or expect static IP addresses ?

If DHCP... then use the M550 machine name command, and let it auto allocate the IP address ( don't try to specify one ).

You can then ping it in command prompt with : ping machine name.

Once you get YAT connected you can run the M588 S"*" first.

Then follow the getting connected guide.

I would follow @bearer advice ..... Use YAT as per the guide ..... Also, before following that guide run M588 S"*" to delete any saved networks ....... it will save confusion later on.

I would set a machine name using M550.

If network IS connecting but not assigning an IP address that you think it is, you can still find the machine by pinging it from Windows command prompt using "ping machine name" .... It will print the IP address and response time if it is on the network. If not then you have at least a clue that its not seen.