« first day    last day (27 days later) » 

tlfong01
tlfong01
1:49 AM
You are welcome. Take your time, no hurry at all. I am also going very slowly, along (1) "A long and winding road": https://www.youtube.com/watch?v=cWpRY0flS2U
I might from time to time, pause and take a break, if case you couldn't follow. By the way, I have 5 hobbyist's years (2008 ~ 2013) in Arduino. You might like to let me know your experience in Arduino or Rpi, so I know if I should run faster, so not to bore you, or walk slower, to explain something in more detail, so not to misleading you. For example, I was wondering if I should pause and explain the operation of the "pullup op…
 
 
1 hour later…
saeed sadati
saeed sadati
2:54 AM
hi, I worked with the raspberry pi serial port.I received and sent data.
I think that's the problem, Because my sensor has this problem.
https://reedpaper.wordpress.com/2018/08/22/pulse-oximeter-max30100-max30102-how-to-fix-wrong-board/
 
 
8 hours later…
tlfong01
tlfong01
10:37 AM
Ah, I didn't catch you. What do you mean by "Rpi serial port"? Is it I2C, or SPI, or UART? Actually if you can use "IC detect -y 1" to find the device, then as I said earlier, your I2C hardware wiring and software setup is more or less OK. I know you get zero results now. But as I suggested earlier, perhaps don't be ambitious or greedy to get the sensor output.
Be humble and go back to just read the max30100's Part ID register first. I will show you this readMax30100PartIdRegister.py later.
By the way, I read the following blog post again and found something wrong. reedpaper.wordpress.com/2018/08/22/…. The guy Valeriy Yatsenkov's explanation of why the module was wrong and how to fix it seems problematic. SO DON'T TRY HIS FIX for now. Let me think again and let you know later.
In the mean time I would suggest to go back to square one and do the "i2cdetect -y 1 " and tell me your results. Then I will give you the "readMax300PartIdRegister.py()" program to do the second test.
Your testMax300.py run with the following results: i.stack.imgur.com/miYRF.png seems to indicate that you are doing well in every step EXCEPT the last step to read the sensor.
You might like to look closely at the schematic (Fig 4 of my answer), and let me know if you more or less understand how the the Rpi 3V3 I2C signals outside and MAX30100 1V8 I2C signals inside the module work.
Ah, supper time. See you late this evening, or tomorrow. Cheers.
 
tlfong01
tlfong01
11:46 AM
I have drafted a test program to read the max30100's Part Id register, as listed in the very end of my answer. I would suggest the following testing procedure:
(1) Run the test_max30100.py(), with zero results, as expected. Even with zero output values, this at lease confirms the following: (a) I2C setup OK, without Error #121, I/O transmission error.
(2) Test my buggy "read_max30100.py()" program (listing at the very end of my answer). By the way, I don't have the real thing in hand to do the testing. So far I have been googling and just guessing. So don't be surprised if you find "a few" bugs! Anyway, it would be nice if you can do the debugging for me :) Good luck and cheers.
 
 
1 hour later…
saeed sadati
saeed sadati
1:22 PM
hi, max30100 device address 0x57 is detected.
 
tlfong01
tlfong01
Good. Now (1) Run your old program that give zero results, make sure no Error #121， (2) Debug my beta read Part Id register program. Good luck. Cheers.
 
 
4 hours later…
saeed sadati
saeed sadati
5:03 PM
in Program Listings ,(2) Setting up multiple I2C buses:
import fprint53 as fprint
import ftime53 as ftime
I didn't understand what these two were!
 

« first day    last day (27 days later) »