[Pi IoT] Alarm Clock #21: Domotics

RE: [Pi IoT] Alarm Clock #21: Domotics

pettitda — Thu, 22 Sep 2016 23:44:35 GMT

Looks like from the oscilloscope shot above that the baud rate is maybe 38400. Your capture window shows a baud rate of 9600. Can you recapture with 38400?

RE: [Pi IoT] Alarm Clock #21: Domotics

mcb1 — Fri, 02 Sep 2016 10:58:48 GMT

Frederick

You may find the first sequence is the address, then the rest is either data read or write depending on the module.

I'm sure someone will have cracked this, so keep searching.

mark

RE: [Pi IoT] Alarm Clock #21: Domotics

Robert Peter Oakes — Mon, 29 Aug 2016 18:55:54 GMT

This protocol may well be ModBusRTU, an old but still very popular industrial control protocol. ModBusRTU being the serial version of this ModBus protocol and is often used along with RS485 to improve range (Distance) and reliability.

it is also possible you have the wrong baud rate and are therefor not seeing as much change in data as you should (Or more), try playing around with that to see if it makes a difference. you could also veryfy with an oscilloscope for the timing

https://en.wikipedia.org/wiki/Modbus

another point is that if it is MODBUS RTU then the serial port would be set slightly different as described in this document:-

Modbus Protocol

Hope this may help

Peter

RE: [Pi IoT] Alarm Clock #21: Domotics

Jan Cumps — Mon, 29 Aug 2016 17:29:19 GMT

Long live Belgian designs [View:/resized-image/__size/16x16/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-04a72d1e-7703-4c68-a16e-d40fbe370754/4048.contentimage_5F00_1.png:16:16]

The 0x0c is the form feed character. One would expect that they'd use a line feed to separate lines.

RE: [Pi IoT] Alarm Clock #21: Domotics

volly — Mon, 29 Aug 2016 14:31:45 GMT

[mention:ca2fe37c8c70477fb45e83ddaf152e5d:e9ed411860ed4f2ba0265705b8793d05], I have full confidence that you will get it done....by the deadline or not...but you will complete this project 100%.

Just keep at it Budd!!!