Jump to content

As of July 17, 2015, the LabJack forums here at forums.labjack.com are shut down. New registrations, topics, and replies are disabled. All forums are in a read-only state for archive purposes.

Please visit our current forums at labjack.com/forums to view and make new posts. To post on the current forums, use your labjack.com login account. Your old LabJack forums login credentials have been retired. There are no longer separate logins for labjack.com and LabJack forums.



  • Please log in to reply
1 reply to this topic

#1 RogerRamjet

  • Members
  • 4 posts

Posted 28 June 2012 - 10:29 PM

Hi I am unable to find descriptions for what 'x1's are, and what channels are. I Googled for a Glossary on the Labjack site but it gave no results.

For example, I am trying to understand how the U3 I2C EEPROM block works, particularly the Combined Read Write section. If I hover over the eAddGoGet block, it describes one of the pins as 'ax1s Write (U8 Arrays)', which is not clarified by looking at the array that is coming in. It seems that an array of 4 0's is appended to an array of zeros the same size as the write that took place in the write section of the diagram. I dont really understand this clearly, so I Google for the page describing eAddGoGet.


This describes that pin as "ax1s An array which is the list of x1s.", so again I have no idea what an x1 is. Also I am struggling to understand the information flow into and out of the eAddGoGet block, is there somewhere that describes what I have to put in these arrays, and what will come out?

A have also failed to find what a Channel is, initially I thought it was a port pin but the data flow into the eAddGoGet block seems to indicate otherwise.

Thanks for any pointers

#2 LabJack Support

LabJack Support
  • Admin
  • 8677 posts

Posted 29 June 2012 - 10:23 AM

Start with the overview in Section 4.1:


With most IOTypes, what to pass for Channel should be obvious. That is, it is the physical input or output channel that the iotype is working on. If it is not obvious, there should be a note in Section 4.3, which is the go-to section for more information.

The biggest exception to Channel being obvious, is the config iotypes such as LJ_ioPUT_CONFIG. This often is used to configure something device-wide, rather than for a particular channel, so the Channel parameter is used to pass what you are configuring (e.g. LJ_chLOCALID would be to write a new local ID).

For I2C, Section 4.3.11 should have all the information you need:


In fact, the pseudocode in 4.3.11 is also for an EEPROM read, so look at this and see if it clarifies what you are seeing in LabVIEW. Let us know if you have any further questions.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users