Gregs

You can use DACB+ by writing to Acc5E.Macro[j][1].a. For instance, make the assignment M1->Acc5E.Macro[j][1], then issue M1=16384*256 // multiply 256 to shift up by 8 bits and you should get 10V on DACB+. Detailed information on Gate2.Macro[j][k] can be found in the 16 AXIS MACRO CPU USER and SRM manuals by looking at the Turbo counterparts. Gate2.Macro[j][k] corresponds to Turbo X/Y:$7xxxx addresses. For instance: Gate2[0]Macro[0][0] is Y:$78420,0,24 Gate2[0]Macro[0][1] is Y:$78421,8,16 Gate2[0]Macro[0][2] is Y:$78422,8,16 Gate2[0]Macro[0][3] is Y:$78423,8,16 Gate2[0]Macro[1][0] is Y:$78424,0,24 All the Turbo PMAC2 MACRO Node registers addresses are listed in the memory and I/O map section of the Turbo SRM under Turbo PMAC2 MACRO Node Registers.

Hi Kit, Manuals are online at http://www.deltatau.com/Manuals/default.aspx The AMP-4 manual is under Amplifiers / 3U Amplifiers. The ACC-E1 (power supply) is under Control Systems / UMAC Turbo / Turbo PMAC2 UMAC CPU / Accessories. Small typo, that is an ACC-P3 (not D3). Please email drawing requests to Cat Foster at catf@deltatau.com.

I think that someone else had this problem. This was the solution: Copy these files onto a USB stick: Windows\INF\PmacUSB.inf Windows\INF\DeltaTau43.cat Windows\System32\Drivers\PmacUSB.sys Go to the device in Device Manager, select Properties, Update Driver Software…, Browse, Let me pick…, Have Disk, and then browse to and select the USB stick.

Turbo addresses are correct, but MACRO Station and PMAC2 Ultralite addresses on page 14 are incorrect, as stated in my last post. The correct addresses can also be seen in other I/O accessory manuals such as the ACC-11E or ACC-65E.

Those addresses are incorrect. Node 7 addresses are X:$C0AC,C0AB,C0AE,C0AF; Node 10 are X:$C0B0,C0B1,C0B2,C0B3; Node 11 are X:$C0B4,C0B5,C0B6,C0B7 addresses. This is corrected in the new edition which hopefully will be released soon. Thanks for reporting.

I could make a recommendation based on the I/O requirements. Note that the ACC-5E has a JIO port which connects to Opto-22 style boards, and a JTHW port which connects the ACC-34AA, but you would lose Gate 3 style MACRO which provides more nodes at lower cost.

Under the heading IO Port Setup, the manual describes how to configure the general purpose IO as either inputs or outputs and inverting or non-inverting. For an inverting I/O point, 0=+5V and 1=0V, and for a non-inverting I/O point, 0=0V; 1=+5V. It is TTL logic. A connection diagram would be helpful, wouldn't it? We are getting those into the I/O manuals now as they are created or revised.

I recommend emailing your question to support@deltatau.com

Hi Gigi, Please email your request to our CAD specialist Cat Foster, who generally handles such requests: catf@deltatau.com

The latest versions of PEWIN32 Pro2 already have the 64-bit drivers; I know that versions 4.3.0.0 and 4.3.2.0 have it.

Have you set PEWIN to "Run as an administrator", and do you have the latest version of the Executive, 4.3.2.0?

That is somewhat of a carryover from non-turbo days with slower CPUs, particularly at 20 MHz. It is much less likely to be a problem with a Turbo PMAC. If foreground PLCs (PLC0/PLCC0) are large enough, a watchdog might occur, especially at power-up. Running a large motion program(s) at power-up will compound the problem. Another consideration is that if background initialization PLCs are large enough, they might not complete before the foreground PLC runs.

Hi Chris, It does sound likely that the old card has a little wider tolerance and not likely that there is any hardware fault on the new card, considering that the amp voltage is already only about 0.02 volts above the minimum.

There is no problem with I54; it only has to be saved once before power is cycled (or a reset is issued). I would expect those jumpers to be at the defaults, which is good. I do not know what else to check, so I suspect that the board needs repair.

Hi Chris, I am inclined to think that the PMAC needs repair if the other PMAC does not have this problem in the same setup, but I would get a power supply that provides a good 12-15 volts first. Watchdog is triggered by the 5V supply not being between 4.5 to 5.5 volts (JMACH pins 1,2,3,&4), not by analog voltage levels on JMACH pins 59 and 60. The LIM flags are fail safe, meaning they will trip if something such as insufficient supply voltage disrupts the current flow thru them. I would expect homing to completely fail if there is a problem. It all depends on how PMAC and control software is programmed as to what will happen on recovery from a watchdog. PMAC would behave the same as if it were reset.

Below are the typical settings in the serial port properties window in PEWIN. Did you try those settings, with your baud rate and port#? Is the computer's serial port proven to work? Does it report in device manager that it is working properly? Did you cycle UMAC power after changing and saving I54? Do you have default jumper settings: E1A = 1-2 E1B = 2-3 E17A,E17B,E18A,E18B = 1-2

Hi Chris, Does the power supply measure 12-15V before being connected to the PMAC? I don't think that the 11V level would cause the noise, at least if it is a steady 11V. Can you check it with a scope? Try re-initializing the PMAC either with E51 jumper or $$$***. Maybe there is programming that is causing the noise. Check the ribbon cable for intermittent or poor connectivity in the IDC connectors.

You will need to use FREAD after power cycling; otherwise, FSAVE values will be overwritten with the last SAVE values. Perhaps you did not need to use FREAD because the last FSAVE and SAVE values were the same. You should not need to use FSAVECLEAR. The only issue would be if two FSAVEs are issued within 2 seconds of each other. And, issuing FSAVECLEAR before each 256th FSAVE would prevent the use of half of the memory space, thus reducing the expected life of the used half, by half. Speaking of expected life, just how often do you expect to issue an FSAVE? You could issue an FSAVE 2,747 times a day for 25 years before you hit 25,000,000! Not enough?

Sounds like a problem with the 5V supply, which you might see with a scope. Make sure that 5V is not being supplied to pin 1 or 2 on the JMACH. The old computer would have supplied 5V on the bus, so 5V should not have been supplied to JMACH pins 1/2 there either. Try disconnecting any other connections on pins 1/2 as well. If that is not it, move on to other JMACH connections.

Hello Chris, See responses inserted below: The watchdog LED is inactive, unless it is switching on for a very short period of time, the ticking is of fairly high frequency so perhaps this is possible? I look a long exposure picture and couldn't see any red in the LED. (The watchdog led is right next to the power led on the top board, correct?) The watchdog LED is normally green and turns red when a watchdog occurs. The IC driver in the new board is 2803A, E1 and E2 are both configured to connect pins 1 and 2, which I believe is the correct configuration. Unfortunately the old board is currently inaccessible, is there a way to tell the type of driver via software? That is for the JOpt (J5) I/O connection. I would try disconnecting that too. No way of which I know of knowing which IC was in place based on the software configuration. I have all the I-variables configured the same (aside from homing and Jog speed). Are there other variables that need to be configured that may cause this problem? The I-vars should be OK. Does this happen when the amps are powered even if PMAC is not enabling any axes? I will try connecting each pin one at a time. Are there any pins that could cause damage if connected independently (like a voltage rail with no ground connected?) No, but I would try connecting 5V and 0V (pins 1-4) first, then +analog power (pins 58 and 59), then -analog (pin 60), and then individual signals. Which jumpers may be a likely culprit? I am looking through the documentation so see which jumpers may affect the 5V rail; I have E40-E43 all on. (although the card is not installed in PCI 0 slot, but that doesn't matter, does it?) E28 connects ping 2 and 3. E85 and E87 are OFF. E89 is ON and E90 connects pins 1 and 2. A fairly likely culprit is conflicting supply voltage connections along with jumper settings. The 5V supply comes from the bus if PMAC is plugged in a computer in which case 5V must not be supplied on the JMACH connector. It is supplied on JMACH (pins 1-4) in a standalone setup. Which do you have? With your jumper settings, +/- 15V should be supplied on JMACH1 (J8) pins 58, 59, and 60. Note that the unmentioned E88 must also be off.

Hi Chris, The noise could be from the watchdog relay. If the 5V supply is too low, the relay will activate. Then, if the 5V subsequently increases or revives, the relay can de-activate, and so on. What is the watchdog LED doing? It could be mis-configured jumpers. I would see that they are the same as on the old board, and also make sure that the socketed IC drivers are the same, either 2803A or 2981A, and use the same backup configuration file. The JMACH1 pin connections are the same. I suggest connecting the pins one at a time to isolate one that causes the problem.

Hello Greg, Glad to hear it is working. I am surprised that USB did not display in Device Manager but did elsewhere. It should be seen in Device Manager now, now that there is communication.

Hi Greg, That sounds like a hardware failure. You could try reloading com firmware. Here is a forum link to instructions: http://forums.deltatau.com/showthread.php?tid=63&highlight=firmware.

Yes, I suggest emailing a request to support@deltatau.com and specifying rack size, accessories, and options on each board. If it is a UMAC that is unchanged from initial purchase, the serial number on the sticker on the side of the chassis will indicate all that information. To view the information, go to www.deltatau.com/sn and enter serial number.

Are you attempting to write directly to the individual bits of the MACRO output words? If so, that would be a problem because only full words should be used, or individual bits in a "mirror" word. See the examples in the MACRO section of the ACC-11E manual.