Skip to content
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

Open
Bx3mE opened this issue Aug 2, 2021 · 8 comments
Open

Teensy40 Unable to connect #12

Bx3mE opened this issue Aug 2, 2021 · 8 comments

Comments

@Bx3mE
Copy link

Bx3mE commented Aug 2, 2021

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.

@terjeio
Copy link
Contributor

terjeio commented Aug 2, 2021

When compiling with Arduino both methods works for me. Something amiss in 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.

@Bx3mE
Copy link
Author

Bx3mE commented Aug 4, 2021 via email

@terjeio
Copy link
Contributor

terjeio commented Aug 4, 2021

I tried with putty too and no response to any input.

If estop is asserted (default if all pins left open) only a real-time request, ?, is responded to.

my goal was to achieve steprate of between 600k steps/s and 4M steps/s to driva a galvo

IMO not possible with a microcontroller. IIRC my FPGA based Smoothstepper (for Mach3) tops out at 1M steps/s.
If the g-code contains a lot of small movements max step rate is limited by the planner buffer size, larger -> faster up to a point. 300KHz is possible, and one user reported a 600KHz step rate after modifying limits (min step pulse with is currently 2.5us) - but that was from a move from a single g-code command.

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:

dac

@Bx3mE
Copy link
Author

Bx3mE commented Aug 6, 2021

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.

@Bx3mE
Copy link
Author

Bx3mE commented Aug 6, 2021

Would you have any interest in helping out in developing this?

@terjeio
Copy link
Contributor

terjeio commented Aug 7, 2021

The protocol is 2MHz and sentences are 20bit so 100000 positions per second

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...

Would you have any interest in helping out in developing this?

Interesting, but I have far too much on may hands to get involved.

@Bx3mE
Copy link
Author

Bx3mE commented Aug 7, 2021

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...

@Bx3mE
Copy link
Author

Bx3mE commented Aug 17, 2021

So I came around to making a first pre alpha version of my implementation: https://github.com/opengalvo/OPAL

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants