Eyewonder

Found it. Had to delete all of the NC32 files, & reload. Then single block worked as normal

Running WinXP , PMAC NC-32 v2.36(1) on PMAC1 Isa Universal LIte, with Adv600 4-switch control panel. All other functions seem to be working, but in both MDI & AUTO mode, all the codes execute, even though I have selected 'Single Block'. Both the toggle switch on the Adv600 panel, & the software control button on screen will change, indicating that it wants to be in single block, but programs & MDI both execute all lines of code. What did I set up wrong? Or NOT set up? Cheers, Steve

Well, found my checksum problem - I had left the E51 jumper on. Removed the jumper, power cycled the cpu, reloaded the plc's via PEWIN, then started NC-32 v2.36(1). No more checksum error problems, but .... I have forgotten how to bring the axes close loop, and then home the axes. Cheers

I'm bringing up a 3-axis system using a PMAC-PC Universal Lite ISA buss, with DPR on board. Software is v2.36(1), & the PROM version is 1.16G. PEWIN works with no problems, I'm able to download plc's & they appear to be working. When I start NC-32 I get messages saying: "PMAC Memory checksum is incorrect or not initialized" & "PMAC PROM checksum is incorrect or not initialized", along with axes not home referenced, amps not enabled, amps open loop. Do I have a hardware problem, or an operator (me) problem? Cheers

I'm using PMAC-NC32 v2.36(1), trying to use the 'Backup' registry button on bottom of the Motion.exe applet. It lets me enter the file name I wish to save to, acts like it completes, but it does not create the backup file - or I can't find it. How can I make that work? Or some other (simple) way to save all the Delta Tau registry settings. Cheers, Steve

I'm looking for an app note, or example of implementing open loop control of spindle for a bench-top wood router. The 4th axis is available for that use. The spindle is rated for ~20,000 RPM, but has no encoder, or tach. I believe the spindle drive gets low voltage (0-10?) for speed command from a pot on its drive cabinet. I would like to be able to issue an 'S1500' etc cmd for speed, and an M03/M04/M05 to turn it on & off. The card is PMAC Universal Lite w/DPR on board, using PMAC-NC32 v2.36(1), WinXP SP3. Cheers, Steve

Kaydon, After you changed the I-vars, did you do a 'SAVE'? I have not had any experience with a PMAC2, but some of the ISA PMACs have a battery, others have flash. If yours has a battery, that would certainly be something to check out. Cheers, Steve

DT, I would like to get the v1.16T firmware update for a PMAC Universal Lite w/DPR onboard (ISA Buss). Board #602402-106. Cheers, Steve

Good call. I checked a known good PMAC by looking at the connector status window, and verified all limit switches functioning. The PMAC-Lite showed ALL switches, ALL channels in open (activated) condition. Eventually found that A+15 was not getting to any of the MCT7 opto isolator chips. Turns out to have been a bad solder joint on one of the jumper pins (E89 - E90 path) that route the A+15 from the 60-pin connector to the MCT7 chips. Cheers, Steve

OK, got it. Cheers Steve

I have several PMAC (1) boards of various versions, and have been trying to verify that they can be used as backups. I have 2) PMAC Universal Lite w/DPR on board, a PMAC Lite needing Option 2 DRP board, and an PMAC-1 needing the Option 2 DRP. My base system uses the Universal Lite w/DPR onboard. The system works (not completely optimized, but usable), and I saved Global configuration. I am able to install the PMAC-1, the Option 2 DPR board, use the saved global configuration to load into the PMAC-1, and verify the expected normal operation. My PMAC-Lite, however, does not behave normally. The board is a 602402-101, Opt 5A, ver 1.16D. I have tried the E51 reset, $$$*** reset, load the global configuration & save. No obvious errors. With the above, I can not make any axis motion using 'View Jog Ribbon', auto tune, Oxx (output) command or any of the NC v2.36 operation control panel. Used 'View Position' to verify all encoder working correctly. With NC32 started, I can feel the X & Z axes holding position. If I remove the servo amp connector to one of the axis, move the axis with my hand, then reconnect the servo amp, the system will snap the axis back into position, as expected. So it looks like the servo loop is being closed correctly, but I can not get any new position commands to the system. Any ideas on things I have not tried? Cheers, Steve

I have a small lathe set up, and am able to to jog, home axes using Adv600 control panel, but do not fully understand how the MDI & buffer operate. I first home the X & Z axes. I enter 'S400 M03' (on separate lines) into the edit window, click the 'Write to Buffer' command button, then push the 'Cycle Start' button. Spindle rotates as expected. If I then enter 'Z1.5' (just some move to verify operation) into the edit window, as soon as I click the 'Write to Buffer' command button, it kills the spindle rotation. Pushing the 'Cycle Start' button causes the Z to move, as expected. Is this 'normal' operation for this software? BTW, this was using the v2.36 software, NOT the v2.36(1) 4 program changes. I enabled buffer logging and got these results: Cheers, Steve

I got the cards a few years ago, along with some other cards, on ebay. The system I am running is PMACNC-32 v2.36(1). When I run the Motion.exe, I double-checked, and the DPR address range includes 0D000. With my good DPR, this address is accepted, the PMAC is registered, and I can start PEWin. I did move the pin-grid-array DPR chip from bad board onto a good board, and the good board worked, the bad board with the previously running DPR chip did not. So unless there is something easy to check/repair, it looks like these are door-stops. Cheers, Steve

I bought two Option 2 Dual Port Ram cards as backups, but they do not seem to work. I tested them in a known working system using the Motion Applet to add the PMAC device. I set DPR address to 0D000 (as with the known working card) but the applet reports that it cannot find the PMAC. Both of the new cards do the same. Comparing these non-working cards to my working one I found a couple of things different. The part # for the good card was 602240-101, while the bad cards were both 602240-102. The good card has a serial number hand etched in the serial number block, and both of the bad cards were blank. Both of the bad cards had pins 41 & 42 (in the 50-pin header) physically missing. I was able to insert pins in positions 41 & 42 in both, but they still remain unusable. Ideas, anyone? Cheers, Steve

Never mind - I found the manuals buried in old file storage. Steve