Jump to content

1zhangyo

Members
  • Posts

    4
  • Joined

  • Last visited

Posts posted by 1zhangyo

  1. On 3/6/2023 at 9:45 PM, Fausto said:

    Hello @1zhangyo.

    How many and which MCC DAQ HATs are you using?  Which RPi module and OS version are you using?  Do you have other third-party HATS installed on your RPi module?

    Please confirm that the SPI and I2C interfaces are enabled on your RPi.  Go to the Raspberry start button and choose Preferences - Raspberry PI Configuration. Click on the Interfaces tab and make sure SPI and I2C are both enabled. 

    image.png

     

    The MCC DAQ HAT Manager utility can also read the EEPROMs and detect your MCC HATs.  Please provide a screen capture after pressing the LIST DEVICES button, in the application.

    image.png

     

    Please confirm that each board has the correct address jumper as mentioned in the hardware installation section of the documentation and list how are they stacked.  https://mccdaq.github.io/daqhats/hardware.html#installing-multiple-boards 

    Regards,

    Fausto

    Hi

    I am using 4 MCC DAQ HATs (4 mcc172 hats). My RPI model is 4B, OS is raspios-buster-arm64, and I don't have third-party HATS installed on my RPi module. The SPI and I2C interfaces are enabled on my RPi (as shown in figure 3). And I confirmed that each board has the correct address jumper.

    As for using MCC DAQ HAT Manager, when i press Read_EEPROMs button, it works well (as shown in figure 4), but when i press LIST DEVICES button, it shows nothing at all (as shown in figure 5).

    figure3.jpg

    figure4.jpg

    figure5.jpg

  2. Hi,

          I have stacked 4 mcc172 hats. When I ran sudo daqhats_read_eeproms, it worked fine (as shown in figure1). But when I ran sudo daqhats_list_boards, it found nothing at all. So I opened the daqhats_manager.py and ran it. It show error: Command ' daqhats_list_boards ' returnde non_zero exit status 1 (as shown in figure 2). 

          I have installed the appropriate address jumpers onto address header locations A0-A2 of the new HAT board. And I don't know why this problem happens. I would appreciate if you can help me figure this out!

    Yours sincerely!

    figure1.jpg

    figure2.jpg

  3. On 12/7/2022 at 4:29 PM, Mussa said:

    Hi @Jeffrey

    I carefully read MCC DAQ HAT LIBRARY (https://mccdaq.github.io/daqhats/c.html#c.mcc172_a_in_sensitivity_write).

    It says:

    "Write the MCC 172 analog input sensitivity scaling factor for a single channel.

    This applies a scaling factor to the analog input data so it returns values that are meaningful for the connected sensor.

    The sensitivity is specified in mV / mechanical unit. The default value when opening the library is 1000, resulting in no scaling of the input voltage. Changing this value will not change the values reported by mcc172_info() since it is simply sensor scaling applied to the data before returning it.

    Examples:

    - A seismic sensor with a sensitivity of 10 V/g. Set the sensitivity to 10,000 and the returned data will be in units of g.

    - A vibration sensor with a sensitivity of 100 mV/g. Set the sensitivity to 100 and the returned data will be in units of g."

    So I think that when we are using the sensitivity parameter, the polling program shows the value in "g".

    Is it correct?

     

    Why nobody answers you? I'm as confused as you are.

×
×
  • Create New...