You can change any parameter on screen. But you can have a setup file at the same time, that can just be loaded. So both things work perfectly and cover different scenarios.
Printable View
You can change any parameter on screen. But you can have a setup file at the same time, that can just be loaded. So both things work perfectly and cover different scenarios.
So how is parameter #115 dealt with (I am beginning to think the manual is telling lies) ?Quote:
Originally Posted by Boyan Silyavski
Whats this #115? i cant see it in manual and my machine is busy for a couple of hours so i can not stop it now to look for it.Quote:
Originally Posted by cropwell
But as i said, you either input it manually or upload a text file. Thats it
I dont see any reason messing with uploading, except if you are a machine producer and upload the same file to a bunch of machines
Hey Alex.Quote:
Originally Posted by AlexDoran
Just wanted to thank you for this post, as I was struggling to get my Huanyang VFD to run at the speed I am setting from Aspire.
I managed to get it turning on and off at the start and finish of a job all ok, but the speed setting didn't work and it just ran to max.
Connecting the DCM and ACM together via a simple wire fixed it, so thank you.
Ian
Not strange logic really (for once!) It makes sense if you think that some controllers have separate power supplies for analogue and digital outputs. For example, this allows you to use the DC output from the VFD to supply the analogue output circuitry in the controller. A lot of cheaper BOBs only have a 5V supply for the digital side of things and need an external supply of 12V or so for the analogue output. And after all, it just needs an extra wire to make it all work with a common ground! The info is on the circuit diagram, although it doesn't leap out at you and I don't think that there is anything specific about it in the HY manual text.
No problem at all glad that its working :D
Alex
It is mentioned in the 2.1 manual here:Quote:
Originally Posted by cropwell
http://www.nvcnc.net/pdf/NVCNC_DDCSV2_EN.pdf
There are also a couple of new parameters there as well.
[/ranton] HOWEVER why in the name of Babbage does the version 2.1 manual still use screen shots of an ancient 1.1 version that does not even show the Machine co-ordinates? Are they taking the piss out of us!!
[/rantoff]
Ah thats better
Will ( a very mad modder)
Having read this thread from end to end (ignoring a lot of the ranting and raving) I have a serious question about tool probing.
I have seen the video showing probing working as expecetd (!!)
It is not working for me.
I have tried to understand the parameters involved:
Parameter #68 Has 3 value 0 Disabled, 1: Mode 1, 2: Mode 2. Anyone have a definition of what these mean?
Parameter #69 Thickness: Ok I understand this one (But I though there was a reference to the controller measuring the tool sensor height)
Parameter #70 Signal Level: Again OK
Parameter #71 Initial Tool Position: If set to 1 machine heads off to Machine Home (as set in MACH workspace) If set to 0 nothing happens in X and Y.
Params #72, 73, 74 Define offsets from the Machine Home if #71 == 1
Parameter #75 sets the retract distance after probing. Understood but as probing doesn't work ...
Todays experiment:
Fit a simple touch plate and wire it in.
Confirm that if #68 == 0 nothing happens.
Set #68 to 1 and 2 and see what happens!
In either mode 1 or 2 state, On starting the probe cycles, it descends slowly, touches the touch plate, pauses and then retracts in the Z+ direction very slowly and then it never stops!!
Totally different behavious to the video where after the contact and brief pause the tool quickly rises to the retract distance.
Please help what am I doing wrong?
So I have been looking at probe.nc as installed
Attached is the original version (with Chinese comments)
Unbelievably I managed to translate the Chinese!!
https://www.google.ie/search?q=chine...hrome&ie=UTF-8
Attatched is the English version
No wonder the spindle rise to infinity and beyond: "G91 G01 Z1000 F5"
@Boyan and Benedikt: Is this the same file as on your working system??
As it was such fun translating the Chinese I decided to have a go at slib.nc.
If this is actually used by the controller (as I'm sure the probe.nc is used) then it shows that the controller can handle very sofisticate g-code and a simple sert of language constructions/data variables/trig functions/macro calls etc.
Attatched is the translation with a bit of re-formatting
Attachment 23722
Where you able to get the probe function to work?
It works for me until I clip on to the tool.
Just touching the 2 probe leads together seems to work, but when I clip either lead on the tool it just goes down and stops/binds up.
No not yet!!
oops this attachment attacher is crap compared to SMF
Thing this is the right one
Attachment 23723
Hey buddy.Quote:
Originally Posted by Bubbles
Just an idea, as I've recently got my setup working along with the touch probe, but do you have the polarity of the touch probe wired up correctly?
From memory the ground pin needs to go to the croc clip which clips to your router bit and the positive to the isolated touch puck which sits on the material surface
If you have it the other way around, as the spindle is grounded, connecting a positive wire to it would confuse things.
Ian Contessa
Thanks for the reply.
I have tried with the probe wired both ways.
It worked with an earlier version of firmware, but I can't seem to get it to work with the Xmas version of the firmware I downloaded from MadModder. https://madmodder.net/index.php?acti...0;attach=39115.
From my understanding of the manual the probe signal is PROBE terminal to +12V-I.
I don't see how it can work that way with the +12V-I connected to the tool. (grounded out) But like I said, I've tried it both ways.
I have also tried PROBE to Ground. (didn't work)
The only way I see that it could work would be if tool was isolated from ground.
That right there is your answer!Quote:
Originally Posted by Bubbles
The guy who is modifying the code has broken something and has not yet fixed it.
I can't see a version list with faults and fixes so you can know what is good in any given version, it's a Crap Shoot!
Hey Buddy.Quote:
Originally Posted by Bubbles
No problem, you're welcome. Glad to try and give some possible ideas.
I'm with magicniner, in that if it was workign on a previous firmware then the current one instaleld has broken it.
I'm watching the Pandora development, as what those guys are doing is brilliant and makes the unit nicer, but I have resisted flashing it myself as the setup works for me so far. So I'm reluctant to mess around until I really need to.
Try flashing back to a previous working firmware and see if that makes things right again.
Ian
Slowly making progress in understanding the control language thats supported. It looks very like Fanuc Macro Control language.
I think this may be where the system variables come from but so far I have had no luck trying to find a concise reference manual for the Fanuc languiage.
Any one have any links?
I have got loops and conditions working now trying to figure out subroutine calls.
Will
Does anyone know if any of the Fanuc Post Processor Scripts in Aspire work out of the box with this?
I had previously created a post processor to work in Solidworks / SolidCAM but had to wipe the PC and cant bring myself to sit for hours re-doing it?
Thanks
Alex
No need. Use G Code ATC /or no/ . Do not use mach3 post, will not workQuote:
Originally Posted by AlexDoran
Hi Boyan,
Thanks that worked! I dont need to use Gcode ATC or Gcode ARC?
I have another question, maybe you can help. Im now using Aspire, and it was working very well, however when drawing in the program the Y Direction of my machine was wrong, so my parts were coming out mirrored on the Y Axis.
So i changed the parameters and wiring to flip the Y Direction and make it home to the Positive, and move in the negative (Because my home position is top left).
After changing everything, the machine moves correctly, and homes correctly. Aspire is generating the code correctly (Making Y move in the Negative direction and not the positive), however now the controller refuses to run the code.
I am pulling my hair out trying to figure out what the problem is.
Any help would be appreciated.
Alex
EDIT: The problem above magically fixed itself.....
Have anyone tried the find center function on the DDSCV1.1? Also wondered if anyone have tried writing macros for it yet?
Never knew about a "Find Center function". How is it invoked.
I have written a test sub-routine:
(Safe Block)
G17 G21 G90 G54 G40 G49 G80
(Investigate Subroutines)
(set initial X, Y and Z)
G01 X0.0 Y0.0 Z0.0 F100
#1 = 3.888
G01 Z2.0
G01 X FIX[#1]; Round Down
G01 Y FUP[#1]; Round Up
G04 P5000; Little delay
(Note the above has nothing to do with testing the subroutine mechanism!!)
M98 P456 L3; Call subroutine 3 times
M30; End main Program
%
(Declare the Sub)
O456
G91
G01 X2.0 F50
G90
G04 P3000; Little delay
M99; End of Sub
%
The find center function can be used by redefining the start button. It can be set in parameter #446
Hi,
First post - and I'm sorry if this is not an appropriate location/method of seeking advice.
I have recently completed the conversion of a Sieg Mini Mill and am using the DDCSV1.1 controller (Madmodder Flashed).
Surprisingly - everything seems to be working and a test gcode sample appears to be doing what I had hoped it would. I have yet to cut any metal with it but that will happen soon I hope.
There is one aspect of the function of the controller that is currently bugging me - that is the Homing Function.
I have proximity limit switches on all the axis and they appear to be functioning properly - but when I invoke the Homing Function the following happens:
Z comes down to limit switch then goes up to upper limit and stops (Unit displays "Z-axis pos limit trig'd")
Then
X moves to neg limit switch then goes back to pos limit and stops (Unit displays "X-axis pos limit trig'd")
Then
Y moves to neg limit switch then goes back to pos limit and stops (Unit displays "Y-axis pos limit trig'd")
leaving all axis at positive limit.
Is this whats supposed to happen? The values on the DDCSV do not reset and the axis do not back off the limits. Is this whats supposed to happen?
I would be very grateful for any advice.
L_Ward
There is an adjustment if the axis should try a couple of times homing, then back off after homing and where the homing happens. Hard to guess more, as you use modded controller.
Thanks for the reply Boyan. Managed to sort things out. Homing OK now.