MicroBlaze MCS General Purpose Input (GPI1_Interrupt)

So I have generated a MicroBlaze MCS v1.2 Core and I enabled General Purpose Interrupt 1 (32-bits) and I checked the box for "GPI Interrupt".
Now the "GPI Interrupt" is set as an output node, while the GPI1 is set up as an interrupt.
I have searched all over the Xilinx documentation and this forum, and I cannot determine the answer to the following:
What and when does GPI1_Interrupt trigger? And why is it an output signal and not an input signal?
Here is a copy of the entity of my core:
entity microblaze_mcs_core is
port (
Clk : in STD_LOGIC := 'X';
Reset : in STD_LOGIC := 'X';
INTC_IRQ : out STD_LOGIC;
GPI1_Interrupt : out STD_LOGIC;
GPI2_Interrupt : out STD_LOGIC;
GPO1 : out STD_LOGIC_VECTOR ( 31 downto 0 );
GPO2 : out STD_LOGIC_VECTOR ( 31 downto 0 );
GPI1 : in STD_LOGIC_VECTOR ( 31 downto 0 );
GPI2 : in STD_LOGIC_VECTOR ( 31 downto 0 )
end microblaze_mcs_core;
I am basically trying to figure out what is the best way to transfer data to and from my MicroBlaze core.  Please note that I am using this core from LabVIEW FPGA, so any logic I use will have to be implemented by me! 

Duplicate post. Look here.
Regards,
Chris Delvizis
National Instruments

Similar Messages

  • Having trouble figuring out how to use trigger inputs as a general purpose input.

    I'm trying to use "Trigger 1" as a general purpose input to indicate the status of external circuitry. I can't seem to get the "Read High-Speed Capture Status" to indicate anything. I'm using the "Configure High-Speed Capture" VI with the capture mode set to Inverting Digital Input, and that VI feeds into a Do-While loop which contains the "Read High-Speed Capture Status" VI, which has the Ret Vect set to 0. I see from the online help that the High-Speed Capture function is available on Servo and Closed-Loop stepper systems, which I suppose is to enable the ability to read the position of the encoders. I'm using an open loop stepper system, so are these High-Speed Capture fun
    ctions unavailable even though I'm looking only for status (Trigger 1), and not concerned with reading position? Thanks in advance, Rob.

    Thanks for the answer Ken. I'm going to try a different workaround. The global was too slow, and I think I'll break my subVI into two parts. I'll create a sub that has all the setup stuff in it, then embed the actual "check trigger status" loop in the main VI. The loop contains only 2 or 3 nodes. Too bad LabView works this way. I can see one reason it should, but another larger reason it shouldn't. Wishlist.... Oh, speaking of wishlist, I like the improvements that 6.0 has brought, but one thing still bugs me. There's no way to have LabView remember the place to look for files when it's first started. It defaults to "My Documents", which should be, as all LabView programers know "LabVIEW6\user.lib" (or whatever). Of course, once th
    ere, LabView remembers for that session. Next time it's started, back to "My Documents" again. How 'bout fixing the "Options", "Path" settings so that it will actually remember the path set? Am I missing something here, or does it have anything to do with the fact that we're using Windows 98? My buddy's using NT, and his works the same. Is there a way around this? TIA, Rob.

  • How to create general purpose database using dbca

    Hi,
    I have installed oracle 10g on AIX .
    and now i have to create a database/instance for the firsttime whch must to be general using dbca.
    I want to create database silently. could any one please tell me the command to create a database silently

    Hello,
    So as to do a completely silent installation you may use a responsefile as follow:
    $ORACLE_HOME/bin/dbca -silent -cloneTemplate *<General Purpose option>* -datafileDestination */datafilepath* -responseFile */local_dir/dbca.rsp*Where dbca.rsp is a response file template that you may edit so as to supply administrative password,...
    Else, about the reason why your command got stuck. You may check the exact options with the statement below:
    dbca -hIt may change from one release to another.
    Hope this help.
    Best regards,
    Jean-Valentin

  • A general purpose TV tuner driver or software for SL?

    I have a tv tuner card which is windows compatible and I would like to use it with my mac. this... http://entermultimedia.com/tvtuner_external_usb210U.html is the one. Is there like a general purpose tv tuner driver for mac?

    Elgato's EyeTV software
    <http://www.elgato.com/elgato/na/mainmenu/products/software/EyeTV3/product3.en.h tml>
    supports many TV tuners, but does not list yours. Maybe yours is actually a rebranded model that is supported. You could try contacting Elgato.

  • "North America General Purpose 2"-color setting back on every start : PS CS5, Win 8.1 HELP

    Hi,
    have a problem with my Photoshop CS5 Color Settings on Windows 8.1. Maybe there's already a thread but haven't found.
    If I close and reopen PS my color settings are gone and back on "North America General Purpose 2" with sRGB. Have to change every time I open PS doesn't matter if I'm admin or user. Why doesn't PS leave my settings as the default the next time it opens?
    Any ideas? Cause this is very annoying ...

    Could be a problem with the Color Settings. Open it up and press the Alt key. The Cancel button will change to Reset. Click on that and it should place it to default. The Custom settings should hold.
    If not, you can use the Save button, give your Custom setting a name, add some notes and Save it.
    Gene

  • How can we distinguish b/c general purpose and top level containers?

    how can we distinguish b/c general purpose and top level containers?plzzz help me out

    May be this will help u out
    http://www.ictp.trieste.it/~manuals/programming/Java/tutorial/uiswing/components/components_pics.html

  • MicroBlaze MCS: UART TX in Interrupt Mode (I/O Module)

    I'm getting my feet wet with the MicroBlaze MCS IP Core, and I'm having trouble using the XIOModule_Send function in interrupt mode.  My assumption is that I simply don't understand how things are supposed to be hooked up - I'm hoping someone can show me what I'm doing wrong.
    Below is my C code: 
    #include <stdio.h>
    #include "xiomodule.h"
    #include "xparameters.h"
    int main()
    u8 msg[20] = "Buffer Text\r\n";
    XIOModule io;
    microblaze_enable_interrupts();
    microblaze_register_handler(XIOModule_DeviceInterruptHandler, XPAR_IOMODULE_0_DEVICE_ID);
    XIOModule_Initialize(&io, XPAR_IOMODULE_0_DEVICE_ID);
    XIOModule_Uart_EnableInterrupt(&io);
    XIOModule_Connect(&io, XIN_IOMODULE_UART_TX_INTERRUPT_INTR, (XInterruptHandler)XIOModule_Uart_InterruptHandler, &io);
    XIOModule_Start(&io);
    XIOModule_Send(&io, msg, 20);
    xil_printf("Immediate Text\r\n");
    If I understand correctly, as each byte of msg is transmitted, XIOModule_Uart_InterruptHandler should fire and call SendDataHandler, which in turn calls XIOModule_SendBuffer.  That function manages shifting the SendBuffer.NextBytePtr pointer to the next byte in the buffer, decrementing SendBuffer.RemainingBytes, and transmitting the next byte.  This process of interrupts should continue until the entire buffer (or however many bytes are specified in the XIOModule_Send call) are transmitted.
    However, the output I end up with is this:
    BImmediate Text
    I was expecting something more like this:
    BImmediate Text
    uffer Text
    Interestingly (to me, who admittedly doesn't fully understand how all this works), if I debug the program, and step through the code, making sure to step INTO the XIOModule_Send call, and step INTO the XIOModule_SendBuffer call, the output comes out like this:
    Buffer Text
    Immediate Text
    If I step OVER either of those functions, my output is the same as simply letting the program execute.
    I realize that I can use the XIOModule_Send function in "polled mode", essentially placing it in a loop, and using the return value of the function to see how many bytes were transmitted during the call (if any), then re-calling the function with an appropriately updated buffer pointer, and finally exiting the loop when the entire buffer is sent.  My objective, however, is to utilize the "interrupt mode", allowing the UART buffer to transmit while the micro performs other tasks (and not "blocking" it for the entire message all at once).
    I'll also mention that I've made the correction to my XIOModule_Uart_InterruptHandler mentioned here.  I have written a few other pieces of test code, and can get receive interrupts to fire as expected.
    Thanks for your time!

    I hacked away at this for a couple of weeks, and finally got things straightened out.  The short of it is that the Xilinx drivers for the I/O Module UART aren't the most robust, and have problems that stem from three main issues:
    1) The UART status register and interrupt enable/pending registers do not contain the same kind of data.  In more than one location, data from one is compared as though it came from the other.
    2) UART interrupts are acknowledged before they're serviced.  This means the interrupt pending register can't be checked to see what type of UART interrupt (RX or TX) fired.
    3) The UART TX interrupt fires when the UART TX buffer is emptied.  This means the UART TX buffer can't be relied on to tell what kind of UART interrupt fired.
    So, on to the code...  I made changes to XIOModule_Uart_InterruptHandler and XIOModule_SendBuffer, both located in xiomodule_uart_intr.c, and things are now working basically as I would expect.  I'll quickly mention that, if anyone wishes to make similar adjustments, they should be made to the "master" source files located at \Xilinx\14.7\ISE_DS\EDK\sw\XilinxProcessorIPLib\drivers\iomodule_v1_04_a\src (assuming your version and installation are similar to mine), and then the board support package will need to be regenerated; changing the source files in an already-generated BSP won't actually do anything.  Play it safe - make backups, or just comment out the original stuff.
    First off, let's pick apart the "out-of-the-box" XIOModule_Uart_InterruptHandler (this function is intended to be connected to UART RX and TX interrupts - XIN_IOMODULE_UART_RX_INTERRUPT_INTR and XIN_IOMODULE_UART_TX_INTERRUPT_INTR from xiomodule_l.h - using the XIOModule_Connect function from xiomodule.c):
    void XIOModule_Uart_InterruptHandler(XIOModule *InstancePtr)
    u32 IsrStatus;
    Xil_AssertVoid(InstancePtr != NULL);
    * Read the status register to determine which, could be both,
    * interrupt is active
    IsrStatus = XIOModule_ReadReg(InstancePtr->BaseAddress,
    XIN_IPR_OFFSET);
    if ((IsrStatus & XUL_SR_RX_FIFO_VALID_DATA) != 0) {
    ReceiveDataHandler(InstancePtr);
    if (((IsrStatus & XUL_SR_TX_FIFO_FULL) == XUL_SR_TX_FIFO_FULL) &&
    (InstancePtr->SendBuffer.RequestedBytes > 0)) {
    SendDataHandler(InstancePtr);
    To begin with, the value of the interrupt pending regsiter is read and stored to the IsrStatus variable.  Bit 0 is then compared (XUL_SR_RX_FIFO_VALID_DATA = 0x0 in xiomodule_l.h) to determine whether or not a UART RX interrupt fired (bit 0 of the UART status register indicates RX valid data; it tells whether or not the UART TX buffer, which holds a single byte of data, is full).  As matthijsbos points out in his post (link in OP), this comparison doesn't accomplish anything, and always results in a false result, since IsrStatus contains data not from the UART status register, but from the interrupt pending register, bit 0 of which indicates whether or not a UART error interrupt fired.  Hence, ReceiveDataHandler is never called.  Following is his recommended correction, the function can be modified thusly:
    void XIOModule_Uart_InterruptHandler(XIOModule *InstancePtr)
    u32 IsrStatus;
    Xil_AssertVoid(InstancePtr != NULL);
    * Read the status register to determine which, could be both,
    * interrupt is active
    //IsrStatus = XIOModule_ReadReg(InstancePtr->BaseAddress,
    // XIN_IPR_OFFSET);
    IsrStatus = XIOModule_ReadReg(InstancePtr->BaseAddress,
    XUL_STATUS_REG_OFFSET);
    if ((IsrStatus & XUL_SR_RX_FIFO_VALID_DATA) != 0) {
    ReceiveDataHandler(InstancePtr);
    if (((IsrStatus & XUL_SR_TX_FIFO_FULL) == XUL_SR_TX_FIFO_FULL) &&
    (InstancePtr->SendBuffer.RequestedBytes > 0)) {
    SendDataHandler(InstancePtr);
    The offset passed to XIOModule_ReadReg is changed from XIN_IPR_OFFSET to XUL_STATUS_REG_OFFSET (from 0x34 to 0x8, both in xiomodule_l.h), resulting in the UART status register now being read into IsrStatus (the variable name should probably have been changed for clarity, but oh well).  Consequently, an appropriate comparison is made against the value of the RX valid data bit, and UART receives now work correctly in "interrupted mode".
    ...however, let's continue on to look at the code handling UART TX interrupts.  The value of the TX used bit, again from the UART status register, is compared, and the value of the SendBuffer.RequestedBytes variable (inside the XIOModule struct, defined in xiomodule.h) is checked to see whether or not a UART TX interrupt has fired.  SendBuffer.RequestedBytes is set when XIOModule_Send is called by the application, and is reset to 0 by SendDataHandler after the indicated number of bytes in the referenced buffer have been placed into the UART TX buffer (both of these functions are in xiomodule_uart_intr.c).  This means it's a solid check to see if more bytes still need to be transmitted, but it's not a stand-alone indicator of whether or not a UART TX interrupt has fired, hence the coupling with the TX used bit check.  This bit tells whether or not the UART TX buffer is full (similar to the UART RX buffer, it holds only a single byte).  Unfortunately, as mentioned at the top of the post, the UART TX interrupt fires when the UART TX buffer is emptied, so when this comparison is performed, it will always return false, and SendDataHandler will never be called.  The inverse comparison can't be made, since it's possible for a UART RX interrupt to occur, and for there to be a byte of data in the UART TX buffer which simply hasn't been transmitted yet (it would also fail following transmission of the final byte of data).
    As a solution, I pose the following.  XIOModule_UART_InterruptHandler is intended to be called only for UART RX and UART TX interrupts.  As written, it is intended to deal with both interrupts firing at the same time (though, for the above reasons, it doesn't actually work) with default interrupt servicing (only the highest priority interrupt will be serviced - to set otherwise, XIOModule_SetOptions from xiomodule_options.c would need to be called passing XIN_SVC_ALL_ISRS_OPTION from xiomodule.h).  The likelkihood of both interrupts occurring "simultaneously" (within the same microprocessor clock cycle) is remote, and thus I claim only a single comparison is necessary to determine which of the two interrupts fired:
    void XIOModule_Uart_InterruptHandler(XIOModule *InstancePtr)
    u32 IsrStatus;
    Xil_AssertVoid(InstancePtr != NULL);
    * Read the status register to determine which, could be both,
    * interrupt is active
    //IsrStatus = XIOModule_ReadReg(InstancePtr->BaseAddress,
    // XIN_IPR_OFFSET);
    IsrStatus = XIOModule_ReadReg(InstancePtr->BaseAddress,
    XUL_STATUS_REG_OFFSET);
    //if ((IsrStatus & XUL_SR_RX_FIFO_VALID_DATA) != 0) {
    // ReceiveDataHandler(InstancePtr);
    //if (((IsrStatus & XUL_SR_TX_FIFO_FULL) == XUL_SR_TX_FIFO_FULL) &&
    // (InstancePtr->SendBuffer.RequestedBytes > 0)) {
    // SendDataHandler(InstancePtr);
    if ((IsrStatus & XUL_SR_RX_FIFO_VALID_DATA) != 0)
    ReceiveDataHandler(InstancePtr);
    else
    SendDataHandler(InstancePtr);
    In my version of the function, only the UART RX receive buffer is checked to determine which of the interrupts fired.  Since XIOModule_Uart_InterruptHandler will ONLY be called when either a UART RX or UART TX interrupt fires, neither of the appropriate handlers will be called erroneously.  There is only the (extremely) small chance that both interrupts will fire within the same microprocessor clock cycle, in which case only ReceiveDataHandler will be called, resulting in only the UART RX interrupt being appropriately serviced.
    ...yet this still doesn't completely get "interrupted mode" UART transmits working.  Let's now take a look at the unedited version of XIOModule_SendBuffer:
    unsigned int XIOModule_SendBuffer(XIOModule *InstancePtr)
    unsigned int SentCount = 0;
    u8 StatusRegister;
    u8 IntrEnableStatus;
    * Read the status register to determine if the transmitter is full
    StatusRegister = XIOModule_GetStatusReg(InstancePtr->BaseAddress);
    * Enter a critical region by disabling all the UART interrupts to allow
    * this call to stop a previous operation that may be interrupt driven
    XIomodule_Out32(InstancePtr->BaseAddress + XIN_IER_OFFSET,
    StatusRegister & 0xFFFFFFF8);
    * Save the status register contents to restore the interrupt enable
    * register to it's previous value when that the critical region is
    * exited
    IntrEnableStatus = StatusRegister;
    * Fill the FIFO from the the buffer that was specified
    while (((StatusRegister & XUL_SR_TX_FIFO_FULL) == 0) &&
    (SentCount < InstancePtr->SendBuffer.RemainingBytes)) {
    XIOModule_WriteReg(InstancePtr->BaseAddress,
    XUL_TX_OFFSET,
    InstancePtr->SendBuffer.NextBytePtr[
    SentCount]);
    SentCount++;
    StatusRegister =
    XIOModule_GetStatusReg(InstancePtr->BaseAddress);
    * Update the buffer to reflect the bytes that were sent from it
    InstancePtr->SendBuffer.NextBytePtr += SentCount;
    InstancePtr->SendBuffer.RemainingBytes -= SentCount;
    * Increment associated counters
    InstancePtr->Uart_Stats.CharactersTransmitted += SentCount;
    * Restore the interrupt enable register to it's previous value such
    * that the critical region is exited
    XIomodule_Out32(InstancePtr->BaseAddress + XIN_IER_OFFSET,
    (InstancePtr->CurrentIER & 0xFFFFFFF8) | (IntrEnableStatus & 0x7));
    * Return the number of bytes that were sent, althought they really were
    * only put into the FIFO, not completely sent yet
    return SentCount;
    First, XIOModule_GetStatusReg (from xiomodule_l.h) is called to retreive the value of the UART status register.  This value is then apparently used with a bit mask to disable any enabled UART interrupts.  Unfortunately, this is another case of comparing dissimilar data from two different registers.  Further complicating matters, the contents of the interrupt enable register can't be read as an alternative (an attempt to read any of the constituent bits will return a 0, even if the associated interrupt is truly enabled).  Continuing, the value of the UART status register is again checked to ensure the UART TX buffer is empty, appropriate variables in the XIOModule struct are checked to see how many bytes still need to be transmitted, and the address of the next byte to place into the UART TX buffer is used to do just that.  After send counts are updated, the value of the UART status register is again erroneously used in an attempt to re-enable any UART interrupts that had been disabled earlier in the function.
    My corrections instead rely on the value of the CurrentIER ("current interrupt enable register") variable in the XIOModule struct, which is appriopriately updated by other functions as interrupts are modified, to correctly disable and enable UART interrupts:
    unsigned int XIOModule_SendBuffer(XIOModule *InstancePtr)
    unsigned int SentCount = 0;
    u8 StatusRegister;
    u8 IntrEnableStatus;
    * Read the status register to determine if the transmitter is full
    StatusRegister = XIOModule_GetStatusReg(InstancePtr->BaseAddress);
    * Enter a critical region by disabling all the UART interrupts to allow
    * this call to stop a previous operation that may be interrupt driven
    //XIomodule_Out32(InstancePtr->BaseAddress + XIN_IER_OFFSET,
    // StatusRegister & 0xFFFFFFF8);
    * Save the status register contents to restore the interrupt enable
    * register to it's previous value when that the critical region is
    * exited
    //IntrEnableStatus = StatusRegister;
    XIomodule_Out32(InstancePtr->BaseAddress + XIN_IER_OFFSET, InstancePtr->CurrentIER & 0xFFFFFFF8);
    * Fill the FIFO from the the buffer that was specified
    while (((StatusRegister & XUL_SR_TX_FIFO_FULL) == 0) &&
    (SentCount < InstancePtr->SendBuffer.RemainingBytes)) {
    XIOModule_WriteReg(InstancePtr->BaseAddress,
    XUL_TX_OFFSET,
    InstancePtr->SendBuffer.NextBytePtr[
    SentCount]);
    SentCount++;
    StatusRegister =
    XIOModule_GetStatusReg(InstancePtr->BaseAddress);
    * Update the buffer to reflect the bytes that were sent from it
    InstancePtr->SendBuffer.NextBytePtr += SentCount;
    InstancePtr->SendBuffer.RemainingBytes -= SentCount;
    * Increment associated counters
    InstancePtr->Uart_Stats.CharactersTransmitted += SentCount;
    * Restore the interrupt enable register to it's previous value such
    * that the critical region is exited
    //XIomodule_Out32(InstancePtr->BaseAddress + XIN_IER_OFFSET,
    // (InstancePtr->CurrentIER & 0xFFFFFFF8) | (IntrEnableStatus & 0x7));
    XIomodule_Out32(InstancePtr->BaseAddress + XIN_IER_OFFSET, InstancePtr->CurrentIER & 0xFFFFFFFF);
    * Return the number of bytes that were sent, althought they really were
    * only put into the FIFO, not completely sent yet
    return SentCount;
    With both of these functions modified as I have above, UART transmits work as I would expect them to in "interrupted mode".  Once a byte is placed into the UART TX buffer, execution returns to the primary application.  When the UART TX buffer clears, a UART TX interrupt fires, the next byte is placed into the UART TX buffer, and execution again returns to the primary application.  This continues until all indicated bytes are transmitted, and then the application provided send data handler is called (set with XIOModule_SetSendHandler in xiomodule_uart_intr.c).  A good pracitce for this handler would be to immediately disable/disconnect UART TX interrupts in order to avoid complications and unintended results.  It's worth mentioning that attempting to interject non-interrupted mode UART transmits (say, for instance, using xil_printf) in the middle of an interrputed mode transmit will produce very unpredictable results.
    That all being said...  I would wager that many of those using an embedded MicroBlaze controller for its UART functionality are probably doing so while their VHDL is doing all the "heavy lifting", and the gains made by utilizing "interrupted mode" transmits would be marginal.
     

  • Ymenu - Interfaces - Post Document (General Purpose) -- FBB1

    Hi,
    I tried to perform as per below:
    I went to ymenu - -> Interfaces --> Post Document (General Purpose) -- FBB1
    After that in the Source file, i selected the file that i would like to upload.
    Follow by click on the execute button.
    Can i know after i have uploaded to the SAP system then how am i going to display or review back the uploaded data in the SAP System. (The data is in Excel)
    Which transaction code should i use?
    Thanks.
    Best Regards,
    Joo

    Hi Gimmo,
    Thanks for the links.
    I went to  "Reports for evaluating transferred data - RFBELS00 "
    Then i enter RFBELS00 into the SAP system but this Transaction code does not exist?
    i went to SE16, i think RFBELS00 is not a table rite?
    Can i know how am i going to display it?
    Thanks.
    Best Regards,
    Joo

  • I am having trouble with custom color settings. It randomly reverts back to North American General Purpose without warning. This is a big problem for me. My customers (professional photographers) expect consist colors in my printing. Help!

    I am having trouble with custom color settings. It randomly reverts back to North American General Purpose without warning. This is a big problem for me. My customers (professional photographers) expect consist colors in my printing. Help!

    Do you even know how to nuke and re-set Photoshop's preferences, colorplak?  Your last post seems to reveal that you don't understand what I'm talking about. Here's a link you can click on:
    Preference file functions, names, locations | Photoshop CC
    To re-create the preferences files for Photoshop, start the application while holding down Ctrl+Alt+Shift (Windows) or Command+Option+Shift (Mac OS). Then, click Yes to the message, "Delete the Adobe Photoshop Settings file?"
    Note: If this process doesn't work for you while you're using a wireless (bluetooth) keyboard, attach a wired keyboard and retry.
    Important: If you re-create the preferences by deleting the Adobe Photoshop CC Settings file, make sure that you only delete that file. If you delete the entire settings folder, you also delete any unsaved actions or presets.
    Reinstalling Photoshop does not remove the preferences file. Before reinstalling Photoshop, re-create your preferences.
    Note for Photoshop 14.1 and later: If you use Generator and reset your Preferences, Generator is disabled. Choose Preferences > Plug-ins to turn it back on.
    Video: Julieanne Kost created a video that takes you through two ways of resetting your Photoshop preferences. The manual preference file removal method is between 0:00 - 5:05. The keyboard shortcut method is between 5:05 - 8:18. The video is located here.
    Mac OS
    Important: Apple made the user library folder hidden by default with the release of Mac OS X 10.7. If you require access to files in the hidden library folder to perform Adobe-related troubleshooting, see How to access hidden user library files.

  • PXIe-8234 General Purpose?

    I have a PXIe-1082 chassis with a spare slot.  Can the PXIe-8234 be used in any slot and act as a general purpose Gigabit Ethernet interface for TCP/IP, UDP, multicast, and all that?  I don't need it for it's stated use as a GigE Vision interface, I may just need additional network I/O through LabView RT and through Windows 7 (Dual boot or separate hard drives).
    Thanks,
    Robert
    Solved!
    Go to Solution.

    Hi xl600,
    The PXIe-8234 can be used as a normal GigE interface.  It comes with the Vision Software which aids in vision-related applications, but this will be a functioning GigE interface for your PXIe system and doesn't have to be used for vision.
    Julian R.
    Applications Engineer
    National Instruments

  • OS X Server as a general-purpose LDAP server?

    Greetings!
    Wha's the conventional wisdom on the suitability of OS X server as a general-purpose LDAP server?
    It would seem to me that the OD schema extensions and ties to OS X logins might make it hard - is that accurate?
    Is it possible to add custom schemas to OD? Is it easy? (By easy, I mean as easy as, say, OpenLDAP under Linux?)
    Thanks!!!

    Hi,
    Wht is it you are trying to do?
    You can modify the schema as you do under Linux. However, the default configuration does conatin extra data that apple uses for various reasons such as networked home directories. You can completely change the schema if you wish, but its not really a recommendation I would make. You would be best just adding to the existing structure to try an meet your requirements.
    Thanks
    Gary

  • Will zeroizing and regenerating the Default-RSA-Key affect any other general purpose keys on my ASA 5545x?

    I have an ASA 5545x that is a production device for receiving all AnyConnect VPN traffic for our organization. We purchased and installed a Comodo certificate to create the trust level necessary for our employees to connect. I'm attempting to enable SSH on the device for management purposes, but the current <Default-RSA-Key> does not allow me to initiate a valid SSH session. I have encountered this issue on other ASAs within our organization, and it hasn't been an issue to simply zeroize the current key and regenerate it to restore the ability to SSH to the devices. Where the snag comes in is that this 5545x is the only ASA that has a key installed that wasn't self signed. With that in mind, I have a few questions about whether 3rd-party signed keys are dependent on the self-signed keys on the device. I intend to zeroize both the <Default-RSA-Key> and the <Default-RSA-Key>.server certificates if they will not affect my VPN-associated Comodo key.
    Does the Comodo key depend on other keys existing on the ASA?
    Am I free to zeroize only the <Default-RSA-Key> without affecting the VPN associated Comodo key?
    Here is the result of the command "show crypto key mypubkey rsa" :
    Key pair was generated at: 12:02:29 CDT Aug 19 2014
    Key name: <Default-RSA-Key>
     Usage: General Purpose Key
     Modulus Size (bits): 1024
     Key Data:
    <Redacted>
    Key pair was generated at: 10:16:52 CDT Sep 20 2012
    Key name: my.comodo.key
     Usage: General Purpose Key
     Modulus Size (bits): 2048
     Key Data:
    <Redacted>
    Key pair was generated at: 01:35:42 CDT Jul 30 2014
    Key name: <Default-RSA-Key>.server
     Usage: Encryption Key
     Modulus Size (bits): 768
     Key Data:
    <Redacted>
    Thank you to any and all that assist me in understanding how the ASA handles certificate keys.

    As long as the Comodo-signed certificate is bound to the my.comodo.key private key (i.e. you used that key when generating the certificate signing request), you should be fine to zeroize the Default-RSA-Key. The latter should ideally only be used for ssh access.

  • Using cRIO chassis slots for general-purpose

    hi,
    i have cRIO 9004 and cRIO 9103 chassis, labview 2011...
    as i know, cRIO chassis controls its slots if there present any module or not.. if detect anyone, read EEPROM and so on..
    but how can i control cRIO chassis slots for my own general-purpose without any module...
    when i create projects, it just shows me as chassis I/O
    * chassis Temperature
    * FPGA LED
    * Scan Clock
    * Sleep
    * system reset
    i couldn't write anything from chassis slots and see on oscilloscope screen, (for example: using as analog or digital output) ... 
    Davut..
    Solved!
    Go to Solution.

    thanks for your reply
    in fact i have...
    -module development kit 2.0
    -compactRIO module support 4.0.1
    -NIRIO 4.0
    i know which pins i can use for DIO or etc.. 
    the point is, i haven't thought that it is not possible without hardware.. i read the manuals but couldn't create all structure in my mind..
    So, as i understand from your message, i have some programs but it s not possible to controlling chassis slots without hardware.. am i right?

  • MicroBlaze MCS GPO write issues

    I'm using the Microblaze MCS with the XIOModule_DiscreteSet, and XIOModule_DiscreteClear functions to manipulate the GPO busses. For example here is how I use the function:
    XIOModule_DiscreteSet(&gpo, 1, (1 << 4)); //Turn on bit 4 of GPO1.
    Now the problem im having is if I use DiscreteSet or Clear in different functions each time I use a new function it completely resets the whole GPO bus.... This seems like a bug to me, but maybe Im doing something wrong?
    Here is an example of what I'm talking about:
    Lets say I call "XIOModule_DiscreteSet" in fuction "foo". I set bits 3 and 4 of the gpo. After foo ends and the program procedes to the next fuction "bar" and I again use "XIOModule_DiscreteSet" to set bits 5 and 6. But as soon as I try to get bit 5, it clears bits 3 and 4....
    Some other info: I have GPO declared as a global variable and the first thing I do in main is "XIOModule_Initialize(&gpo, XPAR_IOMODULE_0_DEVICE_ID);" Before I didnt have the GPO declared globally I just delared a new instance of GPO and re-initalized it in every function but I still saw this exact behavior

    Hi,
    In my opinion, this is probably not Windows GPO problem. To confirm the suppose, you can follow the path below to check GPO settings if there is any change after the software installed.
    Computer Configuration\Administrative Templates\System\Removable Storage Access
    User Configuration\Administrative Templates\System\Removable Storage Access
    These two policy manage system and current user Removable Storage access.
    If there is no change with these policy, it would be better to contact the manufacture of the driver for further assistance.
    Roger Lu
    TechNet Community Support

  • Is there a general purpose output stream class like in java?

    Hi, I sometimes create tools (abap OO classes) which output characters, that I would like to store in any media (frontend file, server file, string variable, ftp, clipboard, etc.) This is easily done in java via the output stream classes.
    Do you know if this kind of class exists? I saw some classes like that, but they are specialized, for example XML, SOAP. I look for non-specialized classes like in java.
    Same question for input streams! (normally, we should deduct the input stream classes from the output stream classes)
    Or did you develop yourself such input stream or output stream classes that you'd accept to share?
    Thx a lot
    sandra
    Thx a lot!
    Edited by: Matt on Nov 20, 2008 9:50 AM - Fixed the posting

    Yes it exists, but in release 7.10 only. [ABAP Keyword Documentation u2192  ABAP - By Theme u2192  Process External Data u2192  Streaming|http://help.sap.com/abapdocu/en/ABENSTREAMING.htm]

Maybe you are looking for