Casting via the REST API

[Bolt]

Thank you for getting this implemented, this is going to be great!

Now, not to stare a gift horse in the mouth, but is there a way to access casts via the API?  Previously, I have been accessing all the data via modbusphp.  As such, I have hundreds of data points in MHR data, many casted as : D or :RD, depending on need.  To transition things to the API, it would be easiest to begin by simply referencing the existing locations, such as

Code: [Select]

/data/json?dataPoint=MHR400:RD, but I am presented with a "Bad Request" response.  Is there a simple workaround?

Again, not poo-pooing on your implementation, but I'm so eager to start implementing this that I don't want to re-write my program to contain everything in "real" double word or real address locations.

Thanks!

[BobO]

Thank you for getting this implemented, this is going to be great!

Now, not to stare a gift horse in the mouth, but is there a way to access casts via the API?  Previously, I have been accessing all the data via modbusphp.  As such, I have hundreds of data points in MHR data, many casted as : D or :RD, depending on need.  To transition things to the API, it would be easiest to begin by simply referencing the existing locations, such as

Code: [Select]

/data/json?dataPoint=MHR400:RD, but I am presented with a "Bad Request" response.  Is there a simple workaround?

Again, not poo-pooing on your implementation, but I'm so eager to start implementing this that I don't want to re-write my program to contain everything in "real" double word or real address locations.

Thanks!

The symbol processor handles it, but it may be an issue at the URL level. I?ll check tomorrow.

One thing that might work is to nickname the cast element, then reference the nickname.

[BobO]

After digging a bit, the symbol processor does not handle it. Honestly not sure why. I coded it, and the code is clearly handling bit casts, but is also clearly not handling any other form of cast. Possibly an oversight, but I always worry about stuff like that. When I'm elbow deep in it, decisions get made, time passes, and the reasoning gets lost...which is sometimes a bad thing when I come back second guessing. Sometimes there was no reasoning...just got missed. I'll ponder some more.

And in other bad news, I checked the nicknaming of a cast...that doesn't work either. Sorry.

[Bolt]

Well, this data belongs in a UDT anyways, not an array of Modbus Registers, that is becoming cumbersome.  I'll work that direction.  Thanks for clarifying.