Greetings all; Code that I had composed and ran on the sim, which is 2.7.7 these days, refused to run on the G0704 yesterday, with a really weird failure, getting to a spot in the code where I had stopped the spindle,and initialized some more variables, than set the spindle speed much higher to do the next 15 minutes worth of making chips. Motion.enable was true but motion would stop, presumably from a false input to motion.spindle-at-speed. The running spindle did emit a fairly heavy click, I assume because it was already turning at 400 revs, but my halfile does a boot sequence on Jon's pwmservo driver that runs the spindle any time a stop/start is done, this reboot of the spindle driver is inserted.
No other indications of an error but I did note that the former spindle speed would drift downward and if I sat there scratching my head long enough, it would even start running backwards, very slowly gaining speed. Looking at the code from the view of motions, I could see the the M5 was effectively followed immediately by the S1500M3, so on a hunch I added what I think is a Que breaker in the form of a G4P1 between them which I've now made the P a .1 so the pause is less noticeable, and it still works. I don't know if this is a bug, or if its something to do with the hal code that inits the driver any time a stopped to start transition occurs. IIRC motion.spindle-speed commanded changes, but I don't recall if the new speed was making it to hm2_5i25.0.pwmgen.00.value, ISTR seeing it still at about a noisy 6 when it should have been up around 25 Perhaps I shouldn't do the stop/start and just change the speed as I know that works well? The code snippet: G0 z1 ( stop spindle) M5 G4 P.1 (enforce a Que break else it stops and spindle slows, reversing eventually) ( change tool to a 1/4" end mill here ) ( no choice but to edit tool table for length of drill and length of ) ( 6.35mm end mill as mounted in a Chinese TTS toolholder ) ( this tool change will need to be added here but I don't know how to ) ( use the GO704's tool table from this sim axis running on coyote ) #<_x_travel> = 26.00 #<_z_deep> = -9.000 ( just a hair over 3/8" thick ) #<_z_tmp> = 0.000 #<_z_dec> = -2.0000 G0 z1 S1500 M3 G0 x#<_x_travel> y#<_y_width> The machine actually makes this last move, but I have to believe that the spindle-at-speed being false has inhibited any further motion. Since I still need to work on 3 more of the bellows nipples yet, and I cannot stop these tool holders from slipping and screwing up my work, I'll without doubt be working on the q value for a G83 command above this code, which is where the tool slippage is occurring. Smaller seems to help the slippage problem. A fresh tool might help too, as does some buttercut. The problem slippage is because these Chinese TTS holders can't be tightened in by the drawbar bolt, tight enough to stop the TTS from turning in the R8 when I am tightening the nut on the TTS. IMO these should have been keyed into the R8, but wasn't. I need a longer, 100 mm's doesn't give me enough leverage, square box end, not open end, wrench for the drawbar bolt. Those, in this neck of the woods, are apparently made out of hens teeth, or pure unobtainium maybe. I've not seen an 8 point box end in decades. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
