search

parallaxinc / BlocklyProp

Blockly based visual programming editor for Propeller C
MIT License
44 stars 24 forks source link

S3 Add blocks to adjust calibration/default settings #1199

Open MatzElectronics opened 7 years ago

MatzElectronics commented 7 years ago

Give the user access to some non-volatile storage. C functions already in place.

wstodghill commented 7 years ago

@MatzElectronics - That should allow for the adjustment of the settings on what was referred to in the Spin Object as the hub variables - Am I understanding this correctly? These are some I was particularly interested in from the Spin Object...

Default values - These values are assigned to their respective variables on startup, unless overriding values are stored in EEPROM.

SOURCE CODE... DEFAULT_FULL_CIRCLE = 955 DEFAULT_WHEEL_SPACE = 153 DEFAULT_LIGHT_SCALE = 0 DEFAULT_LINE_THLD = 32 DEFAULT_OBSTACLE_THLD = 1

We could change these in the new C version of the S3 object using BlocklyProp - correct?

Of course, it would have many other uses as well... The above issue is one I was recently asking about...

MatzElectronics commented 7 years ago

@wstodghill These blocks will simply be for writing values to the user (open/blank) space in upper EEPROM. We could do another block that adjusts specific values like you describe above - we'll have to debate whether or not we want to open that functionality up...

wstodghill commented 7 years ago

Got cha!

MatzElectronics commented 6 years ago

@wstodghill, can you verify these blocks? Load a value, turn it off, unplug. Then reconned, and see if that value is still there? Thansk!

wstodghill commented 6 years ago

@MatzElectronics - Works great!

See - http://demo.blockly.parallax.com/blockly/editor/blocklyc.jsp?project=1604 and - http://demo.blockly.parallax.com/blockly/editor/blocklyc.jsp?project=1605

MatzElectronics commented 6 years ago

Standard EEPROM blocks tested and verified. Changing issue to reflect block request for setting defaults/calibration above.

wstodghill commented 6 years ago

@MatzElectronics - Thanks for addressing this concern Matt!