Hello,

I have OpenJausv3.3.0b and I'm running on Windows.
Sometimes the nodeManager's application crash. Is it a known problem?
In addition, the broadcast mechanism working only on subsystems (subsystemId.255.255.255). Is there any way to fix it?

Thanks in advance,
Mayan.

Mayan,

There have been a few fixes to OpenJAUSv3.3b that may fix your crashing problem. You can get a copy of the latest code from the version3.3c repository on openjaus.googlecode.com.

As for the broadcast mechanism problems, we need to know more about your system setup. Can you post a copy of your nodeManager config files? Have you read our tutorials about setting up the node manager?

Thanks
Tom

According to your suggestion, I've download version c. I hope it will fix the nodeManager's collapse.
Is there somewhere list of changes that you made from b to c?

Regard to the broadcast problem, I tried again with version c and I still have a problem.
For example, when I send message with destination 255.255.255.3, all components recieve the message.

I don't know why, but I don't succeed to upload the configuration file, so I copy it:

# This subsection defines the JAUS characteristics of the node
[JAUS]
SubsystemId: 17
NodeId: 1
Subsystem_Identification: OJSubsystem17
Node_Identification: OJNode1

# This subsection defines the interfaces and their options for component communication
[Component_Communications]
JAUS_OPC_UDP_Interface: true
OpenJAUS_UDP_Interface: true

# This subsection defines the interfaces and their options for node communication
[Node_Communications]
Enabled: true
JUDP_Interface: true
JUDP_IP_Address: 127.0.0.1
#JAUS_OPC_UDP_Interface: true
#JAUS_OPC_UDP_IP_Address: 127.0.0.1

# This subsection defines the interfaces and their options for subsystem communication
[Subsystem_Communications]
Enabled: true
JUDP_Interface: true
JUDP_IP_Address: 188.168.0.17
#JAUS_OPC_UDP_Interface: true
#JAUS_OPC_UDP_IP_Address: 192.168.0.10

You can find a list of changes in the Changelog.txt file in the repository. Also, you can view the "changes" in the googlecode source browser.

As for the broadcast problem, you have a problem with your node manager configuration. You cannot configure the Node_Communications IP address to use the loopback: 127.0.0.1. It will confuse the internal routing logic of the node manager. This is probably the reason you're having problems with broadcast. If you do not have a node network, then just set the Node_Communications Enabled: false.

I've looked in Changelog.txt but I think it details the changes between version a and b (the date is 8.9.09).
Is this page list the changes?
http://www.openjaus.com/downloads

Here is my new configuration file. The problem remains (in version b and c).

# This subsection defines the JAUS characteristics of the node
[JAUS]
SubsystemId: 17
NodeId: 1
Subsystem_Identification: OJSubsystem17
Node_Identification: OJNode1

# This subsection defines the interfaces and their options for component communication
[Component_Communications]
JAUS_OPC_UDP_Interface: true
OpenJAUS_UDP_Interface: true

# This subsection defines the interfaces and their options for node communication
[Node_Communications]
Enabled: false
#JUDP_Interface:
#JUDP_IP_Address:
#JAUS_OPC_UDP_Interface:
#JAUS_OPC_UDP_IP_Address:

# This subsection defines the interfaces and their options for subsystem communication
[Subsystem_Communications]
Enabled: true
JUDP_Interface: true
JUDP_IP_Address: 188.168.0.17
#JAUS_OPC_UDP_Interface: true
#JAUS_OPC_UDP_IP_Address: 188.168.0.17

The latest Changelog.txt can be found by browsing the code here:

code.google.com/p/openjaus/source/browse/?repo=version33c

Now that we've ruled out your config file problem. I've looked into the code repository and I see that the current version of the node manager will route the message to all components and all instances if either the destination component is 255 or destination instance is 255. I'm not sure if this is a mistake or if this was done by intent. I'd have to go back and revisit the design. Do you have a need to route the message to instance 3 of all components on all subsystems? This seems like a very strange and rare case. What are you trying to do? Can you provide me with a simple diagram of your system? How many subsystems do you have, how many nodes and components? Where do they reside and how are they connected?

I still don't understand. I need a better idea of what you are trying to do, and I'll be able to provide you with a solution.