bit of banging with NOR-8451

Similar Questions

• LM92 with NOR-8451 I2C temperature sensor

  Hello!

  I try to communicate with a temperature sensor LM92 via the NI USB-8451 box by I²C Protocol. I have a problem with the address because the sensor 7-bit address is 1001011 (A1 and A0 set to 1) but the LM92 works in little endian (LSB first) and Labview adds the R/W bit at the end of the address, so that full frame sent to the LM92 is 1001011R/W.

  I'll try to find a solution to reverse the complete frame before seending to communicate with the LM92.

  LabVIEW returns the 301742 error because the address is not the wright one and I can't find how to send the address in little endian.

  I just need to read the record of the temperature of the sensor so I need to write anything in it.

  Does anyone have an answer?

  To solve the problem:

  The problem of addressing is not the address sent in Big Endian, my LM92 was on a Board and a pilot forbade LM92 sensor to connect with my USB-8451 (I don't know why yet).

  So I unsolder just my LM92 and improvement directly + 5V SDA SCL and GND wires on him and it works with examples of Labview you will find in HELP from-> examples

  Thanks for trying to help me MrHappyAsthma !

• NOR-8451 with embedded Windows

  The NOR-8451 is not compatible with Windows Embedded? I have LabVIEW on but I can't get 8451 drivers to install. When I run the installation of the drivers I don't get the error messages to give me an indication that something was wrong. Thanks for the help.

  Hi jmountney,

  Yes, the OR-8451 is compatible with Windows Embedded.   Depending on your version of Windows, you may need to add additional packages.  The model recommended to register is the "application compatibility", which should include everything you need.

  Nick

• Control of the ZL62044 of Zarlink with NOR-4851

  Hello

  We use Zarlink ZL62044 unit which is a 2 sons but not standard I2C.

  I'm am tryng to read and write in the Zarlink ZL62044 with the help of NOR-8451 Labview with the I2C read & write VI.

  Eran,

  Actually, looking at it more I realized 8451 can send a receipt of the signal if another master's write data on it. However, we cannot always ensure that the 8451 cannot send an ACK signal because the material on the 8451 follows the I2C Protocol, which automatically sends these signals.

• Use of NOR-8451 talk to TI BQ20Z60-> question address Chip

  I'm working on the product test this chipset use the TI LI-ON "gas gauge".  The chip talk bus smb and chip address 0 x 17.  In order to access some features you need to do a series of Scriptures to register 0 x 77 with the data 0 x 48, followed by a reading of the register 0 x 78.

  I can talk all day to the device using the smb TI-2300 adapter but can't seem to understand the sequence necessary to specify address 0 x 17, then the address of register 0 x 77 & 0 x 78.

  So I guess that the line background question how do you manage the addresses of the chip with the NOR-8451?

  I found the answer.  The chip required a PEC byte at the end.  I had to calculate the CRC and add it to the transaction among other things.

• Support for alarms diagnosis field according to FF - 912 with NOR-FBUS Configurator 3.2.3

  I tried to control the utility alarm monitor and diagnosis field according to FF-912 alarms since a FF camera H1 with NOR-FBUS Configurator 3.2.3.

  Alarms standard block for example in the case of a change of parameter are monitored in the alarm monitor.

  Field diagnosis according to FF - 912 alarms are not controlled.

  Are field alarms diagnosis according to FF - 912 took supported by the NOR-FBUS 3.2.3 Configurator. or something special to do to activate the analysis.

  If not, what tools or host systems are available for monitoring these alarms?

  Alarm in the software OR-FBUS monitor doesn't have a field of diagnostics alarms. You can try to use NOR-FBUS C API nifWaitAlert2 to monitor this alarm. We will find the detailed description of the API OR FBUS Hardware and Software User Manual Chapter 6.

• Encoder interfaced with NOR-9401

  I bought a coder who has open collector and resistance to pull-up 3.3 kohm (TTL) logic output.

  The encoder comes with four sons: power + 5V, GND, channel A and channel B. channel A and B are logic output.

  Channel A and B are connected to the OID of NOR-9401 which is mounted on the cRIO.

  A standard VI for encoder counting is used and compiled under the FPGA environment.

  During the measurement, I have observed that there are number of significant loss in both directions encoder.

  I don't think that there is a problem with VI like I used it several times on the encoders with output RS422.

  Is there a problem with my current encoder with respect to its electrical interface with NOR-9401?

  Thank you.

  I don't think that there is a problem with pull-up resistance. Even if the digital IO ports have their own resistance to pull-up (usually of the order of 4.7kOhm - should be included in the manual), the power to be handled by the circuit of encoder output transistor is about 2mA. -Check your configuration for a correct connection GND. You must connect the encoder directly power GND to DGND to the printed circuit board Terminal.

• connect labveiw 8.2 with nor pci-6251

  I have no pci-6251 and its cd driver with labview 8. How can I connect the daq with labview 8.2 and run programs

  Hello

  I can't download the driver of NOR-DAQmx 8.7.1, connect labview 8.2 with NOR-DAQmx PCI-6251...

  Why?

  Please answer...

• Using PCI-8532 with NOR-DNET 1.6.6 / NOR-DNET 2.0.2

  I have a PC with the following configuration test set-up:

  • Card PCI-8532 DeviceNet
  
  
  • Windows 7 Enterprise, SP 1
  
  
  • LabVIEW 2010 Runtime
  
  
  • NOR-DNET 1.6.6 with MAX 5.0
  
  
  • No environment of LabVIEW Development
  
  
  • PCI-8532 isn't available in MAX and Windows Device Manager indicates the card as "PCI Device" with an exclamation mark.

  Here is a screenshot of Windows and MAX Device Manager:

  

  I can't install the NOR-Industrial communications for DeviceNet 2.0.2 on this computer because I get the following error:

  

  Well, I have two questions

  1. How can I install and use the PCI-8532 and see with NOR-DNET 1.6.6? If this is not possible:
  
  
  2. How can I create an executable file on my system (portable) development with LabVIEW 2010 or 2011 LabVIEW and run this executable on the test set-up. I currently have on my development system:
  
  
  • Professional 2010 LabVIEW and LabVIEW 2011
  
  
  • NOR-DNET 1.6.6
  
  
  • No hardware OR at all
  
  
  • I have to install the NOR-Industrial Communications for DeviceNet 2.0.2 on my laptop (my development system)
  
  
  • This will interfere with my current NOR-DNET 1.6.6 and then I select which driver to use at compile time

  Thank you

  Nick

  Nick HY,

  No, it is defenitely not a replacement yet and I will work with our Web Department who make clearer on our web page.

  The development of the new API is pretty well done, but based on your feedback, we are planning to improve compatibility, so you can for example use the old APi 1.6.x and the new APi of 8532 on the same machine, so you can use the old and the new material on this same machine. Which would be important for you?

  For the moment we intend not to allow only one type of material on the same machine to save you development time. Let me know what you think.

  To clarify the situation today: The InCOM for Devicenet component is not part of LabVIEW. It's just a very simple means of communication with the I/o variables and blocks of function for the MS. The driver should install fine even without installed LV. The error message is quite a Bug on our side, and the solution would be to use the Builder installer LV to create a new installer that can install 2.0.x Incom Dnet driver without having installed Lv.

  And today, you should be able to have the 1.6.x both pilot 2.0.x in parallel and use the API 1.6.x with old boards yonce and the variable approach of IO 2.0.x with your new Board of Directors.

  I'll keep this post updated as soon as we have a stable Beta available I'll post something.

  DirkW

• problem with loopback test base with NOR-6008

  I recently started to use DAQmx in c# .NET 4.0 with NOR-6008 USB DAQ. I tried a loopback test by connecting output to an analog input analog and tried readign the signal from the output to the entrance but did not send the signal (or maybe a problem with the code). The analog input readign reads a random value rather than the value entered by the user for the output. I connected ao0 and ai3 on data acquisition. Here's the code.

  private void button1_Click (object sender, EventArgs e)

  {

  Task analogOutTask = newTask();

  AOChannel myAOChannel = analogOutTask.AOChannels.CreateVoltageChannel ("Dev1/ao0", "myAOChannel", 0, 5, AOVoltageUnits.Volts);

  AnalogSingleChannelWriter writer = newAnalogSingleChannelWriter (analogOutTask.Stream);

  Double analogDataOut;

  analogDataOut = Convert.ToDouble (AnalogOut.Text);

  writer. WriteSingleSample (analogDataOut, true);

  }

  Private Sub button2_Click (ByVal sender As Object, EventArgs e)

  {

  Task analogInTask = newTask();

  AIChannel myAIChannel = analogInTask.AIChannels.CreateVoltageChannel ("Dev1/ai3", "myAIChannel", AITerminalConfiguration.Differential, 0, 5, AIVoltageUnits.Volts);

  AnalogSingleChannelReader reader = newAnalogSingleChannelReader (analogInTask.Stream);

  Double analogDataIn is reader. ReadSingleSample();

  AnalogIn.Text = analogDataIn.ToString ();

  }

  Hello

  I built an application using your code (with task.verify) and it works beautifully.

  Have you tried different channels of inputs/outputs?

  

  Curt

• PWM with NOR-USB 94xx?

  Hello everyone,

  already, I asked once about the creation of PWM with hardware. And I was pleased with the response. But now I found 94xx Series-USB OR hardware. Here are the materials of high-voltage-Digital i/o. If any of you have already met with this one, would like to hear your conclusion about them. Would also appreciate if you could answer my question:
  Is it possible to create a PWM Signal with NOR-USB 94xx?

  Thank you

  Grigory

  Grekov wrote:

  I'd be more interested in the USB Module NI 9472 USB connection. Because it's the only one that would match my request.

  What is your application?

  Why don't choose you something in this list.

  If your condition is out to say 24 v PWM signal... you can also plan to use a custom circuit intermediate, not only to scale the output signal of the device (at 24 v) but also the reader following circuit.

• Clock and hw external trigger with USB-6210 on Linux with NOR-DAQmx Base?

  I have two devices USB-6210 I need to synchronize so that they both collect data exactly at the same time. I was told by support OR I can send the clock off Dev1/PFI4 and have the two USB-6210 s read the clock in through their own PFI0. I also want to trigger data collected for each device by sending a trigger off Dev1/PFI6 and have two devices to receive the signal on PFI2.

  All my attempts to try this are filled with error messages and my research online seem to say that's not possible with USB devices on NOR-DAQmx Base 3.4.0f2 on Linux.

  I "ve tried using example AI programs and those who do not seem to work either for external clocks. Here is the code I tried:

  #include "NIDAQmxBase.h"#include 
  
  #define DAQmxErrChk(functionCall) { if( DAQmxFailed(error=(functionCall)) ) { goto Error; } }
  
  int main(void){    // Task parameters    int32       error = 0;    TaskHandle  taskHandle = 0;    char        errBuff[2048]={'\0'};    int32       i;
  
      // Channel parameters    char        chan[] = "Dev1/ai0";    float64     min = -10.0;    float64     max = 10.0;
  
      // Timing parameters    char        clockSource[] = "/Dev1/PFI7";    uInt64      samplesPerChan = 1000;    float64     sampleRate = 10000.0;
  
      // Data read parameters    #define     bufferSize (uInt32)1000    float64     data[bufferSize];    int32       pointsToRead = bufferSize;    int32       pointsRead;    float64     timeout = 10.0;
  
  printf("Calling CreateTask...\n");    DAQmxErrChk (DAQmxBaseCreateTask("",&taskHandle));printf("Calling CreateAIVoltageChan...\n");    DAQmxErrChk (DAQmxBaseCreateAIVoltageChan(taskHandle,chan,"",DAQmx_Val_Cfg_Default,min,max,DAQmx_Val_Volts,NULL));printf("Calling CfgSampleClkTiming...\n");    DAQmxErrChk (DAQmxBaseCfgSampClkTiming(taskHandle,clockSource,sampleRate,DAQmx_Val_Rising,DAQmx_Val_FiniteSamps,samplesPerChan));printf("Calling StartTask...\n");    DAQmxErrChk (DAQmxBaseStartTask(taskHandle));printf("Calling ReadAnalogF64\n");    DAQmxErrChk (DAQmxBaseReadAnalogF64(taskHandle,pointsToRead,timeout,DAQmx_Val_GroupByChannel,data,bufferSize,&pointsRead,NULL));
  
      printf ("Acquired %d samples\n", pointsRead);
  
      // Just print out the first 10 points    for (i = 0; i < 10; ++i)        printf ("data[%d] = %f\n", i, data[i]);
  
  Error:    if( DAQmxFailed(error) )        DAQmxBaseGetExtendedErrorInfo(errBuff,2048);    if(taskHandle != 0) {        DAQmxBaseStopTask (taskHandle);        DAQmxBaseClearTask (taskHandle);    }    if( DAQmxFailed(error) )       printf ("DAQmxBase Error %d: %s\n", error, errBuff);    return 0;}
  

  When I run the resulting program, I see this:

  $. / acquireNScans-ExtClk
  The CreateTask call...
  Call for CreateAIVoltageChan...
  Call for CfgSampleClkTiming...
  Error-89136 DAQmxBase: route specified cannot be satisfied, because the hardware does not support it.

  For example, a clock and a trigger can be imported via one of the PFI lines by using a USB-6210 on Linux with NOR-DAQmx Base? A clock and a trigger exportable via one of the PFI lines?

  If so, does anyone have the code example illustrating how to do this, or can you at least tell me the names of the lines ("PFI0/Dev1" or other) so I can try again?

  Clues or suggestions would be helpful.

  Thank you

  -Tom

  The clockSource in the example specifies an output rather than an input channel channel. Change source "/ Dev1 / PFI0" solved the problem.

  Please close this post.

• How to calibrate the PCI-6110 with NOR-DAQmx

  Hello

  I am a new user of the PCI-6110 Council tries to run the calibration using LabVIEW procedure. I look at the document "Calibration" on the page of the manuals for the Board of Directors,

  http://sine.NI.com/NIPs/nisearchservlet?nistype=psrelcon&NID=11888&lang=us&q=FQL: 28locale % 3Aen % 29 + AND + % 28phwebnt % 3 A 1081 + OR + phwebnt % 3 A 7075% 29 + AND + 28nicontenttype % 3Aproductmanual % 29 + AND + % 28docstatus % 3Acurrent % 29% 20RANK % 20nilangs: en & title = NOR + PCI-6110 + manual

  One of the first steps in the document is to call the AI_Configure command to set the input mode, beach, etc. I'm using LabVIEW 8.5 with the NOR-DAQmx software, and I can not find the command (which, in LabVIEW, seems to be "AI Config.vi") anywhere. The calibration paper was written in 2003, and I gather from Google searches (please, correct me if wrong) that this command is actually a part of NOR-DAQ traditional, who was replaced by driver OR DAQmx.

  My question is this: what is the equivalent to AI_Configure command in the latest software? Is it perhaps a subsequent document describing how to calibrate using NOR-DAQmx?

  Thanks much for any help.

  Tom McLaughlin

  Hi Tom,

  The calibration Procedure series B, E, M, S, which is also linked from this page, describes how to calibrate the PCI-6110 with NOR-DAQmx.

  Brad

• or-scope with nor-6229

  Hi all

  I would like to know if I can use or pci-6229 with nor-soft scope? I found no information on it.

  Thank you

  Dima.

  
  

• All 32-bit applications crash with error 0xc000005 after windows Server 2008 R2 backup

  Hello world...

  I am in a big mess... and really need help!

  I did last night a Backup windows... but one of my users were connected to the server works with applications...

  and this morning No 32 no bits applications... same installer...
  the 64-bit application works very well...

  Others or generating an error 0xc000005 and stop...
  failing Ole32.dll module...

  And I'm sure that the backup is reliable, even if the backup of windows said it was successful...

  I tried to restore only the apps files... but it seems more complicated than that...

  If anyone has an idea...

  Hi, Emeric,.

  Thanks for posting the question on Microsoft Community.

  According to the description, it seems that 32-bit applications crash with an 0xc000005 error code in Windows Server 2008.

  As the question more appropriate forums Technet, write the topic in this forum for better support.

  http://social.technet.Microsoft.com/forums/en-us/WindowsBackup/threads

  Using the windows-related issues feel free to post on Microsoft Community.