Forum Replies Created
-
AuthorPosts
-
harrison
KeymasterI have designed the PCBs and have some (unassembled) sitting on my desk, but have not had time to assemble them. If you fancy doing some soldering I can send you schematics so you can do it right away.
harrison
KeymasterHi Nishant,
Do you not have any reactor at all?
You should be able to load the software without having a reactor involved if you disable all the “Initialise” functions in the software – these are responsible for checking reactors are there and setting default values for all the hardware.
If you do have a reactor, but it isn’t connecting properly and blaming the Multiplexer, there may be a fault with the PCB attached to the Beaglebone Black. This is a hardware issue with some boards – Labmaker should be able to fix it for you.harrison
KeymasterYes, send them an email. Mention I sent you and it seems you have a faulty pump board. Attach the logs above so they can see it is causing continual errors.
harrison
KeymasterFrom the look of the above it seems that there must be a faulty pump board. There should be very few such errors (maybe once every few thousand times you send the command, not EVERY time). It seems that in MOST of the logs you attached the system is able to correct the error (as it is designed to), but infrequently it fails to do this, which is why it then stays on for longer than expected. I expect the issue is a poor connection on the USB connector or circuitry on the Pump PCB, which Labmaker should be able to sort for you.
harrison
KeymasterVery good – I have just designed a custom PCB to fit this to Chi.Bio, will have them manufactured and keep you posted!
harrison
KeymasterBoth of those look promising, we could fairly easily integrate either into the Chi.Bio. Was your plan to have this combine with the Atlas sensor PCB?
harrison
KeymasterHi Gian – I assume you got this sorted (sorry, I didn’t see your topic previously). But yes, it seems multiplexer is the issue, a faulty PCB I expect.
harrison
KeymasterHi John, it looks like a faulty Multiplexer PCB. Has Labmaker gotten back to you on this front?
harrison
KeymasterLet me know when you get a chance to test that, in the meantime I will try to figure out what else could be done to fix it in software (though I think working hardware would be a better first step!).
I can now see your other replies to this thread with logs for when the system worked. In these cases you can see the connection to the pumps is still causing issues, but nevertheless it is able to recover. So, it seems sometimes the recovery fails – perhaps this could be fixed by adding additional checks to the recovery procedure, but this will then slow down the entire system in general.
-
This reply was modified 5 years, 4 months ago by
harrison.
harrison
KeymasterHi Pablo,
Looking at your log it says at the top:
| BeagleBoard.org Debian Buster LXQt Image 2020-05-18So it seems you are using the LXQt Snapshot, rather than the “Debian Buster IOT Snapshot” which is linked just below it on that page (and is I believe what is specified in the Chi.Bio software manual). I think if you install the IOT snapshot there should be plenty of room on the device.
harrison
KeymasterI will have a look at well – currently we are investigating implementing the Atlas PCB you linked previously.
harrison
KeymasterCertainly, different probes may be more accurate than others. However, I would focus right now on getting one that is able to easily integrate (i.e. physically fit!) within the test tubes you are using. Probably your application doesn’t need absolutely the best pH precision, right? More important is that it is timely, effective etc…
harrison
KeymasterSo, in IMG_9434 you are repeatedly switching the pump on-off-on with it set at 0.007 rate? Or, are you only switching it on-off-on when the camera pans to look at the screen?
If you keep toggling the pump on-off-on manually then it will pump at a higher rate since each time you turn it on it will output a small amount.However, this does not explain what happens at t=~20 in that video. At this point it seemed the pump somehow stayed on for much longer. Something similar happens at the start of 9433. I think these correspond to the entries in your PuTTY terminal saying “Failed transmission test on Pumps 1 times…” This happens if the digital communications with the Pump PCB fail first time around. It seems the software has identified this and is trying to fix it, but is then struggling to disconnect the multiplexer when it comes back around to try doing that communication again. This a hardware problem.
Do you ever see similar faults with turning on/off the LEDS? I.e. when you tell one to turn off/on and it doesn’t do so? If not, then it would indicate that the chip on the pump board is faulty, and so I would ask Labmaker to see if they can replace the pump board.Potentially we may be able to come up with a software fix that will mitigate the issue so long as it doesn’t happen all the time. It is good that the error is caught in the software, but it seems whatever is wrong with the communication to the pump is subsequently causing the multiplexer issues. Perhaps the following will help diagnose:
1. Go to the function “def setPWM….” in the code.
2. Immediately before the line “if sysDevices[M][device][‘startup’]==0:” (which is near the start of the function) add the following:if (ConsecutiveFails>0):
print(str(datetime.now()) + ‘ Attempting to retry PWM Transmission’)Note that in the above there needs to be a tab space indent infront of the print statement.
3. After the line “CheckHighON=I2CCom(M,device,1,8,channels[‘ONH’],-1,0)” inside “def setPWM” add the following:
if (ConsecutiveFails>0):
print(str(datetime.now()) + ‘ Completed retry of PWM Transmission’)4. Try running the new code and see what is shown in the Putty window when the excess pumping error occurs. I am puzzled by what you are seeing since it SEEMS that the self-correcting code is working (i.e. becasue it doesnt say it Failed the transmission test a second time), however it is evidently not having the desired effect (the pumps aren’t turning off as needed!).
harrison
KeymasterHi Gergo,
It is likely an electrical issue in assembly of the control PCB (the one attached to the Beaglebone). The Multiplexer is a part on this PCB.
I recommend contacting Labmaker and asking for a replacement – they should be able to send out a new one.harrison
KeymasterI think this looks like an interesting project and I’d be glad to help. I agree that the Atlas Scientific solution seems elegant, low cost, and I would be happy to make an adapter PCB to integrate this with the existing Chi.Bio.
The major challenge I foresee is mounting the PH probe itself in the device’s test tube – it seems the default probe from Atlas is quite large. They do have some smaller versions: https://atlas-scientific.com/probes/
Such as their micro pH probe: https://atlas-scientific.com/probes/micro-ph-probe/
But they are also quite expensive.What kind of probe were you thinking of using? There are others offered by companies such as ThermoFisher:
https://www.fishersci.com/shop/products/orion-9810bn-micro-ph-electrode/13299511
Though they are even more expensive.Harrison
-
This reply was modified 5 years, 4 months ago by
-
AuthorPosts