@executivul Thanks makes sense and I just started to read simular explaination in other places, but yours helped.
How about rpm ? Is it generally considered that higher RPM is better, or at least not being limited by a low speed ? I've seen 1 300w spindle rated at 60,000rpm would this be better than a higher power slower spindle ?
@neverdie so to get the max rated RPM out of a dc motor you need to operate at its max rated voltage ? with no PWM ?
Running a DC motor rated at say 12-60V with PWM at only 12V would never get to top speed ?
Am I understanding correctly ? Thanks for the link
@neverdie 
Now I'm even more confused with this difference between brushed and brushless...
@neverdie Thanks thats what I thought, but I'm confused about the voltage range of some of the spindles. They use variable DC voltage to regulate speed ? I don't thinks so, they use PWM at any voltage I provide it with, no ?
So the V range specified on DC spindle is just what it can be driven at, and its the PWM which actually controls the speed ? Is this right ?
Thanks
Just found a more powerful one...
@rfm69 link text
So could this or the 30A version, power an 800w DC 0-48V motor ?
@coddingtonbear What materials are you milling ?
I want to get a spindle for mostly wood, just hobby, but don't want to go too cheap, and face buying over when I realize its just not > W
I'm also looking for a good spindle so thanks for the links and comments.
Thought I'd share this link text. Its the 30A High Power Single way H-bridge DC Motor Driver Module. That "Frank From Germany" found and is using as part of his tool changing, along with a current sensor so he can brake, reverse and control speed on his tool changer, via arduino, to make it all work.
@bjornhallberg Thanks for the info, I got a bit frustrated trying to find this on the rawcnc website... i was in some loop, very frustrating.
I'm going to learn with the mpcnc and then posisble upgrade if I can justify it, or feel more flush. But thanks for the info...
This shipping costs, can be a big factor, so I do understand, but the openness and transparency or generally communicating well, which you don't get at all from most china suppliers, and some closer is just as important.
@bjornhallberg Any estimate on the cost of mechanical parts ?
feeding too much solder into the joint before you've heated up both sides, and melting the solder on the iron instead of the pins or board before those parts are hot enough.
@neverdie I'm gathering parts to make the same 3d printer with the carbon rods. I understood the weight reduction on the moving parts with carbon rods was the reason to go for them. And with the light 3d printer head that model can print much faster because of the stability and lightness. Which perhaps dosn't apply for the 2418 cnc ?
@neverdie you mean the tool changer, yes he has a blog and git pages where he shares. Its neccessary to speed control with current limiting breaking the spindle, which he's done via cheap ebay motor controller and arduino. Same goes for the spindle locking mechanism powered by a servo. and the CNC software..
Heres the git link text
Heres the blog link text
Its not step by step, perhaps he'll get their but I know he'll be happy if people copy, or chime in :), or add
@neverdie I saw this stepcraft automatic tool changer, its nice, but the design aproach of Franks is really novel, and way cheapper, simple ingenious. But my skill level is much lower, so I could be wrong
@scalz Agreed... the P&P is beyond my knowledge level, but what I found fascinating in what and how he was doing the project to make something himself, how he evolved the project was very interesting.
He's got something similar for a tool changer on a 3d printer which is very nicely designed... along with the software and controllers.
Perhaps slightly off topic but I wanted to share very interesting youtube channel of FRANK from Germany link text who's been working on a PCB pick and place module along with a CNC tool changer in the video above.
Very inginious, and clever work if you've not come accross his videos and work yet.!
I updated a few things, perhaps not all working properly yet, but have put a git page up at https://github.com/dudman8/MysensorsPairNodeLocal
Added registering multiply pairings, flashing led to indicate if nodes are in pairing mode etc. Still needs some work though, any feed back welcome.
Id like to add some messaging so controller could query the nodes and how they are connected, and configure them also from the controller, but don't know yet how to to this with templates and custom buttons etc in mycontroller.
@user2684 Thanks, I've implemented something myself with changes to the library, just playing around to understand it better. But will look at the SensorSonoff you mention.
Thanks again, its a great library.
Had a quick look at 1.7 dev branch is this ready for using already, testing or trying, or have you got more to do before its refactored etc ? I was interested in looking what the changes in architecture were.
@scalz Agreed, It might be anough for me, but a good cheap learning platform
@neverdie Generally I get the feeling from reading other peoples experience that its a mistake to quickly make the machine too big because of rigidity. But people do make mods to address this issue or to add heavier spindles.
Heres one mod i/d like to do link text
But to change the size just need to get new pipes which even if you use SS they are they cheapest part.
@monte I didn't think, or worry to much yet about the exact logic of buttons or what would happen with confused logic between controller yet. I just commented some things out for testing so I could get it working again, after I had refactored it into the separate class. I think I agree with you and what you said, but have to get my head around it.
The avdweb_switch.h code, it isn't mine, but I took it from link text. I'll document and finish up the code a little more, and of course happy to share everything.
I've been trying the NodeManager code as well, which made me want to modualize your code a little, because well I get confused easily and need things to look simple.
@neverdie The same web site has a few other designs for larger machines.
@neverdie They've already answered the concrete idea, many people consider that, but a simple center support I think solves the problem. They have nice forums over at the vicious.com link I shared.
@neverdie Yes thats the one... I'm got it working but am waiting a few things by post to be able to connect the 3d printer. And then I need still to order a new spindle.
There are some modifications people have made on thingyverse to strenghten the Z access to take heavier spindles... you can redesign the connecting corners and just print them out.
I'd like to get a 1.5kw spindle, but might just get a small one to begin with.
Or you could try a MPCNC link text. I'm just finishing one myself.
@scalz Thanks for the suggestion. By CS do you mean the DI00 on rmf69 and pin2 INT0 on mini pro ?
I get confused by these things, so need to confirm.
What type of value pullup would you suggest. Again I'm new to this.
Thanks
@monte I was wondering if you'd used it or what your experience of it was. I'm also just enjoying learning by doing... but wanted to see the node to node communication working and more easily configurable. I'd like to configure this from the controller also perhaps.
I've moved much of the functionality to its own class so that it can be more easily added to nodes. Heres what I've got so far.
I used avdweb_Switch.h to simplify and abstract a little the button press/etc.
I'd still like to clear up a little and add a few more things, like having multiply nodes paired together etc.
Its still pretty much your origional code.
There was a small error that both nodeid & sensorid had to be different from the master and slave paired node... that was in gateway.ico
Gate Way.ico
/**
* The MySensors Arduino library handles the wireless radio link and protocol
* between your home built sensors/actuators and HA controller of choice.
* The sensors forms a self healing radio network with optional repeaters. Each
* repeater and gateway builds a routing tables in EEPROM which keeps track of the
* network topology allowing messages to be routed to nodes.
*
* Created by Henrik Ekblad <henrik.ekblad@mysensors.org>
* Copyright (C) 2013-2015 Sensnology AB
* Full contributor list: https://github.com/mysensors/Arduino/graphs/contributors
*
* Documentation: http://www.mysensors.org
* Support Forum: http://forum.mysensors.org
*
* This program is free software; you can redistribute it and/or
* modify it under the terms of the GNU General Public License
* version 2 as published by the Free Software Foundation.
*
*******************************
*
* DESCRIPTION
* The ArduinoGateway prints data received from sensors on the serial link.
* The gateway accepts input on seral which will be sent out on radio network.
*
* The GW code is designed for Arduino Nano 328p / 16MHz
*
* Wire connections (OPTIONAL):
* - Inclusion button should be connected between digital pin 3 and GND
* - RX/TX/ERR leds need to be connected between +5V (anode) and digital pin 6/5/4 with resistor 270-330R in a series
*
* LEDs (OPTIONAL):
* - To use the feature, uncomment any of the MY_DEFAULT_xx_LED_PINs
* - RX (green) - blink fast on radio message recieved. In inclusion mode will blink fast only on presentation recieved
* - TX (yellow) - blink fast on radio message transmitted. In inclusion mode will blink slowly
* - ERR (red) - fast blink on error during transmission error or recieve crc error
*
*/
// Enable debug prints to serial monitor
#define MY_DEBUG
// Enable and select radio type attached
//#define MY_RADIO_NRF24
//#define MY_RADIO_NRF5_ESB
#define MY_RADIO_RFM69
#define MY_RFM69_FREQUENCY RFM69_433MHZ
//#define MY_RADIO_RFM95
// Set LOW transmit power level as default, if you have an amplified NRF-module and
// power your radio separately with a good regulator you can turn up PA level.
#define MY_RF24_PA_LEVEL RF24_PA_LOW
// Enable serial gateway
#define MY_GATEWAY_SERIAL
// Define a lower baud rate for Arduino's running on 8 MHz (Arduino Pro Mini 3.3V & SenseBender)
#if F_CPU == 8000000L
#define MY_BAUD_RATE 38400
#endif
// Enable inclusion mode
#define MY_INCLUSION_MODE_FEATURE
// Enable Inclusion mode button on gateway
//#define MY_INCLUSION_BUTTON_FEATURE
// Inverses behavior of inclusion button (if using external pullup)
//#define MY_INCLUSION_BUTTON_EXTERNAL_PULLUP
// Set inclusion mode duration (in seconds)
#define MY_INCLUSION_MODE_DURATION 60
// Digital pin used for inclusion mode button
//#define MY_INCLUSION_MODE_BUTTON_PIN 3
// Set blinking period
#define MY_DEFAULT_LED_BLINK_PERIOD 300
// Inverses the behavior of leds
//#define MY_WITH_LEDS_BLINKING_INVERSE
// Flash leds on rx/tx/err
// Uncomment to override default HW configurations
//#define MY_DEFAULT_ERR_LED_PIN 4 // Error led pin
//#define MY_DEFAULT_RX_LED_PIN 6 // Receive led pin
//#define MY_DEFAULT_TX_LED_PIN 5 // the PCB, on board LED
#include <MySensors.h>
unsigned long currentTime = 0;
int waitTime = 10000;
int masterNodeAddr = 0;
bool masterNodeAddrPresent = 0;
int masterSensorAddr = 0;
char str1[8];
char str2[8];
bool pairing = 0;
//Messages for answering pairing requests
MyMessage msg(254,V_VAR2);
MyMessage msg2(254,V_VAR2);
//Time counter function instead delay
boolean isTimeUp(unsigned long *timeMark, unsigned long timeInterval) {
if (millis() - *timeMark >= timeInterval) {
*timeMark = millis();
return true;
}
return false;
}
void setup()
{
// Setup locally attached sensors
}
void loop()
{
//We are keeping ids of pairing nodes only for 10 seconds while pairing
if(isTimeUp(¤tTime, waitTime)) {
masterNodeAddr = 0;
masterNodeAddrPresent = 0;
}
}
void receive(const MyMessage &message) {
//I used specific message type for filtering out pairing request
if (message.type == V_VAR1) {
Serial.print("Incoming message. Node - ");
Serial.print(message.sender); Serial.print("-");
Serial.print(message.sensor);
Serial.println(message.getString());
// If we had already a pairing requests within the last 10 seconds ? Then lets setup ready to pair
if (!masterNodeAddrPresent) {
currentTime = millis();
masterNodeAddr = message.sender;
masterSensorAddr = message.sensor;
masterNodeAddrPresent = 1;
}
// Listening for the second node slave to request pairing.
else if (message.sender != masterNodeAddr ) { //&& message.sensor != masterSensorAddr) {
//Construct message string with node and sensor ids
snprintf(str2, 7, "%d;%d", message.sender, message.sensor);
snprintf(str1, 7, "%d;%d", masterNodeAddr, masterSensorAddr);
Serial.print("First address: "); Serial.print(str1); Serial.print("Second address: "); Serial.println(str2);
// Send answer to nodes
msg.setDestination(message.sender);
send(msg.set(str1), true);
wait(500);
Serial.println("Sent message to second address");
msg2.setDestination(masterNodeAddr);
send(msg2.set(str2), true);
wait(500);
Serial.println("Sent message to first address");
masterNodeAddr = 0;
masterSensorAddr = 0;
masterNodeAddrPresent = 0;
Serial.println("Pairing finished");
}
}
}
Button.ico
/*
* Description on node
*/
// Enable debug prints to serial monitor
#define MY_DEBUG
// Enable and select radio type attached
#define MY_RADIO_RFM69
#define MY_RFM69_FREQUENCY RFM69_433MHZ
#include <MySensors.h>
#define CHILD_ID 3
#include <avdweb_Switch.h>
#include "pair.h"
#define SET_BUTTON_PIN 5 // Arduino Digital I/O pin for button/reed switch
#define BUTTON_PIN 4 // Normal button PIN
Switch button = Switch(BUTTON_PIN);
PairLocal pairLocal = PairLocal(SET_BUTTON_PIN);
// I think send to controller the button regardless if its paired directly
void presentation()
{
// Send the sketch version information to the Controller in case node is'nt paired
//if (!paired) {
sendSketchInfo("Binary paired button", "1.0");
present(CHILD_ID, S_MOTION);
//}
}
void before()
{
pairLocal.before();
//optionally pass function in, This button node won't recieve messages to do something from a slave
uint16_t ptr = &arryChange;
pairLocal.setParedMessageRecievedFunction(ptr);
}
// Function called when a paired master node sends a message
void arryChange()
{
}
void setup()
{
pairLocal.setup();
}
void loop()
{
pairLocal.loop();
// Process our own sensors additional button
button.poll();
// button was pushed
if (button.pushed()) {
pairLocal.sendPairedMesage();
} else {
// if (!paired) {
//MyMessage msg(CHILD_ID, V_TRIPPED);
//send(msg.set(0)); // NOT SURE IF WE NEED THIS ????
// }
}
}
void receive(const MyMessage &message)
{
pairLocal.receive(message);
// Do any additional processing here.
}
Relay.ico
/*
* Description on node
*/
// Enable debug prints to serial monitor
#define MY_DEBUG
// Enable and select radio type attached
#define MY_RADIO_RFM69
#define MY_RFM69_FREQUENCY RFM69_433MHZ
#include <MySensors.h>
#define CHILD_ID 1
#define RELAY_PIN 5 // Arduino Digital I/O pin number for relay
#define RELAY_ON 1 // GPIO value to write to turn on attached relay
#define RELAY_OFF 0 // GPIO value to write to turn off attached relay
#define SET_BUTTON_PIN 4
bool relayState;
MyMessage msg(CHILD_ID,V_LIGHT);
#include <avdweb_Switch.h>
#include "pair.h"
PairLocal pairLocal = PairLocal(SET_BUTTON_PIN);
// I think send to controller the button regardless if its paired directly
void presentation()
{
// Send the sketch version information to the gateway and Controller
sendSketchInfo("Relay", "1.0");
present(CHILD_ID, S_LIGHT, "Test light", true);
// Send saved state to gateway (using eeprom storage)
send(msg.set(relayState),true);
}
void before()
{
pairLocal.before();
// Setup the relay
pinMode(RELAY_PIN, OUTPUT);
digitalWrite(RELAY_PIN, 1);
delay(1000);
digitalWrite(RELAY_PIN, 0);
// Set relay to last known state (using eeprom storage)
relayState = loadState(CHILD_ID);
digitalWrite(RELAY_PIN, relayState ? RELAY_ON : RELAY_OFF);
}
void setup()
{
pairLocal.setup();
//optionally pass function in, Relay change state
uint16_t ptr = &processPairMessageFromMaster;
pairLocal.setParedMessageRecievedFunction(ptr);
}
void loop()
{
pairLocal.loop();
}
void receive(const MyMessage &message)
{
pairLocal.receive(message);
// Additional process message from Gateway
if (message.type == V_LIGHT && !message.sender) {
// Change relay state
relayState = message.getBool();
digitalWrite(RELAY_PIN, relayState ? RELAY_ON : RELAY_OFF);
// Store state in eeprom
saveState(CHILD_ID, relayState);
// Write some debug info
Serial.print("Incoming change. New status:");
Serial.println(relayState);
}
}
// Function called when a paired master node sends a message
void processPairMessageFromMaster()
{
Serial.println("Relay changed state by master node");
digitalWrite(RELAY_PIN, relayState ? RELAY_OFF : RELAY_ON);
relayState = relayState ? 0 : 1;
}
Finally got it working, and starting to understand it, had to change a few things, perhaps because its on latest version of mysensors, or possible because of old values in eproms.
Thanks for sharing, want to make a few changes or additions to suit my needs will share more as I have something working.
@monte Great, just looking now, looks good. Thanks for sharing that.
Thanks for the info, I've got it working on boards which arn't already soldered to radios, however just cant burn a new bootrom to a board with a RF69 soldered across pins miso mosi and sck. Is this normal ?
Great code, another question.
For the SensorDimmer, each sensor has only one type set so a dimmer can't receive v_status & v_percentage messages.
I've worked around this by registering two sensors at the same Analog out pin. But they don't then have access in a nice way to the status of each other as values are changed. So if I turn the led on/off via the v_status message I can't preserve the previous percentage, set by the other v_percentage sensor.
Is this normal ? I'm new to all this but at least mycontroller lets you specify for a single sensor both v_status,v_percentage so both types of messages can be sent and processed in onRecieve()...
Perhaps some enhancement on the SensorDimmer class could do this ? in ModeManager.cpp (if (message.type != _type) return;) inside Sensor::recieve.... isn't that too restrictive ?
You could do this dynamically, on the light nodes have a little button that sends out a message which is valid for say 60s, any other button/door node that would send a message within that time could become paired
The SensorSwitch/Door/Motion all work on interrupt pins only ? Sorry if I've misunderstood the code, thats possible.
Anyway I've made a few changes so that busywait, if thats what they are called buttons can be also used. I'll see if I can use git somehow to share the changes, or show them at least
Great library, looking to convert other things to use this.
@mahesh2000 If you find anything be sure to post it hear... I've used the hook up method for mini pro and rf68 which are nicly shown in a post here https://forum.mysensors.org/topic/1723/which-is-better-rfm69-or-nrf24l01/32
@skatun Can you use git, not an expert... but I think thats the way to go...
I noticed these being sold on ebay, together, cheaper than the FRM69HW on their own. Was wondering if the old RFM12Bs would still be usable in the network ?