RS232 input module problem

Hello everyone,
I am trying to read and record data from a balance using DASYLab.
Dasylab and Windows device manager detect the right COM port, although sometimes I cannot see the connected port in command prompt (using command "mode").
Everything looks all right, but I don't get any data in RS232 input channel.
I tried to monitor the interface module even while requesting data (using 2WOW\f), but no success!
I appreciate your help and suggestions.
Solved!
Go to Solution.

This is the setting that you want, I think
AUTOPRINT PC (Continuous data output)
The setting AUTPRINT PC is in the PRINTER-routine, and there it can be selected or deselected. When
AUTOPRINT PC is active the actual weighing values will be sent continuously via the RS 232 interface.
The command that you're sending should be
"2WOW\r\n" not "2WOW\f"
But I'm not sure what the command is. The book says this
t Tare.
w a weighing value (or unstable) is sent via RS 232 interface.
s a stable weighing value is sent via RS 232 interface.
If the balance receives the command w or s, it acts without printing delay.
So, I would send
s\r\n
If you have the vendor's software, you can use a RS232 port monitoring package to see what that software sends and receives.
this is the package I like to use.
http://technet.microsoft.com/en-us/sysinternals/bb896644
- cj
Measurement Computing (MCC) has free technical support. Visit www.mccdaq.com and click on the "Support" tab for all support options, including DASYLab.

Similar Messages

RS232 Input and Output in the same time

Hello
I have problem with rs232.
I read information from my power supply by RS232 Input:
Expected string: 1923456789<CR>OK<CR>
Channel 0
Measurement data request: GETD00\r
Measurement data format: 4a
Channel 1
Measurement data request: (empty)
Measurement data format: 4a
Channel 3
Measurement data request: (empty)
Measurement data format: 1a4x
Sample interval: 0.20s
The date are readed correctly until I don't send other string by RS232 Out.
Output [a]\r (VOLT00123)
After sending string Power Supply return data OK<CR>
After sending string by RS232 Output the data form RS232 are readed incorrectly.

In the Output format, you need to skip the OK<CR> so it doesn't confuse the input parsing.
The Help says the following
If there is the need to wait for the Response String of the external device the following string has to be attached to the format string.
‘\#x' (x=1-999)
That ensures that no other module will address the interface. If the response is received the defined number (x) of characters will be skipped.
So, the output string should be
[a]\r\#3
That will send the command, then wait for the OK<CR> before handing control of the serial port back to the RS232 Input module.
- cj
Measurement Computing (MCC) has free technical support. Visit www.mccdaq.com and click on the "Support" tab for all support options, including DASYLab.

Input help problem

Current scenario i have an input textbox attached to an input help. A user needs to find a particular table, but do not know the exact name. The user only knows that the table starts with 'PA'. So, we need to filter all the tables that start with 'PA' for e.g. 'PA0001' and return it to the user for selection.
The problem now is that i cannot retrieve the input string given by the user for e.g. 'PA'.
Does anyone knows how to solve this problem?

This is my codes. The string 'PA' is not hard coded. We need to read what the user input in the textbox. For example it can be PA, PB, PC or any other input.
REPORT ZMEIHUI_METADATA.
*& Global Declaration
DATA: IO_TABLEA(40) TYPE C,
      IO_TABLEB(40) TYPE C,
      VALUE(40) TYPE C,
      VALUE2(100) TYPE C,
      PROGNAME TYPE SY-REPID,
      DYNNUM TYPE SY-DYNNR.
*& Processing Blocks called by the Runtime environment
START-OF-SELECTION.
CALL SCREEN 8000.
MODULE STATUS_8000 OUTPUT
MODULE STATUS_8000 OUTPUT.
SET PF-STATUS 'UI'.
SET TITLEBAR 'TITLE'.
ENDMODULE.                    "STATUS_8000 OUTPUT
MODULE USER_COMMAND_8000 INPUT
MODULE USER_COMMAND_8000 INPUT.
CASE SY-UCOMM.
    WHEN 'BACK'.
      LEAVE PROGRAM. "need to change to the previous screen!!!"
    WHEN 'EXIT'.
      LEAVE PROGRAM.
    WHEN 'EXECUTE'.
     " PERFORM VALIDATE_REQUIRED_FIELD.
ENDCASE.
ENDMODULE.                    "USER_COMMAND_8000 INPUT
MODULE F4_INPUT INPUT
MODULE F4_INPUT INPUT.
TYPES: BEGIN OF VALUES,
    TABNAME TYPE DD02T-TABNAME,
    DDTEXT TYPE DD02T-DDTEXT,
END OF VALUES.
DATA: F4_VALUES TYPE TABLE OF VALUES.
PROGNAME = SY-REPID.
DYNNUM = SY-DYNNR.
VALUE = IO_TABLEA.
CONCATENATE VALUE '%' INTO VALUE2.
SELECT DISTINCT TABNAME DDTEXT FROM DD02T
    INTO TABLE F4_VALUES WHERE TABNAME LIKE VALUE2.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
    EXPORTING
      RETFIELD    = 'IO_TABLEA'
      DYNPPROG    = PROGNAME
      DYNPNR      = DYNNUM
      DYNPROFIELD = 'IO_TABLEA'
      VALUE_ORG   = 'S'
    TABLES
      VALUE_TAB   = F4_VALUES.
ENDMODULE.                    "F4_INPUT INPUT

OPC input module unknown upon worksheet startup. No sound card installed error.

Hi all,
I am on v11.00.00 and have two problems.
1. Upon startup, I get a 'no sound card installed' error despite having already selected the sound board from the Measurement tab. I've already checked the Windows Device manager and verified that the sound card is working OK.
2. Upon loading a worksheet, I get a module unknown error - in this case an OPC Input module for a DT9837B sound and vibration measurement box. I've already installed the DAQ OEM drivers.
Can anyone tell me what's wrong?
Thanks...

You may need to edit the sounddrv.ini file to change the device number.
The default file is this
[SETUP]
PlayWelcome=1
DisplayNoSoundCardMsg=0
InputDevice=0
OutputDevice=0
BitsPerSample=16
LeftVolume=50000
RightVolume=50000
SameVolume=1
Change InputDevice to =1
File is in the Public users folder (Documents and Settings\All Users on XP), in the DASYLab\11.0.0\Eng folder.
OPC and DT have nothing to do with each other. They may be conflicting, however, since both are add-on drivers. If you edit the DASYLab.ini file (same location as the SoundDrv.ini file), put a semicolon character ";" in front of the line that loads the OPCC.DLL.
If the line is missing (i.e., the DT installation obliterated it), change one of the other lines to be DLLx=Opcc.dll. That will add it back in.
Ensure that the DT driver is loaded. Both of these are in the [EXTEND] section of the file.

NI SPDIF Input Module

Has anyone tried to use the NI SPDIF Input Module? I already checked the document, but still, I am having troubles making it work. It doesn't read a 48 KHz signal with a 7831R board.
Thanks for any suggestions.

I have two suggestions to try.
In regards to developing your own SPDIF reader; when you only measure the pulse lengths you get the proper readings, but as you add more code to the loop the readings changes and become incorrect. This is most likely a result of the extra code slowing down the loop and causing it to not run fast enough to read each pulse. Using a regular While loop in LV FPGA, each function block you use takes up at least one FPGA clock cycle. In addition the While loop has an overhead of two FPGA clock cycles. So assuming you have a While loop with 5 consecutive functions it will take 7 clock cycles to run each iteration of the loop. If you were to use this loop to measure the pulse length it would give you a measurment with a resolution of 7 ticks, i.e. the pulse length would be 7, 14, 21, 28, etc. As you add more code to this loop the length of each iteration increases and the resolution of the pulse width decreases. In order for us to adequately measure the width of the pulses in the SPDIF signal we need to have a loop iteration time of less than 6 or 7 clock cycles (about half of the shortest pulse we want to measure). This is the reason why the original SPDIF code is set up in three different loops and the first loop that measures the pulse width is kept very simple. It also uses pipelining to further reduce the time of each iteration and we compile the FPGA for a 80 MHz clock rate to get more clock cycles per pulse. I think in your code as you add the Case structure and additional code, you are increasing the loop time above the necessary limit.
One 'easy' solution to this problem is to use the Single Cycle Timed Loop (SCTL) instead of the While loop. This loop is processed differently by the compiler so that all of the code inside the SCTL is executed in one clock cycle. (The SCTL was not available in LV FPGA when the original SPDIF code was developed, otherwise we would have used it then.) So in the updated SPDIF code we use the SCTL and can include all of the SPDIF processing in one loop. There are some limitations on the code that can be included in a SCTL. Information about the SCTL and optimizing FPGA code can be found in this prsentation (Advanced FPGA Programming). I think if you convert your code to the SCTL (right click on the While loop and chose Replace with Timed Loop) you should be able to measure your signal correctly.
Getting back to the SPDIF code I included on my last post. This code does work correctly on my end with a SPDIF signal coming from a Soundblaster sound card. This signal has two raw audio channels with 20-bit data per channel. The 4 AUX bits in the SPDIF packet are not used. I have logged the data to file and can load the file using the Reader VI included in my last post. To play the sound back on a regular sound card in LabVIEW I have to resample the data to 44.1 kHz and then use the upper 16-bits of the 20-bit audio signal. I'm attaching a sample file of logged data on this post that you can open and play back using Read SPDIF Data File.vi.
Is there a chance that the audio data in your signal is formatted differently? Could it be using 5.1 or 6.1 encoding with DTS or Dolby?
Christian Loew, CLA
Principal Systems Engineer, National Instruments
Please tip your answer providers with kudos.
Any attached Code is provided As Is. It has not been tested or validated as a product, for use in a deployed application or system,
or for use in hazardous environments. You assume all risks for use of the Code and use of the Code is subject
to the Sample Code License Terms which can be found at: http://ni.com/samplecodelicense
Attachments:
sampledata.zip ‏2987 KB

How do I acquire multiple signals in the NI cDAQ 9172 using 2 analog input modules?

Hi everyone,
Is anyone familiar with using the NI cDAQ 9172? This is my first time using it and I am not sure what exactly I am doing wrong... Alone with a NI 9233 analog input module, it works great. I can grab my 4 signals from each channel and go. However, when I add another analog input module to the mix, it gets an error. It looks like it is reading only one and not the other. It bombs at one of the DAQ start task and read task.
Basically, the block diagram is just a double of the one 9233 working alone. Is there something needed for input to make the 9172 working? Any ideas?
Any help is much appreciated. Thanks!!

Hi Jud,
Both threads are correct. The cDAQ-9172 has a single analog input timing engine, so both of your analog input modules will need to be in a single task. The other VI you referenced shows one analog input task (with channels added from two modules) as well as an analog output task. Analog output has a separate timing engine from analog input, so both of those can run in parallel independent tasks.
The beginning of this thread is a good example; a single DAQmx Create Task followed by a DAQmx Create Virtual Channel for channels from each module. Also, Getting Started with NI-DAQmx will give you the fundamentals for data acquisition, though I don't know how many of their examples use CompactDAQ.
Regards,
Kyle

"Chassis Temperature" in Analog Input Module for FPGA (cRIO-9201)

I have just gotten my cRIO with a analog module (9201) and a digital output module (9472).
When I place an Analog Input Module on my block diagram and double click it, I can choose from the following inputs:
Channel 0 through Channel 7
AND
Chassis Temperature
I have tried to find any documentation for this "Chassis Temperature" but so far without success.
If I read this input and feed it straight to an indicator, I get values in the range of 120 to 150.. Now, without more information, this number is rather useless. Does anyone know how to transfer this data to a temperature (either in the Celcius scale or the Fahrenheit scale)?
Thank you!
Project Engineer
LabVIEW 2009
Run LabVIEW on WinXP and Vista system.
Used LabVIEW since May 2005
Certifications: CLD and CPI certified
Currently employed.

I still did not find any documentation for this "feature" but I lucked out and found the following:
in the folder: \labview 7.1\examples\FPGA\CompactRIO\cRIO-910x\
you should have a file called:
cRIO-910x support files.llb
in this there is a convert to temperature vi.
To get the raw data as a temperature, it looks like all you have to do is divide the binary data by 4 and the answer will be in Celcius.
Project Engineer
LabVIEW 2009
Run LabVIEW on WinXP and Vista system.
Used LabVIEW since May 2005
Certifications: CLD and CPI certified
Currently employed.

How to use both digital and analog input modules in the same worksheet - MCC USB1208LS

Dear all,
Hi, I am Imran. I am using MCC USB1208LS. I have created the worksheet using digital input module as below and able to execute (run).
But when i add another analog input module in the same worksheet and executes, An error Message pops-up as in the below image
I have connected temperature sensor sognal to the analog input of USB1208LS. When using analog input alone in the worksheet, it indiates the actual values.
is any black box solve? please guide me. I am attaching in images
We already placed a purchase order for USB1208FS. Will it sort out my issues?.
Thanking you,
Imran Mohamed.
Attachments:
present worksheet digital input only.JPG ‏67 KB
with analog input module.JPG ‏81 KB
error menu.JPG ‏77 KB

Hello Imran,
the USB-1208LS is not capable of running concurrent operations such as an analog input scan and ANY digital Ins, Outs, counter reads, or analog outs. In Dasylab, the 1208LS is scanning, and nothing else from that particular device can be requested of it while that is happening.
Yes, using the 1208FS will resolve some of these issues.
Please refer to the ULHELP.CHM file installed on your computer in c:\program files\measurement computing\daq for details on this issue, et al.
also I recommend you send your MCC/DASYLab requests for support to [email protected] as MCC staff (that includes me) does not normally monitor NI's Developer Zone.

Will Analog Instruments ADXL330 triaxial accelerometer work with the SCXI-1531 input module?

I have an SCXI-1001 chassis and will soon be purchasing an accelerometer input module (SCXI-1531). I'm also investigating possible accelerometers to buy. Does anyone know if the the Analog Instruments ADXL330 accelerometer can be made to work with the SCXI-1531? Here is a link to the Analog Instrument's page about the device:
http://www.analog.com/en/sensors/inertial-sensors/adxl330/products/product.html
Thanks!

Hello,
The output voltage and current levels are within specification of the module, the only concern I have is interfacing between the IC chip and the BNC connections on the 1531. If you have a way to effectively connect the pins to BNC connectors and connect that to the module, then it should work. Are you using the module's excitation source as well?
Kyle A.
National Instruments
High Speed Digital I/O Product Support Engineer - R&D

Using NI 9214 16-Channel Thermocouple Input Module

Hi,
Now that we have the NI 9214 with NI TB-9214, 16-Channel Thermocouple Input Module with
Terminal Block how do we go about using it?
It was not obvious as to what or where I get the instruments drivers for this, so any direction would be good?
Also I have the CVI sample code, ContThrmcplSamps-IntClk.prj, are there any others about?
Thanks
Simon

Hi Simon,
Minimum driver requirements for all modules can be found using the software support tool and selecting the module you are interested in, in this case C Series modules and accessories>:NI9214.
Link to Software Support Tool: ftp://ftp.ni.com/pub/gdc/tut/crio_software_versions.htm
The latest NI-DAQmx driver version, is as above, the NI-DAQmx 15.0.1: http://www.ni.com/download/ni-daqmx-15.0.1/5353/en/ and the latest NI CompactRIO Device Driver is the NI CompactRIO 15.0: http://www.ni.com/download/ni-rio-15.0/5363/en/
I'd recommend having a look through the Example Finder (through LabVIEW>Help>Find Examples) in particular the "NI 9214 Getting Started.lvproj".
You could also try http://www.ni.com/examples/ to see if there is anything suitable available. The search can be narrowed using keywords and filtering i.e. Software>LabWindows/CVI
Hope this helps!
Rebecca
National Instruments Applications Engineer

Touchscreen xorg input module

Several touchscreen input modules (evtouch egalax etc) work fine in Ubuntu but not in Arch.
The error is:
(EE) module ABI major version (0) doesn't match the server's version (2)
(EE) Failed to load module "evtouch" (module requirement mismatch, 0)
(EE) No Input driver matching `evtouch'
I'm not sure what direction to take here as I'm not exactly sure about ABI and I'm not sure what server it's comparing to (xorg? kernel module?)
I've tried IgnoreABI but the system crashes so clearly there's an issue somewhere.
Can someone point me in the right direction?
Thanks!

OK, I seem to have this working now. Seems that all the touchscreen input modules that I've tried were not compatible with version 1.4 of the X server.
evtouch 0.8.7-3 seems to work and can be gotten from a Debian package.
http://packages.debian.org/unstable/x11 … ut-evtouch
The only file you really need from this package is evtouch_drv.so. Copy this file to /usr/lib/xorg/modules/input.
Set your xorg.conf to use the evtouch driver (there are many instructions around for this)
You may need to set up a udev rule so that your USB touchscreen has a known link and doesn't change every reboot (there are instructions around for this too.)

Batch input recording problem in MM module

Hi all,
i make zpabi to make recording to creat contract in me31k but when it arrived in line 16 do not complete recording
and not make new scroll.
can any buddy help me.

Hi,
As we already have std BAPIs for creating contract like, BAPI_CONTRACT_CREATE and BAPI_CONTRACT_CREATEFROMDATA, what is the need for going to a ZBAPI?
Remember that ZBAPIs will not be supported by SAP and if any screen seq changes with custom fileds etc, BDC will not work. Try to use std BAPI if possible.
Regads,
Ganga

Trans. ME32K. Batch Input. Problem in header versions with container

Hi all:
I've got a problem with the transaction ME32K.
The required action is meant to be changing the address delivery in the agreement position.
The bapi BAPI_AGREEMENT_MAINTAIN doesn't solve the problem because the field adrn2 is not present in this function module, so refering to other posts I've decided to implement a batch input.
The problem starts when I try to introduce REVOK and RSCOD in grid container in section header version. When I simulate the transaction ME32K with shdb the only code appearing is:
SAPLMEDCMV     0200     X     BDC_OKCODE     =GRIDENTER
                                                            BDC_SUBSCR     SAPLMEDCMV                              0100SUB0
SAPLMEDCMV     0200     X     BDC_OKCODE     =SAVE
     BDC_SUBSCR     SAPLMEDCMV                              0100SUB0
and then the values 'X' in REVOK and '0007' in RSCOD are not recognized.
How can I introduce the new version in header ?
Thanks in advance.
Jose Luis.

Hi Jose,
did you find a solution for your issue?
I have the same problem now.
Greets,
Valentin

IDOC: Incorrect function module problem

Hi,
I am working on inbound IDOC processing. I created an extension for an IDOC. I created custom segment & included it in the extension that I created. The Message type was also custom. (I merely copied an existing standard Message Type for some other purpose). I also assigned Function Module to Message Type & IDOC type. I have other necessary settings configured as required. The problem that I am encountering is as follows:
Incorrect function module IDOC_INPUT_SHPCPR called up
Message no. B1044
Diagnosis
The function module IDOC_INPUT_SHPCPR, which was called for the application input, was not able to process the IDoc. A possible cause is that the IDoc has wrong message type or IDoc type.
Procedure
Please check the message type assignment for the application function module in the ALE customizing.
Now to troubleshoot the above error, I made sure that I have an entry with FM. IDOC_INPUT_SHPCPR, IDOC Basic Type ,custom IDOC extension & custom Message Type. But even then I see the above error. This error appears as Status 51 for the test IDOC that I processed.
Can anyone please tell me how to solve this? Thanks in advance.

On line 49 of the function module :
* Loop through the IDocs' control records
LOOP AT idoc_contrl.
*   Check the IDOCs message type
    current_mestyp = idoc_contrl-mestyp.
    PERFORM idoc_message_type_check
                 TABLES   idoc_status
                 USING    idoc_contrl
                          mestyp-shpcpr
                 CHANGING subrc.
Perform looks like this ( in Include LV56IF0C...)
FORM idoc_message_type_check
          TABLES   t_idoc_status STRUCTURE bdidocstat
          USING    f_idoc_contrl STRUCTURE edidc
                   default_mestyp LIKE edidc-mestyp
          CHANGING subrc          LIKE sy-subrc.
IF current_mestyp <> default_mestyp.   " Here the variable default_mestyp has the value SHPCPR
    MESSAGE ID      msg-id             "Global variable
            TYPE    'E'
            NUMBER msg-nr_wrong_function    "Global variable
            WITH    current_mestyp     "message type
                    'IDOC_INPUT_SHIPPL'"Your function module
                    f_idoc_contrl-sndprt     "Sender partner type
                    f_idoc_contrl-sndprn     "Sender number
            RAISING wrong_function_called.
Again let me warn you that you will have to copy the entire function group V56I. Copying the function module alone will not help because there are many reusable subroutines in different includes of the function-pool.
regards,
Advait

Rfc functional module problem

hi
am created a rfc functional module program(se37) which receives the two input value from calling program and just add and it returns to the calling program(se38).
the program is executed successfully but the probs is the rfc functional module does not print it executable contents. the calling program does print its executable contents.
PLZ RESOLVE THIS PROBLEM
see the calling program and rfc functional module below
REPORT YSUSEX51.
PARAMETERS : I1 TYPE I ,
I2 TYPE I,
DEST1 LIKE RFCDES-RFCDEST DEFAULT 'NONE'.
DATA: RESULT TYPE I,
SYSTEMID TYPE SY-SYSID.
CALL FUNCTION 'Y_RFCMODULE' DESTINATION DEST1
EXPORTING
A = I1
B = I2
IMPORTING
C = RESULT
SYS = SYSTEMID
EXCEPTIONS
INVALID_DATA = 1
COMMUNICATION_ FAILURE = 2
SYSTEM_FAILURE = 3.
CASE SY-SUBRC.
WHEN 1.
WRITE: / 'NO DATA AVAIL'.
EXIT.
WHEN 2.
WRITE:/ 'CONNECTION COULD NOT BE ESTABLISHED'.
WHEN 3.
WRITE : / 'SYSTEM NOT AVAIL'.
EXIT.
ENDCASE.
WRITE:/ 'INSIDE THE CALLING MACHINE'.
WRITE: / RESULT.
WRITE: / SYSTEMID COLOR 7.
IN THE RFC FUNCTIONAL MODULE IT DOES NOT PRINT THE A ,B,C AND SYS VALUE,
FUNCTION Y_RFCMODULE.
""Local Interface:
*" IMPORTING
*" VALUE(A) TYPE I
*" VALUE(B) TYPE I
*" EXPORTING
*" VALUE(C) TYPE I
*" VALUE(SYS) LIKE SY-SYSID
*" EXCEPTIONS
*" INVALID_DATA
WRITE: /'INSIDE THE REMOTE SYSTEM'.
WRITE: / A.
WRITE: / B.
C = A + B.
SYS = SY-SYSID.
WRITE:/ C.
WRITE: / SYS COLOR 7.
ENDFUNCTION.
REGARDS
surender

Hi
Instead Of giving write statement inside a function module
write these statement where this rfc is called.
if rfc connection is established ,then
number will be printed.
otherwise not.
Dont forget to reward points
Edited by: neetu chhabra on Mar 10, 2008 12:14 PM

RS232 input module problem

Similar Messages

Maybe you are looking for