Hello Guest it is April 26, 2024, 01:03:04 PM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - hyildiz

Pages: « 1 2 3 4 5 6 7 8 9 »
71
Hi Craig,

I changed the relay output with signal output and it does the same glitch.

I am controlling the VFD with 0-10V, PWM signal and i think u are right about the start signal and frequency signal but logically u adjust the vfd to turn that signal on when spindle is at commanded frequency not when start running, so i think there is a bug in vfd's logic also.

In m3 code it checks the input62 whether it is HIGH or LOW and if its HIGH it goes on to script, is it possible to put a time constraint to alter the momentary signal? for example is it possible to say if input62 is HIGH for lets say 2 seconds go on, if it is not for lets say 10 seconds feed hold the machine and display a message in window and ask user if he wants to go on or not with spindle off, because sometimes u may run the code without turning on the spindle to check if the code is ok for some reason..

if this is too complicated we can just feed hold the machine.

Regards,

Hakan

72
Hi Craig,

Its not that complicated actually, arduino is C based programming and i can do it (as long as its not too complicated) and as u know it has a wide resources for projects of all kind including communication with Mach4 via Ethernet. I will use arduino mega, ethernet and usb host board connected and its peripherals because i already start the machine with a fingerprint reader and arduino is controlling the power up procedure with relays. So it is already installed and later, through usb host i will add 3dconnexion 3d mouse to control the machine by wireless 3d mouse in all axis.

Arduino will watch the ac line with a voltage sensor so it will know the value of the voltage because in here sometimes it fall below 220V which is bad for electronics. Installed UPS will balance the voltage but if it takes too long to return to normal state arduino will interfere in that case too.

As u know some gcodes takes 9-10 hours to finish, with this setup i will be able to leave the machine on its own at nights so if lights out it will park and wait, when AC line comes back it will go on from the point which it stopped. In case of flickering in AC line or phase lost installed UPS take care of that. Its some kind of helpful automation ;-) installed UPS and batteries have enough power for running the machine about 10minutes with full functionality so it will give more than enough time to arduino for parking and recording the states of DROs, machine coordinates, gcode file, gcode line, etc. Arduino has external separate ups which holds it on for 1-2 days, so it will park the machine and shut down the power and wait for AC line to come back by itself.

Related with the signal glitch problem,

In this Delta VFD there is 2 outputs, 1 is a relay and 1 is an output signal(not relay), i connected the spindle at speed to relay output which is making that glitch so today i will change it with signal output and connect the relay to spindle at zero i think it will solve the problem because signal output does not make that glitch.


Regards,

Hakan

73
Hi Craig,

Das's code is not suitable for my purpose.

I was referring to the m3 code u sent last, when it can not see the input62 it says "spindle does not respond" and then instead of stopping it goes on to gcode/MDI code and all axis moves with spindle turned off. Is there a way to stop it when there is no input62 HIGH signal?

Regards,

Hakan

74
Hi Daz,

Our purpose was to get the "spindle at speed" input HIGH before moving the gantry, so that while using MDI or Gcode machine will not move before vfd does not send the signal.

Which reminds me Craig, in this code if vfd does not send the signal m3 code gives "spindle does not respond" and continues the gcode when spindle is not moving. Can u add a code there if input62 is not HIGH machine should not move.

I am trying to make this logic work because there will be a AC line lost procedure which will be controlled by arduino, machine has internal ups, basically while machine working for hours if AC line lost occur arduino will take control and feed hold the machine first then record the coordinates and gcode line then it will park all axises to a location and shut down the power. Then it will start to listen the AC line, when line comes back it will turn on the machine, goes to the coordinates recorded, input the gcode to Mach4 and goes to the last line and start from there. During this procedure it will check the spindle input but to be sure i need that function also in Mach4 so it wont dive in to part with spindle off which is very dangerous.


Regards,

Hakan

75
Hi Craig,

the last ones u sent works fine, but in my case vfd sends a signal to input62 for a 2-3 milisecond when spindle starts, it just turns it on for some miliseconds and closes it then when spindle reaches the entered frequency it turns it on, i dont know why it does that but when it turns it on for a 2-3 milisecond or so the m3 code sees the input62 gets high and it says "m3 at speed" and continues the gcode while spindle is still accelerating. In m5 it works correctly because input63 does not do that glitch.

I also checked whether if ISIG_SPINDLE_AT_SPEED did not work because of this glitch but no it doesnt work for m5 either.

So the last code works fine, i will contact with delta vfd support to sort it out.

Regards,

Hakan


76
Thanks Craig,

I will check and reply.

Regards,

Hakan

77
Hi Craig,

The last M3 code you sent does not work, the one before works fine but the last one says "m3 at speed" but it does not wait "spindle at speed" input to turn on, it dives in to gcode while spindle still accelerating.

Regards,

Hakan

78
Hi Craig,

I wont be able to test new macros for a week but when i test it i will write u the results.

When we finish this lets open a new topic in mach4 forum with name " Macros for Mach4" and lets put working macros under it so all users can find and use them easily.

Regards,

Hakan

79
Hi Craig,

I tried your last M3 code it works fine spindle waits for the signal and then goes on to gcode, but i found out something which u can say "bug" for the code ;)

When i write a code in MDI i write it as "M3 S6000" in a same line but i tried one of the gcodes roadrunner.tap to test it and in that gcode M3 and S60 commands are in different lines its like this;

F60.000000
G0 X0.000000 Y0.000000 Z0.200000
M3 (start Spindle)
S60.000000
G43H5
G0 X0.000000 Y0.000000 Z5.00000
G0 X1.179950 Y4.004260 Z0.200000

(I changed S60 to S6000 in the test)

When u press cycle start with this code M3 macro came up with "spindle does not respond" message.

So because S6000 was not at the same line with M3, it didnt start the spindle and because of that Spindle At Speed signal did not turn on and M3 macro could not see the signal so it gave "spindle does not respond" message.

I dont know why in roadrunner code it is in different lines but in general M3 and S command should be in same line in gcodes so it wont be a problem i think.

I will change the M4 M5 macros  and button scripts, spindle cw and spindle ccw on screen according to this M3 macro so they all should work correctly.

Thanks for your help, i couldnt came up with that code for a month.

Regards,

Hakan

80
Hi Craig,

Ok, thanks for helping me out.

Regards,

Hakan

Pages: « 1 2 3 4 5 6 7 8 9 »