raw.githubusercontent.com issues **SOLVED** Set ?forcerefresh=true in the URL.

http://raw.githubusercontent.com issues
Set ?forcerefresh=true in the URL.
Loading an entire workspace from http://raw.githubusercontent.com is currently causing severe lack of functionality in Chilipeppr.
Now, the problem appears to stem from Github, as using services like rawgit or hosting the “auto-generated-workspace.html” file locally fix the problem with their obvious security and efficiency drawbacks. Here’s the links that will be of interest:
Chilipeppr boot script: https://gist.github.com/PyroAVR/94c950ff62ec4ace1905

Github repository: http://github.com/PyroAVR/pyroavr-tinyg

Chilipeppr Workspace: http://chilipeppr.com/pyroavr-tinyg


You should fork /TinyGstaging instead as we moved all widgets to github

@jlauer I haven’t been able to crack this one. I can confirm that his boot code is entirely from the readme.MD, and using rawgit to host the raw github url does load the workspace without issue. He also substituted the rawgit url “preview” url into the boot script and everything loaded in CP.

The error when using the original boot script is:

Uncaught Error: Load timeout for modules: inline:com-chilipeppr-workspace-pyroavr-tinyg

John - Andy’s workspace was originally forked from github workspace-tinyg which is what chilipeppr/tinygStaging uses. So in a sense he’s already what you suggested.

check that there are square brackets inn the load statement. An old runme.js didn’t put them in

@jlauer Where should the brackets be?

Please compete against workspace-sample.


My brackets are in place correctly as compared to chilipeppr/sample. The only square brackets are in the cpdefine() statement, correct?

All you had to do was forcerefresh=true


Remember, CP caches everything and only refreshes if you force it to. This is so you can have 100% uptime regardless of all backing hosting sites like github.

Eureka! Thank you! I did not know that was the case.

Lessons learned. Thanks John.

  <div class="settings-overlay">
    <!-- <div style="position:absolute;border:1px solid green;height:100%;"> -->

      <button type="button" class="btn xbtn-xs btn-primary btn-touchplaterun" style="width:100%;">Run</button>

    <div class="" style="text-align:right;">Feedrate to Probe</div>
    <div class="input-group">
      <input class="form-control frprobe" type="number" placeholder="0.00" value="25">
      <div class="input-group-addon">mm/min</div>


    <div style="/* position:relative; <b>//</b> left:20px; <b>//</b> top:20px; */" xclass="pull-right">
      <div class="" style="text-align:right;/* padding-right: 30px; */">X plate dimension</div>
      <div class="input-group">
        <input class="form-control widthplate" type="number" min="0" placeholder="0.00" value="1.75">
        <div class="input-group-addon">mm</div>
    <div style="/* position:relative; <b>//</b> left:20px; <b>//</b> top:20px */" xclass="pull-right">
      <div class="" style="text-align:right;">Y plate dimension</div>
      <div class="input-group">
        <input class="form-control lengthplate" type="number" min="0" placeholder="0.00" value="2.00">
        <div class="input-group-addon">mm</div>
    <div style="/* position:relative; <b>//</b> left:20px; <b>//</b> top:20px */" xclass="pull-right">
      <div class="" style="text-align:right;">Z plate dimension</div>
      <div class="input-group">
        <input class="form-control heightplate" type="number" min="0" placeholder="0.00" value="2.60">
        <div class="input-group-addon">mm</div>

    <!-- <input type="number" class="form-control input-val z-threshold" value="1"/> -->
    <!-- </div> -->


There were enough issues in the past where any downtime was unacceptable, so I had to put that cache in place. It works brilliantly, but the downside is you have to know about it if you do development. Maybe we should add a comment in that auto-generated boot script.

Not a bad idea to mention that. That may have been causing issues earlier with my developments in JSFiddle as well, and I didn’t even realize it.

I mention it in the 3 videos i posted on the homepage on how to fork, but yeah, it should be made more obvious.

I must not have caught that when I went over those.

the super touch plate is intriguing. what does it do?

I saw a 3-dimensional touch plate on someone’s machine that was using Mach3. The idea was that it works like a carpenter’s square, it lines up with the corner of the workpiece, and then the machine touches off in x, y, and z to set its zero there, therefore making zeroes repeatable in all axes automatically. I’m nearly finished with it aside from the formatting, but I can’t seem to force the run function to wait until it receives a response from SPJS before sending the next command. I have some restructuring to do on that one.

I assume you can’t just send a bunch of the probe commands in a row and then read the responses asynchronously? Do you need to run one axis, then read results, then send probe for next axis? If so you’ll have to just do callbacks. Watch the onRecv and then call the appropriate callback when you see the result you are waiting for.