# Jogging issues X-Carve (old) **URL:** \ **Category:** ❓ Something's Up\ **Created:** [March 31, 2026, 5:05pm UTC](https://forum.sienci.com/t/jogging-issues-x-carve-old/26066 "2026-03-31T17:05:55Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Dac](https://forum.sienci.com/letter_avatar_proxy/v4/letter/d/a9a28c/32.png) [@Dac](https://forum.sienci.com/u/Dac)\ **Post date:** [March 31, 2026, 5:05pm UTC](https://forum.sienci.com/t/jogging-issues-x-carve-old/26066/1 "2026-03-31T17:05:55Z")
Hi all, First post. History: I have an original kit version of an inventables X-Carve (1000x1000). It has been idle for about a year. It ran flawlessly using Vetric and picsender to create and carve files. Picsender disappeared from my laptop and I downloaded and installed the latest version. 3 laptops later, 2 died. I can’t find the new version of picsender (now an Easel product??). I downloaded gSender. I set it up and connected it to the CNC (USB). It would not connect. Checked device management and it was not listed as a usb device, it showed up as xcarve in other devices, checked it and it indicated no driver available. Searching Easel’s site I found a driver EaselDriver\_0.4.5.d4d27bc2ce.exe, downloaded and installed. The cnc now shows up as a serial device under usb. It connected. The Jogging controls were greyed out. Changed settings and it was active, or so I thought. Current problem: When I try to jog to set XYZ to set zero I get an “error on line number. Undefined/ N/A “ I can still carve but the setup is really weird. 1: Disconnect the cnc from g-Sender. 2: Disconnect the machine from x-controller (using emergency stop). 3: Manually set XYZ to the material. 4: Reconnect the x-contoller. 5: Reconnect gSender. 6: Load job, (gSender assumes 0,0,0 for XYZ on connecting). It works fine. I have to go thru the same routine when changing bits as well, Just the Z axis. I downloaded Candle and UGS, Tried both. Got UGS to connect but did not like either. I like gSender’s interface, resembles picsender. Would like to know if anybody has run across this or has any suggestions to try. Thanks, Don ---
**Author:** ![Karver\_One](https://forum.sienci.com/user_avatar/forum.sienci.com/karver_one/32/11233_2.png) [@Karver\_One](https://forum.sienci.com/u/Karver_One)\ **Post date:** [March 31, 2026, 11:04pm UTC](https://forum.sienci.com/t/jogging-issues-x-carve-old/26066/2 "2026-03-31T23:04:22Z")
I did an AI search for you. This is the response. Working with the soft limits might help. It appears your [X-Carve](https://www.google.com/search?ibp=oshop&prds=pvt:hg,pvo:29,imageDocid:5009907067501676036,gpcid:11261882211853180980,headlineOfferDocid:4507328124799452101,catalogid:15196346408165600525,productDocid:13223302356140117811&q=product&sa=X&ved=2ahUKEwjai42TncuTAxWqRjABHUI-AScQxa4PegYIAQgCEAI) is encountering a specific communication or firmware reporting error in gSender that is preventing the software from properly calculating movement commands, leading to the “undefined” error during jogging. **Potential Causes and Solutions** The behavior you described—where jogging is greyed out or throws errors, but the machine can still run pre-loaded code—often points to a discrepancy between gSender’s expected machine state and the actual GRBL firmware settings on your X-Controller. - **Status Report Configuration** : gSender requires the machine to report its “Work Position” (WPos) rather than just “Machine Position.” If this isn’t set, jogging controls may fail to update or return “NaN” (Not a Number) or “Undefined” errors. - **GRBL Version Incompatibility** : The original X-Carve often shipped with an older version of GRBL (pre-1.1f). gSender is optimized for GRBL 1.1 or later. If your firmware is too old, it may send “Bad number format” or undefined errors during real-time jogging commands ($J). - **Soft Limit Conflicts** : If soft limits ($20=1) are enabled but your machine isn’t homed, gSender may block jogging because it thinks the move will exceed the machine’s boundaries, resulting in an “undefined” target or “Error 15”. - **Jogging Speed/Rate Resets** : In some versions of gSender (notably 1.5.0), the “Normal” jogging speed can randomly reset to 0, which triggers “Error 22: undefined feed rate” when you try to move. Again this is an AI response. Someone here might know more. ---
**Author:** ![Dac](https://forum.sienci.com/letter_avatar_proxy/v4/letter/d/a9a28c/32.png) [@Dac](https://forum.sienci.com/u/Dac)\ **Post date:** [April 12, 2026, 10:30pm UTC](https://forum.sienci.com/t/jogging-issues-x-carve-old/26066/3 "2026-04-12T22:30:06Z")
Thanks for the info. I tried the soft limits first, no help. I just flashed the grbl on the x-carve to 1.1g and it appears that has cleared the issues. Probing works, jogging works. Thanks again, issue is resolved for now ---
**Author:** ![Karver\_One](https://forum.sienci.com/user_avatar/forum.sienci.com/karver_one/32/11233_2.png) [@Karver\_One](https://forum.sienci.com/u/Karver_One)\ **Post date:** [April 13, 2026, 1:26am UTC](https://forum.sienci.com/t/jogging-issues-x-carve-old/26066/4 "2026-04-13T01:26:01Z")
Glad you are up and running and the Flash suggestion worked. ---
**Author:** ![gwilki](https://forum.sienci.com/user_avatar/forum.sienci.com/gwilki/32/366_2.png) [@gwilki](https://forum.sienci.com/u/gwilki)\ **Post date:** [April 13, 2026, 1:53am UTC](https://forum.sienci.com/t/jogging-issues-x-carve-old/26066/5 "2026-04-13T01:53:03Z")