Hello! While working in premises of my customer to add new automatic material loading/unloading module for one of my machines, I have encountered strange error in ClassicLadder. I took a video on my phone with it: http://www.youtube.com/watch?v=9YjkGbpuT50
I will try to explain: The idea is to use classicladder to control valves for pneumatics that load the material in machine, hold it in place and then unload. When I started working on the ladder logic, everything was working fine, but then, at one moment, I think at the moment, when I linked one of classicladder input pins to motion.spindle-on, it just stopped turning the outputs on and off in a correct manner. Some of outputs are working fine, but others are doing I do not know what - seems like turning on for a very small amount of time at random moments. It is 2.5~pre, installed from buildbot package some time almost a year ago. I did copy all the config files, so I can share them, if that helps. I tried to workaround this with M62/M63 and M64/M65 commands and G4 inbetween them to specify correct time distances between any 2 events, but that did not work out nicely - I did not notice any difference after changing almost all P values for G4 command from 0,5 to 3,5. Restarting system for several times did not help either. I do not know, how many times did I restart LinuxCNC... Does anyone has any idea, what went wrong? -- Viesturs If you can't fix it, you don't own it. http://www.ifixit.com/Manifesto ------------------------------------------------------------------------------ WINDOWS 8 is here. Millions of people. Your app in 30 days. Visit The Windows 8 Center at Sourceforge for all your go to resources. http://windows8center.sourceforge.net/ join-generation-app-and-make-money-coding-fast/ _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
