I will put one in to night a see if it changes anything
Thanks, I'll add the PWM input, though its opitional, its only used in the CNC mode.. not NGrave which
is the normal mode for CNC usage. It is handy though to see if the PWM input makes the box
switch to CNCMode from diags.
I took mine apart last night and it had a loose 5vdc wire, so it seems to be running well again..
Let me know when your operational and well run some tests to see whats up. In Engrave mode you should
be able to see Darwin send power commands to the box with just a simp[le test or two..
G540 controlling motors, limit switches and estop
MB-06 V2 bob for controlling laser outputs and a kill switches for MB-06
pins used on MB-06 are
step flag pin 14 to pin 3 arduino
serial data pin 16 to pin 11 arduino
serial clock pin 17 to pin pin 2 arduino
pwm output pin 1 to pin 7 arduino
kill switch (NC) for MB-06 pin 10
MB-06 set to active high
EDIT Circuit diagram updated to include series resistors for LED's
Well I have built it but I can't get it to work - no laser output pulses (except for the tickle pulse ?) :'(
It's got to be something really silly that I am doing wrong but so far it is eluding me. ;D
Wow, thats looking good. Ok, lets debug it one step at a time and see where
Ive screwed you up..
Lets get diosga running, its the easiest test just so we know all else is running..
Test 1 for any panel: Does it fire in Diags mode?
1) Set to Diags, set count to 1000, ( 1/5th second).
2) Run button LED should now flash ( if box has one.. :)
3) Pressing fire should count down , PWM should go to power set by the pot.. 100% for test
4) did laser fire during count?
Ok course, being Tweakie you may already know the pwm firing section works, I ask the above
only so future new users will see an initial test responce..
Second test, NGrave mode. For this Darwin and Mach4 must be setup correctly.
This you will know if the following is true.
StepFlag pulses everytime any motor does a step. Doesnt matter what motor..
Serial Flag also pulses every time motion occurs. This doesnt match step by step,
when a waypoint is sent to Darwin, the serial clock will pulse 16 times each time
changing the state of the Serial data on each pulse...
Test: Set Darwin to Laser mode in the diags menu of mach4 under darwin. This turns on
the Laser outputs. Ensure Serial clk, serial data and Step flag are enabled and on proper pins.
Setup a PWM spindle in Mach3 and darwin, set it to frequency controlled in Darwins config at 25hz
what you set the frequency to doesnt actually matter in Darwins config, the diags setup in Mach4 will also
ask a frequency and Darwin will fill in the rigth hardware frequency then.
So in MAch4's diags menu setup for Darwin turn on PWM Spindle. Set it to 50hz. In Mach4, set the spindle range
to 0 min and 100max. Set Motor max rev at bottom of tab to 100. (all this is for power scaling).
Execute a S100F1000 in the MDI, then press the SpindleOn button on the screen or execture an M3.
The lcd in the panel should now show 100 in the REM: in the upper rigth corner indicating its getting
a spindle power of 100 currently. It wont shoot till it moves, but the power should show up as 100%
Lets trouble shoot from there.. :)
Just so we're sure we're all on the same page, here's the code I will be running my machine on when testing why
you ( or dan ) may be having troubles. I'll compare to this codes standard .. it has a change you probably dont have, in the FireLaser routine there is a change in the CNCModes power level to the new standard I use. ( Which is the user of Mach sets a power word ( S0 - S100 ) as a percentage demand to the laser panel, which then gives 0-100% of the
dialed up power on the pot. this is true in all modes. It allows one to adjust power at the laser to see effect and judge
actual required power you might need. SO the pot is the master power selection, and the PWM ( cncMode) or DarwinLaserCalc ( NGrave Mode) are slaves demanding simply 0 - 100% depending on circumstances..
Here is the current Darwin I use as well as the current laser box code..
[The extension txt has been deactivated and can no longer be displayed.]
- (2.73 MiB) Downloaded 382 times
Doesnt work that way.. Pin 9 is a PWM signal, so if its set to 50% you should read 2.5volts or so.. if set to 90% you should see abotu 5 volts. Changing the pot would do nothing to the voltage. 100meg or 100K..doesnt matter, it just tells the arduino what timing for the PWM to use. So while a scope is what should be used to look at pin9, you can use voltage , just consider it a voltage of 0 - 5 volts in 100 increments of the power pot ( in the case of diags mode when firing..).
In Diags mode, at 100% and CW selected as count, ( constant wave), you should get between 4-5vc measured on pin9.. a pwm of 200us in period, and with no fire command you should see about 1us pulses, that go to about 190us pulses at full power..
Generally though, if you see the voltage go up quite a bit when you press fire, then its probably working fine..
Users browsing this forum: No registered users and 1 guest