search

EnviroDIY / YosemitechModbus

A library to use an Arduino as a master to control and communicate with the modbus sensors produced by Yosemitech. Depends on the EnviroDIY/SensorModbusMaster library.
Other
10 stars 7 forks source link

Test CHL sensor #2

Closed aufdenkampe closed 8 months ago

aufdenkampe commented 7 years ago

Sara didn't have one to test.

aufdenkampe commented 7 years ago

My test output of the Chlorophyl sensor (Y514 Chlorophyl with brush) is discussed in issue #3.

SRGDamia1 commented 6 years ago

Can you verify timing for me for the Chloropyhll sensor?

I would like to know how fast it will respond to any command, how long after the sensor begins taking readings until something stable comes out, and how fast new readings can be returned.

aufdenkampe commented 6 years ago

Here are some result tests for my Y514-A Chlorophyll sensor with Wiper (YL3617022701, hw 1.2,sw 2.0). Note that these tests use:

Results:

Output from ChangeSlaveID_AltSoftSerial.ino, changing from 0x05 to 0x03, with debugging on.

ChangeSlaveID_AltSoftSerial.ino
Allowing sensor and adapter to warm up
10...9...8...7...6...5...4...3...2...1...

Changing Slave ID:
Raw Request >>> {0x05, 0x10, 0x30, 0x00, 0x00, 0x01, 0x02, 0x03, 0x00, 0xA4, 0x63}
No response received.
Raw Request >>> {0x05, 0x10, 0x30, 0x00, 0x00, 0x01, 0x02, 0x03, 0x00, 0xA4, 0x63}
No response received.
Raw Request >>> {0x05, 0x10, 0x30, 0x00, 0x00, 0x01, 0x02, 0x03, 0x00, 0xA4, 0x63}
No response received.
Raw Request >>> {0x05, 0x10, 0x30, 0x00, 0x00, 0x01, 0x02, 0x03, 0x00, 0xA4, 0x63}
No response received.
Raw Request >>> {0x05, 0x10, 0x30, 0x00, 0x00, 0x01, 0x02, 0x03, 0x00, 0xA4, 0x63}
No response received.
Raw Request >>> {0x05, 0x10, 0x30, 0x00, 0x00, 0x01, 0x02, 0x03, 0x00, 0xA4, 0x63}
No response received.
Raw Request >>> {0x05, 0x10, 0x30, 0x00, 0x00, 0x01, 0x02, 0x03, 0x00, 0xA4, 0x63}
No response received.
Raw Request >>> {0x05, 0x10, 0x30, 0x00, 0x00, 0x01, 0x02, 0x03, 0x00, 0xA4, 0x63}
No response received.
Raw Request >>> {0x05, 0x10, 0x30, 0x00, 0x00, 0x01, 0x02, 0x03, 0x00, 0xA4, 0x63}
No response received.
Raw Request >>> {0x05, 0x10, 0x30, 0x00, 0x00, 0x01, 0x02, 0x03, 0x00, 0xA4, 0x63}
No response received.
Address change failed!

Output from Modbus Runner via USB-RS485 adaptor, changing from 0x05 to 0x03, successfully.

SEND: 05 10 30 00 00 01 02 03 00 A4 63 
GET: 05 10 30 00 00 01 0F 4D

This is confusing, because it appears that the send requests are identical!

aufdenkampe commented 6 years ago

It worked!

Output from ChangeSlaveID_AltSoftSerial.ino, changing from 0x05 to 0x03, with debugging on.

ChangeSlaveID_AltSoftSerial.ino
Allowing sensor and adapter to warm up
10...9...8...7...6...5...4...3...2...1...

Changing Slave ID:
Raw Request >>> {0x05, 0x10, 0x30, 0x00, 0x00, 0x01, 0x02, 0x03, 0x00, 0xA4, 0x63}
Raw Response (8 bytes) <<< {0x05, 0x10, 0x30, 0x00, 0x00, 0x01, 0x0F, 0x4D}
Address change complete.

Output from GetSlaveID_AltSoftSerial.ino.

GetSlaveID_AltSoftSerial.ino
Allowing sensor and adapter to warm up
10...9...8...7...6...5...4...3...2...1...

Scan takes several minutes, please be patient!

Scanning for Yosemitech modbus sensors....
------------------------------------------
Modbus Address ------ Sensor Serial Number
     0x03      ------    YL3617022701

This was my bad, because I first ran ChangeSlaveID_AltSoftSerial.ino with the wrong model number, and although it said it failed, it actually succeeded in reseting the SlaveID, so when I ran it again with the correct model number, it didn't work because the SlaveID had already been changed.

aufdenkampe commented 6 years ago

Here is where I shared some timing results for the Y514 sensor: https://github.com/EnviroDIY/YosemitechModbus/issues/3#issuecomment-316819583

I'll need to retest.

aufdenkampe commented 8 months ago

This should have been closed a long time ago. The Y514 works well with this repo!