Mango M2M Community

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?

Ctrl-F5, Clear recent history (Firefox), tried in in IE, restarted mango, still the same dialog.

I upgraded to 1.9 and wanted to change the update period on the modbus data source. I get a dialog box that says error and no description.

Used to work in v1.8.

So I downloaded v1.9 and wanted to try out the pachube feed. I have data collected over modbus and wanted to publish a point to pachube as my "hello world" test.

I created a point link from modbus point to pachube point. That worked. Is that the best practice for doing this under Mango?

Great. It is nice when progress is made.

I transfer write registers to separate variables. If I need feeback of a write I use seperate read registers. That way I know my embedded code is performing correctly.

I will be hacking a broadcast as well for my nightly time syncs. Slave ID of 0 is not allowed from the ui. I will pick one arduino to respond to an address 1 request while the others are passive and used that as my broadcast address.

I used that one as well. It does not have a modbus function 6 which is what is sent out from Mango. I hacked a function 6 in the arduino and I can write to it now. It is not pretty and plan on create a class someday to abstract the communication layer.

The Mango datapoint entry UI is set to accept a slave address of 1-240 so if I understand your reply, Mango cannot support modbus broadcast without changes to the application layer of Mango?

I suppose hack my ardiunos to take address 1 as a "broadcast" rather than the standard 0 address and hardcode only one device to send a response back.

What I ended up doing was setting a softpoint to contain the epoch in local time based on a CRON pattern. e.g. every 10 seconds. I can't think of another way to get the current timestamp to use in the event handler.

I used the schedule to fire once a day to feed an event to set the time into the given setpoint to be sent to the slave.

What I wanted was to use the softpoint to do it. e.g. CRON once a day, then set the the time for all slave devices. e.g. p.value = timestamp. Alas, this cannot be done at the softpoint level. It seems I have to create a schedule time event for each slave, then a event handler for each schedule event.

Another option is that I can change the arduino code to deal with slave ID of 0 and implement a broadcast write. Will Mango deal with broadcasts and if it does what doe it expect back?