I2C custom display and real-time reports

[petehughes55]

Hi, I have created a wireless jog controller and a wireless display and I would like to get the real time status information sent to the display. I would like to create an indicator that shows that status of the probe pin so I can test that all is working before I start a probe cycle. I know I can do this with ioSender, but I am using MillMage to drive my mill and having to switch between apps (and computers) just slows my workflow down. I have also created a macro to do a Z probe (after a tool change) that I can activate from my jog controller, so having an indication that the probe is functioning would be very helpful.

I have searched and searched but cannot find a solution.

I hope someone can help me?

Thanks
Pete

[terjeio]

Do you have wireless communication with the pendant up and running?
Via Bluetooth?
Which controller?

[petehughes55]

I am using ESP-NOW for the communications. I have an ESP32 acting as the I2C interface talking to my teensy 4.1 controller. I have a waveshare 4.3 inch touch panel as the keypad and a "Cheap Yellow Display" (CYD) as the display. The keypad sends the jog (etc.) commands to the interface which then sets the strobe active (low) and the controller consumes and responds.

The controller sends the binary machine status packets back to my interface which then forwards them on to the display and the controller.

All of this is working well and having pulled the latest version of the teensy firmware the jogging works really well too - I had issues with jogging and the 2nd order acceleration until I flashed the latest code.

As I said I would just like to get the real-time status info to the display so I can see the pin states and hence display an indicator to show the touch pin state. I am sure I will think of other uses for it as time goes by :o)

On a side note - I had to modify the keypad plugin code slightly to increase the amount of time before it checks to see if the keypad was there (I added retry code too) as there was a bit of a race condition going on between the teensy 4.1 and the Arduino Nano ESP32 - the teensy always won until I delayed it.

[terjeio]

The I2C interface plugin provides pins status etc. Are you using this or something you made?

On a side note - I had to modify the keypad plugin code slightly to increase the amount of time before it checks to see if the keypad was there (I added retry code too) as there was a bit of a race condition going on between the teensy 4.1 and the Arduino Nano ESP32 - the teensy always won until I delayed it.

Yep, the ESP32 is slow to boot up so that is to be expected.

[petehughes55]

I am using the standard I2C interface plugin, but I am not getting any status messages when the touch input changes state.

[terjeio]

It is a "bug", replace this line with:

    probe_state_t probe_state = hal.probe.get_state();

    status_packet.signals = hal.control.get_state();
    status_packet.signals.probe_triggered = probe_state.triggered;
    status_packet.signals.probe_disconnected = !probe_state.connected;

I'll fix it in the next commit.

[petehughes55]

Thank you so much for looking into this for me, your solution works perfectly :o)

I really appreciate you taking the time to answer my query.

Pete

[terjeio]

Fix committed.