Advanced Search

Model groups:
Each object of a model can optionally be assigned to a group. The assignment method can be called
on an existing object (2 lines of code)
Example 1: 'work_piece = Box(600,600,600)'
'work_piece.set_group('work')'
or the object can be created and the 'set_group' method called in one line.
Example 2: 'ReadPolyData('work_piece.stl', path_stl).set_group('work')'
Vismach will automatically create a checkbutton to show or hide each group used in the model.

class ModelGroups(object):
    def __init__(self, model):
        self.groups_in_model = {}
        self.get_groups(model)
        self.has_groups = len(self.groups_in_model.keys()) > 0

    def get_groups(self, objects):
        for item in objects.GetParts():
            if hasattr(item, 'group'):
                if item.group:
                    if item.group in self.groups_in_model.keys():
                        self.groups_in_model[item.group].append(item)
                    else:
                        self.groups_in_model[item.group] = [item]
            if isinstance(item, vtk.vtkAssembly):
                self.get_groups(item)

    def update(self, checkboxes):
        # SetVisibility does not seem to work on modifier objects so we use Scale
        for group in self.groups_in_model.keys():
            for checkbox in checkboxes:
                if checkbox.objectName() == group:
                    if checkbox.isChecked():
                        for item in self.groups_in_model[group]:
                            item.restore_scale()
                    else:
                        for item in self.groups_in_model[group]:
                            item.store_scale()
                            item.SetScale(0,0,0) 
 

• It prevents having to hardcode every possible GUI/component prefix inside POSTGUI_COMPONENTS.
• It handles custom user interfaces, custom PyVCP/GladeVCP panels, or non-standard naming schemes seamlessly.
• It allows users to decide explicitly where each net lives directly from the Rio Flow design environment.

• Use Case: I need to load and thread ClassicLadder (

  loadrt classicladder_rt ...

  , 

  loadusr -w classicladder my_logic.clp

  ) to handle auxiliary machine logic and map FPGA inputs/outputs directly to 

  %I

   and 

  %Q

   points before the motion thread starts.
• Currently, modifying generated main HAL files requires re-editing them after each export. Would it be possible to have a persistent "User HAL Block" or a dedicated non-destructive include file in Rio Flow?

• Use Case: Connecting physical hardware inputs mapped in RioCore to GUI-specific pins like 

  touchy.cycle-start

  , 

  touchy.single-block

  , or 

  halui.machine.on

  .
• Since these pins only instantiate after the display loads, they must live in the PostGUI phase. However, each time Rio Flow regenerates/exports the setup, the auto-generated PostGUI call chain (

  postgui_call_list.hal

   / 

  custom_postgui.hal

  ) gets wiped/reset.