[rachel.murray]

We have made sure that the power supplies are sharing the same ground. There seems to be some issue with the serial connection to the modbus, maybe related to a conflict in the libraries that handle t

We have made sure that the power supplies are sharing the same ground. There seems to be some issue with the serial connection to the modbus, maybe related to a conflict in the libraries that handle the physical and software serial connections.

We are able to read values using SoftwareSerial as the Modbus serial connection and the ‘GetValues.ino’ script on the EnviroDIY Github (YosemitechModbus/Examples/GetValues), and we can also read values using a similar script with NeoSWSerial as the Modbus serial. However, we are unable to retrieve values using AltSoftSerial at all.

The software serial connections only work when I am running a simple test script that references the YosemitechModbus library. As soon as I try to run a logging script and reference the ModularSensors library, I can’t read any values off the Y4000, using either the modified SoftwareSerial library or NeoSWSerial. The brush is activated and then the serial output has some odd characters (sometimes it says ‘connection failed’) and then the script re-starts.

I have attached the output from the logging script, as well as the outputs from the ‘GetValues.ino’ script.

More...

Less...

Attachments:

1. 

   Altsoftserial_y4000_test.jpg
   

2. 

   softwareserial_y4000_test.jpg
   

3. 

   Screenshot-122.png
   

[rachel.murray]

Thanks for the reply,

Yes, I am working with Troy :). We have had some success with the decagon CTD, including using a wifibee and portable wifi hotspot to log data to monitormywatershed.org. It woul

Thanks for the reply,

Yes, I am working with Troy :). We have had some success with the decagon CTD, including using a wifibee and portable wifi hotspot to log data to monitormywatershed.org. It would be nice to have turbidity measurements as well, which is one reason we are interested in the Y4000 device.

In our y4000-mayfly setup, I have tried removing the wifibee modem, along with the associated code. I have also tried running with and without other sensors. We are currently testing using an external 12V power supply to power the y4000 (left on constantly for testing purposes). Regardless of the setup, the result is the same – the mayfly can’t seem to communicate with the sensor.

The mayfly reboots right after attempting to activate the brush. This makes a brownout seem like a likely problem, however connecting to an external 12V supply doesn’t seem to help. I’m wondering if there might be some sort of problem with the serial connection using Altsoftserial.

I’m going to try a few more tests and report back – are there any particularly useful debugging flags that could shed some light on the problem?

Thanks for your help,

Rachel

More...

Less...

Attachments:

1. 

   IMG-2601.jpg
   

2. 

   Screenshot-1.png
   

[Author]

Posts