| Author |
Message |
|
|
yes but not for those you want. If I get a chance I implement the change I suggested, but don't have much in terms of cycles so can't give a time.
|
 |
|
|
|
It gets difficult if you don't feel comfortable changing the modus C++ code on the arduino side. The code is easy to follow and change.
|
 |
|
|
There are several options presented in thread. If you don't feel comfortable with the C++ or looking at the Mango code, as stated earlier you ca create an event to write to each of the registers in your arduiono with a UNIX epoch timestamp from Mango.
|
 |
|
|
That is the one I used and modified on my own for my own consumption last year. Even if you add a broadcast in the arduino code, the UI on the Mango side won't let you add a broadcast address of 0. So elegant changes or a hacks needs to be made, hence my suggestions.
|
 |
|
|
You can't set the broadcast address of 0 on the mango UI. If you want to work with the existing code base, select another address say 1 as the "broadcast" address. Not sure what you have for modbus implementation on the arduino side but probably is minimalist and probably does not have broadcast handling capabilities. I am assuming you got what was floating around for free. I had to add modbus functions on the arduino side to do what I want. I did not do broadcast functionality but it should not be too hard to implement.
I would change the code to handle a "broadcast" address and have only one device respond to a request to the master and the others are passive listeners. That way only one entry is required on the Mango side along with a CRON event to trigger write the timestamp.
Otherwise you could probably use Mango events to fire off to write the date/time as a unix epoch timestamp or what ever format you want to send to registers in Modbus and manually configure a date/time point for each device. That would emulate a broadcast.
Not sure if that helps.
|
 |
|
|
Well that would explain the spikes.
I have simple feature request..Deadband option like that presented in the datalogger.
What is send period of 15 minutes do? It was not described in the help for this.
|
 |
|
|
I set up 1 feed with 9 data stream as a pachube publisher. I have the update event set to on change and snapshot send period of 15 minutes. I am not understanding why I get API rate increases every now and then. What in the configuration is causing such a high API request rate? Am I correct in assuming the the way I configured it should send changes to Pachube every 15 minutes? Or is every change in the point causing a pachube publish event regardless of the send period?
* Profile
* Feeds
* Favourites
* Messages
* Settings
* Subscriptions
API request rates
You were last rate-limited less than a minute ago (on Fri Oct 15 04:36:04 +0000 2010).
Requests using your API key were denied because you exceeded Pachube's rate limit policy.
Here are your API request counters for the last 3 minutes:
* 2010-10-15-04:36 --> 12
* 2010-10-15-04:35 --> 29
* 2010-10-15-04:34 --> 29
|
 |
|
|
Ok. My bad. I always sand-boxed myself in the data source world. I never used publisher and saw it. No brainer now.
|
 |
|
|
Well I added the point link back since I thought I saw it work without it. I can only make the push to pachube via the point links.
|
 |
|
|
|
I removed all point links. Now when I go back to point links the target point only has two entries in the drop down. I have a lot more than that as per the source point. Any idea why the drop down is populated with only two points?
|
 |
|
|
That did it. Left overs from something.
thx
|
 |
|
|
System setting = 1.9
See attached file for JSP.
|
 |
|
|
Serial.
WARN 2010-06-30 14:35:31,884 (org.directwebremoting.util.CommonsLoggingOutput.w
arn:59) - Marshalling exception: Missing method or missing parameter converters:
DataSourceEditDwr.saveModbusSerialDataSource
WARN 2010-06-30 14:35:31,884 (org.directwebremoting.util.CommonsLoggingOutput.w
arn:59) - --Erroring: batchId[3] message[java.lang.IllegalArgumentException: Mis
sing method or missing parameter converters: DataSourceEditDwr.saveModbusSerialD
ataSource]
|
 |
|
|
Pachube manual feed via put. I tried it without a point link. Works fine.
Thanks
|
 |
|
|
|
So in the name field of the panchube point detail, I enter the modbus tag name?
|
 |
|
|