-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Teensy40 Unable to connect #12
Comments
When compiling with Arduino both methods works for me. Something amiss in platformio.ini? "Unable to connect" is a bit vague - do you mean unable to communicate? If unable to connect then you may have driver issues, are the ports showing up in the device manager? If so, is connection is refused? I do not have PlatformIO installed and are not familiar with the ini-file structure so I am afraid I am not of much help regarding that. |
Connected but no data coming on the stream. I tried with putty too and no
response to any input. (Tested "$$", "G0 X3", $I" etc.) My board is a blanc
Teensy 4.0 with no pins connected to anything. I´d suspect the board to
return an error if in E-Stop or similar state but nothing. After grounding
all pins, i actually made it respond but my goal was to achieve steprate of
between 600k steps/s and 4M steps/s to driva a galvo but it seems i will
not get close to that. I maxed out at 200... I will abandon this for the
time beeing...
Den mån 2 aug. 2021 kl 14:33 skrev Terje Io ***@***.***>:
… When compiling with Arduino both methods works for me. Something amiss in
platformio.ini
<https://github.com/grblHAL/iMXRT1062/blob/master/grblHAL_Teensy4/platformio.ini>?
default_envs is set for teensy41, have you changed that?
"Unable to connect" is a bit vague - do you mean unable to communicate? If
unable to connect then you may have driver issues, are the ports showing up
in the device manager? If so, is connection is refused?
I do not have PlatformIO installed and are not familiar with the ini-file
structure so I am afraid I am not of much help regarding that.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#12 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEYS3MMLB6NNNPOAEFBF3ULT22GA3ANCNFSM5BMMKCVQ>
.
|
If estop is asserted (default if all pins left open) only a real-time request,
IMO not possible with a microcontroller. IIRC my FPGA based Smoothstepper (for Mach3) tops out at 1M steps/s. You have step/dir driven galvos? I made an experiment earlier with a 16 bit I2S D/A converter for analog output instead of step/dir signals - but I did not tune anything to find the max frequency possible. This was with a STM32F446 dev. board. Here is a XY plot on my scope I made then: |
I made my own Galvo controller that takes step/dir and outputs XY2-100. The protocol is 2MHz and sentences are 20bit so 100000 positions per second, but the galvo is much faster with a setting time of 0.4ms. I am currently giving it a try to ignore any planning and just calculate the number of positions I can manage to send in the timeframe of the upcoming move and then divide the travel of the command move with that number of positions and output as many positions along that path as I can manage. so far it looks good as the setting time outperforms any need for correction of mechanical issues normally present as jitter jerk etc. |
Would you have any interest in helping out in developing this? |
Sounds like a job for the Pi Pico to generate the XY2-100 protocol stream - via a PIO program. We've made a driver for grblHAL for it that outputs step/dir signals via PIO code and shift registers with sub microsecond resolution of the step signals...
Interesting, but I have far too much on may hands to get involved. |
ok Tnks, I got my head straight yesterday and got on track to make a implementation. As I dont think it needs the same kind of complexity as a 3d printer firmware maybe I can get away with a minimalistic implementation. I will push it to OpenGalvo when done... |
So I came around to making a first pre alpha version of my implementation: https://github.com/opengalvo/OPAL |
changing in my_machine.h :
#define BOARD_T40X101
//#define BOARD_T41U5XBB
and leaving the following commented out:
//#define USB_SERIAL_CDC 2
OR setting it to
#define USB_SERIAL_CDC 2
Compiling with PlatformIO Uploading with Teensy Loader 1.54
Used both FTDI-Driver and built in Microsift Serial Driver on Win10 to test, both configured to 115200 8N1.
Used UGS and PUTTY to test connection.
The text was updated successfully, but these errors were encountered: