TDrumheller

It successfully synced the coordinate system from the PMAC and updated the “systemsetup.cfg”, but unfortunately it is still adding the SignIsDirType line to systemsetup.cfg (with the default value of 0) when it updates it, even though that isn't a valid element of Coord[x] in this firmware version (only in firmware 2.6 and newer according to the Software Reference Manual), so it's still giving an error message when it tries to download the systemsetup.cfg to PMAC and tries to set an element that the firmware doesn't understand.

I'm having some problems downloading projects with any coordinate systems defined to a Power Brick AC with older firmware (2.3.2.5). The IDE automatically adds the "Coord[1].SignIsDirType=0" setting to the systemsetup.cfg file, but that parameter is not supported on the older firmware, so it gives an ILLEGAL CMD error when it tries to download the systemsetup.cfg file. For now I'm working around the problem by just not defining the coordinate system in the project and manually sending the axis definition commands, but I was wondering if there's any way to exclude certain values from being generated in the systemsetup.cfg to prevent this problem.

Thanks!

I'm currently trying to set up a system with a Power Brick AC controller which is a few years old (PowerPC 460EX, firmware 2.3.2.5), and according to the software reference manual, the Gate3[0].AdcAmpStrobe value should default to $FFFFFD on the Power Brick systems. When it is freshly reset to factory default settings ($$$***), it seems to be doing this as expected, but as soon as I send a "BrickAC.Reset = 1" command (for example in the PowerOnResetPLC in the standard power brick template project), the Gate3[0].AdcAmpStrobe value changes through a rapid sequence of values over about half a second before settling at $800001. If I set BrickAC.Monitor =1, the Gate3[0].AdcAmpStrobe value continuously changes, but certain digits don't change, it's always $8?4??1. The value will change even when the write protect is enabled (Sys.WpKey = 0). The low byte of Gate3[0].AdcAmpCtrl is not changing, only the AdcAmpStrobe part of it is changing. Is this the expected behavior of AdcAmpStrobe, or is something malfunctioning or incorrectly configured on my unit? Thanks for your help

Serial#: C000A4KE Part#: GBL4-F3-800-13D00000 Thanks, Tim

I'm using the Geo Brick Drive (with built-in amplifiers), not the Brick Controller. The page numbers I was referring to were from the October 13, 2011 version of the manual, and it looks like there was a new version of the manual on April 15 that moved the relevant section to pages 138-140, but the information seems to be the same. The suggested configuration (page 138, formerly page 150) that I used for the analog input is: M505->Y:$078105,8,16,S ; ADC Input value (ADC5A) M605->Y:$07810D,8,16,S ; ADC Input value (ADC6A) M705->Y:$078115,8,16,S ; ADC Input value (ADC7A) M805->Y:$07811D,8,16,S ; ADC Input value (ADC8A) I7106=$1FFFFF ; Servo IC1 ADC Strobe Word

I'm currently trying to configure the analog I/O options (connector X9) on a Geo Brick controller and I'm running into a few difficulties. The device connected to the input provides a single ended unipolar signal (0-10V), and I've verified that it is working with a volt meter. The device connected to the output expects a single ended bipolar signal (+/- 10V) I've configured the I variables and M variables to the recommended settings on pages 150-152 of the Geo Brick manual (the controller is currently at factory default configuration, except for the recommended I/O configuration settings), and I got the following results: The analog output seems to work, except that when pin 7 is tied to AGND as shown in the Single Ended wiring diagram on page 151, the output saturates at about +/- 4.2 V instead of +/- 10V. It seems to be linear and correctly scaled up to that point, but won't go any higher. With pin 7 disconnected, I can get the full +/- 10V range (measured between Pin 3 and AGND). Is it alright to just leave pin 7 disconnected? Also, the output is 12-bit, so it should have a range of 4096 counts, but the default settings restrict it to +/- 816 (1633 counts). If I'm understanding the documentation correctly, this limit is based on the PWM frequency configured by I7100. Based on the requirement that PWM frequency should be a multiple of (Phase frequency/2), it seems like I7100=2175 would be the closest to the +/-2048 needed to get the full 12-bit resolution. This would put the PWM frequency at 13.55 KHz (4.5173 KHz * 3), which is significantly below the 30-36 KHz range recommended. Is this reduction in frequency likely to cause serious ripple problems, possibly negating any benefits of the increased resolution? I'm having problems getting any reading at all from the analog input. With the suggested configuration on page 150, M505 always reads -1, and it does not change at all (not even a few counts of noise that might be expected if nothing was connected). Is there something else that needs to be configured to read these inputs? Thanks, Tim Drumheller