¿Cómo sincronizo varias señales en un DMA FIFO?

Buenas,
Tengo 3 señales en FXP y quiero llevarlo a un bloque FIFO para despues poderlas visualizar en un waveform chart. Cuando lo hago con una sola señal puedo visualizarla sin problemas, pero cuando intento mandar las 3 no lo consigo. Tambien he intentado poner un bloque FIFO para cada señal, pero cuando intento visualizarlas me sale un retraso entre las señales. Me podeis echar una mano en este asuntillo?
Un saludo.

Hola JesúsG,
Ante todo muchas gracias por tu contestación.
Le he quitado entradas y sólo he puesto 7, 6 de ellas están adquiriendo una señal de tensión y otra está conectada al COM.
Esta es la gráfica con las señales que estoy adquiriendo.
Si pauso la compilación y hago zoom obtengo esto
Como puedes observar en las imágenes hay un retardo entre señales, así que no creo que sea debido al número de canales, pero sigo sin saber cuál es el problema.
También me he fijado que depende de cuando pause la compilación cambia la señal que está a 0 y el retardo entre señales también varía.
¿Sabes a qué se puede deber?
Saludos

Similar Messages

Como puedo promediar varias señales analogicas en labview

hola a todos, estoy haciendo un proyecto en labview en el cual estoy recibiendo señales analogicas mediante un dac pero mi problema es que utilizo 4 sensore de temperatura de los cuales quiero promediar sus diferentes dato pero no se obtener su promedios alguien me puede orientar con un ejemplo?????

Hola Cazador:
Por lo que entendí es esto lo que estás buscando.
Saludos!
Juan Gil
NI México
Attachments:
promedio.vi ‏63 KB

How can i decide the depth of all3 DMA fifo's are used as target to host at RT contoller side(host)?

Hello,
I am using all DMA fifos,I want to acquire data from 3 AI modules upto 50 khz frequency.Sampling rate can be varied according to application.
please suggest me how should i allocate memory of my RT controller for those DMA fifos?I am also facing one problem, I am using 3 time deterministic loop with different different priorities,each time loop has one fifo where data is reading with polling method(first fifo.read=0 then againg fifo.read=remaining elements).and each time loop has been interact to host vi with global varibales.those global variables data update from normal time loop.can anybody suggest that this procedure is right or not.if my problem is not much clear i will again explaing my query with snapshot of my application.
Pratima
*****************Certified LabView Associate Developer****************************

You wouldnt need to allocate memory separately on your RT Controller for the FIFOs. You need to create a FIFO under your FPGA target and use the FPGA interface VIs in your RT VI to access the DMA FIFO. You would need to use the FPGA interface invoke method VI to access your DMA FIFO.
As for the other questions, I would recommend you to create a separate post the RT section of LabVIEW so that you can get a faster response to your questions.
I hope this helps!
Mehak D.

Flexrio FPGA dma and dram simulation

I have a pair of Flex RIO 7966r boards where I am trying to perform DRAM to DMA transfers. Each FPGA uses both banks of DRAM. One bank for capturing Camera Link frames, the other bank for capturing sub-frames from within each frame (And performing some processing on the sub-frame data).
Each DRAM bank is written into from their own target scopes FIFOs.
Each DRAM bank is read into their own target-to-host DMA FIFOs.
When only one side is operating or the other (Capturing sub-frames by themselves or full frames by themselves) everything flows nicely. But when I capture both at the same time, there appears to be some sort of contention in the DRAM (I suspect from the DMA engine). Since I am simulating all of this, I would like to ask if anyone has the detailed descriptions of the DRAM interface signals below? These are generated by LabView but I have found no explanation of what they mean in any documentation.
Also, in the simulation build, there is obviously a DMA simulation. But from within the simulator, I can find no signals related to the FPGA based DMA FIFOs or the simulated DMA transfers. All I can infer about the DMA transfers is the effect on the DRAM above. The DMA FIFO is being populated directly from the DRAM (Yes, this is a highly modified variant of the 10 tap cameralink (with DRAM) example from the NI-1483 examples).
Does anyone know how I can see the DMA bahavior from within a simulation? This would most likely allow me to see exactly why the contention is taking place.
Thanks!

Hey xl600,
I'm not immediately sure how to have ISim display the DMA Engine behavior, but I'll see if I can I dig anything up for you. I've come across a couple of other users encountering issues with FIFO signals appearing in ISim over on the Xilinx forums, so it might be worthwhile to post there as well in case it happens to be due to ISim itself.
Regards,
Ryan

Issue with fixed point number output from 9219 module for full bridge measurement (cRIO/FPGA)

Hi,
I have a question regarding the fixed point output acquired from a 9219 module (in FPGA on a cRIO) when setup to acquire a strain measurement (full bridge).
Software: Labview 2009
Hardware: cRIO-9012 (NI-RIO 3.2.1), NI-9219 module
The 9219 module is configured in the project as follow:
Ch0: Full-Bridge +/- 7.8mV/V
Ch1: Voltage +/- 4V
Ch2: Voltage +/- 15V
Ch3: Voltage +/- 60V
The calibration mode is 'Calibrated' so the FPGA outputs fixed point numbers.
My issue is that the precision of the fixed point number for Ch0 (strain) is "(fixed point <+/-32,-1>[-2.5e1,2.5e1]:1.16e-10)", which indicates that the fixed point number is a value between +/- 0.25 and not the +7.8mV/V as I expected?
The fixed point number does not change in precision whether the range for the strain measurement is set at +/- 7.8mV/V or +/-64mV/V (the two available options).
As the fixed point number doesn't change precision I'm assuming that changing the range of the strain measurement changes the resolution of the acquired number? And as such I will need to perform additional scaling on the fixed point number to convert it to the expected range?
There is no mention of scaling of the voltage or strain measurements mentioned in any documentation or examples, with the only scaling example provided for the thermocouple measurements.
Any help/clarification is much appreciated.
Regards,
Mike

Hello Mike,
Hopefully I can help clarify some of the behavior you are seeing.
My issue is that the precision of the fixed point number for Ch0 (strain) is "(fixed point <+/-32,-1>[-2.5e1,2.5e1]:1.16e-10)", which indicates that the fixed point number is a value between +/- 0.25 and not the +7.8mV/V as I expected?
For calibrated values on the FPGA VI, the returned data is a Voltage measurement, not a directly calculated strain value. Based on the specified ranges for the 9219 in a Full bridge configuration, 250 mV will encompass all possible input values, at the module provided excitation (2-2.7V dependent on the sensor gage resistance).
The fixed point number does not change in precision whether the range for the strain measurement is set at +/- 7.8mV/V or +/-64mV/V (the two available options).
As you may notice from the fix-point definition, the fixed point data contains 32-bit precision which is larger than the acquired precision of 24-bits provided by the 9219. The fixed point data-type is coded to accept input encompassing both the range and precision of the instrument; such that, no additional coercion of the input data values is required based on user-defined software settings, i.e. the bridge sensitivities +/- 7.8mV/V or +/-64mV/V.
As the fixed point number doesn't change precision I'm assuming that changing the range of the strain measurement changes the resolution of the acquired number? And as such I will need to perform additional scaling on the fixed point number to convert it to the expected range?
The documentation does not clearly define that by varying the discrete levels of strain input (+/- 7.8mV/V or +/-64mV/V) the range of the ADC on the module is also adjusted. I am working to follow up further on this topic, to provide a clarification on the module documentation. As for scaling, the voltage values acquired regardless of the ADC resolution will still be related strain via the bridge sensitivity. The resolution of the ADC will simply define the smallest measurable change in the strain value.
There is no mention of scaling of the voltage or strain measurements mentioned in any documentation or examples, with the only scaling example provided for the thermocouple measurements.
For converting the acquired voltage values to a strain measurement, I would recommend the documentation linked here for a detailed explanation on strain calculation. Often, users will forward the acquired voltage data as fixed point values through a DMA FIFO to the RT controller on the Compact RIO; such that, they may handle conversion from voltage to strain using floating point math in real-time.
I hopes these responses provided a bit of clarity. I will continue to work to provide additional information on the 9219 specification information. Please post back any further questions.
Cheers!
Edit: Forgot to add the link.
Message Edited by Pcorcs on 04-14-2010 04:55 PM
Patrick Corcoran
Application Engineering Specialist | Control
National Instruments

Using ALE to synchronize Variant Configuration data from Production to Dev

SAP Gurus,
We are trying to move away from opening our production environment every time with need to add new Variant configuration for products.
In order to do so, we need to ensure that our development and staging systems are in line with production LO-VC data. We have been looking at a possible ALE solution but I would like to get other suggestions.
Any thoughts you may have with regards to either pros and cons of ALE, or another solution we may have overlooked. If your clients are transporting Variant Configuration to production, what method are they currently using to ensure data consistency between environments.
Our landscape currently has two production environments for two separate business lines but both use LO-VC therefore we would like to standardize the process.
Thanks and Regards,
Kevin Webb
SAP SD Senior Consultant

Hi Webb,
General its a complex process to transport VC but for system consistency you can:
1. do the changes Manually in each system
2. Use ALE idoc process to transport.
But ALE transport generally used for fresh VC transport, if the VC already present in transporting system, it may cause inconsistency. Hence if you want to transport some changes then I can suggest you to do MANUALLY.
But if you are transporting VC freshly in each system, go for ALE.
try and revert

ALE error - variant LOGSYS does not exist?

In trying to setup ALE within SAP (ECC 5.0) to send a material master IDOC from the ERP to XI. I followed the ALE Quick Start guide and several other resources on the net including IDOC Cookbook and others. When I try to select transaction BD10 (Send Material Master), it returns the following error:
Variant LOGSYS does not exist
The long text is:
Variant LOGSYS does not exist
Message no. DB612
Diagnosis
You selected variant LOGSYS for program RBDSEMAT.
This variant does not exist.
Procedure
Correct the entry.
In trying to narrow down the problem, I created a minimal scenario of just sending the MATMAS IDOC from one client to another on the same system and I get the same error.
My first thought was the logical systems for the two
clients were not setup correctly, but they seem okay. I'm using the 'PRODUCTION' logical system that came with the IDES version we installed (client 811) and trying to send to a new client I setup as logical system VM1CLNT300 (client 300) on the same system.
RFC Destinations test okay, partner profiles, ports, and the distribution model seem okay.
Googling for that error message above produced nothing that I could get an answer from. Any ideas?
Thanks,
-tim

Yes, both logical systems are there. Additionally, each
client has been set to the appropriate logical system:
client 811 -> PRODUCTION logical system
client 300 -> VM1CLNT300 logical system
-tim

ALE Error + Mass deletion of variants for Reports

Hi,
I have two questions
1- is there any transaction in SAP, which delete the mass variants for reports for all users?
2- I am getting an error An Idoc without a message type was passed to the ALE layer.
I have already check file port is set up correctly and I am passing message type HROT_BRM.
This also happen in previous test, as user does not have the proper authorization, so I assign the authorization and ran it. It worked.
However, this time a user has the authorization and still the error messaging is coming. Am I missing something?
Waiting
Bye

There are some function modules like "KYVA_REPORT_VARIANTS_DELETE or get user variants "RM_GET_VARIANTS_4_REPORT_USER".
- is there any transaction in SAP, which delete the mass variants for reports for all users?
2- I am getting an error An Idoc without a message type was passed to the ALE layer.
I have already check file port is set up correctly and I am passing message type HROT_BRM.
This also happen in previous test, as user does not have the proper authorization, so I assign the authorization and ran it. It worked.
However, this time a user has the authorization and still the error messaging is coming. Am I missing something?

Distributing Variant BOM (bills of material) with ALE

Hi all,
we need to distribute variant BOMs from one client to another in the same system. But in SAP standard it's not possible to distribute variant BOMs with ALE.
Has anyone an idea, how we could manage it?
Best regards!
Heike

Have you tried message type : MATERIALBOM_CREATEBOMGROUP ,but i think you need to create custom program.
Anurag

ALE Master Variant data distribution

Hi all,
I m working on ALE and I want to transfer data from System1 to System2.Data includes all related to material classification i.e class,characteristics,charistics values,material,variant tables,configuration profiles,dependencies,etc.
I want to transfer material variant.So I m using transaction BD10 and message type MATMAS02.The material goes with the entire data of material variants except for the plant-specific configuration details on the MRP3 view.
Do i need to change the message type or the transaction that i m using??
Kindly reply back soon.
Regards,
Ankit

Hi Ankit,
first of all, welcome to SDN! Sorry, this is the wrong forum for your question, the experts in the <a href="https://www.sdn.sap.com/sdn/collaboration.sdn?node=linkFnode2-3&contenttype=url&content=https%3A%2F%2Fforums.sdn.sap.com%2Fforum.jspa%3FforumID%3D50">ABAP forum</a> will probably help you.
Regards, Stefan

Variant Configurator and ALE

Has anyone had any experience with using ALE to transport all aspects of the Variant Configurator set-up to another SAP instance? We had planned to go this route, but have had people tell us that they wrote custom programs to download data from one instance and then use BDC's to load them in the new system. Is there a problem with using ALE for VC set-up data or anything we should be aware off?
Regards.

Hi Cynthia,
I have done this in the past. Definitely ALE is the way to go over BDC's etc.
The only thing you have to watch is the sequence that you send the data in. For example you must send dependency function module definitions before you can send any dependencies that call those functions. Otherwise you get an Idoc failure.
Where you get circular references (for example you have a characteristic which has a dependcy attached to it, and the dependency actually refers to the characteristic by name) then the best thing is to set the status of the dependency to deactivated, ALE it to the target system (syntax check will pass because its deactivated), ALE the characteristic, set the status back on the dependency, and then ALE it again.
Apart from occasional circular references, however, it works really well.
Another thing to watch is that when you set up your ALE distribution model, that you consider the possibility of concurrent development and ALEing between systems. For ease of administration, we set up our DEV system as the source for both QA and for PROD (rather than having DEV as source for QA and QA as source for prod) but this means that you shouldn't do any development on objects currently in QA as the latest changes will be ALE'd from DEV to PROD.
I think the general sequence of ALEing that worked the best was:
1. Characteristics
2. Function module definitions
3. Dependencies
4. Configuration profiles
I feel I have forgotten something there, but I guess you get the idea.
Last thing, you can't ALE the configuration profile user interface. So if you have designed your own layout for the characteristics (with tabs, and userexit buttons etc.) you have to recreate these manually in each environment. Not much fun when you have 10+ clients in your landscape. I kept meaning to write a program to handle it but, time got away from me.
Finally, you have to ask yourself why SAP didn't treat all this stuff as configuration though, and allow you to migrate using change requests. Wouldn't that be nice!!!
Hope that helps.
Cheers,
Brad

ALE Variant Configuration

Hi , I am not having much idea about ALE , I am some problems in it.
When running the ALE to move the Variant Configurator from Client 130 to other Clients, I am running into the following issues.
1)it does not copy the dependencies within the Configuration Profile. It copies the dependencies themselves and the profile, but when you go into the profile, there are no dependencies listed. An example is: For SLCase in Client 130, go into the profile and you can see several dependencies there, but when you go into Client 110.
2)it does not always update the dependency when it already exists.
3)it does not update the Table structure when the table already exists.
4)it does not update the data in the table when the table already exists (this oculd be because the structure of the table changed in Client 130, but didn't update the structure in the other clients (as in #3 above).
5)it does not update the Default checkbox on the characteristic when the characteristic already exits.
Thanks.
Ankesh Jindal

Hi
Check SAP note 10745. It has details how to transfer classification data from one client o another by ALE. Hope it will help to solve your problem
Regards
Antony

ALE Transactional and VA01 Again

Dear Friends
Some of you gives me good links fordocumentation but after customizing and done a lot of thing I can't have an automatic IDOC when I create a sale order via VA01.
As it was explain in the documentation I have written a module function and done a lot of thing but nothing appens.
With an user exit SAPMVFZZ I can create the IDOC and it well sent to the good port. So BD64 is good.
==========================================================
Table NAST is not filled up when I create an Sales order.
==========================================================
Here after a resume of what I heve done.
If you have a good idea and may be you know why no IDOC when I create an Sales order, you are wellcome.
1. OUTBOUND PROCESSING
1.1. Create IDoc type (WE30) Client independent
IDoc type ZSALES01
To create the IDoc type, follow these next few steps:
Enter transaction WE30 (ALE -> Extensions -> IDoc types -> Maintain IDoc type)
Type in ZSALES01 and click on Basic IDoc type, click the Create icon
EC1VBAK (father) and two sons
EC1VBAP Enter EC1VBA2
1.2. Create message type (WE81) Client independent
To create a new message type, follow these next few steps:
Enter transaction WE81 (ALE -> ALE Development -> IDoc -> IDoc types Development -> WE81 logical messages ZORDER01
Save and exit.
1.3. Link message to IDoc type (WE82 & BD69) Client independent
To link the message types to the IDoc type follow these next few steps:
Enter transaction WE82 (ALE -> ALE Development -> IDoc -> IDoc types Development -> WE82 IDoc Type for message
Enter the message type ZORDER01 and the Basic IDoc type as ZSALES01
Save and exit the result is set in SAP table EDIMSG
1.4. Transaction NACE / NACT
Creation of OUTPUT TYPE Z001 for application V1.
Access sequence 004 = SalesOrg/Sales Order Type
Default Value
Dispatch time send immediately
Transmission Medium Distribution ALE
Time
Timing 2 is set off Job and time entry
Condition table 5 has been generated.
Consistency check for output control all is OK
Assignment output type to partner function In the IMG
Creation of Procedure Z00001 OUTPUT FOR IDOC ZSALES01 for Usage B and application V1
The control procedure: control type z001 requirement 2 (Order confirmation)
1.5. Assign Output type to partner function
Z001 A SP (sold to party)
Transaction V/43 assign Output determination Procedure
Allocate Sales Document header
Sale doc type OR Output procedure Z00001 Output type Z001
1.6. Transaction WE20
Partner profile
Partner number 0000000001
Partner type KU
Partner role SP
Message type ZORDER01
Partner status Actif
Output options
Port A000000002
Pack size 1
Transfer IDOC Immediate YES
Cancel processing after syntax error YES
IDOC Type Basic type ZSALES01
Message control
Application V1
Process code ZVA01
Message type z001
Result of checking (program RSECHK07) with partner 0000000001 and partner type KU: All OK
Table EDP13, table EDP12 message control are well filled up.
A module function is created with the good parameters ZSALESORDERIDOC
The process code point to a function ZSALESORDERIDOC (transaction WE41) Outbound process code
Process code ZVA01 Linked to module function ZSALESORDERIDOC processing with ALE service
Function module version 3.0
Table EDIMSG Output Types and Assignment to IDoc Types give
Message type ZORDER01 Basic type ZSALES01 release 50A
Enter transaction BD69 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Assign message type to IDoc for ALE)
Enter the message type ZORDER01 and the Basic IDoc type as ZSALES01
1.7. Maintain object type for message type (BD59) Client independent
Type in your message type ZORDER01 and press enter
Enter your object type, KUNNR (We need to use the customer as a filter object), the segment name where KUNNR resides, EC1VBAK, a number 1 for the sequence followed by the actual field name KUNNR
1.8. Configuring the Distribution Model BD64
This task is performed on your ALE reference client.
Manual Configuration (BD64) Client dependent
Create a new model. (Create model POCALE)
POC ALE to send Outbound Idoc POCALE
Choose the receiving systems to which the sending system must forward message type ZORDER01 to.
We have generated the model view after creation.

He Ferry,
I try your checking and with VA02 -> Enter <sales order> -> Enter -> Extras -> Output -> Header -> Edit.
The system propose me Z001 when I click on OUTPUT TYPE (F4).
I have selected Z001 and submit. The following message comes "Processing program missing for output Z001 " ==> "No processing program is defined in table TNAPR for output type Z001 (transmission medium A) in application V1."
In transaction NACE for V1 and OUTPUT type, in TAB Processing routine I can add one program and Form routine.
The module function created zsalesorderidoc has generated a program (SE38) ZSALESORDERIDOC===============FT
Is this one I have to use or I have to create a special one? If I have to create one may I have a model?
In the program ZSALESORDERIDOC===============FT we have these FORM.
FORM EXISTENCE_CHECK CHANGING VARIA.
FORM FUNCTION_CALL.
FORM CLEAR_DATA.
FORM CLEAR_TABLE.
FORM DELETE_LINE USING KEY INDEX.
FORM INIT_EXCEPTIONS USING NAME.
FORM PARAM_ACCESS_TYPES USING KEY DEST P_MODE P_UPPER.
FORM PARAMETER_SET USING NAME DIRECTION VALUE.
PERFORM CB_CALLBACK_VALUE_SET(SAPLSEUJ)
 USING VALUE
 CHANGING %_IOBJECT.
FORM PARAMETER_GET USING NAME DIRECTION
 CHANGING VALUE
 OLD_VALUE.
FORM PARAMETER_TABLE_SET USING NAME VALUE.
FORM PARAMETER_TABLE_GET USING NAME
 CHANGING VALUE.
FORM PARAMETER_DESCRIBE USING CBPROG
 NAME.
FORM PARAMETER_CONTAINER TABLES LCONT STRUCTURE SWCONT
 USING NAME
 DIRECTION .
FORM TABLES_CONTAINER TABLES LCONT STRUCTURE SWCONT
 USING NAME
 DIRECTION.
FORM SET_VARIABLES USING KEY VALUE.
FORM GET_VARIABLES USING KEY
 CHANGING VALUE.
FORM PARAMETER_READ_INPUT USING NAME
 KEY
 CHANGING VALUE.
FORM PARAMETER_READ_OUTPUT USING NAME
 KEY
 CHANGING VALUE.
FORM PARAMETER_COMPARE USING NAME
 CHANGING VALUE.
FORM EXPORT_IMPORT_MEMORY USING SEL KEY STRUCTURE EXPORTKEY.
FORM EXPORT_IMPORT USING SEL KEY STRUCTURE D102N_EXPORTKEY.
FORM GET_EXCEPTION_DIFFERENCE
FORM COMPARE_DATA
 TABLES DIFFERENCES STRUCTURE UNTERSCHIED
 USING FIELD
 CHANGING RETCODE.
Thank you for All
Best regards
Henri

Generation Partner Profiles from ALE Distribution Model

Hi ABAP/EDI experts,
I am a trainee. I am getting training from Pvt consultancy. I am working on SAP Demo systems.
I am trying t generate an IDoc using ALE method.
IN SALE window, I created two logical systems,ZVK_SS_800 and ZVK_SS_820. I assigned them to two clients 800 and 820 respectively.
In SM59 i created an RFC connection ZVK_RFC004 of type 3. Here I gave the client Number as 820. ( I'm not sure what to give)
In BD64, I created an ALE Model and added the message type MATMAS with Sending and Receiving Logical systems.
From the Environment drop down menu , selected generate partner profiles and executed with defaults checked. ( Transfer IDocs Immediatley and Trigger Immediately).
I got the following log.
Log For Partner Profile Generation:
Partner:
In Green Color
Partner ZVK_SS_800 as partner has been Created ( Sending System)
Partner ZVK_SS_820 as partner has been Created (Receiving System)
Port:
In Red Color
Port Cloud not be Created
RFC destination ZVK_SS_820 not specified for system ZVK_SS_820
Enter the RFC destination and Restart the generation.
Please help me to fix this probelm.
Any kind of Help will be surely rewarded.
Thanks,

From SM59, you can Test your RFC Connections between Clients. I would do this from Client 800 and test the Connection to Client 820. If that checks okay, I would then try SM59 on Client 820. Check the RFC Connection from Client 820 to Client 800. Be sure you have your Logical Systems defined on Both Clients. You can also double click on your Error Message to see if there is a Long Text Available that might give you further information as what needs to be corrected. I am not an Expert in this area, but have setup several ALE Models for my Variant Configuration without any problems. If you could include your EMail Address on your Business Card I could EMail you my instructions. Your Basis person may also be able to help you based upon your Error Message.

Ale Idoc

I am sending an idoc from one system to another system, in the receiving system idocs status is 64.
its not posted.
In WE20 partner profiles, I have assigned a process code to the message type CHRMAS(characteristic master) in inbound parameters for
the corresponding logical system
Again I have assigned that procees code to FM "IDOC_INPUT_CHRMAS" with option as "processing with ALE" and type as "processing by function module".
I have checked "Trigger by background program" for processing by fun module.
When i tried to push the idoc thro BD87, it works successfully.
Could anybody help in this, what other check should i need to do so that idoc posts automatically.
Thanks in advance,
Ponraj.s.

Hi,
For the path of Scheduling Idoc processing inreceiver system :
Go to transaction SALE ->Modeling and Implementing Business Processes -> Partner Profiles and Time of Processing -> Scheduling IDoc Processing in Receiving System.
Define Variant & schedule a job.
Thanks.
Mark points if helpful.

¿Cómo sincronizo varias señales en un DMA FIFO?

Similar Messages

Maybe you are looking for