search

COAST-Lab / c3po

Coastal Conductivity Communication Probe
0 stars 2 forks source link

Copy EZO test code to use for Boron +modify #6

Closed BentleySettin closed 4 months ago

BentleySettin commented 4 months ago

Successfully modified the code that reported results onto VS code serial monitor.

Code found here: https://github.com/TinyCamML/ConductivitySensor/commit/7703fb7e5f5312fb9e9be97079b88f1de391776f Forum I used: https://community.particle.io/t/atlas-scientific-ardiuno-to-particle-code-issues/21860

BentleySettin commented 4 months ago

Examples of results (dry testing): 000000953 [mux] INFO: Starting GSM07.10 muxer 0000000955 [mux] INFO: GSM07.10 muxer thread started 0000001254 [mux] INFO: Gracefully stopping GSM07.10 muxer 0000001254 [mux] INFO: Closing all muxed channels 0000001255 [mux] INFO: Muxed channel 1 already closed 0000001255 [mux] INFO: Muxed channel 2 already closed 0000001256 [mux] INFO: Muxed channel 3 already closed 0000001256 [mux] INFO: Muxed channel 4 already closed 0000001257 [mux] INFO: Sending CLD (multiplexer close down) 0000002157 [mux] INFO: Received response to CLD or timed out, exiting multiplexed mode
0000002207 [mux] INFO: GSM07.10 muxer thread exiting 0000002207 [mux] INFO: GSM07.10 muxer stopped 0000002222 [ncp.client] INFO: Using internal SIM card 0000003314 [mux] INFO: Starting GSM07.10 muxer 0000003315 [mux] INFO: Opening mux channel 0 0000003315 [mux] INFO: GSM07.10 muxer thread started 0000003318 [mux] INFO: Opening mux channel 1 0000604456 [ncp.client] WARN: Resetting the modem due to the network registration timeout 0000604457 [mux] INFO: Stopping GSM07.10 muxer 0000604458 [mux] INFO: Gracefully stopping GSM07.10 muxer 0000604458 [mux] INFO: Closing all muxed channels 0000604458 [mux] INFO: Closing mux channel 1 0000604459 [mux] INFO: Muxed channel 2 already closed 0000604459 [mux] INFO: Muxed channel 3 already closed 0000604460 [mux] INFO: Muxed channel 4 already closed 0000605727 [mux] INFO: Sending CLD (multiplexer close down) 0000605729 [mux] INFO: Received response to CLD or timed out, exiting multiplexed mode 0000605729 [mux] INFO: GSM07.10 muxer thread exiting 0000605730 [mux] INFO: GSM07.10 muxer stopped 0000613237 [ncp.client] INFO: Using internal SIM card 0000618067 [mux] INFO: Starting GSM07.10 muxer 0000618068 [mux] INFO: Opening mux channel 0 0000618068 [mux] INFO: GSM07.10 muxer thread started 0000618071 [mux] INFO: Opening mux channel 1 0001219506 [ncp.client] WARN: Resetting the modem due to the network registration timeout 0001219507 [mux] INFO: Stopping GSM07.10 muxer 0001219508 [mux] INFO: Gracefully stopping GSM07.10 muxer 0001219508 [mux] INFO: Closing all muxed channels

SUPScientist commented 4 months ago

Could you add a note here about what is expected vs. actual behavior? It looks like what is pasted in the comment above is the actual behavior (i.e., what the system is doing). Is that what is expected/desired? I don't see anything that explicitly describes conductivity/conductivity data, so I'm not convinced this issue is ready to close unless there's a separate, more specific issue related to getting conductivity data.

Edit: https://github.com/TinyCamML/ConductivitySensor/issues/8 mentions the need to collect actual conductivity data.