I am looking for assistance on an application we are developing. The requirements are making available an analog and multiple discrete values from the on-board I/OX card of a GX400 to a client application utilizing the WAN interface. Ideally we would like to make the GX400 a modbus slave exposing these values that can be read by a master on demand. Can someone give me a call to quickly discuss the application and possible configurations for this use case?
You can access I/O with the “devicetree” API. Some elements on the tree are dedicated to IO access. You can then use the “socket” API to open a server socket. You would have to implement a Modbus Slave module, or you could implement your own protocol. If you need your socket available to the WAN you need to forward a WAN port to the local interface (by default the AAF server socket are not reachable from WAN for security reasons). To forward the port you have to configure it in ALEOS in “Security>Port Forwarding” and forward your port to 127.0.0.1.
I hope this will help.
What version of ALEOS supports the I/O XCard?
When using the Device tree
local DIN1 = ‘system.aleos.io.in1’ works fine…
local din1 = assert(devicetree.get (DIN1))
local DIN2 = ‘system.aleos.io.in2’
local din2 = assert(devicetree.get (DIN2))
produces an error at runtime.
In thread: 0xcded0: error: main.lua:67: handler not found
Is there new firmware that is available that enables this to work?
Also is there a link to the Device tree for the GX400 with the I/OXCard
“The list of all variables and their meaning is partially device-dependent, and is given in a separate document.” Where is this separate document?
Just a quick update, I upgraded to ALEOS 4.3.6 and the DIN2 now works as expected.
I am still looking for documentation for the devicetree and the GX400 with the I/O XCard…
The closes thing I could find is: https://eclipse.googlesource.com/mihini/org.eclipse.mihini/+/5d104425f63a99568466ac223b5e292789abcb1f/agent/agent/treemgr/maps/aleos.map
but that doesn’t include the extra I/O
I thought I would add this since I finally found the documentation for the devicetree
developer.sierrawireless.com/Res … ccess.aspx
Although it still doesn’t have the Xcard I/O