Im from Austria, pls forgive me my old bad english.
1)
Using 2 Pcs of XBee 1mW-Moduls for RC-Function 100meters, is it correct to use also the “XCTU”-Software to get comunication between this moduls? Can i followe the explaining-videos shown on YouTube?
2)
Does it work when taking this SSC-32 servo sequencer Utility, redesing it with the bought flowbotics-software(Deleting last 6 Servos(26-31) on the third under-menue)? Or will there be an error-message because i didnt Change any programming i only deleted those servo-symbols?
3)
When deactivating such hook on a servo(in the Software), is it like the function with 0ms on the control-cable to the servo? Will it deactivate the servo without any motor-function?
4)
How can i add a Switch-Symbol+LED to a servo, where the Switch has the function: SW1 pos0=1500ms(0%)/pos1=1300ms(-20%)…SW2 pos0=also1500ms(0%)/pos1=1100ms(-40%)…SW3 pos0=1500ms(0%)/pos1=900ms(-60%)…same for Switches 4-5 for -80% and -100%…? A Servo should have no slider(min/max/Center) no arrows only those 5 Switches with adjustable Milliseconds for each Switch? maybe 10 Switches 5 for negative and 5 for positive%?
5)
How can i add a vertical slider instead of this horiz.slider on such a servo, rest should be same?
Please find below answers to your questions/comments:
We are unsure what you mean by “using the XCTU software to get communication”. Typically, you use this software combined with two (or more) XBee modules and a USB dock (for the XBee). You then connect to each module using XCTU software to change the XBee module settings to whatever you need (network ID, target/source address, encryption, etc.). Once all your modules are setup, you should not need the XCTU software anymore. In a case with a SSC-32U, you would typically have one configure XBee module on the SSC-32U directly and another configured XBee module on a USB-XBee adapter on the computer running your software.
Please let us know if we misunderstood your question and we’ll be glad to review our answer appropriately.
We are unsure which videos you are referring to. Please provide a URL to said video in your reply.
To be honest, we never did try to simply just delete modules. Since FlowBotics Studio works in a dataflow paradigm and that each component has to be connected to inputs/outputs using “wires” between the modules, it is possible nothing bad will happen. The modules that produce output for those servos control components (and use their outputs as input) will most likely simply not work whereas the other will most likely continue to function without issue.
Also, please note you can also simply make the parts you do not want to see invisible in the interface. Here is an example:
If you completely delete the block, the result is uncertain without looking deeper into the Ruby code that generates the outputs to the SSC-32U. Most likely it will send a default value (this may indeed be 0, or it could be 1500 or something else).
If you simply make the blocks invisible in the interface, nothing will chance and the channels will most likely have a pulse of 1500 µs coming out. That being said, if you have nothing connect to those channel pins, it does not really matter.
To do this, you will need a few things:
You will need to understand better how FlowBotics Studio works and also read up a bit on Ruby, since you will have to at least modify some Ruby code to make this work. The FBS user manual is a good place to start. You may also want to check out this page and read at least Getting Started.
You will have to look at the Ruby code of the sequencer and the sliders to understand how values are transferred from the slider to the sequencer/SSC-32U. Once you understand that, you should be able to make switches using the existing primitives that will send values to the sequencer/SSC-32U properly.
Please note that while this is certainly possible, you will have quite a bit of learning to do and therefore this will not be trivial.
You can find the slider objects by searching for them:
As mentioned above, you will need to figure out how the current slider interacts with the rest of the code if you wish to replace it with a different slider.
